• Your favorite








    , and
  • iPhone 3.1 "Coma Mode" Reports Mount, Apple Silent

    Apple's support forums are humming with reports of iPhones gone non-responsive after their owners upgraded to version 3.1 of the firmware, and users are growing increasingly restive at Apple's steadfast denial that any bug exists. When the error occurs, the iPhone isplay appears to be functional, but does not react to any input on the touch screen or external buttons, and needs a hard power cycle and reboot before it will work again. The problem - dubbed "Coma Mode" for the phone's complete lack of interactivity when it gets in this state - has been noted sometimes when the phone has been put to sleep, sometimes when it's locked, and sometimes at completely random moments.

    One user brought his 3G in for service at the Apple Store, where they promptly tried to sell him a 3GS. However, he got a mixed message from the Genius Bar tech, who gave him an interesting mix of party line and good guidance:
    the official line is 'it is an un-repeatable error that can't be replicated on demand' so therefore, we don't acknowledge it as something to fix'.... but guys, I think your best bet is to roll your O/S back to the previous version if that worked better for you.
    Fairly consistent reports show that rolling back to 3.01 resolves all "Coma" issues, a strong indication that the problem has to do with the new firmware.

    Problems that can't be easily replicated are definitely frustrating to developers, and it's understandable that companies may not want to allocate resources to chase down a problem that may not be a problem after all. However, customer perception still has dollars-and-cents value, and Apple should be cognizant of the price they pay when polls like this one start cropping up on websites:

    Has anyone experienced this issue, and if so is there any consistency in when and how it appears?
    This article was originally published in forum thread: iPhone 3.1 "Coma Mode" Reports Mount, Apple Silent started by Paul Daniel Ash View original post
    Comments 110 Comments
    1. iRockish's Avatar
      iRockish -
      The only problem I've faced on 3.1 is the phone app crapping out on me until I reboot

      If I don't reboot and try to call with it, I can't hear the other person or the call never connects.
    1. metyme's Avatar
      metyme -
      I'm still having the problem. I upgraded my 3G on Friday, didn't know anything was wrong until Saturday and the problem is reoccuring today twice. It seems the phone goes into a coma if it goes into sleep mode for more than an hour. It's really p**sing me off! I've missed important phone calls behind this crap.
    1. Garage Battle's Avatar
      Garage Battle -
      Quote Originally Posted by HomieG35 View Post
      I use my iPhone in a clinical setting that requires a certain program be installed on our PDAs. I cannot have my phone in a comatose state while trying to chart data of a coma patient. Nothing more frusterating.
    1. Wolftamer's Avatar
      Wolftamer -
      I've had it happen twice now. Both times as I locked my phone. It then wouldn't never come back from the lock. Just stayed on the black screen. I had to perform a reboot each time to get my phone back. Very annoying.
    1. cyprez's Avatar
      cyprez -
      Quote Originally Posted by cuty_kamu View Post
      i think this coma mode only jail-breakers are getting it... i'm using official unlocked iphone which i bought from hongkong is working exactly fine as i have not jailbreak my phone.
      Definetly not just JB having probs. Mine is a 3G, not JB anymore and I've had this issue since upgrading FW. I have had several instances where I cannot dial, text, etc. If you call the phone it will eventually go to voicemail just as if I didn't answer. On occasion if I put the phone to sleep then hit the home button, I get nothing. The only way I've found to fix the problem is holding home/power to reboot. Just holding power to try and turn off gets no response either. My wife has a 3Gs and same upgrades, non JB, and has had no issues at all.

      I've called at&t once, and got the usual BS, turn off, remove sim card, blah, blah, blah.... We'll see shortly how the second call goes as I have had to reboot already this a.m.
    1. cranie's Avatar
      cranie -
      My wife has a 3G on 3.0 JB and it has now started to display these symptoms as well
    1. Cyberwaste's Avatar
      Cyberwaste -
      Trying to downgrade but having issues running iRecovery for windows. My iss is that when i install iRecovery i lose ALL usb functions. Mouse stops working, no sound from speakers etc... Anyone one running windows have this problem and if so how did you correct it. Thanks ALOT in advance
    1. CZroe's Avatar
      CZroe -
      I've been getting this recently with plain-Jane FW3.0. I lock the phone and see the animated "shine" on the "slide to unlock" text but it will not respond. I can press sleep/lock twice and sometimes it will respond then but, often times, it requires more than that (another sleep/lock cycle or a power cycle).

      It has nothing to do with a screen protector or an errant touch on the multitouch touch screen. Which reminds me... I'm kinda pissed off that multitouch confuses the slider lock screen. I mean, isn't that kinda thing what multitouch is for?! My finger on the side of the phone from the hand holding it should not affect the interaction my other finger has with the slider.
    1. mdc929's Avatar
      mdc929 -
      for once it pays to have a 3GS
      think i might completely ignore this update even when JB comes out
    1. ddonuts4's Avatar
      ddonuts4 -
      i now have 3.1.2 and have had no "Coma mode" issues yet has anybody else still been having them?