yashsingh1/xdaforums huggingface dataset:
[Magisk] iamjimmy:
Anyone using the pixel 3 XL with the ACC?

The battery levels in the ACC app are always lower than displayed by Android.

I did 2 full charge and discharge cycles to recalibrate the battery.

Also charged to 100 percent using ACC as well.

No matter what I do, there is always a variance between ACC reported battery and Android reported battery.
[Magisk] BostonDan:
This has been the case for me as well (Pixel 3 XL). I do not reset battery stats upon unplug, etc. and it keeps the discrepancy smaller. When I use to reset the battery stats through ACC, sometimes it would have a difference of 30-40%.

Cheers,

B.D.
[Magisk] iamjimmy:
Thank you. Thanks so much. I was going NUTS. I thought my phone was DEFECTIVE and that the battery was bad.

So it seems this is a BUG in app, and it doesn't behave properly with the Pixel 3 XL. Hopefully [MENTION=5228676]VR25[/MENTION] can fix this in a future release.

Also have you observed ANY battery drain with this app? I mean has it been good with your phone or do you see extra battery drain because of using ACC? Thanks.
[Magisk] k0rner:
I also have Pixel 3 and noticed this behavior.

ACC reads battery level as it is reported by Android kernel, but Pixel software (google_charger module and above) displays lower battery percentage by some design choice.

So it looks like it's not a bug in ACC, but rather a Pixel 3/XL "feature".

"100%" reading matches between kernel value and OS-provided value, but lower than that it differs.
[Magisk] jiexi:
Are you on android 10?
[Magisk] KapilNagpal01:
[MENTION=5228676]VR25[/MENTION] sir as discussed before I have been able to seek support for OnePlus 7 with kernel developers in our forum. They are willing to support by adding a commit for setting max battery charging voltage value at custom values.

They are asking me to provide commit and they would add the same to the kernel. Can you help us by providing the commit to be added? Thanks for your support. :svetius:
[Magisk] iamjimmy:
Actually I've found that the P3XL battery % is ALWAYS higher than the ACC battery %.

Sometimes the difference is 5-6%. Sometimes it's as high as 10-15%.

So ACC might say battery % is 72%, but P3XL will say 83%.

If I charge the phone to 100% per P3XL charge status, ACC still shows 88% or so. Then I kept on charging until BOTH ACC and P3XL said 100%.

At that point there was no discrepancy. But as the phone discharged, after a few cycles, now again the difference is like 7-9%.

In contrast to that, P2XL is dead accurate. ACC % always ties to P2XL reported %. I think the app might NOT work well for the P3XL.
[Magisk] lollyjay:
OK I am a dummy! I flashed the ACP app and I cannot find it. What am I doing wrong? :confused:
[Magisk] ktmom:
If you flashed in recovery, then you flashed the core ACC module. Open a terminal, switch to root (su) then type "acc -i". You should get a list of status information.

The app is an APK that is installed through the android package manager.

I personally use ACC through the terminal, and it can be used as a set it and forget it tool that way as well. The README file on VR25's github page has loads of information.
[Magisk] lollyjay:
But I cannot find the download for the acc apk

Link?
[Magisk] ktmom:
https://github.com/MatteCarra/AccA/releases/ see the attached screenshot.

If you read the README file I linked before, the link to the app was there.
[Magisk] lollyjay:
Thank you for your assistance ?
[Magisk] sicut:
Same happening on my S10E (stock, rooted, latest TWRP), so its definitely the combination of S10 + ACC.

Even without clicking the Reboot option in MM it instantly reboots and bootloops until u delete the module in TWRP again.

If anyone needs logs, Id be happy to help too.
[Magisk] Mikes:
ACC is trying to read some debug file which Samsung for some reason forbids. Try to flash this modified version. It's working on my S10+.
[Magisk] gu200123:
Charging stopping at 40c temp

Hi!,

First of all, this is a one of the best modules, if not the best

I was using the old version (mcs) until today, I had to reinstall my rom, so I updated magisk to lastest version.

Installed acc, then I saw that when my battery reachs 40c temp, thephone says that its charging but stops. It gives live 100 mA to battery and holds charge on current percentage, until reboot.

I did some research, then disabled coolDown and temperature control (via terminal and app) and changed the charging switch but no success. I tried to read the logcat, but couldnt understand.

I am attaching my logcat and the config file, hoping to solve it and get back using this great module.
[Magisk] VR25:
Recent (unreleased) versions have that fixed.

One of these was recommended below your comment.

Thanks!

Your config has an issue: null values are unacceptable, except for language.

Run "acc --set reset" (or "acc -s r") to reset the config.

The cool down feature is disabled by default.

Providing relevant logs:

1. Reproduce the issue.

2. Shortly after, run "acc --log --export" (or "acc -l -e").

3. Send me /sdcard/acc-logs-*.tar.bz2.
[Magisk] KapilNagpal01:
[MENTION=5228676]VR25[/MENTION] can I get some support from you for commit to be added in kernel to control the max voltage for OnePlus 7. Thanks in advance for your support
[Magisk] VR25:
Indeed that's a Pixel "feature".

But I'd rather call it "ugly bug".

In fact, people who don't even use acc are facing worse battery/charging issues.

I've been watching these closely - so much so that two acc features (capacityOffset and capacitySync) were born specifically for such scenarios.

I recommend using capacityOffset. The syntax is either +Number or -NUMBER (default value: +0). This is added/subtracted to/from the capacity reported by the Battery Management System (kernel level).

Command: acc -s capacityOffset VALUE

Also, turn off resetBsOnPause, to prevent further fluctuations in discrepancy.

Command: acc -s resetBsOnPause false

I'm not into kernel development (yet).
[Magisk] VR25:
Motorola devices (Snapdragon) are well known and supported.

Use the acc app: https://github.com/MatteCarra/AccA/releases/

Work in progress

Setting a specific charging switch may help

Check the readme's troubleshooting section: https://github.com/VR-25/acc/blob/master/README.md#charging-switch
[Magisk] VR25:
"acc -v" prints the max charging voltage. If it wasn't altered by acc, the output is "Default".

"acc -v :" outputs available voltage control files. None was found on your system. Send me "/sbin/.acc/acc-power_supply-mako.log" for analysis.
[Magisk] ktmom:
[MENTION=5228676]VR25[/MENTION] just wanted to give you a heads up that a small donation is on its way to you. Thank you very much for developing and supporting ACC. This is single handedly the reason I root my devices.
[Magisk] VR25:
New Pre-release: https://github.com/VR-25/acc/releases/tag/201910130

- It's ready for daily use - new and advanced users alike.

- Among a handful of new features and a massive number of changes, this version embraces the idea that simple is better. So, all features are disabled by default, except resume-pause capacity limits. Essentially, that's mcs with optional steroids.

- Whether or not you're using the app, acc can be upgraded from Magisk Manager, EX/FK Kernel Manager, or similar.

- Those who are using a version newer than 2019.7.21-r1 can also upgrade by running acc -u dev as root.

- Updated documentation: https://github.com/VR-25/acc/blob/dev/README.md

EDIT: version 2019.10.13-r1-dev is up. It fixes `acc --upgrade`, but you have to flash the zip this time.

EDIT 2: you can upgrade to build 2019.10.13-r2-dev from the previous, with "acc -u dev" or "acc -u 201910132".

Thank you very much!
[Magisk] Droid_JD:
How it's ok to put this here, but has anyone been able to use any feature other than "capacity control" on a 6T?

Vr25 and team, love the work! Thank you so much!
[Magisk] shuini:
How to use acc without root and without Magisk?
[Magisk] guest4711:
You simply can't. Root is needed for changing the charging parameters.
[Magisk] Droid_JD:
With extreme difficulty.

You need root to use ACC.

What device do you have? There's likely a root solution for you.
[Magisk] shuini:
Can I use Init.d to boot the operation?
[Magisk] VR25:
Without root, you cannot install acc, configure it, grab logs, stop/restart accd. You need superuser privileges to work in /data/adb/, which is where acc and its config file live.

With init.d and missing "su", the daemon can still be started on boot. Init.d scripts are executed by init*, which always has superuser access - whether or not the system is actually rooted.

* A Kernel Mythology god
[Magisk] shuini:
Thank you for your warm answer
[Magisk] iamjimmy:
Pardon my ignorance, but does anyone know how to get the .apk installable file for this release. On the linked page the Assets section only has the . Zip and the .tar files.

I'm currently using the previous version of 2019.7.21. I'm just using the GUI version and did not install the command line version.
[Magisk] sicut:
Sorry for the late reply, but I was customizing everything else first before coming back here.

edit

: It worked just fine when installing it via Magisk. Sry for the inital mishap. Thank you for pointing out the that it works with the beta releases!

(original post:

Your posted version and the latest version (201910130) both are giving me error 255 when trying to flash it :-/

recovery.log:

I:operation_start: 'Flashing'
Installing zip file '/sdcard/Download/acc-201910130.zip'
Checking for Digest file...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
[B]E:Can't execute '/tmp/updater': No such file or directory[/B]
Updater process ended with ERROR: 255
I:Install took 0 second(s).
Error installing zip file '/sdcard/Download/acc-201910130.zip'

Could you please point me into the right direction by any chance?)
[Magisk] ktmom:
The app (GUI) installs the acc backend for you. I think the easiest way to update is to use a terminal app, and issue the following commands;

su
acc -u

This switches to root rights then updates the acc backend.

Other choices are use the acc module in Magisk manager or use Franco's Kernel Manager to flash the acc zip file.
[Magisk] VR25:
ACC is not built to be installed from recovery.

Install/upgrade from Magisk Manager, FK/EX Kernel Manager, or similar app - whether or not you're using AccA.

Alternatively, if you are on version 2019.10.13-r1 (201910131), you can also upgrade by running "acc -u" as root.

Rebooting after installation is unnecessary.
[Magisk] KaMyKaSii:
[MENTION=5228676]VR25[/MENTION] I just upgraded from acc 2019.10.13-r1-dev (201910131) to latest version using the "acc -u" command, the update was successful but the script did not exit automatically. No big deal but I found it necessary to report
[Magisk] iamjimmy:
Thank you for the instructions. I tried the commands using the Terminal emulator for android.

When I ran the acc -u , I get the following error:

"wget: bad address 'raw.githubusercontent.com'.

Any guidance on what could be done?

Another point: In the ACC GUI app there is a settings -> ACC version. Right now it is defaulting to the "bundled version". However there is an option for version "201910132" . Will selecting that upgrade the version? Or am I totally off-base?

Sorry about the newbie questions.

Apologies again: https://github.com/MatteCarra/AccA/releases -- It seems there is a NEW release for the app which contains a newer version of ACC.
[Magisk] ktmom:
I understand that you have solved your immediate problem. But...

If you are running an ad blocker, firewall or similar, try disabling it for the update. This works fine on my device.

I don't use the app, but my knee jerk is, just try it [emoji16].
[Magisk] VR25:
Yes, I noticed that.

It may be a shell limitation or wrong logic somewhere.

Pressing the enter key triggers exit.

I'm investigating.

Thanks

Some users faced an issue with the program wget (missing HTTPS support) - hence the "bad address" error.

Versions >= 2019.10.13-r1-dev (201910131) use curl instead.
[Magisk] Omer89:
It gives me error when flashing via TWRP and thr same via magisk.
[Magisk] ktmom:
Have you tried starting acc using the button in the app? Have you used a terminal to verify that acc is installed (run as root; acc -i)?

The app installs the acc backend for you. Within the last 10 or so posts is a discussion on updating.

What are you flashing in TWRP?
[Magisk] VR25:
1) Note that acc is not meant to be installed from TWRP.

2) Which version are you trying to install? Always check for updates.

3) What specific error(s) are you stumbling upon?

4) Installation and initialization logs are stored at /data/adb/acc-data/logs/.
[Magisk] Omer89:
Whenever i try to install it via magisk gives me the error In the attached ss below
[Magisk] JV Spartacus:
This version does not work for me too .go to github link or telegram group for latest one
[Magisk] VR25:
Download the latest zip from https://github.com/VR-25/acc/releases/latest/.
[Magisk] Omer89:
Thanks, but I have to ask how to install that zip ? As you mentioned it doesn't meant to be flashed via TWRP, sorry for my dumb question.
[Magisk] ktmom:
See this earlier post:
[Magisk] Ijustneedoneapp:
K so Dev isn't responding and telegram group isn't found. So maybe someone here can help. I got the acc app, put it on default profile which is set to stop charging at 80. It doesn't. Why? I have the right charging switch set to battery/input_suspend 0 1 (the only one that says it works) and my battery doesn't stop at 80.
[Magisk] Droid_JD:
This may sound silly, but the daemon is running, correct?
[Magisk] iamjimmy:
Pardon my ignorance. What does [MENTION=5228676]VR25[/MENTION] mean when they say use "curl" instead.

Apologies for the newbie question.

I've had errors flashing ACC using Magisk. So I've been just installing the APK using the link: https://github.com/MatteCarra/AccA/releases

This installs ACCA v1.0.20 (24) and ACC version: 201910132 - when I go to the app and setting -> About

Does this mean that the latest version of ACC has NOT been installed? Will I need to use a terminal emulator and do acc -u (I get Wget errors).

Should I try to uninstall ACCA and then flash the .zip linked in the latest release from [MENTION=5228676]VR25[/MENTION] in Magisk. I'll reboot and try. Maybe flash factory images and then try?
[Magisk] ktmom:
The statement:

means that the wget command has been replaced with the curl command in versions equal to or higher than 2019.10.13-r1-dev.

There is no reason to flash factory images for anything to do with ACC.

You can get ACC current version information in a terminal with: acc -V (-V|--version Show acc version code)

I don't use the app, but 201910132 is higher than what I have installed on my device. Though I don't tend to chase every release [emoji6]
[Magisk] crackers8199:
am i missing something on how to get pixel fast charging to work? i added the line to the config file, but it doesn't seem to have any effect. if i manually go in and edit voltage_max while the phone is on the charger, fast charging works...but acc doesn't seem to do anything.

edit: nvm, i'm an idiot. figured it out.
[Magisk] crackers8199:
is there a way to get it to only reset battery stats at 100%? mine seems to be resetting whenever i take it off the charger, regardless of what level i'm at. i have reset on unplug as false, but it's still resetting them when i pull it off the charger...
[Magisk] ktmom:
I don't use the app. The same config file is used for both the basic cli install and the app.

It may be that you have the "resetBsOnPause" set to true, even though "resetBsOnUnplug" is false.

These are the two settings that apply:

# Reset battery stats after pause capacity is reached. If enabled, this may temporarily worsen capacity report discrepancies between Android and the BMS on Pixel devices.
resetBsOnPause=false

# Reset battery stats every time charger is unplugged, as opposed to only when pause capacity is reached.
resetBsOnUnplug=false

I would double check the configuration by using a terminal app (I use Termux), you must switch to root (su command), then run:

acc -s

You'll get the current configuration on your device. The default configuration includes comments for each possible entry.

# acc -s

versionCode=201910130
capacity=0,60,75-80
capacityOffset=+0
capacitySync=false
temperature=70-80_90
coolDownRatio=
resetBsOnPause=false
resetBsOnUnplug=false
loopDelay=10,15
chargingSwitch=battery/charge_disable 0 1
applyOnBoot=
applyOnPlug=
maxChargingVoltage=
rebootOnPause=
chargingOnOffDelay=1
language=en
wakeUnlock=
prioritizeBattIdleMode=true
forceStatusAt100=

On the command line, you can toggle the setting using:

acc -s resetBsOnPause false

-or-

acc -s resetBsOnPause true

The config file resides at "/data/adb/acc-data/config.txt"
[Magisk] robbayani:
why default value "temperature=40-45,90"??

is 40°-45° really harm for battery??

i'm charging always stop in around 40%-50%..
[Magisk] Macusercom:
Does acc already support A10? I couldn't find anything so I guess it hasn't been tested yet? :confused::)
[Magisk] goRt:
Working on my OnePlus 6 A10 ob1
[Magisk] ktmom:
It looks like a problem with your busybox install.

What device, root method and OS?

Could you please go back and edit you post, putting that long terminal output into hide tags.

"[" HIDE "]" some text here "[" "backslash character" HIDE "]"

Remove spaces and quotes in above example. The "backslash character" is the one that starts to the left asked goes down to the right. The forum software doesn't display it.

You could always put terminal output into a text file and attach it to a post.
[Magisk] jasonkhoo87:
Sorry for long terminal post, I have edited it. Using mobile phone to post.

By the way, I am using busybox stericson 1.30.1.

Root method by twrp

Using Samsung Galaxy Note 3 running Android 5.
[Magisk] ktmom:
By "root method" I meant are you using Magisk, SuperSu, kingo, something else.

From [MENTION=5228676]VR25[/MENTION] README documentation;

The thing is, I don't see that script, but I assume amongst other things, it calls (install path)/acc/busybox.sh which simply adds busybox to the PATH variable. You might be able to do the same thing manually;

PATH=/sbin/busybox:$PATH
[Magisk] EriksR:
Using MCS all versions since last month, and when using cs value, it stops charging if I am on the phone that moment with screen on, but if I lock the screen and open again - phone starts charging again. Also, whenever I left it overnight, it always ended up at 100%, ignoting the cs value.

Terminal battery optimixation is excluded.

LineageOS 14.1, device SGS3 (d2att)
[Magisk] t3chwizard:
Try this it might work https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/post74497160
[Magisk] VR25:
[MENTION=5358604]rjmxtech[/MENTION], did you try the beta version I just uploaded? It was especially designed to wok as you described. Using a script as such with previous versions generates a lot of garbage in relatively short time. This might negatively impact you device's performance if you left it powered on for a couple of days straight. That's why I never recommend such a practice.

The repo hasn't been updated to 2017.11.13 build. So, if you installed the beta, simply download the latest stable version from Magisk Manager.

I have an idea to overcome that issue. Wait for the next build.

To all: every time you report a compatibility issue, please provide a cs_debug.zip -- or a link to a previous post containing it. -- Thanks
[Magisk] t3chwizard:
Where do I find the beta build?
[Magisk] guest4711:
A few posts back: https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/post74496610
[Magisk] EriksR:
:good:
[Magisk] Younex:
I installed this and I'm not sure, does it do anything on its own or do we HAVE to set it up from the terminal ? Haven't noticed any battery pausing/resuming yet.

TIA :)
[Magisk] guest4711:
See the instructions in OP. You should open a terminal and execute commands like

su -c cs 80 20
[Magisk] VR25:
If you installed the beta version, it'll work on it's own without any user interaction whatsoever. In that case, "cs 90 10" (default) config is set automatically.

As stated previously, though -- you should've read the OP before installing this thing.

Make safety one of your best friends by reading instructions prior to using a product.
[Magisk] EriksR:
I'm looking forward if ever/whenever you'll come up with a user interface. A slider, couple buttons maybe.
[Magisk] x1reN:
Hello all, I would like to install this module. I rooted my SM-950F now but I have to be honest, I have no idea how to install it now. I'm not that stupid, just need a start and so on, is anyone able to explain it?
[Magisk] guest4711:
1. Download the beta-version (see https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/post74496610 )

2. Open MagiskManager, select modules, add (+), select the zip just downloaded and let it install

3. Reboot

See also the guide in op and https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/post74503764
[Magisk] x1reN:
Thank you! Can I edit the created file somehow? Which App do I need?
[Magisk] guest4711:
You need an terminal app (usually inluded in your ROM) or a similsr app like Terminal Emulator for Android (Access Android's built-in Linux command line shell. Unleash your inner geek!) - https://f-droid.org/app/jackpal.androidterm

And you should read the instructions in first (or opening) post (aka OP). It will tell you the meaning of the parameters of cs command.
[Magisk] iluvatrix:
I've downloaded the beta, opened Magisk Manager, selected Modules , added + the zip but for the life of me I can't figure out how to install the zip. Someone throw me a lifeline.

Thanks

Edit, managed to install by long press the zip then click Open
[Magisk] iluvatrix:
I'm using a Nextbit Robin on Los 14.1 official.

I've installed latest beta , able to test cs -i & also set cs 80 78

The charging does stop at 80 but does not restart at 78 or lower.

If I do cs -e then the charging will resume but go past 80

Is this still an unsupported device issue?

What should I get & attach to get a fix?

Or do you think I should try the official repo version?
[Magisk] __riptide__:
Love this mod, working like a charm on my j5 2016.

Quick question: if charging is paused through this mod but the charger is physically connected, does the device use battery power or power from the charger?
[Magisk] Droid_JD:
Love the Mod, but I wish it worked for me.

Running Pixel XL (Marlin) with Stock Oreo (8.0) and Magisk 14.3

Older versions of the MOD would charge the battery beyond the intended level, but the batt% in the status bar would NOT increase. (For example, if at 50%, then after 10, 20, 30 mins, the Batt% would still remain at 50%). When I ended the Mod, and rebooted the phone, the Batt% would report more accurately (i.e. 90%, 100%, etc. )

Using this Beta version, the Batt% in the status bar would update continuously, and the battery would charge beyond the intended value.

See attached screen shot and CS_Debug. When I started CS, the battery level was at 48%.

Hope this info helps!