yashsingh1/xdaforums huggingface dataset:
[Magisk] RomainD2:
Is this problem is still present? I have noticed the same think with the original smartcharging feature available on the crdroid ROM on my Mi9T Pro.

I noticed that the problem come from the following kernel wake lock :

c440000.qcom,spmi:qcom,pm8150b@2:qcom,qpnp,smb5

This problem is really annoying and because of that, I never use this amazing feature... Is it only on Xiaomi phone? Do you have any ideas to solve that?

Thanks
[Magisk] esarve:
Hi have anyone faced bootloops after installing the magisk module in MIUI 12 (android 10)?
[Magisk] CheepPlüm:
Why can i not install the djs module?

The app ask me everytime again to intall it...but it is already installed in Magisk
[Magisk] VR25:
I'll consider that.

Thanks for the feedback!
[Magisk] VR25:
You need curl for this feature.

Refer to the documentation for details.

Strange things happen from time to time.

They say that's how life is.

Your system holds a wakelock while the charger is plugged.

You either have to find a way of blocking that wakelock (acc won't help) or set your resume_capacity to pause_capacity - 1 (e.g., pause at 80, resume at 79).
[Magisk] VR25:
AccA does not run in the background.

ACC does.

The app must be excluded from battery optimization only if the root method is not Magisk.

"Force doze" apps won't help.

That's a kernel level wakelock.

The wireless charger does not turn off because the phone still draws some power, even though charging is stopped.

If idle mode is supported, then the phone runs off external power entirely when charging is paused.

Placing a piece of cardboard between the phone and wireless charging pad may help keep the phone cool.
[Magisk] VR25:
Great!

Could you also share a fresh log archive afer installing the latest version?
[Magisk] VR25:
acc 80 20

System must be mounted first.

Generally, you're not supposed to install acc via TWRP, though.

There's install.sh in the zip.

If you don't have Magisk Manager, exteact the archige and run "su -c sh /path/to/install.sh" (no reboot required).
[Magisk] VR25:
DJS needs an update.

Not yet...

Use ACC's own profile facilities instead.

You can have different config files and tell accd to use a specific config.

accd /path/to/config

Refer to the documention for details.

Install the latest version and remove /sdcard/Download/acc/config.txt .
[Magisk] VR25:
The issue is weird to say the least.

It's triggered by writing seemingly anything (file/folder) to /dev/ or /sbin/ or both - and leaving the data there (of course, that data is volatile).

ACC has been doing that for ages (e.g., it stores tmp data in /dev/.acc/.

The thing is, this problem makes no sense.

Both /dev and /sbin use a writable tmpfs and /dev/ in particular, is often used for holding temporary data in addition to device files and such.

That's likely caused by ungraceful shutdown.

ACC goes for it if the graceful shutdown fails.

To test this, launch the camera then run "su -c reboot" on terminal.

I personally shoot for 2000 mA max.

If your battery gets significantly warm or charges from 0-100% in less than an hour, it's probably getting too much current.

Try the usual wireless/voltage_max::9000000
[Magisk] VR25:
You may have seen the solution posted by another user.

This is a WEIRD MIUI 12 issue that can't be fixed by ACC.

Refer to previous posts.

I just found out about and what triggers it.

AccA no longer downgrades acc.

I updated the installer.

Ensure you're running the latest version of the app.
[Magisk] VR25:
Try the latest version.

If the problem persists append " --", without quotes to your charging switch.

For details, refer to documentation > troubleshooting > charging switch.

Read https://github.com/VR-25/acc/tree/v...e-on-oneplus-78-variants-possibly-5-and-6-too
[Magisk] VR25:
Limiting voltage also limits capacity.

3.92 V doesn't really correspond to 80% capacity - and the exact number depends (mainly) on temperature, battery age and charging current.

This feature requires Termux API.

Regular vibrations work only on interactive shells for now.
[Magisk] baldybill:
I was running the 1.0.20 just fine on my LG V20 (US996).

I just updated to the 1.0.26 and I now get "switch doesn't work" on every charging switch I test. As I said, it worked fine on the 1.0.20. But even when I revert back to that one, the switches no longer work.

Can anyone shed some light on this?

In searching the forum, I only ran across the following, which didn't help.
[Magisk] gonzo1963:
Good afternoon,

How do I create the log?

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
Have you switched/upgraded ROMs/kernels as well?

Have you tried the latest acc version on top of AccA 1.0.26?

Does the output of acc -t say the same?

Does the issue persist after removing /data/adb/acc-data/config.txt or /data/media/0/Download/acc/config.txt?

acc -le
[Magisk] baldybill:
Thanks, VR25.

I didn't use any new/updated ROM or kernel.

But I tried out the new acc version as you suggested, and that fixed it.

Thanks! And thanks for such a great tool.
[Magisk] dtrail1:
I've been using this module for quite some time. But it started to misbehave.

It doesn't matter if I use only the module or the app. It always works for one single time, charging to my specified capacity value (I.e. 90%). Then it will only charge up to 70%, no matter what I do or how I configure the module. Only when I reboot my device, it will work again for one single charging process.

I tried all of the versions, settings, etc. without success. I tried this on multiple devices (Samsung and Huawei), with the same result on all of them.

However, I remember that it used to work just fine with an older version. There I was using ACCA (app). But today, when I try Acca with this exact version, it behaves like described here.

I also opened an issue on Github, where other users confirmed this problem.

Is there a way to fully reset the module an its settings, or any other way to fix it? I really tried a lot of things, but if someone knows about a potential solution, please let me know.

Or is it by chance a known problem in certain devices or roms? I use the S9 (starlte) with LOS 17.1.

Thx in advance

Edit: I didn't yet try the latest version. Just seen it. I'll report back later.

Gesendet von meinem SM-G960F mit Tapatalk
[Magisk] gonzo1963:
Good afternoon,

In this moment, I have the AccA app version 1.0.24 installed, and Acc the one that installs the application by default (v2020.5.4-rc), and it works ok.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] dtrail1:
I've installed the latest module without the app, and so far it's working great - Finally!

I want to thank the dev(s) of ACC for this great piece or work! It's an incredible help!

Edit: I'm sorry, but now after my last report, it started again with charging only up to 70%. I've updated my rom (dirty flash, as usual), so I'll try to reconfigure it and see how it goes.

Gesendet von meinem SM-G960F mit Tapatalk
[Magisk] simonchen.android:
Nice app. reserved.:D
[Magisk] DaCHeF36:
Awesome app, dev. I used to use Battery Charge Limit, but it quit working under LineageOS 17.1/Android 10. Seeing Acc/AccA, Battery Charge Limit isn't half as capable! Really cool work...

However, I am seeing the same issue on the 7/26 release. It would work fine the first time after installation, but then on subsequent charges, my Samsung Note 4 would stop charging at 35%. It would report as discharging and wouldn't budge for many minutes. It appeared to use external power fine, as it remained at 35% plugged in, but it never seemed to charge farther than that. I think a reboot might make it work once more, but then it would revert back to this behavior again. I have uninstall the 7/26 version and installed 1.0.24/v2020.5.4-rc to see if it works any better. Based on Gonzo's advice. I'll report if there are additional issues. Much obliged.
[Magisk] swieder711:
I'm running ACCA 1.0.26 on a pixel 3 with stock android 10 (Aug) and Magisk 20.4. Kernel = Kirisakura 1.5.4

The Magisk module is 2020.9.14

I have seen ACCA reset capacity control repeatedly from 95% back to 75%.

Any suggestions on what might be resetting this setting? Do I need to upload my Log file?

EDIT: I deleted all of my profiles because I thought that they might be interfering with my saved settings. I need to read up on how profile work.
[Magisk] dtrail1:
Well, somehow this module doesn't work as intended. After one successful charge I have to reboot my phone, otherwise it would stop charging at 70%

Edit: and the latest problem is that it doesn't even stop charging anymore... Somehow. It stays on the specified amount (in my case 80%), but it doesn't really stop the process anymore. It seems to stop for a short moment and then continues charging again - so it always stays on 80%, instead stopping it entirely until reaching the resume capacity value.

Maybe this module is just a little too complex. All the nice features would be great to have - If it would work properly.

Gesendet von meinem unknown mit Tapatalk
[Magisk] ZXR:
I have the same issue, but I am not using Telegram, so it is not easy to use VR25's support.

Something that might help:

On my S8 (SM-G950F Exynos, Android 8) ACC v2020.7.3 works and charges not only the first time above 70%, it is ok! But later ACC versions, e.g. the current v2020.9.14 has that 70% bug back.

On my Note 10 (SM-N970F Exynos, Android 9) also the v2020.7.3 has that 70% bug, the other ones also.

Whatever the ACC v2020.7.3 does on my S8, it has a workaround. Just sad that it is not working on my Note10.
[Magisk] swieder711:
The "Apply on Plug" setting of "voltage_max::9000000" does not stick on my Pixel 3 XL running Stock Android 10.

Between this issue and the issue listed above Capacity control going back from my setting of 95% to the default of 70%, I wonder if I need to downgrade my ACC magisk module or ACCA application.

Would sending an ACC log help debug this problem?
[Magisk] dtrail1:
Support isn't the best unfortunately. I've opened an issue directly on Github a few weeks back, and they responded once. But after that nothing happened.

I just switched to IPC. It's much simpler, but at least it works without a problem.

Gesendet von meinem unknown mit Tapatalk
[Magisk] swieder711:
What does IPC stand for? I did a couple of searches and couldn't find it.

Edit: I found the magisk module for Input Power Control and will give it a try.

View attachment 5102103
[Magisk] DaCHeF36:
Unfortunately, 1.0.24/v2020.5.4-rc behaves the same. Charging stops at 35% after the first go. Drat.
[Magisk] Koushik87:
I was using ACC bundled with ACCA app and it was working flawless. Recently i had to reset my handset, when i re-installed the ACCA observed the set parameters works for the first time only and after that its presets to default parameters. Doesn't matter how many times you set the values it only works for the first time. Anyone aware of solution or workaround. The version of ACC that came built on was 7.26. I have tried upgrading to latest version of ACC but it has same issues.
[Magisk] ZXR:
I do not want to mention anything negative regarding the support for an app that is free. It is just that he uses Telegram and me not.

Thanks a lot for mentioning IPC (Input Power Control), it works also on my Note 10 and has no 70% bug. Hopefully no other issues.
[Magisk] Juno1337:
OK so I have a question. I apologize if it's something obvious. Is there any way to stop android from reverting the control files to their defaults or is it baked into android? It causes the charging current to constantly fluctuate as the system and the app constantly keep rewriting the control files. I'm using a moto g5s with lineage os 17 (Android 10)
[Magisk] VR25:
Refer to readme > troubleshooting > charging switch.
[Magisk] VR25:
Here are two prereleases.

Reboot after upgrading to reset all temporary data.

**v2020.9.23 (202009230)**

- Cooldown no longer interferes with capacity_sync.

- Delay accd initialization (5 minutes) to prevent conflicts with fbind.

- Do not auto-shutdown if charging was disabled by accd itself at temp >= max_temp.

- Do not remount / rw if it's not tmpfs.

- Fixed cooldown_custom.

- Major optimizations

- MTK and Razer specific tweaks

- New charging switch for Motorola One Vision

- Removed obsolete features.

- Simplified config.

- Updated documentation.

Release Notes

- Config will be reset.

- MIUI bootloop issue possibly fixed.

**v2020.9.24 (202009240)**

- Fixed --disable issue (unplugged).

- Performance enhancements
[Magisk] gonzo1963:
Good morning,

I attach the log files that have been created when installing the latest version.

I can say that in a first test that I have done, apparently this latest version does not work well.

It continues to charge despite having the charge limited to 80%.

Regards View attachment logs.zip

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
The top two reasons I've been using Telegram more often than GitHub/XDA lately, are limited bandwidth and [sometimes] unstable internet connection.

I try my best to provide support, but connectivity issues don't help.

Unstable connection hit my already-limited time a bit harder.

I cannot respond to everybody, for obvious reasons - but I do read all reports - and write them down.

Eventually, fixes/suggestions are implemented.
[Magisk] VR25:
Hi,

Since the latest version resets the config, charging may not stop exactly at 80% the first time.

accd may take a few minutes to test and reconfigure the charging switch.

You can do that manually (fast) with acc -ss command (wizard).

Try that and report back.

P.S., the provided logs are incomplete. When you have to share logs, run acc -le to generate a proper log archive.

Thanks
[Magisk] gonzo1963:
Hello again,

I include again the logs copied from the folder:

/storage/emulated/0/Download/acc/logs

Regards View attachment logs.zip

Enviado desde mi unknown mediante Tapatalk
[Magisk] swieder711:
Good news. The latest release of ACC is holding it settings!
[Magisk] gonzo1963:
Good morning,

I currently have AccA v1.0.26 (2020-07-27) installed and have tried the last two versions of Acc: v2020.9.14_.202009140 and v2020.9.24_.202009240.

It does not work well, it charges up to 100% even though the setting is 80%.

I have tried it several times and it keeps crashing.

I attach the folder logs:

/storage/emulated/0/Download/acc/logs

in case it helps you solve the problem.

I return the AccA v1.0.24 (2020-05-04), with its corresponding Acc included, which is the only one that works for me.

It even works with the smartphone off and charging.

Come on, wonderful!

RegardsView attachment logs.zip

Enviado desde mi unknown mediante Tapatalk
[Magisk] RomainD2:
Hi,

I haven't seen any answer about this subject, dou you have any ideas [MENTION=5228676]VR25[/MENTION]?

Thanks
[Magisk] Macusercom:
My OnePlus 7T Pro seems to always charge to 100 percent since v2020.9.24. Logs are attached.

EDIT: After manually setting

acc -s "s=battery/charging_enabled 1 0"

it works again but it lead to error messages after trying it again after rebooting.

It seems even after 10-15 minutes and a complete reinstall it doesn't test the charging switched and edits the config file.

It was plugged in over night where it reached and stayed at 100 percent for hours.

Furthermore, uninstalling it via terminal leads to a wrong path (see attachments) :)

EDIT 2: Reinstalled v2020.09.14 and it's working flawlessly here ?
[Magisk] beeshyams:
Run acc - t and choose the mode that offers battery idle mode true

[battery/op_disable_charge 0 1] works

- battIdleMode=true

This is for One Plus 7 and other One Plus devices. This is on Oxygen OS

IIRC, developer mentioned this in FAQ on Git (I had requested him to add). I haven't seen your logs but this may help. I am on the ACC module that comes bundled with ACCA. Haven't upgraded
[Magisk] Macusercom:
It doesn't show up as an option if I test all switches. Maybe it's only implemented in the Open Beta? I also don't have OnePlus' 80 percent cap option in the current stable. Are you running the Open Beta? :)
[Magisk] beeshyams:
Nah.. Stable 10.3.4 GM57AA. Sorry can't help, beyond pointing out the switch that works for OnePlus

Edit: Worked since 10.3.2
[Magisk] Macusercom:
No problem, it depends on the kernel as I've read. I'll try that but nevertheless it seems that v2020.09.24 doesn't properly configure the charging switch. Maybe this can be fixed with the logs provided :o

EDIT: On the OnePlus 7T Pro running OOS 10.0.10 and blu_spark r119 op_disable_charge doesn't work, unfortunately. Just an information if anyone is interested. Not sure where to find the commits necessary to include it in the kernel.
[Magisk] beeshyams:
Stock kernel works fine for this feature. Tested on 10.3.2 & 3 (unless the 7T version kernel is totally different, which is quite unlikely. I am currently using Kirisakura kernel for other reasons)

I would suggest you uninstall fully and trying with ACC version 202005040 (bundled with ACCA) and run the command suggested and then work upwards till the last version that works with OP_disable_charge option. That may help dev zero in on the problem
[Magisk] lpcysmi:
I must restart daemon manually each time

Hello:

I have an Xperia z5, and I had not updated in a long time (it used to work perfectly). Last week I decided to update, since I updated like every 10 hours the daemon stops, because my device charges completely, and I most go in to console and type "aacd". This did not happen before... I have tried using the app and the same thing happened it charged completely until I started the app, and then it works for a couple of hours, never more than 10.

Could someone help me.

PS: I updated through MAGISK
[Magisk] Macusercom:
Thanks for your suggestion. I'd need to try it with the stock kernel but while op_disable_charge would be nice though but isn't really my issue.

I was happy with charging_enabled but on v2020.09.24 acc seems to stop working at some point. But as others face similar issues, it doesn't seem specific to my device :)
[Magisk] Zielony360:
I also have constant issues on my OnePlus 7 Pro, Kirisakura kernel, since last few updates. Earlier acc was working fine.

Sometimes it just stops working and charges to 100%. Sometimes it forgets setting made from acc CLI and uses one from config.
[Magisk] medkim:
Hello guys

Is there any command to stop charging after reaching 90% for instance??. Because mine when the battery is down by 1% start charging again
[Magisk] lm089:
Look up acc's README file. The combined Param in config.txt you're looking for is called "capacity".
[Magisk] Camerado:
New version is buggy. Setup at screeshot:

1) Cooldown not working

2) After reaching 80% screen started blinking each 5 seconds and charging not stopped.
[Magisk] dtrail1:
I tried the latest version when I saw the changelog. Unfortunately it's still the same problem - charges only to 70%, no matter the settings.

Gesendet von meinem unknown mit Tapatalk
[Magisk] zioloiso:
Latest version no works good. I have limit 80%, charge to 100%... Previous version works fine.

Wysłane z mojego HD1903 przy użyciu Tapatalka
[Magisk] swieder711:
I have given up on this application. The reported battery level was getting stuck. Phone was not charging properly.
[Magisk] pekkle_hksar:
For those using latest version and charged upto 100% without stopping, most likely it is the charging switch problem.

Information from TG group.

Try 'acc -t' in terminal to check which switch is working.

Then 'acc -ss' and setup the charging switch manually.

Hope this help.
[Magisk] gonzo1963:
Good morning,

Thank you very much for the suggestion, but in my case it does not work.

I have tried with the same charging switch that I have in the version that I currently have: acc_v2020.5.4-rc, and it does not work.

In fact, this version along with AccA 1.0.24 is the only one that works well for me.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
It's in the README.

Some kernels hold a wakelock while the charger is plugged in.

I call that "bad design".

If your system does not have a wakelock blocker, use a resume_capacity of pause_capacity - 1 (e.g., acc 80 79).
[Magisk] VR25:
**v2020.10.1 (202010010)**

- Fixed automatic charging switch management issues.

- Fixed ghost charging problem related to cooldown and capacity_sync/capacity_freeze2.

- General optimizations

- Persistent data is now saved in /sdcard/vr25/acc/.

- Workaround for EdXposed's service.sh bug

Release Notes

- Confirmed: the MIUI bootloop issue is gone.

- If you face any other issue, run `rm /sdcard/vr25/acc/config.txt; accd` to reset the config and restart accd.

https://github.com/VR-25/acc/releases/tag/v2020.10.1
[Magisk] t3chwizard:
It is possible that the magisk core only mode setting in magisk manager could be messing things up, I am going to see if it makes a difference

Yea...That was it...LOL [MENTION=5228676]VR25[/MENTION]
[Magisk] __riptide__:
After updating to latest version (15) I've been experiencing weird behavior. If I disable charging before plugging in the phone it works fine, but if I disable charging while plugged in, the charging indication is removed but percentage keeps rising. Reverting to previous version. My device is j5 (2016) with custom RR os.
[Magisk] Stibit:
Hello! I would like to install an older version of 2017.10.21. Tell me where you can find and download?
[Magisk] dankimani:
I think there should be an archive with past versions of the app. So that anybody can use whichever works for them.

Past several updates haven't been working for me, trying to get the past versions from github but returns updater-script error.
[Magisk] t3chwizard:
https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/post74526435
[Magisk] Hastaloego:
doesn't seem to work anymore since the last update.

i set it to "cs 80 20" and kept the terminal running, but charging didn't stopped at 80%
[Magisk] t3chwizard:
I had the same issue
[Magisk] michaelcrossland:
It's is a Samsung S5 T-Mobile version. I'm running 7.1.2 in my phone I had change the make of the phone from Samsung to htc or lge because the Samsung Gear Manager for there watches will not run on a Samsung phone that don't have the crappy Samsung stock OS that was stuck on 5.x. I well try the new version you have posted. If it able to be gotten from the Manger app or do need to download it from here?
[Magisk] Stibit:
Thank you!
[Magisk] VR25:
A new build is up.

Everyone facing "cs not found" and/or similar issues, please try it and report.

As always, changelog is on the 3rd post.

Those who recently uploaded debugging data due to device incompatibility, wait for the next version -- coming up soon.
[Magisk] EriksR:
Is it safe to uninstall the module without anything left on the phone affecting charging? I guess Disable - Restart - Uninstall? And same for the zzz-cs-service?
[Magisk] guest4711:
What have you done, bro? Now even cs -i fails and overwrites symlinks in filesystem:

jfltexx:/ $ su
jfltexx:/ # cs -i

(!) cs: Unsupported device

(i) Gathering debugging data...
mv: can't remove '/sdcard': Read-only file system
mv: can't remove '/sdcard': Read-only file system
chmod: /sdcard/cs_debug*: Not a directory
- Done.

(i) Please upload /sdcard/cs_debug.zip to the official XDA thread.

Previous version did not show errors like them... And I hope you did not try to "rm -rf /sdcard" :eek:

Edit: I noticed that cs destroyed the link "/storage/self/primary" (which pointed to "/storage/emulated/0") and replaced it by the debuglog.zip using the filename "/storage/self/primary" :( :( :(

"/sdcard" is also a link pointing to "/storage/self/primary" on my S4.
[Magisk] t3chwizard:
Feel free to hit the thanks button if I helped :)
[Magisk] VR25:
If you uninstall the module, cs service won't do anything -- simple as that. In the next version, /magisk/zzz-cs-service/service.sh will auto-remove /data/media/cs and self destruct afterwards if /magisk/cs doesn't exist.

Oh man... that's bad! "cs debug" code hasn't been touched for a while now. Not sure why that happened to you. Check the attached screenshots.