Related
Hi
I'm looking for a SW to display current consumption on my Touch HD in order to check which program I use drains my battery
In particular I would like to measure the GPS consumption because I think this is the main reason
I tried acbtaskman but it can't read the power consumption
- This SW can keep monitoring and display a history graph even when the device is "OFF"
- the SW show power consumption only during charging
I also tried home screen++ that has a thread here but this program only shows one number and not historic graph
Would appreciate your help in finding the right program or setting parameters
Moti
You could give PowerGuard a try
even powerguard ist not able to read consumption on Blackstone.
Is there any other tool?
I had no problems with battery since I´ve deinstalled some software. but now it´s unbelievable bad.
How can I solve this?
There's no immediate correllation between consumption and a particular process running or installed on your device. It's the way that certain software is designed that may cause increased consumption, but it's almost impossible to catch unless you know how exactly this software is impacting your battery life.
Hard reset, install your software one at a time and watch battery life.
Once you have found the culprit, hard reset again and don't install it this time.
I've been using "battery guard" which seems to do similar to what you want. It only gives you a total,however you can add and subtract what you want to monitor ie. GPS,Audio etc, and that should help somewhat.
My battery consumption is also higher than I would expect (about 180mA with nothing turned on)....I'd be interested to hear what other peoples usage is.
My battery consumption is 180-190 mA too (basic sw running and light on). Seems quite high.
When charging PowerGuard (v1.3) shows some 200-210 mA, can I assume that the charging current is ~400mA?
Is there a way to decrease the power consumption?
Thanks
2 amp car charger
Not sure,but I think you get 500mA charge from USB & 1A through powerpoint. I've been trying to find agood car charger as 500mA doesn'tcut it when running GPS. I found a 2A one
http://www.netimes.com/shop/2000-ma-miniusb-htc-mobile-car-charger-p-1342.html?cPath=80_612
I'm still trying to figure out if 2 amp is safe. I think the phone limits input so I think so. If anyone knows better, please enlighten me.
Sammy
At home I use 2500mA charger
In the car I use a 2000mA charger
The vaiues measured by PowerGuard are s mentioned above (~400mA)
Battery Guard Developers Page
Battery Guard Developers Page
http://mobile.dlugosz.net.pl/Products/BatteryGuard/tabid/59/Default.aspx
Which 2A car charger do you use?
zolom said:
At home I use 2500mA charger
In the car I use a 2000mA charger
Which car charger do you use? and how long have you been using it? I just noticed the only review on the one I looked at was verynegative. Says his device was killed on the 2nd use.
Click to expand...
Click to collapse
The car adapter is new; details here
The home adapter (with selectable votages) is used for 2 month allready with no issue. This is soething that was bought in an electronics shop.
Hello, i just installed powerguard v1.3 but when i tried to open it its says..
"error..missing method exception, this application requires a newer version of the microsoft .net compact framework than the version installed on this device? whats that mean guys?
Cheers Paul.
mr london said:
Hello, i just installed powerguard v1.3 but when i tried to open it its says..
"error..missing method exception, this application requires a newer version of the microsoft .net compact framework than the version installed on this device? whats that mean guys?
Cheers Paul.
Click to expand...
Click to collapse
Try this
http://www.microsoft.com/downloads/...49-3c6b-42f1-9fd9-0041345b3385&DisplayLang=en
or here
http://forum.xda-developers.com/showthread.php?t=347537
Sammy
netimes.com Sucks
samlives said:
Not sure,but I think you get 500mA charge from USB & 1A through powerpoint. I've been trying to find agood car charger as 500mA doesn'tcut it when running GPS. I found a 2A one
http://www.netimes.com/shop/2000-ma-miniusb-htc-mobile-car-charger-p-1342.html?cPath=80_612
I'm still trying to figure out if 2 amp is safe. I think the phone limits input so I think so. If anyone knows better, please enlighten me.
Sammy
Click to expand...
Click to collapse
Ok so I went ahead an bought this one.....piece of ****....I should have known.....
It doesn't supply 2 amps (even though it says so on the box. At best, it delivers 500mA. I went back to the site and they no longer supply it....looks like I was the final sucker to fall for their false advertising.
Try this little app
Cheers Spartan
Nice little program.
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
EDIT 1: after some more testing You can go upto MAX 1600MHz (Your mileage may vary)
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
streetsmart999 said:
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
Click to expand...
Click to collapse
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Kukl said:
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Click to expand...
Click to collapse
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
streetsmart999 said:
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Click to expand...
Click to collapse
I try it immediately, I hope it works!
Thank you very much
Kukl said:
I try it immediately, I hope it works!
Thank you very much
Click to expand...
Click to collapse
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
streetsmart999 said:
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
Click to expand...
Click to collapse
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Kukl said:
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Click to expand...
Click to collapse
Humm... Anyway @1600 mine died at 30% .. So made it 1500 and past below 18% and Still running. So I guess 1500 is max I can go
Also Before coming this conclusion: I did the fowling
Charge 100%
Delete Batterystats.bin
Run this command from adb "adb shell dumpsys batterystats --reset"
And then Changed the CPU max (Please NOTE , Select "On Boot" to keep the same parameters). Once u change the CPU settings .. Reboot and see .. if its keeping the same settings.
Many thanks. I tried all of the the things you tried and setting the cpu max frequency is the only thing that worked.
I could get away with seeing it to 1600.
Deleting batterystats.bin does nothing https://www.xda-developers.com/goog...-battery-stats-does-not-improve-battery-life/
Now with a new battery, PureNexus Rom and your amazing fix my Nexus 10 is a thing of beauty again.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO..
Click to expand...
Click to collapse
Streetmart you absolute legend. I'd never thought I'd see the day my Nexus 10 would drain down to zero again. I tried 1600, then 1500, to no avail; then I said screw it I'll just go down to 1200 (with little hope of it working).
It feels so weird to actually have an internet “solution” work. I'm super happy. I didn't want to buy another tablet. I love this one and it worka perfect for what I use it for.
Thank you! :good::highfive:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Icetech3 said:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Click to expand...
Click to collapse
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Hez0 said:
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Click to expand...
Click to collapse
What a difference... i installed that a few days ago, and i haven't used my N10 much but on standby it's still at 99% usually it would be WAY lower.. i think that program did more than just lower the max cpu a little.. don't care though. the N10 lives on!!
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
I'm currently running at 1600 with this guy modified kernel and wow, besides no more suddenly shutdowns it runs very smoothly, it reminds me the pre-marshmallow age of this tablet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
Where are you finding these control settings to change?
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Der_Graf said:
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Click to expand...
Click to collapse
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
If i reduce the CPU speed from 1700MHz to 1200MHz I get to go down to 20% instead the N10 shutting down abruptly at just 30%
I do have a spare battery in the fridge for later on. Once I open up the N10, I'll see if there is a capacitor or two, that could replaced in the power supply area to possibly fix the issue.
Note:
1. On second full charge since lowering the CPU to 1200MHz the battery got down to 14% & I have decided to charge it instead of letting it die at some point at a lower percentage
2. I should have mentioned earlier, that I still use the original N10 battery & plan to replace the original battery with a new aftermarket battery later on if I need to.
3. I use the N10 in an air-conditioned room for no longer, than half an hour at a time only browsing & reading articles with a short 10min video from YouTube.
4. Before lowering the CPU clock from 1700MHz to 1200MHz, the tablet consistently has shut down abruptly, at 27-30% battery level to my dismay.
5. Tried complete battery drain / cache reset to 0% in Recovery mode & then fully charging it while shut down 3 times without success.
6. So far lowering the CPU clock has made a difference & for prof now I am evaluating the N10 battery capacity with AccuBattery.
7. I charge my devices at around 20-25% or higher up to 80% to prolong battery life using apk's to stop charging or alert me.
I have switched to the UNOFFICIAL Resurrection Remix for Nexus 10 (ResurrectionRemix-M-v5.7.4-20161208-manta) MM ROM after rooting my N10 (Danke schön Corinna ) & had to update the baked in Kernel Adiutor.
Installing from APKMirror the "Kernel Adiutor (ROOT) 0.9.73 beta (Android 4.0.3+)" has allowed me to lower CPU MAX Frequency and have it stick after BOOT!
com.grarak.kerneladiutor_0.9.73_beta-241_minAPI15(nodpi)_apkmirror.com
Ottoman Mint said:
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
Click to expand...
Click to collapse
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Der_Graf said:
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Click to expand...
Click to collapse
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Ottoman Mint said:
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Click to expand...
Click to collapse
Sometimes it shuts down at 20% and other times it won't. I'm almost pretty sure it doesn't have anything to do with advanced power settings or any kind of internal power settings with the kernel. There are no thermal configurations on this device and they don't add any drivers for it or support for it until much later versions. Heat seems to play a role especially down here Florida when outside. So far in my experience it's most likely to shut down at 20% if it's too hot and not likely to do so if it's been idle for a bit or not plugged in.
Sent from my Samsung Nexus 10 using XDA Labs
While I've had many Android phones, this is the first phone that I decided to use a battery charging controller to regulate how my battery is charged. I just wanted to share my journey with others and encourage others to try this out if you are not already.
Although there are several different battery charging controllers out there (and more than one named "ACC" which makes it even more confusing) I decided to use the Advanced Charging Controller module developed by VR25. I choose this module because I felt it provided the most customization.
Step 1 - Installation
Installing the module is easy. It is listed in the Magisk repository. Simply browse the available modules and find the one titled, "Advanced Charging Controller (acc) created by VR25 @ XDA-developers". There are several ACC modules, so make sure you install the one by VR25 to follow this thread.
Magisk will flash the module and start it automatically. You don't even need to reboot, although it is the only way to clear the Magisk notification that the module will be started at the next reboot.
Step 2 - Changing the Charging Switch Setting
I found that the default charging switch setting (auto) does not work reliably with our phones. Therefore I would suggest changing it using the commands below. Personally I have choose option 2 (battery/charge_disable 0 1) but I listed all the options with the quirks that I have found with each one.
Step 2.1 - open your preferred command line app - I use Terminal Emulator.
Step 2.2 - type "su" and hit enter to gain root
Step 2.3 - type "acc -s s" and hit enter - this is the command that allows us to select another charging switch
Step 2.4 - type what number of the charging switch you want to use.
Here are the available charging switches and the issues I have found with them:
1) Automatic - this switch tries to cycle through the available switches until if find one that "works".
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: No - I found that the phone would charge anytime it was plugged in and below the Pause threshold. It did not seem to wait until the battery level was below the Resume threshold.
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:
2) battery/charge_disable 0 1 :
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): Yes
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: ???
- Suffers from wakelock issues when phone is plugged in but not charging: It does have a "overheat_mitigation" wakelock when on the battery idle mode, but because the phone is not using the battery power, it doesn't effect battery life and therefore I don't concern myself with this issue.
- Other issues:3) battery/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): Yes
- Charges and discharges according to the cooldownratio: Yes
- Works with battery idle mode (the phone will pull power from the AC power and not the battery when the battery reaches the Pause threshold): No - phone begins discharging from battery when Pause threshold is reached but the phone is still plugged in
- Begins charging when phone reaches Resume threshold: Yes
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging: No - may show charging icon when phone is really discharging, especially during cooldownratio times and the chime doesn't always ring when charging resumes.
- Suffers from wakelock issues when phone is plugged in but not charging: No
- Other issues: The phone seems to follow the cooldown charge/discharge times even before reaching the cooldown threshold. I find the phone pausing for 10 seconds (my cool down ratio) when the batter level might be a 50% - long before the 60% cooldown threshold I have set in the config file.4) dc/input_suspend 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:5) battery/charge_control_limit 0 1:
- Passes the ACC switch test (type "acc -t"): NO, so this switch doesn't work with ACC
- Charges and discharges according to the cooldownratio:
- Starts discharging when the phone reaches the Pause threshold:
- Begins charging when phone reaches Resume threshold:
- Charging "chime" and battery icons correctly reflect if the phone is charging or discharging:
- Suffers from wakelock issues when phone is plugged in but not charging:
- Other issues:
Step 3 - Configuration
You can configure the ACC controller using a couple of different methods. You can do everything using command lines, you can use the beta ACC app (see note below), or you can edit a config file that ACC creates when it is installed. Personally I found that editing the config file was the quickest and easiest method to make general changes.
The ACC config file is found at /storage/emulated/0/acc The file is named "config.txt" You can open the file with a text editor. I personally use the app Root Explorer. I long click on the file name, and then press the three dot button in the upper right hand corner. Choose "Open in Text Editor" and the config file will open and allow changes to be made. Saving the file will automatically push the changes to ACC, you do not need to reboot or restart the ACC daemon for changes to take effect.
I won't go into a lot of detail about all of the different configuration options here as the developer's xda thread is the best place to get that type of information. But I will talk about the most basic setting - the "capacity" setting. It is the second setting listed in the config file and it should look something like "capacity=0, 60, 70-80". Here is a break down of what those numbers mean:
- The First Number (0): is battery level were the phone will shut off. The default setting of 0 means the phone will turn off when the battery level hits 0. Personally I don't want my battery completely draining, so I have it set at 5.
- The Second Number (60): is the battery level where the module starts it's "cool down" functionality. Cool down (listed as coolDownRatio in the config file) is where the phone will stop charging briefly and then restart charging. The default "cool down" setting is coolDownRatio=50/10 which means the phone will charge for 50 seconds, and then stop charging for 10 seconds before charging again for 50 seconds, etc, etc, etc. This is designed to keep the battery temps low. A battery with a charge level less than this number (60 in this example) will charge without pausing, but when the battery level gets to this number or above, the phone will charge and pause based on the coolDownRatio.
- The Third Number (70): is the "resume" value. If the phone's battery level is below this resume value, the phone will charge. If the battery level is at or above this resume value, the phone will not charge even while plugged in.
- The Fourth Number (80): is the "pause" value. This is the battery level where the phone will stop charging and should not charge above this value.
The default settings are set this way because research has shown that a phone's battery will last the longest with the least amount of battery capacity loss if it is charged to a max of 80% of the battery's capacity, and allowed to discharge just a small amount (10%) before being charged again. I realize this goes against the old "wives tale" that our phone's batteries have a very limited number of charges and it is best to limit the number of charges by only charging the phone when it gets to a low level. This is not true in actual battery performance however and if you charge like this, you are actually decreasing your battery's life expectancy and performance.
Obviously the default settings may not be the best setting for you. The default settings are probably only practical for a device that is plugged in 100% of the time. Personally I have changed my capacity setting to capacity=5, 60, 70-90. This means my phone will turn off when the battery level reaches 5% (something it has never dropped to yet), it is charged to a max of 90% and will discharge to 70% before charging again, and the cooldown charging cycling starts when the battery is 60% or higher. Obviously I'm not on my charger all the time, so it is very common for my battery to drop below 70%. However, if the battery is below 70% and I have a charger at my disposal, I am going to charge the phone back to 90% rather than let it the battery levels continue to fall.
Final Notes and Misc Thoughts
There are lots of other options and commands you can use in ACC. Feel free to share any changes you like to make, or post if you are having problems getting the module to work as expected on the 3a. I hope this helps some people feel give the module a try.
There is an ACC app that is available now that allows you to control some of the settings from a nice GUI. I personally did not like using it as I found it would overwrite settings in the config file that I was not intending to be changed.
There is an ACC telegram group if you want to join and have direct communication with the developer and others.
Thanks to @jellopuddingstick for educating me on what the battery idle mode does and why it is beneficial to have it working!
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
pbanj said:
if you want to extend your batteries life, one of the best ways is to not fast charge it. fast charging not only degrades it a bit faster because of the amount of current, but it also tends to heat the battery up more which makes it degrade even faster too. heat is the main reason i tell people not to use wireless charging.
Click to expand...
Click to collapse
This is why I always use a low current charger unless I absolutely need a quick charge. I have used the Dash charger that came with my OnePlus 5 only about 10 times in 2 years.
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
sic0048 said:
As I use my phone more, I realize that none of the charging switches seem to work 100% of the time as expected. I'll continue to do trial and error tests, but please share if you find a switch that works consistently.
Click to expand...
Click to collapse
I was having issues with ACC not working before installing the apk. I'll report back if I have any issues.
Nice guide BTW.
I've continued to edit my original post to provide as much information about the different charging switches and the issues I see with each one. Hopefully it is easy to understand.
I still find myself defaulting to the 3rd charging switch option and while it can act a little erratic sometimes, it does work normally most of the time.
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
sic0048 said:
I'm just curious if anyone has tried the "auto" charging switch in the latest ACC version? According to the release notes, there was some changes made to the auto system as it may not have been working correctly.
I'll try it here in a little while, but thought I would ask.
Click to expand...
Click to collapse
I've been using the apk auto switch, no issues.
Is this working for anyone:
usb/current_max:500000
I have is set in the app as an On plugged option and It is not working for me.
gargleblarg said:
I've been using the apk auto switch, no issues.
Click to expand...
Click to collapse
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
sic0048 said:
The phone discharges at the pause threshold and not simply hold the charge at the threshold percentage?
I found the auto setting showed the same tendencies as switch 2 - not discharging below the pause threshold. But I haven't tried it with the new release which specifically mentioned the auto setting bring changed.
Click to expand...
Click to collapse
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
@creeve4, I can't get the On Plugged options to work either. I tried "./usb/current_max:500000" and "usb/current_max:500000", I tried unplugging/plugging in the charger, resetting the daemon, still no luck. The settings were saved to the config file correctly. No idea.
gargleblarg said:
I'm on 2019.6.14-r1 version.
I charged up to 80% and kept it plugged in to see if it would drop or maintain, it dropped. It took forever.
Edit: 8 hours later and it has only dropped to 78%
Click to expand...
Click to collapse
Interesting. That's unfortunately not what I experience.
I just tried the auto setting and plugged my phone in and it immediately went into what I am calling a "maintenance charge". It was only charging the phone by about 200 mA. I set the charging switch back to #3, unplugged and replugged in the phone and it is charging at about 1200mA which a pretty normal charging current for me.
It's this same roughly 200mA charge that I have seen previously with the auto setting after the phone reaches the set pause threshold - so the phone charges at normal current levels and then drops to the 200mA current after reaching the pause threshold. Admittedly, I did not allow the phone to reach the pause threshold this time (which would take forever at 200mA), but seeing that charging level at all leads me to believe that the auto charging switch is still not working for me (it should either be fully charging or full discharging). I suspect because the phone was above the resume threshold it defaulted to this maintenance charge (thinking the phone shouldn't be fully charged until it dropped below the resume threshold).
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
What was the battery level when you plugged it in?
sic0048 said:
Interesting. That's unfortunately not what I experience.
Click to expand...
Click to collapse
That is interesting, have you tried updating yet?
I should also mention that I have only changed the percentage to 3% for the phone to shut off, the rest of the options are default.
Is anyone else getting the following message in the acc app after updating to the latest version?
creeve4 said:
Is anyone else getting the following message in the acc app after updating to the latest version?
Click to expand...
Click to collapse
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
sic0048 said:
I'm not using the app, so I can't answer your question. I was hoping someone else might chime in if they are using the app.
Click to expand...
Click to collapse
I just needed to update to the latest app version. The module was updated before the app.
Did anyone else lose their config settings when updating the ACC module recently? I updated a day or two ago and woke up to my phone at 100% charge. I started troubleshooting and found that the config file was set to all the default settings. This means the charging switch was set to "auto" which has never worked for me and it explains why the module didn't pause the charging at the default pause setting (80%).
The release notes talked about a lot of changes in the config file, but it never mentioned that users would lose their settings and be reset to default. I was just curious if anyone else experienced the same thing or not.
There's a bit of misinformation / misunderstanding going on here, I think. The best control file for our devices is battery/charge_disable. The "maintenance charge" (ACC refers to it as "idle mode") you're referring to is a good thing! This is explained both in the ACC readme [1] and by the developer of Battery Charge Limit [2][3]. The ping-ponging between the upper and lower thresholds is a fallback, it's not the desired mechanism. Hope this clears things up!
[1] "Charging switches that support battery idle mode take precedence", https://github.com/VR-25/acc/blob/master/README.md
[2] https://forum.xda-developers.com/showpost.php?p=76523599&postcount=1834
[3] https://android.stackexchange.com/a/200037
umm, i would be happy if someone give an advice to me the best configuration for the best battery charging cycle, anyone can help me?
What does it means?
How can I solve it.
I just want to limit the battery and I tried ACC and battery limit but none of them works.
Gerard03 said:
What does it means?
How can I solve it.
I just want to limit the battery and I tried ACC and battery limit but none of them works.
Click to expand...
Click to collapse
Explain more what is going on
AntoXik72 said:
Explain more what is going on
Click to expand...
Click to collapse
I set a charge limit to 80% then I put my phone to charge and when it reaches 80% of battery appears an error in notification bar saying daemon error 7 and the charge doesn't stop.
If you want to limit the battery charging, i mean if you want it to last as long as you want by charging slowly, There's no secret, use a slow wall block. That's the best solution
I Don't really know why someone would like to charge his phone till 80 only but if it's for lithium preservation then that's the best solution i Guess, even if you download an application that is working well on another phone, i Guess it's like a TV, even if it's off, electricity goes by, nothing can limit water to flow by, same for electricity
Have you tried using Tasker with a profile to get this done ?
i don't understand these current flow, voltages, etc... but i am sure it's not possible to charging battery in 3min the values are higher. is this ok ?.
just worried about my battery.
*Custom rom : { Havoc-os v4.19 }.
*Advanced charging controller : { magisk module }>
....... don't know why ?. but. if i use this module charging stops at 70%. and if i remove it will charging 100%. and after 50% the W goes down like 2.0 or 0.1 like that. and time also increase after 50% to 60%.
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
I am not using ACC as usually after sometime I experience some issue or the other. The GUI frontends are especially buggy and I am not a fan of using commands to tweak stuff. I am using Termux commands in Tasker to automate this. Best thing with the upgrade to 4.9 kernel was the ability to limit the maximum battery charging voltage which is the one of the best ways to prolong battery longevity. Thankfully even in A12 and A13 ROMs it continues to work. Some charging switch or the other should enable limiting voltage in ACC I think.
aospray said:
ACC works by stopping charging at 75% by default to prevent battery wear. If you do not like how ACC stops charging at 75% by default, you can either adjust the charge level to 80 or 85%. Or you can disable and deactivate ACC.
@amn1987 might have better ACC settings for our 3s.
Your "3 minutes until full" might be due to both using a fast charger and the battery wear of your 3s.
Click to expand...
Click to collapse
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Maheshmahe said:
How to do that ?. ( by commands ? ). i want to limit it at 95%.
Click to expand...
Click to collapse
Root is necessary of course and use only ROMs based on kernel version 4.9.
In any proper file manager like Solid Explorer or Mixplorer etc. simply navigate to sys/class/power_supply/battery/voltage_max which is located in the root partition and open it as a text file after changing the file permissions to rw-rw-rw from the default read-only.
By default the max. charging voltage is set at 4.4V. It’s in milli Volts. So 4400. 4.05V corresponds to 75% battery charge. 4.15V to ~85% and 4.3V ~95%. I wouldn’t recommend going above 4.2V (which corresponds to 90%) as the battery will be at a constantly high voltage (as battery percentage won’t ever decline as long as it’s plugged in) all the time otherwise. Ideal range is 30-80%(15-90% in newer models). If the device will be used plugged in a lot shoot for 60% (3.95V).
su
echo 4300 > /sys/class/power_supply/battery/voltage_max
I kept the battery at around 80% for the first 3 years when it was used as a primary device and afterwards at 60% as it's plugged in most of the time. Probably that's why battery health is still above 80%, 6 years later. Still lasts almost 10 hours during offline video playback (indoors).
P.S. The voltage under voltage_max resets at every boot. That's where Tasker or Macrodroid or even a script comes in handy.