Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What is up with Beta 3 and Phones becoming unresponsive?
- Thread starter Armen
- Start date
- Sort by reaction score
Happened to me today (while waiting for a text message). Very annoying, as it never happened once over the past month of using beta 1 & 2.
Then today I got a voicemail (no call) and that was the last straw. I switched back to beta 2 and have no more problems like those at all.
Then today I got a voicemail (no call) and that was the last straw. I switched back to beta 2 and have no more problems like those at all.
It wasn't though, was it? The way you wrote not only your opening post but subsequent replies all sounded far too much like you're a member of the YouTube tin foil hat brigade; looking for a conspiracy when there isn't one. When someone pointed out that it's beta software and stuff like this happens with beta software, you came back with:
"Something in Beta 3 has had at least..."
"Something". Makes you sound like you're looking for an explanation.
Let's put this into perspective a little bit here. iOS7 is a major reworking of the iOS platform, therefore bugs will be more random and possibly more serious than in betas of incremental upgrades such as iOS 4 to 5, or 5 to 6.
OS X Mavericks is getting some extremely clever CPU and memory optimisations and it is entirely possible that these technologies are making their way over to iOS. If that is the case and this is the first beta where the technologies are implemented then yes, you are going to get more faults deep down in the OS.
I never said nor hinted that "It's a beta" wasn't rude and flippant, however, it is an acceptable answer to the query. It's not a useless statement either. Some people on this forum in particular seem to be completely oblivious to the fact that iOS7 isn't finished yet and seem to either not know or not care that the software is beta.
If we're going fully by the book, discussion around these bugs is not valid discussion anywhere outside the Apple Developer forums. When developers downloaded the IPSW's, they digitally signed a Non Disclosure Agreement. Following the rules, this means that the software shouldn't be discussed outside the Apple dev forums at all. Sure, we all know that people have been pirating the betas, and that cannot be stopped, so what is the point of discussing any bugs found on this forum, when nobody is going to actually report it to either the Apple developer forums, or the Apple bug reporter?
Exactly. And complaining that as a result of these bugs people are "missing important calls and texts" isn't an acceptable reason to research the bug. They shouldn't be using the software on production devices, ESPECIALLY ones that are relied on for day to day activities.
I'm just going to say again in this thread also, this has been present since iOS 6.
I've said this before also, people just don't listen.
This is not an iOS 7 beta issue, this has happened on iOS 6 as well (both iPad and iPhone), its just that lately its become more known.
https://discussions.apple.com/thread/3404650?start=0&tstart=0
Couldn't this have been added to your last conspiracy theory thread? Report it to Apple, then it'll get fixed. Simple as that.
Aye, just reached for my phone to find it non responsive. I thrown it in to DFU mode and iTunes installed iOS 6 on it once again.
The most annoying bit is that the logs are of course erased, so I can't pass them on to Apple. Oh well, chances are that it it's happening to this many people Apple will no doubt have seen this issue on one of their phones.
For the record, I use an iPhone 4S.
The most annoying bit is that the logs are of course erased, so I can't pass them on to Apple. Oh well, chances are that it it's happening to this many people Apple will no doubt have seen this issue on one of their phones.
For the record, I use an iPhone 4S.
I have an extremely hard time believing that people have no clue it's a beta when the OS even say's Beta when you try to install it. So, sorry, "I'm not buying it" (LOL). The reply "It's a beta" is useless and should be deleted by the Mods any time it's posted and repeated offenses should result in a warning. It should be treated just like any other off topic or "one word" reply as listed in the forum rules.
By the book???? By who's book? Apple's? Since when has MR EVER followed Apple's rule book? You do realize the website you're on and the legacy it has...correct?
If MR had intentions of going "by the book", this subforum wouldn't exist until iOS 7 officially launched.
This I can agree with. And if they chose to do so, they must accept the consequences and not complain.
Last edited:
My phone does this multiple times a day. It happened once in B2 but since B3 it's been a nightmare. Had to go buy myself a real alarm clock since my phone shut off in the middle of the night and failed to wake me up :/
Saw lots of users reporting that it happens when their phone is locked for a period of time. However, I can lock my phone and literally 30 seconds later it will be shut down on me.
Edit: Added photo of crash log.
Saw lots of users reporting that it happens when their phone is locked for a period of time. However, I can lock my phone and literally 30 seconds later it will be shut down on me.
Edit: Added photo of crash log.
Attachments
Last edited:
Hey RyanGJ, any panic.plists on your diagnostic log? The issue everyone appears to have is when the phone is idling and just goes black and unresponsive. That has happened once, but the other time was simply deleting a song off my phone and I saw it crash and eventually go blank on my screen. Had to do the same thing and do a home button power button reset to get it back. The result is 2 panic.plists.
I have 3 panic.plist and they are around 3-10 seconds before a ResetCounter is created. I have had about 3-5 crashes a day but only 3 panic.plist files are in the log from the last week.
Edit: resetcounters are created as the device is booting up from a hard reset. Panic.plist appear to have been made during the boot sequence.
my theory is that the "DFU mode" that all of you are experiencing is not DFU mode at all, in fact, I think it's a kernel panic. when the OS panics, it will just lock up and not respond. if you've gotten any *.panic.plist in your diagnostics + usage section, that is probably the crash report that the kernel generates.
if you've got a panic.plist, i'd like to see a certain part of it (see attachment, original image taken by andrewsjra). this will tell me the name of the process that is causing the panic.
if you've got a panic.plist, i'd like to see a certain part of it (see attachment, original image taken by andrewsjra). this will tell me the name of the process that is causing the panic.
Attachments
Last edited:
Well, a cheaper solution would be to downgrade to an actually usable OS (6.1.4.). It did that to me last night and if it happens again I'm going straight back to iOS 6. I can deal with the minor bugs, but kernel panics are too much.
Downgrading my phone doesn't do me any good when developing/testing an app.
I dont think its a kernel panic. I only have 3 panic.plist files created. And my phone has shut down at least 10 times since the files were created.
I have managed to figure out what is happening. Its not DFU. And its not a real kernel panic. Its more of a system halt.
I need another member to help me with testing some stuff. Its to much work for just me.
I need another member to help me with testing some stuff. Its to much work for just me.
So twice my phone did a random reboot and acted as though the phone was turned on. The other 2 times it went completely dead where I had to hold the home and power button. One of those times it was idling and did it when I wasn't aware. The other time it happened when I was deleting a song from my phone. It crashed in front of me. After this I checked my diagnostics and verified that it was the last panic.plist message I posted. So these crashes that people are referring to as in dfu mode most likely are a result of a kernel panic. At least mine are so far
My phone just entered "coma" mode for a 2nd time tonight. It had done it last Tuesday, when it would not wake up from sleep. I did the force reset, and had not had any further problems until tonight, when again with no indication of problem it would not wake up. When I did force reset it, battery had dropped from in the 90+ % to 56%. Some kind of process is hanging, and killing the battery while it is inaccessible to us. I will report this again over on the developer board.