Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Phone wont turn on when left idle since updating to Beta 3

  • Hasn't happened to me yet

    Votes: 83 42.6%
  • Yes, it's happen to me at least once.

    Votes: 33 16.9%
  • Yes, it's happened to me several times

    Votes: 79 40.5%

  • Total voters
    195
I've seen at least 4 users today post saying they would just set their phones down to idle and they'd come back to it and the screen wouldn't turn on.

Zmagik chime in I know you've been following along with me all day.

I have the same issue!

My "lock" button has been dead for 6 months... does anyone have any tips of how i can restart my phone? ?
 
could be just a coincidence but i havent had this happen anymore after i turned background app refresh back on. maybe some bug related to idling? just throwing out some ideas.

i guess i'll find out when i go to bed. if my alarm doesnt go off i'll know my iphone died again lol
 
The answer to every unexpected behavior cannot be "its a beta".

It most certainly can, when its beta.

Pray tell, what do you think is going on? Is there a bug that's causing it? Yes? Who'd have thought it, a bug with beta software! What's the world coming to?

I think it's a fair point to make, (the OP) This is precisely what a forum is all about. Yes, we know "it's a beta", but some of us actually like to discuss hiccups that occur from beta to beta. "It's a forum."

But he doesn't believe it's a beta problem...! "Sorry not buying that" is a stupid and arrogant response to a correct answer.

It may not be what he wanted to hear but at the end of the day it's beta software. There WILL BE bugs, bugs that were in one beta may not be in another beta and bugs that weren't in one beta may be in subsequent betas. This is how betas work. You are using the beta operating system to test for and report bugs, therefore, stop with the conspiracy theory crap and report the bugs to Apple.
 
It most certainly can, when its beta.

Pray tell, what do you think is going on? Is there a bug that's causing it? Yes? Who'd have thought it, a bug with beta software! What's the world coming to?



But he doesn't believe it's a beta problem...! "Sorry not buying that" is a stupid and arrogant response to a correct answer.

It may not be what he wanted to hear but at the end of the day it's beta software. There WILL BE bugs, bugs that were in one beta may not be in another beta and bugs that weren't in one beta may be in subsequent betas. This is how betas work. You are using the beta operating system to test for and report bugs, therefore, stop with the conspiracy theory crap and report the bugs to Apple.

Arrant nonsense. This is a forum and we may discuss what we like. Of course we know there'll be bugs, but we choose to discuss that glaringly obvious fact. You don't like it, tough, build a bridge and get over it. Next!
 
Sure it's not just the weather overheating phones? Could there be a particular app running on these devices?
 
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.

Serious bugs can and do show up even late in the process. I am not one who has a problem with discussion bugs, but the attitude that it is unacceptable a serious bug shows up this late is a bit unreasonable.

Here is why - often betas are on scheduled where on this date or that date is when the next beta is coming out and devs code toward that date. it is possible that in fixing one bug they realized they would have to rewrite a large chunk of code that might break other things. Often in those cases, you go on and do the rewrite in time for the next beta and deal with any new bugs that generate as a result in the next one. They may have already known before the beta went out about this bug but it was scheduled for the next beta to be fixed.

Something like this would be a serious bug and most likely one near the top of the list to work on next, but if introduced while fixing something else they wanted done in beta 3, there just may have not been the time to address this one in time to make it into beta 3 (or they didn't know they introcued it until beta 3 went out but I'm sure they know now).

Serious, even critical bugs can show up at any stage of the beta process. This is a serious one definitely but it showing up in beta 3 when it wasn't in beta 1 or 2 is the way things can do in the development process and shouldn't be unacceptable or disappointing... it is the way the process works.
 
Serious bugs can and do show up even late in the process. I am not one who has a problem with discussion bugs, but the attitude that it is unacceptable [for] a serious bug shows up this late is a bit unreasonable.

Here is why - often betas are on scheduled where on this date or that date is when the next beta is coming out and devs code toward that date. it is possible that in fixing one bug they realized they would have to rewrite a large chunk of code that might break other things. Often in those cases, you go on and do the rewrite in time for the next beta and deal with any new bugs that generate as a result in the next one. They may have already known before the beta went out about this bug but it was scheduled for the next beta to be fixed.

Something like this would be a serious bug and most likely one near the top of the list to work on next, but if introduced while fixing something else they wanted done in beta 3, there just may have not been the time to address this one in time to make it into beta 3 (or they didn't know they introcued it until beta 3 went out but I'm sure they know now).

Serious, even critical bugs can show up at any stage of the beta process. This is a serious one definitely but it showing up in beta 3 when it wasn't in beta 1 or 2 is the way things can do in the development process and shouldn't be unacceptable or disappointing... it is the way the process works.

This is exactly right.
People also need to remember that it is not really the OS that Apple is wanting tested. It is the new APIs for developers to use in their apps.
Even an iPhone beta that was completely unable to make or receive calls would not be unreasonable. It would be extreme and unlikely but not unreasonable.
Those are the kind of things people need to understand up front and that is why there is a warning at the beginning of the whole process that says the software is to be installed on development devices only.
 
Serious bugs can and do show up even late in the process. I am not one who has a problem with discussion bugs, but the attitude that it is unacceptable a serious bug shows up this late is a bit unreasonable.

Here is why - often betas are on scheduled where on this date or that date is when the next beta is coming out and devs code toward that date. it is possible that in fixing one bug they realized they would have to rewrite a large chunk of code that might break other things. Often in those cases, you go on and do the rewrite in time for the next beta and deal with any new bugs that generate as a result in the next one. They may have already known before the beta went out about this bug but it was scheduled for the next beta to be fixed.

Something like this would be a serious bug and most likely one near the top of the list to work on next, but if introduced while fixing something else they wanted done in beta 3, there just may have not been the time to address this one in time to make it into beta 3 (or they didn't know they introcued it until beta 3 went out but I'm sure they know now).

Serious, even critical bugs can show up at any stage of the beta process. This is a serious one definitely but it showing up in beta 3 when it wasn't in beta 1 or 2 is the way things can do in the development process and shouldn't be unacceptable or disappointing... it is the way the process works.

Fair enough

----------

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

Judging from the attitude you're giving me I figured you'd have plenty of Crayons laying around.
 
Last edited:
No, because it's a rude and flippant response that doesn't add any value to the conversation.

And someone giving a response gets

"Sorry I'm not buying that" as a response isn't rude and flippant?

At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.
 
And someone giving a response gets

"Sorry I'm not buying that" as a response isn't rude and flippant?

At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.

The entire thread was just an observation I made about a new issue that has sprung up and my disappointment with how that got passed QA. As I'm typing this more and more people are experiencing the issue. I was being "laughed" at when I mentioned 3-4 people already have the issue and now that number has grown.

Also somewhere in the middle of this apparently Niki and I got into a e-sword fight.
 
Last edited:
Fair enough

----------



Judging from the attitude you're giving me I figured you'd have plenty of Crayons laying around.

Too many edits kid, couldn't you make mind for a comeback that you had to edit it, hahahaha, plus your comeback is pathetic, I just told you I don't have any crayons to explain it to you, but I have some time now.

When someone tells you it's a beta problem, and you say, "I'm not buying that" then you my friend have no place in your own thread.

So quoting your previous childish comeback, "you should leave your own thread" hahaha
 
Too many edits kid, couldn't you make mind for a comeback that you had to edit it, hahahaha, plus your comeback is pathetic, I just told you I don't have any crayons to explain it to you, but I have some time now.

When someone tells you it's a beta problem, and you say, "I'm not buying that" then you my friend have no place in your own thread.

So quoting your previous childish comeback, "you should leave your own thread" hahaha

Are you done?
 
And someone giving a response gets

"Sorry I'm not buying that" as a response isn't rude and flippant?

At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.

Exactly, this Armen aka Sherlock Holmes, is trying to go deep down into a conspiracy that the masterminds at Apple are working on.

I just don't see how hard is it to accept that is a beta problem, when you fix something other things may become unstable and there's no time to fix them so they release beta X and work on it for the next beta release.
 
The entire thread was just an observation I made about a new issue that has sprung up and my disappointment with how that got passed QA. As I'm typing this more and more people are experiencing the issue. I was being "laughed" at when I mentioned 3-4 people already have the issue and now that number has grown.

Also somewhere in the middle of this apparently Niki and I got into a e-sword fight.

It's not an issue as you're making it out to be at this point. It only becomes an issue, when iOS 7 is finally released to the public. If phones are still randomly going into DFU mode still, then you can complain.

As of right now, it's a Beta. Weird **** is going to happen. Each new Beta release things will be fixed, others broken. It's how it works. I have been a developer since iOS 5. I have never had my phone go into DFU mode randomly. Rebooting, crashing, acting wonky - yes.

As for the user that has an entire family with phones on iOS 6 going into DFU mode, go to Apple. There is obviously an isolated issue with your phones/software/update. It's not normal and random DFU mode is not something that has been "happening" since any iOS version.

Please stop acting like this is a final product. Asking why a beta is doing something is irrelevant. If you really want to know - become a developer (if you're not already) and look at the code to see what is going on. Also use the bug reporting feature. If you're not a developer and can't use any of those features, please stop bitching.
 
It's not an issue as you're making it out to be at this point. It only becomes an issue, when iOS 7 is finally released to the public. If phones are still randomly going into DFU mode still, then you can complain.

As of right now, it's a Beta. Weird **** is going to happen. Each new Beta release things will be fixed, others broken. It's how it works. I have been a developer since iOS 5. I have never had my phone go into DFU mode randomly. Rebooting, crashing, acting wonky - yes.

As for the user that has an entire family with phones on iOS 6 going into DFU mode, go to Apple. There is obviously an isolated issue with your phones/software/update. It's not normal and random DFU mode is not something that has been "happening" since any iOS version.

Please stop acting like this is a final product. Asking why a beta is doing something is irrelevant. If you really want to know - become a developer (if you're not already) and look at the code to see what is going on. Also use the bug reporting feature. If you're not a developer and can't use any of those features, please stop bitching.

So am I wrong to assume every beta should be more stable than the previous? If so, then Ok. I guess things could get worse before they get better. :)
 
So am I wrong to assume every beta should be more stable than the previous? If so, then Ok. I guess things could get worse before they get better. :)

Overall, stability should go up as we get further into the beta process. If a major stability issue cropped up in a beta two weeks before the product is supposed to go to final release, you'd be right in having the reaction you did. But we are still at beta 3, so setbacks at this stage are common and to be expected.
 
And someone giving a response gets

"Sorry I'm not buying that" as a response isn't rude and flippant?

At the end of the day, what is there to discuss? Sure, add to the discussion if you've found what the issue is, or are contributing to the reports of the issue, but at the end of the day these issues are caused by beta software. There's nothing more than that to discuss.

How does the reply make the "It's a beta" response any less rude and flippant? I don't like the guys reply either, he's obviously wrong in thinking a beta software should provide some level of stability. However, that doesn't change the fact that saying "It's a beta" is a useless statement and I think posts of that nature should be deleted as off-topic.

Issues are not caused by beta software. "Beta" causes nothing. Issues are caused by BUGS in beta software. Discussion around these bugs trying to determine the different ways to replicate the issue is a valid discussion and saying "It's a beta" does nothing to add to this discussion. It's that simple.

Edit: English
 
Last edited:
This happened to me today, for the first time ever. Just went to check my phone for a text message after not using it for 5-10 mins, and it wouldn't turn on at all. I had to hold home+power for 10 secs to turn it on. Luckily I still received the texts I missed while it was off (was waiting for a friend to go to lunch).

No idea what the culprit is though. This did not happen to me in beta 1 or beta 2. So far, beta 3 has been nothing but problems, so I think I'm gonna go back to beta 2 tonight.

Note: Yes, I said beta. Yes, we all know it's a beta. And yes, I report these bugs I find in the beta to Apple.

This whole "it's a beta, get over it!" attitude is worthless and annoying. Everyone knows it's a beta. If you don't care to read about current issues, why are you even here in the first place??
 
Beta 3: My phone won't turn on poll

Can we get a realistic count? How many of you have come back to your phone when it's been sitting idle and have not been able to turn it back on since you went to Beta 3?

If your screen has turned off while using it and you couldn't get it to come back on with a reboot you should also answer yes. I don't want to call it DFU mode because from discussing with others I don't think this is the correct description of the state the phone is in.
 
I just hold the power button and home button to force restart and it has worked every time. Good to know it's not some weird glitch exclusive to my phone or something. Only started happening in Beta 3. Shame because the rest of it is quite stable. Oh yeah and the battery life.
 
I too had this happen to me. I hadn't checked my phone for a while and when I did it didn't light up when I pressed the home button. I thought my phone died but I had enough battery it shouldn't had. I plugged it to the wall outlet and nothing. I ended up holding the power and home button and it rebooted and was fine. It's only happened once but it's gone through a restart cycle twice where it goes black and the Apple logo pops up. Not to be confused with the quick crash to the home screen. That happened to me in beta 2. Other than that, everything else seems smoother. Did you check your diagnostics? Any panic plists? I think that is what happened to your phone as its only listed once on my list.
 
This seems to have turned into a heated debate with people attacking each other. For those arguing about it showing up in Beta 3, I'm sorry to disappoint you but it started in beta 2 (at least for me). Beta 1 was fine, but beta 2 was too buggy that i went back to 6.1.3. From all the issues people are having with beta 3 i think i'll wait for beta 4..... or maybe 5.

Beta 1 had the occasion apps crash but never completely locked up my Iphone 4. IOS 6 never gave my any issues and since I went back to IOS 6 there has not been on lock up.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.