yashsingh1/xdaforums huggingface dataset:
[Magisk] VR25:
v2020.10.14 (202010140)

- acc -i: show additional power supply info, if any.

- build.sh: copy uninstaller to build dir.

- cooldown_current: instead of pausing charging periodically during the cooldown phase, lower the charging current (0mA or custom). This is the default behavior (smoother).

- Fetch current and voltage control files only once per boot session to prevent loss of default values.

- Fixed daemon restart/stop timeout issues.

- Fixed Zygote-related issue that prevented accd initialization on boot.

- Misc fixes & optimizations

- MTK switch delay ranges from 5 to 20 seconds.

https://github.com/VR-25/acc/releases/tag/2020.10.14

See whether this issue remains.
[Magisk] VR25:
v2020.10.15 (202010150)

- Current control optimizations

- Dynamically determine the right temperature reporter; use a dummy file (25°C) if none is found.

https://github.com/VR-25/acc/releases/tag/2020.10.15
[Magisk] h-cspu:
I can confirm that starting accd out of userinit.sh works again. :good:

But, AccA shows still 0mA and -1°. (AccA version 1.0.28 with acc version 2020.10.15 -Master-) :(
[Magisk] gonzo1963:
Good evening,

I am in full testing with the tablet.

One question, if I only install AccA and from the app, I install Acc, would it work?

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] swieder711:
From my experience, AccA will install Acc for you.
[Magisk] gonzo1963:
Good morning,

My question corresponds to a device that is rooted with SuperSU and with added Busybox, which is different if it is rooted with Magisk.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] VR25:
Share a fresh log archive generated by acc -le.

P.S., acc logs contain no personal information.
[Magisk] VR25:
Yes, AccA, the app alone, is enough.

It comes with acc.

Though, I recommend upgrading acc afterwards.

AccA > hamburger menu (3 dots) > settings > acc version > master
[Magisk] VR25:
Is the latest acc (October 15) working for you?
[Magisk] h-cspu:
Another log archive?

I don't have AccA installed anymore and use only acc.
[Magisk] Koushik87:
Thx dev. October 15 version fixed issue of settings getting defaulted after the 1st charge. DJ's still have issues but i can live with that.
[Magisk] ssdnvv:
When testing battery idle mode, AccA tells me that my kernel doesn't support it.

What exactly needs to be activated in kernel to have this function supported?

I'm using lineageos 17.1 stock kernel on a Sony Xperia XZ2 compact.
[Magisk] dtrail1:
You can't. You need a kernel with certain support for battery management and drivers. Most custom mod kernels do support such things. See if there is a custom kernel that supports also LOS/AOSP roms for your device.

Gesendet von meinem unknown mit Tapatalk
[Magisk] Koushik87:
Only certain kernels support battery idle mode like MCD and Radioactive. Both are good... support custom rom ..gives good SOT. But my personal preference is MCD. Check if your device is supported by the dev though.
[Magisk] ssdnvv:
There seems to be an issue on my device with the display of current battery percentage - this started somewhen after testing battery idle mode.

The battery is not showing the current value anymore neither in AccA, nor in settings (see attached picture - I configured AccA to load until 80% once, it loaded until 83% and then the load level didn't decrease anymore for more than 2 hours now).

What can I do to debug this and get my current value and stats back?

Edit: never mind, it seems there was really no consumptionin that period. It now decreased to 80% another hour later.

View attachment 5118387
[Magisk] OSX.Nobody:
Hi, I have some stupid questions, please bear me.

1).. It says 3920 mV is an ideal value to set for voltage. but what I see is, voltage is never constant, even without ACC. Rather is depends on battery capacity. When charge is low (say 30-40), voltage is around 3920 mV, no matter charging or discharging or even fast charging. And when capacity is high (say 70+), voltage is always higher than 4100 mV. even without charging. So I'm confused, when doc says 3920 mV is ideal, this value is depends on what? because it seems rather related to capacity than charging. (it would be nice to have an explanation)

2).. Now based on 1st point, when i set value to 3920 mV. as long voltage is less than this range, all good. but as charge increases, voltage reaches higher than 4000 mV. then battery health shows "Over", in CPU-X app, it shows "Unexpected Failure".

3).. Idle mode doesn't support on my device, so I tried another workaround as mentioned in the doc. I set the current value to 0mA (tried 50mA too). but it leads to unexpected behavior. Current value keeps jumping in -300, 0, 50, 500, >1500. When it jumps to minus value, charging shows disconnected. so its jumping between charging and discharging. (also setting any value less than 1000mA leads to unstable current value) If I set it to 1000, then it stays around this value.

4).. When battery limit reaches, is it safe to leave the charger connected for a long time? not just for battery, also is there any effect on Charger? I have a 30W fast Charger.

5).. About Cool-Down feature, does it have any negative effect on either battery or charger to constantly keep connecting and disconnecting every 50 seconds? Like, degrading battery lifespan?

6).. In order to enable/disable charging at specified value, I think acc has to pull battery status every few seconds, isn't it power consuming?

7).. Why there's no way to disable acc temporarily in AccA apps. Also no option to deselect all profile. Only workaround I can see either reset from shell, or stop the daemon, which is also auto start every time I open AccA.

I'm afraid if anyone will reply to such big post. But It would be really helpful. Thanks.
[Magisk] Keule-Tm:
Open AccA; in the "Battery" card choose "Load once to #% without restrictions" (or equivalent, in German "Einmal bis #% ohne Einschränkungen aufladen").
[Magisk] swieder711:
Acc Oct 8 has been working nicely for me. I just updated to Oct 15 and will let you know if any issues come up. Thanks for the continued work on Acc/AccA.
[Magisk] Extreme_Ninja2099:
Hi, I installed ACC on my Oneplus 6T. I just want to know about my stats, which line in acc -i is the battery cycles?
[Magisk] OSX.Nobody:
No one to reply? can anyone at least suggest another place where i can ask these questions ?
[Magisk] gonzo1963:
Good afternoon,

Finally, with the latest versions of AccA (v1.0.28) and Acc (v2020.10.15) almost everything works fine on my smartphone: Motorola One Vision.

Two things do not work:

1.- The function: "Prioritize the battery inactive mode". If I activate it, it is always charged to 100%.

2.- If I turn off the smartphone with the charger plugged in, it also charges 100%. With "AccA v1.0.24" and with Acc included: "v2020.5.4-rc", under the same circumstances, it respected 80% as maximum load.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] yalyq:
Anyone facing battery drain after install this module?
[Magisk] jaggillararla:
Yepp I stopped using it. Made my sot go dooooown
[Magisk] tavocabe:
For me, scheduled jobs is not working, I've set up to begin charging to 100% at 6am but it's not getting triggered so I woke up to a ~70% charged phone. Also, when I go to shedules in AccA it's blank with no shedules registered.
[Magisk] VR25:
[MENTION=8958852]OSX.Nobody[/MENTION]

Recall that battery voltage and charging voltage are not the same.

Even if the charger can supply constant voltage, battery voltage won't be constant.

It varies due to factors such as battery age and chemistry, temperature and charging current.

After unplugging the charger, battery voltage eventually drops to nominal (~3.8 Volts for modern batteries).

Limiting the charging voltage to 3920 mV when the battery voltage is already above that does not mean it won't eventually drop to ~3920 mV.

That number is frequently quoted by Battery University.

One of the sources is https://batteryuniversity.com/index.php/learn/article/bu_808b_what_causes_li_ion_to_die .

A battery testing and maintenance company (Cadex Electronics Inc.) supports the website.

This suggests your kernel does not support custom charging voltage limits.

Refer to readme > troubleshooting > custom charging current and voltage limits.

Same as #2.

Greatest longevity is achieved through maintaining 40-60% capacity or 3.8-3.9ish Volts.

The longevity of the charger and/or power brick is a different story.

Generally, you don't have to worry about this.

I don't recommend "fast chargers", though - let alone "wicked fast chargers", the greatest and most destructive gimmick ever.

Regular power adapters are safer and last a lot longer.

No, what causes problems is prolonged exposure to high voltage and temperature - which is exactly what cooldown fights against.

Cooldown lets the battery, and charging gear take breaks.

It does so very efficiently.

You can use a resources monitoring app to check.

You'll find that Android apps, even those that don't even run in the background (e.g., AccA itself), consume way more power than acc daemon.

The "charge once to a given % (default: 100) without restrictions" feature is available (acc -f 100 command or within AccA app).

Once the desired battery level is reached, accd restarts with regular settings.

AccA has several issues (especially with profiles) and it does not map all ACC features to a Graphical User Interface.
[Magisk] VR25:
If your battery is draining fast, your device has a troublesome charging switch or your config is wrong.

Refer to readme > troubleshooting > charging switches.

Also ensure your config is correct or just reset it with acc -sr.
[Magisk] VR25:
[MENTION=5189622]gonzo1963[/MENTION]

1. This confirms my suspicions. I'm removing that setting.

2. Note that changes made by acc are not supposed to persist across a shutdown/reboot.

ACC does not work when the phone is off and charger is plugged.

Refer to readme > troubleshooting > charging switches.
[Magisk] ausaras:
I am using ROG Phone 2 with the latest AccA (1.0.29). I think there is something wrong with the "Cool Down" feature.

Whenever I enable "Cool Down", the charging current is very low...around 300mA or less. Sometimes, it stays in the negative range. So, my phone is not even being charged.

I think it worked find when I was using AccA 1.0.26 or 1.0.27.
[Magisk] Vantskruv:
Hello again!

I wrote before I uninstalled ACCA, but I got some problems anyway which I thought was the cause of ACCA, so I reinstalled. But I think I got some major problems with ACCA again, and uninstalled (charging switches where automatically changed, even though I forced to set a specific a charging switch in config file, also ACCA seemed to freeze, i.e. when pressing the cogwheel icon on the mainscreen to see current loaded settings).

Though, I remember first time not using ACCA, still my set charging switch (charge_disable 0 1) was reset to automatic. I do not understand why this happens, as this charging switch works perfectly well on my device. Is it because ACC crashes, and restarts loading default values somehow?

Basically, to allow me to troubleshoot, I need to understand how ACC is started initially, and if there is some type of poll-service, that checks if ACC is running or not, and restarts ACC if it is not running (i.e. if it crashed). I am not sure if there is something like that, or even if ACC is crashing, hence, what is happening?

I am not sure where the log-files are stored, but is it correct to read the log by typing "acc -l -a cat"?

Edit: Note that the charging switch does not always change, sometimes it works perfectly, but I have no clue why the charging switch is reset without me doing anything, or maybe I done something without knowing it? Under which circumstances can this happen without calling "acc -ss", or changing the chargingSwitch line in config file to "chargingSwitch=(charger/charge_disable 0 1 --)"?
[Magisk] OSX.Nobody:
Thanks for replying. I got all my questions answered. I have two more queries,

1) I have read the Troubleshooting section, I want to mention about current limit again,

Setting the value to 1000mA or above DOES work. As example, If I set it to 1500mA, it will be around this value (eg 1450mA to 1570mA). For values less than 1000mA, it still does work, just not stable.

So, does that mean my device supports current limit? is it safe for me to use value above 1000mAh?

2) Unfortunately, my phone came with a 30W fast charger and I don't feel safe to use cheap charger from market.

Is there any switch to disable fast charging via acc? eg "adaptive_fast_charging" . If there's, how to find the correct switch for my phone?

Thanks again.
[Magisk] Vantskruv:
Latest version seemed to have fixed this. :)

I think I found a bug in acc.

When typing the command acc -s "s=charger/charge_disable 0 1 --", the config file may look like this:

chargingSwitch=(charger/charge_disable 0 1 -- 0 1"

hence, the extra '0 1'.

This happens only if the chargingSwitch is already set to a charging-switch.

So, I bought the Tasker app, and have setup some tasks:

Charge to 42%

Charge to 62%

Charge to 80%

My profile in Tasker is set to run a task at a certain time, i.e 06:30 in the morning.

How do my tasks looks like and how did I set them up?

I.e for 'Charge to 62%', I created that task and named it like that.

Then I added two shell commands (to add a shell command, press the '+' icon, and then select Code->Run_shell. A dialog appears).

For the first command, I tick the 'Use Root' option, and then type in the command in the Command field:

acc -sr

This command resets the current config. I need to do that because otherwise the bug I wrote here in the top of post will appear.

The second command, I do the same, but the command is:

acc -s mcc=500 mcv=4000 rc=59 pc=62 "s=charger/charge_disable 0 1 --"

Why do I enforce the charging-switch? That is because I noticed that the chargingSwitch may be reset, i.e. when terminating or restarting acc.

I currently do not know how to make acc default to a set chargingswitch when restarted....
[Magisk] VR25:
**v2020.10.24 (202010240)**

- [Experimental] Current-based charging control - enabled by setting charging_switch=milliamps (e.g., 250).

- cooldown_current is no longer the default cooldown method due to issues observed on some devices.

- Fixed `acc -ss`.

- Major optimizations

- New charging switch for OnePlus Devices

- Shutdown if battery temp hits shutdown_temp, default: 65 degrees Celsius.

- Updated default config, project framework and readme.

Release Notes

- AccA has been found to be behind several issues, e.g., unwanted config resets, changes to config not sticking.

- If you still face issues after uninstalling AccA, see whether resetting acc config (`acc -sr`) helps.

- Recall that if you feel uncomfortable with terminal, you don't have to use it at all!

The config file can be edited manually (text editor).

The process is very straightforward.

Just do not edit in Windows Notepad, ever!

It replaces LF (Linux/Unix) with CRLF (Windows) line endings.

https://github.com/VR-25/acc/releases/tag/v2020.10.24

Edit

The charging switch reset issue is caused by AccA for the most part.

It happens after switching profiles.

See if the latest acc still has it (with AccA not installed).

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

Running that multiple times causes no issues.

i.e., the chargingSwitch=(battery/charging_enabled 1 0 --) remains intact.

I tested the latest version.
[Magisk] VR25:
You can even set the limit to 9999mA.

The phone will simply ignore it - i.e., it'll draw only the max it supports.

Your device supports custom max charging current limits.

Values that don't generate noticeable heat are safer.

You have to test.

I use 1000mA most of the time, 500mA at night and 2000mA max (for when I'm in a hurry).

Just lower the max charging current limit.

Ignore what the lock screen says about charging power.

It's inaccurate.

Check the output of acc -w or acc -i instead.
[Magisk] VR25:
Those who face major issues with AccA, stick with Tasker, MacroDroid (free) or similar, for now.

Scheduling profiles with these apps is very straightforward.

Config reference in in the config file itself: `/sdcard/Documents/vr25/acc/config.txt`.
[Magisk] Vantskruv:
Seems to work quite nice now, with Tasker, knock on wood! :D

Thanks!
[Magisk] jaggillararla:
Did mattecarra fix it on the latest acca ? The v 1.029?
[Magisk] OSX.Nobody:
Thanks for your time and detailed explanation. Have a good day. [MENTION=5228676]VR25[/MENTION]
[Magisk] Vantskruv:
[MENTION=5228676]VR25[/MENTION]

Do you want some log files generated by acc -le command?

ACC worked very nice yesterday in batteridlemode. Before I went to sleep, I noticed my phone UI got locked up, so I restarted the telehpone, and initialized acc with my script:

$su -c 'acc -s mcc=500 mcv=3920 rc=30 pc=42 s="charger/charge_disable 0 1 --"'

And then went to sleep. When I wake up, I noticed that telephone charge was at 100%. The first thing I did was to pull out the plug, and execute the command acc -le to save the logs.

The logs is quite hard to decrypt and read, so I am not sure what the cause of this, maybe the charging switch I use does not work as well as I thought?

I am afraid to but up the the acc-logs-coral.tar.bz2 file here. Answer or PM if you want to read the logs, and them being given to via PM or another way.

I am using a Google Pixel 4XL (Android 11 RP1A.200720.009), and ACC version v2020.10.24
[Magisk] VR25:
[MENTION=6541888]jaggillararla[/MENTION], AccA v1.0.29 still has major issues.

[MENTION=2508606]Vantskruv[/MENTION], it seems the command failed to restart accd or it wasn't running in the first place.

Whenever the charging switch is updated via acc -s, accd is automatically restarted.

You don't need to issue acc -s s="..." every time.

The logs do not contain any personal/private information.

I'm pro-privacy.

You can share the archive here or somewhere else, no big deal.
[Magisk] edorner:
Hey Romain,

Unfortunately, I can confirm that the issue is still present, the wakelock is still there with the Mi 9T Pro / K20 Pro. (I am on the latest release of LOS 17.1 and the stock (perf) kernel, BTW. ) See attached screenshots, created after the phone was left on the charger, with the screen off, 20min after the charging had terminated. Maybe trying one of the custom kernels is worth a shot, there are quite a few available for our device.
[Magisk] VR25:
This is a kernel issue.

The latest acc has an experimental feature that aims to cover it and add idle mode support to more devices.

### Current-based Charging Control (EXPERIMENTAL)

Enabled by setting charging_switch=milliamps (e.g., `acc -s s=0`, `acc -s s=250` or `acc -ss` (wizard)).

Essentially, this turns current control files into [pseudo] charging switches.

A common positive side effect of this is [pseudo] idle mode - i.e., the battery may work just as a power buffer.

Note: depending on the kernel - at `pause_capacity`, the charging status may either change ("discharging" or "not charging") or remain still ("charging" - not an issue).

If it changes intermittently, the current is too low; increment it until the issue goes away.
[Magisk] edorner:
Thanks for the tip, [MENTION=5228676]VR25[/MENTION].

I gave both s=0 and s=250 a try (with the v2020.10.24 stable version), but unfortunately neither of them worked for me. Once the pause threshold was reached, charging was terminated, and the battery began discharging. On issuing acc -s after the charge cycle, I noticed that the active charging switch reverted to "input suspend". Edit: interestingly, resume and pause capacity also revert to my previous choices.

After modifying the switches, I did not restart the daemon (since the readme says it is performed automatically when needed).

On the other hand, I did try to disable the charging switch cycle/fallback mechanism, but did not succeed. Both acc -s s=0 -- and acc -s "s=0 --" commands were rejected by acc. So, in the end, I applied just the plain acc -s s=0/250 commands like you suggested, and I also tried setting them through the wizard, with the same result.

Edit: Logs attached
[Magisk] VR25:
[MENTION=2732498]edorner[/MENTION], run acc -s s=0 again.

See if it works after a reboot.

Another user deported success with this procedure.

The subsequent tests (e.g., acc -s s=250) don't require a reboot.

I'm updating the logic and documentation of this feature.
[Magisk] edorner:
Ok, I gave it another try:

acc -s s=0

reboot

check if settings are still retained: acc -s -> yes, they are

plug in charger while capacity < resume capacity -> charging begins

pause threshold reached -> charging terminated again, battery is discharging

check if settings are still retained: acc -s -> yes, they are

create log export package #1

acc -s s=250

plug in charger while capacity < resume capacity

-> charging begins ... or so I thought...

As it turns out, even though LOS shows "charging rapidly" on the lockscreen, and ACC also reports "charging" state, the phone draws no current at all from the charger. Instead it is discharging at the same rate as if the charger weren't connected.

create log export package #2
[Magisk] VR25:
**v2020.10.28 (202010280)**

- 500 mA preset for charging_switch.

- `acc [pause_capacity [resume_capacity, default: pause_capacity - 5]]`, e.g., acc 80 (resume_capacity defaults to 80 - 5)

- Enhanced current-based charging control (still experimental, but should be more stable now).

- General fixes and optimizations

- Updated documentation.

Release note: those using current-based charging control should reboot after the upgrade.

https://github.com/VR-25/acc/releases/tag/v2020.10.28

@edorner, see how things go with this one.
[Magisk] fabix95:
https://imgur.com/gallery/VXhHbcp this Is my setting and my situation al 100% with op8 pro. Idle mode work or not?
[Magisk] jaggillararla:
Hahahahahah he just said don't use acca ?? what do you do? Use acca ??

Thank you for making my day fabix
[Magisk] gonzo1963:
Good morning,

I have discovered the "Charging switch" of the "BQ M10FHD" tablet, it is this:

/sys/devices/platform/battery/power_supply/battery/status/

The problem is that the options are not "1" or "0", they are "Charging" and "no charging", and it is not possible to write these options.

Another curious thing, the AccA version 1.0.28 works; version 1.0.29 doesn't work, it hangs installing Acc and doesn't install it.

An important fact: the tablet is rooted with SuperSU and with Busybox installed, not with Magisk.

Regards

Enviado desde mi unknown mediante Tapatalk
[Magisk] Vantskruv:
I do not know why, but my acc (v2020.10.28) seems to always reset the set chargingSwitch to nothing at all, and then fails when reaching idle mode, charging it up to full (not using ACCA). It has worked before when I was at a previous version off acc (do not remember which) and Android 10. Now I am using Android 11 on my Pixel 4XL.

Sorry for complaining. :angel:

Edit: Sometimes it works though, as it currently do now. :eek::rolleyes:
[Magisk] Vertron:
The charge limit doesn't work for my Alldocube X (MediaTek), it hides the charging icon but it continues to charge. Any ideas how to fix it?
[Magisk] VR25:
AccA needs major fix-up.

/sys/devices/platform/battery/power_supply/battery/status is just a status reporting file.

All devices have it.

You can't use it as a charging switch.

The file is read-only to begin with.

On devices where it is writable, changes do not stick.

Devices such as the Nexus 7 2013 (flo) reboot right after the file is modified.

Install the acc version that works then upgrade acc from settings > acc version.

If you still have no known charging switches after upgrading acc, share the file generated by acc -le.

ACC/A works as long as you have root and Busybox.
[Magisk] VR25:
This is most likely a charging switch issue.

Refer to readme > troubleshooting > charging switches.

It seems batt_slate_mode does not work properly.

acc -t says store_mode does not work, but if the first fails to re-enable charging, logically, the second will fail completely.

See if enforcing store_mode with acc -ss and rebooting solves the issue.