Database Develop

Need Help w/ Battery (Yes, I've done my research as best I could)

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

How to isolate and fix battery drain (and maybe lag, too)

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.

[Q] 2.2 Froyo update, battery life lost

I have not yet updated my Captivate to 2.2. Reading posts in regard to the update I am very bothered by a common complaint that battery life has just died. My Captivate has excellent battery life using it fairly heavily over a 1 day period. I charge it every nite. Also, my GPS is workng fine in 2.1. So am considering not updating it due to the problems I am hearing about.
Anyone else have input on battery life after the update??

I went from STOCK 2.1 to Cognition 4.1 (built on Froyo 2.2) and my battery life is about the same. My usage varies wildly from day to day, but as best as I can tell, overall battery consumption is about equal.
I wonder if the people complaining about battery life have set up their phone "post-update" with different apps or turned on "apps syncing background data"...

Battery life did reduce on 2.2 but it is obvious in my point of view. But its not too bad either.

it's about the same, i upgraded to stock 2.2, feel no difference on the battery life. moderate usage last mine for about more than 24 hrs, u should update to froyo for you to experience it.
Sent from my SAMSUNG-SGH-I897 using XDA App

SnackCracker said:
I went from STOCK 2.1 to Cognition 4.1 (built on Froyo 2.2) and my battery life is about the same. My usage varies wildly from day to day, but as best as I can tell, overall battery consumption is about equal.
I wonder if the people complaining about battery life have set up their phone "post-update" with different apps or turned on "apps syncing background data"...
Click to expand...
Click to collapse
I upgraded Stock 2.2 end of Feb and noticed a big drop in my battery life the first week. But just reading above, i did turn on "apps syncing background data" so i think that's my problem. Just turned that off so we shall see...

Let your phone go through a week or so recharging cycle before judging its battery life after a ROM flashing. You just lost all your battery stats when flash a new ROM. Your phone/OS has no clue how your battery will operate until it has time to learn or you manually calibrate it.
For what it is worth, my battery life is about the same or slightly better than leaked 2.2 ROM as well as 2.1 ROM. No big changes.

My battery has been about the same since the 2.2 upgrade. At first it felt like my battery was draining quicker but I also noticed I was playing with more phone more. The screen is the biggest power drain on the phone so just playing with menus and looking at new settings can cause a small dent.
Give it a week or two after upgrading and you'll notice it'll be about the same. Unless of course you have more accounts or programs syncing data in the background.

Why upgrade to 2.2
Thanks everyone for the input. The more I read and hear the more I am leaning toward not upgrading to 2.2. On different forums I am seeing and hearing problems with battery life and some saying about the same battery life. Also, seeing GPS not being fixed or going from working ok or good to not working so good. Right now my phone does everything I want, GPS works really good, email works fine, internet works fine, battery life is outstanding, mp3 works great, screens all are clean and to my liking, I have an easy work around for turning off 3G and one tap returning my volumes to normal after using a USSD code.
REally cannot see any advantage to upgrading and risking introducing a problem I don't need. The list of new features really does not thrill me.

gstreff said:
Thanks everyone for the input. The more I read and hear the more I am leaning toward not upgrading to 2.2. On different forums I am seeing and hearing problems with battery life and some saying about the same battery life. Also, seeing GPS not being fixed or going from working ok or good to not working so good. Right now my phone does everything I want, GPS works really good, email works fine, internet works fine, battery life is outstanding, mp3 works great, screens all are clean and to my liking, I have an easy work around for turning off 3G and one tap returning my volumes to normal after using a USSD code.
REally cannot see any advantage to upgrading and risking introducing a problem I don't need. The list of new features really does not thrill me.
Click to expand...
Click to collapse
2.2 ROM is a big step forward, not backward, IMO. Sure it didn't solve GPS issue but it is not making it worse either. GPS issue is purely hardware issue. If you have a good one, it doesn't matter which stock firmware you use.
I just can't see any disadvantage for upgrading (other than slightly more difficult to root or unlock, but not impossible). Battery life thing is as I mentioned above. You will see all kinds of complaints (either dain too fast or too slow) after a new firmware comes out, any firmware. You don't know what you're missing until you upgraded.

I noticed a big improvement in battery life. Sometimes with light use it will last up to four days, whereas before with 2.1 it would putter out after maybe two days.
GPS isn't fixed, but drop one of many GPS fixes in and it will get somewhat normal performance.

Wifi sleep policy
You may also want to check the Wifi sleep policy after the upgrade to Froyo. In my case, the default was "Never sleep". Changing this to "When screen turns off" improves battery life on 2.2, as it does on 2.1.
Just my $.02 worth.

foxbat121 said:
Let your phone go through a week or so recharging cycle before judging its battery life after a ROM flashing. You just lost all your battery stats when flash a new ROM. Your phone/OS has no clue how your battery will operate until it has time to learn or you manually calibrate it.
For what it is worth, my battery life is about the same or slightly better than leaked 2.2 ROM as well as 2.1 ROM. No big changes.
Click to expand...
Click to collapse
I'm on stock 2.2 since the day it came out. My battery life is actually trending worse day-by-day. I did a full battery clear/reset this weekend and after 4 days I'm finding battery life is not improving at all. The degradation from stock 2.1 is significantly noticeable to me.
For the first couple of days post-update it seemed actually to be better, but got worse and worse, to where I was lucky to find the phone working 12 hours after disconnecting from the charger @ 100% ... even if I hadn't -touched- the phone during the day. My applications loaded are virtually identical to before.
I did have Background Data on, so I've just disabled it, but was this option not in 2.1? I know that Google Voice, etc, were doing background syncs in 2.1.
It can't be WiFi, as for the last 2-3 days I've kept WiFi turned off. However just for sanity I did adjust the sleep policy.
I'm wondering ... my battery woes seemed to start when I hooked up my Microcell. Could having a strong 3G signal so close to the phone actually be causing problems?

jahfry said:
I did have Background Data on, so I've just disabled it, but was this option not in 2.1?
Click to expand...
Click to collapse
it is the same as in 2.1.
I'm wondering ... my battery woes seemed to start when I hooked up my Microcell. Could having a strong 3G signal so close to the phone actually be causing problems?
Click to expand...
Click to collapse
That might be your problem. I don't know. I know 2.1 doesn't work very well with microcell either.

Yep. I'm pretty convinced it is the microcell now. Phone works great with it from a call/data/signal standpoint. However after unplugging my microcell last night, charging my phone to 100%, and then letting the phone discharge normally with no microcell ... I'm now 10 hours later and have an almost full battery.
Sad, because our reception here is so spotty that we lose calls and data regularly without the microcell. My wife says her phone charge has been pretty normal, so I'm getting ready to move the cell away from my desk and see if distance helps the story.
So, as far as this thread is concerned, my results for 2.2 and battery life are great ... better than with 2.1 ... just don't use it with a microcell.

Froyao 2.2 Battery Usage Dillema
I see no significant or excess battery drain while riding the KB1 over the JF6.
Just a thought for those experiencing excessive or significant battery drain. KB1 loads some new features and new additional bloatware that loads on boot and runs as a service, process and both.
If you're familiar with poking around your system settings and understand what doesn't need to always be running in the background, or what doesn't need to load on boot, you can simply kill the process and even alter the way a certain application handles on boot.
By killing many unneeded or unwanted processes at boot time, it will significantly save you hours upon hours of battery life in the longer scheme.
Another FYI, Lithium Ion batteries have memory. You need to train or retrain the batteries memory over time in order to sustain a longer life for it.
Tips:
Don't continually through the charger on your device after minimal drainage. Let the battery run down before fully recharging it again.
When flashing to another ROM wipe your battery stats.
When flashing any new code to your device - a few forced charge deaths to purge the battery and reset the memory again prior to recharging may be a good idea...
Hope this helps...
Peace-
Liv33viL

[Q] Battery life question - are there different battery versions?

Hello all,
I have a brand new Galaxy Tab ( three full charges so far) - and I get quite different results re. battery life then others.
Then again: I read some posts with really long batt life, and others with shorter.
I have Gingerbread - Overcome RC1 installed, and I in about 1.5 hours use ( no 3G, some wifi, medium backlight; time spent mainly installing / removing apps, some games, some email and web browsing) I am at 75%.
When the unit is fully charged, after I switch it on it goes to 99% immediately (I see 100% maybe for less than a minute). This morning I am at about 65% battery life, with about 2 hours use. ( I have erased the battery stats after installing the Overcome rom).
When not using the unit for several hours (for example over night): I do a complete shut-down.
Now others seem to get significantly longer run times.
Is it possible that there are (at least) two versions of the GT, one with better battery the other one with weaker battery?
Or do I have a defective unit and should I try to return it? ( I am within the 30 days return policy, and could go for an exchange)?
Or is my experience totally normal, and the "really long" battery lifes are more the exception?
Or will my battery life get longer after a few more charge / recharge cycles?
I would appreciate any feedback!
Thank you!

People claiming better battery life are running custom firmwares, have their cpu moderated, and have pulled all kinde of tricks to achieve this.
Also, your battery has to "settle"
Sent from my GT-P1000 using XDA Premium App

Thank you for the reply.
I am also using a custom firmware but no other tricks (slowing CPU etc.)
So my unit is then probably normal?
How long does it take for the battery to reach full capacity?

I think I will return the GT for replacement...
Another update.
Yesterday, I have done a full recycle ( fully empty the battery and fully recharge).
Today, when I started to use it, within 50 minutes the battery level went to 80%.
I have removed now all apps, all widgets etc ( factory fresh gingerbread) and I will fully charge and then reset the battery memory within CW.
Lets see how that goes... but I start to worry now as my return period has just passed ( 14 days from purchase) - so I may be stuck with a unit with a battery problem...

I would reccomend to stop delete battery stat everytime now and then. Another thing is please wait few cycles so battery will settle down as someone said. When I got my SGT for the first time I was quite worried that my battery drain so quick. Simple internet browsing over wifi last for 3-4h. Later on I found tha some apps sync itself constantly, name pulse, weather widgets, rss readers etc. Ive check the apps and disable auto sync. Also moving from 2.2 to 2.3 gives me huge boost and make battery last muuch longer.
Sent from my GT-P1000 using XDA App

Thank you. Lets hope you are right.

Install the version beta2. The battery on it lasts much longer. I checked and returned to the beta2 since RC1. Only first JJ4, then JQ1 and beta2. My English is not good, so I apologize if I wrote something wrong

Wow. That is an interesting theory. I will definitely test: you well may be right. I have used beta2 only for a short time, but I think the battery did last longer...

In beta2 worked for 11 hours. The RC1 is less than 7 hours. A friend has the same. Both went back to beta2. Wi-fi enabled, much inernet ,radio, Google mail, mp3. Used on a single chargefor more than iPad

Same problem here..
Strange it is. .
So far i know. .
Battery life is always been the hillarious thing ever, on a smartphone..!!!
Hehehe. . .
Sent from my GT-P1000T using XDA Premium App

For me it has always been a big differens in battery life after a couple of weeks when the battery is performing better.
In the beginning with stock rom i barely got trough one day with heavy use.
Now its no problem getting trough two days of heavy use. Using Overcomes (rc1) latest rom.

Gadgetguy2005 said:
Thank you. Lets hope you are right.
Click to expand...
Click to collapse
I would deffinitelly recommend going back to beta2 as in my case on rc1 I was able to get maximum 7-8 hours when switching to beta2 gave me at least 12 hours. At the moment when not extensively using the tab I am able to get around 60 hours.
ps1
as someone mentioned before pleae stop erasing batterystats.bin
ps2
Do not try to install beta2 on rc1 as it wil cause you a lot of problems. Start with jq1 at least and then beta2.

Hello,
I had the same problem too, but I have resolved it now.
I started by browsing this thread:
http://forum.xda-developers.com/showthread.php?t=986067&highlight=false+status
Then I opened up my tab and disconnected battery for 30 mins. Reconnect and close up and that fixed the problem permanently.
For some people, flashing overcome 2.0 rc1 solved their issues.
Hope that helped.

jpanggy said:
Hello,
I had the same problem too, but I have resolved it now.
I started by browsing this thread:
http://forum.xda-developers.com/show...t=false+status
Then I opened up my tab and disconnected battery for 30 mins. Reconnect and close up and that fixed the problem permanently.
For some people, flashing overcome 2.0 rc1 solved their issues.
Hope that helped.
Click to expand...
Click to collapse
Link does not work. Please correct if you can.

Link Fixed

Thank you all. I will just wait for the next overcome release: i hope tht will give longer run times.

Battery help please

I know there are countless threads/topics regarding high battery usage re p880, but I didn't want to resurrect an old thread, or hijack someone else's, so if I'm wrong in creating this thread, then I apologise.Can someone please tell me what exactly this service is/does, as it seems to be the biggest problem regarding my lousy battery life.. phone just sees it as android system (pic 3) where as BS+ sees system back up service. As i have backup disabled, this is puzzling me.
Thanks in advance,
Edit: in the time it took to write this message, ive lost 14% in battery, including the time it took to screenshot.
Edit 2: Ah, now im back on PC i can type properly.
been playing around, disabling system backup service, but a new process just gets launched in its place, from key chain, to LocMgrProvider...seems as you disable one, another replaces it, all using same battery. Must i just accept, that the android system is just going to eat my battery?..like cookie monster at the biscuit counter?
If it helps, im running stock 4.0.3, freshly flashed, with F/reset, unrooted.
Thanks in advance, and any help is very much appreciated,
Sun
Sent from my LG-P880 using Nuke Powered Pigeon

SunHounD said:
I know there are countless threads/topics regarding high battery usage re p880, but I didn't want to resurrect an old thread, or hijack someone else's, so if I'm wrong in creating this thread, then I apologise.Can someone please tell me what exactly this service is/does, as it seems to be the biggest problem regarding my lousy battery life.. phone just sees it as android system (pic 3) where as BS+ sees system back up service. As i have backup disabled, this is puzzling me.
Thanks in advance,
Edit: in the time it took to write this message, ive lost 14% in battery, including the time it took to screenshot.
Edit 2: Ah, now im back on PC i can type properly.
been playing around, disabling system backup service, but a new process just gets launched in its place, from key chain, to LocMgrProvider...seems as you disable one, another replaces it, all using same battery. Must i just accept, that the android system is just going to eat my battery?..like cookie monster at the biscuit counter?
If it helps, im running stock 4.0.3, freshly flashed, with F/reset, unrooted.
Thanks in advance, and any help is very much appreciated,
Sun
Sent from my LG-P880 using Nuke Powered Pigeon
Click to expand...
Click to collapse
that's... waaaaaay too much. why are you on ICS anyway?
my suggestion is - factory reset from stock recovery (warning: your internal sd card will be fully formatted). in case you don't care about ICS, i strongly suggest JB. if you don't care about voiding warranty, i strongly suggest unlocked bootloader + custom rom and kernel. oh and also, grab better battery stats app, it shows an easier-to-understand overview when compared to apps you used

Flying_Bear said:
that's... waaaaaay too much. why are you on ICS anyway?
my suggestion is - factory reset from stock recovery (warning: your internal sd card will be fully formatted). in case you don't care about ICS, i strongly suggest JB. if you don't care about voiding warranty, i strongly suggest unlocked bootloader + custom rom and kernel. oh and also, grab better battery stats app, it shows an easier-to-understand overview when compared to apps you used
Click to expand...
Click to collapse
Thanks for such a quick reply.
I'll tell you the scenario, as quick as i can make it.
had the phone 2 weeks, got it on a 24mnth contract ( i know, sigh)
anyway, updated it to JB (4.1.2?) through LG pc suite, but thought the battery life seemed to be worse, so i downgraded with LG flash tool, to ics.
after a F/reset, i rooted, then F/Reset again, but it seemed sluggish.
the long and short of it is, ive gone up to JB twice, and down to ICS twice, rooted and unrooted twice, disabled a whole HOST of stock bloatware, and am still left with similar results as posted in the pics.
ATM ive a clean ICS and im at a loss as to what to do. ive been reading all the threads about improving battery, culling the bloatware apps etc before i decided to post.
as for bootloader, i will probably do that sometime in the future, when im more knowledgeable on the subject. at present, i dont want to be left with a 2 year contract to a brick
thanks again,
ps: you say better battery stats is better than battery stats plus?...will download now, thanks
Sun

interesting situation. it's strange that sluggishness persisted between factory resets and .dz flashes back to 10x version.
first off, how does the phone behave when you're not using it? is it draining battery bad? is it going into deep sleep? what are the percentages of cpu states (you can check this in better battery stats, as battery stats plus seems to be too clunky for me to read proper info)?
if it's deep sleeping properly, then yeah, the issue is with something sucking up the juice while screen is on. next off, check cpu states - if it's locked at 1.5ghz often, when you have screen on but doing nothing, it's significant info.
what i've noticed with display, you can count up to 3:30 hours of onscreen time with stock rom (this is with very conservative use of wifi and data during this period, and no heavy gaming for example) - that's around 200 minutes of on screen time, meaning you should get around 2 minutes of screen on per 1% of reduction in battery - how far are you from this result?
i hope we manage to get to the bottom of this, but i still recommend unlocking bootloader and flashing custom kernel and/or rom. you can't really brick o4x while unlocking bootloader afaik, and you've done more complex operations when switching from 20a to 10h than bootloader unlock is.

I would go the other way to be honest. If you do a full factory reset, install no apps, no Google account or anything and still get a similar problem with the battery drain then I would take the phone back for replacement as that is abnormal.
No point running a risk with your warranty when might be a hardware fault.

It's midnight here now so can't really test it till.morning now. When phone is in standby, it seems to hold.its juice ok. I'm sat here now, with nothing switched on except WiFi, screen at 23% brightness , and am just using tapatalk and I'm getting 2-3 mins per 1% screen. Less if I play in the menus. First thing tomorrow, I'll reset the phone again, before dl'ing any apps. Then I'll only download BBS and see how I get on. I'll also.monitor battery loss over night.
Sent from my LG-P880 using Tapatalk 4
edit:
after i wrote the above last night, i decided to watch a movie on my phone in bed.(headphones, dont wanna disturb the missus ) and i managed to watch a movie of 2hrs 10 mins, with 23% battery drain, on stock video player, yet just browsing through the phones menus/ light web surfing, eats the juice like crazy.
left phone off charge over night, and didnt even have a 1% drop in 7 hours (wifi off,sync off, data always off(dont use it)) and phone set to 2g mode
Sun

current set up
Right,
I've performed another F/reset, and rooted. Installed TB pro, and uninstalled/frozen a skew of apps/services as listed per the thread in my sig.
Installed better battery stats, charged phone to 100% took off charge, and am just waiting to see how it goes now. Would you recommend using phone as normal while BBS collects its info, or to let the phone alone for a while?
thanks again,
Sun

SunHounD said:
Right,
I've performed another F/reset, and rooted. Installed TB pro, and uninstalled/frozen a skew of apps/services as listed per the thread in my sig.
Installed better battery stats, charged phone to 100% took off charge, and am just waiting to see how it goes now. Would you recommend using phone as normal while BBS collects its info, or to let the phone alone for a while?
thanks again,
Sun
Click to expand...
Click to collapse
you can leave it alnoe during night to check if it deep sleeps properly, right now you're interested in cpu states option in bbs, to see if it uses too much cpu when doing normal tasks such as surfing, reading, watching/listening media etc. your goal is to get over 2 mins per 1% drain (in the end, over 3 hours of onscreen time with no heavy gaming). with those stats, your can say that your phone is draining normally, just that lg reports stupid stuff (f.e., stock roms report screen as using 20% of the battery, while in reality screen is using waaay more, the most actually)

Thanks Flying_Bear, I'll refrain from doing any more resets etc for the rest of the day, see how the readings progress and post on that tomorrow, after overnight analysis.
This piece of one of your previous posts just stuck in my mind:
Flying_Bear said:
i hope we manage to get to the bottom of this, but i still recommend unlocking bootloader and flashing custom kernel and/or rom. you can't really brick o4x while unlocking bootloader afaik, and you've done more complex operations when switching from 20a to 10h than bootloader unlock is.
Click to expand...
Click to collapse
TBH, from everything I've been reading on it, it kind of scared me off the subject, but to see you say it was less complicated than what I've already done, has got me to thinking.
The biggest thing for me at the minute, before considering that, it to rule out faulty hardware. At least if thats the case, i still have warranty intact.
Is the performance increase really that noticeble after flashing custom kernels/roms?
Thanks again for your time,
Sun

no.
apart from everyone here praising custom roms and kernels, DON'T flash a custom rom, when you are concerned about battery.
the best rom out there regarding battery life is by far a stock rom, be it 4.0.3 or 4.1.2.
the worst thing about the custom roms is WiFi. with stock i was able to let WiFi run through the night with less than 1% loss per hour.
on every custom rom my battery needs at least 5% per hour for WiFi, but most of the time even more. its just not useable.
shortly followed by 3g network, which has a much bigger battery drain than stock, too.
i am on CM and different kernels for some month now and i consider going back to stock, because i want to leave WiFi on in the night, otherwise my phone eats up my 100MB free 3G traffic way too fast.
BUT...
the reason for your battery hungry phone is not the ROM, the kernel or the phone itself.
your battery drain is absolutely absurd for stock ROM and can only be caused by badly programmed apps you have running.
OR:
you have your phone relatively new and play with it EVERY FRICKIN MINUTE, which would be an explanation, too.
you said, you were able to watch a whole 2h movie with only 23% loss, that sounds like the stock ROM i know. on custom you would lose around 50% for this. but when your phone loses battery when you "play with the launcher", you maybe have installed a 3rd party launcher, that eats your power, are using facebook/skype/whatsapp/(insert any other badly coded program, that has no push mode), or have just fiddled with the developer settings a bit too much.
Because you noticed your battery drain with 4.1.2, too, then i suspect a badly coded app. these are the reason for nearly every battery drain (and the reason for wakelocks, too) apart from bad drivers in custom kernels, like the WiFi desaster all the custom rom users have here.

I think the only reason I would consider custom roms, is a performance increase.... If it wont give me one, then I see no point in going down that route.
LamerDuck said:
i am on CM and different kernels for some month now and i consider going back to stock, because i want to leave WiFi on in the night, otherwise my phone eats up my 100MB free 3G traffic way too fast.
Click to expand...
Click to collapse
Totally agree, its why I refuse to enable data in the first place.
the reason for your battery hungry phone is not the ROM, the kernel or the phone itself.
your battery drain is absolutely absurd for stock ROM and can only be caused by badly programmed apps you have running.
Click to expand...
Click to collapse
when I took the original screenies, in OP, I didnt really have much in the way of apps on it. I'd not long before done a clean flash, then removed some of the bloatware that came with it.
OR:
you have your phone relatively new and play with it EVERY FRICKIN MINUTE, which would be an explanation, too.
Click to expand...
Click to collapse
At first yes... hey it was a new toy at the time. Novelty wore off about day 3 though.
you said, you were able to watch a whole 2h movie with only 23% loss, that sounds like the stock ROM i know. on custom you would lose around 50% for this. but when your phone loses battery when you "play with the launcher", you maybe have installed a 3rd party launcher, that eats your power, are using facebook/skype/whatsapp/(insert any other badly coded program, that has no push mode), or have just fiddled with the developer settings a bit too much.
Click to expand...
Click to collapse
yeah, it handled a movie quite well, I was quite pleased with this. When i said messing with the menu, I just meant exploring the phone; no custom/3rd party launchers, no messing with Dev stuff.
At the minute now, the only extra apps on my phone are XDA Dev app, tapatalk4, BBS, TB-pro and root uninstaller pro.
Oh, and can I ask.... aside form the ability to "pimp" your phone out, or the extra customization, is there any benefit to flashing custom roms? As it cant be for better performance....
thanks
Sun

LamerDuck said:
no.
apart from everyone here praising custom roms and kernels, DON'T flash a custom rom, when you are concerned about battery.
the best rom out there regarding battery life is by far a stock rom, be it 4.0.3 or 4.1.2.
the worst thing about the custom roms is WiFi. with stock i was able to let WiFi run through the night with less than 1% loss per hour.
on every custom rom my battery needs at least 5% per hour for WiFi, but most of the time even more. its just not useable.
shortly followed by 3g network, which has a much bigger battery drain than stock, too.
i am on CM and different kernels for some month now and i consider going back to stock, because i want to leave WiFi on in the night, otherwise my phone eats up my 100MB free 3G traffic way too fast.
BUT...
the reason for your battery hungry phone is not the ROM, the kernel or the phone itself.
your battery drain is absolutely absurd for stock ROM and can only be caused by badly programmed apps you have running.
OR:
you have your phone relatively new and play with it EVERY FRICKIN MINUTE, which would be an explanation, too.
you said, you were able to watch a whole 2h movie with only 23% loss, that sounds like the stock ROM i know. on custom you would lose around 50% for this. but when your phone loses battery when you "play with the launcher", you maybe have installed a 3rd party launcher, that eats your power, are using facebook/skype/whatsapp/(insert any other badly coded program, that has no push mode), or have just fiddled with the developer settings a bit too much.
Because you noticed your battery drain with 4.1.2, too, then i suspect a badly coded app. these are the reason for nearly every battery drain (and the reason for wakelocks, too) apart from bad drivers in custom kernels, like the WiFi desaster all the custom rom users have here.
Click to expand...
Click to collapse
yeah wifi can drain too much, but i had almost same stats on custom as on stock - 3-4% per hour if wifi is left on, with sync on and push notifications and blabla. you've got things going great if you have 1% per hour with wifi on.
lg has crammed up a whole lot of **** inside their stock rom - apart from useful stuff like proper mhl drivers, quickmemo, nice gallery & video apps, it's bloated to hell - mlt logging, ****ty launcher (imo), widgets that only work on stock launcher, "smart log service", RIDICULOUS throttling etc). you can root and uninstall most of these, but even then you might not get what you're looking for.
my best onscreen time on stock 4.1.2 20a/20b was 3 hours 3 minutes. that's with conservative use of wifi, 3g and almost no gaming. on custom rom & kernel, today i pumped out 3 hours 37 minutes, and was on 17% battery, when i plugged it in in order to recharge it. that was an obvious increase for me (keep in mind there were custom rom/kernel combinations that had me pulling barely 2 hours onscreen time).
you need unlocked bootloader for custom kernels, and say what you say but proper kernels ARE battery savers and performance enhancers. stock kernel has for some people insane issues with baseband_xmm wakelock (for me it was rediculous, 6% per hour drain when not using a phone and no deep sleep at all) and wipes didn't help with that; only custom kernel fixed it. it has RIDICULOUS (for emphasys) throttling effect, slowing your cores down to 1ghz each when battery hits 43 degrees celsius (which for me was around 20 seconds of normal usage on a hot day outside), which leaves you crippled if you're planning on doing any complex action with your phone.
alternative is - unlock bootloader, check custom roms and see if you like'em (Zaiben is f.e. debloated and improved stock, something OP might like, or he can go cm, or carbon or any other if he prefers custom features). if you don't, it's easy to flash a .kdz file back.

Flying_Bear said:
yeah wifi can drain too much, but i had almost same stats on custom as on stock - 3-4% per hour if wifi is left on, with sync on and push notifications and blabla. you've got things going great if you have 1% per hour with wifi on.
lg has crammed up a whole lot of **** inside their stock rom - apart from useful stuff like proper mhl drivers, quickmemo, nice gallery & video apps, it's bloated to hell - mlt logging, ****ty launcher (imo), widgets that only work on stock launcher, "smart log service", RIDICULOUS throttling etc). you can root and uninstall most of these, but even then you might not get what you're looking for.
my best onscreen time on stock 4.1.2 20a/20b was 3 hours 3 minutes. that's with conservative use of wifi, 3g and almost no gaming. on custom rom & kernel, today i pumped out 3 hours 37 minutes, and was on 17% battery, when i plugged it in in order to recharge it. that was an obvious increase for me (keep in mind there were custom rom/kernel combinations that had me pulling barely 2 hours onscreen time).
you need unlocked bootloader for custom kernels, and say what you say but proper kernels ARE battery savers and performance enhancers. stock kernel has for some people insane issues with baseband_xmm wakelock (for me it was rediculous, 6% per hour drain when not using a phone and no deep sleep at all) and wipes didn't help with that; only custom kernel fixed it. it has RIDICULOUS (for emphasys) throttling effect, slowing your cores down to 1ghz each when battery hits 43 degrees celsius (which for me was around 20 seconds of normal usage on a hot day outside), which leaves you crippled if you're planning on doing any complex action with your phone.
alternative is - unlock bootloader, check custom roms and see if you like'em (Zaiben is f.e. debloated and improved stock, something OP might like, or he can go cm, or carbon or any other if he prefers custom features). if you don't, it's easy to flash a .kdz file back.
Click to expand...
Click to collapse
Hi Flying_ Bear, can you pl confirm what combo of rom and kernel is giving you 3 hr 37 min of screen on time and which ones to avoid (ones that gave you 2 hrs)?

Carbon rom 4.2.2 version with iodak v7 had the best onsceen. Id say stock was worst, 2hrs 45mins of onscreen with no gaming and low brightness, with stock kernel