Related
Yo
heres a brutally simple battery monitor software thingy that graphs your usage and battery level - top graph is mAh usage (15000ms refresh (os updates info every 30 secs)) and bottom graph is battery life (60000ms refresh)
i wrote this thing to monitor my batt usage cause my bat life is utter crap, barely lasts 8 hours with my level of use/cellular climate, which sucks its just a straight up .exe, just copy to where-ever and run it
this version here is so pre-alpha-uber-dev-debug-build its not funny but i thought id put it up for you lot anyway as i have found it useful just to glance at from time to time - there are no user controls, i spazzed this out in a hurry but i intend to improve on it and implement any features you lot might think useful.
best i can get out of my raph with screen on with celluar, gprs and bt ad2p connected is -63mAh - whats the best you can get?
just tryin to put smt back into the community <3
p.s. this is a debug build (i kept getting microsoft error reporting crap on the emulator, so i dunno how itll go on other devices)
p.p.s. i take no responsibility if this bricks your device, sleeps with your wife, sets your house on fire or kills your cat etc etc (but it works ok on my raph
***UPDATED 25.03.09***
SEE POST #9 IN THIS THREAD BELOW
going to try this out soon, loving the simple graph
now i can see whats happening when 40% of my battery dies overnight as i sleep >:O
works good, any way of making it show the current time on the x-axis? or able to scroll left and rigth to see what happened earlier?
and whats the bottom graph for?
07accordEX said:
any way of making it show the current time on the x-axis? or able to scroll left and right to see what happened earlier?
Click to expand...
Click to collapse
both of these features are on the todo list (which ill put up when i get a moment)
and whats the bottom graph for?
Click to expand...
Click to collapse
read the initial post.
the top graph shows the past hour of activity (ish, its actually more like 57.5 mins), the bottom graph shows the past 8 hours (ish, more like 7.7hrs).
no data is collected when the device is asleep - and the graph doesnt get updated during these times, so you only see 'active' use in the graphs - i plan to implement some sort of visual cue system to signify times of sleep and also to keep the temporal coherency of the graph more contiguous (lol, e.g. a graphed minute will be 8 pixels wide no matter what).
i believe its impossible to collect data while the device is asleep as afaik when the processor goes to sleep the only part of it that functions is the bit that listens for interrupts (from i.e. the phone management cpu, etc) (and maybe a timer (for alarms etc?)) - if im wrong on these details please enlighten me.
fusi
Nice app I would love to see it becoming more mature, will probably end up with my standard equipment, thanks 12
12aon said:
Nice app I would love to see it becoming more mature, will probably end up with my standard equipment, thanks 12
Click to expand...
Click to collapse
thanks, watch this space should have something new up by the weekend
This opens up a blank white page on my phone. Did I do something wrong?
behrouz said:
This opens up a blank white page on my phone. Did I do something wrong?
Click to expand...
Click to collapse
the graphs dont refresh as soon as you open the app - youll hve to wait for the first update (15 and 60seconds) before anything is rendered - this will be fixed soon.
ok, a bit later than advertised but here is an updated version - fixed most things, still working on scrolling through the history - will add more features in coming days (colour customisation, toggling graph display, scrolling through history, exporting graphs as images, user customisable update intervals, etc)
btw ive added in support for unattended mode - this keeps the cpu alive when the device is asleep - i dont recommend keeping this on unless you are trying to debug unexplained power drain in standby - unattended mode keeps my raph ticking along at -21mAh, when im pretty sure true idle for this handset is more like -4mAh. so yah, not recommended to leave it on
im pretty sure there arent bugs but if you find one please let me know!
enjoy
fusi
fusi said:
ok, a bit later than advertised but here is an updated version - fixed most things, still working on scrolling through the history - will add more features in coming days (colour customisation, toggling graph display, scrolling through history, exporting graphs as images, user customisable update intervals, etc)
btw ive added in support for unattended mode - this keeps the cpu alive when the device is asleep - i dont recommend keeping this on unless you are trying to debug unexplained power drain in standby - unattended mode keeps my raph ticking along at -21mAh, when im pretty sure true idle for this handset is more like -4mAh. so yah, not recommended to leave it on
im pretty sure there arent bugs but if you find one please let me know!
enjoy
fusi
Click to expand...
Click to collapse
I'm curious to know what you think the power consumption caused by this program is. Like you, I get about 21mA drain with the phone screen off - but I'm getting that with your old version. I use S2U2 with the "but only blank screen" option and turned off standby in Windows power management so I think that's effectively putting the phone in unattended mode. Normally (without your program running) I see pretty modest battery drain with the phone in unattended mode. Just off the top of my head I'd say that 5-15% battery drain per hour would be about what I'm used to with zero usage - phone just sitting in my pocket or on a desk in "unattended mode" but just now while running your older EXE my phone went from 65% to about 40% in under an hour while "unattended" (locked, screen off). Looking at the graph for that time period I see a consistent 21mA drain. If 21mAh=25% capacity, I'm in trouble. I know my battery isn't that far out of whack because I get what I'd consider (based on reading other's experiences) pretty normal life out of it. Maybe the drain characteristics for that "portion" of the battery are a little different - I'm not sure whether the capacity is judged solely on capacity minus drain or it figures voltage levels in as well...?
To be clear, I'm basing my sense of normal battery consumption on nothing more than "took it off the charger in the morning, didn't use it all day at work and have ~50% when I get home 9 or ten hours later" so it's anecdotal at best.
I'll keep playing - I love this tool. Maybe I'll be a little more scientific about my testing and see if I'm imagining things.
Hi thanks for posting
if your just turning the screen off, i dont think thats unattended mode, unattended mode actually powers down non essential parts of the device.
if unattended mode is off in the program and your phone goes into standby, it wont consume any battery as when the phone goes into standby everything is shutdown and the cpu pretty much stops functioning (apart from a very small part) - but this also means the historical data and graphs dont get updated . if unattended mode is on and your phone hits that standby timeout, it wont go into standby but unattended mode instead where it just turns off a lot of the non-essential stuff, like voltage to the sd card, the screen, etc - but it keeps the cpu running and the operating system pumping its messages.
i think a chunk of that 21mAh is going to be the operating system - but not all of it - currently the program registers 2 timers with the os, one has a 15second timeout and the other has a 60 second timeout. timers do drain battery, as the cpu keeps having to go 'is it time yet? is it time yet?' ad infinitum.
btw, when i said 'true idle' in my prev post i meant that that is the current used in true standby.
one way to calculate how much current its drawing is to leave your phone running it for 24hours (airplane mode on etc) and see how much its depleted over that time, then do it again without it running. using that information you can figure out how much current its using - i havent done this yet, i cant put the thing down for 5 minutes let alone 24 hours
im currently working on a system that doesnt use timers, it might work, might not if it does i hope to see that 21mAh reduce, but i dont imagine itll go down by that much. there are however loads of optimisations that can be done, and im investigating them atm.
im no battery scientist but as far as battery capacity, i think li-ion batteries judge their capacity by their voltage, from something like 3v up to 4.2v (0% -> 100% [wiki link below]) - i could be wrong on that though.
http://en.wikipedia.org/wiki/Lithium_ion_battery <-- this is a good informative read.
i dont think the battery is very capacious tbh - any amount of drain and it seems to go down very fast - i think the saving grace of the device is that is consumes minimal power when in standby - on days where im constantly using it heavily, im practically tethered to a power outlet as the battery just drains far too fast - i think the manufacters banked on the assumption that users would mostly have the phone in standby mode for most of the day. i usually use it for music while im at work and have putty sessions open etc, so its always on - i barely get 8 hours use without a charge .
ive noticed with my battery that even though the drain is constant (i.e. 21mAh or 63mAh) the charge level of the battery does not decrease linearly - e.g. ive noticed my phone suddenly start going down and lose 10% in 5 minutes before, and then the charge level would level out and stay at the same capacity for like 10 minutes before starting to go down again - this to me seems a little funny, as if the circuitry reporting the capacity isnt quite accurate - i think there a many factors, including battery temperature, the drain on the battery in mAh (i think a spike of higher drain may cause the battery do the nose-dive-then-level-out thing) - but i also think that the battery just doesnt deplete linearly, it seems to always have lumps and bumps in the graph, no matter how smooth the drain is.
glad you like the app ill be posting an update to it in a week or so.
peace
fusi
I'm not sure what exactly S2U2's "but only blank screen" does, but it leaves me with a 21 mA draw, so it can't be much different from unattended mode. I haven't tried to monitor it in that mode with (for example) an active Wifi connection or a program accessing the SD card to see if that changes things, but as it is it seems to be running the same things your set is.
The only reason I think the capacity calculation must not run off of only the voltage is that it has a definite "learning" capability. I think it must be doing some more complex things behind the scenes in terms of monitoring consumption and recalibrating periodically based on charge and discharge rates. I know I've seen it sit at 99% charging for a (very) disproportionately long time. The only good explanation for that is that it wasn't perfectly calibrated and the battery is still accepting charge at a higher rate than an almost full battery would. I've seen the same behavior in a lot of charge monitoring systems as they "learn" the characteristics of a battery. I guess it could be basing that purely on voltage, but I doubt it. While connected to a charge, the system will report a substantially higher voltage than it will as soon as the charging voltage is disconnected.
I don't know, I'm just kind of thinking aloud here. It would be great if there were a way to poll the power consumption without affecting the power consumption - sort of a Heisenberg's uncertainty problem... I'd really like to know what the power consumption is in unattended mode as well as true standby. Even if you do the 24 hour test you have to assume a lot of things about the battery's initial condition and the accuracy of the meter to arrive at a consumption number (and, like you, I'll never have a day I don't want to putter around with this phone). I suppose if you were really into it you could stick an ammeter between the battery and phone and control for the added loss
It's definitely true that the discharge isn't linear, even given a constant discharge rate. This has to be an artifact of including battery voltage in the capacity calculation. If it was using purely capacity minus usage the relationship would have to be linear.
Anyways, keep up the good work. I love stuff like this, just from an academic standpoint. Practically speaking I'm pretty much tethered to my chargers, too...
hyachts said:
I'm not sure what exactly S2U2's "but only blank screen" does, but it leaves me with a 21 mA draw, so it can't be much different from unattended mode.
Click to expand...
Click to collapse
That's exactly the case, this setting causes your device to run in unattended mode (backlight off, audio off, wi-fi off, ...)
hyachts said:
I think it must be doing some more complex things behind the scenes in terms of monitoring consumption and recalibrating periodically based on charge and discharge rates. I guess it could be basing that purely on voltage, but I doubt it. While connected to a charge, the system will report a substantially higher voltage than it will as soon as the charging voltage is disconnected.
Click to expand...
Click to collapse
Microsoft's reference battery driver for PXA270 CPU is calculating battery percentage based on voltage exclusively. HTC's custom driver for Qualcomm cores seems to have some kind of more advanced logic behind it, but it doesn't work well/smooth.
hyachts said:
I don't know, I'm just kind of thinking aloud here. It would be great if there were a way to poll the power consumption without affecting the power consumption - sort of a Heisenberg's uncertainty problem... I'd really like to know what the power consumption is in unattended mode as well as true standby.
Click to expand...
Click to collapse
Not without external tools, it should be possible to hook up an external multimeter to the battery directly to measure the voltage accurately in standby. Using the battery driver information you can only evaluate it and the evaluation is likely to be pretty rough.
Attached are some charts from my Touch HD...
The battery level graph seems to follow consumption graph very closely.
You can barely notice the resemblance with the voltage graph though.
These charts depict my device's utilization over 2 days, assuming 0 mah consumption when in standby. This assumption is apparently not accurate, as the battery capacity is 1350 mah and only about 1000 mah were utilized. Out of these 48 hours the device was in standby for about 40 hours, so my estimated standby utilization is -350mah/40h => -8.75mah. This doesn't sound reasonable, as according to manufacturers specs, the device is capable of 450h of standby, with 1350mah battery standby consumption should be -1350mah/450h => -3.375mah. I would agree with fusi, that taking manufacturer's estimation errors it should be safe to assume standby consupmption is around -4mah.
40*-4mah=160mah, so I have about -190mah remaining unaccounted for. I blame measurement accuracy for this... IMO, with this degree of inaccuracy, standby consumption can not be accurately estimated and has to be assumed based on manufacturers specs only.
I'm running more tests to reconfirm these observations, but I doubt the results will be extremely different.
For your reference, I get -69mah on Touch HD when idling with minimal backlight level and -27mah in suspended mode.
So the other day, I forgot to close an app down--the Schwartz Unsheathed, if you are curious--and when I fished my phone out again, it was hot. Very, very hot. Battery information indicated 41C which, in the grand scheme of things, isn't that high (wouldn't worry me with a PC's graphic card, for example, or CPU) but it felt incredibly warm to the touch. Fine, I shut the app down, removed the battery cover and let the phone cool down. No problem.
It might be the apps I've been trying since then, but I have been experiencing performance and stability issues. Things slow down sometimes. On the Desire ROM, Rosie kept force-closing every now and again. On Enomther's which as we all know is just about the stablest thing that ever stabled, Launcher2 does ditto (the Launcher Dock may be the culprit, though, as it seems to do some weird **** and I've removed it since. Fiddling around with BetterCut also seems to cause force-closes). So could that be it? Did the phone overheat (but if so, shouldn't it have shut itself down) and now something's broken? Getting antsy. :/
41°C should not be a problem, but consider that this was a measurement from the battery pack and that a sensor like that can easily go +/- 5 to 10 degrees.
so well, some chip on the nexus could have gotten way hotter than 41°C. maybe something fried, some defect that was already there and now its really broken.
still, this can be a bit subjective, the phone will seem broken if you think it's broken you can always do a factory reset, reflash the current rom and try from there.
Yeah, could just be my own jitters--I'd experienced issues before, usually caused by a ROM or whatever--and lately my PC's been having problems, so it might well be some kind of placebo effect. Unless it and my N1 magically entered a symbiosis or something.
Thanks for the quick reply.
once my phone accidently fell onto my bed and under my pillow while i was charging it over night and i woke up at 4 am and found a burning out nexus under my pillow. i unplugged it and nothing seemed damaged but it still worried me.
I think if you are worried about it and you are rooted you should install SetCPU. It has a profile designed so that is you his a preset temp it will down clock your CPU.
I use setCPU to save my batterylife ie.
100% - 50% run full cpu on demand.
Idle/Standby downclock to 400Mhz
50% or less down clock to 600Mhz on demand
20% or less down clock to min.
I also complement this with locale for low bat. dimness, wifi off, bluetooth off. etc.. etc.. ( a little off topic I know)
Well, looks like updating More Icons Widget was what did it; things seem to work okay now.
Was wondering what the maximum advisable temperature is?
Maybe the phone has protection for the CPU? but Li-ion batteries dont like heat, it shortens their effective life.
my battery reached 44.3C yesterday on a 4 hour journey in the car using co-pilot and the phone actually net discharged despite the fact it was on a 1A USB charger for the entire journey - about 80% at start of journey and 20% at end.
I've installed setcpu now and set the temperature profile to drop the max speed to 768 if temp is >44C and another one to drop the speed if power is less than 30%, may need further tweaking though. This was not in my car and the back of the phone was effectively unventilated, in my car I have an open backed holder near an air vent.
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
I only have 5 widgets, and my brightness is also low as possible. I have wifi off when i don't use it, but my battery still dies kinda fast. Should i delete cell standby? And what else can i do?
You really should define "kinda fast" so folks can answer objectively
Well just playing games like angry birds for 20 minutes it drops like 10%
EverythingNook said:
Well just playing games like angry birds for 20 minutes it drops like 10%
Click to expand...
Click to collapse
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
HotShotAzn said:
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
Click to expand...
Click to collapse
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
EverythingNook said:
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
Click to expand...
Click to collapse
What drain are you seeing with screen off/idle?
with the screen off for about 5 hours i saw a 21% drain.
Drop the widgets and livewallpaper if you've got it. Retest standby.
If you're getting high battery drain during standby your nook isn't going into deep sleep and chances are that background overhead translates to poor efficiency at idle when the nook is on as well. Couple poor idle efficiency with CPU intensive work while in use and your overall battery life is terrible.
If you're forcing the nook to stay out of deep sleep for other reasons like keeping wifi alive then you may be stuck with living with some sort of elevated drain but you can minimize it by reducing idle overhead by keeping widgets to a minimum and refraining from using live wallpapers and other background services that aren't critical.
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
distortedloop said:
Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running.
Click to expand...
Click to collapse
If you suspect it, disable it and see. I'm thinking that would be a prime suspect.
distortedloop said:
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Click to expand...
Click to collapse
I believe typically overnight you should see less than 10% drain.
In CM7 at least, in Spare Parts you can see what uses the battery while the NC is asleep.
distortedloop said:
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
Click to expand...
Click to collapse
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
No, not yet. It's 100% stock, other than rooting and downloading apps. I'm going to put SystemPanel on it and see if it gives a clue.
I've got a good idea of how to track down battery issues on most android devices, I was just mostly curious what the typical drain other rooted users saw was.
Thx for the suggestions to all.
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
Good lord, this isn't going to help anything. Normal Nook Colors on the stock ROM (and kernel....) use about .2%/hr in standby.
Clearly something is running wild on this guys NC, and needs to look at Spare Parts. Install it from the market.
System Panel as well as other tools can help as well.
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
distortedloop said:
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
Click to expand...
Click to collapse
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Extra deep. Two stages...
First stage 5 pins, second stage 12 pins...
Sent from my Nexus One using XDA Premium App
Yup same cable as my Droid2 and Droid before it....
Krazypoloc said:
Yup same cable as my Droid2 and Droid before it....
Click to expand...
Click to collapse
Does this mean we can use the droid2 and droid's cables as alternatives?
khaytsus said:
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Click to expand...
Click to collapse
Thanks for the extra info about the additional voltage; so it will charge much faster this way? (rhetorical question)
I still am annoyed at yet another non-standard cable that I'll have to carry around with me when I travel to keep various devices charged, but in the scheme of things it's a minor annoyance. Stuff like this should be standardized, IMHO.
And it's extra DEEP, not wide. It's the same width as a standard micro-usb cable or I wouldn't have been able to stick my phone's charging cable into it at all, but I was able to, it just didn't go in deep enough to charge at all. On the flips side, the B&N cable fits into my phone, but only inserts half-way deep; if it were extra wide it wouldn't fit into my phone at all.
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
beache said:
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
Click to expand...
Click to collapse
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Craz Basics said:
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Click to expand...
Click to collapse
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Tips for better battery life.
And a lot of common sense.
tuncan said:
Tips for better battery life.
And a lot of common sense.
Click to expand...
Click to collapse
very helpful thanks
chewingum16 said:
very helpful thanks
Click to expand...
Click to collapse
Tnx. :good:
Zombie said:
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Click to expand...
Click to collapse
yes it will on many cases, but I can't tell with the OP5. Is the circuit will cut-off the battery from the phone to avoid drain? If yes, in that case, it won't hurt significantly the battery.
In general , what can hurt li based batteries : time, heat and numbers of time of electrons changing direction.
Having the phone plugged in, every X time the % will drop, and the charging circuit will trigger the battery.
As I said, can't tell how op5 is working, and it probably be minimal anyway. But technically it will reduce the capacity : http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Heat : 20W charger, even if its a vooc, at one point the battery will get a high current load = heat, and chemical li-po arrangement changes.
Time : cant do nothing here, chemical arrangement will degrade, its a normal process for most battery, specially li based one.
But at the end, not much people would see any difference, since nowadays people changing their phone every 1-2 years, fck ridiculous...
Back to topic :
Pixel off apps , many of them on the play strore, can't tell which one is good or not.
Basically, it will turn off pixels on the screen.
https://play.google.com/store/apps/details?id=com.anrapps.pixelbatterysaver&hl=fr
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
dkryder said:
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
Click to expand...
Click to collapse
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
shangxor said:
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
Click to expand...
Click to collapse
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
dkryder said:
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
Click to expand...
Click to collapse
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
[/COLOR]
shangxor said:
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
Click to expand...
Click to collapse
yes, i offered the link as a punchline to your comment about joking. however i do have a question about your comment,
"He had based part of his study on incorrect data also"
why didn't you include the part of the study and the incorrect data? because, when statement like this is made it is left to the reader to determine the part of the study and the incorrect data which may lead to misunderstandings.