Q: Mysterious random total shut downs following 3.1 update

Ive missed calls, nothing that has caused me to lose business at least that i know of. Have you gone into apple after talking to tech on the phone and made a case to them as to why they should replace your phone? I would try that. I understand upset. Im not exactly thrilled with it myself.

I would have thought twice about restoring from that backup. Although the new os is apparantly buggy, restoring from backup just put the same buggy os you had before, most likely accelerating the issue. Try a restore, setup as new phone, download carrier update, disable fraud warning in safari and reset network settings. You might have more luck that way.

Add me to the list too. Same problems - random coma mode for no reason.

Mon Oct 5 23:05:23 unknown SpringBoard[25] <Notice>: MultitouchHID(208ae0) uilock state: 1 -> 0
Mon Oct 5 23:05:24 unknown SpringBoard[25] <Notice>: MultitouchHID(2afb50) device bootloaded
Mon Oct 5 23:05:49 unknown com.apple.launchd[1] <Warning>: (com.apple.UIKit.pasteboardd) Check-in of Mach service failed. Already active: com.apple.UIKit.pasteboardd
Mon Oct 5 23:05:54 unknown searchd[488] <Warning>: EAS|EAS Protocol Manager set to ASProtocolUnknown
Mon Oct 5 23:06:01 unknown com.apple.searchd[488] <Notice>: CPSqliteStatementSendResults: interrupted
Mon Oct 5 23:06:12 unknown com.apple.searchd[488] <Notice>: CPSqliteStatementSendResults: interrupted
Mon Oct 5 23:06:35 unknown configd[23] <Notice>: jetsam: kernel memory event (91), free: 372, active: 1633, inactive: 901, purgeable: 0, wired: 6692
Mon Oct 5 23:06:36 unknown com.apple.launchd[1] <Notice>: (com.apple.mediaserverd) Exited: Killed
Mon Oct 5 23:06:36 unknown SpringBoard[25] <Warning>: Memory level is urgent (9%). Asking 'Safari' to exit.
Mon Oct 5 23:06:36 unknown MobileSafari[444] <Warning>: Safari got memory level warning, killing all documents except active.
Mon Oct 5 23:06:44 unknown MobileSafari[444] <Warning>: Safari got memory level warning, killing all documents except active.
Mon Oct 5 23:06:44 unknown MobileSafari[444] <Warning>: Safari got memory level urgent while suspended, self-terminating
Mon Oct 5 23:06:46 unknown com.apple.launchd[1] <Warning>: (UIKitApplication:com.apple.mobilesafari[0x28f3]) Exited with exit code: 101
Mon Oct 5 23:06:46 unknown SpringBoard[25] <Warning>: Application 'Safari' exited abnormally with exit status 101
Mon Oct 5 23:10:30 unknown SpringBoard[25] <Notice>: MultitouchHID(208ae0) uilock state: 0 -> 1
Mon Oct 5 23:12:17 unknown SpringBoard[25] <Notice>: MultitouchHID(208ae0) uilock state: 1 -> 0
Mon Oct 5 23:12:17 unknown SpringBoard[25] <Notice>: MultitouchHID(2afb50) device bootloaded
Mon Oct 5 23:12:27 unknown kernel[0] <Debug>: launchd[498] Builtin profile: MobileSafari (seatbelt)
Mon Oct 5 23:13:50 unknown kernel[0] <Debug>: AppleMRVL868x::setCIPHER_KEY() [kernel_task]: type = CIPHER_TKIP, index = 1, flags = 0x0


ok, so this is interesting: i didn't even have SAFARI running but it's 'low memory' and force-quit by the system.

I'm going to keep my console log running any time i'm by the computer and send the logs in; i have no idea what it means, hopefully something helpful can be parsed from it.

right now my buggy 3.1 is more joyful to operate than the 3.01 that was more stable, but that could be because i dont' have a SINGLE non-apple app. I had one (coincidentally that uses push).. for those who mentioned the 'notifications' pane gone from prefs... it comes back when you install something that needs it! anyhow.. i did install that shortly before the ONE crash i had.. so maybe i'l put it back in and the log can show something useful.

I was concerned that apple had partitioned the working memory too small (they have a habit forever of not giving enough RAM breathing room)... but when i did the 'hacked' installs i bumped up the system partition 200MB and it didn't make it less flaky.

my sms (incl. MMS) and my voicemail are working and calls are going and coming with regularity so i'm going to stick with 3.1 for a bit, hopefully find out some helpful things.

-awr

When this happened to me I held the top button for a while and then pressed the the menu button for a while, like you would do to close an unresponsive app. My screen came back on but when ever I pressed the top or menu button(one at a time) it would take a screen shot. Everything went back o normal after 30 sec.

Add me to the list of disgruntled users after the update. Battery Life BAD, Coma everyday BAD, Can't always answer calls BAD. Looking forward to another update to fix or a new phone that works.

I had been having the same coma issues (six times or more daily) since upgrading my phone to 3.1.

After my first Genius appointment, I was told to go home and restore to factory settings, which I did. It didn't solve a darned thing. I was going to try some of the "fixes" described in this thread, but since it is still under its factory warranty and I purchased Apple Care to boot, I decided they need to deal with this, not me. I made another Genius appointment for today and was given a new phone. Luckily, this one still had 3.0.1 and I have not had a single coma all day.

I will NOT be upgrading again until they get this figured out. I can live without the features that were in 3.1 as long as I have a working phone.

ETA: There were at least 3 other people in the store at the same time as I having the exact same issue. You can't tell me that Apple isn't starting to realize this is an issue. A little acknowledgment that, "Yes, we know there is a problem, we're working on it" would go a long way to smooth some ruffled feathers at the moment.

Message was edited by: DomesticGeek

Andrewwynn,
I have a 'memory' app that I can run. it shows all currently running processes. I think why Safari is shown running is that after the last time you ran safari, when you exited, it left safari in memory for quicker starting the next time.

Roger@pcfubar wrote:
Andrewwynn,
I have a 'memory' app that I can run. it shows all currently running processes. I think why Safari is shown running is that after the last time you ran safari, when you exited, it left safari in memory for quicker starting the next time.

i think you are correct. I do have a pretty big mail demand (active sync with 20 folders or so; 6 being pushed).. but i had the bug back when i was using IMAP as well.

i re-installed the 'trapper' app that i put in just before crashing before, i'm going to log for 24 hrs maybe before putting in the bazillion apps i used to have and then AFTER i'll do it again and send the two 24-hr logs to apple for the s/w/ engineers to try to decipher.

the problem with 'intermittent' bugs that affect a small percentage is they are darn near impossible to squash! hopefully i can help shed some light and they can get 3..2 made and everybody can be happy.

the big problem is.. who's going to have the balls to install 4.0? only if i get a signed contract saying i can downgrade to 3.5 (or whichever) or at the very least: that i can revert to what i had JUST BEFORE the upgrade! comon man, just make a .dmg of the entire iPhone and replace it 'as is' if it just didn't work out!

-awr

Yep, same here as well. Sometimes seems to be triggered by an incoming mail. You hear the mail alert sound and then bingo, phone has shut itself down. Hard reboot forces it to come back but every once in a while it will come back to life itself with an odd play button hovering over the normal wallpaper.

What is supremely annoying is that any calls received during the "outage" of the phone go straight to voicemail. So if you're expecting a call and this happens you are screwed.

Apple please fix this as soon as possible. It is frustrating to have my phone be so randomly unreliable.

geez, just keep your favorite iphone/ipod playlist running on no volume, it does the trick until the goobs figure it out.

Despite having desactivated Push and Notifications, for the fist time for one week, again I had a new sleeping crash this weekend while consulting the agenda and going into a building, I stepped inside a lift and the time I used to do all this (maybe 1 min), it had crashed. I'm fed up with this problem. I bought an iPhone because I trusted Apple for being able to make good material+software. I'm an Apple user for 15 years and never I had to face such annoying bug and such silence from Apple. My warranty will end next week and I'm afraid to get stuck with a buggy iPhone if Apple doesn't take this problem seriously. So finally I will have to return it for a repair.

Having the same issue. Phone shuts down often and only hard reboot helps. Hope Apple will fix this issue ASAP!!!

Will this coma mode render the Find my iphone service pointless? Might give this a go next time I phone goes into its regular coma and see what happens, might not be a good time to lose or get your phone stolen until 3.2 appears.

I can see the conversation now, "sorry but could you wait until 3.2 is released before you steal my iphone..."

NeoSe7en wrote:
People aren't so much angry that there is still in issue. They're angry because Apple hasn't done so much as even make any acknowledgment of the issue's very existence.

It is, and has been for a long time, Apple's policy to not acknowledge these types of issues until they are fixed (when the acknowledgement is implicit in the fact that they are fixed). That's just the way Apple operates. They have their reasons.

What you can be sure of (despite what many people on these forums say) is that Apple DO take notice of what is said on these forums, especially a thread like this one with hundreds of people reporting the same issue. The other thing you can be sure of is that Apple ARE aware of this issue and are working on a fix. Even if they won't acknowledge it.

I reported it as a bug to Apple and I wasn't the first. I know the original Apple bug report number assigned to this issue (but NDA prevents me from telling you what it is). They are DEFINITELY working to resolve this problem, just need to be patient.

Whenever a similar type of issue surfaces, you can be sure that someone will have reported it to Apple and that they are working on a resolution. You just have to take it on faith and wait for the fix in the next software release. That's just the way that Apple works. Once you know that this is how it works there's no reason to get angry.