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.
I returned to stock rom just to play (Pokemon go) and other thought was might get better battery life than custom rom I was using. But I am experiencing damn slow phone with worst battery backup. Moreover its stuttering and lag while playing any game like gta sa or any other also phone is getting too hot to handle.
Anyone else experienced same in a while ? should I consider clean flashing of stock again?
First try clearing the battery logs by rebooting to bootloader -> volume up once to bootloader logs -> press and hold power for > 7 seconds until the phone reboots. Then charge the phone to 100%. If that doesn't help, a clean flash might help. I would certainly try it.
Has the battery ever been replaced? If not, then it's time.
The lag/stuttering is probably the battery throttling kicking in. If I remember right, it's around 40% on stock. Custom ROM/kernels will adjust this.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
First try clearing the battery logs by rebooting to bootloader -> volume up once to bootloader logs -> press and hold power for > 7 seconds until the phone reboots. Then charge the phone to 100%. If that doesn't help, a clean flash might help. I would certainly try it.
Has the battery ever been replaced? If not, then it's time.
The lag/stuttering is probably the battery throttling kicking in. If I remember right, it's around 40% on stock. Custom ROM/kernels will adjust this.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Ok. I'm sure its battery replacement time. Using device since 3 yrs your comment is 100% valid about voltage throttling. Thanks buddy.
Btw I kept n6 for screen and front speakers seems pixel xl is here to rescue me.
Hello,
I want to manage power outlets for charging my phone based on the battery status.
Are there any (wifi controlled) power outlets/sockets which can be managed by tasker?
Best regards
Bacardi Man
No personal experience, but googling on "tasker wifi home automated outlet" seem to bring up options.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
When I see my friend use his one Plus 5 something, I find it so fascinating how snappy it is.
Why can't Nexus 6 also stay snappy by only sticking to bare minimum application? The CPU and GPU can't be that slow to handle menial tasks such as WhatsApp and browsing yet my phone feels laggy.
Firefox lags so much so does switching between apps after not clearing up the RAM which gives slight improvements until it starts to get filled up again.
Does it mean I'm doing something wrong with my phone?
My N6 is fine. When was the last time you clean flashed? if internal storage is nearly full, then that can contribute also.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
no encryption, a good old stock rom with the right kernel optimized for your daily usage, no social media app eating ram usage and constantly waking up your phone every 2 minutes, a fstrim every week + cleaning from time to time cache and data. ANy other idea ?
Complete device wipe. Install Nitrogen 8.1.
[NG]Owner
Help! After latest "update", Bluetooth is the only thing showing in battery stats?
OK, so there was a new stock "update" and an old problem came back, namely that my phone shows Bluetooth as the only thing using battery. I had this a while ago (in this thread here about "crazy mega bluetooth battery drain") but the same fix of resetting the logs does not seem to be working.
A short time after charging the phone and resetting the logs, the phone shows Bluetooth has a CPU total of 0s, Keep awake of 7s, and computed power use of 17895mAh. No other process is listed as using battery!
The phone is stock, not rooted, "updated" to N8I11F with the OTA that came last week.
Anyone know how I might resolve this?
Various solutions have been discussed in this thread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Various solutions have been discussed in this thread.
Click to expand...
Click to collapse
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.
ModemJunki said:
Well, thanks again. I've tried turning off the Bluetooth headset in the Google app (Google app->Settings->Voice).
I guess I'll know after I use Bluetooth next if it helps or not.
Click to expand...
Click to collapse
OK, yesterday after I drove my car which has Microsoft Sync 2, the bluetooth problem returned. So I went through the threads again and did found that maybe the reset wasn't working because I was charging with an LG charger at work. So I tried topping off the battery with the OEM turbo charger (and not using a Qi charger either). Tethering is off as well.
But this is also not seeming to work. After 22 hours, BT is showing 23% battery use (though I do now see other apps in the battery stats).
Still looking for a solution.
Did you turn off instant tethering as suggested in that thread?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Did you turn off instant tethering as suggested in that thread?
Click to expand...
Click to collapse
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.
ModemJunki said:
Yes, instant tethering is off.
I can confirm that if I charge the phone and don't use Bluetooth, the problem does not exist. I was able to let my phone run for 24 hours and the battery stats were normal, showing more than 1 day of runtime at the beginning.
As soon as I connect to my car, then only Bluetooth shows in the battery stats and the battery life is reported as shortened considerably.
Click to expand...
Click to collapse
I'd factory reset at this point. Something is wacky and it's not wide spread.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I'd factory reset at this point. Something is wacky and it's not wide spread.
Click to expand...
Click to collapse
I was hoping to avoid that but I'll give it a shot later today or tonight.
ModemJunki said:
I was hoping to avoid that but I'll give it a shot later today or tonight.
Click to expand...
Click to collapse
Fingers crossed that once you put in that effort, the problem is fixed. You could try going into safe mode and see if that resolves things. Safe mode will reset ROM/system settings, but you won't lose your apps.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Don't do it, it's not going to work.
I learned how to live with battery drain stats
I'm on Oreo and doesn't matter what custom ROM I'm on this annoying issue occurs always when I keep my BT open, but not connected to any device
I've tried all the "fixes": not optimizing the BT, clear the BT cache, clear the bootloader logs, disabled the BT tethering etc... none of them helped.
When I connect to a device (headphones, or car) the consumption is normal and very low, no problem of showing the correct figures in Battery menu.
The issue occurs only if BT is not connected.
I can't believe this issue has not been reported yet to Google, but it seems they don't care about it...
Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...
ModemJunki said:
Well, after using Safe Mode, no difference. I think that even if I don't use a Bluetooth device the problem comes up after a while.
How can we report this to Google? They don't support the phone any longer...
Click to expand...
Click to collapse
Use the Nexus support forums.
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Is your battery original? The only time I have personally had to trouble was when my battery started failing. It was a precise to the early shutdowns and when I replaced the battery, I never had the problem again. Not on Nougat or Oreo.
Click to expand...
Click to collapse
Yes, original battery. The phone was purchased as new old stock last August. The battery is good, runs all day with heavy use, or more than a day when I'm not using the phone much.
Well, all I can tell you is this doesn't not exist on every phone. And unlike the earlier post indicating it's an inherent problem on Oreo, the attached screenshots show that's not true on my device.
The first image is after some time with Bluetooth on but not connected and the second with a device connected.
OK, so Google support connected me to Motorola support and they had me try clearing my storage cache which did not work. I will try calling them back tonight as I have a case open.
If that doesn't pan out I'm going to try doing a factory reset and setting up the phone as a new device - I've not done this before so I hope it's straightforward. Then I will use the phone stock for a day to see what if anything happens. If it's all good I will re-add my applications one at a time. I don't have all that many apps on the phone.
It might have to wait since I have some other work and household projects going on, but if I do find the root cause I will post back here.
OK, reporting back. Motorola support was polite but unhelpful. Reset the phone, reset the logs, oh thats it - out of warranty, replace the phone for $$$ even though it was our OTA that caused the problem.
No thank you, Motorola. I'll spend my money elsewhere after you broke my phone.
However, my complaints aside, I am tentatively pleased to report that the behavior has changed, and if it keeps running this way I'll hang on to the phone until it's well worn.
The change is that now even though only Bluetooth is shown as battery draining, the phone shows more normal battery stats so it's like it was before the update. For example at the moment I have 68%, 1 day 6 hours left, 14 hours after last full charge (I charged it and let it sit idle overnight, then today have been re-installing the few apps I use like Authenticator, Outlook, Facebook, WhatsApp, WyzeCam, DropBox, Dark Sky, Alarm Clock Xtreme). The only change made from stock was to turn off Bluetooth tethering in settings and to turn off Bluetooth headset in the Assistant. Before this, after connecting to my car radio and driving for 30-40 minutes or so, the battery estimate would drop from >1 day to 7-8 hours. It did not do that today so I figured I'd try and reinstall my apps.
This change is purely by chance, I am not certain that this can help anyone else. Here is what I did:
1) Backup local data.
2) Reset phone to factory from the menu in Settings.
3) Setup up phone as a new device.
4) Turn off Bluetooth tethering in settings.
5) Turn off Bluetooth headset in the Assistant.
6) Shutdown, clear logs.
7) Restart, install Battery Calibration app (Imobs Ltd.) (paid version).
8) Run a "Premium Calibration".
9) Charge phone to 100% using the OEM TurboCharger.
10) Let phone sit idle overnight.
I'm hoping the behavior sticks after I reinstall my apps. I'll post back if it does not.
It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.
ModemJunki said:
It's been a while and I was going through my phone cleaning up pictures when I remembered this thread.
So I opened my battery settings on the phone and somehow the battery statistics are working properly - I see a normal list of items for power consumption.
I am confused because I have not made any further changes to the phone settings or attempts to solve this aside from uninstalling Battery Calibration and using AccuBattery to keep an eye on battery life, but those changes were made months ago.
Click to expand...
Click to collapse
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.
alryder said:
Did you update your Oreo ROM to a newer version? I am running ABC ROM and my battery stats weren't working until a recent update. It never bothered me so I never made any attempts to fix it, it just started working on its own again.
Click to expand...
Click to collapse
No updates for me - I'm running stock build N8I11F.
It must have been an update to some other component that fixed it. I can not think of any other way for it to suddenly be "fixed".