[Magisk] Nazo:
So I need to ask for help regarding acc on my phone. Unfortunately I'm using Magisk because I'm on LineageOS 17.1 which is Android 10 and they seem to have abandoned the older, simpler, cleaner method of just directly writing to the system partition and simply using root access directly and Magisk is pretty much the only proper way to do things now it seems. I'm sure you don't support the Magisk version officially, but hopefully you can still help figure this out anyway. I'm using a Samsung A5 2017 model and it is blatantly obvious the battery Samsung put in this one is just not really designed to handle 4.35V well. I've found I have to limit the charge to 95% -- maybe even 94% -- to get more or less to the point where it doesn't seem to be overcharged which only acc seems to be able to do.

Unfortunately what's happening is basically acc seems to only work once on a bootup. Once it charges up to whatever value I've set (95% in this case, but I've tried other values and it goes to whatever it's set to successfully first) it never charges again (so acc is at least working so far as to prevent charging clearly.) The only thing that makes it work again is to reboot the system. Once I reboot it once again works until it reaches the set percentage (unless it's already at that percentage, then it simply doesn't work at all.) I've tried restarting the daemon and even stopping it, waiting a bit, and then recharging, but it still doesn't allow charging. In fact it seems if I stop the daemon it still doesn't charge -- even if I reconnect the charger. I've tried updating (interestingly the update function within acc does actually seem to work just fine) but the problem still remains.

One thing I've noticed that may show a little about whatever is going on is the "test charging switches" function seems to stop working when acc stops being able to control charging. After it successfully charges once it will say "(!) Charger must be plugged in to continue..." twice before it says to press ctrl+c to abort and begins the process, then it will remain indefinitely until I eventually give up and press ctrl+c (not just a few minutes, but as long as I've ever given it which I think was more than an hour at least once.) On the other hand, when it's actually working it only says (!) Charger must be plugged in to continue..." once then almost immediately says "(!) Alright, this may take a minute or so..." and successfully finishes the test saying batt_slate_mode works but store_mode doesn't work. In fact, I never even see the part about pressing ctrl+c to abort. So I think the problem is acc for some reason is still able to prevent charging even after it quits working but unable to tell when the charger is connected anymore after that first charge. Though I can't imagine why it would continue to prevent charging even as the phone eventually drops below 80%.

In addition to stopping and restarting the daemon, I've tried removing and reinstalling the Magisk module itself with no real change there. (This also downgraded it back to the older version which I also tried leaving it on without updating just in case, but no change whether it's the older version or the newer one.) I also use Greenify, so I tried making sure that it's not killing the terminal in case that could affect BusyBox or whatever acc may possibly need., but it seems to have had no effect to stop that. Of course, since it stopped working immediately upon rebooting into a high enough percentage to prevent charging I have to assume it's not due to anything being killed by Greenify (it doesn't kill anything until a few minutes after the screen has been off.) I did originally have the acc GUI app installed, but I also tried just uninstalling it just in case it had issues. Since the configuration is set now and I don't really intend to swap around I just left it uninstalled, so it's pretty much just the console acc tool only now.

Any thoughts that might lead towards getting this working properly at least? I know Magisk is not the way acc is meant to be used, but as far as I can tell it's the only option I have in Android 10 even with LineageOS.

EDIT: Just saw that about the acc -le command. I'll attach a log below. (BTW, I decide to lower the threshold to 94% for now.)