Q: Mysterious random total shut downs following 3.1 update

I am experiencing the shutdowns, I tried to call my iphone and did not ring the screen did not do anything.... but after this has happend randomly 10-15 times since os 3.1....I have waited when the so called shutdown happens ... the iphone is not shutdown . I hit the lock button numerous times hit the home button waited i did this for about a min or 2 . the iphone suddenly woke up with no AT&T bars or 3G or Edge, then it went back up to full bars. . Apple it seems when the iphone goes into standby mode the phone is getting confused and turns off the cellular radio - this is why when I called my phone there was no response ..... this is bug is delaying response from the iphone buttons when it is standby mode . whatever you did with the standby mode it messed up the response when going out of standby mode and turn off the cellular radio randomly make the iphone useless until the user realizes its in standby no response mode.

You may think we are just pitching a fit, and that's your prerogative.BUT, I'll tell you this: I just got back from the Apple store in Orlando and their attitude has changed 100% since Saturday. I barely got the words "3.1" out of my mouth and they were getting me a new phone. The tech told me that they really don't know if it's hardware or software, but they are just replacing the phones with ones that have 3.01 on them and told me "DON'T UPDATE IT".

Seems like a pretty solid, "it's our fault, but you didn't hear it here" statement if there ever was one.

Oh, there were several people in line, in front and behind me, ALL with the same problems.

OUCH!!!

Had the problems since 3.1 upgrade as well

Seriously this is ridiculous. How long do we have to wait to see a fix??? Missing calls, missing texts, missing emails. Some people use they're iPhones for BUSINESS. So add missing important business calls to that list.
This is supposed to be the phone to beat all phones, but i don't see Blackberry's or Pre's with this problem. I'm happy that I kept my Blackjack so at least I have a phone that works!!! We should rally for refunds on phone bills or free iTunes downloads or something for this because paying for data plans is useless if you don't have something reliable to use it on.
We've all been patient for updates on certain things such as MMS but is it really worth it all? I have a friend who is already fed up and is switching to Sprint for the Pre Because it already has everything that we iPhone users have been asking for! I don't Blame him honestly. I LOVE my iPhone, don't get me wrong, but if this is how it's gonna be where the customer isn't satisfied then why stay? I've been faithful to AT&T and Apple and hoping that eventually all will be fixed. I've done my best to alert other iPhone users NOT to update but unfortunately I was too late for some of them. One of them is a business owner who is missing business. Time to act Apple.
My iPhone now has shut down at least 15-18 times since update. I've tried turning off WiFi and still shutdown. I've backed up and restored and still shut down. I've deleted apps that I've downloaded thinking maybe that'd help. Nothing. C'mon now. After I finish writing this I'm probably dusting off my Samsung Blackjack and putting my SIM card in that to stop missing calls and texts. I'm a pretty patient person but I'm sure this will discourage potential iPhone owners and maybe even current owners to re-think Apple.
You got smart people over there. hope this is remedied SOON.

SAME PROBLEM HERE..I THOUGHT THIS 3.1 CRAP WAS A UPGRADE..ALL IT HAS DONE IS CAUSED PROBLEMS FOR ME THUS FAR..

2 comments...

1. Please fill out a bug report with Apple if you are experiencing the problem. Coming here and telling us that you are also having a problem after 3.1 does nothing. Everyone on this forum already knows 3.1 is terrible. Link: http://www.apple.com/feedback/iphone.html

2. Rolling back to 3.0.1 has solved the problem for both everyone on this forum and on the MacRumors forum. Complaining about 3.1 when there is a simple fix by rolling back the software is just stupid. Yes, 3.1 is horrible. Get rid of it and wait until Apple gets it right. The link to rollback instructions has been posted MANY times on this thread.

My phone died like everyone elses.

jkoslow3:
1. "Coming here and telling us that you are also having a problem after 3.1 does nothing."
Sharing the impact helps everyone see how important fixing this and improves visibility through media attention as shown here: http://reviews.cnet.com/8301-19512_7-10357176-233.html?tag=TOCmoreStories.0
2. "Complaining about 3.1 when there is a simple fix by rolling back the software is just stupid.The link to rollback instructions has been posted MANY times on this thread."
How about just pasting in the link again instead of making me look through 65 pages of posts?

http://www.youtube.com/watch?v=jD6wti-ayOs

Message was edited by: jkozlow3

Add one more to this issue...

Apple replaced my phone!

Having same problem (see post above). Called Applecare and talked to a "product specialist". Told me this was a known issue with 3.1 software, and he gave me a case number. Took that down to the apple store and they gave me a new phone! Less than 2 hrs start to finish.

Let's see Nokia do that!!!

Of course now to restore all my stuff I need to put 3.1 on the new phone. Oh well, hopefully no problems this time.

I also own the iPhone 3G, updated to OS 3.1, and now have the same problem (lock ups). I've submitted feedback, but wanted to post here too.

Niomar

After installing 3.01 update, I'm having issues with my 3G freezing up. Hard restarts don't seem to work correctly, sometimes not doing anything at all. Please help us Apple, the many affected by this issue will not go away. It's time to take action on the issue at hand.

i believe you, but is it the same even if you aren't under the warranty and paid the 199 for a new phone? would you still get a "refurb" and not a "new" phone?

Hi All, I have informed a newspaper about this thread to try and publicise further this issue, maybe we will get Apple to at least acknowledge the coma problem and perhaps even tell us what they are going to do for a fix.