Database Develop

Power management - an explanation

I cannot find a decent explanation of some of the power management options available for my Diamond and so I wondered if an expert would mind explaining what the following are, what they do and how much power we might expect to save by enabling them in the power management section of advanced config:
AsyncMac1
PPTP1
L2TP1
I dont want to compromise the ease of going online, my IMAP email polling or my push email through ActiveSync, but of course I am keen to extend battery life.
In addition, I have found that during my 1 hour commute undergroud each day, my battery goes down by about 20%! However, the next hour (in my office), battery usage drops by only around 5-10% depending on usage. Does anyone have any specific advise to help with this? On the underground, the device goes to sleep as well as I am not using it.
Thanks in advance.

The Jones said:
In addition, I have found that during my 1 hour commute undergroud each day, my battery goes down by about 20%! However, the next hour (in my office), battery usage drops by only around 5-10% depending on usage. Does anyone have any specific advise to help with this? On the underground, the device goes to sleep as well as I am not using it.
Thanks in advance.
Click to expand...
Click to collapse
that's normal. using yr phone in a place where the reception is not good will drain yr battery faster.
i can add (there is a relation) that the level of radiation that any phone is emitting it is also higher when reception it is not strong enough. i've seen it demonstrated yesterday. entering in yr car double the level of radiation, in an elevator the radiation increases 10 folds! yr phone tries to connect and that's energy consuming and radiation emitting (electromagnetic).

KukurikU said:
that's normal. using yr phone in a place where the reception is not good will drain yr battery faster.
i can add (there is a relation) that the level of radiation that any phone is emitting it is also higher when reception it is not strong enough. i've seen it demonstrated yesterday. entering in yr car double the level of radiation, in an elevator the radiation increases 10 folds! yr phone tries to connect and that's energy consuming and radiation emitting (electromagnetic).
Click to expand...
Click to collapse
Thanks for that. Now I am not sure if I should try and solve this problem or throw away my phone and save the radiation
But just in case I choose to keep using it, is there anything I can do to mitigate this rapid power loss at all? Is there a setting which will stop the phone from trying too hard in these circumstances?

Check this out:
http://www.wikihow.com/Make-Your-Cell-Phone-Battery-Last-Longer

The Jones said:
Thanks for that. Now I am not sure if I should try and solve this problem or throw away my phone and save the radiation
But just in case I choose to keep using it, is there anything I can do to mitigate this rapid power loss at all? Is there a setting which will stop the phone from trying too hard in these circumstances?
Click to expand...
Click to collapse
don't save the radiation!
the ministry of health in my country just issue a general warning regarding the danger of prolonged/heavy use of mobile phones. it is strongly recommended to use the phone only in open spaces and with headphones. they even warn the mobile phone users not to sleep with their phone close by. the phone is constantly emitting electromagnetic radiations.
i guess that you bought yr phone not too long ago. i know it sounds strange but after a few cycles yr battery's life is going to improve and i am not the only one to observe it.
don't stop the charging when the battery icon is full. i learned using a wall charger with LED (red for charging, green for charged) that after diamond's icon said 100% the charging continues for at least 30 minutes more (the led was not fully green but was blinking red-green).
from my experience u can use all power management option from shap's advanced configuration without loosing yr connectivity. i can not tell u what those option are but after using all i can tell that diamond's battery life improved.

I have tried using all the power saving options in advanced config tool, but when I restarted my device, I lost connectivity. I couldnt connect to anything. So I set them back to disabled, soft reset the phone and all is well again.
Any idea what that could be?

[APP] [Lesser Dev-Phase] Battery Monitor Graph App **UPDATED 25.03.09**

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.

Drastically Increase Battery Life -|- Tips and Tricks Everyone Should Know *4/26/13*

I've been revamping this thread for new devices for years hoping to share some of the love with newer users. Over the time I've been on android, I've learned a few simple things that can greatly assist in the battery life of our wonderful smartphones.
If you get anything out of the thread, please don't hesitate to rate it and drop me a thanks!
If you read the thread and like the tips, have a new one to suggest, or have a revision, please post it.
On a similar note, moderators, thanks for the sticky!
General Lithium Ion Battery Information - This link includes stuff about charging, including trickle charging aka SBC (Why NOT to use it, or at your own peril)
My tips for good battery life:
Tips for both Rooted and Non-Rooted users
1.Turn off all radios when not in use.
(Bluetooth, wifi, data, 4G/Wimax/LTE, NFC, etc) Use a widget like the default power widgets, Switchpro, or a similar app from the market. *Many rooted ROMs generally allows users to access these radios and other settings from the notification pulldown menu.* The radios of the phone draw power if on even if the user isn't actually utilizing the radio's functions. A radio searching for signal (if you are in a low-signal area) drains more than a radio with good signal, so again, turn 'em off when you aren't using 'em.
To manually turn off radios without a toggle, go to Settings>wireless & networks. This can be accessed from the notification pulldown and hitting the cog icon.
Wifi uses less battery than 3G, so use wifi when you can. Another important setting to note is more dependent on the user. If you live in an area without 4G LTE coverage (check here to see), then go into Settings>Mobile data>Network Mode and check CDMA Only. This will prevent your phone from unnecessarily searching for LTE coverage, which wastes a ton of battery life.
3. I love live wallpapers, and I’ve always been a fan of pixel zombies, but they are really only good for showing off due to their battery drain.
4. Set your screen timeout/brightness to something that fits you.
The screen is the highest drain of battery power on any smartphone. BY setting the timeout, you can prevent your phone from staying on when you don’t manually turn off the screen. Also, manually turn off your screen when you’re done with your phone.
Another huge tip is to turn on automatic brightness (it is enabled by default). This greatly reduces power consumption by constantly changing the brightness of your display, tailoring it to your needs.
Settings>Display, gestures & buttons>Sleep
I use 30 seconds.
4. Task killers used to be all the rage, but no longer.
Here is the ultimate, in depth, graphically assisted, explanation by the famous Fresh ROM's chef, Flipz. Shortly, in light of recent testing, really don’t do anything but force apps that the android OS needed to be open, and thus didn’t close, to re-open. So try not using them, unless for stuff like trying to figure out why your phone isn’t sleeping with system panel. You really won’t notice a performance difference, and the adverse effects you aren’t seeing will stop
+=+ A good alternative is the application SystemPanel Pro. It has a free version, but I highly reccomend purchasing the paid app. It basically monitors everything going on with your phone's usage both in real time an in terms of usage history. If your battery is draiging fast, it tells you what app was doing it, how much it was doing it, and allows you to stop it.
5. I'm sure you have all heard around that your phone isn't "sleeping".
This is referring to the phone's "awake" time, hence the name. When you go to Settings>Power>History. You can compare the lines from awake to screen on versus time on. "Time on battery" refers to the amount of time since the last reboot. The "awake time" is how long the screen has been active. The problem is, a lot of the time, due to the endless possibilities of inconsistencies between apps/ROMs/kernels/phones, the phone will not go to "sleep", drawing power proportionate to the screen being in use when it reality the phone is sitting idle.
If you compare these times and they are the same, or if you note the difference (turn off the screen for a minute, then re-check and they are the same), then your phone is not sleeping.
One solution is to reboot.
I recommend two apps to help monitor:System Panel and Better Battery Stats. These two apps (explained in their FAQ's and descriptions greatly aid in finding those rogues.
Usually, SystemPanel will show an app that has gone "rogue" and is keeping your phone awake.
-This is done by hitting menu>settings>monitoring enabled. Then after some time has passed, ht menu>monitoring>history>change tab to top apps, and see if anything is above, say, 2-4%.
Uninstall applications/reinstalling them slowly, checking after every install to see what is causing it is one tedious but surefire solution.
Lastly,
Follow these steps that I have discovered almost always work.
1. Reboot phone.
2. Instantly upon reboot, as soon as you gain control, open up some type of monitor/taskkiller
3. "kill all" tasks on startup; about 2 times in quick succession should do the trick.
4. Turn off the screen and leave it for about five minutes.
5. Check the up time v. awake time and see if they are the same.
6. If they are, repeat steps 1-5. If they are different, you are good.
6. Apps and Combinations to watch out for!
-Facebook- Tries to sync live feed all the time, HIGHLY recommend unchecking this box, as it creates a massive draw on data
-Skype- This app reportedly (I've seen it myself) likes to sync random data and open up the network for fun. Sign out of app when not in use to fix
-GTalk- This application keeps you constantly connected to all of our google contacts across of your accounts. I have several accounts that I must maintain, and by default the application had me signed in and maintaining a connection with all of them. Open GTalk, then hit each account and sign out to neutralize this puppy. Unless of course you want to stay signed in.
7. Manage your syncing.
This is a big one, and it differs from person to person. Go to Settings>Accounts and Sync, and take a look at what's going on there. Listed app titles means that there is an account syncing data. I, for example, have four email addresses, facebook, dropbox, box, weather, etc. That is bad. You should go through and turn off syncing for nasty apps you might not have known were accessing the internet, or limit the access of apps and services that you do want to allow.
The problem lies in the way this syncing is handled. Each app/service runs on its own schedule, making it particularly likely that your phone could almost always be establishing a data connection and trying to download data for your various apps. See step 2 regarding the app Juice Defender to handle this problem.
8. Vibrate/Haptic Settings
Vibration and haptic feedback eat up a surprising amount of battery. If you have the haptic feedback enabled, then every time you press anything your phone puts out some juice to make itself dance.
Settings>Sound>Vibrate on touch
Some apps have their own haptic feedback settings, and notifications are their own set entirely.
Tips for Rooted users:
1. Try out custom kernels.
By going to the Sprint HTC One Android Development section of the forums, you can see all of the different kernels being developed. These allow for all kinds of modifications like underclocking the CPU and undervolting, both of which save battery. To see how to use them, read the FAQ's in each thread's OPs.
Here is a great guide to custom kernel's by mroneeyedboh.
2. Use Rom Toolbox Pro, SetCPU, or some CPU clocking app in compliance with whatever your custom kernel allows.
This site will explain the basics of SetCPU: http://www.setcpu.com/
-Profiles from SetCPU should usually involve these for battery life optimization:
-Screen off at the minimum clock speed for both, with the max raised on level if sluggishness is apparent
-A temperature greater than “X”
-General power related profiles that lower cpu speed at lower battery levels
(Note that setcpu has fallen off of the radar, but clocking your cpu to levels that suit your needs is still viable, although many argue that the android system's core management should best be left alone. Read up for yourself and make an educated decision)
------------------------------------------------------------------------------------------------------
NOTES:
*Some apps or processes begin to run at startup and keep the phone awake. These apps are not detected by things like spare parts or system panel, unless sometimes represented in the "system" process, in which case its usage will be unusually high.
This shouldn't take more than three repeats, and if it does, you need to factory reset, and slowly add apps back to see what's causing the problem.
___----When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities, consider my position: No matter what you do, the cellphone battery is the cellphone battery. You can tweak it and customize it with kernels, ROMs, and settings, but none of that will turn it into a car battery. The main problem (besides a false sense of pride) that leads to these reports is the misunderstanding of what the usage levels are, so here’s my best summary:
* *Light usage – Phone screen actually on for maybe 0-2 hours. Things like a few texts, some emails, 20 minutes web browsing, etc.
* *Moderate usage – You watched a few youtube videos or similar apps, sustained web browsing, hundreds of texts, some games. Hours range from about 2-5 of screen on
* *Heavy usage – LOTS of video watching and games, pictures or video recording, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
*I’m sure everyone doesn't agree with all these numbers, but this is most likely a good average of what powerusers think. All specific hourage may vary due to differences in phones, batteries, ROMs, and kernels… Which also means that most battery comparisons are pointless; it’s only what you can improve on that counts!
I’ll update this whenever I see good stuff, people remind me, or I remember/come across things I do.
Hope it helps everybody!
Hit the "THANKS" button if I help you!

Good thread, we need more informational threads like this.

Biofall said:
* *Heavy usage – LOTS of video watching and games, 3D pics or video, or some high def gaming/movie watching for at least an hour to an hour and a half in total, with lots of emails and texts, browsing, and other app shenanigans. 5+ hours
Click to expand...
Click to collapse
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.

Stickied for the time being

demo27vol1 said:
This isn't the Evo 3d forum Bio . Good to see another 3vo user around these parts haha.
Click to expand...
Click to collapse
Haha yep!
Nice catch though, there was a lot there to change.

Hello Biofall,
I was wondering how effective is the Snapdragon BatteryGuru app from qualcomm vs juice defender if you ever tried that app before? I have used juice defender with my EVO 3D but I didn't liked the that the app was turning off Wimax even tough my phone was charging while using it.

Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2

Well done.

treIII said:
Not only are we fighting the screen. We are fighting the quad core processor. It seems to be very aggressive.
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
It's aggressive when it feels the need to ramp up. When installing several apps, the damn thing actually gets hot to the point where I put it in the freezer. [edit: this is dumb according to the device's thermal protection] I know that the components shouldn't be reaching those temps....
I'm on the lookout for more info on explicit effects of the quad core on battery life and direct ways to combat it.
eXplicit815 said:
Well done.
Click to expand...
Click to collapse
Thanks! I've been scouring for empirical info for years and I owe a lot of thanks to other people.

Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.

Felnarion said:
Turn off Juice defender. In fact, uninstall it. You will see your battery life is actually improved.
Leave the quad core component alone. If the cores aren't being used, they're offline. Offline is essentially 0 power consumption. The only case I can see improving battery by disabling cores would be for games. Otherwise, its probably detrimental.
Click to expand...
Click to collapse
Juice defender has a large multitude of components. If some parts use more power for you, then you should post which of them you believe they were, before and after, possibly with battery graph screenshots.
On the last quad-core device that I had used there was a problem where the cores would ramp up unnecessarily for small tasks, so there is certainly a possibility for improvement.
On an unrelated note, there are other things that I want to add to this thread, including screenshots, so if anyone has anything to add, just tell me.

What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!

Vincent Law said:
What I don't get is that a lot people seem to believe they know better than HTC's engineers. Doing things like forcing off cores, how do you know that's really saving power? For all you know, the power loss of enabling an extra core for a small task is insignificant to ramping up an already active core to do the same thing.
Sure there are some things you can do to improve power usage (such as avoiding wakelocks) but if you start changing numbers for how internal software power functions work, you should have some damn good reasons why. Even a graph isn't going to be terribly accurate unless you can substantiate the gains across multiple tests. Many of the improvements people mention often have an impact of less than 1% over the course of an entire charge, and that's nearly impossible to even measure. The battery percentage indicator is only an estimation and not only varies between device, but even varies based on the temperature!
Click to expand...
Click to collapse
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Sent from my HTC ONE using xda premium

Edited

Biofall said:
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.

Edited

Originally Posted by Biofall
Sure man, sure. There are surely negatives associated with turning off, down, or generally altering core performance. However, taking the decisions that HTC engineers coupled with HTC software designers implemented for mass consumption as the best option for all users is foolish. The reason we have a development community revolves around that concept.
Several of the things I talk about have an impact in terms of hours the device can function without being plugged into an outlet, which has little to nothing to do with battery percent levels.
Click to expand...
Click to collapse
Battery percent or how long the device is on is still a hard comparison to make.
You could do the EXACT SAME THING on the phone twice, from full charge to dead, and you'd get a different length of time. Batteries aren't that consistent.
A couple things that bother me:
1. You stick the phone in the freezer because it gets warm. The phone already has thermal protections that keep it from overheating. The CPU can deal with far greater heat than you know (70C isn't even a problem). Anandtech was able to run it through the entire gauntlet of its tests (which are much harder on the device than just installing apps) without it ever triggering thermal protection. Most thermal protections exist solely for the battery's sake, which in itself can deal with 50C while charging, or even higher when not.
2. In almost all cases, it is better to let the CPU drive itself as fast and as hard as possible in order to finish tasks. Let it turn on all the cores and such. Because once it's done, it can go back into deep sleep, where everything is off. This is why almost all phones, not just HTC ones, are designed to do just that.
I agree with Felnarion's sentiment. Juice Defender is probably wasting more power just measuring your battery usage than it is helping you save.
Click to expand...
Click to collapse
You could do the same thing and get different results, but in reality strong trends in usage are reflected in battery life.
As for this the CPU discussion, all that I said was that I'd like to look at more in depth studies or core process handling. So it bothers me too.
In regards to JD, it won't be making it into the next revision of the thread, as I have noticed unnecessary draw. Honestly android implemented most of the vital operations into the OS, so it is mostly useless coupled with the other tips and just general awareness.
Finally, the xda app is acting up, sorry for the clutter.
Sent from my HTCONE using xda premium

Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.

Lauski said:
Thanks for the write up. I went from being a little unimpressed by battery life to blown away. Biggest saver from stock is dropping all the SYNC stuff. Totally unnecessary IMO. If you aren't consuming the news and updates (you know actually in the app), you probably don't need it refreshing. Still baffles me this is the from-the-factory type setup.
Phone used to eat 5-10% of my charge per hour with light use and barely make it through my "day" (~15hr away from charger). Now, after 6hrs. since it's been off the charger, I'm still at 91%.
Kill LTE and go to CDMA only if you don't have it in your area either, or it's still rolling out. Seemed to help too.
EDIT: And I should note my scores are with never letting the Data Connection completely sleep, so I can still get emails as they come in which I find important.
---------- Post added at 01:44 PM ---------- Previous post was at 01:17 PM ----------
Here's another tip: Go into Google Talk and make sure to sign yourself out if you don't use/care for the service.
Click to expand...
Click to collapse
Solid tips man. Will update the OP. I always forget to change my mobile data to CDMA only. Also, I had three accounts signed into gtalk, which was unnecessary.

Biofall,
Nice thread.. Very very nice.
The battery issue --
When it comes to people claiming 20 plus hours of moderate/heavy use out of their current setup or other ridiculous absurdities
Click to expand...
Click to collapse
While I actually agree with what you say I do feel a bit different. I base mine on previous usage.
My days really fall into one of three areas. When you get old like me you will see your days are all about the same. :crying: My heavy use is going to be someone else light day.
For me I can judge based on different phones, kernels and roms. The 4g days I needed to have a charger at my desk. There was no way I could get through a whole day regardless of how many calls I made.
Now I am judging verse the LTE I had and and very surprised on how well its holding up even on
my
Click to expand...
Click to collapse
heavy days.
Have you had time to try this yet? http://forum.xda-developers.com/showthread.php?t=2230403
Not sure it works, like you said some of these apps just use more than they save. I am going to see what happens over the next few days and see if I can see differences.
Your Facebook and sync statement, man do those hit home! I still have a few phones at work that these guys don't get it.
Gtalk.. beh turns on when you flash a new rom.. People have to remember to go back and shut that sucker off!
Thanks for your post, I am going to show a few people this, maybe it will open their eyes.

An exercise in battery longevity.

Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min( 652800) Max( 652800) Max.screen off(300mhz)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
Installed gsam for more meaningful data logging.
Unchecked Auto Sync Data in the Data Usage settings
Changed CPU clock min/max 652800
Installed Deep sleep battery saver Xposed module. (on slumber profile) buts phone into deep sleep when screen is off.
If i remember anything else i did on here, i'll post it.
(sorry its taking so long for replies/updates, "new user status" prevents my posts 5 minutes in between.) (hard to believe, been a member since 2011, just lurked alot.)
*May have found lower limit on the CPU, no instability as of yet, however phone is acting a bit erratic, looking into this currently. (booting takes FOREVER. this is a problem.)
*Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
*Changed CPU freq. to min max 652800 based on advice of the community.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?

gh0stpirate said:
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min(960000) Max(stock) Max.screen off(157440)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
If i remember anything else i did on here, i'll post it.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
Click to expand...
Click to collapse
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.

It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.

bblzd said:
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
Click to expand...
Click to collapse
Thanks for the tips! heres what i changed:
installed gsam for more meaningful data logging.
unchecked Auto Sync Data in the Data Usage settings
changed CPU clock min/max 300mhz

Zainiak said:
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
Click to expand...
Click to collapse
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.

gh0stpirate said:
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
Click to expand...
Click to collapse
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.

bblzd said:
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
Click to expand...
Click to collapse
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!

gh0stpirate said:
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
Click to expand...
Click to collapse
Unfortunately I do not, just speculation based off what I've seen when monitoring current draw (using Current Widget) and the battery percentage before and after a reboot.
I do have shots demonstrating low idle drain with Auto Syncs and Locations disabled. On average I'd say my drop is about 1% over 5 hours of deep sleep, but it's always hard to tell because there's no way for me to know exactly when it drops without active logging which would interfere with the phone's deep sleep.

Generally speaking a reboot uses ~1% of your battery. If you're locking your CPU to run at only 300mhz I would just leave it on the entire time. Especially if mobile data is off and so is WiFi. Make sure you go into Settings > WiFi > *Touch the 3-dot menu* > Advanced > Disable "Scanning Always Available". I lose about 1-2% in airplane mode overnight over clocked with high quality sound driver from Viper4Android. Plus the Google now hotword activated everywhere but lock screen.
A while back I did a test with my N5 to purposely nerf its power to see how long of a SoT I could get with it. I did pretty much everything you mentioned in the OP. Locked max CPU frequency to match min. Lowest screen brightness, airplane mode, etc. I was able to get over 12 hours SoT. So if the N5 can get 12 hours with the screen on using the same setup you plan in using with the phone getting nice and warm... I don't think a week standby time is too farfetched as long as it's idle most of the time except for pictures. Depends on how much music you listen to I guess. Only problem is even with music saved on the device itself, running at 300mhz you're going to run into skips and pops. Especially when the screen is off. Music playback will be kinda iffy.
Good luck though and let us know how it goes.
Edit: Actually I was mistaken. I just disabled everything like location, sync, etc. Default kernel parameters except switching to ondemandplus governor. This was on an older release of Uber kernel. 12+ hours SoT with ~30% battery remaining!
Here's my post;
http://forum.xda-developers.com/showthread.php?p=52133394

You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.

KJ said:
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
Click to expand...
Click to collapse
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.

RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
Currently Using Apollo music player, can confirm Zero issues using music playback, confirmed CPU freq. using cpu frequency app. most of these things are using hardware decoders

RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
But if the phone is sleeping soundly as it should.... The max CPU is irrelevant if not being used. The lag and strain to run processes may hurt a lot though.

You let the music play while the screen was off for a few minutes or did you just play it for a few seconds? I have music stutter on screen off with frequencies higher than 300mhz. I get it with 729mhz. If it doesn't happen to you, awesome. Not sure why though. Do you have time to purchase an OTG charger? Might be worth looking into and they aren't that expensive.
http://www.amazon.com/Best-Sellers-...-Phone-Battery-Packs/zgbs/wireless/7073960011

Currently listening with screen off/on full songs. No issues. no time to purchase an OTG charger however :/

Updated main post to reflect newest enhancements.
Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?

It can be done
Sent from my Nexus 5 using XDA Free mobile app

I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,

Flukzr said:
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Click to expand...
Click to collapse
I remembered a discussion along those lines, ill bump the freq. to 652800 min max, and update the main post. An external pack would be great, but i unfortunately just don't have the cash at the moment. between the trip and i just ordered a triple monitor stand and a new wifi usb to play with nethunter

gh0stpirate said:
Screen Brightness set to low as possibe.
Airplane Mode
Click to expand...
Click to collapse
This is basically all you need, the phone will idle for a week or so in airplane mode.

Limit Battey Charge % Android 11

Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge.
Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.

I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.

jljtgr said:
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
Click to expand...
Click to collapse
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
This the settings you have?
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1

hawkswind1 said:
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
Click to expand...
Click to collapse
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1

jljtgr said:
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
Click to expand...
Click to collapse
I think that's the custom setting probably restored from your Google backup. Same one I was using. I'm gonna try it again though, thanks

hawkswind1 said:
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge. Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
Click to expand...
Click to collapse
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).

v12xke said:
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
Click to expand...
Click to collapse
Accubattery is fine and all for reporting and giving an idea of where you want to stop charging... but it has no ability to limit charging. The only thing it can do is nag you to take the phone off the charger. This thread is about root applications actually blocking the phone from charging past a certain level without making the user do anything or even notifying the user about what's being done.

I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.

rcbjr2 said:
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
Click to expand...
Click to collapse
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.

jljtgr said:
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that I use the notification to trigger Tasker profiles, so I was hoping to figure out a way to get it to stop flipping back and forth while also retaining the notification. I think it's just the standard control file since it's a OnePlus phone, but I'm not sure I can figure out otherwise. When I first start using BCL, I found the control file and was able to manipulate it with a SQL editor and Shell commands in Tasker, but I haven't poked around the OnePlus 8T that much yet.

Just as a PSA, I think Adaptive Charging from the January update can conflict with this. On days where I set a morning alarm, I found that my battery was more full than it should be. I suspect that Adaptive Charging does something that Battery Charge Limit cannot block. I won't know for a few days if turning this off in settings fixes things 100% or the January update just really screws with this.

Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com

Well, as a root method it does seem to work. Depending on your taste, it might be cleaner than an app toggling a different variable. Of course you need an app to set the file back to 100 when you want it. Some Tasker widgets work for my purposes... could probably make it a QuickSettings toggle in the shade, actually.

Bottom of that thread, I was wondering specifically if there might be way to force an unrooted device to think it met one of these conditions, so it only charges to 80%.
Specific post link:
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
i.e.
... your phone automatically limits charging to about 80% under certain conditions:
Continuous charging under high battery drain conditions, like game play.
Continuous charging for four days or more.

I've done very little research on this, but I expect the ways to fool the phone into thinking those things are happening is even more complicated than using that root file control. Meaning also requiring root but manipulating other control files.
I suppose you could have a case and a ribbon USBC connector that fools the charging logic into thinking it is constantly connected to a hardware charger even though it's still at a net negative power. After 4 days of having the case on, it might work. I don't know why anyone would have already built something like that, however.

I would root my phone but, as my daily driver, I need things like banking apps to work. They (at least some) detect rooted phones and refuse to load as a security measure (which is probably a good thing) :-(

Banking apps are usually just a frontend to their website used API. They have no problem with you using a browser on a rooted phone or Linux PC, etc. Any app that stores sensitive data on your phone and relies 100% on the filesystem being locked down was created wrong and lazily. The only thing about banking apps that might be legitimate is when things like unique CC info is stored for NFC and using a TPM can't be assured. Most banking apps, however, do not store anything sensitive on your phone aside from a login token which all websites also do. (it's called a cookie)
My personal preference is that no app is better for me than being able to root my phone. I don't play mobile games that want to keep you from cheating and I don't even care about Google Pay, which I'm not sure has legitimate need to block root either... they just do it to keep banks happy, which as I suggested, I think they're full of BS.
The only thing more BS than this no-root nonsense from app companies is when carriers do it by locking bootloaders. I try to re-use my phones for as long as possible and without the ability to limit battery charge, the batteries swell and die quickly, every time. It's good news that Google added code where phones plugged in constantly will limit charge automatically... but I doubt there is a way to trick it from the outside. (without root)

Hmmm. Maybe lazy programming, but I'm not ready to change my Bank so I can root my phone

Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.

jljtgr said:
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
Click to expand...
Click to collapse
I would like to definitely solve this problem I have been struggling with for years. What did you do, can you please help me? It seems extremely similar to what you wrote here.
I have been using battery charge limit on my Xiaomi Mi Mix (1st model) since android 7.1 (lineageos) (and I might have messed with a couple files, not sure, can't remember). When updating to android 9 (lineageos) couple years ago I started having the problem you described. Also I notice sometimes I plug the phone at safe levels such as 35% or 60% and it doesn't charge same thing. Also it only charges with certain chargers and not others.
Earlier today it was 11% battery, could not boot android, didn't charge. I got the idea for the first time to try booting in TWRP (on+volume up buttons) and it immediately started charging at full speed. So there's obviously nothing wrong in the hardware, it's software or just config.
I would like to definitely solve this problem, but I don't understand exactly what you did on your side to fix it. Please reply or message me if you have any suggestion Thank you!