Related
Well I've had my G4 a few weeks now and rather happy with it, seeing some custom ROM's out there which is great, my only issue I can't get a good answer on the G4 is the battery. I charge my phone on the nightstand next to me nightly (sysadmin on call!) but I will get up 3am, or 4am and the phone is lit (dimmed) on the lockscreen and it's because the phone is 100%.
So can this be disabled and if so how? I need notifications on so can't just diable that, but just searching I find things like this (note this was NOT on XDA)
"Download Du Battery Saver, free app in the app store. It will optimize your phone, tell you what to turn off, give you suggestions on how to keep it cool and help you charge your phone correctly. Never charge these S4's overnight even though some people say it's okay. When it is fully charged you are supposed to unplug it. You charge it when it is 20% or less on a fast charge to 80%, then a slow charge to 100%, then remove the charger. Phone will then not heat up and battery will last a very long time. I am getting 3 days on one charge with this little app"
The reviews on the app look good, but 3 days! I have always used juice defender, but back to the main point/question. Should you be charging overnight, and if it is ok, how to disable the turn on the screen once done!
Note I am rooted and saw some root explorer things to disable, but figured I would ask the real group 1st!
Thanks
The problem is that when the phone reaches 100%, the screen turns on to notify you of such. Guessing that you have the developer option turned on to leave the screen on when plugged in? You want to turn that setting off or else if you're rooted, you can use something like Nottach Xposed module to disable the wake up on full charge.
I'm not sure if my problem is with OxygenOS or Nougat, but I've scoured the internet for months and haven't found an answer
I have two problems that I think are linked to doze mode on my device, and they both occur under the same conditions. First is my alarm clock (Alarm Clock Xtreme) doesn't work in the morning, and second is my Samsung Gear Fit 2 needs manually reconnected each morning. And through troubleshooting I've determined the problem occurs under rather unique conditions. The problem ONLY occurs when my phone is plugged in and sits overnight (so fully charged sometime during the night). Which is most nights, because I want a full battery in the morning.
But if I happen to go to bed and leave the phone unplugged, the alarm clock WORKS in the morning and the smart watch stays connected all night. So unplugged overnight, no problems. Plugged in, alarm clock won't work and Bluetooth connection to smart watch is dropped.
I haven't been able to find an answer in the 3 months I've had my OnePlus 5. Any thoughts?
Specs: OnePlus 5, Oxygen OS 4.5.10, Nougat 7.1.1.
I can also move this post elsewhere if there is a more appropriate area of the forum for this question. But I don't have this problem with my old device.
You can try disabling battery optimization for selected apps.
doggie13_ said:
You can try disabling battery optimization for selected apps.
Click to expand...
Click to collapse
Thanks, but I already tried that. It doesn't work.
It's probably the apps man if you think about it. Try using a different application and report back.
Dchoi229 said:
It's probably the apps man if you think about it. Try using a different application and report back.
Click to expand...
Click to collapse
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.
Liam1694u said:
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.
Click to expand...
Click to collapse
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.
jhs39 said:
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.
Click to expand...
Click to collapse
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.
Liam1694u said:
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.
Click to expand...
Click to collapse
It's recommended these days to keep your battery charged between 40%—80% to prolong its life and not keep the phone plugged in overnight like in the old days. I charge mine to 80% before going to bed.
If it's actually a Doze issue I don't understand why it wouldn't happen when the phone isn't plugged in. Do you have a screen saver enabled?
Fellow OP5 user here, I have the EXACT same problem.
If I leave the phone charging for long time and doze kicks in, the phone basically shuts down for all purposes until I unlock it with my pattern. Meaning, only the built in alarm (that works even with the phone turned off) will work. Any other (Timely, radio...) won't.
Now here's the kicker: sometimes the deep sleep will cause a weird bootloop, upon which the screen will indefinitely hang on the spinning logo, with the screen turned on, requiring a reboot. And of course this makes the alarm not sound.
This last bit happens at random. If I disable the screen sleeping in Dev options, the alarm will work but when I wake up the pattern input screen would be there, after all night on, which isn't really healthy for the screen.
Turning doze off makes this problem apparently disappear, but I need to investigate some more to draw conclusions. For the time being I sleep without charging, quick charge and the phone's great battery makes it unnecessary to keep it connected all night.
Another fun tidbit of this deep sleep mode: it stops USB tethering. I would have imagined a wakelock in there, but apparently there isn't.
For information : I use vanilla kernel and OOS. I have Magisk on and Gravitybox via Xposed Magisk, but other than that I have nothing particular going on.
I've been hearing that from other sources as well, about not letting it sit overnight on the charger at 100%. Which is why I think I'm gonna keep using the smart switch of my nightstand charger. The OnePlus Dash charging system works great for a quick charge anyways, so having 100% fully charged to last all day long is no longer necessary. I have a normal USB cable at my night stand, so it's a slow charge. If I set the timer to stop after an hour it at least gives me a small charge overnight, without overdoing it. And I have dash charger at work to give me the full quick 20 minute charge that puts me at 60-70%.
No I don't have a screensaver running. It is weird that the phone locks in the doze mode for the alarm and boots me off my watch's BT connection, but only when plugged in and sitting at a full charge for an extended time (haven't stayed awake all night to test just how long it has to sit). But that IS what it IS. Those have been confirmed as the only conditions in which this problem arises. I've been using the smart switch for 3 days now to keep my phone from going to and staying at 100%, and the alarm clock is working again and the watch is staying connected.
It's not that it's a big of a deal for me to have to use a work around like this. I don't mind. But I hate finding a glitch in something and not being able to truly "fix" it. Work-arounds work. But they don't actually solve the problem. This is just a gripe I have in general whenever something like this happens. It's in my nature to want things to work properly. Which is why I haven't had a non-rooted device in at least 5 years. I NEED to have the ability to fix the [email protected]$$ sh1t the software developers and phone manufacturers screw up. Of course, that's probably the number one reason xda exist. This open up the full potential of these devices, because the manufacturers are either too dumb or are financially motivated to not fix things (ahem...Samsung). Thank you everyone who chimed in with advice. I appreciate it.
It has been my experience with this phone so far that doze mode doesn't work. At all. I regularly have widgets that won't update even though I have doze turned off...
Just one of the many annoyances that has me thinking about finally rooting and getting rid of this garbage os...
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?
Hello guys,
Do you have any info about this feature.
Seems work well first days.
When I plugged my phone, charging stopped at 80 and 2hours before I wake up the phone was fully charged.
Yesterday night woke up at 4am (was thirsty ?) and phone was already fully charged..
Anyway, do you guys have any info how it works exactly or how to configure it !
Thanks a lot
Cheers
Appreciate the gesture and what it's trying to do, but it is in fact relying on very small components to deliver on a critical part of your device.
My advice, don't charge overnight on any phone, ever. You will develop issues, it's not a question of if it's when.
Your standby drain will last the night losing only a couple of % so why charge overnight?
Turn off optimised charge and let warp do is job.
100% in less then an hour 1-2% overnight loss.
No need for optimised charging at all.
When I had it enabled, it would stop charging at 80% and would start again I think an hour before my alarm. I didn't do any additional configuration, I think it just "learns" your behaviour over time.
I don't have it enabled anymore, though. Like the user mentioned above, warp charge doesn't require overnight charging. I am at about 50% when I wake up and get to 90% in the morning very quickly!
Thanks guys.
Yeah that's what I was thinking as well.
Just wanted to know if someone has more info on this obscure option ?.
Warp charge speed is all I need ??
Yeah sure this warp charge is a blast
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.