yashsingh1/xdaforums huggingface dataset:
[Magisk] T Ghost1:
Slow charge on my Infinix Note 2, my phone usually charges fast 1.30 to 2hr at most, but at the cost temperature surge 😕 but since I started using Acc that changed, it takes 3-4 hours to full charge😞 really like Acc but I guess I can't have everything. Nice module by👍👍👍#VR25 #ACC
[Magisk] Vantskruv:
Hello! I have a question!

If prioritizeBattIdleMode is set to true, what is the behaviour if using a wireless charger? The option works on my device (Pixel 4XL) when using a wired charger.

I guess it will not work, maybe even not recommended? But it would be cool if it would.

I currently do not have a wireless charger, but thinking on buying one to relieve the mechanically wear on the USB-C port.
[Magisk] Vantskruv:
Could not resist and bought myself a wireless charger.

It seems to work great for now, temp is low (currently 26.5 C) while using battery idling mode, and I am currently supervising it. :)
[Magisk] Fif_:
Do you have charging optimization turned off? I suspect it uses the same sys switch as acc (battery/op_disable_charge) and night interfere with it?

Also, would using "battery/input_suspend 0 0" have any effect since it's using 0 for both turning charging on and off?
[Magisk] VR25:
**v2021.9.19 (202109190)**

- Additional charging switches - the database is more concise with the extensive use of wildcards.

- Battery status detection enhancements

- capacity_mask=true: forces Android to report capacity = capacity * (100 / pause_capacity), effectively masking capacity limits. This replaces capacity_freeze2.

- current_workaround no longer requires a reboot (just accd --init).

- Fixed cooldown and acc -f issues.

- General fixes & optimizations

- Optimized --parse (acc -p).

- Support for "volatile" plugins (gone on reboot, useful for debugging): /dev/.vr25/acc/plugins/

- Updated documentation (mainly tips > idle mode and alternatives)

- Upgrade rollback feature (-b|--rollback or wizard option f)
[Magisk] VR25:
Broken Kernels Killing Charging Control

Extensive testing suggests that several kernels have been messed up lately.

Either the manufacturers themselves are doing it on purpose or something extraordinary is going on.

To put that into perspective, some devices even have 6+ known charging switches. Yet, none works.

While I'm still keeping an eye on this issue and trying to come up with workarounds, don't expect much from my actions.

This should be addressed with actual kernel patches.

Start threatening kernel devs with guns.
[Magisk] VR25:
Idle Mode and Alternatives

1. Charging switch that supports idle mode (the obvious winner).

Note that self discharge is a thing.

This is as if the battery were physically disconnected.

Extremely slow discharge rate is expected.

2. charging_switch=0

If current fluctuates, also set current_workaround=true (only takes affect after a reboot).

If this method works, the behavior is exactly the same as #1.

3. charging_switch=3920: only works on devices that actually support voltage control.

Unlike regular idle mode, this maintains 3920 mV (the sweet spot) indefinitely.

This is not good with higher voltages.

We're trying to minimize battery stress as much as possible.

Maintaining a voltage higher than 3920 for a long time is not recommended.

4. acc 3920

This is short for acc 3920 3870 (a 50 mV difference).

It tries to maintain 3920 mV without voltage control support.

Yes, it's definitely not a joke.

This works with regular charging switches and voltage readings.

5. acc 45 44

I prefer this over acc 50 49, since voltage and capacity (%) do not have a linear relationship.

Voltage varies with temperature, battery chemistry and age.

Considering those variables, acc 45 44 is more optimal than acc 50 49.

50% is more likely to translate to voltage values higher than 3920 mV.
[Magisk] Koushik87:
ACCA app keeps freezing and force closing whenever new values are applied. Profile also doesn't get applied. Running OOS A11 with MCD kernel on my Fajita (OP 6T). Any1 can suggest workaround. I don't want to go terminal emulator way.

Using ACCA version 1.0.35 and ACC version bundled with it.
[Magisk] gorilla p:
Regarding my issues with the OP9, this appears to be one with an aforementioned broken stock kernel? Constant problems with daemon failing while charging.

Arter97 just released a Non-OOS but CAF-based kernel and ACC is working fine with it so far, at least while plugged in. Will test wireless charging soon.
[Magisk] VR25:
**v2021.9.20 (202109200)**

- General enhancements

- Manual capacitySync toggle (`[capacity_sync|cs] = [true|false]`) - it overrides the automatic. Both include the `freeze at 2%` feature. This is the actual `capacity_freeze2` replacement now. `capacity_mask` implies `capacity_sync`.

- Unlike in previous versions, changes to `capacity_mask` and `capacity_sync` take effect (within a few seconds) without a daemon restart.

- Updated documentation
[Magisk] VR25:
There's a new front-end in town.

I've been working closely with the dev.
[Magisk] Koushik87:
Thanks. The UI is pretty simple but looks promising. I am excited to see the final version of it. Thanks dev and will let know for any specific observations on this test version.
[Magisk] yg213:
My battery life is down after install ACC via AccA. My phone's minute per %1 was 5-6 minutes before, and now %2-3. Also, Charge is decrease (%14-15) even after I do not use my phone for 7-8 hours. I uninstalled AccA app and ACC by executing the uninstall file but nothing changed :\\
[Magisk] Vantskruv:
Yeah, something new with the kernel is disturbing the charging, having big problems after upgrading Android Coral from june version to september version. Had the phone cable-connected to power while sleeping tonight, it sneakly charged it up to 77% from 46% in 6 hours, but I wanted to be in idle mode keeping (charging span between 39% to 42%).

So it seems ACC bravely is fighting for its life not to charge, as I told it to do. :D

Using v2021.9.19.

(I did see now a 9.20 version is released ...)
[Magisk] Koushik87:
The 9.20 acc version is working fine for me now along with new UI app. However, the new app for ACC is missing DJ's. Hope this will be incorporated in future builds of the app.
[Magisk] Koushik87:
Please check if you are coming from clean install of a kernel. Sometimes leftovers from previous kernel can cause such issues. Suggest re-flash stock/custom rom then Kernel and try acc version 9.20 if there is any improvement.
[Magisk] yg213:
My last kernel flashing was:

1. system recovery > wipe cache partition

2. flash everything (boot.img included) of stock ROM without PRELOADER (sp flash tool)

So I don't think I am coming from bad installation of kernel

%4 has gone even writing this :/

I will try re-flash without USRDATA.
[Magisk] CapnRene:
Hi! Can't get ACC or ACCA running. I keep it short and give a thread url: https://xdaforums.com/t/managing-battery-charge.4337129/
[Magisk] yg213:
I re-flashed ROM but nothing changed, I think ACC damaged my tablet's battery.
[Magisk] melphoi:
Hello, I installed ACC module from Magisk on stock ROM A11 Pixel 3 with Kirisakura Kernel

I set ACC to pause charging at 80 and resume at 50, it seems working but the charging stopped at 70-73% instead 80%

And also when I try to check on charging switch, it says :

[battery / step_charging_enabled 1 0 ] won't work

[dc / input_suspend 0 1 ] won't work

While the other 2 charge_disable and input_suspend says "works"

Maybe someone could me by pointing to where should I look for the fix, cause I'm noob myself, and the documentation kind of confussing for me

Edit : I got it working now, and also I think editing the commands via Termux works too.

But still what bothering me is why the charging process stopped at 70% instead of 80% :unsure:
[Magisk] gorilla p:
ACC is working on my OP9 with the latest update while plugged in.

When using wireless charger, it continues to charge to 100%, despite ACC daemon being active.
[Magisk] VR25:
README > TROUBLESHOOTING > CHARGING SWITCH
[Magisk] thirtythr33:
anyone have AccA working on op9 pro, 11.2.9.9, and latest Omega kernel?
[Magisk] swords90:
Works good new front-end with op6t.
[Magisk] gorilla p:
Nope. Attempting to use this on my OP9 with Omega and fails while wireless charging. Daemon active but wont stop charging.
[Magisk] thirtythr33:
ah damn thanks for replying though hopefully will work in the future (loved this mod on my 6T)
[Magisk] Ascii3:
Thank you @VR25 for the Advanced Charging Controller (ACC) software.

I want to bring to your attention to a related problem/complication that I believe many Android users face, including myself: The Android charger/charging port is quite often co-mingled with the USB port and such Android devices are configured to always charge when connected to a USB-cabled power source, regardless as to whether that source is for data, alternate mode function, or other non-charge function. Oftentimes one wishes to use the USB port for its USB data function only and not perform charging operations unless necessary (even more especially so when the host source providing the charge is itself running on battery and it is important not to drain the host).

Is there a way to

automatically

have the charging settings be applied differently, depending on what kind of connection (charger, USB data, USB alternate mode, etc.) is being negotiated? If not, would you please consider its implementation?

Also, is there a way to disable special or fast charging standards like the various Quick Charge and Power delivery standards, so that one may just rely on basic USB bus power to charge? If not, would you please consider its implementation?
[Magisk] Saphira209:
I've been using ACC normally without issue for a long time, but since a few days ago my phone keeps charging to 100% over night, no update or change was made before this.

I have checked to make sure acc was running before going to sleep last night, but in the morning phone was still fully charged and in the command it shows acc daemon is not running.

What might be the problem here? I'm using Redmi K40 with xiaomi.eu rom.
[Magisk] Bjberry00:
Hey, I'm new to the ACC World. Just downloaded ACC via Magisk (23) on my mi 10 ultra with weekly xiaomi.eu 21.9.28.

Also I downloaded the settings app.

I did no modifications what so ever, but it seems, it's not charging at 120W anymore.... :-(

What can I do? What did I mess up?
[Magisk] TioCareca:
some xiaomi's had reported dying after using this because of faulty pmic chip....
[Magisk] Bjberry00:
Hmmmm .....that's good news!!! NOT!

How do I get it off the system? Will removing in Magisk be enough?

And to be clear, it's still charging at "lower" speeds.
[Magisk] TioCareca:
just removing from magisk is enough.
[Magisk] gorilla p:
Running initial test on wireless charger provided

:/ $ su
:/ # acc --test

(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...

(!) [/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/mmi_charging_enable 1 0] won't work

:/ #
[Magisk] LNS:
Damn, being on xiaomi thats something worth mentioning at install, good thing I stumbled upon your post. Thanks.
[Magisk] TioCareca:
it's not all, there were reports on all line of poco's and in some redmi 9 and note 9, in telegram some said its on others too, but i still to see real report of that...
[Magisk] LNS:
Well it's very worth mentioning if devices are dying("all line of poco's"). I believe the dev will do what's needed informing users if this indeed is happening. (I Am on a note 9s btw)
[Magisk] liott:
Hi, I don't understand what's going on every key pressed on the keyboard produces this strange effect :

Tested on different keyboards and laptops
[Magisk] TioCareca:
you not pressing the right option, or its not recognizing
[Magisk] wilsonhlacerda:
Hi Tio! Can you please give us more info on that??? What is exactly dieing? Mobile itself, charging in general, fast charging?

Can revert it??? Or does it cause a hardware damage?

Well please tell us everything you know! And maybe point to us where other people are talking about that. This can be a problem to lots of people if a confirmed bug.

I'm just about to start using ACC on both Poco X3 NFC and X3 PRO. 😲😲😲
[Magisk] TioCareca:
hi, it started here:

[ROM] [OFFICIAL] ArrowOS 11.0 [android-11.0][vayu/bhima]

ArrowOS for POCO X3 PRO (vayu|bhima) ABOUT ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat. Website: https://arrowos.net Telegram: Channel | TG Portal/Links Github: https://github.com/ArrowOS...

xdaforums.com

and was talked in telegram and some people said the same, and some reported there that was seen in others outside poco line...

As i had understand its hardware, the pmic (charge controler) bug when used smart charging or other power supply options and phone stop charging completely, until now don't know if it's possible to revert...
[Magisk] liott:
On the screenshot I pressed 9 > > Edit config.txt

All the options produce this mess of the keyboard.

What do you mean by 'its not recognizing' ?

EDIT : please help me, I just reinstall everything on my old S4 mini (from scratch) LOS18.1 + magisk + acc plugin >> same crazy keyboard :(
[Magisk] Valiante:
Not sure what the heck happened but my device is continually charging to 80 and discharging to 60 before charging again.

I have battery idle on and it worked in the past so I'm not sure what's going on?

I want it to charge to 80 and stay there ...
[Magisk] TioCareca:
same phone and same rom?

battery idle is kernel dependent, if kernel don't support it will not work....
[Magisk] Valiante:
Yeah everything is the same, I just had to reinstall the app because I was testing something. But when I reinstalled it, battery idle wouldn't work anymore

Edit: like an idiot I left my rom's smart charger enabled. Problem is now solved lol
[Magisk] StefCGN:
Hi,

i was trying to install the APK on my SM-T800 Tablet with LineageOS and SuperUser installed.

The App is starting but tells me, that installation failed. I should send the Logfile, bute in the mentioned path there is no logfile.

Does anybody have an idea?

Edit: Busybox was not installed. The charging was working one time.

The charger remains in the slot and currently the battery is below 56%.

I have enabled the "Default" Profile, which is 80% to 60%. Currently, it says, it is discharging, but it should be charging.

Any ideas?

Thanks
[Magisk] StefCGN:
HI,

is it also possible, that the cable stays in the slot and the charging process repeats everytime from 60% to 80%?
[Magisk] zenfone selfie:
tried this on zenfone selfie(z00t) using groovy nougat rom and didn't work. phone just keeps charging
[Magisk] roxy1712:
Just started using the app again on my Pixel 4a.

Is there a bug that's keeping the screen on while charging? I have my phone set to keep screen off, AOD is off, but it keeps popping back on. Charger is firmly plugged in at both ends.
[Magisk] arik100:
just wondering,

is this still useable if i have android 12 and poco x3 pro?

thanks
[Magisk] 73sydney:
why not install and test it, theres an automated test via the ACCA app to see if the ROMs kernel supports a range of charging switches

its what i'd do rather than post here and wait for someone with the same device and A12 to come along and chance upon your post.........

it cannot hurt your device to try....
[Magisk] VR25:
Added to the todo list.
[Magisk] VR25:
Reset your config (acc -sr).

Check whether at least one charging switch works (acc -t) and report back after testing acc again for some time.

Keep in mind that a kernel update often breaks things. This has been happening quite frequently lately,.
[Magisk] VR25:
HAVE

Have you tried workarounds (e.g., using voltage/current control files as charging switches) as described in the readme?

Start by checking whether current/voltage limits are honored while charging wirelessly.
[Magisk] TioCareca:
Careful, this may cause your pmic to bug because some units of px3p have a faulty chip.

You can read about it in https://xdaforums.com/t/rom-official-arrowos-11-0-android-11-0-vayu-bhima.4267263/post-85119331
[Magisk] VR25:
Seems to be an issue with your device's shell program.

Do you face the same issue after running read v?
[Magisk] VR25:
This is documented under README > WARNINGS.

There are temporary solutions/workarounds.

GitHub - VR-25/acc: Advanced Charging Controller

Advanced Charging Controller. Contribute to VR-25/acc development by creating an account on GitHub.

github.com
[Magisk] VR25:
Unfortunately, Android is a mess when it comes to standards.

Only a handful of devices/kernels actually offer fairly well defined intefaces for those features.

Nonetheless, I'm exploring ways of abstracting as many control interfaces as possible.

Keep an eye on release changelogs.

Meanwhile, as workarounds, you can disable/enable charging on demand with acc -d and acc -e, respectivelly - and limit the max charging current to 500 mA.
[Magisk] VR25:
**v2021.10.30 (202110300)**

- Additional charging switches

- All control files (switches, current and voltage) are now contained in a single file (ctrl-files.sh) and it can be overridden by a plugin with the same name.

- Fixed issue #117 (@onokatio).

- General optimizations

- Shutdown warning notifications are less annoying (non-repetitive), but are still disabled by default. To enable, create the file `/data/adb/vr25/acc-data/warn`.

- Strip newlines from the output of acc -p.

- The logs tarball now also includes the outputs of `getprop` and `acc -p` (potential/new charging switches).

- Updated Documentation
[Magisk] AnonVendetta:
@VR25: I just rooted my Galaxy Tab S7+ and installed MatteCarra's ACCA app from the GitHub releases page. Magisk v23 is showing updates available for ACC and Daily Job Scheduler. But since ACCA uses its' own bundled releases of these, I'm wondering if it's safe to update (in other words, will the app have issues if I use something other than the bundled version)? I'm more comfortable with a GUI rather than CLI, so I went with the app instead.

Also, I have disabled fast charging in my stock firmware's settings. But ACCA says it is on. Should I just ignore this? Or is the app ignoring my settings and forcing it to be enabled? is there a terminal command I can run to definitively determine its' status? I really would prefer for it to be disabled.
[Magisk] VR25:
Upgrade. Those releases fix issues.

Whenever acc/djs releases are incompatible with acca, the changelogs mention that.

The status you see - Charging (Fast) - is provided by the kernel itself (usually through /sys/class/power_supply/battery/charge_type).

In my experience, it's meaningless.

Eventually, future AccA versions will no longer display that.
[Magisk] VR25:
By the way, one can run acc -b (or acc --rollback) to quickly revert to the pre-upgrade version and config.
[Magisk] wolfenstein3de:
Hello, does anybody have any idea how to set ACCA so it won't show charging icon, when connected&not charging? I would like to see to be able to check when the phone has stopped charging during the night, exactly.
[Magisk] VR25:
Run su -c acc -s cs=true on terminal.

cs is short for capaciy_sync (more details in the readme).
[Magisk] gorilla p:
After latest update, I now get

[/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/mmi_charging_enable 1 0] works

- battIdleMode=false

Will see how it works tonight
[Magisk] VR25:
That's one of the recently discovered charging switches.

There might be more, according to the output of acc -p.
[Magisk] wolfenstein3de:
$ su -c acc -s cs=true

/system/bin/sh: acc: inaccessible or not found

$
[Magisk] VR25:
v2021.11.3 (202111030)

- Fixed installation issues

- Improved support for the current Magisk canary.

- Shutdown warning notifications (mV) are now posted at shutdown_capacity + 100mV (formerly 200).

DJS has also been upgraded.
[Magisk] Ascii3:
I shall keep an occasional watch for the changes.

Thanks. Right now disabling and enabling online charging manually is what I oftentimes do.
[Magisk] Gibsonflyingv:
I'm curious if anyone has had success with this on the Pixel 6. I read this on the acc github but I'm not sure how to make use of that in the configuration (I'm a noob with this module/config app).

It mentions:

/sys/devices/platform/google,charger/charge_start_level:100
/sys/devices/platform/google,charger/charge_stop_level:0

I'm confused on how to create the commands to set this up. It's clearly a "acc -s" command, but where does the "charger/charge_start_level:100" go? I'm assuming "/sys/devices/platform/google" is the switch file?
[Magisk] zee3are0:
Same. I'm interested and want to learn how to setup ACC the best for my P6P...
[Magisk] VR25:
You ca

You can place those lines into a file (e.g., acc -p /sdcard/my-list.txt) and run acc -t /path/to/file to test all.

Perhaps you may want to filter the output a bit - i.e., remove lines that don't remotely resemble a charging switch.

Sometimes, certain lines may trigger a reboot. ACC remebers to skip those next time, so that one can continue testing by simply running the same command again until all lines get tested.
[Magisk] VR25:
zee3are0 et al.,​

I've been experimenting with botth.

So far, those control files seem to behave very inconsistently.

Perhaps Google released non-production quality software.

Have you tried the current/voltage approaches? (Readme > tips > idle mode and alternatives)

Anyway, here's how to test and and set those two switches:

1. /sys/devices/platform/google,charger/charge_stop_level and /sys/devices/platform/google,charger/charge_start_level

Test: acc -t /sys/devices/platform/google,charger/charge_stop_level 100 5 /sys/devices/platform/google,charger/charge_start_level 0 95

Set: acc -s s="/sys/devices/platform/google,charger/charge_stop_level 100 5 /sys/devices/platform/google,charger/charge_start_level 0 95"

2. Just /sys/devices/platform/google,charger/charge_stop_level

Test: acc -t /sys/devices/platform/google,charger/charge_stop_level 100 5

Set: acc -s s="/sys/devices/platform/google,charger/charge_stop_level 100 5"
[Magisk] Darth Bidder:
Should I update the Magisk module even though I'm using the AccA or should I only update the AccA through the apk?

Last update for AccA was from a few months ago while the Magisk module was just last updated back in the 1st week of November.
[Magisk] VR25:
The general rule of thumb is updating things only if you absolutelly need to.

Don't fix what's not broken.

That's not to discourage anyone.

Being a bit adventurous won't hurt.

I don't intruduce breakng changes without notice.

Besides, acc has a rollback feature - acc -b command reverts everthing (including the config) - no reboot required.
[Magisk] gorilla p:
After testing, I found the following 2 reporting "works" on my OP9.

sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/chg_enable 1 0

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0

For each, I entered acc -ss /path/to/switchabove.

Ill see of it works nay better.
[Magisk] VR25:
To set switches, run acc --set charging_switch="file on off file2 on off --"

As you can see, more than one switch can be set at once, but most of the time, one is enough. The trailing " --" ensures the switch is not unset if it fails (i.e., prevents falling back to "automatic")

acc --set charging_switch= can be shortened for faster typing: acc -s s=
[Magisk] gorilla p:
Ran again with a better usb charger and found another working switch. Applied first and third. Now Daemon is back to stopping while charging. Both with battery idle mode=true cause the daemon to stop almost immediately after starting charging.

I tried the one with battery idle mode=false and the profile didnt work. It didnt throtttle charging or enable cooldown and kept charging past the set threshold of 90%.

/sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/chg_enable 1 0

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/chg_enable 1 0 works

- battIdleMode=false

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0]

works

- battIdleMode=true