[International / GSM] Battery life dropped after root???

[djcs219]

I finally took the plunge and rooted my GNEX today. I love the fact that it is now free but one thing I have noticed, my battery life has dropped off significantly. Has anyone else had this happen?

I have the exact same set up that I had before I rooted. I know that my phone resetted so do I just have to cycle the battery again? Just wondering. If anyone could help me with this or provide suggestions I would appreciate it. Just an fyi, my battery life was at least 7hours plus with 4G on the whole time on an extended battery.

Thanks!!!

 

[AndroidAdvntge]

Some roms have different kernels which will fluctuate your battery life. If you want, I have a guide to improving your battery life.
Android Battery Life Optimization Guide ~ Android Advantage
That should do you some good!
Hope this helped.

 

[djcs219]

I appreciate it but I do all these already thanks. I am just curious to see if anyone has had a similar situation and can offer their resolutions...

 

[scary alien]

If all you did was root (i.e., install the su binary and the Superuser.apk app and optionally, ClockworkMod custom recovery), then you would/should have noticed NO differences in either battery life or any behavior whatsoever unless you install or invoked an app that requests and uses root (superuser) privileges.

These are all passive things that are not active until called-upon.

If you installed a custom ROM, well then, all bets are off .

But the process of rooting won't do anything at all unless you explicitly do or allow something to use your new root powers.

Cheers!

 

[djcs219]

If all you did was root (i.e., install the su binary and the Superuser.apk app and optionally, ClockworkMod custom recovery), then you would/should have noticed NO differences in either battery life or any behavior whatsoever unless you install or invoked an app that requests and uses root (superuser) privileges.

These are all passive things that are not active until called-upon.

If you installed a custom ROM, well then, all bets are off .

But the process of rooting won't do anything at all unless you explicitly do or allow something to use your new root powers.

Cheers!

All I did was follow the superboot method and that was it and all of a sudden its significantly dropped...any ideas as to why?

 

[scary alien]

All I did was follow the superboot method and that was it and all of a sudden its significantly dropped...any ideas as to why?

Sorry for the delay in the reply...

Well, the Superboot method simply soft-boots an insecure boot image which then runs a script via init.rc to install the su program and the Superuser.apk app, so its really no different from the other root methods.

You're not even flashing that boot image, so the only new stuff you are getting would be the su binary and the Superuser.apk file which don't come into play unless an app requests root.

Not sure what else could be going on, but I just wanted to allay your fears that it might be root-related.

 

[djcs219]

Sorry for the delay in the reply...

Well, the Superboot method simply soft-boots an insecure boot image which then runs a script via init.rc to install the su program and the Superuser.apk app, so its really no different from the other root methods.

You're not even flashing that boot image, so the only new stuff you are getting would be the su binary and the Superuser.apk file which don't come into play unless an app requests root.

Not sure what else could be going on, but I just wanted to allay your fears that it might be root-related.

Strange that this would happen but at least you don't think it is the root. I am going to just drain the battery and charge it while in the phone and go from there. It worked when I first got the phone so we will see...thanks.

 

[djcs219]

Sorry for the delay in the reply...

Well, the Superboot method simply soft-boots an insecure boot image which then runs a script via init.rc to install the su program and the Superuser.apk app, so its really no different from the other root methods.

You're not even flashing that boot image, so the only new stuff you are getting would be the su binary and the Superuser.apk file which don't come into play unless an app requests root.

Not sure what else could be going on, but I just wanted to allay your fears that it might be root-related.

Still experiencing the worst battery life ever since I rooted. I'm running Go launcher. I didn't have issues with it before but maybe now? Any suggestions? In getting maybe 4 hours max out of an extended battery when before was at least 8 hours.

 

[scary alien]

Still experiencing the worst battery life ever since I rooted. I'm running Go launcher. I didn't have issues with it before but maybe now? Any suggestions? In getting maybe 4 hours max out of an extended battery when before was at least 8 hours.

Not really sure...do you have any apps that are doing a lot of syncing?

Have you checked the Settings -> Battery display to see what's been using your battery?

Mine shows:

Screen: 63%
Android OS: 15%
Phone idle: 9%
Cell standby: 8%
Market: 2%
Mediaserver: 2%
WiFi: 2%
Android System: 2%

Also, you could install something like System Panel or other performance monitoring apps to see what might be using the CPU (it might also be the radio, so I don't think that will be obvious in an app display).

Here's a thread that one of our Guides, colchiro posted way back when in the Droid X section about how to help identify battery eating issues:

http://androidforums.com/droid-x-support-troubleshooting/378403-those-you-complaining-about-awful-battery-life.html

He's got some great tips in there that might help.

 

[dimitrisg]

I installed Juice Defender yesterday because my battery was draining fast. Juice Defender worked wonders today! After an 8 hour shift at work it still has 67% battery left. Would have been far less than that before. Of course it has only been the first day using it, but that is great so far. I hope it continues doing this well.

Update: After a full day of using my GNEX running Juice Defender, I still had 30% charge before bedtime. It has never done that well in a day. I did have it plugged into the computer a few times to transfer files, but was not that long each time.
So far I am sold on this application. I didnt want to try it because I felt I had followed all the tips here and that was all I could do, but glad I tried it. (I am using the Juice Defender Ultimate)

 

[scary alien]

I installed Juice Defender yesterday because my battery was draining fast. Juice Defender worked wonders today! After an 8 hour shift at work it still has 67% battery left. Would have been far less than that before. Of course it has only been the first day using it, but that is great so far. I hope it continues doing this well.

Never used that particular app, but thank you for the information!

Welcome to the AndroidForums, dimitrisg.

Cheers!

 

[djcs219]

Not really sure...do you have any apps that are doing a lot of syncing?

Have you checked the Settings -> Battery display to see what's been using your battery?

Mine shows:

Screen: 63%
Android OS: 15%
Phone idle: 9%
Cell standby: 8%
Market: 2%
Mediaserver: 2%
WiFi: 2%
Android System: 2%

Also, you could install something like System Panel or other performance monitoring apps to see what might be using the CPU (it might also be the radio, so I don't think that will be obvious in an app display).

Here's a thread that one of our Guides, colchiro posted way back when in the Droid X section about how to help identify battery eating issues:

http://androidforums.com/droid-x-support-troubleshooting/378403-those-you-complaining-about-awful-battery-life.html

He's got some great tips in there that might help.

Ok so I did a factory reset and still getting horrible battery life.

Here is what my battery manager break down shows:

91% discharging
screen 56%
android OS 21%
Phone 7%
Android system 5%
Media server 4%
cell standby 3%
phone idle 3%
android core apps 2%
handcent sms 2%

I don't get how I could just have charged this extended battery and now it is down 10% after only 22mins. Is this normal? I never had this issue before.

 

[scary alien]

Ok so I did a factory reset and still getting horrible battery life.

Here is what my battery manager break down shows:

91% discharging
screen 56%
android OS 21%
Phone 7%
Android system 5%
Media server 4%
cell standby 3%
phone idle 3%
android core apps 2%
handcent sms 2%

I don't get how I could just have charged this extended battery and now it is down 10% after only 22mins. Is this normal? I never had this issue before.

I have the extended battery, too (i.e., the one that's only slightly bigger--don't know if there's a monster one out there or not).

It was in from when the device was first installed, but I have switched back to the standard battery for a while before, too, so I don't think the issue you are having would be battery statistics related. Especially if you are seeing a full charge and then have it drop so quickly and precipitously...

Your readings aren't too different from mine... Did you install CPU Spy or Watchdog to see what might be going on?

 

[djcs219]

I have the extended battery, too (i.e., the one that's only slightly bigger--don't know if there's a monster one out there or not).

It was in from when the device was first installed, but I have switched back to the standard battery for a while before, too, so I don't think the issue you are having would be battery statistics related. Especially if you are seeing a full charge and then have it drop so quickly and precipitously...

Your readings aren't too different from mine... Did you install [COLOR="Blue"]CPU Spy[/COLOR] or [COLOR="blue"]Watchdog [/COLOR]to see what might be going on?

Alien, I installed cpuspy and the majority of use is at 350 mhz at 59% and the next is deep sleep at 22%. Im not sure what to make of it but I assume it should be using the higher end of the processor and it's not. Any help or suggestions? Thank you.

 

[scary alien]

Alien, I installed cpuspy and the majority of use is at 350 mhz at 59% and the next is deep sleep at 22%. Im not sure what to make of it but I assume it should be using the higher end of the processor and it's not. Any help or suggestions? Thank you.

Well, not other than the Watchdog app...that might find if you have a culprit that's hogging things... It seems like a nice little app that could alert you when it finds something that's using a lot of CPU (I don't know too much about it other than that Colchiro recommended it in his battery life thread).

Other than that, I'm not sure...

 

[djcs219]

Well, not other than the Watchdog app...that might find if you have a culprit that's hogging things... It seems like a nice little app that could alert you when it finds something that's using a lot of CPU (I don't know too much about it other than that Colchiro recommended it in his battery life thread).

Other than that, I'm not sure...

Well I got the watchdog app and only 13.6% of apps running in the background so I don't get what is draining my battery. I think I should unroot it maybe keep it that way because ever since then I've had this problem.

 

[dimitrisg]

Well I got the watchdog app and only 13.6% of apps running in the background so I don't get what is draining my battery. I think I should unroot it maybe keep it that way because ever since then I've had this problem.

Not sure what method you used rooting, but I am unlocked and rooted with a Verizon GNEX also and did not notice any difference at all in power consumption. I have the stock ROM. It is actually the 2nd handset I have had and both were rooted the same way.
Sounds strange though. I hope you figure it out.

 

[djcs219]

Not sure what method you used rooting, but I am unlocked and rooted with a Verizon GNEX also and did not notice any difference at all in power consumption. I have the stock ROM. It is actually the 2nd handset I have had and both were rooted the same way.
Sounds strange though. I hope you figure it out.

I used the fastboot method. What method did you use? I feel like I should go all the way back to stock and start over. I tried to calibrate the battery but nothing. Im honestly lost as how to fix it.

 

[WalmartSecurity]

Does the full-wipe when unlocking the bootloader clear the battery stats? If so that may explain it because your battery calibration is off...


if not, then I'm not sure. It shouldn't have any effect.

 

[scary alien]

Does the full-wipe when unlocking the bootloader clear the battery stats? If so that may explain it because your battery calibration is off...


if not, then I'm not sure. It shouldn't have any effect.

Yeah, I don't know about that...

It would have (or would still be) interesting to just let the device run, even if it "says" it low to see how long it lasts...certainly, even with a full (extended) battery, you shouldn't be able to drain it just a few hours. If it truly does (and can't be explained by out-of-sync stats), then perhaps its really an issue with the battery or the device?

I know the OP thought that possibly installing root might be the cause of the drain, but there are so many rooted folks out there, that just installing the root apps in and of itself causing a battery drain would certainly have already been seen by a lot of people (on lots of devices, not just the GNex).

 

[djcs219]

I think I finally got it. Searched rooting changed bettery life on Google and found that in fact the battery needed to be calibrated. I downloaded that battery calibration tool for free in the market and it has worked. The only thing I am curious of now is whether I will have to calibrate each battery individually.

 

[dimitrisg]

I think I finally got it. Searched rooting changed bettery life on Google and found that in fact the battery needed to be calibrated. I downloaded that battery calibration tool for free in the market and it has worked. The only thing I am curious of now is whether I will have to calibrate each battery individually.

Good to know what the problem ended up being. Thanks for the update.

 

[scary alien]

I think I finally got it. Searched rooting changed bettery life on Google and found that in fact the battery needed to be calibrated. I downloaded that battery calibration tool for free in the market and it has worked. The only thing I am curious of now is whether I will have to calibrate each battery individually.

Calibrating the battery statistics is what is actually going on--there's nothing being done to the actual battery itself.

Android keeps statistics / information about the state of your currently installed battery and uses that information to calculate and report back to you the percentage charged, etc. When you install a different battery that has a different charging level than what was installed before, Android has to relearn at what rate the new one drains, charges, etc.