Hey all,
This thread seems to be a good place to get my own frustration out on the reboot problem. I will add some details so you all might benefit from that.
I have owned my Galaxy S2 for over a year now and have experienced several firmware versions. I ran on 2.3.4 for a while without any big problems. I got a little obsessed by maximizing the batt life so I played around with Juice Defender and Juice plotter and got some good results. Side effect was that I noticed weird behavior immediately since I was focussing on my battery drain and what programs were responsible for that. Juice plotter is very useful here.
What I noticed on that firmware version was that my phone sometimes got into a state that drained the battery quickly. As a reference:
Normal: battery could last 48 hours with moderate use
Charging rate: 25% per hour
Abnormal discharging: 10% per hour with no clear apps causing this (phone idle)
I also noticed during this abnormal drain the phone would get really warm. Not sure if that is the battery or the CPU. I am guessing the CPU.
It seemed like such an episode started when I got a phonecall when my phone was on the charger. Like something went wrong during that combination. A manual reboot usually solved it and battery drain went back to normal.
I accepted this behavior and lived with it for a while.
So, then ICS came about. I waited with the upgrade due to a lot of issues on the web. Thought a little legging behind wouldn;t hurt.
. Finally, I decided to upgrade and did it the clean way: factory reset.
That was quite some work since all my apps were gone, all my settings were gone and I didn't want to re-use any restored settings when they were offered.
After the upgrade, I think it was 4.0.2, I immediately had serious problems with my phone and battery drain. My phone regularly was 'dead' when I tried to use it. I could reboot it after holding the power button for a while (5 - 10 seconds). I am guessing this is hard reboot like any normal PC, usefull when it 'hangs'.
When looking at Juiceplotter, the battery level made huge jumps, where the level changed by 30% within a short time (hour or so) and the phone was off. At least that is what it looks like because Juiceplotter is not logging any information so that part of the graph is unavailable.
I removed the battery as a last resort and... it seemed to solve the problem. My phone ran for a week with normal power behavior.
Soon after I solved this I got 2 other upgrades pushed on my phone and ended up with the current 4.0.4. version. Since then (2 months), the behavior has been erratic in waves. Sometimes it runs fine for several days, sometimes it dies twice a day.
During normal operation the battery drain is very good (=low). ICS definately improved when everything is working as it should. As a benchmark:
Battery lasts 72 hours.
Usage: 5 hours of GPS, 4 short phone calls, regular e-mail check.
JD ultimate settings: ping on 30 minute interval, auto connect WIFI at home and at work, nightschedule 00:00 - 07:00
However, when things go wrong it totally sucks! The behavior is always the same:
- Phone seems dead when pushing the home button or power button
- Long press (5 - 10 sec) of the powerbutton forces a reboot
- The phone feels warm to the touch, some process is draining battery fast (20 - 30 % per hour).
- After the battery is dead, in 1 - 3 hours depending on your starting level, the phone obviously is not warm anymore, does not wake up when long pressing the power button and the only solution is to put it on the charger. This will show a battery level of 1 or 2 % with a warning 'critically low'.
- When looking at Juiceplotter, the graph ends after an 'idle' period where battery drain is very low. Then it starts again at the point you have revived it and there is a huge uncharted drop in battery level.
- When looking at the battery stats of android, there is sometimes an app that jumps out with its battery usage. It is never the same app though and de-installing it does not solve the problem.
My conclusion:
- ICS has a serious bug that is not caused by a clash of old firmware leftovers.
- The bug has been there from the first version of ICS.
- The bug seems to freeze random background processes on the phone and causes the CPU to work overtime and use a lot of power.
- When the battery is not fully depleted, a hard reboot helps (long press power button).
- After the battery is fully drained, only recharging will revive your phone.
- During the 'freeze' period the OS totally 'hangs'. None of the apps are able to log anything anymore and it looks like the phone is turned off.
So no solution from me, maybe some piece of mind that you all are not crazy.