battery life is only a few hours!

[mack]

LI flashed gummy nex with 100% battery. My phone will jump around. Right now it's at 46% and its only been off charge for about two hours max. I have not been using it much at all. What gives? Sometimes it will charge in 30 minutes, other times it will charge real slow. I also noticed that if I use it while charging it my battery won't charge.

I did everything. I wiped battery stats. Reinstalled my rom completely. Discharge to 0 and full charge to 100%

I am posting from my phone now, when started it was at 46 now I am at 35%...the first ten minutes off charge it went from 100 to 90 very quickly. Help??

 

[mack]

This is a screen shot..

 

[willstilson]

Something is keeping it awake. Check your data to see if it has increased rapidly. Perhaps something is downloading constantly. I saw in another thread someone had a similar issue, and it turned out to be and Exchange Server incompatibility, causing constant downloading.

 

[mack]

Using what app?

 

[zkSharks]

Using what app?

In the Battery section of Settings, press on the top five or so apps shown as using your battery up. Check the awake time listed for each of them. If the awake time seems unusually high compared to the total time your phone has been unplugged, post it here.

As for checking data usage, you can do that in Settings > Data Usage. See if any apps have been using data repeatedly when you wouldn't expect them to be.

 

[mack]

Everything seems okay. Except android system..

 

[greydarrah]

Why don't you try flashing another ROM and see how it does. Kang, Codename, Bugless...they all run great. Also, have you tried posting this where ever this ROM's main thread exist? I would thing those people would be in a better position to help.

 

[twindragons187]

a rom is only as good as the kernel its using....have you thought about using Franco's kernel?Try it and use the hotplug option (shuts down 1cpu when screen off). Just do a back up before u flash that way if u have to go back, u can.

 

[Nakrohtap]

I am running Franco 14.4 with hotplug enabled and have seen much improvement in battery life. Also, I heard for some reason that setting your minimum to 700 mhz instead of 350 saves battery from draining quick as well. I just downloaded CPU spy and noticed only 2 slots being used.

Sent from my Galaxy Nexus using Tapatalk

 

[mack]

It still is getting really bad battery life with hotplug. It's 11PM and I've had since 4 PM and it's at 3% with minor usage. I noticed it jumps from 100% to 91% almost instantly, there's no way the battery can be bad?

 

[zero neck]

Did you do a clean install (wipe data, cache, and dalvik cache)?
If not, install it again or a different rom if you choose thru recovery mode while wiping those above things.

If you did wipe, you can go to settings>applications>running apps> and force stop android system or whatever it was that was running endlessly.
After you do that, see if it turns back on and drains your battery like crazy this time.

 

[mack]

Did you do a clean install (wipe data, cache, and dalvik cache)?
If not, install it again or a different rom if you choose thru recovery mode while wiping those above things.

If you did wipe, you can go to settings>applications>running apps> and force stop android system or whatever it was that was running endlessly.
After you do that, see if it turns back on and drains your battery like crazy this time.

Yes, I did all that. I wiped everything - Data, Cache, Dalvik, Battery Stats. I even installed with a 100% battery. I'll keep messing with it, if it doesn't improve I'll do a fresh wipe.

On my Fascinate, I was able to Odin my phone back to stock (with PIT file). After I did that, I was able to reflash it. Is this possible on the nexus?

That fixed my fascinate perfectly and the battery idles for 3 almost 4 days.

 

[zero neck]

Did you quit the running process? android services or whatever?
i ask bc i had a similar thing happen, drain and phone got real hot, but i quit the process and it stopped happening. -- although, and this goes to my next suggestion -- the next day instead of dealing with the issue i just restored a nandroid from the previous build (happened to be AOKP b20) and everything is ok.

So what i would do, if quitting the process doesnt work out, is instead of reverting to stock - which i dont think you need to do unless you feel like it - just either restore a nand or wipe cache, data, dalvik, and format /system, then flash a different rom or an earlier build of the rom you're on.
(side note - if you do want to restore to stock, you certainly can. there are threads on how to do that here at ac and also at rootzwiki and xda)

as i dont think there is any reason that this would be solvable only by reverting to stock, i would try a restore to a safe rom first, or a clean install of a new rom.
i think the issue is probably your rom as opposed to kernel but i could be mistaken about that:
in the event that it's the kernel, there are many choices, and on top of that, i've had great results with the stock kernel with the custom roms - although i also have had good results with franco's personally.
additionally, just for perspective, i dont use hotplug, as my battery life is very good without it, and i dont see any reason to go crazy over battery life with my schedule and use..

anyway- good luck whatever route you try now.

 

[mack]

Android System sounds like something critical? I've made changes. If it doesn't fix it I will fully wipe and reinstall my ROM and KERNEL. I'm using Gummy.

 

[zero neck]

Android System sounds like something critical? I've made changes. If it doesn't fix it I will fully wipe and reinstall my ROM and KERNEL. I'm using Gummy.

True I just mean, if you force stop it from running, it might fix the bug and then start running normal again when it restarts.
Worst case, you boot loop, battery pull, and boot straight to recovery to restore or clean flash a new rom.

But either way, gl and let us know how it goes.

Edit: on second thought I would just do what u said, clean install. Probably not worth the other trouble.

 

[mack]

True I just mean, if you force stop it from running, it might fix the bug and then start running normal again when it restarts.
Worst case, you boot loop, battery pull, and boot straight to recovery to restore or clean flash a new rom.

But either way, gl and let us know how it goes.

Edit: on second thought I would just do what u said, clean install. Probably not worth the other trouble.

I haven't done it, but I disabled a few things - still issues though. I'll probably do it tonight.