Is there a particular reason you can't download "the latest version" from the Google Play Store (linked in the OP)? Is there a particular reason you need an older version?
[APP][ROOT][4.0+]Battery Charge Limit v1.1.1
- Thread starter sriharshaarangi
- Start date
-
- Tags
- battery charge charging limit
Absolutely, i don't want to install a google account on my phone
That phone won't be used for browsing the internet
Also, the version currently available in Google App store is 1.1.1, which is the one i want to download but i can't, the link does not work.
Well....that's an "interesting" decision...I'm curious as to your reason (if it is worth the hassle and/or a reasonable decision)....Absolutely, i don't want to install a google account on my phone
That phone won't be used for browsing the internet
Also, the version currently available in Google App store is 1.1.1, which is the one i want to download but i can't, the link does not work.
Regardless, all the links seem to work for me (both the Google Play Store link and the androidfilehost.com ones). If they were really down, I would suggest you could download it from APKMirror -- the only caveat is that the latest is the 1.1.0 version (about a few weeks before the last update). If you were good with that one, you could download it to a computer or other device, then "beam" (bluetooth, NFC, flashdrive, put on PC and transfer through cord, connect both through a PC, etc.) it to that device to install.
The only thing I can think of as to why you can't get the links to work is something is blocking your connection; host blocking (AdBlock), firewall, router filter. You should re-check on any setting that may related to those and try again.
It's on F-Droid too
Battery Charge Limit | F-Droid - Free and Open Source Android App Repository
Stops charging at a desired level
I made a screenshot to show you my situation. It's not related to some sort of blocking. It just says "no mirrors found".
Attachments
Thank you, your link actually works.It's on F-Droid too
Battery Charge Limit | F-Droid - Free and Open Source Android App Repository
Stops charging at a desired levelf-droid.org
Try installing the ACC Magisk module and run the command "acc -t". It will test all known strategies and save the results to /sdcard/Download/acc-t_output.txt. You can then add one of the working control files reported in Battery Charge Limit's settings.
You can also just use ACC if you like, it still gets updates and support. Just install ACCA or ACCSettings for a gui similar to Battery Charge Limit's.
Last edited:
I did, got this output:
1/6: /proc/mtk_battery_cmd/current_cmd 0::0 0::1
switch: off (0 1) current: 1mA (Idle)
switch: on (0 0) current: 535mA (Charging)
Switch works
- battIdleMode=true
2/6: /proc/mtk_battery_cmd/current_cmd 0::0 0::1 /proc/mtk_battery_cmd/en_power_path 1 0
switch: off (0 1, 1) current: 3mA (Idle)
switch: on (0 0, 1) current: 542mA (Charging)
Switch works
- battIdleMode=true
3/6: mtk-master-charger/constant_charge_current_max 1980000 0
switch: off (1980000) current: 1mA (Idle)
switch: on (0) current: 463mA (Charging)
Switch works
- battIdleMode=true
4/6: usb/current_max 1500000 0
switch: off (1500000) current: 544mA (Charging)
Switch doesn't work
5/6: mtk-master-charger/constant_charge_current_max 1980000 50000
switch: off (1980000) current: 0mA (Idle)
switch: on (0) current: 590mA (Charging)
Switch works
- battIdleMode=true
6/6: usb/current_max 1500000 50000
switch: off (1500000) current: 588mA (Charging)
Switch doesn't work
I've selected the ones with a green checkmark (one by one) from the above list, and pressed Test the charging switch (from the app), the result: an error has occurred.
Edit: Manually selecting the first profile from the list above stopped the charging at 75% which was the plan. Not sure why the error came up but it works.
Last edited:
You need to find the
You need to find the proper file and settings. Read the thread.
This apps is so good creating control loop sets by the battery percentage which creates hysteresis band outputting switching pulses of charging state to control the BMS. It still crude because of the high current spike at the band limit. But it's okay for now.
I couldn't find of how to change the control loop to voltage instead of battery percentage, how to do that?
I couldn't find of how to change the control loop to voltage instead of battery percentage, how to do that?
Last edited:
Is there any support for Moto Z3 Play phones? I tried this app (Battery Charge Limit) to limit charging to 80% and it didn't do anything. Properly rooted and all. Also using Pixel Experience 13 ROM.
I could not find anything on the device on how to make this work via some control file:
I could not find anything on the device on how to make this work via some control file:
Code:
ls -la /sys/devices/soc/800f000.qcom,spmi/spmi-0/spmi0-00/800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2/power_supply/battery <
total 0
drwxr-xr-x 3 root root 0 1971-03-17 06:31 .
drwxr-xr-x 9 root root 0 1971-03-17 06:31 ..
-r--r--r-- 1 root root 4096 1971-03-17 06:31 age
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 battery_charging_enabled
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 capacity
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charge_counter
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charge_done
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charge_rate
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charge_type
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charger_temp
-r--r--r-- 1 root root 4096 1971-03-17 06:31 charger_temp_max
-r--r--r-- 1 root root 4096 1971-03-17 06:31 constant_charge_current_max
-r--r--r-- 1 root root 4096 1971-03-17 06:31 current_max
-r--r--r-- 1 root root 4096 1971-03-17 06:31 current_now
-r--r--r-- 1 root root 4096 1971-03-17 06:31 current_qnovo
lrwxrwxrwx 1 root root 0 1971-03-17 06:31 device -> ../../../800f000.qcom,spmi:qcom,pm660@0:qcom,qpnp-smb2
-r--r--r-- 1 root root 4096 1971-03-17 06:31 die_health
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 dp_dm
-r--r--r-- 1 root root 4096 1971-03-17 06:31 fcc_stepper_enable
-r--r--r-- 1 root root 4096 1971-03-17 06:31 health
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 input_current_limited
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 input_suspend
-r--r--r-- 1 root root 4096 1971-03-17 06:31 num_system_temp_levels
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 parallel_disable
drwxr-xr-x 2 root root 0 1971-03-17 06:31 power
-r--r--r-- 1 root root 4096 1971-03-17 06:31 present
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 rerun_aicl
-r--r--r-- 1 root root 4096 1971-03-17 06:31 set_ship_mode
-r--r--r-- 1 root root 4096 1971-03-17 06:31 status
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 step_charging_enabled
lrwxrwxrwx 1 root root 0 1971-03-17 06:31 subsystem -> ../../../../../../../../class/power_supply
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 sw_jeita_enabled
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 system_temp_level
-r--r--r-- 1 root root 4096 1971-03-17 06:31 technology
-r--r--r-- 1 root root 4096 1971-03-17 06:31 temp
-r--r--r-- 1 root root 4096 1971-03-17 06:31 type
-rw-r--r-- 1 root root 4096 1971-03-17 06:31 uevent
-r--r--r-- 1 root root 4096 1971-03-17 06:31 voltage_max
-r--r--r-- 1 root root 4096 1971-03-17 06:31 voltage_now
-r--r--r-- 1 root root 4096 1971-03-17 06:31 voltage_qnovoShould be supported afaik, weird. I see candidates battery_charging_enabled 1 0 and input_suspend 0 1, but you really should use acc for testing at the very least.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
399Please 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-0558Todo:
-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
