[APP][ROOT][4.0+]Battery Charge Limit v1.1.1

[amn1987]

I don't have the same problem that you described in your previous post, at least I don't think so. Haven't checked it out too much.

Yes block the wakelocks that occur while using acca or battery charge limit to avoid 2-3% standby drain during the night and so on. Just make sure to take your time to test it out and make sure everything still works when blocking the wakelock.

I attached a screenshot of the wakelocks I'm blocking. Haven't been blocking all these for that long but my standby drain is about 0.5% per hour at the moment while charging cable still plugged in and everything seem to work and I haven't experienced any problem with massive drain later or so. Also this is on my poco f1.

Thanks for the suggestion. I had been looking for an app to block wakelocks reliably for some time. Just started. Hopefully this will do the trick.
P.S. Only those depicted in your ss need to blocked? Also safe to apply on boot?

 

[JD. A]

Thanks for the suggestion. I had been looking for an app to block wakelocks reliably for some time. Just started. Hopefully this will do the trick.
P.S. Only those depicted in your ss need to blocked? Also safe to apply on boot?

I've haven't found any problem by blocking these, it's not that easy finding out exactly what they do though. I suggest you try yourself and start blocking both kernel and app wakelocks which is keeping your phone awake for long amounts of time if you run into a problem revert the last blocked wakelock. Also don't block any wakelock containing "PowerManager" etc. Those are basically catch alls from what I've found out. So if you block them you'll most likely run into problems.

 

[andrasandhi]

Charging control file on Realme 6 Pro (RMX2061)

 

[Snah001]

Unfortunately app doesn't work on my new Poco F2 Pro.
On my Mi 9T Pro it worked flawless.

 

[gonzo1963]

Unfortunately app doesn't work on my new Poco F2 Pro.
On my Mi 9T Pro it worked flawless.

Good morning,
Try this to see if it works for you: https://xdaforums.com/showthread.php?p=73676068

Regards

Enviado desde mi unknown mediante Tapatalk

 

[Osprey00]

FYI, I found that the following CTRL file works for wireless charging on my phone (LG V30):

/sys/class/power_supply/dc-wireless/charging_enabled

Many thanks to the developer for this great app. If I may make a suggestion, it would nice if we could designate multiple CTRL files so that the service could work with both wired and wireless. If it's not possible to detect which charging method is being used, you could possibly just enable/disable both files at the same time. Edit: Also, adding that path as one of the pre-defined ones in the app would be quite useful, I'm sure.

Edit: I forgot to mention that one quirk that I've noticed is that, only when using that path for wireless, the app ignores the "Recharge below" setting and starts recharging as soon as the percentage drops 1% below the max.

 

[whitedavidp]

FYI, I found that the following CTRL file works for wireless charging on my phone (LG V30):

/sys/class/power_supply/dc-wireless/charging_enabled

Many thanks to the developer for this great app. If I may make a suggestion, it would nice if we could designate multiple CTRL files so that the service could work with both wired and wireless. If it's not possible to detect which charging method is being used, you could possibly just enable/disable both files at the same time.

Edit: I forgot to mention that one quirk that I've noticed is that, only when using that path for wireless, the app ignores the "Recharge below" setting and starts recharging as soon as the percentage drops 1% below the max.

After this I went looking on my V40 Thinq (LM-V405QA) and found this file:

/sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled

Without a wireless charger I cannot test. But I have added it to my Tasker routines that approximate what this app does. So both wired and wireless get written. Thanks

 

[Osprey00]

After this I went looking on my V40 Thinq (LM-V405QA) and found this file:

/sys/devices/platform/soc/a90000.i2c/i2c-4/4-0061/power_supply/wireless/charging_enabled

Without a wireless charger I cannot test. But I have added it to my Tasker routines that approximate what this app does. So both wired and wireless get written. Thanks

Yeah, that's the same file. The path that I gave includes symbolic links and, if you follow it in a file manager, resolves to a path very similar to what you gave, which looks to be specific to the SOC. On my LG V30, which has a Snapdragon 835, a couple of numbers are different than yours on an 845. In other words, the shorter path is the one that should exist on most phones (at least ones with wireless capability) while the longer one will differ slightly from phone to phone. Either one works with Battery Charge Limit, I've found, but the generic one is probably the better one to use.

I didn't consider automating writing of the files. I may have to try that. Thanks.

 

[maxs8007]

App isn't working on android 10

 

[cattolicboy]

App isn't working on android 10

this an s a very false information

 

[guest4711]

App isn't working on android 10

No, it's working if the kernel supports it. I use it on some devices running Android-10.

 

[maxs8007]

No, it's working if the kernel supports it. I use it on some devices running Android-10.

How can I identify whether my phone's kernel support it's or not?

 

[guest4711]

How can I identify whether my phone's kernel support it's or not?

If you'll find a suitable control file the kernel supports it.

 

[evronetwork]

Wish there was an update of this app, it works as expected but the reset stats doesn't work, so I'm doing it manually

Xiaomi Mi MIX 2s

 

[bamn]

@sriharshaarangi or anyone who could help.

Maybe you could help me out, I am looking for a way to manipulate the battery temp reading or to force charging ignoring low batt temp.
The problem is that my batt temp reading sometimes jumps to -20(c) and it won't charge.

I can warm the phone up (hot air) or run a benchmark and the temp reading goes back to normal, it seems downwards from about 26c it jumps to -20.

It's a U11 running lineagos 17.1
Ideally I would only ignore the -20 value as this is never correct and keep the rest of the safety intact.
But I wouldn't mind ignoring the low temperature protection completely as it is rarely below 0 where I live.

I hope you are willing to help me out, I do understand the risks of ignoring temp values!

 

[Osprey00]

@bamn

If you look under /sys/class/power_supply/battery, there are three files that seem relevant:

charger_temp
charger_temp_max
temp

temp appears to hold the current temperature, since I see the value is slightly different each time that I open it. It's hovering around 290, which seems to be about what normal is. I'm guessing that the other two determine whether charging occurs by comparing their values to the value in temp. My charger_temp is blank/unreadable and my charger_temp_max is 1216. I'd try setting either or both to -1, then try 0, then other values. If you can't write to charger_temp, changing the permission might help or maybe you can even rename it and create file in its place with its name that you can write to. If none of that works, perhaps you can rename temp or change its permissions/ownership so that the system can't update it. Anyways, those are just some ideas.

 

[bamn]

@bamn

If you look under the same folder where the charging_enabled file is, /sys/class/power_supply/battery, there are three files that seem relevant:

charger_temp
charger_temp_max
temp

temp appears to hold the current temperature, since I see the value is slightly different each time that I open it. It's hovering around 290, which seems to be about what normal is. I'm guessing that the other two determine whether charging occurs by comparing their values to the value in temp. My charger_temp is blank/unreadable and my charger_temp_max is 1216. I'd try setting either or both to -1, then try 0, then other values. If you can't write to charger_temp, changing the permission might help or maybe you can even rename it and create file in its place with its name that you can write to. If none of that works, perhaps you can rename temp or change its permissions/ownership so that the system can't update it. Anyways, those are just some ideas.

Many thanks for your help!
I am able to open all these files but I cannot change the values and safe.
Changing the file name or permissions also gives an error.
I am rooted/unlocked and I tried different root enabled file managers and the echo/chmod command through terminal/tasker.

All options fail...
It's really stupid, I need to heat up my phone to get it to start charging, as long as it's charging the battery temp stays normal and slowly drops, from about 22 downwards it'll jump to minus 9 and then soon to -20.

With - 20 it won't charge and if I switch off/reboot it won't come back on again.

 

[shiroichiii]

cool

 

[shiroichiii]

Hi I use this app yesterday, I set my limit to 80% and set recharging to 70%, i decided to disable it, it didn't work so I reboot my phone it still don't work, then I tried to cleanflash and installing new ROM but it still doesn't work it still limit my charging to 80% I even tried to changing back to my stock ROM but the problem is still here, please someone help me((

 

[Osprey00]

Many thanks for your help!
I am able to open all these files but I cannot change the values and safe.
Changing the file name or permissions also gives an error.
I am rooted/unlocked and I tried different root enabled file managers and the echo/chmod command through terminal/tasker.

All options fail...
It's really stupid, I need to heat up my phone to get it to start charging, as long as it's charging the battery temp stays normal and slowly drops, from about 22 downwards it'll jump to minus 9 and then soon to -20.

With - 20 it won't charge and if I switch off/reboot it won't come back on again.

It turns out that I have the same problem. Sorry. I should've tested, myself. The permissions on the file and folder appear to be OK. I'm reading that the system can "write lock" certain files to prevent them from being overwritten, which could be what's happening here. I'm not an expert in this area, so I'm not sure if there's any way around this. Something that you could maybe try is setting charging_enabled to 1 and then setting permissions and/or ownership on it to try to prevent the system from ever changing it back to 0. If that doesn't work, you might try an app like Tasker to set that file to 1 automatically whenever it reads that it's 0 or you connect your charge or something.

Hi I use this app yesterday, I set my limit to 80% and set recharging to 70%, i decided to disable it, it didn't work so I reboot my phone it still don't work, then I tried to cleanflash and installing new ROM but it still doesn't work it still limit my charging to 80% I even tried to changing back to my stock ROM but the problem is still here, please someone help me((

Have you uninstalled the app? If you installed it from the Play Store, then it will have re-installed itself on each new ROM as soon as you signed into your Google account.