3.1 leading to unresponsive device

[toobigtofly22]

Add one more...

I've had the same issue since 3.1 update. Cannot get the screen to wake up. The only thing that has worked for me is the reset (home + sleep). This happens a few times a day. I am a MobileMe subscriber with push enabled. The past few times it has done this, I have performed the reset, and as soon as the iPhone completely boots, I get the new email sound and have items in the inbox. Maybe this problem is with the mail app. I do not remember if this was the case the previous instances when it became unresponsive, but I will see if this is a trend in the future.

 

[Mark Booth]

I have no idea how many folks with the "iPhone unresponsive" problem had installed a tethering hack (or jail broken) their iPhone before installing 3.1 but.... I had an AT&T level 2 tech tell me outright that installing 3.1 over a "hacked" iPhone will almost always lead to problems. After installing 3.1 on my 3GS I started having problems with complete loss of data service (had to reset the phone to get data to work again) and complete loss of visual voicemail. I HAD installed one of the tethering hacks under 3.0. The rep flat out told me that was what was causing the problem. He instructed me to do a complete restore to factory defaults (don't use a backup install) and manually reinstall all of my settings/songs/apps. That completely fixed all of my problems.

So, if you "hacked" your iPhone in any way prior to 3.1, that could be the problem.

Mark

 

[3460169]

So, if you "hacked" your iPhone in any way prior to 3.1, that could be the problem.

That could certainly be a accelerant but again many of us are good little boys and girls and haven't, ever, hacked or otherwise modded our phones and still have this issue.

 

[3460169]

Just a reminder:

http://www.apple.com/feedback/iphone.html

If you're experiencing the problems described in this thread, and haven't yet visited the above link to post a bug report to Apple, please take a moment to do so.

 

[intrepid00]

Just got done my Genius Bar appointment and the only thing reported as errors were software. Offered a hardware swap after I said already did new restore. Said no thanks cause I'm sure it is just an issue with either the baseband or springboard.

 

[HJ76]

So, if you "hacked" your iPhone in any way prior to 3.1, that could be the problem.

Mark

Nope I have never hacked/jailbroken my phone

 

[Dansk]

Mines completely factory never hacked/jailbroken etc and I only have a few apps I mainly use it as a portable email device ( missing my BlackBerry BIGTIME this thing has been a lot of grief )

 

[wacky4alanis]

LOTS of us having this problem have never jailbroken our phones (including me). We just want the phone to work properly as advertised.

 

[wolfpackfan]

So, if you "hacked" your iPhone in any way prior to 3.1, that could be the problem.

Haven't done it - never have and never will and my 3.1 iPhone has locked up at least 10 times. My setup is about as plain vanilla as they come.

 

[mrpoovey]

I dont have MobileMe and I am getting this problem as well

 

[CoreyHM1]

Add one more to the list, this has happened to me about three or four times in two days.

 

[Helmigurt]

Mine too, froze, people could call me but the screen showed nothing (black). I restored the iPhone (3G 16GB) and it got better but it stells feels a bit sluggish compared to 3.0 especially with safari (no snappines this time )

I don´t have a mobileme account, neither did i jailbrak anything, but i had the benm.at hack to configure tethering (which isn´t available in 3.1...)

 

[Appdict]

Yes! I experience the same thing. It mostly happens when I leave a text-message notification on the lockscreen. I'm incredibly happy it isn't only me!

Although, I have the Mophie JuicePack air so it doesn't do this whilst plugged in. But when I have it caseless, it does this pretty often.

Also, I do have MoblieMe set up.

 

[3460169]

From the Apple discussion forums regarding this topic (which is now 33 pages and counting) -- take a at the first post here if you're on a Mac (don't know where crash reports are kept on windows, sorry). Curious to see what kind of crash data people who are experiencing a lot of crashes are getting.

The crash data from my phone for the month of September, sorted by date (sorry, a little hard on the eyes):

200909161354 iapd_2009-09-15-193625_kPhone.crash
200909161354 aggregated-2009-09-15.crash
200909161354 Baseband/log-bb-2009-09-14-stats.txt.submitted
200909151123 aggregated-2009-09-14.crash
200909141214 aggregated-2009-09-13.crash
200909141214 Baseband/log-bb-2009-09-13-stats.txt.submitted
200909141214 Baseband/log-bb-2009-09-12-stats.txt.submitted
200909122226 aggregated-2009-09-12.crash
200909122226 Baseband/log-bb-2009-09-11-stats.txt.submitted
200909121641 aggregated-2009-09-11.crash
200909121641 NAVIGON_2009-09-11-131929_kPhone.crash
200909111132 aggregated-2009-09-10.crash
200909111132 ResetCounter.crash
200909111132 Baseband/log-bb-2009-09-10-stats.txt.submitted
200909101229 aggregated-2009-09-09.crash
200909101229 BeejiveIM_2009-09-09-183325_kPhone.crash
200909101229 Baseband/log-bb-2009-09-08-stats.txt.submitted
200909091703 Baseband/log-bb-2009-09-08-20-36-57-csi.txt
200909091703 Baseband/log-bb-2009-09-07-stats.txt.submitted
200909080202 MobileSMS_2009-09-05-122311_kPhone.crash
200909080202 Flixster_2009-09-05-171731_kPhone.crash
200909080202 Baseband/log-bb-2009-09-06-stats.txt.submitted
200909080202 Baseband/log-bb-2009-09-04-stats.txt.submitted
200909050230 Baseband/log-bb-2009-09-03-stats.txt.submitted
200909032245 Baseband/log-bb-2009-09-02-stats.txt.submitted
200909021333 Baseband/log-bb-2009-09-01-stats.txt.submitted
200909021333 Baseband/log-bb-2009-08-31-stats.txt.submitted

Those "aggregated" ones certainly look suspicious; don't see any of 'em prior to Sept. 10th.

 

[bamafever09]

ive had my replacement for about three hours now and not a single problem yet.... fingers crossed

 

[iWally]

I have no idea how many folks with the "iPhone unresponsive" problem had installed a tethering hack (or jail broken) their iPhone before installing 3.1 but.... I had an AT&T level 2 tech tell me outright that installing 3.1 over a "hacked" iPhone will almost always lead to problems. After installing 3.1 on my 3GS I started having problems with complete loss of data service (had to reset the phone to get data to work again) and complete loss of visual voicemail. I HAD installed one of the tethering hacks under 3.0. The rep flat out told me that was what was causing the problem. He instructed me to do a complete restore to factory defaults (don't use a backup install) and manually reinstall all of my settings/songs/apps. That completely fixed all of my problems.

So, if you "hacked" your iPhone in any way prior to 3.1, that could be the problem.

Mark

I've only just done the tethering "hack." Should I just remove that profile and reset the phone before upgrading the software? I'm afraid to even try it!

 

[rebby]

That could certainly be a accelerant but again many of us are good little boys and girls and haven't, ever, hacked or otherwise modded our phones and still have this issue.

I am one of them. I have a bone stock 16g iPhone that I bought in December. Never hacked it, likely never will. Additionally I have a friend who just bought an iPhone about 3 weeks ago. His came with 3.0 and he "upgraded" to 3.1 2 days ago. He immediately started having major problems, just as I did.

 

[champ01]

WHY IS THIS NO FRONTPAGE NEWS???

What's up with that macrumors!

LOTS OF PEOPLE CANT USE THEIR PHONE ANYMORE SINCE 3.1

Doesn't macrumors think this is a major problem?

THIS IS REAL NEWS!

 

[WeegieMac]

WHY IS THIS NO FRONTPAGE NEWS???

What's up with that macrumors!

LOTS OF PEOPLE CANT USE THEIR PHONE ANYMORE SINCE 3.1

Doesn't macrumors think this is a major problem?

THIS IS REAL NEWS!

While I agree 100% with your comments, I was more or less called a liar on here after people claimed I wanted 3.0 pre-installed on the iPhone 3G I'm buying next week instead of 3.1 so that I could jailbreak or unlock it, when in actual fact I'm paranoid about having a £342.50 brick.

It seems that the general consensus is that if you're having 3.1 issues then you've attempted to jailbreak or modify the phone in some way in the past or have been too impatient to allow the upgrade to finish completely and disconnected your iPhone too soon ... some people will, unfortunately, rather point the finger at you rather than Apple, which is a common trait on this board no matter what facts you supply in return.

Will it is common knowledge that people only really post problems on forums, which thus amplifies the problem to some peoples eyes, there have been far, far too many reports of people's iPhones bricking or becoming useless after installed 3.1.

 

[nickrw]

FWIW: I have not had any more problems since connecting to iTunes, clicking restore and setting the phone up again from backup (NOT as a new iPhone).

Prior to the 3.1 update I did have the tethering hack installed, but since it was useless after the update I removed the APN settings bundle (this was prior to the restore).

 

[wolfpackfan]

I haven't had any more problems since I set Calendar to sync manually with Google Calendar/Exchange rather than push. I've also removed any apps that I felt I didn't absolutely need. So far no lockups (knock on wood).

 

[HJ76]

I have just had a thought - rare occurance escpecially at work!

While I have never hacked or Jailbroken my iphone, i have no clue about it's history before it was given to me as a white box replacement in june.

 

[3460169]

My phone crashed this morning for the 4th time since upgrading to 3.1. Only four crashes is a blessing since some folks are seeing 10+ per day.

The crash log data created in ~/Library/Logs/CrashReporter/MobileDevice/<myphone>/ are utterly useless. The only files created there are

aggregated-2009-09-16.crash
ResetCounter.crash


This was also a hard lockup; with previous crashes the phone came back to life after a little bit on its own. This one required the Home+Sleep fix after having let it sit for an hour.

And what was the phone doing at crash time? Nothing at all. Just sitting on my coffee table like it had been the previous 9 hours.

 

[DravenGSX]

My phone crashed this morning for the 4th time since upgrading to 3.1. Only four crashes is a blessing since some folks are seeing 10+ per day.

The crash log data created in ~/Library/Logs/CrashReporter/MobileDevice/<myphone>/ are utterly useless. The only files created there are

aggregated-2009-09-16.crash
ResetCounter.crash


This was also a hard lockup; with previous crashes the phone came back to life after a little bit on its own. This one required the Home+Sleep fix after having let it sit for an hour.

And what was the phone doing at crash time? Nothing at all. Just sitting on my coffee table like it had been the previous 9 hours.

Can you post the content of the aggregated-2009-09-16.crash file?

 

[toobigtofly22]

I'll have to check my error log as well. I will venture to guess that it is pretty extensive, considering my phone locked up 4 times yesterday. It hasn't locked up today yet (knock on wood). Also, as many others have also stated, my phone is neither jailbroken or hacked in any way. I think if everyone leaves feedback at Apple's website, we will probably see a software update relatively quickly. Also, I have my phone set up to send error reports to Apple when syncing. This may also help speed up the update/fix process.