yashsingh1/xdaforums huggingface dataset:
[Magisk] :
Set it all up with my custom settings and on 8.0 Shamu, it simply charges up above the limit... If any one knows a solution, let me know or if someone wants logs... If not, oh well. Thanks again fellas
[Magisk] AlexBurnout77:
Extreme lag caused by CS

Hi,

I did extensive research and testing with Android Oreo and CS for Magisk on my 1+3. I am finally able to say that your module is causing me major freeze lags and touch delays. It's not even funny. Do you know of this issue? Can you please fix it?

P. S.: I've looked into what others say about 25-1 and it's pretty much what I would say. Happy coding, then!
[Magisk] x1reN:
I have another problem now, I don't have any lags anymore, but the settings I want to use aren't working. I tried cs 87 84 but it's not working.
[Magisk] SignetSphere:
It will charge up to 85% and then pause after that. Then it will charge again once it hits the minimum percentage that you've set (in your case is it at 10%).

As for me... I've uninstalled this module atm... i think the cs service doesn't like me lol. It is still charging after I've unplugged the cable (Ampere app shows 0maH though). I think I'll wait for the latest version before I try this module again.

EDIT:

Using a Galaxy S4 here with RR 5.8.5 Nougat (Final) btw.
[Magisk] IkerST:
Does anyone have a problem with apps freezing and leading to a kernel panic

I saw this issue in a Moto G4 play running official lineage os (7.1.2), resurrection remix(7.1.2) and an Oreo rom (8.0)
[Magisk] wilberfan:
The developer is working on the issues we've been experiencing:

https://xdaforums.com/showpost.php?p=74732663&postcount=511

For those of you that absolutely can't wait, there's a (non-Magisk) app that works very similarly.

https://xdaforums.com/android/apps-games/root-battery-charge-limit-t3557002
[Magisk] TeknicalGeek:
Blu R1 HD incompatibility log

I have attached the zip
[Magisk] Jaymin.0.1910:
Hi all, for those experiencing lags with the module, I have modified the last magisk repo version a little bit, which solved the issue for me. I have attached the zip, give it a try. And please upgrade to original version when a lag-free build is available as I am not the developer of this module.

# Deleted, no longer needed, official update available with fix
[Magisk] Koeties:
Hi. Is there a manual way to download the release candidate? On my Galaxy Tab A 10.1 with LineageOS 19 the update via acc -u -f dev gets stuck when trying to install the module to the acc module directory. Tried various terminal clients.
[Magisk] Uluru25:
... there are three ways:

1) join dev's tg-group and download it from there (pinned build)

2) open this page, hit "tags" and create it by yourself

3) if you dare a guy like me unknown to you, you can use the enclosed file 🤠
[Magisk] Spaceoid:
Hi there!

After using ACC for a long, long time now, recently I experience a weird issue:

I just updated my OnePlus 6 from Android 13 to Android 14 (LineageOS 20 to 21) a few weeks ago, and I am using the latest dev build of ACC, v2024.2.25-rc.

I have my cooldown cycle set in a way that charging should pause every 50 seconds for 10 seconds once the battery reaches 60% capacity.

I then did a charging switch test, and it appears there are only four switches that support idle mode, too:

3) charge_control_limit_max

9) op_disable_charge 0 1

19) current_max 1500000 1

20) current_max 1500000 10000

Now, weirdly, with switches 3) and 9), charging stops above 60%, but only around every three minutes instead of every 50 seconds, measured with the Ampere app.

With switches 19) and 20), charging won't stop at all.

Charging altogether is limited to 85%, so that limitation works, but since the Android update, something with my cooldown cycle is amiss. I will attach my config file to this post and will happily provide further information if needed. Maybe someone here has a clue what is going on? Thank you loads in advance!
[Magisk] Uluru25:
... you have configured two (!) triggers to activate a cooldown scenario:

1) cooldown_capacity=60%

2) cooldown_temp=35 ºC

Moreover, you have defined the same temperature of 35 ºC as max_temp.

I guess, this interferes since max_temp will stop (!) charging until your resume_temp (33 ºC) is reached. If the ampere app allows you to read also the temperature conditions during charging, look if this is the issue.

I would recommend you to

1) choose only 1 trigger and

2) if you select ct as trigger, to have 1 or 2 ºC space between ct and mt.

My recommendation is to forget cc (define it as 101) and to let temperature conditions control cooldown scenarios.

🤠

*otherwise this might help you
[Magisk] Spaceoid:
What is recommended - letting ACC choose the switch by itself, or choosing it manually? And how many charging cycles would ACC take to find a proper switch?
[Magisk] Uluru25:
... if you run the latest build, let acc choose the switch. The switch is found during the very first charging and kept if it works.
[Magisk] Brettroth:
I'm curious, I have a op 12r that has charging stop at 80. Curious if your module would be better to have direct DC because I'm not sure the built in limiter does that. I think it just drains a little charges a little.
[Magisk] Uluru25:
... then check it out but take care to disable any inbuilt charging limiters and do not install the front-ends but directly (via magisk) the acc.zip.

See here where to find the latest build.

🤠
[Magisk] Brettroth:
Thank you for the response sir. You've helped me before even making a custom build for my 6t. The module works beautifully with the 12r even better than the 6t as there was still random voltages when on battidle. But now it is locked at 0 just the way I wanted it.
[Magisk] Brettroth:
Not sure why OnePlus wouldn't take a page out of your book lol. Also curious if you know about batteries much, with a brand new battery is it a good idea to charge to 100 once or would going to 80 be best forever?
[Magisk] trevtdogg:
my current understanding is:

that you should avoid any battery level over 80% as much as possible to increase longevity.

for the lower end, it's a sliding scale but 20% is considered a strongly recommended minimum to not go below.

topping back up to 75% whenever it gets below 65% is the absolute ideal, but is unrealistic for most people's mobile phone use.
[Magisk] Uluru25:
... I wouldn't recommend to re-charge at 65 % but rather between 25 - 40 %.

Read here if you are curious to know why...

🤠
[Magisk] alnosr:
Hello,

I woud like to use acc to bypass battery, so that the phone runs off the charger instead of the battery, to conserve it's life esperance.

I do stuff that makes my battery runs very hot, I thought with this method since it bypass the charger I could not only reduce the temperature, but also reducing the number of cycle.

I have a motorola 40 edge pro phone, which do posses that "bypass battery" functionnality. It's called "Battery optimisation" under motorola stock rom, and basically, it learns your phone charging pattern, so that when you plug in at night, it charges only up to 80%, and use the charger to run the phone (I could tell because it's constantly 0mAH in accubattery). Then, when you're supposed to wake up, it charges till 100%. Thefore the functionnality is indeed present, but do not allow much user control.

Anyway, I'm trying to reproduce that through acc. At first, even the basic core functionality didn't work for me, I had to switch to switch 1. Now it's fine, but I still can't get battery idle (the 0mAH ) to work.

I tried emulated "idle mode", but I feel it's not very satisfactory? I set acc 65 64, and what it does it that it simply charge to 65, discharge to 64, and continusly. Considering my usage (let's say gaming), does that makes any difference from just running on battery to 30% and then charging to 60%? Basically a lot of small cycle vs a bigger one (but not as big as 100 0), the impact on the battery should be quite similar? Also, when running high CPU usage process, the battery does get hot. But then, even with small cycles, I'm still charging it therefore increasing temperature?

Would like your opinion on that please, also if you have any idea how to make idle battery work (since my phone does support the functionnality), I would also be very happy to hear your feedbacks.

Thank you !
[Magisk] Uluru25:
Let's start with two simple questions:

1. Which build of acc are you running?

2. Have you any front end / gui (like Acca or Acc Settings) installed?

🤠
[Magisk] laur89:
Run acc -t and see which switches have battIdleMode=true. Those should allow for what you're asking.
[Magisk] alnosr:
Hello,

1.I'm using the latest build on GitHub. (2023/10/16)

2. I tried with acc only, acca and acc settings. Right now I'm mainly using acc setting and manual as it's more stable.

That is what I did. The switch I selected does have battidlemode=true, however impossible to get the 0mAH, only emulated idle mode with something like acc 65 64.
[Magisk] Kamiruku:
Hi, I am on Xiaomi Poco X4 Pro (A13, Miui14). I flashed the latest github release (20231016) via Magisk and then tried acc -t In Termux, in which it just ends at "Terminated".

I tried updating to the latest dev build via acc -u -f dev, which it succeeds. But now it just returns "Segmentation Fault" when I run any ACC command.
[Magisk] Uluru25:
Any front-ends like Acca or Acc Settings installed?
[Magisk] alnosr:
Only ACC settings now.

I did tried removed it briefly and only do with terminal but didn't change anything so I installed it back.
[Magisk] Uluru25:
O. K.

I would have recommended you

1) deinstall all front-ends

2) update in the terminal via acc -u -f dev

3) try if it works

🤠
[Magisk] alnosr:
Ok I just tried to update with your command.

I get this error

":/data/data/com.termux/files/home # acc

Segmentation fault"

I could not even downgrade I had to manually uninstall and reinstall with GitHub last release
[Magisk] Uluru25:
... 1) what is your rooting solution and) have you granted root privileges to termux and 3) did you enter "su" before the acc -u -f dev command?
[Magisk] alnosr:
I'm rooted with magisk. Yes termux has root privileges and yes I entered su before the command.
[Magisk] Uluru25:
... either join VR25's telegram group here and download there the last pinned build - or if you trust an unknown person - download this file, rename the .txt extension and flash this file with magisk.
[Magisk] alnosr:
Thanks for the link. Just installed, still can't get true idle mode to work :/ only one switch with has battery idle=true, I selected that one but then I still get the continuous discharge and not 0mah.
[Magisk] Uluru25:
... dont stick too much on 0 mA. Set a resume capacity 5 % or more below your pause capacity. Then (if your battery is below resume capacity) plug to the charger. Let the phone be plugged over night and check the next morning whether it has only lost 1 - 3 % (as a rule of thumb). Then idle mode seems to work.

Consider to log and check the (dis-)charging with an app, e. g. this.

🤠
[Magisk] alnosr:
Well it's definitely not idle as I said, I'm running CPU intense process, and the discharge rate is pretty much the same weither in idle or not.

I did manage to "trick" my phone to launch the native version of battery idle though, which gives me no discharge rate. But it's very troublesome, I have to change my phone time, set an alarm etc... I really wish I could do it directly in ACC.
[Magisk] Uluru25:
... maybe post your problem in the dev's TG-group so that someone else might give you help...
[Magisk] Gapkobob:
Can someone recommend me what would be an optimal settings for phone that is plugged in 24/7? I've only applied "acc 60 59", should I change anything else?
[Magisk] Uluru25:
... does your setup provides "idle mode"?
[Magisk] Gapkobob:
It is set as true (default). Do I need to check if it works? How can I do that?
[Magisk] Uluru25:
... check it with acc -t in the terminal.

You are not running any front-ends like Acca or Acc-Settings?
[Magisk] Uluru25:
Macro to write some values like batt. temperature, charging current, charging voltage, batt. percentage, selected acc-config parameters, etc. to a. txt file during charging

edit: updated here

This post is an update to a previous post here, providing a MacroDroid macro to monitor during charging some related parameters over the time depending on the respective acc settings.

If you want to use the macro, download it, rename it to .macro and import it. It will start automatically when the charger is plugged.

First, read the explanations already given here.

Then, see the long comment at the very end of the macro, trying to explain the used variables and which / how to modify.

Since I haven't logged all changes I made since the last release, the following summary might be too long / too short, sorry:

- different output directory can be defined in the variable

- output directory is created if not already present

- macro checks if charging follows the config or follows an acc -f command

- even for a charging following an acc -f xx -s yy command the defined values (like target capacity xx or additional limits defined in the yy term) are reported

- variables to be reported can be (dis-)activated in the array variable

- loop to repeat reading of charging voltage if reading was not successful

- configurable warning if charging was started but macro has detected that acc daemon is not running

- configurable auto-activation of acc daemon if if charging was started but macro has detected that acc daemon is not running

😉
[Magisk] Gapkobob:
I've got an output that some switches work and some current max - don't.
[Magisk] Gapkobob:
This is what I've got.
[Magisk] Uluru25:
... great! Several switches support native idle mode!

Keeping the battery in a region between 40 - 60 % is good for always plugged devices. Personally, I would set rc lower to avoid recharging in case of small fluctuations.

Enter acc -c h aiapc to get more info from the dev for always plugged devices (but as I understood you, this doesn't applies for you).

🤠
[Magisk] sic0048:
I would recommend that you set the resume charge at something like 30 and the pause charge at something like 60. Do this with the terminal command, "acc 60 30".

If you are really going to leave this device plugged in 24/7, then I would also suggest that you turn the "allow_idle_above_pcap" setting to false. It is set to true by default. By changing this setting to false, the device will discharge the battery once it gets to the pause battery level. If it is set to true, the device will try to hold the battery at the pause battery level and not let it drop. For a device that is plugged in 24/7, that isn't the functionality we want. We want the device to discharge it's battery once it hits the pause threshold and only start charging again when it hits the resume threshold. To make this change, enter "acc --aiapc false" with a terminal command.
[Magisk] Uluru25:
... the recommendation to set aiapc=false is in line with the dev's point of view (see above). However, I understood the effect of it differently: if the battery (for what reasons ever) was charged above pause capacity, aiapc=false will allow a 24/7 plugged device to reach again the pc level. What you described (cycling between charging to pause capacity and the discharging the battery down to resume capacity) means to deactivate idle mode. If desired (I wouldn't do so), this means setting pbim=no.

Also here, just enter acc -c h pbim to read dev's explanations.

🤠
[Magisk] Uluru25:
ACC- Front-End // Your help is appreciated!

I have made (for fun) a MacroDroid* based front-end for ACC and consider to make it available for others who are interested.

Before doing so, I would need two or three guys for testing to get feedback how the front-end works on other devices than mine.

You should:

- have already some experience with configuring ACC via the terminal

- have no issues with your actual ACC configuration

- have installed the MacroDroid app (or are willing to do so which requires to grant root access** to it) - Pro-version is

not

needed

edit:

* take note that Jamie, the developer of MacroDroid, is also an XDA member having an own thread for MacroDroid

**if granting root access is a concern for you: root is needed since MacroDroid has to pass acc commands to the shell as ACC does (which also requires root as you know 😁); however internet access of MacroDroid can be prohibited with a firewall (e. g. AFWall+) and is nevertheless working fine.

If this fits and if you want to help me, please send me a private message.

Features of the Front-End:

Spoiler content hidden.

🤠
[Magisk] Fdm76:
hi, does anyone use the acc advanced charge controller? I can't charge above 70% with the switches present
[Magisk] Fdm76:
I use the latest version only from the terminal on a Samsung S24ultra, however on the Mi11ultra it works perfectly, thanks
[Magisk] Uluru25:
... let's see!

First, please share the results of acc -v and then of acc -sp.

🤠
[Magisk] Uluru25:
... and acc -v?
[Magisk] Fdm76:
View attachment 6091817
[Magisk] Uluru25:
... could it be that your mt=35 has stopped charging before reaching your pc=75?
[Magisk] Fdm76:
during charging it does not exceed 33 degrees, I think it has to do with rom the samsung rom
[Magisk] Fdm76:
This is a device-specific issue (by design?). It's caused by the store_mode charging control file. Switch to batt_slate_mode to prevent it. Refer back to charging switch above for details on that. I can't find a solution
[Magisk] Fdm76:
On the telegram group they gave me the following instructions, but I am unable to proceed:

Black list store mode switch in write.l

Try not to trigger it with acc -t (which the blacklisting is fo

Reboot once usually solve it, you can also locate it in /sys/class/power_supply/battery and have acc apply_on_plug set it to 0 for safe measurer

What should I do?
[Magisk] Uluru25:
... will tell you later...
[Magisk] Uluru25:
Here I am back. You have three options:

1) install a file manager with root capabilities I use X-Plore from e.g. here, grant root and navigate to data/adb/vr25/acc-data/logs/. There you will find the write.log file. Open it (in the root explorer), and put a hash (#) before the switch you want to exclude. No space between the hash and the switch. Compare in the attached file. Then save the modified file and leave the root explorer.

2) open your terminal and enter there

cp /data/adb/vr25/acc-data/logs/write.log /storage/emulated/0/Download/write.log.txt

Then open this file with a notepad app, add the # as described in 1) and save the file. Then enter this command in the terminal

cp /storage/emulated/0/Download/write.log.txt /data/adb/vr25/acc-data/logs/write.log

3) have patience and wait until I publish here my front-end. There it is a feature from the menu (I know that you won't choose this option 😁)
[Magisk] Fdm76:
E Follow the instructions to the letter, insert # in front of the switch and give the command from the terminal for battery store 0, put it on charge and update you
[Magisk] Fdm76:
it doesn't work, it still stops at 70%, I give up
[Magisk] Uluru25:
== New build (202404290) ==

Edit: updated here

Macro to write some values like batt. temperature, charging current, charging voltage, batt. percentage, selected acc-config parameters, etc. to a. txt file during charging

This post is an update to a previous post here, providing a MacroDroid macro to monitor during charging some related parameters over the time depending on the respective acc settings.

If you want to use the macro, download it, rename it to .macro and import it. It will start automatically when the charger is plugged.

First, read the explanations already given in the linked posts.

Then, see the long comment at the very end of the macro, trying to explain the used variables and which / how to modify.

Summary of changes made since the last build:

- fixed issue of non-reporting with new acc build 202404260

- terminates no. of retries if no voltage could be read

- log file name contains seconds to always create a new log even if being started in the same minute

🤠
[Magisk] Uluru25:
sAFE - A MacroDroid based front-end for ACC

edit: new build see here​

I have made (just for fun) a MacroDroid based front-end for ACC and - after some testing by a few brave ACC-users - decided to make it available for others who are interested in an alternate way to control almost all functionalities of ACC without the need to use a terminal app.

Be warned: if you expect a stylish app with nice visual gimmicks, stop reading here. This is not what sAFE will provide you!

sAFE is rather like a "swiss knife" - not necessarily nice but full of features: you can control and configure more or less all settings of ACC (and even do some things more)...

Still interested?

Then download the attached macro, delete the trailing ".txt" to have the correct file extension ".macro", import it into MacroDroid and create a widget on your home screen to open it (read the attached file "Steps_to_install_the_front-end.txt" in case you don't know how to do so).

Features of the Front-End:

- read / modify most acc variables (30+)

- directly see the default values

- get dev's help text for the acc variables

- backup / restore your config

- return to default config

- background / manual acc update checks

- direct upgrade / rollback of acc builds

- start / stop the daemon (idle mode)

- enhanced one-time charging (acc -f)

- add / modify /delete time profiles

- test / set all or selected charg. switches

- (de-)activate selected charg. switches

- get static / dynamic (dis-)charging info

- show full / filtered config info

- create full / short acc logs

- execute pasted terminal commands

- write outputs / results into files

- define directories for output writings

Let me know if something doesn't work or something is missing.

🤠
[Magisk] Uluru25:
Edit: updated here

== New build (202405060) ==

CharLog - a MacroDroid based macro to write some values like batt. temperature, charging current, charging voltage, batt. percentage, selected acc-config parameters, etc. to a. txt file during charging

This post is an update to a previous post here, providing a MacroDroid macro to monitor during charging some related parameters over the time depending on the respective acc settings.

If you want to use the macro, download it, rename it to .macro and import it. Enable the macro either with the slider from the macro list or with the menu (see attached). No widget is needed, it will start automatically when the charger is plugged.

You need nothing to modify (it should work "out of the box" but in case you want to tweak it a little, read first of all the explanations already given in the linked posts and then, see the long comment at the very end of the macro, trying to explain the used variables and which / how to modify (see also the attached screenshot).

Summary of changes made since the last build:

- fixed issue of no voltage could be read due to changed format of acc -i voltage_now from acc build 202405043

- use of [Cha] or [Dis] instead of +/- values for voltage and current

- "|" as value divider

🤠