yashsingh1/xdaforums huggingface dataset:
[Magisk] VR25:
**v2020.4.10-beta (202004100)**

- acc -C: watch `charge_counter` and `charge_full` only; provide calibration instructions for devices that lack these files

- General fixes and optimizations

- Renamed cooldown(_c|C)urrent/cooldown(_c|C)ustom

- Native support for MediaTek mt6795 devices, e.g., Redmi Note 2 (hermes)

- Updated build script and documentation

Flashable zip: https://github.com/VR-25/acc/releases/download/v2020.4.10-beta/acc_v2020.4.10-beta_.202004100.zip

I suggest you set the cutoff level to 75%.

It may not seem like a huge change, but it does makes a huge difference in battery longevity.

The corresponding voltage limit is the value you see (acc -i voltage_now) as soon as the cutoff level is reached and charging, stopped.

Current (mA) is a different story. The higher it is, the faster voltage peaks.

In other words, increasing the current accelerates the constant current (CC) charging phase.

As a side effect, the battery gets warmer.

The voltage of a warm battery peaks even faster.

Heat is one of li-ion batteries' greatest enemies.

What the current limit should be depends on you.

I shoot for 1000 milliamps.

With acc's cooldown cycle feature, you can use fast charging, while keeping the battery cool.

Lastly, nowadays, battery calibration is generally unnecessary.

Modern battery management systems are advanced enough to track battery state with great accuracy.

However, manufacturers still opt for low-end charging circuitry sometimes - to cut costs.

If your battery is not performing as well as it normally would, perhaps its a good idea to calibrate its manager.

ACC has a calibration helper (acc -C).

Recommended reading: https://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[Magisk] DJsushi123:
Oh, I see. I mean, blocking it in Franco Kernel Manager really did kinda solve the issue. The wakelock was no longer there and my device wasn't constantly awake while the charger was plugged and device not charging. But I didn't think of the fact that the wakelock exists there for a reason. But how do other devices then monitor the battery without keeping the device constantly awake?

Also, I've tested out all the charging switches available. The first one is "battery/input_suspend 0 1" which is the default one and it works but creates this wakelock. The second one is battery/charging_enabled 1 0" which also works, but only partially. When this charging switch stops the charging, as soon as the battery drops by 1%, the device starts charging again even if I'm on the "7080" mode for example. So my battery always stays between 79% and 80% because of it.

There's also a third switch, "dc/input_suspend 0 1" but that one doesn't work.
[Magisk] VR25:
Why your system has that wakelock and others don't - I can only think: bad design.

If blocking it hasn't brought you any sort of nasty side effects, you don't have to worry about keeping it blocked.

Btw, are you using a custom kernel that supports wakelock blocking? On my system, Franco Kernel Manager can't block wakelocks.
[Magisk] DJsushi123:
Oh. That 'bad design' part kinda hurt, because it's a OnePlus and I wouldn't expect such a problem on that phone. But nevermind, at least it's solved now.

I haven't observed any side effects yet, but I blocked the wakelock just a few days back. But I also didn't charge my phone to any percentage higher than 75%, so idk. If the wakelock is responsible for cutting the charging at 100%, maybe it is kinda necessary. I don't really know.

And yes, I am using the Radioactive Kernel by acuicultor. Here's the link: CLICK ME

---------- Post added at 06:24 PM ---------- Previous post was at 05:58 PM ----------

I wouldn't advise you to do that. The PowerManagerService.Wakelock is a placeholder wakelock for all the partial wakelocks. The reason why this probably didn't stop your apps from working while the screen is off, is the fact, that ACC probably doesn't support wakelock blocking on the OP6. I tried blocking the same wakelocks using ACC with no success. Instead, try to download a custom kernel that supports wakelock blocking and block them in the kernel manager (at least I did that to fix my idle battery drain). You can read more here on "Step 7": https://xdaforums.com/oneplus-6/how-to/guide-ultimate-guide-installing-custom-t4079937
[Magisk] davidzam:
Acc not estarting uso the app

I the following error

/system/bin/sh: <stdin>[277]: acc: can't execute: Permission denied

Using magisk 20.4 Android 6.0.1 Samsung on5. Thank you
[Magisk] Vantskruv:
Anyone got charge current limit to work? Specifically for the Google Pixel 4XL? I read that many kernel:s do not support this, which kernel supports this? Currently I failed to make it work, so I guess either my kernel does not support this, or I am doing something wrong.

Also a question, if charge current limit had worked for me, where do I set the limit in config.txt? Hence, I noticed that there is a line called maxChargingCurrent (if I remember it correctly), but the charge current limit can also be set in applyOnPlug field. Which one is correct?

Also, I am little unsure of the formats of fields in config.txt. Any good config.txt examples out there, which shows every possible option?
[Magisk] gonzo1963:
Good afternoon,

I want to start using this module to protect the battery in my new Motorola One Vision, but my knowledge is very basic.

Is there a graphical interface that works well for the settings of this module?

I have read that there is one, AccA, which is valid, but I see that it has not been updated since October 22, 1919.

Is it still operational?

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] Alpetrus:
Yes, of course. I use it without any problems on Android 9 (Moto G6 Plus).
[Magisk] gonzo1963:
Good again,

The last offtopic, sorry.

Is it necessary to install the Magisk acc module and the AccA app?

Or is it only valid with AccA?.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] Alpetrus:
The Magisk module is core, ACCA app is frontend (GUI for ACC) if you don't want or don't like command line.
[Magisk] CheepPlüm:
The ACCA app (1.0.23) installs automaticly the magisk module at the start....so no need to install manualy it...
[Magisk] gonzo1963:
Good again,

I have some more AccA questions and in this forum I have not found a specific thread.

Can I use this thread to ask them?.

If not, is there any other channel where I can answer my questions?.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] paolocorpo:
Dear

Here is the Telegram chat where many users are discussing and supporting

https://t.me/acc_group

Inviato dal mio iPhone utilizzando Tapatalk
[Magisk] VR25:
Which acc version is that?

Are you running as root?

It should work if you're on the latest version.

https://GitHub.com/VR-25/ACC/releases/

The new config file has instructions and examples.

You're not supposed to edit maxChargingCurrent. That field is filled by the command acc --set --current milliamps.

You don't have to possess extensive knowledge to get this thing up and running.

Default settings are a nice fit for everyone who's getting started. This means you don't have ro configure anything if you don't need to.

I recommend installing the latest version from the releases link above. You may want to read the documentation first.

The latest AccA can be downloaded from https://xdaforums.com/showpost.php?p=81982171&postcount=3379 .

If you're going the GUI way, remember to keep ACC up-to-date. The app comes with a relatively old ACC version - which has some issues.

ACC can be flashed from Magisk Manager, even if you're using AccA. Alternatively, there's the acc --flash command.

P.S., this thread is dedicated to AccA as well.
[Magisk] gonzo1963:
Good morning,

Thank you very much for your responses.

I have some doubts about AccA:

1.- Can the language be adjusted to Spanish from Spain?

2.- Is there any manual or basic guide to use AccA?

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
v2020.4.17-beta (202004170)

- acc -C: replace misleading 100% with 99%

- acc -s: restoring individual defaults is as simple as running acc -s var1= var2= ...

- Auto-shutdown: run /system/bin/reboot -p as fallback

- autoShutdownAlertCmd, calibrationAlertCmd, chargDisabledNotifCmd, chargEnabledNotifCmd, errorAlertCmd - Termux APIs can be used for notifications, TTS, toasts and more; for details, refer to https://wiki.termux.com/wiki/Termux:API

- Enhanced config auto-backup

- Fixed stable-beta config migration error

- General fixes and optimizations

- Updated documentation

Flashable zip: https://github.com/VR-25/acc/releases/download/v2020.4.17-beta/acc_v2020.4.17-beta_.202004170.zip

AccA 1.0.23 (27): https://xdaforums.com/showpost.php?p=81982171&postcount=3379

Note: If you want to use ACC App (AccA) install and launch it before flashing ACC.

Known Issue

This update makes AccA report absurd charging current and voltage values.

Quick fix - paste and run (as root): (cd /data/adb/acc/; sed -i '/batt_info/s/b/verbose=false; b/' acca.sh; chmod 0777 acca.sh)

1) The app sets its language according to your system's locale.

Currently, there's no option to override that.

If the language you want is unavailable, wait for the next release.

You can also help with tranlations at https://crowdin.com/project/advanced-charging-controller .

2) There are in-app help/hints and the acc documentation (acc --readme).

AccA's own readme needs an update.
[Magisk] heithered:
Just flashed last beta on my Moto Z/Lineage 17.1 and there are no charging switches, acc -t returns /sbin/.acc/charging-switches no such file or directory. Unsupported device. Attached log.
[Magisk] the_poseidon:
Thanks for your effort n new release

For the issue on AccA, shall we use terminal for fixing ( same as below?)

cd /data/adb/acc/; sed -i '/batt_info/s/b/verbose=false; b/' acca.sh; chmod 0777 acca.sh
[Magisk] dragsterman:
[MENTION=5228676]VR25[/MENTION]

Hi,

I have a S20 Ultra and use the latest Magisk modul and the ACCA app with the default settings only the charge switch changed to slate or store modes. My problem is that neither of these modes provides power to the phone directly from the charger adapter. So when my phone reaches 80% the state of charge start dropping quite fast about 1% every 5 minutes while using DeX mode.

Why this could happen?
[Magisk] VR25:
According to the logs, that's NOT the latest version.

It's v2020.3.1-r3-dev (202003013) that ships with AccA v1.0.23 (27).

You missed the note on installing AccA. Refer to my previous post.

Yes, paste and run that - as root - on terminal.

You've got some reading to do: https://github.com/VR-25/acc/blob/dev/README.md#charging-switch .
[Magisk] dragsterman:
I tested my S20 Ultra idle mode with ACCA and it said that my kernel doesnt support battery idle mode but I saw in your older post that Samsung devices support this mode with the slate mode. I am a little confused.

What can I do if my kernel doesnt support idle mode indeed, to be able to draw prower from the charger while charging is paused?

Lastly if it is imposible to be in battery idle mode, then what is better for the health of my battery? I use DeX mode many hours a day so to disable ACC and with stock default charging charge my device to 100% while using DeX and be fully charged for many hours OR charge to 90% and let it dran to 60-50 % while using DeX with battery power?
[Magisk] VR25:
That's a quite old post.

There's an up-to-date and growing list of devices that support battery idle mode and/or custom max charging voltage limit at https://t.me/acc_group/8698 .

It turns out many devices behave differently, even though these are from the same manufacturer - and have the exact same charging switches.

You my want to try acc --test (latest beta) and compare its results to the app's.

Refer to https://github.com/VR-25/acc/blob/dev/README.md/#tips .

If that doesn't work either, install the latest beta and share /sbin/.acc/acc-power_supply-*.log.

I STRONGLY recommend reading more about what causes lithium ion batteries to age prematurely: https://batteryuniversity.com/index.php/learn/article/how_to_prolong_lithium_based_batteries .

In a nutshell, to achieve the greatest longevity, while keeping the device plugged in for extended periods of time, you can...

1) Limit the max charging voltage to 3920 millivolts: acc --set --voltage 3920 (requires a capable kernel).

2) Limit the max charge capacity to 40-60% and let charging resume at pause_capacity - 2 (e.g., I use acc 45 43).

#1 is the absolute best method. If you find a phone/kernel which supports that, kiss it!

#2 can be combined with a custom max charging current limit for best results. Shoot for 500-750 milliamps. This requires the latest ACC version (beta).

Most kernels support custom max charging current limits, at least partially. That means, some values (especially nonstandard ones) - e.g., 750 mA - are ignored. 500 mA - the standard USB current - is almost 100% guaranteed to work.

acc --set --current 500

Notes

- For safety, ACC will refuse to set a voltage limit outside the 3700-4200 millivolts range.

- The same doesn't apply to current. It's not required. The battery management system will simply ignore any value outside its safe range. Go ahead and set a limit of 9999 milliamps. I'll be watching my mailbox for a piece of your fried phone.
[Magisk] dragsterman:
Thank your very much for the detailed explanation. I will try these soon.
[Magisk] Zaxx32:
Pretty basic questions....just wanna be sure...

If I understand correctly, 2019.10.13-r2-dev (201910132), is the 'latest stable rls.

I prefer to charge to 90%...not the 'standard' 80%. Therefore could someone link me to the correct APK for this version and my current setup shown in my sig below. Also, does it support playing a custom notification sound, that I can set, for when it hits 90% and stops charging? Tia...
[Magisk] VR25:
ACC v2020.4.20-beta (202004200)

- Blacklisted troublesome Pixel [1-3]* charging switches

- Fixed absurd charging current and voltage reports (AccA)

- Fixed upgrade and downgrade issues (AccA)

- Include AccA logcat in log archive

- Optimized installers

- prioritizeBattIdleMode=true by default

- Removed acc --calibrate, in favor of universal and comprehensive calibration instructions (README > FAQ)

- Under the hood enhancements

- Updated documentation

- Workaround for encryption preventing AccA from initializing ACC

Flashable zip: https://github.com/VR-25/acc/releases/download/v2020.4.20-beta/acc_v2020.4.20-beta_.202004200.zip

AccA 1.0.23 (27): https://xdaforums.com/sho...postcount=3379

Note: If you want to use ACC App (AccA) install and launch it before flashing ACC.

The latest AccA stable from https://GitHub.com/MatteCarra/AccA/releases/ ships with ACC 2019.10.13-r2-dev (201910132).

However, I strongly recommend installing the versions I just published here.

The latest beta version can play a custom notification sound, but the setup is not simple (yet).

You have to do some reading

Refer to https://github.com/VR-25/acc/blob/dev/Termux:API.md and https://github.com/vr-25/acc#default-configuration .
[Magisk] the_poseidon:
Thanks for your new update

I tried to flash it on Magisk as always but its staying as installig... Waiting waiting but nothing happens... also I tried 3/4 times

Any suggestion?

EDIT : Succeed on installimg after restart, solved.
[Magisk] dragsterman:
[MENTION=5228676]VR25[/MENTION]

I have tried the method in the tips section of the readme about idle mode, so reseted everything and entered these three commands: acc -s r; acc 101 -1; acc -s v 3920.

After this the phone charged to 66% but it started to discharge while using DeX mode and it seemed that the phone uses battery power. It dropped quite fast, then I started to write this post and it started to charge again to 70%. Then as I write this, it is discharging again now at 69%. What is happening exactly, because its not idle mode for sure?
[Magisk] VR25:
Definitely there's something off.

Is the behavior entirely different when not using DeX?

Try also "acc --set --current 0" (or "acc -s c 0").

Restore defaults with "acc -s c -".
[Magisk] gonzo1963:
Good afternoon,

I do not know if it works correctly on my Moto One Vision with Android 10.

Since every time I enter the AccA app, I find that ACC is stopped, after a few seconds it starts.

I have also observed once that I have charged the smartphone and it has been charged up to 100% despite having the "Default" profile active.

I have tried to clear cache and data to see if this behavior changes.

I have installed: ACC 202003013 and AccA 1.0.23 (27).

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
That ACC version is also beta.

Flash the latest zip and see if it helps.
[Magisk] dragsterman:
Yes there is something off for sure.

Today it charged to 100% with the same setting. (Stock settings only the 3920 mV voltage modification).

I tried the "acc -s c 0" and the "acc -s c 500" commands and it wrote something like device not supported.

Nowdays I am at home so its mostly plugged in and DeX is running I have not tried what is the behavior when not using DeX.

I will play with these settings more but what voltage should I set If I want to charge to 80% instead of the 3920mV?

Also If only just the pause at capacity works in the end, I think I its way more good for the battery to charge to lets say 90% and let it drop to like 80% runinng DeX on battery power (if I want 80% to be available for the rest of the day when unplugged) THAN compared to the stock factory settings (charge to 100% and be there while plugged in). Am I right in this, what do you think?
[Magisk] the_poseidon:
[MENTION=5228676]VR25[/MENTION]

On previous versions of Acc, i was able to edit max voltage on ACCA but on this version i try to edit : after i saved, it turns back to nothing / as blank

I tried also on command section via terminal, didnt work

Any suggesiton?

My device is xiaomi with stock kernel on custom mi room
[Magisk] jal3223:
So I fired up fired up my Razer Phone 2 and it seems that none of the switches work with it. Has anyone gotten it to work? Should I grab some logs?
[Magisk] VR25:
ACC v2020.4.22-beta (202004220)

- Ability to override automatic current and voltage units detection - amp_factor (af) and volt_factor (vf)

- acc --info: print the output of dumpsys battery as well

- acc --set --voltage: fixed "settings not written to config"

- accd: fixed autoShutdownAlertCmd

- Misc fixes & optimizations

- Suppress unnecessary vibration feedback

- Updated documentation

https://github.com/VR-25/acc/releases/download/v2020.4.22-beta/acc_v2020.4.22-beta_.202004220.zip

The voltage limit wasn't being reapplied across reboots (fixed).

Custom current limit not supported by such an advanced device is weird. Try the latest version.

See what the voltage reading is, shortly after uplugging at 80%.

Yes, but instead of 80-90, go for 80-85.

AccA 1.0.23 (27) can't limit current nor voltage (bug). Use the command line. There was a problem with voltage control (fixed).

Yes, logs will help. Install the latest version first.
[Magisk] jal3223:
Awesome. Thank you for the willingness to help. Do you want me to start the log before I connect the charger or wait until it starts charging first and then start the log process?
[Magisk] VR25:
In this context, you can export logs at any time and under any condition.

Simply run acc -le.

It'll generate the log archive and print its path.

Edit: [MENTION=1638061]jal3223[/MENTION], if you have a Telegram account, message me @vr25xda to sort this out faster.
[Magisk] jal3223:
Awesome, thank you so much. I’ll get it to you when I get home from work tonight.
[Magisk] LoliIsMe:
Hi, I'm observed a bit of weird situation. I was plugged in and it charged up to 80% and stopped, as intended, and I left it plugged in till it discharged to 70%, and it resumes charging. The weird thing is it charged from 70% - 80% so damn quick, like 1% every 5sec. Is this normal?
[Magisk] VR25:
It may have just been an Android visual artifact - i.e., the actual battery level may not have dropped.

Which acc version and device were your using?

If it was not the latest acc beta, from https://GitHub.com/VR-25/ACC/releases/ , upgrade, run acc -le and share the generated log archive.
[Magisk] gonzo1963:
Good afternoon,

I have installed the latest versions of Acc (202004220) and AccA (1.0.23 (27)) available, and it still doesn't work well.

I have adjusted the "Default" profile, so it should not exceed 80% load.

If I disconnect it from the charger for a while, it does lower the battery percentage, image 1; but as soon as I connect it it starts to charge despite what the image indicates, since the percentage of the battery continues to rise, attached image 2.

Also when I have it connected to the charger it says "Fast", despite the fact that the charger is normal and if I disconnect it it says "Unknown".

Smartphone: Motorola One Vision

Android versión: Android 10

If you need any more information, tell me and if it is "rare", tell me how to get it, since my technical knowledge is limited.

Regards
[Magisk] DebrupGhosh:
Awesome app
[Magisk] gonzo1963:
Good morning,

One more fact, in case it helps.

It has been unplugged from the charger for about 12 hours and this is currently the AccA main screen.

¿Charging?

RegardsView attachment 5003649
[Magisk] VR25:
Your device itself is the source of the problem.

Refer to README > TROUBLESHOOTING > Charging Switch.

Direct link: https://github.com/VR-25/acc/blob/dev/README.md#charging-switch

You can also run acc --readme to read the documentation on terminal.
[Magisk] gonzo1963:
Good morning,

Thank you very much for the reply.

My technical knowledge is very basic, and reading the link you have given me, I don't know how to do what it says; I only know how to make the adjustments in AccA.

If it can't be fixed, I'm sorry I can't use your app, because it's the only one that makes this function easy and well done.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
Well, from the app, you can select a different charging switch - then see whether charging control works as expected.

If it doesn't, try another switch.

Refer to the attached screenshot.

While this trial and error procedure can help, it's not as efficient as using terminal for the job.

All you would have to do is...

1) Run acc --test while the device is plugged in

2) Run acc -s s to pick a working charging switch

3) Test the reliability of that switch

4) Repeat steps 2-4 as needed

Note that most charging switch issues are recognized and taken care of at the user's discretion.

This one is currently undetectable without user intervention.
[Magisk] gonzo1963:
Good afternoon,

A question, where do I enter the commands: "acc --test", "acc -s s" ?.

Sorry for my ignorance.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] beeshyams:
On Termux which you can download from Play Store

You have to give it root permission and above commands need to be run as root-which means you type su first and after that the commands
[Magisk] VR25:
v2020.4.27-rc (202004270)

- ~65% faster charging switch testing

- acc --help and --info enhancements

- Current & voltage control fixes and optimizations

- Fixed acc --force and tarball installer

- Optimized main installer

- Potential fix for "inaccessible or not found" error

- Updated documentation

Flashable zip: https://github.com/VR-25/acc/releases/download/v2020.4.27-rc/acc_v2020.4.27-rc_.202004270.zip

AccA 1.0.23 (27): https://xdaforums.com/sho...postcount=3379

AccA users can also upgrade ACC from within the app: 3 dots > settings > acc version.

Note: if you want to use ACC App (AccA), do not flash ACC prior to installing and launching AccA. Otherwise, the app will reinstall the ACC version that comes with it.
[Magisk] gonzo1963:
Good afternoon,

I have done what you told me, and when I have typed the command "su acc --test su", and it seems that there is something wrong or strange.

Attached screenshot of what appears in termux.

Regards