Q: Mysterious random total shut downs following 3.1 update

I have been having the same problems. A hard reset works. Does anybody have a solution yet?

Dont know if this helps, but I turned off the eBay push notification and my shutdowns have gone from one per day to one every four days.

Note, I am still using 3.0.1, so it may not be relevant for 3.1.

Good luck !

Message was edited by: Paul Brennan

Urgh. I should have waited.

On September 9th after the "It's Only Rock And Roll" Apple Media Event, I updated my MBP to iTunes 9 and shortly thereafter updated my iPhone 3G to the 3.1 OS. I've had this iPhone 3G since Launch Day back in July 2008, and have luckily had great experiences in the past with my firmware updates from 2.0 onward. Not this time. Daily I experience at least 2-3 "comas", with today's culmination of 5 and a weird glitch where the phone rebooted straight to the Camera app, and each the Home button and the Sleep button only acted, when pressed, to take a screenshot of the display! Needless to say, another hard-reboot.

I've been following this thread for a while now, and I've tried the Apple Genius Bar. The Genius who helped me had heard of the issue, but said all he could offer me was a firmware restore, and even then he couldn't get my iPhone to accept anything BELOW 3.1. I walked out with 3.1 hopeful that it would work this time, but before I had even parked the car in my parking garage upon returning home I'd already coma'd out. I've tried restoring on my own, with and without backups. Deleted network settings, tried turning Safari-Anti-Fraud on and off, turning Notifications on and off, turning WiFi on and off - ****, I even tried the bogus method of leaving the phone charging with wifi on and Safari open to properly download the anti-fraud information - all to no avail. This update has made this device near worthless.

By no means will I write off Apple products here, but c'mon Apple. QA: Quality Assurance. It's coding for 3 different hardware configurations - not 10, not 100, not 1000 - just THREE.

I'm left deciding whether or not I want to go argue with the Genius Bar again tomorrow, demanding some kind of replacement. My 1-year warranty is obviously out of effect here, but if anyone dare suggest I should have bought AppleCare for this device, I want to ask you one thing: +Why should I have to purchase AppleCare to protect myself from APPLE THEMSELVES?+ My iPhone has no physical deformities, and I take pristine care of the device. All I've done to this device is upgrade it at Apple's OWN recommendation. If that doesn't warrant a fix of some kind from Apple, I don't know what does.

I usually get my iPhone in a coma when taking pictures, and using other apps (mainly mail) my phone goes into normal sleep, but then never wakes back. I tried with a third-party photo application, same problem. Might the bug be related to large memory read-writes?

toanavinai wrote:
Urgh. I should have waited.

On September 9th after the "It's Only Rock And Roll" Apple Media Event, I updated my MBP to iTunes 9 and shortly thereafter updated my iPhone 3G to the 3.1 OS. I've had this iPhone 3G since Launch Day back in July 2008, and have luckily had great experiences in the past with my firmware updates from 2.0 onward. Not this time.

Maybe this is just a coincidence, maybe not, but to me there seems to be some commonality with people that updated to iTunes 9 first, then did the iPhone 3.1 update. I've read several other threads of people performing updates in this order and running into problems afterwords. Can anyone confirm if they updated their phone first, before updating iTunes, and are still having problems? Both iPhones in my household were updated to 3.1 before iTunes was updated and neither are having any issues whatsoever.

thaw3 wrote:
This just in --Here's some troubleshooting fixes on CNet and info about what Apple is doing to fix 3.1
http://reviews.cnet.com/8301-19512_7-10357176-233.html?tag=mncol;title

Nothing new here, same advice people are giving out in this and other online iphone forums. As far as I can see doing this or doing nothing will give the same result (phone in coma mode on a random basis). I do not wish to start ripping my data apart to try and resolve a major defect that was shipped with the 3.1 release, I await apples response and hopefully some firmware that was correctly tested and not rushed out to meet some marketing date.

toanavinai wrote:
By no means will I write off Apple products here, but c'mon Apple. QA: Quality Assurance. It's coding for 3 different hardware configurations - not 10, not 100, not 1000 - just THREE.

Hardware isn't the only thing that can play a role in creating problems. There are now over 75,000 different apps available for the iPhone, any one of which could potentially create a problem. Does anyone remember the chaos Unsanity's APE preference pane created when Leopard was first released? Thousands, if not tens of thousands, of Leopard installations failed, leaving users with unusable computers, because of one little piece of software. It's entirely possible that a similar circumstance is occurring here. Has anyone tried doing a erase/restore/set up as new procedure WITHOUT reinstalling 3rd party apps?

UPDATE: Thought we had it solved so I didn't go in on Sunday (my phone was scheduled to be replaced) ... but IT'S BACK!
Set up an appointment for Wednesday evening. I'll let you know how it pans out.
My honest suspicion is that this issue is known to Apple and they already have a team of people who have worked it out (or are working it out). It'll likely roll out w/ the AT&T MMS capability (Wow AT&T really knows how to drag out "late summer" don't they?) due any time now (I hope).

Just as with those of us who were lucky enough to experience baseband lockups when we went through a tunnel or stepped into an elevator while on a call (requiring a full power cycle of the phone to get service again) with the original iPhone, Apple is mum on the problem. It's likely they're hoping those not affected won't notice. --As many iPhone users have. Lots of people don't notice it at all or think their battery died. Then magically an update that will come out labeled "MMS + Bug Fixes" (so as not to alarm those who never noticed their phones were silently recovering from fatal crashes) and all will be well.

Really, the options are 1: wait.
2: be useful and provide information to Apple who is trying to get the issue resolved. (To be honest, they haven't been in phones very long and the iPhone OS is far more capable than anything else out there except maybe WinMo... but that has it's own issues!
3: complain... (I'm sure someone's listening somewhere.)

So in the interest of being useful, I have a hang recorded on the console while plugged into iPhone setup utility:
Mon Sep 21 23:36:44 unknown kernel[0] <Debug>: System Sleep
Mon Sep 21 23:36:47 unknown SpringBoard[24] <Notice>: MultitouchHID(208ae0) uilock state: 1 -> 0
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: pmu wake events: exton1(buttons)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::sleepWakeNotification: System Powering on
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: System Wake
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: + AppleMPVDDriver[0xc0b5c800]::setPowerStateGated()
Mon Sep 21 23:40:39 unknown SpringBoard[24] <Notice>: MultitouchHID(2c8780) device bootloaded
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::setPowerState(1)
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: There are 2 assertions for PDP context 0:
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::changePowerStateGated(1)
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: PersConn-apsd-com.apple.apsd-push.apple.com
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMRVL868x::setPowerStateGated(): 0 -> 1, 0xc0c66800
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: PersConn-aosnotifyd-com.apple.AOSNotification
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMRVL868x::wakeupSequence()
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: There are no assertions for PDP context 1:
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AirPort: Enabled AppleMRVL868x (link 1, sys 0, user 1)
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: Telling PDP context 1 to go inactive.
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMRVL868x::setPOWER() [kernel_task]: 1
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: There are no assertions for PDP context 2:
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMultitouchSPIUserClient: Inhibited externally initiated reset
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: Telling PDP context 2 to go inactive.
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMultitouchZ2SPI: enabled power, scheduled bootloading
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: There are no assertions for PDP context 3:
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 29, BTServer)
Mon Sep 21 23:40:39 unknown CommCenter[28] <Notice>: Telling PDP context 3 to go inactive.
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 22, configd)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 28, CommCenter)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 34, iapd)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 24, SpringBoard)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 871, mediaserverd)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 880, MobileMail)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 52, apsd)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: PM notification timeout (pid 30, aosnotifyd)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::sleepWakeNotification: Sysmtem Going to sleep
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::setPowerState(0)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMultitouchZ2SPI: disabled power
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AirPort: Disabled AppleMRVL868x (link 1, sys 1, user 1)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMRVL868x::setPOWER() [kernel_task]: 0
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMRVL868x::setPOWER(): Flushing beacons!!
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::changePowerStateGated(0)
Mon Sep 21 23:40:39 unknown kernel[0] <Debug>: BasebandSPIController::reportError: Error: child driver did not allow low power/0x40: RESET_DET: Low, SPCLKCON 0, SPCON 0, SPSTA 0, SPCNT 0 - Protocol: MRDY Low, SRDY Low
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: !! mux-ad(eng)::fatalError: fatal error: kASMFatalErrorSPI (11): SPI Fatal error (0x40)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: mux-ad(eng)::changeMuxStateGated: state change: Engaged -> Error
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMRVL868x::setPowerStateGated(): 1 -> 0, 0xc0c66800
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: [77634.659667666]: AppleS5L8900XSDIO::sendCommand(): Timeout waiting for CMDRDY indication
Mon Sep 21 23:38:17 unknown kernel[0] <Debug>: System Sleep <<<<<<Why is this event out of order?>>>>>
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: pmu wake events: usb
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::sleepWakeNotification: System Powering on
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: System Wake
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: + AppleMPVDDriver[0xc0b5c800]::setPowerStateGated()
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::setPowerState(1)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMBXDevice(0xc0bbc800)::changePowerStateGated(1)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMRVL868x::setPowerStateGated(): 0 -> 1, 0xc0c66800
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMRVL868x::wakeupSequence()
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleS5L8900XSDIO::sendCommand(): CMD52 Failure - SDIO Cmd Timeout: arg(0x00000a00), error count(1), dsta register(0x0000c004)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AirPort: Enabled AppleMRVL868x (link 1, sys 0, user 1)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMRVL868x::setPOWER() [kernel_task]: 1
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMultitouchZ2SPI: enabled power, scheduled bootloading
Mon Sep 21 23:40:40 unknown apsd[52] <Warning>: <APSCourier: 0x107d70>: Stream error occurred for <APSTCPStream: 0x10e430>: Error Domain=NSPOSIXErrorDomain Code=57 "Operation could not be completed. Socket is not connected"
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: !! mux-ad(err)::bsdIoctl: Fatal error code=kASMFatalErrorSPI(11)
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: !! mux-ad(err)::validateAndGetMuxBsdInterface: Cannot perform Write on Channel 1 when state is Error
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: !! mux-ad(err)::validateAndGetMuxBsdInterface: Cannot perform Read on Channel 11 when state is Error
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSerialMultiplexer: !! mux-ad(err)::validateAndGetMuxBsdInterface: Cannot perform Open on Channel 11 when state is Error
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSynopsysOTGDevice::handleUSBReset
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::setCurrentLimit: current:100, suspended:0
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::setCurrentLimit: current:600, suspended:0
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleSynopsysOTGCore::setCurrentLimit: current:1000, suspended:0
Mon Sep 21 23:40:40 unknown CommCenter[28] <Notice>: Deactivated PDP context 0 that supports connection types 0x1
Mon Sep 21 23:40:40 unknown CommCenter[28] <Notice>: Telling CSI to go low power.
Mon Sep 21 23:40:40 unknown CommCenter[28] <Notice>: CSI can't enter low power yet, so wait longer.
Mon Sep 21 23:40:40 unknown CommCenter[28] <Notice>: Telling CSI to exit low power.
Mon Sep 21 23:40:40 unknown CommCenter[28] <Notice>: Will not sleep. Heard from CSI in 0.025225 seconds
Mon Sep 21 23:40:40 unknown kernel[0] <Debug>: AppleMRVL868x: Baseband reset detected
Mon Sep 21 23:40:40 unknown aosnotifyd[30] <Warning>: Stream:streamCallback - an error occurred on CFReadStream: Operation could not be completed. Socket is not connected
Mon Sep 21 23:40:41 unknown /usr/libexec/ptpd[1065] <Notice>: PTP interface bas been activated at high speed.
Mon Sep 21 23:40:41 unknown lockdownd[16] <Error>: (0x380f92d8) lookupbasebandinfo: The SIM status has changed
Mon Sep 21 23:40:41 unknown configd[22] <Notice>: network configuration changed.
Mon Sep 21 23:40:41 unknown configd[22] <Notice>: CaptiveNetworkSupport:CaptiveHandlePrimaryChanged:2034 new primary: NULL on NULL
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) loadactivationrecords: looking at /var/root/Library/Lockdown/activation_records (1/0)
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) loadactivationrecords: looking at /var/root/Library/Lockdown/activationrecords/wildcardrecord.plist (8/0)
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) extract_recordidentifier: Could not extract ICCID from account token
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) loadactivationrecords: Could not extract ICCID from record
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) loadactivationrecords: This is a wildcard record
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) loadactivationrecords: looking at /var/root/Library/Lockdown/activation_records (6/0)
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) dealwith_activation: No unlock record. Looking for a care flag.
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) dealwith_activation: No care flag. Looking for a record that matches the SIM.
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) dealwith_activation: Looking up the record for ICCID 89014104212131975816
Mon Sep 21 23:40:42 unknown lockdownd[16] <Error>: (0x380f92d8) dealwith_activation: No record for the SIM. Taking whatever we can get.
Mon Sep 21 23:40:42 unknown CommCenter[28] <Notice>: Baseband reset: modem reset: temperature update timeout
Mon Sep 21 23:40:43 unknown kernel[0] <Debug>: AppleMRVL868x: Baseband recovery detected
----
The last two lines look suspicious, though I don't know what's going on here. Anyone have any ideas?

To quote myself:

"I walked out with 3.1 hopeful that it would work this time, but before I had even parked the car in my parking garage upon returning home I'd already coma'd out."

So, as they say, over in one. I don't know about others who may be more gung-ho than I, but I certainly didn't take the time and effort to bring my MBP to the mall and sync my apps as soon as I walked away from the Genius Bar. I can survive the 15 minute car ride home to do that. :P

So, to answer you, yes. Coma'd on default settings. That rules out about 75,000 apps that could cause problems. Again, it comes down to a matter of bad QA.

Memory leaks anyone?

So I played around with genius mixes in iPod as they aren't normally handled well on my phone. Last time it refused to play anything and quit taking user input for several seconds. Feeling like this was maybe similar to the 'coma' I did so while logging the results...

Tue Sep 22 00:39:56 unknown SpringBoard[24] <Notice>: MultitouchHID(208ae0) uilock state: 1 -> 0
Tue Sep 22 00:39:56 unknown SpringBoard[24] <Notice>: MultitouchHID(2c8780) device bootloaded
Tue Sep 22 00:40:02 unknown MobileMusicPlayer[1165] <Warning>: Skipping iTunes Commands.
Tue Sep 22 00:40:23 unknown MobileSafari[1061] <Warning>: Safari got memory level warning, killing all documents except active.
Tue Sep 22 00:40:42 unknown configd[22] <Notice>: jetsam: kernel memory event (90), free: 258, active: 1831, inactive: 973, purgeable: 0, wired: 7278
Tue Sep 22 00:40:42 unknown SpringBoard[24] <Warning>: Memory level is urgent (10%). Asking 'Safari' to exit.
Tue Sep 22 00:40:42 unknown MobileSafari[1061] <Warning>: Safari got memory level warning, killing all documents except active.
Tue Sep 22 00:40:43 unknown MobileSafari[1061] <Warning>: Safari got memory level urgent while active with one document, destroying plug-ins
Tue Sep 22 00:40:43 unknown MobileSafari[1061] <Warning>: Safari got memory level urgent while suspended, self-terminating
Tue Sep 22 00:40:44 unknown com.apple.launchd[1] <Warning>: (UIKitApplication:com.apple.mobilesafari[0x455e]) Exited with exit code: 101
Tue Sep 22 00:40:44 unknown SpringBoard[24] <Warning>: Application 'Safari' exited abnormally with exit status 101
Tue Sep 22 00:40:51 unknown configd[22] <Notice>: jetsam: kernel memory event (90), free: 293, active: 1785, inactive: 1032, purgeable: 0, wired: 7190
Tue Sep 22 00:40:52 unknown SpringBoard[24] <Warning>: Memory level is urgent (10%). Asking 'Mail' to exit.
Tue Sep 22 00:40:53 unknown com.apple.launchd[1] <Warning>: (UIKitApplication:com.apple.mobilemail[0x87ce]) Exited with exit code: 101
Tue Sep 22 00:40:53 unknown SpringBoard[24] <Warning>: Application 'Mail' exited abnormally with exit status 101
Tue Sep 22 00:40:53 unknown SpringBoard[24] <Warning>: Memory level is not normal (10%). Delaying auto-relaunch of 'Mail' for 30 seconds.
Tue Sep 22 00:40:53 unknown SpringBoard[24] <Warning>: Memory level is urgent (10%) and there are no background apps to ask to exit.
Tue Sep 22 00:41:04 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.apple.mobilephone[0xb8c9]) Exited: Killed
Tue Sep 22 00:41:05 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.apple.mobileipod[0xccee]) Exited: Killed
Tue Sep 22 00:41:05 unknown configd[22] <Notice>: jetsam: kernel termination snapshot being created
Tue Sep 22 00:41:06 unknown SpringBoard[24] <Warning>: Application 'Phone' exited abnormally with signal 9: Killed
Tue Sep 22 00:41:07 unknown SpringBoard[24] <Warning>: Application 'iPod' exited abnormally with signal 9: Killed
Tue Sep 22 00:41:09 unknown ReportCrash[1167] <Error>: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2009-09-22-014109.plist using uid: 0 gid: 0, synthetic_euid: 0 egid: 0
Tue Sep 22 00:41:24 unknown kernel[0] <Debug>: launchd[1169] Builtin profile: MobileMail (seatbelt)

Yikes.

I've had so many problems with 3.1. The random shut-downs and the poor battery life everyone else is experiencing of course, but also difficulties charging the phone, which makes the battery drain even more problematic to deal with.

After three full restores that didn't work, I followed an online guide to downgrade from 3.1 to 3.0.1 using Terminal and iRecovery. Lo and behold, my phone works fine again. No comas, no mysterious battery drains, and it charges like it should. Next time I'll wait for a couple of weeks before updating.

I had this exact same problem. Weird, mysterious shutdown. When I went to Apple, they reset my device by holding down down the power button and menu button while the device was plugged in. Then, the support guy looked at the power mgmt and noticed that it was all out of whack. He said, "Yeah, I don't know why this happened, but this is a software problem. You need to set up this phone as a new phone." So, I have to reset the device and set it up as a new phone. Then I have to copy all of the data I have along w/ all of the apps back to it. Major pain!!! There's no way this is just a guess. I'm very disappointed that Apple doesn't release an app for this. I'd much rather have a "I'm sorry, but download this 'repair the iPhone app' that does all of this for me rather than having to lose so much of my life on an evident bug.

Disappointed,
Matthew

Can you confirm that you have no issues after the reset and set up as a new phone?

Hello,

I have tried 2 times to hard reset and restore as a new phone and same thing happens...2/3 shutdowns p/ day.

For now the only solution is to downgrade to 3.0.1.

I did update my phone first and then Itunes. no luck there either. sorry