Weird battery drain issue

[McBowflex]

Hello all,

Not sure if anyone else has ran into this, but my phone has done something pretty funny with the battery twice now. The first time was when I was leaving work I noticed my battery seemed to die, which was believable because I had done 2.5 hours of OT that day but when I got in my car and plugged the phone it and booted it up it said it was already at 51% battery. Now this morning I unplugged my charger around 5:30am when I woke up and left it unplugged while I went back to sleep to enjoy my day off. When I woke up at 10am my phone wouldn't power on. So again I plugged it in, walked away for a few minutes and came back to see the phone was reporting 40%+ battery life. The first time this happened was on the stock standard battery, and this second time was with my new extended battery.

[Ads]

[KneeDragr]

Hmm, maybe do that thing where you run it till it dies, then pull the battery out for 5 minutes, put it back in and boot. Repeat that process until it no longer boots. Then leave overnight on a slow charge, like from a computer.

I did that with my Fascinate and it went from needing a charge every 5 days to every 7 days. Im at 3 days, 2 hours right now, and 71% remaining, meaning I might beat my all time record of 8 days 12 hours!

[BayouFlyFisher]

It sounds like you have gotten the "Keep Awake" bug. You can confirm this by checking the Settings/Battery menu to note the total battery time and then press on the Android OS line and note the Keep Awake time. Then let the phone sit for an hour or so and recheck those readings. The Keep Awake time should only go up by a minute or so if the phone is not experiencing the bug. If it is though, the Keep Awake time will go up by anything from 10 minutes to 40 minutes.

More info:

As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.

In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.

There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.

I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.

Ultimate fix for me was the installation of a custom rom and kernel, but I know that isn't for everyone.

Good luck

[KneeDragr]

It sounds like you have gotten the "Keep Awake" bug. You can confirm this by checking the Settings/Battery menu to note the total battery time and then press on the Android OS line and note the Keep Awake time. Then let the phone sit for an hour or so and recheck those readings. The Keep Awake time should only go up by a minute or so if the phone is not experiencing the bug. If it is though, the Keep Awake time will go up by anything from 10 minutes to 40 minutes.

More info:

As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.

In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.

There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.

I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.

Ultimate fix for me was the installation of a custom rom and kernel, but I know that isn't for everyone.

Good luck

Do you still turn the screen off with the power button all the time, or did you stop doing this when you heard about the bug?

[cynkrzy]

Hello all,

Not sure if anyone else has ran into this, but my phone has done something pretty funny with the battery twice now. The first time was when I was leaving work I noticed my battery seemed to die, which was believable because I had done 2.5 hours of OT that day but when I got in my car and plugged the phone it and booted it up it said it was already at 51% battery. Now this morning I unplugged my charger around 5:30am when I woke up and left it unplugged while I went back to sleep to enjoy my day off. When I woke up at 10am my phone wouldn't power on. So again I plugged it in, walked away for a few minutes and came back to see the phone was reporting 40%+ battery life. The first time this happened was on the stock standard battery, and this second time was with my new extended battery.

Are you running stock ICS or are you running a ROM &/or Kernel ?

[McBowflex]

Well I definitely always use the power button to lock the phone so I will test that out once the battery goes dead again. Right now I'm still totally stock. I haven't had nearly enough time yet to do all of the necessary reading to flash another rom yet. Ma Bell has got me working about 8 hours of OT a week, and its a 30 mile drive to an from work. So spare time isn't something I have a lot of right now. I've attached both the screen shot of my battery usage, and the details of Android OS battery usage
.Screenshot_2012-01-20-13-15-56.jpgScreenshot_2012-01-20-13-16-09.jpg

[Pure]

How do I disable maps ... I can't find it and I'm, tired of it being in my recent... I haven't used it

GNex tappin' from da' frozen north!

[cynkrzy]

How do I disable maps ... I can't find it and I'm, tired of it being in my recent... I haven't used it

GNex tappin' from da' frozen north!

The reason it shows up is Google Location Services, is a process that get's launched from Within Maps. If you were to disable Location Services in settings it probably wouldn't start.

[Pure]

That's easy enough, I'll try it

GNex tappin' from da' frozen north!

[Mujibar]

Alternatively, go into Settings, Apps. Hit the ALL tab and scroll down to Maps. Tap it and uninstall the update. That should roll it back to the version of the application that shipped with the phone.

Don't know if that'll work for this issue, but Maps only started being persistent for me after an update.

Tap'd from my GNex