Welcome to the new AT&T Community
We've got a fresh look! Take the tour to see what's new.
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.
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
I'm tired of waiting for "real soon now" to become "now." I rooted my S2 and installed SuperNexus 2.0 (Android 4.2.2), and it's been running flawlessly. Waiting for AT&T to do the right thing is a fool's game.
ablan, SOD has been an ongoing problem since ICS came out last year...Never had an issue of any kind before that. I can't even count how many times my phone has been wiped and reset. A google search at the time showed many reports of this issue. All technical support would tell me is wipe your phone and reload ICS. I got 4.03 from Kies...I hoped that it would fix my problems, but no. I got 4.04 over the air, then after the SOD incidents increased and the proximity sensor issue surfaced, I went back and wiped it and reloaded from Kies...Twice.
dogtired, I agree with ablan on this. Not denying that you were having SOD issues with 4.03. But I'm thinking your situation was more of an abnormality. I did not have SOD issues prior to 4.04. I received a refurbished S2 around 2/27, running 4.03, and have not had a SOD since then.
You can even clearly see a timeline in this thread. If you got to the first page there were only a few posts, prior to 4.04, that were having issues. Since 4.04 there's been 15 pages of issues.
I had it during the first little bit of the 4.0.3 update, but no where near as much and it went away after a while (not really sure on how)
but since the 4.0.4 update it has happened way too often for me to be happy and continues to do so
I've had the same issues for months. Finally contacted ATT. The service rep stated they know of the issues and they are hopeing for an update from Samsung. The best part was that they were blaming Samsung and that it's not an ATT issue. Anyway, they gave me a credit and sent me another G2. The new phone came with 4.0.4, but it had different things/apps that my previous phone with the update didn't have. So far, it's been a solid week with NO issues (shutting down or no sound on my notifications) . Hope I got lucky.
The SOD issue for this phone started after the ICS 4.0.3 update. It rarely happened, but it was definitely there. The 4.0.4 update made it so it happened much more often.
I now have had JB 4.1.2 installed for about 4 months and no SODs at all in that time. So definitely not an issue with my hardware.
Hi Joseph, we received your private message and replied. We look forward to assisting you.
Phillisa on behalf of Jamileh
This has been a helpful, if frustrating thread. Thanks to everyone who has offered suggestions.
My situation was/is as a Straight Talk customer. I had bought the phone from a private party and enjoyed it on 4.0.3 for a couple months. Obviously, the phone was not under warranty. Then I updated to 4.0.4 in December. I actually probably would not have upgraded intentionally, but I anticipated one more confirmation screen before the over-the-air download started. Oh well, I thought. But within a day, the SODs came.
I was about to commit sepukku over this issue, but decided to give rooting a try. I would encourage anyone still having SOD problems to give that approach a go. I was afraid I wouldn't be smart enough to figure out how to do it, but the xda forum folks are extremely helpful, if you want to try there (although I was able to do everything based on instructions posted in the forums). Not only have I had no SODs for a couple weeks, but the entire phone experience has either remained exactly the same, or improved, sometimes significantly. Wasn't really expecting that kind of success.
Shostock3 is great, for what it's worth. Completely stable for 2 weeks running for me.
So is ATT helping people on an individual basis? I just called tech support and was told that the software update would be out "soon". I asked what date "soon" was and of course the tech didn't know.
Getting help from AT&T seems to be a game of roulette. Perhaps you will get that one person who is aware of the problem and has the willingness (and permission) to help you, and perhaps you will get the call-center operator who doesn't care for you or their job, doesn't really understand phones, and is just reading from the script and collecting a paycheck.
Am I the only one finding this "send us a private message and we'll help you" a bit odd? It's almost like it's AT&T's way of trying to keep the issue "quiet". This shouldn't be done on an individual basis. AT&T/Samsung released an update that ruined our very good phones. They need a fix for this like yesterday. Why not just release the Jelly Bean upgrade?
This is a must read. It's a link to a news site telling about the 4.0.4 update. Check out the comments. There are many that are immediately describing the SOD issue with the update.
AT&T knows they sent out a bad update that has damaged people's phones. All these month's later and no fix. It's pretty clear they're working on squat to fix it and hope people just lay off.
After a number of emails today I was told the S2 will not be getting 4.1. However they will let me buy a new phone for $200 plus an upgrade fee of $36 and extend my contract for 2 more years. I politely told them no thanks and I will be moving on when my contarct expires in 3 months. Their response to this issue is incredible.
I never bothered to post "Me too!" - wonder how many of us there are. But had the same problems... right after 4.0.4 update, started getting SOD (and horrible battery life). Saw all the grief and non-progress made by others and figured I'd save myself the hassle. I don't want a new phone nor a new contract.
Now rooted, running SHOstock3 (Jelly Bean) (gives the SGS2 legs, man!), switched provider, waiting for my AT&T number to port to Google Voice. Paying less now for unlimited voice, text, and data. Saving money even after the early termination fee.
The ROM development community is WAY more responsive to bugs, upgrades, and adding features than the carriers. No bloatware and apps I'll never use.
I would suspect that if News sites (CNET or others) posted stories on this problem then that would certainly get AT&T's immediate and serious attention. How do we go about informing these News sites of this?
Log a complaint with http://www.bbb.org/
Someone will contact you from ATT and offer a replacement phone.
I was offered a cheap(.99 cents) samsung phone - i declined and asked for a Galaxy S3.
I talked to them on Monday and got the phone on Wednesday(Can you believe it)
Hope this helps.
Just adding one more to the list of people with this problem. In addition to shutting off in idle mode, and sucking the battery, mine is also overheating.
Frogger27: I'm with you on Shostock3! I love it. That's Jelly Bean, folks. Our S2s are entirely capable of running that OS. There are other good ROMs out there too, I gather. Like I said before, it's worth looking into rooting. Don't be afraid to at least research it. I was intimidated from even doing that, but it wasn't nearly as difficult as I feared, and the phone is *vastly* improved (not to mention no SODs!). And you can even *unroot* your phone to bring it back under warranty condition.
Frankly, I consider this whole debacle a blessing in disguise. If none of this had happened, I wouldn't be enjoying the Shostock ROM.
I'm still 'mad' at AT&T just on principle, though. There must be more to this programming stuff than I know, because I can't imagine it would be difficult at all simply to offer a rollback to 4.0.3 if fixing 4.0.4 is so difficult. And about that: did AT&T not test a number of phones on this version? I have to think that even burning in just 10 phones for a week would have revealed enough problems to postpone publishing. I'm not a programmer, but I've worked closely with many over the years, and I know to a man, or woman, they would be mortified if software they had written had resulted in this kind of snafu. That's likely true of the AT&T crew, but for whatever reason, they're being kept from providing a fix.
Re: Shostock3 - and this development is being done by one guy (Shoman94) with a full-time job, as a hobby!!! And he just underwent neck surgery. No excuse, AT&T.
Not really positive on the new apps, it's been awhile since the initial upgrade. Doesn't really matter. I'm having the same issues again and still getting the same run around from ATT. I just filed a complaint with the BBB. Hopefully this matter gets resolved.
I just signed up to say it is happening to me also. I updated to 4.0.4 last week and it fails to wake up about once a day.
Why is the update to 4.0.4 still available to the Galaxy S2? There clearly is issues with it as reported on this forum. It should have been taken down when it became apparent there was an issue with it. It was released in December. I shouldn't have been able to update to a defective version three months later.
Anduser- The reason AT&T is not doing anything (I GUARANTEE you they aren't doing squat) is because this only affects one model out of the many different models they offer. If the 4.0.4 update broke EVERYONES phone I know for a fact they would have come up with a fix ASAP and porbably had directions to roll back to 4.0.3 in the mean time. Sadly, it's all about the numbers.
I just installed SHOSHOCK based on everyones recomendations. Thought I bricked it, but a phone call to a buddy of mine eho actually works for XDA and he walked me through it. He said Shoshock is one of the best available and will be very pleased with it and will have none of the dreaded SODs
Add another customer who is experiencing this SOD issue. I really liked my GS2 before ICS. I switched from iPhone 3 because I didn't like the Apple method of phasing out support for "legacy" models. It was a brick after 1.5 years. Now, after 1.5 years of Galaxy use, I have another brick of a phone. As a freelancer who depends heavily on cell phone reliability, this situation is completely unacceptable. Missed calls and texts because my phone is locked without my knowledge = missed work. So frustrating. Seriously considering leaving AT&T over this (our family contracts are almost up). Don't know if any of the others are any better though. Plus I'm grandfathered into the unlimited data plan.
I think AT&T just wants us to give up and buy the S3.
Sure, if we can just tolerate the problem for a couple more months until S4 is released, then we can all upgrade to a free S3 for free. That's exactly what the AT&T fat cats are hoping we all are going to do. BTW my solution was to learn to root my phone and install ShoStock3. Unbelievable. Feels like I just got a new S3 for free! As another poster said, this problem turned out to be a blessing in disguise. Take advantage of this issue as a motivating opportunity for you to learn how to root your phone. Free yourselves! Google is your friend. AT&T is not.
Sign up now to post, reply, and join the conversation.
© 2014 AT&T Intellectual Property© 2014 AT&T Intellectual Property link. This link will open a new window All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. AT&T 36USC220506