Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The following fixed my lockup problem:

My issue was the following set of events:
(1) Phone Would go to sleep
(2) hitting the home button would would take 10 seconds to bring the phone out from sleep. It would stay on the black screen for about ~10 seconds
(3) Once it did wake up it would take another 5-10 seconds for it to become responsive again.

The following set of steps seems to have fixed the issue:
(1) Settings -> Wifi : Disabled Wifi
(2) Settings->Reset->Reset Network Settings
(3) Reboot
(4) Settings -> Wifi : Enable Wifi

My iPhone has not locked up since. ( 5+days now of constant usage).. the previous lockups would occur within a few hours of a phone reboot.

It seems like there might be several causes of the unresponsive behavior.. but this at least fixed mine.

this worked, for about 3 hours. they need to fix this pronto, my phone was great for 9 months and then 3.1 comes out and now it goes into "coma" constantly
 
The following fixed my lockup problem:

My issue was the following set of events:
(1) Phone Would go to sleep
(2) hitting the home button would would take 10 seconds to bring the phone out from sleep. It would stay on the black screen for about ~10 seconds
(3) Once it did wake up it would take another 5-10 seconds for it to become responsive again.

The following set of steps seems to have fixed the issue:
(1) Settings -> Wifi : Disabled Wifi
(2) Settings->Reset->Reset Network Settings
(3) Reboot
(4) Settings -> Wifi : Enable Wifi

My iPhone has not locked up since. ( 5+days now of constant usage).. the previous lockups would occur within a few hours of a phone reboot.

It seems like there might be several causes of the unresponsive behavior.. but this at least fixed mine.

You forgot the part where you remove the cartridge from your Nintendo, blow in the cartridge, blow in the cartridge slot in the Nintendo and then try it again. Always works for me.

nintendo-entertainment-system.jpg
 
Thinking about iPhone alternatives

iPhone 3g 16g

I'm having the same problems everyone else is having with the 3.1 update. The biggest hassles are battery life and the coma. I reset and setup as a new phone - I'm still having the same problems.

I called Apple (1 800 MY IPHONE), and despite over 50M google hits for "iphone 3.1 bugs" in the last 24 hours they refuse to acknowledge a problem. "Sorry sir, we're always the last to know." WTF? Funny thing, when I suggested I was going to call ATT and ask why I was paying almost $100 a month for service for a phone that doesn't work, they passed me on to a supervisor who offered to send me a new phone (I'm out of warranty). Actually, he offered to send me a box/label so that I could eventually get a refurbished phone in 7-10 days (or I could pay $25 for express 3 day service). When I asked why a refurbished hardware would fix a software problem, I got more snottiness (apple geniuses are like a bad SNL skit). When I asked if I could do the swap at the nearest Apple store (45 min drive), he said nope.

Next I called ATT. They were much nicer, but not much help. All they offered to do was extend a $60 credit so I could by a throwaway phone to use while I waited for Apple to send me the refurb phone. Since I'm not convinced that replacement hardware is the answer, I asked them to do one of 2 things: 1) enable me to upgrade to the 3gs 4 months early (kind of a double down on Apple strategy), or 2) waive the cancellation fee, if I decide to pass on the periodic iphone headache - the battery hassle is not new - seems to happen every late summer/fall, and the ATT service has always been spotty (the surrender strategy). They declined both requests.

I really hate doing business with ******s (apple support), and I never, ever wanted to do business again with ATT until the iPhone came out (the death star even bought my local phone company, so I can't get away from the them), so I'm seriously considering walking away from the iPhone experiment.

Anyone else feel the same way?

I'm going to cool off for a day or two, and then maybe do some smart phone shopping over the weekend.
 
My phone bricked again.. :mad:

So this means another 4 hours of not getting phone calls and texts. Thank God it's after 7:00 when work calls stop.

Going back to the Apple store tomorrow.. They better not force me to make an appointment when the store is empty. They tried that route last time.
 
Wow… lots of angry posts here.

I think some of you should just downgrade to 2.2.1 and be done with it. Your iPhone will feel so much faster and responsive on 2.2.1. After running 3.0/3.1 for so long you forget how much better 2.2.1 was.

Anyways… 2.2.1 is working flawlessly on my iPhone and I couldn't be happier with it (well, I could use copy and paste… heh. It's not that big of a deal for me though)

I'm sure Apple will come out with 3.1.1 and it will fix all of the problems people are having.
 
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 - hell, 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.

Sorry to quote my rather long post, but I wanted to follow up on my happenings here. I ended up making a Genius Bar appointment for the 22nd at 8:20PM EST at a different Apple Store location here in Atlanta, because the original one I had gone too had no available reservations for the 22nd and last time I went I had to do standby, and that was a pain.

So I got to the Apple Store and checked in and waited patiently for my turn. When I was called to the Genius Bar I explained my situation again, adding in the details that transpired during my last visit. She was familiar with the 3.1 OS complaints, and asked a few basic questions about the device and ran a diagnostic on it. After some brief chit-chat (she was really helpful... and fairly cute too), she concluded that since my device was in a new-like condition that I hadn't abused the iPhone, and it had to be a hardware/software issue that restoring couldn't fix. To boot, she also added it was unacceptable that I had to wait in the standby line at the other Apple Store location to merely have a Genius Bar rep do a fruitless restore AND not inform me that my Launch-Day iPhone 3G was out of warranty. As such, she announced that she's approved me for a free iPhone 3G replacement, did some paperwork, and said as soon as they get a 16GB iPhone 3G in stock it's mine (should be within a few days, they're all out).

I'm stoked! This visit could not have been more satisfying (well, unless I actually got the phone)! She said that the replacement will hopefully come with 3.0.1 and she would NOT recommend updating until a fix is announced, and in the meantime the new replacement has a complimentary 90 warranty if anything else goes wrong.

Again, I could not be more satisfied with the way this was handled. Kudos, Apple. Now get us a fix and I'll be peachy-keen. :apple:
 
Hi

My 8Gb 3G is "pristine", as previously defined. Upgraded to 3.1, experienced this problem every day since.

This weekend I found time to do a clean restore and set up as new iPhone, rebuilding apps, settings, music, MobileMe and Exchange etc from scratch.

Set up everything as before, except for push notifications from ToDo.

Has now been fine for 24 hours, hasn't crashed once.

Will reconfigure ToDo, and see what happens with push enabled...

Andy

Without wishing to tempt fate, my problem seems to have gone away. In addition to the above, I disabled Safari's phishing filter, as some had suggested earlier...

Fingers crossed. Any further problems and I shall have to make a Genius appointment.

Maybe Apple will release a 3.1.1 software fix soon anyhow!
 
This happened to me too! I don't remember it being locked into the camera, but when I tried to wake mine and found it in a 'coma', I mashed the buttons in exasperation and maybe 15 seconds later it woke up with every button press taking a screenshot. At the time I thought I'd maybe stuck down the lock button so that pressing home was registering as both being pressed together, but apparently I'm not the only one.

You're definitely not the only one. I had that on my first phone. On two occasions it came back to life after a coma, but was stuck taking screen shots for maybe 10 minutes or so. Any time I pressed home or lock, it would take a photo. Weird, huh?

The thing that bugs me out is that after getting a refurb replacement, I started from scratch by setting it up as a new phone, and later discovered that the wifi was dead. I thought this was just bad luck getting a busted refurb, but someone else reported the same thing on this list! WTF?

Now I'm on my third phone! After a horrible, horrible experience dealing with both Apple and Softbank (the carrier in Japan), Softbank finally gave me a brand new phone fresh out of the box. I didn't want to take any chances so I started as a new phone again, rather than restoring from a backup. Everything has gone pretty well, but I had one coma today. I hope to God it was a fluke. I don't have the energy to deal with this problem any more.

Just wondering why all of us are having this problem and not others? I'm using a 1 1/2 year old macbook pro. I wonder if that has anything to do with it, because my wife has a macbook and an iphone bought on the same day as me, and she hasn't had any problems. I have a 16gb black phone and she has the 16gb white. Perhaps its an app that's causing it? Who knows?
 
Well, I'm currently in the Glasgow Apple store, having purchased my iPhone 3G 8GB, and I'm giving it a charge before heading home (cheap I know!). Posting this from a 13" Macbook Pro ...very nice!

Anyway, I am absolutely delighted that my iPhone does not come with 3.1 pre-installed. In fact it's not even got 3.0 pre-installed. My new iPhone comes with 2.2 pre-installed, which might explain why it's nice and "zippy" to use a Steve phrase.

I'm not interested in unlocking it or jailbreaking it, but I sure as hell won't be updating it anytime soon.

Oh, and to those who dissed the iPhone activation zones in the main section of the forum ... business is booming here this morning. There's three guys behind me taking iPhone's and there's another four people waiting to be seen. My own activation went flawlessly, and was very impressed with the assistant who sorted me out.

Although, just in case, how can I obtain the 3.0 update without going to 3.1 ... there's no official source to download 3.0 now.
 
Sorry to quote my rather long post, but I wanted to follow up on my happenings here....

great information toanavinai. My phone (3G 16gb) hasn't experienced the 'coma' thing, thank god, at least not yet knock on wood!! But it did do the 'unresponsive' thing just yesterday. I was talking on the phone and wanted to access another app. Usually just hitting the home button takes you, um, home, but this time it wouldn't dismiss the phone screen. I then tried going to contacts, and from there it let me into the rest of the phone/other apps.

What I've noticed with 3.1 is the increased battery suck. Even with just 2 hrs of use my phone is down to 50% by the afternoon, and down to 20% by the time I go to bed. it NEVER did this before. I don't use my phone that much typically during the day, and it used to always be at ~80% at the end of the day.

Granted, battery suck is better than bricking, but it's still annoying and I wish I could go back to 3.0. Now I'm worried it's only a matter of time before I start getting the coma.

way to go apple! what was that about satisfied customers??
 
Originally Posted by ThirdMartini
The following fixed my lockup problem:

My issue was the following set of events:
(1) Phone Would go to sleep
(2) hitting the home button would would take 10 seconds to bring the phone out from sleep. It would stay on the black screen for about ~10 seconds
(3) Once it did wake up it would take another 5-10 seconds for it to become responsive again.

The following set of steps seems to have fixed the issue:
(1) Settings -> Wifi : Disabled Wifi
(2) Settings->Reset->Reset Network Settings
(3) Reboot
(4) Settings -> Wifi : Enable Wifi

My iPhone has not locked up since. ( 5+days now of constant usage).. the previous lockups would occur within a few hours of a phone reboot.

It seems like there might be several causes of the unresponsive behavior.. but this at least fixed mine.

This seemed to work for me. No lock ups or comas but still laggy as hell.

I decided to do the 3.01 restore and I'm back to all the V 3 goodness that I loved.

What a cluster... from Apple, it giveth and taketh away.
 
My third iPhone has now started to experience the issue. Where do you go from here? I've started with a clean version of the OS, I set it up as a new phone, and only put on a limited number of apps. It's either one of these Apps causing this or the issue comes from my MBP. I have the latest version of iTunes and I'm now using Snow Leopard.
 
Just got back from the Apple store. They gave me another replacement phone (the 2nd one in less then a week) and i am not gonna update to 3.1

After waiting around for 40 minutes and then saying "well all we can do is try to restore the phone", i told him this will be my last trip to the store, and if i do end up back here, its gonna get ugly. A few minutes later they reluctantly gave me another phone with 3.01 installed on it.

I've done multiple restores as new, with manual installs of my apps and whatnot. Still no luck.

I'm happy now.
 
My third iPhone has now started to experience the issue. Where do you go from here? I've started with a clean version of the OS, I set it up as a new phone, and only put on a limited number of apps. It's either one of these Apps causing this or the issue comes from my MBP. I have the latest version of iTunes and I'm now using Snow Leopard.

It's pretty simple...stop updating to 3.1. Rollback to 3.0.1 and wait for Apple to fix 3.1. Rollback instructions have been posted numerous times.

I just don't understand why everyone keeps getting replacement phones and upgrading them to 3.1. It's a SOFTWARE issue. If your phone worked fine before 3.1, use the previous version of your software and you'll have a "usable" phone again.
 
I just don't understand why everyone keeps getting replacement phones and upgrading them to 3.1. It's a SOFTWARE issue. If your phone worked fine before 3.1, use the previous version of your software and you'll have a "usable" phone again.

You're right. It is a software issue. It is a software issue that apple has officially released that is incompatible with its own hardware. Furthermore, apple does not allow me to restore to 3.0.1 without jailbreaking. I, for one, was not going to go through extra trouble to jailbreak just to get a phone that works. It's not that I couldn't have jailbreaked. It is the principle. I'm not going to resort to hacking my phone just to get to a working phone.

So, as I've already posted, I got a replacement. With 3.0.1. And it works.

Do you understand now?
 
You're right. It is a software issue. It is a software issue that apple has officially released that is incompatible with its own hardware. Furthermore, apple does not allow me to restore to 3.0.1 without jailbreaking. I, for one, was not going to go through extra trouble to jailbreak just to get a phone that works. It's not that I couldn't have jailbreaked. It is the principle. I'm not going to resort to hacking my phone just to get to a working phone.

So, as I've already posted, I got a replacement. With 3.0.1. And it works.

Do you understand now?

Yes, but you do NOT have to jailbreak to roll back to 3.0.1. You only use jailbreak software to kick it out of recovery mode - nothing more. And someone even said that you don't even need to do that (though I've not tried the alternate technique).

Anyway, I agree that we shouldn't have to resort to jumping through all these hoops to rollback the software, but it's not THAT difficult. My only point was that people keep whining about 3.1 when there is a fairly simple solution.

Glad Apple hooked you up with a replacement though!
 
Yes, but you do NOT have to jailbreak to roll back to 3.0.1. You only use jailbreak software to kick it out of recovery mode - nothing more. And someone even said that you don't even need to do that (though I've not tried the alternate technique).

Anyway, I agree that we shouldn't have to resort to jumping through all these hoops to rollback the software, but it's not THAT difficult. My only point was that people keep whining about 3.1 when there is a fairly simple solution.

Glad Apple hooked you up with a replacement though!

You actually don't even need jailbreaking software to kick it out of restore either. I use iRecovery. It's a commandline tool that you enter some commands with and the iPhone restarts and everything is fine. I've done this many times. I roll back to 2.2.1 all the time.
 
Has there been any word of a fix for this? My sister has a 3g and wants mms but I've told her she shouldn't upgrade to 3.1 yet.
 
I just don't understand why everyone keeps getting replacement phones and upgrading them to 3.1. It's a SOFTWARE issue. If your phone worked fine before 3.1, use the previous version of your software and you'll have a "usable" phone again.

I upgraded to 3.1 with my replacement phone and there hasn't been an issue in 2 weeks. There are millions of iPhone users out there without any issues with 3.1. All the employees at the Apple Store that I asked upgraded their iPhones to 3.1 without issues and 3 of my friends upgraded without an issue. I have a hard time believing its a software issue when so many have upgraded without issues.
 
This problem was pretty much unheard of until 3.1. Now there is a 17-page thread of people who started having this problem only after updating to 3.1. And everybody who has moved their phone back to 3.0.1 has had the problem go away. If that's not a software issue, then I don't know what is. It could obviously be hardware related as well (i.e. only certain batches of iPhones exhibit the problem due to some minor difference in hardware), but it's very clear that the underlying issue is a software problem.
 
This problem was pretty much unheard of until 3.1. Now there is a 17-page thread of people who started having this problem only after updating to 3.1. And everybody who has moved their phone back to 3.0.1 has had the problem go away. If that's not a software issue, then I don't know what is. It could obviously be hardware related as well (i.e. only certain batches of iPhones exhibit the problem due to some minor difference in hardware), but it's very clear that the underlying issue is a software problem.

You should see the roughly 90-page thread on Apple's own discussion forums!

I find is unbelievable that Apple has yet to make an announcement on this issue.
 
This problem was pretty much unheard of until 3.1. Now there is a 17-page thread of people who started having this problem only after updating to 3.1. And everybody who has moved their phone back to 3.0.1 has had the problem go away. If that's not a software issue, then I don't know what is. It could obviously be hardware related as well (i.e. only certain batches of iPhones exhibit the problem due to some minor difference in hardware), but it's very clear that the underlying issue is a software problem.

I'm not saying anyone is wrong here, its just so weird that this problem is shattered all over.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.