G
Hi. Been using this program and find it useful but have been experiencing a new issue on my rooted Xiaomi Redmi Note 5. It will stop charging when reaching the limit I assign to it but if I leave the charger plugged in, it will start charging again a few hours later well above the low limit I selected. Do I need a special control file for my particular phone or something?
It's normal behavior. On some devices this app works by virtually disconnecting the charging cable, then it won't detect physical [dis]connection until that virtual switch is reset. So it has to wait in the notification area until recharge limit is reached before flipping the switch back and exit itself.After limit is reached here, it disables normally, but then when I disconnect the cord, it does not disable it self, and stay on the notification bar, I have to go there and disable it manually, and the toast saying it's disabled appear. I think it should do it when I disconnect, right? Is it a know problem?
Has always been 100 percent trouble free for me on my Pixel 2 XL rooted on Oreo and now on Pie.Is this working on the Pixel 2 XL ? I cant get it to work. I'm rooted and on Oreo 8.1 stock.
After limit is reached here, it disables normally, but then when I disconnect the cord, it does not disable it self, and stay on the notification bar, I have to go there and disable it manually, and the toast saying it's disabled appear. I think it should do it when I disconnect, right? Is it a know problem?
I am having the exact same issue and it's driving me insane. On my previous Xperia X Compact, the notification would disappear when i disconnected the device. Now I'm using an Xperia XZ1 Compact and it stays on after disconnecting the cord. The only difference I can think of is that my new device is rooted via magisk instead of supersu.
The thing is when i click the notification to disable it... I'm pretty sure it resets the battery stats too.
Very strange. Is there something I can do to correct this?
There are a lot of different implementations for the powermanagement and a lot of different control files. What works on stock kernel may not work on custom kernels for the same device, what works on N may not work on P and vice versa. So you are on your own. Mostly it so sinple and stupid as to check whether changing one control file (in /sys/classes/...) will have any result and if not proceed with the next one.
There are a lot of different implementations for the powermanagement and a lot of different control files. What works on stock kernel may not work on custom kernels for the same device, what works on N may not work on P and vice versa. So you are on your own. Mostly it so sinple and stupid as to check whether changing one control file (in /sys/classes/...) will have any result and if not proceed with the next one.
It would be helpful if everybody would report his device, ROM version, kernel version, control file used on success...
After limit is reached here, it disables normally, but then when I disconnect the cord, it does not disable it self, and stay on the notification bar, I have to go there and disable it manually, and the toast saying it's disabled appear. I think it should do it when I disconnect, right? Is it a know problem?
Hi,
I am trying to find the control file for my Huawei Ideos X5 or U8800. Actually my ROM by Blewfish has his app called "Huawei Settings" which is able to set the current to 0mA (effectively disabling charging) and to different values to enable charging. Would such a file work too with Battery Charge Limit? I am currently trying to find that file with no luck so far, see also here.
Thank you!
10-16 13:52:22.564 30259 30259 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with null: java.lang.IllegalArgumentException: Parameter specified as non-null is null: method com.slash.batterychargelimit.ForegroundService.onStartCommand, parameter intent
10-16 13:52:22.564 30259 30259 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Parameter specified as non-null is null: method com.slash.batterychargelimit.ForegroundService.onStartCommand, parameter intent
10-16 13:52:22.564 30259 30259 E AndroidRuntime: at com.slash.batterychargelimit.ForegroundService.onStartCommand(Unknown Source:2)
10-16 13:52:27.007 30466 30466 E AndroidRuntime: Process: com.slash.batterychargelimit, PID: 30466
10-16 13:52:27.007 30466 30466 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with null: java.lang.IllegalArgumentException: Parameter specified as non-null is null: method com.slash.batterychargelimit.ForegroundService.onStartCommand, parameter intent
10-16 13:52:27.007 30466 30466 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Parameter specified as non-null is null: method com.slash.batterychargelimit.ForegroundService.onStartCommand, parameter intent
10-16 13:52:27.007 30466 30466 E AndroidRuntime: at com.slash.batterychargelimit.ForegroundService.onStartCommand(Unknown Source:2)
I can confirm those crashes, but i haven't looked for the catlog...since going to LOS 15.1 (Oreo), battery charge limit often crashes when plugging in:
Seems these are the relevant messages:
since going to LOS 15.1 (Oreo), battery charge limit often crashes when plugging in:
Seems these are the relevant messages:
This is not as bad as 100%, but it's pretty close!Thanks for this! Using it and will continue to do so, especially when getting a new phone.
Question, I read so much about the charge limit and recommendations to be around 80%. I have mine set to 97%, just to keep it clear from 100%.
Is this bad? I want to have the most amount of charge when I head off to work in the mornings, and 80-85% just doesn't cut it. Is it still fine with those types of batteries?
Thanks again, great app!
Regards
This is not as bad as 100%, but it's pretty close!
Keep in mind, though, what matter most are battery temperature, voltage and charging current.
You have to keep your battery as cool as possible (not freezing, of course) and make sure its voltage doesn't stay high for too long (or doesn't touch/pass the high threshold at all).
Since you're letting your battery charge to 97% capacity, at least refrain from using fast charging!Use a regular/old-fashioned adapter instead, or even better, charge on USB only. The lower (not less than 500mA) the charging current (amperage) is, the better.
High current, voltage and temperature reduce battery lifespan much more that simply charging to near full or full capacity.
Thanks for this! Using it and will continue to do so, especially when getting a new phone.
Question, I read so much about the charge limit and recommendations to be around 80%. I have mine set to 97%, just to keep it clear from 100%.
Is this bad? I want to have the most amount of charge when I head off to work in the mornings, and 80-85% just doesn't cut it. Is it still fine with those types of batteries?
Thanks again, great app!
Regards
Thank you.I finally got the idea to search for mmi_charging_enable under the sys folder. I thought since it's the same OS it could exist somewhere. Turns out it does exist in /sys/devices/virtual/oplus_chg/battery and with that I was finally able to make the phone stop charging.
/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable
looks to be working for the OnePlus Nord n200 running lineage 19.1 (Android 12L). 1 for enable, 0 for disable./sys/devices/platform/google,charger/charge_stop_level