Related
My Galaxy S5 was experiencing extreme battery drain, even while not in use and in my pocket.
After a bit of searching, it turns out I'm not alone. So I thought I'd share my potential fixes to this problem. Your solution may be different to others, so try each one until you find your battery works as good as it should, like mine now does.
Attached is what my battery drain looks like after these 3 tips, even during heavy use.
If you have any extra possible solution, then please post them.
Problem: Android 4.4.2 bug: When location is enabled it causes extreme battery drain. Because it doesn't let the phone sleep.
Solution: Turn off location services until a patch is released.
Problem: Quick Connect not allowing the phone to sleep.
Solution: Root your phone, and either delete or move the APK files: QuickConnect.apk & QuickConnectInteraction.apk from /system/app to somewhere else, such as a disabled folder.
Problem: Skype bug causing battery drain.
Solution: Uninstall Skype until a patch is released.
Hmmm that's strange, my S5 has the best battery life i've ever had on a phone.
I'm pretty sure you turn on the Always ready to connect in Quick Connect that causes thw device unable to sleep.
Sent from my SM-G900H using Tapatalk
nudawa said:
I'm pretty sure you turn on the Always ready to connect in Quick Connect that causes thw device unable to sleep.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
That wasn't working for me. No matter what I did, my battery was being demolished so that I had 50% 3 hours off-charge. Now I get so much more.
craigcrawford1988 said:
My Galaxy S5 was experiencing extreme battery drain, even while not in use and in my pocket.
After a bit of searching, it turns out I'm not alone. So I thought I'd share my potential fixes to this problem. Your solution may be different to others, so try each one until you find your battery works as good as it should, like mine now does.
Attached is what my battery drain looks like after these 3 tips, even during heavy use.
If you have any extra possible solution, then please post them.
Problem: Android 4.4.2 bug: When location is enabled it causes extreme battery drain. Because it doesn't let the phone sleep.
Solution: Turn off location services until a patch is released.
Problem: Quick Connect not allowing the phone to sleep.
Solution: Root your phone, and either delete or move the APK files: QuickConnect.apk & QuickConnectInteraction.apk from /system/app to somewhere else, such as a disabled folder.
Problem: Skype bug causing battery drain.
Solution: Uninstall Skype until a patch is released.
Click to expand...
Click to collapse
Problem: Backlight of the touch keys uses some battery
Solution: Go to settings under Display and turn the backlights off
Problem: Screen uses more power lighting up brighter displays
Solution: Use a BLACK Lockscreen and homescreen
Problem: Air Gestures use valuable battery
Solution: Turn off all un-needed gestures and motions under settings of motions and gestures.
Credit: http://phandroid.com/2014/04/25/samsung-galaxy-s5-first-14-things-to-do/
I was getting the battery drain and slow charging. Removed and reinstalled Google Search and that fixed the battery charging. I couldn't figure out the battery drain so I simply factory resetted it and it has been great since. I am at 30 hours since my last charge and still have 50% to go, with light use.
aft_lizard01 said:
I was getting the battery drain and slow charging. Removed and reinstalled Google Search and that fixed the battery charging. I couldn't figure out the battery drain so I simply factory resetted it and it has been great since. I am at 30 hours since my last charge and still have 50% to go, with light use.
Click to expand...
Click to collapse
You say removing the Google Search fixed you problem with the slow charging of your device ?!? I have noticed that my device charges very slow connected to an USB3.0 port...it only charges with 450mA.
p0tent said:
Hmmm that's strange, my S5 has the best battery life i've ever had on a phone.
Click to expand...
Click to collapse
I agree. Almost 90% of the time battery drain is user error
---------- Post added at 07:15 PM ---------- Previous post was at 07:08 PM ----------
nubsgohard said:
Problem: Backlight of the touch keys uses some battery
Solution: Go to settings under Display and turn the backlights off
Problem: Screen uses more power lighting up brighter displays
Solution: Use a BLACK Lockscreen and homescreen
Problem: Air Gestures use valuable battery
Solution: Turn off all un-needed gestures and motions under settings of motions and gestures.
Credit: http://phandroid.com/2014/04/25/samsung-galaxy-s5-first-14-things-to-do/
Click to expand...
Click to collapse
Backlight keys use very little power
I also use a lockscreen that changes backgrounds (Travel Wallpaper) and have gestures on at all times and my last charge lasted 48 hours and still had juice left . Although what you mentioned above might impact battery drain but only a little and wouldnt cause you to seek answers for poor battery life .Best solution is see whats keeping your phone awake (wakelock)
DirkStorck said:
You say removing the Google Search fixed you problem with the slow charging of your device ?!? I have noticed that my device charges very slow connected to an USB3.0 port...it only charges with 450mA.
Click to expand...
Click to collapse
That can be right, most USB 3.0 ports on laptops and computers do not provide more than 500mA.
For fast charging always use the wall charger. When using the original charger that came with your phone and the original cable (USB 3.0 compatible) your device can pull the full 1800 mA from the charger, since it can sense that the charger is able to handle this safely. When you use a USB 2.0 compatible cable it will only pull 1200 mA from the charger, even if it's an original Samsung wall charger.
I had serious battery problems with my S5 too, battery drained within 8-16 hours. After I removed Skype problems seemed to be solved.
I've had the same problem battery drain only 15 hours I have turned few wifi settings off
Smart network - off
Keep wifi on during sleep - changed to only when plugged in (would have thought this would be default)
Always allow scanning - off
network notifications - off
Hope this helps someone last 2 hours only lost 1-2%
UTH01 said:
That can be right, most USB 3.0 ports on laptops and computers do not provide more than 500mA.
For fast charging always use the wall charger. When using the original charger that came with your phone and the original cable (USB 3.0 compatible) your device can pull the full 1800 mA from the charger, since it can sense that the charger is able to handle this safely. When you use a USB 2.0 compatible cable it will only pull 1200 mA from the charger, even if it's an original Samsung wall charger.
Click to expand...
Click to collapse
Ok. I am using now this kernel ktoonsez KT-SGS5 and with a normal USB2.0 cable I get 1000mA from my USB3.0 port and get 1800mA from my wall charger.
DirkStorck said:
Ok. I am using now this kernel ktoonsez KT-SGS5 and with a normal USB2.0 cable I get 1000mA from my USB3.0 port and get 1800mA from my wall charger.
Click to expand...
Click to collapse
Cool, that means in this kernel some of the original power management restrictions have been removed. It would be interesting to see if the limit on charging via the contact points on the back of the phone (used for Qi wireless charging and by car mounts like Mountr that use inductive charging) now als can accept more than 750 mA...
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
oops, mods please move to appropriate forum. thanks
Thank you. I was looking for it.
The battery don't charge more after unplugged and plugged again with 72%
Charging enable has a wait time of 1 hour. You can change this if you want to enable charging sooner. Wait time thats too short will toggle charge and discharge quickly if device is left plugged in. Not sure what that will do to the device. ?
jonahmt21 said:
Charging enable has a wait time of 1 hour. You can change this if you want to enable charging sooner. Wait time thats too short will toggle charge and discharge quickly if device is left plugged in. Not sure what that will do to the device.
Click to expand...
Click to collapse
OK. Great.
How should i use this ? ?
repulse said:
How should i use this ? ?
Click to expand...
Click to collapse
I didn't get it work either but as no one hasn't given any answers yet I'm going to try... This is what I tried:
1. Import the tasks to Tasker
2. Create a new profile. Select State -> Power -> Power. The source should be kept as "Any".
3. This one is a wild guess but I think you should use the Charge disabled task as the primary one.
4. Add an exit task to that newly created profile. I think it's the Charge enable task.
I left my phone plugged in to a charger and the charging stopped when the desired battery level was reached. However, it never started to charge again. My phone was plugged in for a couple of hours and I had to use my own task to edit the charging enabled file. Did I do something wrong? Any help would be much appreciated.
Edit. Got it working. The charge enable task was somehow corrupted in the import process.
jonahmt21 said:
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
Click to expand...
Click to collapse
Could you please explain why actions 1 and 4 are needed in the charge disable task?
Please read the reference thread. It was already explained there. Thanks
How to change battery level? Do I need to edit the xml file or I can do it at tasker?
Thanks.
jonahmt21 said:
Reference Thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-limit-battery-charge-level-tasker-t3668059
attached are the xml's that works for the OP5T Oreo. ive been using this for a week now and its seems reilable. you can change the values of battery level and wait times.
Click to expand...
Click to collapse
lyrebird said:
How to change battery level? Do I need to edit the xml file or I can do it at tasker?
Thanks.
Click to expand...
Click to collapse
You can edit it with Tasker. Just change the percentage to your liking:
This doesn't seem to be working on OB9. It will stop charging at set level but it will enable charging again after a few seconds. Anybody have an idea why?
jonahmt21 said:
This doesn't seem to be working on OB9. It will stop charging at set level but it will enable charging again after a few seconds. Anybody have an idea why?
Click to expand...
Click to collapse
Have you tried narrowing down the issue? What happens if you manually edit the control file?
It's very unfortunate if Oneplus has started editing the charge control file periodically. I haven't upgraded to OB9 yet and will wait for results before upgrading.
A little more testing...
Removed the charge enable exit task to see if the charging will be permanently disabled, but the charging still enables after a few seconds. Seems like the device is detecting that the device is plugged in and the battery is not at 100% so it enables charging again. Not sure how to get around this. ?
Crap, nevermind, i had a magisk module messing up with tasker. Original tasks still work. Please disregard previous replies. Whew!
Work only on oos or custom rom too
?
Thanks, that's one fewer app.
Running on Liquid Remix.
Duduzinho16 said:
Work only on oos or custom rom too
?
Click to expand...
Click to collapse
Rom version shouldn't make any difference.
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?
Currently running Los 16 with FrancoKernel.
I've used both the Battery Charge Limit app and the AccA app/Magisk Module to limit the charge/discharge levels of the phone. Both apps work great,and I couldn't be happier with them.
My old phone, Pixel XL (1) benefited from the "Battery Idle Mode", meaning, i could set the "charge level" at 65%, and once the phone hit that level, the battery would be bypassed and the phone would draw power directly from the wall. It's my understanding that to achieve this, both the phone's hardware and kernel need to support this feature.
Has anyone had any luck getting this feature to work, or even the Voltage Limit feature in AccA?
It's my understanding that the 1+ kernel doesn't support either of these options, but has anyone had any luck with a custom Kernel?
I also want to know
Any updates? OP, have you found a way to limit charge on 6T?
RobLudo said:
Any updates? OP, have you found a way to limit charge on 6T?
Click to expand...
Click to collapse
I think mcd kernel has this option but no rom have it I believe
I used this and it works well:
Battery Charge Limit [ROOT] - Apps on Google Play
Stop charging at desired level to preserve battery health for most devices!
play.google.com
RobLudo said:
Any updates? OP, have you found a way to limit charge on 6T?
Click to expand...
Click to collapse
Use a slower charger or a different cable.
Using a non-genuine One+ cable should prevent fast charging.
Did anyone solve this conundrum? Haven't had a working config file since 1.1.3. If you do, please share your config please.
I haven't had issues with Acc from the beginning. Following is an excerpt from my config;
Bash:
default_config () {
acc --daemon
acc --set --reset a
acc --set batt_status_workaround=true off_mid=true apply_on_plug=true reset_batt_stats_on_pause=true
# Specific to Nothing Phone
acc --set charging_switch="battery/charge_control_limit 0 battery/charge_control_limit_max --" force_off=true
acc --set max_temp=45 max_temp_pause=90 shutdown_temp=55 shutdown_capacity=5
acc --set pause_capacity=60 resume_capacity=55 max_charging_voltage=3900
acc --set cooldown_capacity=60 cooldown_charge=50 cooldown_pause=10 cooldown_temp=40
}
What does this do?
* Enforces 98% of the time proper shut-off at 60% battery
* Stops charging both wireless and cabled
* No issues with desynced battery status
My Samsung triple wireless charger works flawlessly. I have another unbranded (got gifted) super cheap wireless charger that makes my phone feel warm when charging is turned off.
I actually had issues, but those were AccA and scheduler related. AccA just crashes a lot, up to the point that it's only good for watching battery stats. The inbuilt scheduler didn't work how I wanted, because the CPU sleeps the Acc daemon when not charging, also Acc fails to set new charging voltage/amperages without a recent battery charge applied (the command hangs asking for attaching the charger).
BertProesmans said:
I haven't had issues with Acc from the beginning. Following is an excerpt from my config;
Bash:
default_config () {
acc --daemon
acc --set --reset a
acc --set batt_status_workaround=true off_mid=true apply_on_plug=true reset_batt_stats_on_pause=true
# Specific to Nothing Phone
acc --set charging_switch="battery/charge_control_limit 0 battery/charge_control_limit_max --" force_off=true
acc --set max_temp=45 max_temp_pause=90 shutdown_temp=55 shutdown_capacity=5
acc --set pause_capacity=60 resume_capacity=55 max_charging_voltage=3900
acc --set cooldown_capacity=60 cooldown_charge=50 cooldown_pause=10 cooldown_temp=40
}
What does this do?
* Enforces 98% of the time proper shut-off at 60% battery
* Stops charging both wireless and cabled
* No issues with desynced battery status
My Samsung triple wireless charger works flawlessly. I have another unbranded (got gifted) super cheap wireless charger that makes my phone feel warm when charging is turned off.
I actually had issues, but those were AccA and scheduler related. AccA just crashes a lot, up to the point that it's only good for watching battery stats. The inbuilt scheduler didn't work how I wanted, because the CPU sleeps the Acc daemon when not charging, also Acc fails to set new charging voltage/amperages without a recent battery charge applied (the command hangs asking for attaching the charger).
Click to expand...
Click to collapse
Would you mind sharing the whole config?
miris83 said:
Would you mind sharing the whole config?
Click to expand...
Click to collapse
CLI commands here, the important bits are functions default_config and idle_config.
nothing-phone/acc-setup.sh at d2cb377baed74b3a6f240df88df44fd29503469f · Bert-Proesmans/nothing-phone
Contribute to Bert-Proesmans/nothing-phone development by creating an account on GitHub.
github.com
Attached the daemon config, constructed from the CLI commands.
!! I use acc version 2022-7-30-DEV btw, https://github.com/VR-25/acc/releases/download/v2022.7.30-dev/acc_v2022.7.30-dev_202207300_2206.zip
I truly believe the dev is doing his best to document all things, but I got worn out trying to understand the limits of acc. So I ended up using a single configuration (till 60%) and dropped the dynamic charging profiles.
Acca profiles weren't of much help either because of crashes (i guess the same "connect charger to set charging voltage" issue). Didn't dig deeper since 2 months.
Not sure what's happening with my attachment; I cannot see it myself. Editing my post also doesn't show it.
So I'll workaround this by providing this gist link to the daemon config.
acc-default-conf.txt
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Sorry for the confusion.
* There were no issues with my phone using acc until I upgraded to OS version 1.5
* After upgrading to version 1.5, I had to remove my root modules (because of boot failure) and I slacked on fixing those for a while
** Meanwhile I re-assembled a config from my data above and the phone DOES NOT stop charging at 60% as configured (on version 1.5)
I'm going to find out what's wrong. Best case I might have ran some (extra) out-of-order commands.
Hi, me again!
I've ran my config (see attached) now since new years day.
EDIT; I purged everything acc related from my phone (using the uninstaller package) and started from scratch, even tested all the charging switches it could find.
I used the latest acc development version, which was 2022-7-30-DEV.
EDIT; Don't even open the AccA app before acc is installed and properly configured, because it will install the latest stable of acc and configure it without you approving. Very weird because it explicitly asks approval to install and configure but has done it anyway before you even deny the modal.
The final config didn't change from before actually. At first it seemed broken because I experimented as far until my kernel started lying about the charge/discharge rate. So my phone didn't want to stop charging above the configured threshold.
I gave up, rebooted and left it alone, battery dropped to around 40%. The next time charging (and all following times) it properly stopped charging again at 60% as per config. I'm confused but remember the same 'trick' actually happening in september.
I can't explain why my phone needs to discharge to below the charging threshold before the charging switch properly works, but it does. Probably weird driver shenanigans.
So for me it "just works".
So after 4 days, I've put my phone on a wireless charger at least 40 times. I can say it always properly stops at 60% charge. Around 10% of the times I put the phone on my samsung charger, the samsung charger gets confused and doesn't provide power. This is not misalignment (99% sure), and physically removing the phone for 10 seconds and putting it on the charger again will work normally every time.
This 10% number is certainly a regression in OS 1.5 because before I had <1% charging issues before the upgrade. In the end not that big of a deal for me though.
Don't know why attaching my text file config doesn't work ..
config.txt
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com