Large Battery Drain on bananacake's kernel (0.4) - Desire Q&A, Help & Troubleshooting

I'm experiencing a very big battery drain when the screen is off for a long time. I just left the phone screen off for 2 hours because I took a nap. When I woke up, the battery went from 60% to 40%. (via Juice Plotter) That was 10%, per hour, while screen off. I did not experience this from the AcesMod v35 original kernel. My SetCPU profile for screenoff was 128-345Mhz, smartass V2. Could this be the problem?
Thanks in advance.

I'll give you the best piece of advice concerning changing CPU frequencies.
.......................................................
Don't.

bortak said:
I'll give you the best piece of advice concerning changing CPU frequencies.
.......................................................
Don't.
Click to expand...
Click to collapse
This.
Deleting setcpu will be a move of your life.

erklat said:
This.
Deleting setcpu will be a move of your life.
Click to expand...
Click to collapse
Can i ask whats wrong with setcpu then?

A) Android manages it's CPU frequencies absolutely fine by itself.
B) By running SetCPU, it constantly needs to monitor your phone for it's state, so it can change the CPU frequency, which will just use more battery.
C) Overclocking your CPU will kill it faster.

Related

[Q] Battery life has me at my wits end! Help please!!!

Ok. So I have a G2, with CM7R4. I have SetCPU with all sorts of profiles and JuiceDefender on Extreme. I still can't get more than 6-7 hours out of my battery. I take it off the charger before I leave for work, and before I even clock out, the phone is dead. This is whith even minimal usage. The thing is, with minimal and heavy use, I get about the same battery life. What could possibly be causing this?
I went in to Battery Stats, and Cell Standby was at 60% or more, but my browser (which I've been using for 3 or so hours, and a game I've been playing for about the same, are both only at 2%. I went in to Spare Parts, and it showed the phone has been running constantly for about 3 hours with no sleep, even though I've shut the screen off and stopped using it completely numerous times in the last 3 hours.
There has got to be something I can do. How are people getting 2 days uptime when I can't even get 8 hours? Someone help please!
Edit: Thank you everyone for your suggestions! I drained my battery, wiped battery stats, removed a bunch of SetCPU profiles, and installed Green Power to regulate my data usage. I've seen no decline in functionality, but I have already begun to see a vast battery life improvement.
Stop using setcpu.
Sent from my G2 running Cyanogenmod 7.
Do you have a reason for this? I was told to start using SetCPU the last time I brought this issue up.
What are you setCPU profiles?
Oh yeah, if you made your profiles all whack, the cpu will be constantly running. Specifically if you've set a performance governor anywhere. The more you mess with the profile creator, the more battery life you can free up easiest way to learn is to play around with the governors from time to time.
Sent from my HTC Vision using XDA Premium App
Kevin001111 said:
What are you setCPU profiles?
Click to expand...
Click to collapse
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Have you tried wiping battery stats in ClockworkMod recovery?
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
SnowOokami said:
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App
ohshootrawr said:
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery. Just let your navigation on till it's empty (leave the screen on too) it will go off, you will be able to boot the phone once or twice after that, so it's not a 100% drain, boot in recovery mode then delete the battery stats, reboot and put the charger in it. That did the trick for me. Hopefully it works for you too
I guess you could do it the other way around, charge the phone completely, wipe the battery stats, drain it till it goes off and reboot. That takes a bit longer I guess.
You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...
Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Click to expand...
Click to collapse
That's why I have the temp. profile. I basically have to have my phone in a charger at all times, otherwise it dies. So I have it set to run at max so my games and whatnot work well.
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
Thanks! I'll try this today, because my phone will undoubtedly die before I get home from work. I'd love to get 28hrs use. Last night, I got 7h30m30s on battery. That's good compared to what I usually get, but it left me without a phone during the deadest part of my shift.
You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...
Click to expand...
Click to collapse
Thanks! I'll look and see if this is causing it. I wouldn't've turned it on, but maybe it's on by default?
You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated
Since I've got the phone, I've only used CM, but I have used at least 5 different versions. I'm working on killing it right now. It'll be dead much earlier than usual with all the use its's getting, and I was smart enough to bring a charger so I can charge it as soon as it dies and gets recalibrated.
Let me know if it works for you!
detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
I had a setup similar to this (many different profiles) and I had awful battery drain. I read in a thread somewhere here that it was setcpu that was the culprit of the excessive drain because having many profiles has it constantly using cpu power.
I have since switched my default to 1017/245 on demand and now I only use a screen off profile at 245/245. Since making that change, my battery life improved significantly (25-30% improvement)
I don't do anything that requires the full 1.5ghz on my phone which is why I now run at 1ghz but definitely feel that the setcpu profiles cause some major drainage...
SnowOokami said:
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery.
Click to expand...
Click to collapse
Its unlikely, but possible your battery will not take a charge after you discharge the battery too low (safety circuit does not properly kick in). I've seen this problem crop up (pretty occasionally) from time to time back on the Touch Pro 2 forums, and have seen it happen here to a couple people on the Vision as well.
The battery meter is not all that accurate, anyway. Most of what you suggest if fine: to delete battery stats, let it charge to full, but then drain to 10% or so. You aren't really gaining much by doing that versus totally empty, and its safer.
TrueYears said:
You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated
Click to expand...
Click to collapse
There is no such thing as calibrating a Li-ion battery. You are calibrating the battery meter on the phone.

Downclock CPU to save battery?

I`m not playing games or running CPU demanding apps, just phone calls/sms/bit of non flash web.
Is it possible to downclock CPU to increase usage(save battery)?
Or CPU doesn`t eat that much battery and downclocking would have very little effect on battery?
With a rooted device, you might want to try CPU Master Free. You will be able to decrease the clock speed.
Also, you could try to UnderVolt your CPU. Search for your phone model UV in te forums.
Min frequency is 350MHz so if your not doing anything it will be idling at 350mhz
rbs_uk said:
I`m not playing games or running CPU demanding apps, just phone calls/sms/bit of non flash web.
Is it possible to downclock CPU to increase usage(save battery)?
Or CPU doesn`t eat that much battery and downclocking would have very little effect on battery?
Click to expand...
Click to collapse
It does help you save precious battery life.
You can download the best app for overclock, SetCpu, from the XDA site, it's free for XDA members:
http://forum.xda-developers.com/showthread.php?t=505419
How much more battery life I could get by downclocking CPU? Any feedback from people who have tried such thing?
On my gn i find the screen to be the biggest user of thr battery power so underclocking prob would have little use, ohh and iirc the phone uses race to idle which procesess overything as fast as possible to get the cpu back it low power idle state.
rbs_uk said:
How much more battery life I could get by downclocking CPU? Any feedback from people who have tried such thing?
Click to expand...
Click to collapse
I normally charge my phone before go to sleep, I don't overcharging it during the night.
My SetCpu frequencies are Min 19/ 692 Max.
I am connected through 3G data ALL day and I am always online on Skype, I use my phone a lot, browsing, games, and phone call, and I can tell you, thanks to the undervolting, I got home at night with 50% juice remaining.
Without SetCpu, I would have 10/15% left at night...
yukinok25, that`s huge improvement, I`ll try it definitely.
rbs_uk said:
yukinok25, that`s huge improvement, I`ll try it definitely.
Click to expand...
Click to collapse
And...this is why we all love XDA...
Remember that battery life also depends on Radio version and kernel installed.
I remember there was a topic about "How to charge your phone first time" - cannot find it any more.
rbs_uk said:
I remember there was a topic about "How to charge your phone first time" - cannot find it any more.
Click to expand...
Click to collapse
If you mean after you just bought it, Its enough to let it fully discharge twice, without charging it, in between this two circles.
Anyway with nowdays Li-ion battery, you won't really need to this so anymore, since the lifespan of battery start to decrease from the moment that they left the production factory.
yukinok25 said:
If you mean after you just bought it, Its enough to let it fully discharge twice, without charging it, in between this two circles.
Click to expand...
Click to collapse
Yes.
Discharge twice without charging - hmm... once its dead its dead. I didn`t get it
rbs_uk said:
Yes.
Discharge twice without charging - hmm... once its dead its dead. I didn`t get it
Click to expand...
Click to collapse
Sorry for my english.
I meant during your usage time (during the day) don't charge your phone at all. let it discharge fully twice.
yukinok25 said:
Sorry for my english.
I meant during your usage time (during the day) don't charge your phone at all. let it discharge fully twice.
Click to expand...
Click to collapse
Ok, thanks.
Anytime mate!
Ive read good results on using juice defender app to prolong battery life:
http://android.modaco.com/topic/349071-galaxy-nexus-battery-drain-issues/
L60N said:
Ive read good results on using juice defender app to prolong battery life:
http://android.modaco.com/topic/349071-galaxy-nexus-battery-drain-issues/
Click to expand...
Click to collapse
I would not recommend juicedefender. Doesn't do anything at all. The only thing I notice is that nu wi-fi turned itself off when it shouldn't.
You could try AutomateIt. You can set up your own actions.
Ex: Within 100 meters of school > Sound off

[Q] Can massive battery drain be from undervolting?

I've been fooling around with undervolting.
When setting them -25mV nothing much seems to happen, no gain or loss. But when I set them -50mV or lower, I get a massive battery drain.
Is this a normal problem?
I don't crash or anything, the battery just doesn't last.
The very act of undervolting should be saving you battery, because undervolting makes it so that you use less energy at each clock speed.
Masters2150 said:
I've been fooling around with undervolting.
When setting them -25mV nothing much seems to happen, no gain or loss. But when I set them -50mV or lower, I get a massive battery drain.
Is this a normal problem?
I don't crash or anything, the battery just doesn't last.
Click to expand...
Click to collapse
It can, if services start crashing in the background and it voids deep sleep mode. You'd better just leave it default or try to nip off v's in the maximum freq department.

[Q] [CM7] How can I figure out why my battery is draining?

I got pretty crap battery life yesterday (see attachments). I plugged in my phone in the afternoon so it was fully charged when I left work in the evening, and then I only used the phone a little bit before I went to bed.
From 6 pm to 11 pm (when I went to bed) it drained from 100% to about 55%. Didn't plug it in overnight. When I got up this morning, it was at 17%. Wifi was on, airplane mode was not on, but I didn't use the phone at all and it probably should have just gone to sleep, right?
Anyway, this was only my second day of using CM7 instead of CM9. I had been on CM9 for a week or so before I decided to go back to CM7 for the battery life. It's weird, I've searched for and read several of the battery life posts here in the Q&A section and everyone seems to recommend CM7 for battery life, but in my case it didn't work out so well. There must be something going on - how can I figure this out?
I'm getting great life from cm7! You may want to wipe all caches, and battery stats, and reflash the Rom on top. Then apply v6 supercharger, kak tweaks..
Further more download better battery stats, Google search it, and see what apps have high partial wake times
Sent from my SPH-D700 using Tapatalk 2
omair2005 said:
I'm getting great life from cm7! You may want to wipe all caches, and battery stats, and reflash the Rom on top. Then apply v6 supercharger, kak tweaks..
Further more download better battery stats, Google search it, and see what apps have high partial wake times
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
v6 supercharger, tweaks, etc... isnt required at all.
He needs to show us all his battery stats from Better Battery Stats, and his CPU freq Table from Voltage Control and the I/0 Scheduler and Cpu Governor and What kernel is he using
My kernel is listed as 2.6.35.7 which I believe is an AOSP kernel
I don't own Better Battery Stats
Just installed Voltage Control... Min 100 MHz, max 1000 MHz, I/O scheduler is sio, CPU governor is ondemand, and this is after running the V6 and KAK scripts. I'm going to see how my battery holds up today.
Try with better battery stats app
Sent from my Desire using XDA
you can also use cpu spy to find out if your phone is actually going into deep sleep or if it's running @ something higher.
Mama Luigi said:
My kernel is listed as 2.6.35.7 which I believe is an AOSP kernel
I don't own Better Battery Stats
Just installed Voltage Control... Min 100 MHz, max 1000 MHz, I/O scheduler is sio, CPU governor is ondemand, and this is after running the V6 and KAK scripts. I'm going to see how my battery holds up today.
Click to expand...
Click to collapse
BBS is free and is on XDA, Try conservative for your CPU governor that'll help and if you use CPU Spy as mention below me that'll show the amount of time each freq. is on
Ah, thanks for pointing that out!
I'm going to take some time to figure out how to interpret all this. CPU Spy seems pretty straightforward though. It is reporting that the CPU has gone into deep sleep most of the time it's been unplugged, so that can't be the problem. I did go into Voltage Control and change the CPU governor from ondemand to conservative; hopefully that helps.
For Better Battery Stats I'm going through the official thread and just trying to compare my results against what people are saying there. So far the biggest potential culprit is GTALK_ASYNC_CONN, which has the largest duration of partial wakelocks at 2m22s. Behind that is Wimax (obviously having that on is gonna drain my battery; I don't normally use it but today I have been) and then *network-location* with 1m14s. I'm not sure I really need to post a full dump although if anyone really wants to look it over I could.
Anyway thanks for all the help guys.
Mama Luigi said:
Ah, thanks for pointing that out!
I'm going to take some time to figure out how to interpret all this. CPU Spy seems pretty straightforward though. It is reporting that the CPU has gone into deep sleep most of the time it's been unplugged, so that can't be the problem. I did go into Voltage Control and change the CPU governor from ondemand to conservative; hopefully that helps.
For Better Battery Stats I'm going through the official thread and just trying to compare my results against what people are saying there. So far the biggest potential culprit is GTALK_ASYNC_CONN, which has the largest duration of partial wakelocks at 2m22s. Behind that is Wimax (obviously having that on is gonna drain my battery; I don't normally use it but today I have been) and then *network-location* with 1m14s. I'm not sure I really need to post a full dump although if anyone really wants to look it over I could.
Anyway thanks for all the help guys.
Click to expand...
Click to collapse
In BBB look at since unplugged and kernel wakelocks do you have a "mmc_delayed_work" mine is high that affects battery life too
Slightly different situation now. A couple days ago I switched to an ICS rom, this time AOKP. Things seemed to be fine but this afternoon my battery absolutely tanked while I wasn't using the phone - the standard battery interface showed that the phone did not sleep during that time even though it was in my pocket, and Better Battery Stats showed a huge amount (over 3 hours) of kernel wakelocks from "sec_jack." Know what could be causing that?
EDIT: I should add, using the standard battery screen, it has simply lumped in whatever is now draining my battery into "Android System." It showed a keep-awake time of around 20 minutes when the total time unplugged was 25 minutes. I tweaked a few things, turned off AOKP's weather service and made sure Facebook wasn't pulling background data, and restarted my phone. I'll have to see how it goes.
Solved! I turned off the weather service built into AOKP last night. This morning, the sec_jack wakelocks were gone and my battery had only gone down by a couple % overnight.

Underclocking and Battery life?

hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
hshaikh said:
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
Click to expand...
Click to collapse
I suggest to decrease your max CPU until you feel it affects performance too much. You can also try switching to a governor less aggressive than interactive (try ondemand).
Don't expect magic though. I've played with decreasing max CPU clock, max CPU screen off, governor settings etc with three different kernels. Gathered stats for at least one week each time. Never noticed a difference large enough to actually matter to me. For maximizing battery life, you can gain more by hunting apps that cause a lot of (partial) wakelocks and alarms, and use low screen brightness.
hshaikh said:
and screen off max is 384.
with all that information, what do you suggest?
Click to expand...
Click to collapse
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Darunion said:
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Click to expand...
Click to collapse
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Petrovski80 said:
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Click to expand...
Click to collapse
you are correct. there is a magic middle ground because power consumption doesnt scale in a linear way. but finding that spot would take massive testing and even getting to the center, would still probably only gain about 10-15mins average use on a battery charge :/
bk201doesntexist said:
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
Click to expand...
Click to collapse
what speed show i set to max when screen is off.
did you read anything that Darunion and Petrovski80 wrote? I keep mine at it's max, i don't care, i don't live in the woods with no electricity.
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
hshaikh said:
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
Click to expand...
Click to collapse
Exactly. I get similar performance.
Sent from my Galaxy Nexus using Tapatalk 2

Categories

Resources