No issues with sharing it but the charging control file of OP9 is likely to be different from my Poco F1 in which case it won't work. I have also managed to limit charging voltage and current mostly to prevent battery temps. from rising too quickly.
[APP][ROOT][4.0+]Battery Charge Limit v1.1.1
- Thread starter sriharshaarangi
- Start date
-
- Tags
- battery charge charging limit
Oh. I recently moved my Poco F1 to A11 and no issues so far. In your case I think its a kernel issue probably. In a Redmi 3s only charging control worked in Pie and earlier. But from Q and later (which coincided with a kernel upgrade from 3.x to 4.x) it became possible to limit charging voltage and current as well.
Hello could sombody help me to get it working with Xiaomi Redmi Note 2?
My device is rooted of course but i cant get it working. It is charging always. Even if i changed control file from Motorola Defy+ to Xiaomi Redmi Note 2(hermes).
Or how could i find control file in my phone? I tried using file manager and found /sys/class/power_supply but theres nothing in this folder.
Could somebody help?
EDIT: i found right path and now it stops charging while reaching limit, but "recharge below" doesnt work. i though that when i have set limit to 80% and recharge below 50% - phone should be charged only when reaching <50 and charging max to 80% but it doesnt work.
it doesnt care about recharge below. how can i fix it?
My device is rooted of course but i cant get it working. It is charging always. Even if i changed control file from Motorola Defy+ to Xiaomi Redmi Note 2(hermes).
Or how could i find control file in my phone? I tried using file manager and found /sys/class/power_supply but theres nothing in this folder.
Could somebody help?
EDIT: i found right path and now it stops charging while reaching limit, but "recharge below" doesnt work. i though that when i have set limit to 80% and recharge below 50% - phone should be charged only when reaching <50 and charging max to 80% but it doesnt work.
it doesnt care about recharge below. how can i fix it?
Last edited:
I don't know why it doesn't resume charging when battery charge goes below the level set but you don't need to keep the delta so high. 5-10% below your max. charge is better as it will take much less time and not as much heat. The frequent, small charges aren't damaging.
P.S. Try executing the command to resume charging in Termux or any other terminal client to check whether it's working or not.
Hi all. I have an LG G5 and with stock this app works fine with the universal control file. But if I flash Lineage 18.1, it doesn't work. I've tried a few control files to no avail, can anyone recommend a control file to try for lineage 18.1??
If you know which charging control files have to be tweaked you can use Tasker instead. Works in A11 w/o any issues. I think Macrodroid should also work. I ditch MIUI ASAP in my Xiaomi devices so I can't say if it will work in it or not.
If no modification is possible then perhaps a different kernel is needed. Mi 11 is fairly new so you might have to wait a while. Battery Charge Limit seems to be abandoned. ACC also hasn't seen any updates in months unfortunately.
Hello friends. My phone is Samsung Note 10 plus. This application stops when it is 70%, whereas I set 80%. Is there any ctrl setting you know?
no bro, keep your phone active between 40% and 90% make your battery better so you can charge your phone everytime between 40 and 90%. i had tested on many phones
I just wanted to add for anyone using a Pixel 4 XL, this is the custom control file data you want to set up:
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
Enforce charge limit: disabled
Always Write CFTRL File: enabled
Source: https://xdaforums.com/t/any-way-to-control-charging.4086265/
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
Enforce charge limit: disabled
Always Write CFTRL File: enabled
Source: https://xdaforums.com/t/any-way-to-control-charging.4086265/
Last edited:
Battery Charge Limit is never stopping charging, though it notifies when the charge limit is reached.
Control file /sys/class/power_supply/battery/status exists, but its value is always "Charging", even when the device is at 100% and showing fully charged.
I tried using adb as root to write "Discharging" but when I check the value it is still "Charging".
I first had to change permissions from 444 to 664, and then tried: echo "Discharging" > status
On a Samsung Gio GT-S5660M running Cyanogenmod 11.
Any ideas what's going on and what else I could try?
Control file /sys/class/power_supply/battery/status exists, but its value is always "Charging", even when the device is at 100% and showing fully charged.
I tried using adb as root to write "Discharging" but when I check the value it is still "Charging".
I first had to change permissions from 444 to 664, and then tried: echo "Discharging" > status
On a Samsung Gio GT-S5660M running Cyanogenmod 11.
Any ideas what's going on and what else I could try?
Android 10? This old phone was on 2.3.4, and CyanogenMod 11 (Android 4.4.4) is the most recent ROM I could find for it. I did not try Battery Charge Limit with anything else for the Samsung Gio.
In contrast, BCL works great on an LG G4 running /e/-OS based on Android 9, with control file data /sys/class/power_supply/battery/battery_charging_enabled, 1, 0. Permissions for the file are 644.
I'm wondering if different control file data is needed for the Gio, or if there could be another issue?
Has anyone noticed that the service does not start if plugging in while the screen is off? Once the screen is turned on, the service starts and limits charging.
Haven't encountered this issue in any of my devices so far. Check if Battery Optimization is actually disabled or not.
I just checked and it's not optimized, even though I never put it on the do not optimize list...strange.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
400Please read the following before installing the app:
- This app requires a rooted mobile (Android 4.0 or later)
- Before uninstalling the app, disable limit in the app (if forgotten, reboot after uninstalling)
Usage instructions and app details:
- Enable limit in the app
- Change the limit up to which it should charge (default: 80)
- Check which control file suits best for your device, see Q/A section below for hints. In most cases, the pre-selected choice should be the best that's available for your device.
- The app only gets kicked in while you connect a charger (or USB), and automatically closes shortly after unplugging charger (or USB) i.e it only runs in the background as long as it is plugged in, and won't affect your battery life.
- If your device is not charging even after disabling the limit (which shouldn't happen, just in case), uninstall the app and reboot the device (The changes made by the app don't survive a reboot). Your device should charge normally then.
If the app says "your device is not yet supported"
There are various control files in different devices (due to OEMs), and toggling the values in them (0 and 1) makes it possible to enable and disable charging via software (might not be possible for every device), though the charging cable is still physically connected.
Since we cannot own every device, it is impossible for us to find every file. We can support a lot more devices with information provided by testing possible files on different devices by you, the people in the community.
Hence, for support to be provided to other devices, you need to do some detective work to find the files on the respective devices. Please refer to this file for control files of currently supported devices, so you can know where they are generally present: https://github.com/sriharshaarangi/BatteryChargeLimit/blob/master/app/src/main/res/raw/control_files.json
You can send us a pull request or open an issue on GitHub. If necessary, you can also post the name of the device and the file here.
FAQ
Q) Can you please add support for... (insert arbitrary device name here)?
A) Maybe, but we need your help. Bottom line, this app does nothing but modifying the content of a certain "control file", some more details are given above. If you find such a control file for your device, please let us know (ideally, open a GitHub issue here: https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and we will add support for your device.
Q) I think I observed a bug. Can you fix it?
A) We'll do our best, but we need your help: Please open an issue on GitHub (https://github.com/sriharshaarangi/BatteryChargeLimit/issues) and provide as much information as possible about the problem.
In most cases, we need the "logcat" logs of your device to find out about the exact issue. In order to provide those, you could use aLogcat (https://play.google.com/store/apps/details?id=rs.pedjaapps.alogcatroot.app).
FOR CHARGING-RELATED ISSUES: Select the "Time" format in the preferences of aLogcat, so we can see precise timings, and filter for "(Charging|Power) State" with "Apply as regular expression" ticked.
FOR CRASHES: Please also select the "Time" format and provide unfiltered logcat data that includes the stack trace of the crash.
Q) Why do you want to limit charge to a lower capacity?
A) In short, to prolong battery life in long term usage. For more information, refer this : http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
Q) How does this app work? Does it modify something in the ROM/Kernel to stop charging?
A) It writes "0" or "1" to a control file that represents some state of the power supply hardware, as simple as that. The file is normally read-only, so you need root to overwrite it.
The change might be automatically reversed by the OS if the power supply situation changes. Anyway, it should never survive a reboot of the device.
Q) I can select multiple more than one control file in the radio group. Which one should I use?
A) For most devices, battery_charging_enabled or store_mode are preferable. Try those first and see if it works. If you observe any bugs, try another file.
Q) I have a OnePlus device, and the app doesn't work correctly for me. What to do?
A) Check that the control file you selected is NOT battery_charging_enabled! Although it should be preferred in general, there are known issues for this file with OnePlus devices.
Q) I use the store_mode on a Samsung device. My device always stops charging at 70 % (or other specific percentage), no matter what limit I have set.
A) The store_mode implementation differs among the supported (Samsung) devices.
Normally, it freezes the level at the current percentage when store_mode is triggered until the cable is unplugged for some seconds. This is a normal condition due to Samsung's kernel implementation, it's not a bug of this app.
If this is a problem for you, try to switch to another control file (e.g. batt_slate_mode), if supported.
Q) How does the "automatic stats reset" work?
A) The automatic reset should perform a stats reset when your power supply is removed while the battery level is within the desired range. Everything else is wrong behavior.
Q) No matter if I the "automatic stats reset" is enabled or not, my phone is always resetting my battery statistics. Why?
A) Are you using a threshold above 90%? If yes, your ROM will most likely clear the stats when the power is removed. There is nothing we can do about that.
Downloads:
The app is available on Google Play Store
Alternate APK download links:
v1.1.1: https://www.androidfilehost.com/?fid=674106145207486851
v1.1.0: https://www.androidfilehost.com/?fid=817906626617956614
v1.0.4: https://www.androidfilehost.com/?fid=889764386195927297
v1.0.3: https://www.androidfilehost.com/?fid=745425885120755941
v1.0.2: https://www.androidfilehost.com/?fid=889764386195923345
v1.0.1: https://www.androidfilehost.com/?fid=889764386195919111
v1.0.0: https://www.androidfilehost.com/?fid=817550096634789023
v0.11.0: https://www.androidfilehost.com/?fid=961840155545580765
v0.10.0: https://www.androidfilehost.com/?fid=961840155545576298
v0.9.2: https://www.androidfilehost.com/?fid=457095661767160082
v0.8.2: https://www.androidfilehost.com/?fid=673368273298951679
Please uninstall versions < 0.8 before installing this!
Changelog:
1.1.1:
- Fix charging status layout issues and misc UI fixes @xdnax
- Added switch to disable toasts on service changes @xdnax
- Added switch to show temperature in notification @xdnax
- Ensuring write permissions on the charging control file @real_milux
- Fixed notification sound on limit reach @sriharshaarangi
- Fixed a bug causing crash
- Added Russian translation
- Updated Bengali, German and Brazilian Portuguese translations
- Added control file for Amazon Tate (LineageOS 14.1)
1.1.0:
- UI & icon redesign @xdnax
- Custom control file data support @xdnax
- Improved control file lists @real_milux
- ICS (Android 4.0, API 14) compatibility @real_milux
- Pixel/Pixel 2 support fixes @xdnax
- Added control files for Pixel/Pixel 2, Xiaomi Redmi Note 2, Sony XPERIA Mini, Le 1s, Huawei P10 lite, HTC One, Motorola Defy+, Xiaomi Mi A1
- Bengali translation @AdroitAdorKhan
- Spanish translation @Joseahfer
- Lots of bugfixes and minor improvements
1.0.4:
- New "always write" setting for devices that modify their control files in a problematic way
- Experimental support for Xiaomi MiPad 2, Nexus 5, Nexus 9, Galaxy Nexus (maguro) and Xiaomi Mi6
1.0.3:
- Fixed service starting after boot when disabled
1.0.2:
- Fixed ignoring "ACTION_POWER_CONNECTED" when service was disabled
- Experimental support for Nexus 10, Nvidia Shield and Xiaomi Mi6
1.0.1:
- Added preference to disable limit enforcement aka "state fixing"
- Added expert preference to enable immediate reaction to power state events (be careful!)
1.0.0:
- Tested Magisk 13.x support
- Improved UI
- Even higher service priority (against being killed by Android)
- Online limit change support (limit changeable while service is active)
- Settings with control file selection and temperature scale
- Fahrenheit temperature info support
- Greatly improved "state fixing" with exponentially increasing delay (hopefully fixing GitHub issue #15 aka "rapid cycling")
- Greatly improved SU shell speed/performance
- German translation
0.11.0:
- Improved UI (Using NumberPickers, GitHub issue #13)
- Show voltage and temperature in app and notification (GitHub issue #14)
0.10.0:
- The recharge threshold can now be customized between 0 and the chosen charging limit
- Sending a charging limit of 100 via (broadcast) intent will disable the service.
- Sending values between 40 and 99 will enable and start the service if it was previously disabled.
0.9.2:
- Fixed crash on some devices that are unrooted or unsupported
0.9.1:
- Fixed widget not showing in some devices
0.9:
- Added Widget to toggle service
- Added scrollable view
0.8.2:
- experimental Amazon Fire support
0.8.1:
- Bugfixes
0.8:
- State check after boot (starting monitoring service as necessary)
- Bugfixes
0.7:
- Experimental support for Huawei and Nexus 4 devices
- Support for external control over charging limit
- Bug fixes
0.5
- Ability to select recharge limit (Range: 10%)
- Automatic file selection
- Added store_mode for Samsung devices
- Added option to auto reset stats
- (Huge code refactoring)
0.3
- Updated to support 7.1.1
- Auto-select the battery charging file for Samsung, Pixel and Nexus devices
- Added clear battery stats button
- Auto-whitelisting from Doze mode
XDA:DevDB Information
Battery Charge Limit, App for all devices (see above for details)
Contributors
harsha1397, real_milux
Source Code: https://github.com/sriharshaarangi/BatteryChargeLimit
Version Information
Status: Stable
Current Stable Version: 1.1.1
Stable Release Date: 2018-10-17
Current Beta Version: 1.0.4
Beta Release Date: 2017-09-04
Created 2017-02-15
Last Updated 2020-08-0559Todo:
-Check for charging on device boot
-Widget for quick toggle
- Widget to reset batterystats
-Limit reached alert
- Low battery alert - Needs a service running in the background
-UI overhaul
- on/off switch to enable/disable charging38Announcement: Official Version 1.1.0, welcome @xdnax!
Hello everybody,
it has been quite a while since I wrote my last post here. The reason for this is rather simple:
Apart from being very busy in the last months, I realized some time ago that I was investing more time in reading and answering posts in this thread than doing actual implementation work for BCL, which is definitely not my intended workflow.
Therefore, I shifted my attention completely to GitHub, where the workflow was/is much more efficient.
Some people here suggested to officially fork this project and continue it elsewhere. I want to say the following to those people:
While it is in general a good thing that dead projects are forked and continued, good behavior demands to first open a GitHub issue asking whether the project is to be continued before suggesting an official fork, which did afaik not happen.
Furthermore, a simple look at GitHub would have clearly revealed at all times that I was reacting to issues there on a regular basis, so our project was hardly inactive, and surely not dead!
Luckily, @xdnax was considerate and smart enough to keep mentioning that he wants to respect our work and keep his fork unofficial for the moment, which deserves a huge THANK YOU from my side!
Talking about @xdnax:
He did a great job in contributing to the development of this app during the last months.
Unfortunately, I didn't have his contributions on my radar for quite a while.
Since we love to work with other motivated and decent developers like him, we are happy to announce that he is now the third "official developmer" of BCL.
Welcome to the team, @xdnax!
Some people noticed the appearance of a semi-official version 1.0.5.
Although I never had time to publish an official build, I indeed created this version and uploaded it with a "v1.0.5" tag to our GitHub repo.
This is where the F-Droid build system picked it up and created an APK from it, which I myself wasn't aware of for some while. Sorry for the confusion guys...
During the last days, we organized our internal communication and unified our contributions to bring out a new official version.
Well, here we go: I'm happy to announce that we finally release version 1.1.0!
Link: https://www.androidfilehost.com/?fid=817906626617956614
Please don't get confused about the numbering: This release includes all improvements of @xdnax and more, and is not a major version step because it doesn't introduce any breaking behavior changes.
Happy charging, opening post will be updated soon!
Changelog:
- UI & icon redesign @xdnax
- Custom control file data support @xdnax
- Improved control file lists @real_milux
- ICS (Android 4.0, API 14) compatibility @real_milux
- Pixel/Pixel 2 support fixes @xdnax
- Added control files for Pixel/Pixel 2, Xiaomi Redmi Note 2, Sony XPERIA Mini, Le 1s, Huawei P10 lite, HTC One, Motorola Defy+, Xiaomi Mi A1
- Bengali translation @AdroitAdorKhan
- Lots of bugfixes and minor improvements
22Source code: https://github.com/sriharshaarangi/BatteryChargeLimit
App v0.3: https://www.androidfilehost.com/?fid=745425885120716170
Changelog:
- Updated to support 7.1.1
- Auto-select the battery charging file for Samsung, Pixel and Newus devices
- Added clear battery stats button
- Auto-whitelisting from doze19Update to version 1.1.1
This is mainly a bug fixing update, with loads of improvements. Should reduce crashes as well.
Download link: https://www.androidfilehost.com/?fid=674106145207486851
The update will be available on Play Store soon[UPDATE: Now available]
Changelog:
- Fix charging status layout issues and misc UI fixes @xdnax
- Added (i) Switch to disable toasts on service changes (ii)Add switch to show temp. in notification @xdnax
- Ensuring write permissions on the charging control file @real_milux
- Fixed notification sound on limit reach @sriharshaarangi
- Fixed a bug causing crash
- Added Russian translation
- Updated Bengali, German and Brazilian Portuguese translations
- Added control file for Amazon Tate
- Other minor fixes
