This discussion is locked
Close
Q: Mysterious random total shut downs following 3.1 update
first
Previous
Page
157
of 162
last
Next
-
Oct 15, 2009 2:51 AMby nujec,michaelab, unless you work for Apple tech support or you've done a survey of millions of iPhone users, your blanket statements that all is well are pure speculation and infuriating to those of us who are still suffering serious problems from the latest updates.
3.1.2 does not fix coma mode for everyone "period". My 3G is still frequently suffering from it after updating to 3.1.2. -
Oct 15, 2009 5:38 AMby michaelab,nujec wrote:
My 3G is still frequently suffering from it after updating to 3.1.2.
Then the problem you were/are having is a different problem. THE coma bug which this thread is about was fixed in 3.1.2. I refer you to Apple's release notes about the update: "Resolves sporadic issue that may cause iPhone to not wake from sleep". My phone was going into "coma" roughly once a day with 3.1, I've been running a week with 3.1.2 now and have not had a single issue.Bozo777 wrote:
I have had coma problems since late August (with 3.0)
The coma problem was only introduced with 3.1, so you too must be having a different problem.
What is infuriating is everyone who has a problem that seems to fit remotely into the "coma" category piling into this thread, which is about a very specific problem introduced with 3.1 and fixed in 3.1.2. -
Oct 15, 2009 5:56 AMby PKOneTwo,OK, now I'm really getting nervous and angry!
*** is wrong right now?
perhaps womeone has an answer:
my 3GS was about 35% last night. When I wanted to check my phone (about 10 hors later): may phone was shut off and when i tried to turn it on, it shows me that it needs to be recharged! ***: I just had WiFi on and EDGE! No 3G! no BLuetooth! No apps! No alarm! nothing!
ususally 35% is wnough to stay on even if everything is enabled!
Is this another shut down bug or what? -
Oct 15, 2009 7:27 AMby michaelab,noloze, if you really are still having the coma issue with 3.1.2 then the best thing you can do is:
1. Whenever your phone is in a "coma" state and you can't wake it, press the Home button and one one of the volume buttons (up or down, it doesn't matter) at the same time. Each time you do this it will create a StackShot file on your phone which will record all the processes and threads running at the time, which is a huge help to Apple in tracking down the cause of the problem.
2. Next time you sync your phone these StackShot files will be saved on your computer (and sent to Apple unless you disabled this):
On Mac OS X : ~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>
On Windows XP: C:\Documents and Settings\<USERNAME>\Application Data\Apple computer\Logs\CrashReporter\<DEVICE_NAME>
On Windows Vista: C:\Users\<USERNAME>\AppData\Roaming\Apple computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>
3. Register with the [Apple Developer Connection|http://developer.apple.com/membership/|ADC Sign up] (it's free) and then login to the [Apple Bug Reporter|http://bugreport.apple.com/|Bug Reporter Login] and report the problem you are having, attaching as many StackShot files as you have to your bug report.
Apple will respond to your bug report (sometimes it takes a while) and will let you know if they need more info, or if the problem you are reporting is a duplicate of one already reported by someone else, or finally, if and when the problem has been fixed in a future firmware update. -
Oct 16, 2009 1:54 AMby michaelab,DAtherton wrote:
in other words become an unpaid beta tester for Apple who don't even acknowledge the problems.
No software, however well tested, is ever totally bug free. So, if you experience a bug that you'd like fixed, the best thing you can do is let Apple know about it through the channels they provide for this, instead of screaming and shouting about it on these forums.
I don't work for Apple in any way. I am an ADC member and develop iPhone software. I always report the bugs I notice (which includes the 3.1 "coma" bug) via the ADC bug reporter and am satisfied with the results. -
Oct 16, 2009 7:43 AMby thaw3,I updated from a clean install of 3.1 (after I threw out the first 3.1 in iTunes folder that I had updated to when it first came out. So that iTunes had to download and install the 3.1 again, creating a clean install of that before I installed 3.1.2)
Have had no more comas, but did have a Safari glitch last night when going from Bookmarks to a new Safari window while rotating from portrait view to Landscape view. Had to do a shut down to get out of the frozen screen...
Location Services is much more accurate in 3.1.2 and battery with Location services turned on all day seems to be lasting much longer, too. -
Oct 16, 2009 10:31 AMby michaelab,DAtherton wrote:
+michaellab: I always report the bugs I notice (which includes the 3.1 "coma" bug) via the ADC bug reporter and am satisfied with the results.+
How can anyone be satisfied with silence from Apple for over six weeks when there is such a major problem.
When I reported the 3.1 "coma" bug I didn't get silence from Apple. I was told: "+This is a follow up to Bug ID# nnnnnnn. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering.+"
I was satisfied with that. I don't really know what more you could ask. -
Oct 17, 2009 5:57 AMby criprez,Before I left for my business trip last week I quickly updated to 3.1.2. Since the update every issue that was causing me heartache and creating the inexplicable desire for me to my iPhone as projectile and or tire stop for my Hummer has been resolved.
The ability to once again conduct commerce via the device is quite satisfying. Sure it was difficult to convince some of the clients whose calls were sent into the abyss that the problem was Apple. They too blamed AT&T because when it comes to telephone calls, who else could be responsible…a technology company? No way! Overtime these clients might find their way back to utilizing our Firms services but obviously relying on them to get their heads out of Apple’s *** is rather farfetched.
I have been in the IT/Telecom business for almost 25 years. I have been involved with situations where our mission critical technology experienced “bugs” of one kind or the other. Service effecting issues which effected capability by 20% or greater. You provide your own SLA…..(service level agreement). For ANY communications provider or device to allow such problems to fester for over a month is inexcusable! Apple exposed itself as being nothing more than a typical “IT centric” company who knows NOTHING about providing integrated telecom solutions in their portfolio. If this was RIM….or Motorola…Nokia…etc etc all **** would have been raised publically.
There is a HUGE difference in expectations when it comes to typical “IT centric” solutions (MS EXCH…WEB) and Telecom. Convergence is obviously bring the two closer and closer but one thing always remains…..DONT SCREW WITH MY PHONE!
We long time PDA phone junkies have endured outages for data….emails….web…etc. Just keep OUR phone ringing and out dialing! Look, as much as I enjoy the functionality if the iphone I also consider choosing it as a primary device to be a SACRIFICE simply because of the AT&T network (I keep a Verizon phone used for testing apps we develop in my bag….just in case..and boy did Apple create a perfect reason for me to continue the practice as well learn the new HTC Ozone rocks with a crazy fast processor).
Apple treated this crisis like the federal govt, misinformation and misdirection. Pathetic. I expect that from Washington DC….not Cupertino.
It’s nice to have my iphone functioning again. It was one less concern I had during my week long trip. Yeah things were back to normal alright…..as I drove back to the house last night calling a few west coast employees about our successes during the week, the cnf bridge full of enthusiasm as new deals were being announced as well a few new hires and the like precision Swiss clock work of AT&T wireless service disconnects along the route. Ah yes a small price to pay for “there's an app for that”.
Cheers!
