What is up with Beta 3 and Phones becoming unresponsive?

[iShorty]

I noticed it on beta 2 and now it happened again on beta 3 when returning to my phone from it being on sleep for 5+ hours.

Basically, the phone doesn't wake up while holding the power button or pressing the power button.
'Hard reset' doesn't do anything, however if you hold the 'hard reset' for an extra 20+ seconds (as well as the 10 odd seconds it's meant to take) it seems to then boot up.

Strange but fun.

 

[Armen]

No, not exactly. There should be no ill effects if your phone locks up since this is not a phone you rely on for daily use. And if it is, that is completely on you. Come here to discuss it, but you have no room to blame Apple for anything.

Here are a few things you are not taking into consideration:

- An iPod touch is not a proper device to beta test iOS 7 on because it does not have a cellphone radio and none of the actual "phone" functionality can be tested on it.

- If people had the luxury of having 2 phones how would you discover bugs if you're doing most of your usage/calling on your daily device?

If you really want a real beta test the only way to do so is to run it on the phone you use daily.

Or....we can just wait for the masses to "beta test" for us when it goes live.

 

[Kohkane]

This isn't a beta bug, this happens on iOS 6 also. At least it happened to me a few times, but its random, and far apart.


Speaking of which, it happened to me while I was at Walmart for the first time since I've been on iOS 7 and I just did power button+home and it turned back on and I continued shopping. Odd, but doesn't bother me much since I'm used to it happening randomly.

 

[iapplelove]

Ok, we're in a forum discussing a beta software. There is no need to point out to every person discussing a bug that it's beta. The entire point is to discuss and point out the bugs. And for those that are true devs they can report the bugs to Apple.

SO yeah, we get it, it's a beta. Now please stop beating that poor dead horse and let's move on with an adult discussion of our observations since that is why this sub-forum exists prior to the launch iOS 7.

Because it is beta was a perfectly exceptable responce.

 

[nikicampos]

I'm sorry are you under the impression that I'm not on Apple's side? For every beta of iOS 7 released I'm looking for trends. anything that can be reported to Apple will be so that the final release launches well and doesnt give the media a chance to bitch and moan and cry at every little thing Apple does.

Thanks Sherlock, but apple has its own page for bug reports, and the fact that you can't understand this is a beta bug, it's beyond me, trust me, there are thousand developers that don't come to this forum that report this kind of things, and every bug gets reported to Apple directly.

----------

I hate all the blind nerds that would excuse and defend apple for absolutely everything... "omg it's a beta apple is perfect"


sure it's a beta but those bugs shouldn't be there in the first plce, those are the kinds of bugs that are life threatning (emergencies, calls, texts etc) and downright obnoxious.

they can focus on repairing the phone app first then focus and all the bullcrap like stocks or newstand, who the hell is going to test the betas with a malfunctioning phone app anyways? whats the logic apple?

Reading this type of post, really, really makes me sad...

Ooohh please tell Apple what needs to get fixed first, LOL, the fact that a new bug appears in beta 3, it's not a big deal, sometimes to fix something, other things change and have problems and so on and so on, until you get everything right.

 

[Armen]

Thanks Sherlock, but apple has its own page for bug reports, and the fact that you can't understand this is a beta bug, it's beyond me, trust me, there are thousand developers that don't come to this forum that report this kind of things, and every bug gets reported to Apple directly.

You know what's a bug? trying to set a wallpaper and getting dumped to the spring board.

You know what's a critical bug? crippling the entire phone with the user not knowing about it until they try to wake it up.

If this critical bug was appearing in the Alpha phase of development or even in beta 1 I would understand. When it shows up in the middle of the project in a beta 3 it's not just a "bug".

Meanwhile, more and more threads containing "brick" and "screen" are showing up.

 

[TomH TX]

My iphone4 with Beta3 went into "coma" mode for the first time today. Never did it on ios6, or even betas 1 or 2 of ios7. Was able to get out of it doing the "hard reset". Interestingly, for the first time my battery totally cratered, to below 20%. Something was using enormous amounts of resources and/or battery. Have recharged, and turned off several optional features. Will see what it does tonight.

 

[nikicampos]

You know what's a bug? trying to set a wallpaper and getting dumped to the spring board.

You know what's a critical bug? crippling the entire phone with the user not knowing about it until they try to wake it up.

If this critical bug was appearing in the Alpha phase of development or even in beta 1 I would understand. When it shows up in the middle of the project in a beta 3 it's not just a "bug".

Meanwhile, more and more threads containing "brick" and "screen" are showing up.

Still a bug Sherlock.

There's no such a thing as "critical emergency" an emergency is an emergency just like a bug is a bug.

 

[C DM]

Still a bug Sherlock.

There's no such a thing as "critical emergency" an emergency is an emergency just like a bug is a bug.

There are still severity and priority definitions for bugs. So, most certainly there can be critical bugs that are different (and more important) than other types of bugs. Sure, they are still bugs, but not every bug is treated the same way just because it's a bug.

----------

You know what's a bug? trying to set a wallpaper and getting dumped to the spring board.

You know what's a critical bug? crippling the entire phone with the user not knowing about it until they try to wake it up.

If this critical bug was appearing in the Alpha phase of development or even in beta 1 I would understand. When it shows up in the middle of the project in a beta 3 it's not just a "bug".

Meanwhile, more and more threads containing "brick" and "screen" are showing up.

While this can be a major or even a critical bug, or at least more severe/important than some wallpaper bug, something like this is still not completely unusual for a beta (and a developer-only beta at that). Of course it's not as common in a beta, but certainly far from being unprecedented or even all that crazy. It sucks of course, but it can definitely happen (especially when it's more of an isolated thing that doesn't seem to just happen to everyone a lot of the time).

 

[Georgij]

Armen, why are you here? Go sue Apple

 

[andrewsjra]

My phone did this too. My wife tried calling and texting me and I didn't even know until I saw my phone was unresponsive to the home button. The power button did not turn it back on. I was forced to hold the home and power button to get it to reboot. My phone also rebooted itself later last night as I swiped to unlock my phone. Diagnostics say panic plist which usually isn't good but hey this is beta. I agree with others that I never experienced any of this in beta 2. I do think beta 3 feels smoother when it's not crashing or rebooting. Can't wait for the final product

 

[gglittle]

Ok, we're in a forum discussing a beta software. There is no need to point out to every person discussing a bug that it's beta. The entire point is to discuss and point out the bugs. And for those that are true devs they can report the bugs to Apple.

SO yeah, we get it, it's a beta. Now please stop beating that poor dead horse and let's move on with an adult discussion of our observations since that is why this sub-forum exists prior to the launch iOS 7.

As a developer why should I report an "issue" someone else has with a Beta OS? The ONLY issues I will EVER report are those issues that I have had, and that I can duplicate. The largest percentage of "issues" I see DISCUSSED here are scatalogically bovine, issues that I cannot duplicate, and frequently caused by APPLICATIONS that have as yet to be built for iOS 7.The issues that I have reported in Beta 1 have been addressed and now function in Beta 3. Beta 3 tain't perfect, dude and dudettes, but, then, it's really only a BETA, whether or not you want to hear that.

There is no guarantee that ANY beta will display "fixes" in any type of a progressive fashion. Sometimes you regress a Beta to use a branch of the OS that has problems, that need to be addressed, but have not been merged to the tips or head of the tree. The question then becomes do you worry that a bunch of "lookie-loos" might be unhappy with a regressed beta, or do what needs to be done to improve the final release? As a developer, I have no qualms in what I would, and have, done.

 

[henhowc]

yep. this has happened to be 3-4 times over the last 48 hours. always seemed to occur after i had left the phone go idle for awhile and would require a home+power restart. first time running ios 7 beta so I have no experience with beta 1 or 2.

iphone 4 at&T gsm 32 gb, udid is registered with dev

 

[Grahamwho]

Just happened to me too on a 32Gb Att iPhone 4S. Had to hold home and power. Don't remember it ever happening in beta 1 or 2 and definitely not in ios 6.

 

[Armen]

Armen, why are you here? Go sue Apple

Why would I sue Apple? I own Apple products and have lots of respect for the quality of products they put out. I'm just disappointed such a serious issue came up with some users this far in development.

----------

There are still severity and priority definitions for bugs. So, most certainly there can be critical bugs that are different (and more important) than other types of bugs. Sure, they are still bugs, but not every bug is treated the same way just because it's a bug.

----------

While this can be a major or even a critical bug, or at least more severe/important than some wallpaper bug, something like this is still not completely unusual for a beta (and a developer-only beta at that). Of course it's not as common in a beta, but certainly far from being unprecedented or even all that crazy. It sucks of course, but it can definitely happen (especially when it's more of an isolated thing that doesn't seem to just happen to everyone a lot of the time).

I agree with everything you are saying. I'm just disappointed something so severe (although it hasnt spread like a plague) has shown up in a beta 3 (about halfway through development). That's all.

People need to calm the heck down and stop attacking me as if I'm anti-Apple. I'm pro Apple and just surprised QA didn't catch this.

 

[OTACORB]

People need to calm the heck down and stop attacking me as if I'm anti-Apple. I'm pro Apple and just surprised QA didn't catch this.

Its the nature of beta testing, you don't always catch everything in QA. Also sometimes fixing one thing breaks another, so its a process.

I am just amazed that people are complaining about this stuff. It would be different if this was the gold master release and it was happening.

Oh and I have to call BS on these folks that keep saying.. oh you should never use your primary phone with a beta. Really? I wouldn't want these folks being the people reporting bugs then, because the only real way to find issue is by using it like you would normally everyday. So sorry that is just dumb! If you don't want to deal with the issues that come with a beta, you should not install it PERIOD!

 

[Armen]

Still a bug Sherlock.

There's no such a thing as "critical emergency" an emergency is an emergency just like a bug is a bug.

There is such a thing as priority. This behavior would be considered "High" although it hasn't quite affected every one (yet).

----------

Its the nature of beta testing, you don't always catch everything in QA. Also sometimes fixing one thing breaks another, so its a process.

I am just amazed that people are complaining about this stuff. It would be different if this was the gold master release and it was happening.

Oh and I have to call BS on these folks that keep saying.. oh you should never use your primary phone with a beta. Really? I wouldn't want these folks being the people reporting bugs then, because the only real way to find issue is by using it like you would normally everyday. So sorry that is just dumb! If you don't want to deal with the issues that come with a beta, you should not install it PERIOD!

I agree with everything you have stated.

 

[nikicampos]

There are still severity and priority definitions for bugs. So, most certainly there can be critical bugs that are different (and more important) than other types of bugs. Sure, they are still bugs, but not every bug is treated the same way just because it's a bug.

I think I know that, but this Armen guy was saying this is not a bug but a major flaw, well, in betas this are bugs.

Here, I posted this in the morning, relevant.

Another thread like this, betas are not for the average user, stop complaining, yes you say you know it's a beta but I don't think you know that, you say you are going back to beta 2... stop whining.

Beta 3 is not a "step backward" for you may look that way, because you just focus on fonts, wallpapers and how Facebook looks like, this is more stable that beta 1 and 2.

And for the ones complaining about battery life, please stop, not every beta is supposed to better battery life, of all the bugs, Apple has a priority level and what needs to fix and in which order it needs to be fixed for the next beta release, and sometimes fixing one thing means it will create a new bug or new problem.

Think of fixing/building a car, you don't paint it and then do car work, or you don't put the wheels and rim before fixing the brakes, but being software many people just think "why they don't just fix this ASAP" well, you can't fix the brakes without taking the wheels off first.

The part in black is for you Armen, so calm down.

There is such a thing as priority. This behavior would be considered "High" although it hasn't quite affected every one (yet).

 

[Armen]

I think I know that, but this Armen guy was saying this is not a bug but a major flaw, well, in betas this are bugs.

Here, I posted this in the morning, relevant.

Do tell where in my 20+ comments I ever said "its not a bug! its a major flaw!".

It's a critical bug that needs attention. a major flaw would imply it was a bad design or overlooked from the beginning. This issue has started showing up in Beta 3 "Sherlock".

 

[robsalz]

a

 

[Geckotek]

Here are a few things you are not taking into consideration:

- An iPod touch is not a proper device to beta test iOS 7 on because it does not have a cellphone radio and none of the actual "phone" functionality can be tested on it.

- If people had the luxury of having 2 phones how would you discover bugs if you're doing most of your usage/calling on your daily device?

If you really want a real beta test the only way to do so is to run it on the phone you use daily.

Or....we can just wait for the masses to "beta test" for us when it goes live.

If you are a dev, then investing in an extra iPhone for dev purposes is part of doing business.

Whine about it all you like, but Apple doesn't care and the expectation is clear throughout the industry that beta software is not intended to be loaded on a daily use device. The only people arguing otherwise are not devs.

Only non-devs expect the OS to be stable for daily/emergency use.

----------

As a developer why should I report an "issue" someone else has with a Beta OS? The ONLY issues I will EVER report are those issues that I have had, and that I can duplicate. The largest percentage of "issues" I see DISCUSSED here are scatalogically bovine, issues that I cannot duplicate, and frequently caused by APPLICATIONS that have as yet to be built for iOS 7.The issues that I have reported in Beta 1 have been addressed and now function in Beta 3. Beta 3 tain't perfect, dude and dudettes, but, then, it's really only a BETA, whether or not you want to hear that.

There is no guarantee that ANY beta will display "fixes" in any type of a progressive fashion. Sometimes you regress a Beta to use a branch of the OS that has problems, that need to be addressed, but have not been merged to the tips or head of the tree. The question then becomes do you worry that a bunch of "lookie-loos" might be unhappy with a regressed beta, or do what needs to be done to improve the final release? As a developer, I have no qualms in what I would, and have, done.

Uh, I don't get why you replied to me. You've said nothing contrary to my post. I never suggested anybody report a bug they haven't experienced. I only suggested we stop continuously posting the fact that it's a beta over and over. We all know it's a beta. There's no reason we shouldn't discuss the bugs and issues we've experienced.

 

[henhowc]

urrgh just happened to me again. im going to try turning background refresh on again to see if that prevents my phone from shutting down

 

[Geckotek]

Because it is beta was a perfectly exceptable responce.

No, no it's not. Shall I tell you the model of iPhone you have in your hand after every post you make? There is no need to state the obvious and there is no need to berate people that want to discuss bugs or issues they've experienced.

 

[Geckotek]

Oh and I have to call BS on these folks that keep saying.. oh you should never use your primary phone with a beta. Really? I wouldn't want these folks being the people reporting bugs then, because the only real way to find issue is by using it like you would normally everyday. So sorry that is just dumb! If you don't want to deal with the issues that come with a beta, you should not install it PERIOD!

Any serious dev has dedicated equipment for dev purposes. If they are at a point where they are ready for daily testing, and they need a cell for emergency purposes, they carry 2 devices. Perhaps an older iPhone or some dumb phone.

I'd be truly surprised if any of the people complaining about the stability of the phone for daily use are actually devs.

 

[nikicampos]

Do tell where in my 20+ comments I ever said "its not a bug! its a major flaw!".

It's a critical bug that needs attention. a major flaw would imply it was a bad design or overlooked from the beginning. This issue has started showing up in Beta 3 "Sherlock".

I just don't have the time, or the crayons to explain it to you.