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.
Related
I rooted my incredible about 2 weeks ago, and after jumping around from rom to rom, but finally settled on cm7. 1rc1. At first battery life was great, I could finally get through a full day of normal use. I'm running the stock kernel, conservative governor, 998/245, and a screen off profile of 384/245, and also on the conservative governor. Then I read something about wiping battery stats yielding better battery life, and so I looked up exactly how to do it, and now my battery life went way down. Can't get close to getting a full days use out of it anymore.
Sent from my ADR6350 using Tapatalk
cthorson910 said:
I rooted my incredible about 2 weeks ago, and after jumping around from rom to rom, but finally settled on cm7. 1rc1. At first battery life was great, I could finally get through a full day of normal use. I'm running the stock kernel, conservative governor, 998/245, and a screen off profile of 384/245, and also on the conservative governor. Then I read something about wiping battery stats yielding better battery life, and so I looked up exactly how to do it, and now my battery life went way down. Can't get close to getting a full days use out of it anymore.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
How did you do it? Maybe you did it wrong. Also it DOES take a couple days for it to fully re-calibrate, so give it a few days too if you haven't.
I charged the battery fully with it powered on. Then turned the device off and plugged it back in and waited for the light to turn green again. Then I booted it into recovery, and clicked wipe battery stats, and re booted the phone. Once it booted up I unplugged it and used it normally all day until the battery died and the phone shut itself off. Once I did that I plugged it into the charger and let it fully charge.
Sent from my ADR6350 using Tapatalk
Will do when I get home, thanks
Sent from my ADR6350 using Tapatalk
cthorson910 said:
I charged the battery fully with it powered on. Then turned the device off and plugged it back in and waited for the light to turn green again. Then I booted it into recovery, and clicked wipe battery stats, and re booted the phone. Once it booted up I unplugged it and used it normally all day until the battery died and the phone shut itself off. Once I did that I plugged it into the charger and let it fully charge.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
Sounds like you did everything right. I say give it 3-5 days (I know a long wait) but usually that does fix a lot of calibration issues.
and there's a calibration app? craziness! I must see this..
If you are still having battery life issues, I suggest you install Chad's latest stable incredikernel (7/06/2011). I use it with CM7 and get very good battery life. You might also find juice defender helpful; set it to aggressive. Also you may want to manually adjust screen brightness settings.
Yep... There is a battery calibration app and it really does work. Wipes the stats for you and rewrites them. Just search the market for battery calibration. Should be right at the top.
jlokos said:
If you are still having battery life issues, I suggest you install Chad's latest stable incredikernel (7/06/2011). I use it with CM7 and get very good battery life. You might also find juice defender helpful; set it to aggressive. Also you may want to manually adjust screen brightness settings.
Click to expand...
Click to collapse
The nice thing about the kernel is you can flash a mod onto it that will charge the battery FAST. (If battery life is gonna suck, at least gimme fast charging!) Not sure its on the thread. It is on his blog page at incredikernel.com.
Battery life is back to normal. Just for the heck of it I did a full wipe, and and re installed cm7. 1 in recovery instead of rom manager, used the calibration App, and went thru 2 charging cycles. Thanks everyone!
The more I get to know my rooted inc, the more I wish I didn't do the 2.3 update on my inc2 and could root it right now
Sent from my ADR6350 using Tapatalk
I've updated the radio from the 7.28, not only is the upload/download speed better but so is battery life.
You have to try different ones as they are dependent on your location.
jlokos said:
If you are still having battery life issues, I suggest you install Chad's latest stable incredikernel (7/06/2011). I use it with CM7 and get very good battery life. You might also find juice defender helpful; set it to aggressive. Also you may want to manually adjust screen brightness settings.
Click to expand...
Click to collapse
Checked out his site, and plan on trying out that kernel when i get home. Has anybody tried his incredicontrol app?
Sent from my ADR6300 using Tapatalk
Yep, it's freakin great! Lets you toggle USB fast charge and audio boost, as well as control voltages. Works perfectly for me.
k_nivesout said:
Yep, it's freakin great! Lets you toggle USB fast charge and audio boost, as well as control voltages. Works perfectly for me.
Click to expand...
Click to collapse
Awesome. I'm going to flash his latest kernel and try it out. I'm gonna have to look up how to adjust the voltages correctly for the best results
Sent from my ADR6300 using Tapatalk
There isn't really a "right" way to do it, per se. This is what I'd recommend: on the voltage control screen, there are buttons at the top to increase or decrease the maximum and minimum voltages (in increments of 25). The top buttons apply this change to all frequencies instead of having to adjust the voltage on each individual frequency. I'd try dropping all voltages (maximum and minimum) by 50, and see if your phone is stable that way. There are apps that you can use to do a CPU stress test (setCPU does this), so try that and see if you run into any reboots or anything. If not, keep dropping the voltages (I'd do this in increments of 25) until you run into instability. Use the lowest possible voltages you can with your phone remaining stable and you should notice some increased battery life.
Hope this helps.
k_nivesout said:
There isn't really a "right" way to do it, per se. This is what I'd recommend: on the voltage control screen, there are buttons at the top to increase or decrease the maximum and minimum voltages (in increments of 25). The top buttons apply this change to all frequencies instead of having to adjust the voltage on each individual frequency. I'd try dropping all voltages (maximum and minimum) by 50, and see if your phone is stable that way. There are apps that you can use to do a CPU stress test (setCPU does this), so try that and see if you run into any reboots or anything. If not, keep dropping the voltages (I'd do this in increments of 25) until you run into instability. Use the lowest possible voltages you can with your phone remaining stable and you should notice some increased battery life.
Hope this helps.
Click to expand...
Click to collapse
OK, thanks. Does the stress test on setcpu stop after a certain length of time? If not how long should I let it run?
Sent from my ADR6300 using Tapatalk
I let it run for a few minutes. Just press back once and it will say how many milliseconds it was running and if there were any errors.
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.
Hey all,
I'm having serious battery drain on MIK 2.56 and pretty much any ROM that I flash. I'm running Chopsuey9.2.7 along with SetCPU profiles. I underclock the majority of the times.
My SetCPU profiles are:
Set on Boot = 691max/245min conservative
Charging = 1152/245 performance priority 100
Screen off = 245/245 ondemand priority 99
In-call = 1152/245 performance priority 98
Battery <50% = 691/245 conservative priority 97
Temp >43.7 degrees = 614/245 conservative priority 96
My evo doesn't like to be clocked at 128 or even 499. It reaches temps as high as 115-120 degrees during charging and while in my pocket (I'm thinking it may have got damaged when I used to run the SBC kernels in the early stages). Im starting to think that i have a bad battery. My battery will drain from 100% down to 80% within 5 minutes and usually will be dead within 2 1/2 hours after being off of the charger with moderate usage such as calls
text and checking email. I have Autokiller running and have set memory Lowmem settings to extreme thru Darktremor a2sd.
Any ideas/suggestions?
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
My stock battery lasts all day with my current setup. I have setcpu as well but don't really mess with it. I use Smartass governor with 1075/245 for normal everyday use. If I have too many drinks and have to crash at a friends house without my charger I'll drop the max speed to about 700 and use conservative or just switch the governor to powersave. Then I've got more than enough time till I need to get back to a charger.
i got good life on that ROM using Aggressive Freedom kernel & using set cpu at 245/768 set at boot....no profiles.
So you think the use of profiles is the issue? I'm not completely sure the profile for screen off is working correctly; I ssh'd into my EVO and took a look at /proc/cpuinfo but it will not show the current cpu speed.
I'll give it a shot without profiles and see. As for the govenors, I believe Smartass was removed and replaced with InteractiveX; is InteractiveX as good?
j7jman said:
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
Click to expand...
Click to collapse
I agree but with the way my profiles are set, I'm underclocking the majority of the time and only overclock when charging or on a phone call.
ive noticed i get wose battery life if i set up profiles. Worth a shot.
Sprint will test the battery for charge free I actually did it today
Sent from my PC36100 using XDA App
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
r.storm85 said:
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
That's correct. Also check your spare parts app for any wake lock.
Also, if you're using a havs kernel, setcpu will conflict with the kernel. And in general, you'll always get better battery life on AOSP.
try using setcpu sometimes that will help save battery.
Disabled Profiles in SetCPU....no luck
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Just left Sprint. They tested the battery and it tested bad and was swollen. I got a stock replacement free of charge although he said they normally would have charged me because the 1yr factory warranty expired. He also went on to say that the battery going bad was possibly caused from my phone being rooted which he may be partially correct. The problem began when SBC first came out and I was testing on the beta stage. It nice to have my phone off of the charger and not be down to 60% within 45 mins!
Sent from my PC36100 using XDA App
lostsoul77 said:
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Click to expand...
Click to collapse
my phone has been doing this exact same thing but i took it to sprint they said my battery was good should i go to another sprint tech and let them test it out?
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.
Rule 1: If you haven't taken these steps, you haven't done a thing in the way of actually optimizing your battery life, and please do not complain that your battery is bad if you haven't at least done steps 1 and 2!
Step 1: Use BetterBatteryStats: http://forum.xda-developers.com/showthread.php?t=1179809
This will diagnose battery drain issues. If you have apps that are sucking battery in the background, this will show it. Google the ones that have high partial wakelock, and usually you will get a diagnosis. It is also sometimes very easy to figure out what is sucking battery just by looking at the application that is holding wakelocks or having many alarm wakeups.
Step 2: Sync settings, make sure that all of them are either at push or as high as you're personally willing to allow between sync checkups. Any sync settings that happen too often will trash battery life.
Step 3: Radio based drain is a very big part of battery life! As such, if you do not need constant sync, you can turn off mobile data on your own when you do not need it, or go to the Mobile Network settings and disable always on mobile data. This can greatly increase battery life, but at the expense of sync not working when mobile data is off.
Step 4: Display brightness can greatly affect the power drain of the battery! You can either manually control the brightness, download Lux autobrightness to make your own autobrightness settings, or flash a custom autobrightness setting in the ROM in order to achieve this. It also can have the side effect of making the display of the right brightness when in the sun and in the dark, so it is always at ideal brightness to preserve battery.
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery.
Step 6: Adblocking! One big cause of battery drain and unnecessary network usage is downloading ads. If rooted, use Adaway and Adblock to block ads from ever being downloaded, and use Adaway's adware feature to detect and remove apps with adware!
Step 7: A radical step is to use Core Control or something similar to either underclock, undervolt, or just shut off cores. Undervolting is always highly suggested, as it will help reduce heat and give the phone a longer lifetime, but underclocking and shutting off cores will reduce performance!
Step 8: Custom ROMs and kernel experimentation might yield just a bit more in the way of battery life, and also give much more customization and features.
After this, you have likely topped out all that can be reasonably done to extend battery life. If you find that your battery drain is still poor, perhaps you have a defective battery, or maybe even a defective device (Highly unlikely, but who knows...). It is also possible that you simply have a use case that is much more than the phone can accomplish, in which case you can either use a battery case, or an external battery to charge the phone on the go.
Hunt3r.j2 said:
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery..
Click to expand...
Click to collapse
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
what do you mean by undervolt because i dont understand..what are the consequences ?
nemer12 said:
what do you mean by undervolt because i dont understand..what are the consequences ?
Click to expand...
Click to collapse
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Under volting is when you tell the battery to provide a little less power than usual.
Which is why the battery life usually increases, as less battery is being used than previously.
But as stated, too much can cause the battery to not provide ENOUGH power, therefor crashes and cannot boot properly etc.
One-X-master said:
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Click to expand...
Click to collapse
Pretty much, I would say. Drastic increase of battery in games: phone won't get hot => battery will last longer without overheating and, what is much more important, it will stay healthier in long run.
Even on wall charger while playing, my HOX won't overheat with - 100mv UV.
This is the main feature I miss on JB Sense without custom kernels
Sent from my HTC One X using xda app-developers app
THANK YOU
MysteryE said:
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
Click to expand...
Click to collapse
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
DarkManHaze said:
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
Click to expand...
Click to collapse
The problem is, the phone cannot get the same amount of energy, it consume (in fact, it is the millisecond, where the phone is fully charged, than it discharges for some minutes, than it will be charged again for three minutes and so on periodically). So, what I mean, you will almost never see 0 ma on one X or other modern phones. You can only see that, if device can disable battery while it is fully charge and use wall charger like a main supply. And the last device with such behavior was Huawei s7 back to 2010
So, 3-5ma is pretty ok.
Sent from my HTC One X using xda app-developers app