Related
I need help with my battery drainage, I cannot seem to track down what is the cause of my problems here. While at work I get a drain of anywere from 30-40 percent in about 5-6 hours! now that seems like ALOT.
I've tried stock, CM 6 R2, and Enom - I am on a custom kernel (2.6.35-925mV-CFS-SVS-720p-Monks-081010).. I am currently on that kernel and Enoms latest rom.
I've tried many things I've found on this forum. I installed "ShutUpBatterySaver", I removed my task manager, removed TiKL (heard it wasted battery while not in use), uninstalled ALOT of apps that I dont use/need just in case, Installed OSMonitor and watched to make sure nothing is using the CPU while its trying to sleep (I get less than 10 percent in use at any given time while the phone should be idle from android system mostly), I've stopped using live wallpapers and made sure my auto dim setting is on..
I'm not sure what else to do here Please Help!!
Thanks
viper2g1 said:
I need help with my battery drainage, I cannot seem to track down what is the cause of my problems here. While at work I get a drain of anywere from 30-40 percent in about 5-6 hours! now that seems like ALOT.
I've tried stock, CM 6 R2, and Enom - I am on a custom kernel (2.6.35-925mV-CFS-SVS-720p-Monks-081010).. I am currently on that kernel and Enoms latest rom.
I've tried many things I've found on this forum. I installed "ShutUpBatterySaver", I removed my task manager, removed TiKL (heard it wasted battery while not in use), uninstalled ALOT of apps that I dont use/need just in case, Installed OSMonitor and watched to make sure nothing is using the CPU while its trying to sleep (I get less than 10 percent in use at any given time while the phone should be idle from android system mostly), I've stopped using live wallpapers and made sure my auto dim setting is on..
I'm not sure what else to do here Please Help!!
Thanks
Click to expand...
Click to collapse
Your system is using 10% cpu while the phone is IDLE??? Yeah, that's not right. Mine is in the noise (<1%) when idle.
viper2g1 said:
I need help with my battery drainage, I cannot seem to track down what is the cause of my problems here. While at work I get a drain of anywere from 30-40 percent in about 5-6 hours! now that seems like ALOT.
I've tried stock, CM 6 R2, and Enom - I am on a custom kernel (2.6.35-925mV-CFS-SVS-720p-Monks-081010).. I am currently on that kernel and Enoms latest rom.
I've tried many things I've found on this forum. I installed "ShutUpBatterySaver", I removed my task manager, removed TiKL (heard it wasted battery while not in use), uninstalled ALOT of apps that I dont use/need just in case, Installed OSMonitor and watched to make sure nothing is using the CPU while its trying to sleep (I get less than 10 percent in use at any given time while the phone should be idle from android system mostly), I've stopped using live wallpapers and made sure my auto dim setting is on..
I'm not sure what else to do here Please Help!!
Thanks
Click to expand...
Click to collapse
me too the battery life on n1 sucks for me... i would unplug it then when i get to work on idle i turn it on it drops like 10 -15 percent in about an hour or so...??
Here is what I did.
1. Try to use black themes. I installed black desire bar and use black wallpaper.
2. Install SetCPU and set it to "on demand"
3. Change Wifi sleep policy to never.
4. Turn off autosync and use Shutupbatterysaver (This app automatically closes even after adding to task manager ignore list)
5. Remove widgets that auto refresh.
6. I'm using the same kernel as yours.
I also have **** battery life. Is it almost a must to calibrate the battery if you want to achieve good battery life?
Some people comment about how they have 36 hours of battery life OVERCLOCKED. If only my battery could come remotely close to that!
Unplugged my phone 1.25 hours ago and I'm already at 92%!
Edit: hmm, it tells me that my phone has been awake for 28 of the 75 minutes which is essentially impossible. Is there an issue where the phone takes too long to sleep?
I just recently got some very good usage out of my battery. Over night it only dropped something like 4%.
I'm not sure exactly what to attribute to as I've tried so many ROMS etc recently but the main things are probably
Installed SetCPU and set to 245min 500max
When in wifi location connect to it for data sync instead of 2g/3g as it uses less power when idle.
rickytenzer said:
I also have **** battery life. Is it almost a must to calibrate the battery if you want to achieve good battery life?
Some people comment about how they have 36 hours of battery life OVERCLOCKED. If only my battery could come remotely close to that!
Unplugged my phone 1.25 hours ago and I'm already at 92%!
Edit: hmm, it tells me that my phone has been awake for 28 of the 75 minutes which is essentially impossible. Is there an issue where the phone takes too long to sleep?
Click to expand...
Click to collapse
Something you're running is keeping it awake.. Most likely you have online/syncing/notifications on IM, Facebook, Twitter, something like that... Not the apps themselves, but them set to sync etc..
Spare Parts should be able to tell you what's keeping it awake.
What's UID 10018?
Here is what I did.
1. Try to use black themes. I installed black desire bar and use black wallpaper.
2. Install SetCPU and set it to "on demand"
3. Change Wifi sleep policy to never.
4. Turn off autosync and use Shutupbatterysaver (This app automatically closes even after adding to task manager ignore list)
5. Remove widgets that auto refresh.
6. I'm using the same kernel as yours.
Click to expand...
Click to collapse
Some details I forgot origionally:
1. I have a black theme and my wallpaper is dark not black though
2. SetCPU is not installed but via spare parts I have my max at 107520 and govenor is on demand
3. My Wifi policy is never
4. i tried shutupbatterysaver and switched to juice defender but will probably switch back
5. I removed all widgets that auto refresh except the facebook widget (set to never refresh but it does anyway for some reason), and beutiful home widget set to update weather every 6 hours.
When in wifi location connect to it for data sync instead of 2g/3g as it uses less power when idle.
Click to expand...
Click to collapse
I try to do this as much as possible actually.
Something you're running is keeping it awake.. Most likely you have online/syncing/notifications on IM, Facebook, Twitter, something like that... Not the apps themselves, but them set to sync etc..
Spare Parts should be able to tell you what's keeping it awake.
Click to expand...
Click to collapse
Here is a bit of my partial wake usage: Android system (Most), UID 10020, Dialer, Facebook, TiKL (anyone know what that is?), then News and Weather (I never use this not sure why its there), JuiceDefender, Handcent SMS.
OTher Usage shows: Running 54.9%, Screen on 27.1%, Phone on 15.9%, Wifi On 90.1%, Wifi Running 49.6% - All since last boot
rickytenzer said:
What's UID 10018?
Click to expand...
Click to collapse
It's usually OS monitor I think.
Anyone have any answers?
viper2g1 said:
Anyone have any answers?
Click to expand...
Click to collapse
In the process of calibrating my battery by draining it COMPLETELY (as in I can't even access the bootloader) and then charging it fully. I'll let you know if that helps!
Seems as if it's helped quite a bit. I managed to boot up, deal with the phone for a few minutes and download a 65MB file over WiFi and when I unlocked I was still at 99%. Try re-calibrating.
Try removing handcent. I used on my g1 and out was a serious battery hog.
Sent from my Nexus One using XDA App
Ok, so ever since I upgraded to CM6 (which I LOVE) I've had serious battery issues and I've tried to fix it by installing Pershoot's kernel and I have SetCPU to underclock in depending on what battery life it's at. Also, I've wiped my battery stats and I've calibrated my battery already.
Today my battery was at 64% after only 3hr and 26min. I don't have GPS on, auto backlight is on, 3g/2g and sync are on. If it makes any difference I have the Korean radio installed (which btw improved my reception a lot! ). After about 9hrs and half, my nexus one died. As per usage, I wouldn't say it's much at all because I'm in class most of the time and I've only talked on the phone for about 1 min, browsed a few websites, and sent only a few texts.
I keep reading on the forums about how people are getting 1-2% lower per hour while on standby but the % I reported earlier, my battery's draining at over 9%/hr!
I really just want to be one of those people that can say that "I still have 50% left after 12 hours!" lol
So, is there anything else I can to increase battery life? Is my battery just crap? Any recommended setCPU profiles?
If you're one of the users that get really good battery life from your Nexus One, please tell me what you did to get it that high! Thanks!
Don't use setCPU to manage battery life, only to overclock. It overrides the kernel's settings. Sounds like you need to wipe and flash the rom again. Then gradually add applications you want, something is sucking battery life.
Last, buy a new battery.
CM6 has less than stellar battery life. If you check the "help with my battery life" type threads, you will see most of the OP's have CM6 as their ROM. Try another ROM, you will get better results.
adambenjamin said:
CM6 has less than stellar battery life. If you check the "help with my battery life" type threads, you will see most of the OP's have CM6 as their ROM. Try another ROM, you will get better results.
Click to expand...
Click to collapse
Quoted for lies
I'm using CM6 and I get between 22-32 hours on a single charge. I just use the kernel that comes with it and i almost always have sync on. No GPS or bluetooth though.
Are you using a battery you purchased on ebay? Or are you using the stock battery? ebay batteries last me about 9-12 hours and die. The stock battery is amazing
Exactly the same situation as you:
CM6.
N1.
Student.
Experiences massive drainage in short amounts of time with low usage.
Tried everything.
I'll now be trying Enomther, because yes I have heard CM6 users get worse battery life.
Just a viewpoint on what I'm facing. For the past week I've gone to bed with 100% battery and woken up ~7 hours later on 75%. I've tried WCDMA and GSM auto settings and neither male a difference.
evilkorn said:
Don't use setCPU to manage battery life, only to overclock. It overrides the kernel's settings. Sounds like you need to wipe and flash the rom again. Then gradually add applications you want, something is sucking battery life.
Last, buy a new battery.
Click to expand...
Click to collapse
Thanks for the advice! I'll be looking into this!
KAwAtA said:
I'm using CM6 and I get between 22-32 hours on a single charge. I just use the kernel that comes with it and i almost always have sync on. No GPS or bluetooth though.
Are you using a battery you purchased on ebay? Or are you using the stock battery? ebay batteries last me about 9-12 hours and die. The stock battery is amazing
Click to expand...
Click to collapse
I'm using the stock battery so I don't know what the problem. I just ordered another official stock battery though yesterday and I'm going to see if there are any differences.
Forge94 said:
Exactly the same situation as you:
CM6.
N1.
Student.
Experiences massive drainage in short amounts of time with low usage.
Tried everything.
I'll now be trying Enomther, because yes I have heard CM6 users get worse battery life.
Just a viewpoint on what I'm facing. For the past week I've gone to bed with 100% battery and woken up ~7 hours later on 75%. I've tried WCDMA and GSM auto settings and neither male a difference.
Click to expand...
Click to collapse
Thanks, I'm glad I'm not the only one with this problem. I thought I was being an idiot by doing something wrong...
I've calibrated my battery several times already while trying to fix this issue. Could that have killed my battery life?
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Sorry, double post.
Jack_R1 said:
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Click to expand...
Click to collapse
crap, all the guides that i've read regarding calibration told me to discharge it completely.
My CPU usage seemed normal. It was stable at around 245 and would jump up to 998 from time to time that doesn't last for more than half a second though.
My battery seems to be in good condition as it's labeled as "healthy" by my battery apps and the voltage seemed normal....
lol at this thread...
http://forum.xda-developers.com/showthread.php?t=714184
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
For calibration, complete discharge is necessary. Doing it once is not too harmful. As long as the battery is reported "healthy" - you're ok.
There are apps that will show you the approximate capacity of your battery in numbers. Try to find one like that.
Please check discharge current and voltage over time. It doesn't make sense that a phone on 245 MHz in sleep mode will draw the current required to discharge 10%/hour.
in same boat as OP
im in the same position as the OP
student.
dont use phone for nearly 7 hrs a day
backlight on lowest, gps and bluetooth off.
ive been looking around for answers (hence why im reading this)
when class gets out ive gone from 100% to nearly 65%
running cm6 and ive wiped battery,
about to switch ROM, maybe that'll help.
adambenjamin said:
lol at this thread...
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
Click to expand...
Click to collapse
Thanks, I'll look at that ROM and check it out when I get time (probably this weekend).
Jack_R1 said:
For calibration, complete discharge is necessary. Doing it once is not too harmful. As long as the battery is reported "healthy" - you're ok.
There are apps that will show you the approximate capacity of your battery in numbers. Try to find one like that.
Please check discharge current and voltage over time. It doesn't make sense that a phone on 245 MHz in sleep mode will draw the current required to discharge 10%/hour.
Click to expand...
Click to collapse
Cool, thanks for the advice. I'll look for an app ASAP and report what happens.
Branden10 said:
im in the same position as the OP
student.
dont use phone for nearly 7 hrs a day
backlight on lowest, gps and bluetooth off.
ive been looking around for answers (hence why im reading this)
when class gets out ive gone from 100% to nearly 65%
running cm6 and ive wiped battery,
about to switch ROM, maybe that'll help.
Click to expand...
Click to collapse
Awesome, if you find a fix let me know please.
I haven't been able to do any of the suggestions yet but (when it comes to flashing) but I do have an update that might shine more light on this issue.
Today in class I noticed that my N1 was warm when it was in my pocket but nothing was running and gps and bluetooth was off. I checked the temp of my battery it was at 36.1C while it's usually at 30-31C when I'm not doing anything.
Also, I checked spare parts this morning and found that, while I was asleep, my N1 was not asleep for half that time but my screen on for only 4% of that time (probably from my messing with it before and a little bit after sleep).
I've checked to see if anything is running in the background that might lead to this but so far none of my apps should drain my battery that much while I was asleep.
Is this normal? Shouldn't my phone be mostly in sleep mode when I'm asleep since I'm not doing anything to it? As for the battery heating up, do y'all think it's a faulty battery or the fault of the OS?
Thanks again for all of y'all's helpful replies!
Is this normal? Shouldn't my phone be mostly in sleep mode when I'm asleep since I'm not doing anything to it? As for the battery heating up, do y'all think it's a faulty battery or the fault of the OS?
Thanks again for all of y'all's helpful replies!
Click to expand...
Click to collapse
About battery heating...
I checked and mine is at 75-78F while in class. My n1 is also in a case, so for it to be that low is good. Just thought to throw that in as a comparison.
Also i've switched ROMs to help with battery, no luck there. Still experience 7-8% drop per hour.
I've been keeping my phone off now at school, which has helped, though I still lose nearly 15% while it's off.
Sent from my seXus One using XDA App. While I gripe about battery stats.
Branden10 said:
About battery heating...
I checked and mine is at 75-78F while in class. My n1 is also in a case, so for it to be that low is good. Just thought to throw that in as a comparison.
Also i've switched ROMs to help with battery, no luck there. Still experience 7-8% drop per hour.
I've been keeping my phone off now at school, which has helped, though I still lose nearly 15% while it's off.
Sent from my seXus One using XDA App. While I gripe about battery stats.
Click to expand...
Click to collapse
I understand if my battery was at 71-78F but my battery was at almost 97F just sitting in my pocket...
Hmm, I think it's weird that the battery still drops 15% when the phone is off...
adambenjamin said:
lol at this thread...
http://forum.xda-developers.com/showthread.php?t=714184
Do a nandroid back-up of CM6, and then try out the above ROM. You can always go right back to CM at any time.
Click to expand...
Click to collapse
Alright, I just flashed it with that OS. I'll let you know how it goes. Thanks!
timchoi89 said:
Alright, I just flashed it with that OS. I'll let you know how it goes. Thanks!
Click to expand...
Click to collapse
i was using the cyanogen mod 6.0 for my nexus one and had a major battery iss i would wake up for work fully charged 100 percent goes on stand by with my set cpu to the lowest possible and the task manager running... note its on standy by with the screen low powered no gps or wifi running? so its 100 percent charged and then i leave to work arrive at 6 or 6:30 and its down 10 percent or more??? please if anyone knows a good kernel or rom to use please let us know my battery is in good health and from stock.....
Jack_R1 said:
1) Discharging the battery below 10-15% is bad for the battery, doing it many time will destroy the battery, making it last just about nothing.
2) Check CPU usage - download System Monitor or some other app like that, and check the running frequency of the phone. When you just run the program and don't touch the phone, it should float around 300 MHz. If you have it locked on 998MHz - you have an app that got your CPU stuck in a loop.
3) Download some app that stores battery stats, and check your discharge current and battery capacity - that way you'll know if it's your battery dead or your apps drawing the juice.
Click to expand...
Click to collapse
im checking the cpu usage but i really dont know where and which app specificly i use but i took a few pics and will try to post them up as soon as possible....battery stats i will post that up too...please help anyone...i was using cyanogen mod now leofroyo2.1
Some battery threads:
http://forum.xda-developers.com/showthread.php?t=978269
http://forum.xda-developers.com/showthread.php?t=1004760
updated tl;dr for most of you lately:
Your problem is probably that you flashed a new ROM or kernel recently, which causes battery stats to be very inaccurate. The most common symptom is that suddenly the battery drains like crazy, when before it just dripped. The opposite can also happen - you flash a new ROM and it seems like the best battery life ever. Until it suddenly jumps from 60 down to 10. This can happen even if you erased stats after flashing. You need a few days with your new ROM first, then you should see what your battery usage is really like. Do full charge cycles to speed up this process. (Bump charge, erase stats, drain, charge, don't bump charge or erase stats anymore, drain, charge, drain, charge, etc.) Simply put: you cannot judge battery performance after flashing a ROM. Often it can be a week or more before battery performance and battery level reporting becomes stable.[/tl;dr]
Every time a chef makes a new ROM available, or even among those using stock OS, there seems to be wildly inconsistent feedback on battery life. Many report catastrophic battery drain, while others using the same hardware/firmware/kernel/ROM say it's the best battery life they've ever gotten.
It would seem that a battery can run away on you for a variety of reasons, and flashing back, or returning to the store, doesn't have to be the first thing you do to fix it. This thread is to consolidate many of the complaints around xda about sudden battery drain, and discuss proven (or superstitious) fixes for it. This is not another discussion on tips and tweaks to extend battery life. There's a good wiki on that already. This is specifically about when you experience an unexplained dramatic increase in how fast your battery is draining, and the usual tweaks aren't having any effect.
And, in some cases, if you are experiencing battery drain associated with one of the "more interesting" issues below, you might be experiencing lag for the same reason. Please attempt all of the below to the best of your ability before making a post about battery drain or lag with a particular ROM or kernel.
We'll start with the simple.
Don't rule out your imagination or neurotic behavior as the main problem.
I hate to open with a "shut-up-noob," but this one is real. I know I've almost fallen victim to the disease of "let me turn on the screen just one more time to check the battery %." Or hours of "man this new lagfix is great watch how fast I can swipe screens and load apps over and over!" Both of which, obviously, result in more battery usage. Then there's also the case where you just installed a numerical battery meter for the first time, and watching it tick down is weighing on your psyche much harder than the previous, barely noticeable movement of the bar and making you think your battery is draining wildly. Which then can also then lead back to disease #1 in a vicious cycle of psychosomatic battery abuse.
It may just be the battery itself. Some are reporting an apparent quality control problem with the batteries. You might get a great one, or if nothing below helps you then maybe you got a dud. I can't help much there. Try reporting the problem to AT&T or Samsung. I hear AT&T is a lot better to deal with.
Check the basic battery usage stats. Settings -> About Phone -> Battery Use. This won't necessarily tell you a whole lot, it isn't always accurate, but it can give you an idea of what the system thinks is using most of the battery. Such as whether it's playing with the screen too much, or making a lot of phone calls, etc. Keep in mind... I'm pretty sure that these stats are only based on the time period listed at the top of the screen. A lot of people get confused when it shows the display using 90% of the battery. But if that's only based on the 30 seconds since you unhooked the charger, then it isn't all that confusing anymore.
Be wary of the "battery full" status. I have repeatedly found, at least in leaked 2.2 ROMs, that this alert actually goes off long before the battery is finished charging. This bug often continues even after you've done all of the other various tricks and tweaks and recalibrations. It says "100" and that the battery is full and to disconnect the charger, but when you disconnect, it instantly drops into the low 90s and drains quickly from there. Rather, if you ignore the alert and keep charging for considerably longer, it will actually be at 100 when you disconnect, and will drain slowly.
Click to expand...
Click to collapse
I'm quoting out the above, since I can't find the strikethrough tag. With new accurate battery mods, this isn't true anymore. Your battery doesn't need to go to 100%. It will be high-90s when you unplug, this is normal.
Drain and charge.
Sometimes the battery meter will seem to plummet, but then sit at <10 for hours before it finally shuts off. Giving a full drain may help calibrate where the "zero" really is. Run a long video, or just leave the camera up, until it shuts itself off. Then charge it back to 100%.
The bump charge (now commonly referred to as recalibrating).
Maybe your phone forgot where zero really is, or maybe he forgot where 100 really is. Here's the bump charge. Read carefully; I did it wrong for a while before I got it right. Charge the phone to 100% while it's on. As soon as it hits 100%, unplug the charger and power off. Now plug in the charger while the phone is off, and charge to 100 again. As soon as it hits 100, unplug the charger and power on. Wait until it boots completely, then don't charge this time, just power right back off. Now charge to 100 one more time with the power off. Power on and you are bump charged. Many also consider a stats wipe to be essential to this process as well. See below.
See joeybear's post (linked below) for more info on bum charges and battery stats, such as different procedures for CyanogenMod.
Erasing the battery stats (for you rooters/flashers)
Sometimes you just want your phone to forget everything he thinks he knows about his battery, and re-learn it from scratch. Your phone maintains a file with statistics on battery usage, which in turn is used to help calculate battery life at any given time. Sometimes, especially if you've been playing with ROMs, kernels, and lagfixes, the stats in the file just aren't applicable anymore to how the hardware is being used, so you get crazy battery drain.
Clockwork Recovery has a simple function to wipe the battery stats. If you can't run Clockwork, use ADB or a terminal emulator (search the market) to delete that battery stats file located at /data/system/batterystats.bin. The link at the bottom to joeybear's thread has a little more info.
The general idea is to start by trying the above - make sure it isn't your own fault or maybe just a bad battery, then drain, bump charge, and wipe stats - in that order.
There are lots of ideas about what may or may not happen when you experiment with the above. Wiping battery stats after a ROM flash that already wiped them for you is at least redundant and may even contribute to a battery drain problem. Some say you should wipe first and then drain and bump charge. Be careful about wiping stats and bump charging too much, though. Over-charging your battery will hasten its demise.
HOWEVER, if you're like I was when I first started this thread, you've seen the above recommended many times, and none of it has ever helped you one bit with an actual sudden battery drain problem.
Now for more interesting work.
Occam's razor. The simplest answer is the most likely. Battery appear to be suddenly draining faster? Well, it could be that you need to retrain your phone (or your mind) by using the procedures above. It could be that your battery suddenly went bad. A more simple answer is that something is draining your battery. Something is abusing your CPU, your memory, or your network interfaces. Try to find out what, or at least stop it even if you don't find out what. Simply looking at the stock report of battery usage isn't likely to tell you everything you need to know, though.
If you've recently flashed something, try your flash again, and this time be more aggressive. Make sure you turn off any lagfixes you've installed beforehand. Make sure you've got the most charge you possible can before flashing (see above - you want a true 100% charge immediately before flashing). Take the plunge and opt for repartitioning, data wiping, formatting, master clearing, or any other options you may have to start with a clean slate with the new ROM. Even flash stock first. Pay close attention to battery usage as you re-install apps and get your phone set up again. It may be one app in particular that was responsible.
Uninstall all task killers. Yes, uninstall. I know task killers are supposedly battery savers, but 99% of you (including me) don't know what we're doing when we get our hands on a good task killer. It is very possible you've got one service that is constantly trying to load and call home, and another that is constantly auto-killing it. If you really want to include task killing as part of your phone maintenance and battery tweaking processes, then download an app that is specifically designed and configured just for battery efficiency, not a general-purpose task killer that will allow you to hose up your Android system.
Check your background syncs. Experiment with turning them off, one at a time, and see if there's improvement. The app may have gotten confused after all your flashing and is doing something crazy as it syncs. If you isolate one that makes a difference, reinstall it or try living without it.
Live wallpapers. They actually improve your battery life, no lie. Ok, actually that is a lie. Some of them look awesome, but many users, myself included, experience a significant increase in battery drain when there's a fancy full-screen animation running non-stop on the phone. Try getting rid of them and see. There are some nice, simple, dark wallpapers that don't animate but are still pretty enough to impress the ladies at the bridge club. Live wallpapers can also create some majorly noticeable lag in your other apps, too.
Install OSMonitor. Set it to sort process by load, descending order. There shouldn't be much in the list, the OSmonitor app itself should show up near the top, at around 20%. Other apps should be in a 0% wait state or occasionally grabbing a few %. If you recognize an app sitting consistently at 50%+, that could be your problem. Make sure you know what it is first (not a critical system service) and try uninstalling it.
Is kswapd0 taking a lot of CPU? This is the memory swap / page file process. It's normal for it to be grabbing little chunks of CPU here and there, but if it's sitting at a high %, or jumping in frequently to a high %, then something's going on with your memory cache. Unistall your lagfix and try a different one. If you aren't using a lagfix, get OCLF and use it to install EXT2 and then OCLF V2+. Despite the changelogs and debates that claim otherwise, several have found OCLF to be very useful after flashing to any Froyo ROM (unless that ROM already includes a lagfix such as voodoo or stumpy's). If none of that works, your kernel may be the problem. Swap it or go back to stock.
Look at data/network usage. If you have a router or other device on your home wireless network that can give you some info, try that. Does your phone appear to be trying to send or receive an unusually high number of packets/data even when you're not doing anything with it? Also, while off wifi, watch the little green and red data icon in you notification bar (the 3G / E icon). Are they spasming green and red constantly every 2 or 3 seconds, even when you don't think you're doing much data transfer?
OSMonitor can also again be your friend here. Under "Network" you can expand each interface and look at live data transfer #s. Does one of them seem to be really active despite you not doing anything in particular with your phone right now?
If you have any of these signs of heavy data usage, go back to OSMonitor and look at Connections. Turn on DNS reverse lookups in settings. Turn on some whois. Ignore any loopback (127.0.0.1) and likely you can ignore the 1e100.com stuff, that's just Google (get it? 1x10^100). Are there any other established connections? Does the reverse lookup (the domain name) indicate what application might have the connection open? For example, if it's weather.com, that might be a Weather Channel widget or app. That one was responsible for destroying my battery one time. Use whois and similar tools in OSMonitor and on the Internet to help you figure out what your phone is connecting to. If you've got heavy data usage and an app or apps have open connections, uninstall / reinstall those apps and see if the battery drain stops.
Under-volting. Xan's Voltage Control App. There's a lot more of this going around now that there are several overclocking and undervolting kernels available. There isn't a whole lot to be said here. Different CPU clock steps can be individually adjusted to pull a little less juice from the battery. Make sure you keep them as temporary settings and do not "set on boot" until you're sure you've got a stable configuration. If you set something to a level your phone can't handle and script-save it for booting, you might not be able to boot again. Anyway, under-volting will not suddenly revolutionize your battery performance, but it can help.
Also, switching UV settings can significantly affect your battery meter after reboot. If you've recently switched UV settings and rebooted, your battery meter might suddenly show 20% more or less batterly life than before. This is simply what the meter thinks to be the case, obviously your battery did not just jump 20%.
Backlight notifications. I don't have hard data to back it up yet, but I've noticed that when a backlight notification is active, my battery starts racing to zero.
Cyanogenmod. It's available on Captivate now. It isn't stable/supported. It has a lot of debug code enabled. That means it uses more battery than it will someday when it's stable RC and debug code is commented out.
I've successfully used all of the "interesting steps" above in different cases where I had sudden battery drain and the basic steps didn't fix it. Anyone else have success with these? Any other tactics to share? Please post.
Thanks to joeybear23 for good info on recalibrating the battery.
Great info on the battery.
And you mentioned Occams Razor... the simplest answer is the most likely!
Ok, maybe your batteries are actually no good. Many have found theirs to be faulty and that after replacing them all is well again.
I just got a spare and the new one is great!
Maybe a batch of samsung batteries has problems and they begin to lose charge quite quickly after they have been in use a month or 2 (Or they get confused after multiple Flash's of ROMS .
Basically, I bought a cheap aftermarket battery as a spare and decided to try it in my phone today. I have made several calls and installed some apps and have played around with the phone as per normal. After 7 hours it is at 53%. MUCH better than before. With old battery it would be at 10-15% after a day at work.
Only thing different is I did install the lag fix over the Beta 5.5 to see if it helps speed.
Is it the battery or the phones software causing the problem??? Well if they have a chip in them maybe it IS the battery...???
Great read there! I haven't really been having any problems with battery life lately, but installed OS Monitor anyway just to see what was running. Nothing too out of the ordinary, as everything seems as you say it should be. OS Monitor is up there at 15-20%, android system is at another 8-10%, and system/bin/sensorserver_yamaha is running at anywhere from 7-16%. I assume this is the sensor that monitors what position my phone is in. Other than that, I don't see any other process taking more than a small slice of CPU or so from time to time.
I have done all of the suggestions before; bump charging, draining, and wiping stats, but I also feel that there may be differences since I am using a few different batteries. If I seem to get amazing battery life from a battery after wiping the stats and then using it til it dies, when I put in the next battery, it may work differently, thus screwing with the stats yet again. I have tried to not be as worried about battery life, especially since I have multiple batteries, but it's still something of interest to me.
I'll be subscribing to this thread, and look forward to reading some other users' thoughts/experiences with their batteries.
Scott -
In my own experience, putting lagfix on cog 5.5 has a huge beneficial effect on battery drain. I'm not sure yet but I believe the Unhelpful kernel uses a lot of cpu trying to manage swap unless you put an ext cache on it.
However, it's also true that you can great great life out of a new battery for the first 2 or 3 charge cycles. But a battery suddenly draining faster than normal is probably something your phone system is doing and not a bad battery.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cog 2.2 beta 5.5 with OCLF
Also, Demented, don't forget to look at antennae/network abuse, not just CPU. I once had a malfunctioning weather widget that wasn't using much CPU but was going berserk on my 3G and sucking batt juice so fast that you could hear the battery whimpering a little bit.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cognition 2.2 Beta 5.5 with OCLF
There should be a college class on correct battery usage.
Thank you so much for this thread, my battery thanks you as well!
Sorry if i shouldnt be posting this here. But i just read that wiki link at top and i was wondering what you guys think about leaving use wireless networks and power saving mode checked on to save battery???
Sent from my SAMSUNG-SGH-I897 using XDA App
Good thread; subscribed. I'll be trying some of this stuff out and reporting back here.
roadrash7 said:
Sorry if i shouldnt be posting this here. But i just read that wiki link at top and i was wondering what you guys think about leaving use wireless networks and power saving mode checked on to save battery???
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Some of the stuff there is valid; not sure I agree with using the task killer or the advice about leaving "Use Wireless Networks" on and GPS off. I leave both off, and when I want GPS access I turn on the GPS from the power control widget.There's no need for your Wi-Fi adapter to always be searching for networks and associating with Skyhook, etc.
Regarding leaving Wi-Fi on rather than 3G, it does make sense when you are using data. However, if the phone is idle, I doubt leaving the Wi-Fi card enabled will actually save battery life, as it will have to maintain connection with the access point (see your Wi-Fi sleep settings). I think a few short bursts of 3G download/upload when syncing, etc. will be less drain on the battery than leaving Wi-Fi enabled just for those small amounts of data that will be used when syncing. But, if you always want to be ready to browse, or do a lot of DL/UL at a moment's notice, I could see how keeping it on would be justified.
If manually syncing is acceptable to you, then by all means turn off the background data and auto syncing... personally I feel like the phone is really being limited and you have to balance utility and battery life, so I leave those options enabled.
Just some thoughts, if anyone can correct me on anything, I'm eager to learn.
TheYar said:
I'm not sure yet but I believe the Unhelpful kernel uses a lot of cpu trying to manage swap unless you put an ext cache on it.
Click to expand...
Click to collapse
I'm not really sure what you mean by that? There is no swap in use unless you add your own script to mount a swapfile.
Sent from my SAMSUNG-SGH-I897 using XDA App
Update
Updated the OP with some other items I forgot.
Unhelpful said:
I'm not really sure what you mean by that? There is no swap in use unless you add your own script to mount a swapfile.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry I wasn't being very accurately descriptive there of what I've seen. I rarely know for certain what caused or fixed a battery drain issue. Thanks for calling me out on this one, because going back over my history on this it looks like I was largely mistaken in thinking your kernel had much to do with it. One of my worst experiences with battery drain, it seemed that I had some apps/widgets that just didn't work well after the kernel swap, but Cog also made some non-specific references at that time to battery issues with the kernel and that stuck in my head. Another time with a Cog ROM I believe I may have misread the changelog and I was under the impression that I was on a new Unhelpful kernel, when I wasn't. Looks like that time it was actually a stock kernel partly responsible for the drain, which makes sense. Was I totally confused thinking Cog 2.2B5.5 uses an Unhelpful kernel?
As for what I was seeing (thinking now it was actually not on your kernel), kswapd0 was going berserk on my CPU. All I know is that is generally the name of kswapd0 is referring to virtual memory management, and putting OCLF on fixed it.
Well, vm also allows clean pages that are backed by files to be "swapped" out by freeing them, without using a swapfile, because the data already exists in storage.
A release or two ago I had some battery drain issues that were resolved by reverting some config changes.
Cognition 2.2 can't use any of my kernels, the froyo leak uses a different kernel version, and we don't have Samsung's modified sources yet.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
Cognition 2.2 can't use any of my kernels, the froyo leak uses a different kernel version, and we don't have Samsung's modified sources yet.
Click to expand...
Click to collapse
Right, which makes sense when I look back over my flashing history. DG had two versions in one changelog, and a line about re-adding your kernel to Cog 2.1.7 slipped in between some changelogs about Cog 2.2 beta releases. So I originally misread and figured that you'd somehow made a 2.2 kernel. It started draining my battery like crazy, which is exactly what happened the previous time I used an Unhelpful kernel (though again probably unrelated or only somewhat related to the kernel), and so I figured I was on to something. I was wrong. My b.
The issue that still remains is that I believe many people who flash to Cog 2.2.B5.5 (and perhaps 6), without master clearing and stocking first, end up with some odd behavior with whatever kswapd0 does (e.g., odd behavior like constantly using up to 90% of CPU for no dang reason). This is probably a cause, or the cause, of the Lagfixgate scandal and maybe Sudden Rapid Battery Drain Syndrome. And for whatever reason, OCLF fixes it.
I master-cleared and flashed 2.1 stock and then Cog 2.2B6, and kswapd0 and lag are no longer an issue even without OCLF. Battery is too soon to tell, though. Seems to be fairly normal, but not as good as some of what I used to see on Eclair with various other kernels swapped in.
Great resource here. Please keep updating! Subscribed...
Although you can't see it so well in the vid, the lagfix demo I captured also demonstrated a couple of points of battery life improvement.
http://forum.xda-developers.com/showpost.php?p=8631303&postcount=15
Bumped for updates in the OP.
With any of the 2.2 builds my cpu runs at constant 10%. We know its beta but worth looking into. Only info i have seen on my phone was android system. So im unsure what it is. Havent tore into it yet. But that was all stock with no apps installed. Even cog 6 i have the same cpu readings. So who knows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guess its not really 10% but up there
Just a tip. I was using latitude and wasnt getting the normal battery life i usually was when i wasnt using it.
I didnt know it was effecting it though cause you dont see it in task manager but you will in applications/running services. Anyways i signed out of latitude and battery life is back to normal.
It wont be remarkably better but it was noticeable to me. Just a tip.
Sent from my SAMSUNG-SGH-I897 using XDA App
smokestack76 said:
With any of the 2.2 builds my cpu runs at constant 10%. We know its beta but worth looking into. Only info i have seen on my phone was android system. So im unsure what it is. Havent tore into it yet. But that was all stock with no apps installed. Even cog 6 i have the same cpu readings. So who knows.
Guess its not really 10% but up there
Click to expand...
Click to collapse
How does that compare to when you're on earlier (eclair) builds? I expect there'd always be a little utilization going on.
Simple Poll.
Have you seen a decrease or increase?
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
nagash91 said:
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
Click to expand...
Click to collapse
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
OK I have done.. but the problem is that when I use it 3 o 4 minutes (for example I install an application using a file explorer, then I read a message and then I come back to home) m battery get 5% lower...
In standby I lose 10% in 6 - 7 hours (I think this is normal).
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
I am currently without a computer therefore immune to this USB bug. I flashed CM6.1 to this and the other g1 and both suffered substaintial amounts of battery drain so I nandroid restored back to CSDIv4 and still the lowest frequencies and settings did little to combat the descending digits. So I tried this...
Recalibrated my battery
Flashed SuperWipe.zip
Reboot
Flashed SparksMod's latest
Reboot
Wiped battery stats
Unplugged...reboot
Battery lasted 23 hours the first day never seen anything like it.
Lifes great.
Sent from my HTC Grandaddy via XDA app
Sent from my HTC Grandaddy via XDA app
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
nagash91 said:
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
Click to expand...
Click to collapse
I got real excited when I heard about the new radio and hboot even thought that its exclusion was the source of the the battery issues. Haven't been able to try it as I'm without a up-to-date PC at the moment.
It would be real nice if I could find a seasoned dev who understands battery consumption. I thought the kernal was the main culprit but I've tried two different roms with the same kernal and one has notably better battery life than the other. So confusing.
Sent from my HTC Grandaddy via XDA app
I can't use my phone with this battery drain...
I will come back to official android OTA-AOSP 1.6.. with +14mb.
So I'll test if this kernel with 14mb is a cause of battery drain.
PS: I'm not a lover of rom customizations.. I think the official roms are the best.
The other are all too heavy. I'm not a fan of cm kernel, that is too heavy for g1.
I would see an official OTA 2.2 without customizations, so every one could customize as he want, and if he want.
PS: OK I flashed AOSP 1.6 using ezBiff_kernel to have 15mb (cause I have new radio and spl, so I can flash roms only using this kernel).
Result: my battery life is similar to froyo 2.2 roms... so the problem is:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
2) New radio/spl?
3) My battery (I don't think so.. it's new battery. I buy it 2 weeks ago and in the beginning it works so well.. but then I flashed new radio/spl and new kernel for 15mb..)
nagash91 said:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
Click to expand...
Click to collapse
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Cm/pershoot have some interesting new power management code from other htc devices.. So hopefully soon all will be better. (I merged most of it to my kernel but there are some loose ends.. works well untill the phone locks up.. so no public release yet)
ezterry said:
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Click to expand...
Click to collapse
Ok sorry I talk without knowledge. I really don't know the effect of the cm kernel. I only know that all roms based on cm release, with cm kernel, are so heavy and slow.
I like your rom (2.2.1 AOSP) and I love your new way to get 14mb.
But I have this orrible problem. My phone has a lot of battery drain when I use it. With screen off, no problems.
I have never used swap or compcache in this days, and I also try different clock speeds (not over 528mhz).
The result is that when I unlock my phone, I go to settings, I see for example 95% battery. Ok, I return to home, I open a message, I return to home, I open contacts and I scroll some contacts without make calls.
Then I come back to battery settings and I see that is 92-93%..
in 2 minutes of soft use.. I think this is impossible. If I open stupids 2D games... ahah in 5-10 minutes my battery lose 10 - 20%.
I remember 1 year ago, with 1.6 (no cyanomod) my battery was good.
Now it isn't (I have a new battery).
Today I flashed aosp 1.6 with your kernel for 14mb (I have new radio&spl) but nothing... I lose a lot of battery percent as in froyo.
So I think problem is or battery calibration, or something to wipe, or cm kernel, or new radio&spl + your new kernel...
Now I'm recalibrating battery (is at 1% from 2 hours, I'm not using it.. ) then I will recharge for 8 - 9 hours and then wipe battery state, but I have done this process a lot of time without a benefit.
I'll try to remove the new radio+spl (so also using standard kernel) if my battery continue to lose percents so fast.
I'll keep you update on my "story".
PS: Sorry for my bad english!! XD
OK.. after a day of low discharging and a night of 8 hour of recharging, I wiped battery states, I wiped data-cache-ext ecc... I flashed aosp 1.6 and ezbiff kernel..
"battery drain" continue...
I will try tomorrow to reflash death-spl and old radio..
BTW, is normal for hours battery 4v at 90%?
On the back of the battery sais 3.7v... I thought 3.7 was the voltage for 100%
Update
I know this thread is a little old, but I ran into this problem as well. What I found was that the official US radio (2.22.23.02) used considerably more battery than the international one (2.22.19.26i). The other thing I noticed is that switching to "use 2G networks only" in mobile networks settings and disabling data over mobile drastically improved battery life.
I also noticed that wifi used a fair bit of juice so my recommendation is to disable wifi if you're going to be on the go for a bit, and disable data/3g if you're just going to be hanging out in the local webcafe, your/a friend's house, or some other location with wifi access for a while.
If you wanted to be ambitious and cared enough you could write a script to use as a shortcut on the home screen to do the swap automatically (detect which setting(s) are enabled and swap them to the opposite).
With those changes, you should get much better battery life. My thoughts on different Froyo flavors is that possibly different builds have different settings by default. Cyanogen comes with data and 3g enabled by default so this will quickly suck out your battery if you're running your 3g, 2g and wifi antennas all at once.
The stock build (1.6) got about the same battery life as I'm getting now with those settings applied. With either build, having all antennas on all the time will drain your battery very rapidly. Being a little more cognizant of the settings (perhaps you also had it set to 2g only on the stock build) you're using will significantly improve your battery life. And when I say significantly, I mean night and day (but the antenna version definitely does also make a difference... at least in my case).
sorry for the new thread
i use kuyadroid 2.7 , and i feel that my battery drain very fast like hell,
i only use the 3g, i have calibrated my battery but it not help me, can someone help me please?
Dont know...u may try a full wipe...than turn of all modules u have like overclock that in some roms comes enabled!
Well u can charge it to 100% without disconnecting and do again battery calibration!
goldenr said:
...than turn of all modules u have like overclock that in some roms comes enabled!
Click to expand...
Click to collapse
how can i turn off ??
Check the link in my signature.
ok i'll try, i'll report back after it
i have freeze some app like dsp manager, whatsapp, email,yahoo mail and messenger. i decreased brightness and undervolt my processor.
i can feel the difference, but i think the battery drain still fast, i'll do a calibration after charge my phone.
/edit : i use 2g only too/
maybe your battery is not in good condition gan.
Or try to reduce brightness, animation, and timeout screen :-D
Cheers up, guys. Cool down.
I use PowerMax app from market, plus some tips in here: http://forum.xda-developers.com/showthread.php?t=942241 my x8 can last at least 2 days...with normal (almost hard use).
i have question to ask, i charge my phone till 100% and the battery gauge in System Panel (i used this application for monitoing my phone) shown 4769 mV. When my phone reach 10%, the gauge shown 3669 mV. Should in normal circumstances it is in what position when the battery runs out?
sorry for my english,