07-06-2012 12:21 PM
Recently, I noticed that my phone shuts off while in sleep mode. This just happens when I don't check it for a while and the display is turned off. When I do go to check my phone, it's unresponsive, even if I hold down the power button. So far, I've had to remove the batter every time this has happened in order to reboot it.
I just don't get what the issue is. I'm probably missing phone calls because I'm not even aware that my phone is turning off. I feel like after the ICS update my phone has had issues. I already performed a factory reset last week since I was having a problem with the notifications not ringing and vibrating, and now, this is happening on top of that.
If anyone has any suggestions, that would be greatly appreciated.
I have a Samsung Galaxy S2 i777.
Oh, and another thing, I noticed that my batter is at 95-100% before it shuts off by itself, and once it boots up again it's down to 85-89%. I also feel like it might be an issue with overheating: I noticed that my phone feels hot after I've been using it for a while, like texting or using the internet, and then I set it down to do other stuff when I notice that it's turned off. My phone usually feels really hot too, and the case I have for my phone probably does not help either.
Solved by: Go to Solution.
03-29-2013 7:27 AM
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
02-06-2013 8:57 AM
Here is one possible solution I am trying now. For about 18 hours, I didn't see the issue again.
It seems like it's power down/idle related issue per all the postings up to now. So I tried to overwrite the power down/saving scheme by:
Settings/Power saving/Custom power saving - ON
Custom power saving settings/Power saving starts at - 10% battery power
The thing I tried to achieve was by setting above configs the auto power saving/power down is not activated and only activated when there remains ony 10% of battery. I hope it overwrites the power saving mechanism that triggers the death. For the last 18+ hours I haven't got any issue yet. Hope this is the workaround of this issue.
That sort of makes sense... and is worth trying. Good idea. I do know that, one time, mine froze up over night while it was charging. So, that would rule out the power saver feature as the culprit.
02-06-2013 9:04 AM
02-06-2013 3:15 PM
OK... add my voice to the chorus!!
I actually caught this after only having the phone for 6 months so I have already had them send me one new phone.
The new one was made in Korea... the first one in China.
Upgraded to ICS Android (4.0.4) and that is ALL I did.
Both phones have been the "CLK3" build after ICS upgrade.
It worked fine for 2 weeks... like the first one... then started doing this.
I honestly think it is caused by something ATT is pushing down to the phone when we are not looking and they know it and won't admit it cause they don't know how to fix it.
Currently testing disabling the following apps:
the "0 memory" clock, Dual Clock, FaceBook, both Social Hub apps, Movies... last 3 cause I just don't use them. Yes, there are stil people on this planet NOT on FaceCrook )
I am leaving WiFi off unless I am using it... and this was the case before so unless turning WiFi off still leaves something running in the background, that is NOT the problem.
Synch is off as well.
I turn on GPS only when using it as well.
I only have a few months left on warranty so I'll give it a week or two and report back. Then, yep, they are going to send me new phones every couple of weeks until the warranty expires or they admit the problem and fix it.
Why not... missed calls and dead phones are a MUCH bigger issue to me than a dozen phones are to A$&$.
02-06-2013 4:06 PM
Just a status update: About 24+ hours, for the 1st time in the last couple of weeks, the phone is OK w/o any shutting down. Before this, my phone sometimes went to dead during idle, during even charging, during even 1 minute idle, etc and it became worse and worse. But now after config power saving as posted earlier, it's still ok. I tested idle, charging, etc and looks ok. I don't know the details but it seems like this customized power saving option blocks the dead mechanism. Hope it keeps going on. I will keep updating.
02-06-2013 4:34 PM
I don't use a 64gb microsd, my 32gb one works fine. I do not use MHL either.. sorry. Google Play is working fine after installing gapps. Had to install Flash 10 from the .apk, but other than that, the oether GP apps installed from the web just fine. I've only been running it for about 24 hours now, so I'll check back in periodically and let you guys know if I find anything that isn't working as expected.
02-07-2013 3:33 AM
Finaaly got a 3rd phone and it runnning ICS 4.0.3 and working nicely.
How do I shut off auto update, I do not want it to update to 4.0.4 again.
also my family has different phones and report that after the upgrade to 4.04 ICS they having SOD issue.
I have tried all fixiesposted here, even the fix I posted because i thought it fixed my phone but was wrong.
So I have a 3rd phone that att sent me with 4.0.3 and running good.
Please tell e how to uncheck the auto update
02-07-2013 5:59 AM
Here is another follow up:
In almost 4 weeks, my phone shut down only once! (as opposed to several shut downs a day before that).
In my case, I disabled all AT&T applications and I only turn on wi-fi (or GPS) when I need it.
02-07-2013 9:34 AM
Again an update. 48 hours. No problem yet. At least up to now, happily enjoy the power of ICS w/o any problem. Happy.
02-07-2013 10:37 AM
I know its a pain... but for those that are saying their phones now work, take the extra minute to say what you did to make it work. even if its just copying and pasting from your last post.
I have also had the problem since upgrading. I have turned att apps off, the clock, this and that and no luck. Today I had it re-flashed with 4.04 at the ATT store because thats all they said they could do. I explained the problem and she would/could not roll it back to 4.03. Its only been about an hour or two, but we'll see. In addition, I also disabled most of the apps that appeared to be ATT ones and the additional clock app. I was getting 1-3 SOD's a day, I know it hasnt worked for others, but I will post up if/when the problem continues.
The service person also said that she had not heard of the problems before and I told her that there was plenty of information on the ATT website about it! I know what I was saying was falling on deaf ears, but at least I tried.
02-07-2013 1:11 PM
02-07-2013 5:47 PM
Greetings all, Two points. I checked back into this thread as it is check marked as solved. I do not see any official problem solved statement from AT&T or any do this kind of direction from same. Today, after charging my phone to 100% I got in my truck and after sometime I noticed that my Bluetooth connection was not working. Sure enough the phone had entered the dreaded sleep of death. I rebooted the phone, which was now at 85% charge by the way, when low and behold I see the Android Dude spinning on my screen with the words Android Updating. I was going 55 MPH at the time so that's all I saw. Rebooted my wife's phone when I returned home in hopes of seeing it on her phone no such luck. SO.......is there an official fix???? Did anyone else see an Android update screen today?????
02-08-2013 6:48 AM
why is this thread marked as solved? there is no solution so far... please go ahead and mark it appropriate. thanks.
02-08-2013 10:31 AM
02-08-2013 12:28 PM
Add me to the list of users with this problem.
"Customer Support" has replaced my battery twice. The second time was a month before my warranty expired, obviously because they knew it was cheaper than replacing the phone or fixing the problem. I put up a fight about it stating it was the second battery, and that they should replace the phone, but I was told it was the protocol they had to follow before a new one would be issued.
When I complained a few weeks later about thesame issue, they basically was told too bad, you're out of warranty, contact the insurance. The "best" they could do was to offer me an upgrade. I did neither.
AT&T is well aware of this issue, so the bait and switch of replacing batteries when they know there is another problem is inexcusable. I, and others, have been with them far too long (former Cingular customer), and the GSii was the only reason I broke my staying off contract and signed for two years. I'm sorry I did.
When my contract is up, I will consider another carrier. In the mean time, this issue needs to be fixed. If I'm going to pay the insurance $199, I may as well go to Walmart and buy the Straight Talk that runs off AT&T for $299 and get a new phone. Why have insurance if you're paying that much out-of-pocket?