yashsingh1/xdaforums huggingface dataset:
[Magisk] Admiral2145:
Mine does... You have to set the correct battery profile and it'll hold.
[Magisk] hyp89:
Hello, i am using crdroid with my xiaomi mi 9 and wireless charging is overheating my phone. Is it posibile to limit wireless charging only (mah limit)? Which options do i have to set? Looks like the app have many many options :)

Thx for helping!
[Magisk] Johncaffee:
Correct battery profile ?

I think I have set all parameters correctly. I don't understand :(
[Magisk] zzenyoo:
Command line (connected to charger)

su

acc -t

This will test available battery switches and show wich one works (and have 'battery idle mode).

This is for my phone (X3 NFC).
[Magisk] Nik1979:
Hi, I have an LG G3 phone and ACC worked fine until few weeks ago.

When I try "acc -t", it says "won't work" for all methods.

I have now switched back to version 2021.12.20 and there "acc -t" says "works" for all 5 methods.

Something seems odd with the latest version.
[Magisk] rcbjr2:
I'm having the same problem. Charges to 100% every time. Did you figure out a fix for this? Thanks.
[Magisk] Johncaffee:
I don't find a solution. I have reinstalled the 2022.1.8 version.
[Magisk] david003:
Seems to be working ok, as far as I can tell, on a Xiaomi Note 10 pro running MIUI 13.0.4 (xiaomi.eu version). I'm using the AccA app, so the version of acc it installs is a little older.

I can see it stop charging when it hits 80%. The max temp is set to 40c with a 90 sec cool down, and I don't see it go over 40c when charging. Whereas before it would sometimes get to 42c or 43c (using the 33w fast charger). However, I haven't noticed any indication that it hits a 90 sec cool down cycle. It still shows as charging. Should there be an indication if charging is paused? Or is it normal not to see it?
[Magisk] JhinCuatro:
The module can help with preventing your battery from getting low (depth of discharge is the biggest factor in battery longevity; deeper discharges per session has bigger impact than less deep discharges (20% battery remaining is significantly healthier than 5% remaining). It also can prevent your phone from being topped at 100% for extended durations (keeping at 100% for several hours puts unnecessary strain on battery due to elevated voltage, but also passively drains battery faster. Battery at 90% or lower has significantly less passive energy drain.). Finally another feature is battery idle mode (can work on unsupported device with further steps, but your luck will vary from device to device), which is useful for using your device directly from a power supply without draining nor charging a battery (useful for resource intensive tasks, like gaming).
[Magisk] JhinCuatro:
Is this normal behavior for pseudo battery idle mode? My oneplus 9 pro stock kernel isn't supported for battery idle mode in the acca app settings, but I've been able to enter some state of battery idle mode whenever I "No limits charge to %value" and reach the target value, which no longer charges/discharges, so long as my charger isn't plugged in and out again. The "current" seems to constantly fluctuate from 10ma to 0 repeatedly (while maintaining same voltage).
[Magisk] Ryakna:
I have a weird problem.

I installed ACC on a new phone (Poco F3 with Lineage 18.1) and defined voltage and current limits with set --voltage and --set --current. Not using charging switch or capacity limits.

Everything seemed to be working well, the phone was charging within the current limit and up to the voltage limit. However, when I disconnect the phone, IF I disconnect it near the voltage limit, it remains in charging status (both acc -i and lock screen info) until I reboot it. Even connecting and disconnecting the phone repeatedly doesn't solve it, only rebooting does.

How do I solve this?

Even if I can't solve it, is this in any way harmful, to constantly have the charging info while discharging?
[Magisk] tomiasx22:
Hello,

I have Samsung Galaxy S10 (EU version) so with Exynos...

Is it possible to configure module (i.e. in AccA app) so that it really charges in "fast mode"?

I see that 15W (in fact 12-14W) is achievable only with original Samsung charger.

While using any other charger I mean 20W to 35W - max charging current is not more than 1,3 - 1,4A...

As far as I know there are Magisk modules that work, but with Qualcomm processor...

Is it possible to configure module so that on Exynos fast charging was really working?

In the picture there is configuration I made in the app but with no effect...

I configured using tips from ACC help.

Another question is Wireless charging. When I use 15W charger (I know real efficiency is 60-70%) but on average it charges 5-6W, whereas on the screen it shows "fast wireless charging" - is there another separate configuration of ACC for wireless mode?

Please advise, thanks!
[Magisk] DinethIrusha:
Ok, It works!

I set the the charge limit to 95% and it stops at 95% and shows 100% on the Android Battery Info,

I guess charge mask makes the device think device is 100% but battery charge is at 95% on Acc Settings.

Kudos to the developer.
[Magisk] Axospirit:
Hi, i have the same issue only on Wireless charging on Mi). Have you fixed in the end?
[Magisk] VanGray:
For you lazy man/woman like me, you can execute idle mode just on pressing a tile in the Quick Setting Tiles

You need Xposed Edge Pro to do this (obviously xposed/lsposed)

I'm using Lsposed

Here's the steps:

Open Xposed Edge Pro

Tap Quick Settings tiles > add tiles and create one tiles + check the box

In Action, select Shell > put command:

su

acc -d

Check the root box

Allow xposed edge to have root access

Put a label and an icon, then save

You can add this tile to your quick setting tiles so each time you click on it, your phone will go to idle mode without typing command on a terminal
[Magisk] xumixu:
Are there any kernels that allow battery idle mode on xioami phones?
[Magisk] VanGray:
It depends on your phone,

The one I've used:

Redmi note 8: Sixteen kernel, SilonT, Quicksilver,SurgeX, almost all Redmi note 8 Kernel

Redmi 7: SilonT (I was on A10 derpfest)

Redmi note 7: can't find one
[Magisk] tomiasx22:
OK, but what about Samsung Galaxy S10 with exynos, could anyone help...?
[Magisk] VanGray:
I don't use Samsung but you can try acc - t to find charging switch that support idle mode

I've installed it for a friend on old Samsung S6 A10 in LOS and the idle mode is supported
[Magisk] xumixu:
Thanks a lot, that gave me hope. I'll try to find one for my mix 3. Its battery really suffers and it would help a lot to slow its degradation.
[Magisk] midozalouk:
I have a future request

Something like smart charging from the 1+ it's for the overnight charging

The users enters the time when he awakes

And the app calculate the required charging current based on how many hours to wake up and the current percentage of the battery

Is this applicable?
[Magisk] Vanta-Chan:
Hi, I have an issue with AccA, I'm using a Poco F1 on LineageOS 19 and my current setting is this:

(Sorry if it's not 1:1 translated to english, I'm assuming the words)

Capacity control:

Shutdown at 1%, Start Charging at 75%, Stop Charging at 95%.

Charge switch: Automatic

Any other charge control is disabled.

Now if I charge my device to 95%, the charging stops, but around 15 seconds it begins to charge itself again until it stops and this is looping.

The status switches between "Discharging (N/A)" and "Charging (Taper)". Is there a solution to prevent this charging loop?
[Magisk] Zaxx32:
Is idle mode available for you?
[Magisk] Vanta-Chan:
Nope, my stock/LineageOS kernel doesn't support it.
[Magisk] pepeq:
for Poco X3 NFC (surya) I use this kernel with crdroid v8. 5:

https://xdaforums.com/t/kernel-surya-optimus-drunk-kernel-v12-5-13-05.4198627/page-15

It supports idle mode.
[Magisk] trevtdogg:
i've noticed something even though the charging stops correctly.

after the charging stops, but while it's still plugged in with the screen off - the battery drains faster than it usually would when it's unplugged from power with the screen off.

is this just a rookie mistake on my part i assume? a setting or two i need to adjust?
[Magisk] :
This happens because the phone won't enter deep sleep while charging.

AFAIK there is no way to fix that.
[Magisk] LG Studiotan:
Get rid of AccA, its boring!

LineageOS 19.1 / Poco F1 works perfectly with this config.txt:

configVerCode=202111030

capacity=(20 99 70 88 false false)

temperature=(28 36 300 55)

cooldownRatio=()

cooldownCurrent=

cooldownCustom=()

resetBattStats=(false true)

chargingSwitch=(battery/input_suspend 0 1)

applyOnBoot=()

applyOnPlug=(battery/constant_charge_current_max::600000::1800000)

maxChargingCurrent=()

maxChargingVoltage=(battery/voltage_max::4200000::4400000)

language=en

runCmdOnPause=()

ampFactor=

voltFactor=

loopCmd=()

prioritizeBattIdleMode=false

currentWorkaround=false

Charge current (600mA / real 450 mA) trickling down when maxChargingVoltage (4200mV) is reached and stops unfailing at 88% capacity. Doesn't charge above 36°C, cools down for 5 Min. then retries again.

Change values at will. Check performance with app: " 3C Battery Monitor" or similar.

have fun!
[Magisk] Vanta-Chan:
Yeah you said that but where would you put your config.txt?!

By the way, 3C Battery Manager looks like it got stuck in 2010.
[Magisk] LG Studiotan:
RTFM! :)

Located at /data/adb/vr25/acc-data (README.md). Change your config.txt also there, reboot not really necessary but i would recommend to do so.

3C Battery Manager still get updates every second week or so.
[Magisk] saoudien07:
So is this the correct way this module is supposed to work??

For me, it stop as setted at 85%.

About Android system and info, it says "85% and charging done in 27min", and in InfoBar also.

So I let it for 10 min, and when I see it is never gona reach 100%, I removed.

Thx for additional informations.
[Magisk] natewu:
Hi I tried to update acc now and then acca stops working(Freezes when trying to modify settings). Then I reinstalled previous version and it still doesn't work. Uninstalled everything and reinstall nothing works. Then I try to test on the terminal(termux) and it says acc is not a command...

What can I do to fix this?
[Magisk] whiterabbit62:
what shoul i type in the apply on boot section in ACCA magisk GUI app ?

Sometimes it will not work and let the battery charge with full amps which i do not want it to do.
[Magisk] VR25:
**v2022.6.4 (202206040)**

- -n|--notif [[string] [user]]: post Android notification; may not work on all systems;

- -t|--test [p|parse]: parse potential charging switches from power supply log (as acc -p), test them all, and add the working ones to the list of known switches; implies -x;

- acc -p: exclude all known switches and additional troublesome ctrl files;

- acc -s: Enforce valid pause_capacity and resume_capacity difference;

- acc -t: show more useful information; source read-ch-curr-ctrl-files-p2.sh;

- accd: if possible, avoid idle mode when capacity > pause_capacity;

- Additional charging switches;

- Blacklisted usb/vbus_disable;

- Fixed accd /path/to/config --init;

- Fixed runCmdOnPause and loopCmd parsing issues;

- Fixed: "after a reboot, accd doesn't control charging, until the keyguard is unlocked";

- General refactor;

- Hard reset wipes config and control file blacklists (acc -sr a or acc --set --reset a);

- Improved advanced battery status detection;

- Misc fixes & optimizations;

- New config variables: batt_status_override=Idle|Discharging|'custom', batt_status_workaround=true, reboot_resume=false, reset_batt_stats_on_plug=false, schedule='HHMM command...' (refer to the config or readme files for details);

- One-line scripts;

- Parse config ampFactor from batt-interface.sh as well;

- Post exit code notification if accd stops due to an error;

- Removed obsolete source code files;

- Run dexopt-job only once per boot session (if battery is charging, and system has been up for at least 15 minutes);

- Save acc -t output to /sdcard/Download/acc-t_output.txt;

- Tuning variables for not_charging() timeout (seqCount) and voltage-based idle mode (voltOff);

- Updated documentation;

- Updates can be downloaded with busybox's wget as well (may not work on all systems). Try upgrading with acc -u.
[Magisk] Camerado:
configVerCode=202206010

capacity=(5 60 75 80 false false)

temperature=(40 50 90 55)

cooldownRatio=()

cooldownCurrent=1000

cooldownCustom=()

resetBattStats=(true false false)

chargingSwitch=(battery/input_suspend 0 1)

My config, all other is default. But after reaching 60% cooldownCurrent setting not working, fast charging continues.
[Magisk] Uluru25:
"CooldownRatio" is missing e. g. (1 600) so that 10 mins charging with reduced current, then 1 sec with default (max. ) current, then again 10 min with reduced current...
[Magisk] Spaceoid:
No idea what exactly changed, but with the new ACC build now my cooldown charging cycle works completely as expected. Thank you!
[Magisk] Camerado:
In description:

# cooldown_current (cdc) #

# Instead of pausing charging periodically during the cooldown phase, limit the max charging current (e.g., to 500 mA)

Keyword "Instead", so cooldownRatio not needed, i think 🤔
[Magisk] Uluru25:
Just try it. I use Acc with the GUI from here https://github.com/CrazyBoyFeng/AccSettings and do need both: entering a cool down current AND the time ratio. If you don't need it be happy...
[Magisk] Uluru25:
in my case my terminal app needed root and the command "acc" needed that I switch to superuser. Thus, enter in the terminal "su", press the enter button, and retype "acc" (all without the quotation marks ""). Good luck.
[Magisk] Camerado:
Installed the app and saw, thanx. Waiting for updated apk release )
[Magisk] Flippy6:
Hey, i 'accidently' killed the temperature sensor of my galaxy s9 while changing the battery.

The transplantation was succesful but i'm not able to charge the phone anymore at all since it's acting as the temperature is too low/high/whatever.

I was hoping that your module could help me by spoofing the temperature of the phone, do you think that this is possible?
[Magisk] Uluru25:
I don't think so. And if this would be possible it could be VERY harmful and dangerous since all Li-batteries need a protection so that they do not incinerate etc. Spoofing the reak temperature of the battery could leed to dangerous situations. But this is my personal and non-scientific pov.
[Magisk] VR25:
v2022.6.4 strange behaviour · Issue #153 · VR-25/acc

Update: see comment below #153 (comment) v2022.6.4 doesn't work. AccA is not responding. accd. command doesn't work. Trying to revert to previous version but unable install (installation process is...

github.com
[Magisk] VR25:
Some kernels have interfaces such as, temp_warm and temp_cold. If yours has those as well, it may be possible to adjust the values to make the battery charge again. However, as Uluru25 suggested, by doing so, temperature control will be on you. You'll be fine, as long as the charging current is optimal (the device does not get significantly warm while charging). Run acc --log --export, and share the generated log archive.
[Magisk] Flippy6:
It's alright, i'm not using any cpu heavy applications, i'm not gaming or watching HD stuff/netflix on it.

I'm a true newbie regarding rooted phones though.

Do i have to type "acc --log --export" in termux?
[Magisk] VR25:
su -c acc --log --export # or su -c acc -le, for short.

Termux, any other terminal or adb shell, as root.

You can actually do anything on it, as long as the device does not turn into a stove. Lowering the max charging current (e.g., to 1000 mA) is one way of preventing overheating.
[Magisk] Flippy6:
Okay, where do i find the file now?

Termux says /data/adb/vr25/acc-data/logs/acc-logs-starlte.tgz

I also installed a GUI, and it says -20°c temperature, lol, need to push that up.
[Magisk] Zaxx32:
1A?? Hell, where's the fun in that? 🧐

...heh, says the guy who never leaves AccA. Speaking of...is there any chance you'll tinker/tweak AccA too? ...for us casual users ofc. can't find many Pixel 4a folks to copy cat. 🤔 ...js
[Magisk] VR25:
The file is literaly that shown on terminal (the .tgz archive). You can copy it to your Download folder by pasting and running the following on terminal:

cp /data/adb/vr25/acc-data/logs/acc-logs-starlte.tgz /sdcard/Download/ (the next release will do this automatically)

-20C definitely won't let your battery charge.
[Magisk] VR25:
1A is just a good starting point. One can go higher, while paying attention to the temperature.

I'm not the developer of AccA. What I can do is add an acc setting to easily override temperature thresholds.
[Magisk] Flippy6:
Hmm, it keeps telling me that it has no permissions to copy it.

I gave it permissions to access the storage though
[Magisk] Zaxx32:
ooops...my bad. :rolleyes:

I'm already triggering a cooldown cycle @45C. Haven't strayed far from factory settings. Bumped max current from 3A to 3200mA and max voltage to 4100mV. It'd help if I knew the max safe temp.
[Magisk] jakito:
Hi, I have a question about idle mode. Supposedly, my kernel supports it and acc reports it as working. My question comes after reading this in the FAQ:

My phone when reaches this idle state stays locked on:

Is this healthy/safe?

The phone never gets over 35°. I like to let the phone charge over night at 1A and when it's done, it just stays there at 80% on idle mode.

Just making sure I'm not stressing the battery without a reason.

Thanks!
[Magisk] Uluru25:
Thanks that you will do this stress test for all of us! Please let us know how long your battery has survived this torture (3.2 Amps). I guess most ACCA users use ACCA to reduce (!) the charging current in order to extend battery life time. But for sure it's solely up to you to do whatever you want...
[Magisk] jacko9000:
Hi,

I've been using acc since v2021.8.31 on a Xiaomi Poco X3 Pro running Android 11.

From what I can remember, the only setting I ever changed was to charge between 70% and 75%. All of the Magisk module upgrades since that 2021.8.31 version have worked fine, but with this most recent one, v2022.6.4, it doesn't stop charging at 75% anymore, but instead goes all the way up to 100%. So, I've went back down to v2022.2.22.1 and it's working fine again.

Is there some setting I need to change to get v2022.6.4 to work? Or is there a log I can check somewhere? I can use either acc in the terminal or the AccA front-end.

Any help or advice would be much appreciated.

Thanks for your help.

Best regards,

Jacko
[Magisk] duttyend:
This behavior happened to me on 2 different devices running latest LineageOS (Poco F1 and Poco F3), I solved it by disabling the module in Magisk, restarting and enabling it again.

Otherwise, you could try the reset command in terminal (acc -sr).
[Magisk] jacko9000:
Thanks for the reply.

I re-installed ACC v2022.6.4, but this time I did not install the AccA front-end.

And now ACC seems to be working.

AccA was useful, though, for setting the charging range and viewing things at a glance, so I have installed a different front-end, ACC Settings, which has been updated for ACC v2022.6.4.

I hadn't tried the acc reset command in the terminal, but I will keep that in mind for future reference.

Thanks for your help.

Best regards,

Jacko
[Magisk] jakito:
I have the last version and my phone always stops charging at 71%. I have the same config I had on the previous version:

I'm using the OP7 Pro OxygenOS 11.0.7 and the kirisuma kernel.

Can someone help?

Thanks!
[Magisk] VR25:
Try the latest snapshot.

acc_v2022.6.10-dev_202206100_1431.zip

- 06fff97 Add Turkish tranlations (Türkçe (tr)) by github.com/cutiness

- e429770 Enhance current unit and polarity detection

- ddc8c50 Accelerate accd stop

- 8df12eb Export log archive to /sdcard/Download/

- 9c4cce3 Include acc-t_output-${device}.log in log archive

- 1579304 Save acc -t output to /sdcard/Download/acc-t_output-${device}.log

- a0846f9 Blacklist /sys/class/qcom-battery/vbus_disable 0 1

- 12ceb6a --parse: exclude all known switches

- fc1e98b Fix typo

Alternate way of upgrading to this from the latest stable: acc -u -f dev
[Magisk] VR25:
max safe temp depends on the battery tech

the general recommendation is to avoid 40+ degrees C.
[Magisk] VR25:
that's fine, as long as you don't let it plugged for extended periods of time (e.g., a whole day)
[Magisk] VR25:
try the latest snapshot
[Magisk] jakito:
Is battery idle mode safer or as safe as the other switches that simply disable charging?
[Magisk] VR25:
try the latest snapshot

if the issue persists, as soon as charging stops at 71%, run acc --log --export, and share the generated log archive
[Magisk] jacko9000:
Well, now I'm back to the previous problem of it always charging to 100%. And now downgrading doesn't work either.

I think I read somewhere that you said you had testers. In the case of the Poco X3 Pro? I think I also read somewhere that you said you can't test every device. I get that. But I can't be a tester. If I could be, then I would. But I can't.

Best of luck with your project.

Best regards,

Jacko
[Magisk] VR25:
acc_v2022.6.12-dev_202206120_1403.zip

- (wip) Always check real batt status before comparing current

- 1076997 Fix "charging keeps stopping at min < capacity < max"
[Magisk] Spaceoid:
I know the message I quote here is a good step from the past, but it was the only post I found mentioning that problem.

I am using a OnePlus 6 with latest OOS and LOS 19. If I use the "charge once to 100%" feature, it will result in the phone charging to 100% multiple times even after the first time.

Easy workaround is to restart daemon, so no big deal, but I thought it might be worth mentioning here.

Edit: Did not test the version mentioned above yet, so this statement might only hold true for the version before.
[Magisk] VR25:
**v2022.6.12-dev (202206120)** (https://github.com/VR-25/acc/releases/tag/v2022.6.12-dev) (PRE-RELEASE)

- 9110ed8 Always check uevent batt status before comparing current

- 5746f7e Fix acc -f

- 1076997 Fix "charging keeps stopping at min < capacity < max"

- 06fff97 Add Turkish tranlations (Türkçe (tr)) by github.com/cutiness

- e429770 Enhance current unit and polarity detection

- ddc8c50 Accelerate accd stop

- 8df12eb Export log archive to /sdcard/Download/

- 9c4cce3 Include acc-t_output-${device}.log in log archive

- 1579304 Save acc -t output to /sdcard/Download/acc-t_output-${device}.log

- a0846f9 Blacklist /sys/class/qcom-battery/vbus_disable 0 1

- 12ceb6a --parse: exclude all known switches

- fc1e98b Fix typo
[Magisk] downhere:
"Daemon stopped with exit code 7!"

What does it mean?

Build: v2022.6.4

Occurred during wireless charging at about 71% charging level.

Used default settings except max. capacity = 85%.
[Magisk] VR25:
It means all charging switches failed.

Wireless charging can't be paused on your system, with that version of acc.

Try the latest build.
[Magisk] VR25:
v2022.6.19-dev​

b1b02c3 Battery status workaround enhancements

3c988ff Lower ctrl file write frequency and time

fcc0e1e Update README & translations

07b620b Add offMid toggle

# discharge_polarity (dp) # (not new, just improved)

# This overrides the automatic current polarity (+|-) detection.

# off_mid (om) #

# Whether to turn off charging after rebooting or restarting accd, if capacity is within resume_capacity and pause_capacity (default: true).

acc -t now shows a switch count (current/total), and AccA should recognize idle mode support again.
[Magisk] KemikalElite:
I'm trying to get this working on a 2015 Amazon Fire 7 running LineageOS 14 Android 7.1.2.

I'm using ACC Settings frontend and the battery will not discharge lower than 99% even with the default config.

The app shows cmd discharging and 0.00A current and android battery status shows "unknown" in about tablet.

Charging indicator is visible in the status bar and my USB meter shows the battery is consuming 0.3A with the screen on.

I've attached the diagnostic info.

I've also tried this on a Nexus 5 and 5X in the past with similar results. Is ACC just not compatible with older devices?

Also has the Pixel 3a been tested to work with ACC?