yashsingh1/xdaforums huggingface dataset:
[Magisk] VR25:
Greetings everybody!

- A new version is up.

# 2017.11.5 (201711050)

- Additional devices support

- Control files caching for better performance

- Fixed MacroDroid config

- Massive optimizations

- Updated Tasker config

- Work in progress -- automation without apps (cs service)

Attached are "still unsupported" devices. Of course, there are more. These are just a few I'm aware of with very odd charging control mechanisms. More extensive investigation and debugging tools are needed to determine the target files -- work in progress.

This is a Magisk module. If you have no clue on how to install it, then you're in the wrong place my friend. It's dangerous out here -- snakes & spiders everywhere!
[Magisk] Ridsever:
Not working after last update. I can't make a debug file. Huawei P8 Lite
[Magisk] DeathNebula:
I get the same error after the last update, I have a oneplus 5. It worked great before.
[Magisk] deepak549:
Not working after update . Pls refer attached file for terminal error .

I am on OnePlus 3, magisk rooted and xposed
[Magisk] VR25:
Fixed.
[Magisk] deepak549:
Working perfectly.

Thanks :D
[Magisk] Ridsever:
Works, but there are some errors.
[Magisk] VR25:
Nice to know! :)

Cool. Say goodbye to "broken pipe" and zip errors right away. As per "charging not found", your device has an exception in the battery uevent file -- white spaces. Those have to be filtered out. Next version will kill all these issues. ;)
[Magisk] michaelcrossland:
Hi I'd like to try this out but every time I try to use it in both of my terminal apps. Using both just SU then cs and tried the su # ad well both don't work. Just keep telling my the device unsupported. I have a SM-G900T running 7.1.2. I hope that someone can figure out what is going on as this app could help my battery a whole lot.
[Magisk] Tommytommy1234:
I guess can work if you disable Temperature Check in acc app. And yeah, you need magisk to get the module.
[Magisk] MB525:
Sorry if the question was already answered or is stupid... just found this incredible tool and this thread is loooong.

Am i right that it would be possible to set this daemon to automatically:

- Charge to f. ex. max. 50% (or what would be best) in the evening and stay there to stress battery less over night

- then charge to 90% in the morning to get through the day
[Magisk] stillnoexpert:
How about aged batteries? (Some years used)

I ask, because when I always charge from about 50% or 60% to 70% then there are different voltages at the end of the charge. I did that now for several times and the final voltage went from 4050 mV to 4200 mV in 3C Battery Monitor.

Device: Oneplus 2 (LineageOs 16)

(I got it a few days ago)
[Magisk] firefoot007:
Ok, i seem to have found out the issue not letting my charge greater than 70 % (may help others too), cooldown was not the culprit. Actually its charging voltage, my device default charge voltage is 4400 millivolts and when set to 4050 mV or lower thru terminal or app, charging slows down (with lower mV understandably even more slow).

Right now voltage is set to 4199 mV and its charging 630mA at 89 %

Thanks for this module
[Magisk] stillnoexpert:
eldrod16's Maxlife seems to be quite old (from November 2017). It clams to charge SLOW.

Limiting to 500mA is easy. Put a film over the data line (D+, D-) in the USB connector.

Another way to limit mA is to use an USB extension cable. (brings mV down and as a result mA too)

The question is whether limiting to 500 mA is good, bad or useless for the battery life?
[Magisk] Demodroid:
Useless for charging. Charge as fast as you want, keep the temperatures cool. https://www.nature.com/articles/nmat4084

Discharging at a high rate does cause greater damage though. Also heat has a significant effect.
[Magisk] stillnoexpert:
I have a Oneplus 2 with aac running.

It looks like that the battery consumption after the end of charge is noticeably higher with the cable still connected than without.

Has someone been watching something similar?
[Magisk] MoHed:
Not happenning here

I usually leave my 1+6T connected to the charger overnight. It charges to 80% in around an hour. It then loses 3-4 percent overnight. This is the same whether the charger is disconnected or left connected.
[Magisk] goRt:
I get the same on my op6, when I pull the charge cable out I get next to zero battery drain.

Something's preventing deep sleep with the charge cable in.
[Magisk] shayanb2004:
it enable & disbales the charging periodically...50s/10s

how is it healthy for the battery? doesnt it make battery's life shorter????
[Magisk] cinmil:
Hi op.would u mind to told me this 3 switch setting for what?cant find any info for this switch on readme.info file
[Magisk] shayanb2004:
[MENTION=5228676]VR25[/MENTION]

the module won't turn off charging when the phone is idle and the screen is off

the moment I turn on the screen it cuts off power

Today when I picked up the phone it was charging and was 82% (threshold was 80)

after 5-10 Secs it cut off power

what should I do???
[Magisk] Demodroid:
The best way to configure the module is to use it to limit the max percentage of charge and also the max temperature. Current/C rate doesn't affect most batteries until you exceed 1C, which for most phones is more than 3000mA or 15W.
[Magisk] shayanb2004:
sorry to ask but I'm a little bit new

I'm using samsung S8 , 3000mA battery

how can I limit the current?

and I'm using the default voltage config
[Magisk] Demodroid:
Current is limited with a third party app, you don't need to limit it, use temperature control instead or use a slower charging brick.

capacity=0,101,70-80 # Disable shutdown/cooldown feature, it isn't useful, avoid discharging below 20% using common sense. Stop charging at 80%, resume charging at 70%.

#coolDown=50/10 # Comment this out because pulse charging doesn't help LiPo batteries and can actually be harmful.

temp=500-420_180 # Cooldown at 50'C. Pause charging at 42'C, increase this in hotter countries like India.

resetUnplugged=true # Optional, I use this as I charge my battery to 80%, 90% is the stock reset value.
[Magisk] shayanb2004:
Awwsome thanks a lot.

Btw with this temp config, temp will never reach the cooldown(50) ... Is that right?
[Magisk] Demodroid:
Temp shouldn't reach 50'C as it will throttle at 42'C.
[Magisk] shayanb2004:
I test the daemon with terminal and it is working

but I think android doze is getting in the way since sometimes the charger passes the Maxlimit charging state and after I turn on the screen it recognizes and switches the charger off...

what can I do to stop this from happening
[Magisk] elvinguitar:
I've got the same problem. Anyone knows the solution to this?
[Magisk] guidozoner:
Downloaded the app on GitHub but it keeps showing: Installation Failed. I'm on a Samsung A5 2017 (A520F).

Any thoughts?
[Magisk] Tommytommy1234:
Did you Installed the magisk module and granted root to acca app?
[Magisk] guidozoner:
Yes! I have installed the magisk modules through the downloads tab and then downloaded and installed the apk file (granted root as well).

After that I got that installation failed message and all I can do is to retry (message keep showing) or close the app.
[Magisk] Hastaloego:
hi is it normal that using dash charge on op5 becomes a stop and go on the last percentages before the set Max limit is reached?
[Magisk] rodrichu:
I'm unable to get accd to run. Running others commands appears to be working fine like acc -t, acc -d, acc -e. When I use "acc -D start" it says the daemon started but it do not work at all and acc -D says it's not running. What may I do?

Enviado de meu GT-I9505 usando o Tapatalk
[Magisk] shayanb2004:
[MENTION=5228676]VR25[/MENTION]

Do you have any plan to update the ACC??
[Magisk] Mikesew:
I founded that my phone battery control file is found @ /sys/class/power_supply/battery/status

Enabled Value---- Charging

Disabled Value---- Full

And It becomes Not Charging when I disconnected my phone from charger.

Please help me on setting the acc control file to my phone control file/custom control file via Terminal, b/c I doesn't understand the guide on README.MD of your module it's a little bit confusing.

My Phone is:-

BRAND:- TECNO

ANDROID:- 7.0 AOSP

RAM:- 2GB

ROM:- 16GB

CHIPSET:- MT6737M

Now a days I started to think that almost every devs focused and also try their work on Qualcomm and high end devices, Please take in cosideration with Mediatek phones also.
[Magisk] Mickey03:
Anyone with an idea
[Magisk] shayanb2004:
I think the thread is abandoned :(

nobody is answering :((
[Magisk] guest4711:
It heavily depends on the questions ;)
[Magisk] Mickey03:
We posted our phones bug or errors with your module in keeping with the forum rule so why it depend on type of question sometimes saying "I can't help you" is more than enough. Ok!
[Magisk] guest4711:
If anybody who reads a question and cannot answer it would write a post as you told us ("I cannot help") the threads will become almost unreadable... And some questions are so complex no one will answer. Other questions are answered a lot of times but nobody seems to read the answers before posting/asking again.

BTW: It's not my module.
[Magisk] Unspec:
I'm having massive discrepancies between system UI reported battery level, and ACC reported levels. This is way too big of a difference to be normal.

Almost a 30% difference.
[Magisk] Mickey03:
I Can't start the demon of acc on my phone please help me when i type acc -D it says demon started but when i check it's not.
[Magisk] Macusercom:
I can't seem to find ACC in Magisk anymore :confused:
[Magisk] lohanchien:
Yeah all I see is Advanced Charging Switch now. Built by someone else.

Can anyone explain the difference between ACC, MCC and ACSwitch?
[Magisk] shayanb2004:
Acswitch is based on the database from acc but it has less variables to set. Just the upper and lower threshold

No cooldown or voltage monitoring

I kinda saw it today that it isnt available in the magisk repo :(

Dont knkw what happened with the dev
[Magisk] wilsonhlacerda:
I've seen something about that on this trend before. Check some old pages that probably you'll find.

---------- Post added at 07:22 AM ---------- Previous post was at 07:19 AM ----------

I remember that OP [MENTION=5228676]VR25[/MENTION] frequently have Internet access problems, the place he / she lives seems is not well served.

Just be patient and probably he / she will be back soon.
[Magisk] yoyo182:
acc is the module using old magisk installer, which was deleted from the repo on may 1st.
[Magisk] Macusercom:
Oh, I see. Anyone knows if ACC is compatible with v19 or v19.1? They seem to change the way Magisk handles modules and I'm afraid of upgrading if it breaks ACC.
[Magisk] shayanb2004:
I am using acc (march 3rd update) with the latest canary and it is working fine
[Magisk] Macusercom:
Which canary? You mean v19? V19.1 is stable.
[Magisk] shayanb2004:
Check out the image
[Magisk] joemanbui:
Working okay for me on magisk 19.1
[Magisk] skinnywaffles:
Hello, I just got my pixel 3 and pixel stand, will this force fast wireless charge on the Pixel Stand? I keep seing stuff about how the stand never fast charges the P3 on its own and hope this makes that a non-issue. I will be sure to try it out. Thanks
[Magisk] HatchetEgg:
I flashed the latest version, despite it not showing in Magisk downloads. I did get a warning message when flashing it, and said something on the lines of "This module has not been fully tested, on this version of magisk" in this case version 19. But everything still seems to work as it did before.
[Magisk] rodrichu:
Is there an ACC by another person now?

Enviado de meu GT-I9505 usando o Tapatalk
[Magisk] shayanb2004:
haha

it was previously named acswitch

he just changed it to accontrol :D
[Magisk] mworl:
I installed the magisk module, then the ACCA and gave it root access.

On starting the app I get the message "Config read error. I wasn't able to find the AAC config file"

The daemon is not running and will not start, at least not through the app UI. Also there is not sdcard/acc folder on my device. I'm on a pixel 3 running lineage os.

Any idea how to get this working?

Edit: Nevermind, had installed an old version of the module. Reinstalled latest and working
[Magisk] VR25:
Charging slow down

Yes, set "shutdown at" to zero.

I'll be updating djs soon. A new ACC version may be release before it, though - and it will no longer include djs.
[Magisk] VR25:
As I observed, BMS temperature readings cannot be overridden. Your case may be different. Try writing a different value to /sys/class/power_supply/battery/temp (or batt_temp). If it sticks, I'll automate that.

I use a modded battery on my Moto G4 Play and it always reads -42°C. The battery charges slower than normal and hardly reaches 80% capacity and/or 4.2V.

The issue is usually caused by broken thermistor.

In my case, I'll have to rewire the battery pins to use the thermistor.

50 is good. A little lower (e.g., 45) is better. You can program this, but the current scheduler (djs) is very rudimentary.

For now, here's how you do it:

su [Enter]

acc 45 44 && sleep $(( 60 * 60 * 7 )) && acc 90 80 [Enter]

Translation:

acc 45 44 # keep battery capacity at ~45%

sleep $(( 60 * 60 * 7 )) # for 7 hours

acc 90 80 # keep battery capacity at 80-90% for the rest of the day while plugged in

djs, the scheduling module is still in its infancy. It will eventually make this easier.

Due to inaccurate capacity loss calculations performed by the "smart (pseudo) battery" the reported capacity is not always real, even though the voltage may be. The next ACC has a feature named capacitySync that will solve this problem.

P.S., voltage changes dramatically with temperature and fast charging, regardless of battery age.

For this reason, there will no longer be a default voltage configuration.

That's good for keeping temperature low and slowing down voltage rise rate. Once voltage is in the "high" range (e.g., 4.2+V), this approach is no longer effective against rapid voltage rise, but rapid temperature rise protection still remains.

This issue is not directly related to ACC. Rather, it has to do with your device's charging mechanism. See whether enforcing a particular switch (acc -s s) solves the problem.
[Magisk] VR25:
That's the same as "acc -s s" command. It lets you select a particular switch from the database and use it only, as opposed to cycling through all (automatic mode). Use this when you have issues such as those below.

Refer to the previous answer.
[Magisk] VR25:
I focus on all devices.

Enable this switch right now by running acc -s s "battery/status Charging Full"
[Magisk] VR25:
So far, 3 users have reported that. I'll talk more about it later.

The next ACC version is bringing capacityOffset and capacitySync features to tackle this issue.

It's coming back soon.

P.S., the current version is compatible with Magisk 19.
[Magisk] VR25:
To force fast wireless charging, run acc -s onPlugged wireless/voltage_max:9000000.

Alternatively, you can open /sdcard/acc/config.txt in a text editor and set onPlugged=wireless/voltage_max:9000000. Changes take effect within seconds.
[Magisk] shayanb2004:
[/COLOR]

I did force the batt_slate_mode but it didnt work and it cuts off power at some random point

sometimes on the desired level that I have set and sometime around 82 (my upper threshold is 80) :confused:

btw happy you are back ;)
[Magisk] VR25:
Thanks!

Is "shell" excluded from battery optimizations/saver? If not, this could be the issue.

...Or your kernel may have some crazy power saving feature that blocks even the shell by default.
[Magisk] shayanb2004:
shell is not among the optimised apps (it is not optimised) & I love my kernel it runs great

well it works somehow for now :D (doesnt matter 2-3 percentage above or below)

im just happy that it works :) ;)

will be waiting for your awesome updates too :)
[Magisk] davidk21770:
I am having a problem that took me a long time to figure out. I appologise if it's been reported and there's a fix that I haven't found...

I control acc using shell scripts that I can execute from an icons on my desktop using fx file manager.

I found that sometimes navigating using the GPS in my car, it slowly discharges to 0! and the only way to overcome this was to reboot with acc disabled.

I think that I've discovered the reason -- the sun + GPS battery draw is increasing the temperature dramtically and you throtte trying to reduce temperature! But the throttled charge is not enough to overcome the draw of the GPS.

Right now, it does not appear to be possible to change the temperature throttlig from the commandline (IMO, *all* settings should be accessible without resorting to an editor). Can it be brought out? Or (alternatively), can a charge threshold be applied to the temperature throttling -- say if the battery's below 35% it stops throttling altogether?

-- or have I misdiagnosed the problem. <sigh>
[Magisk] wilsonhlacerda:
Have you tried the ACCA app? Even on it there's some temperature fine tuning. I'm not sure I got your point, but that may help you. To download it, see previous pages.
[Magisk] shouk_1987:
Updated to today's version and acca had an error as attached
[Magisk] rayman128:
acca keeps asking to reboot after i updated to latest
[Magisk] paolocorpo:
dear VR25

Nexus 5X and last version of your module

I noted the battery level achieved 95% despite the limit was set to 85%
[Magisk] MatteCarra:
Here you are a temporary apk with the necessary compatibility fixes.

I'm very far from the final version, but I won't be able to do more updates until next Saturday because of university.

All the basic stuff should work.

I've not yet implemented scheduled tasks.

Let me know if you face any problems.

Download: https://github.com/MatteCarra/AccA/releases/tag/1.0.5

EDIT: OUTDATED. NEW version

P.s: if you want to select a profile just click on it. if you want to edit/remove long press on the profile.

This will be changed in the next release obviously.
[Magisk] Macusercom:
I just upgraded ACC and it works fine without a reboot. However, if I reboot ACC can't be found anymore. I have to reinstall to get it running every time. It is not recognised in the terminal nor can I get acc to run.

Using OxygenOS 9.0.5 on a OnePlus 6 with Magisk 18.1.
[Magisk] rayman128:
i updated the ACCA app with the latest module and the acc daemon still won't run :(
[Magisk] elimiriel:
On HTC 10, It shows ACC is working at the terminal command, but current ACC and battery percentage status are not recognized correctly, and config via app seems not applied.(battery was 86% because my previous charging limit was 90%)
[Magisk] MD500:
I Installed ACC with Kitkat (yes, magisk 19.1 support KitKat) but it doesnt work.

When i type:

acc

I get:

Acc[541]] Set: pipefail: bad option

Installed ACCD but it force closes.

org.xmlpull.v1.XmlPullParserException
[Magisk] VR25:
[MENTION=4235848]davidk21770[/MENTION], you can increase temperature limit by running acc -s temperature 40_50_90

Ignore the 40 for now (use it as is); focus on the 50°C and the pause time (90 seconds).

Everyone,

The latest ACCApp (1.0.5) is incompatible with the latest ACC (201905121). Always make sure you're using the latest ACC before reporting issues.

If Android Studio worked fully offline (i.e., no need to sync regularly), I'd have fixed ACCApp right away. I'm currently waiting for Gradle to finishing syncing on my slow-af network. MatteCarra and Squabbi have been busier lately. We haven't been able to sync as much nor as fast as we used to.

How to Grab Relevant Logs

1. Reproduce the issue

2. Run acc --log --export (-l -e for short)

- The output file is /sdcard/acc-logs-deviceName.tar.bz2
[Magisk] MatteCarra:
[MENTION=9909286]rayman128[/MENTION] [MENTION=2530490]elimiriel[/MENTION] The app was compatible with yesterday builds.

Here you are a temporary apk with the necessary compatibility fixes.

I'm very far from the final version, but I won't be able to do more updates until next Saturday because of university.

All the basic stuff should work.

I've not yet implemented scheduled tasks.

Let me know if you face any problems.

Download: https://github.com/MatteCarra/AccA/releases/tag/1.0.6

P.s: if you want to select a profile just click on it. if you want to edit/remove long press on the profile.

This will be changed in the next release obviously.
[Magisk] rayman128:
[MENTION=9731715]MatteCarra[/MENTION] thank you for updating the app and helping out ? despite busy sched. The app still can't find the ACC config file and ACC Daemon doesnt run

update: its all fixed now thank you!
[Magisk] Macusercom:
Still got the issue with acc not being found. After a reboot even /dev/acc/magiskPath/acc isn't found. I always have to reinstall after a reboot to get acc working.

Is it possible that it is v18.1 related? I did not upgrade yet.
[Magisk] rayman128:
[MENTION=9731715]MatteCarra[/MENTION]

update: I setup my settings for Cooldown option and it is not working
[Magisk] MD500:
Unable to make log in latest version...

Using KitKat 4.4.2
[Magisk] paolocorpo:
dear all

i don't remember the app that can workaround the small issue related to the sound related the alternate switch on/off of charging when we are under safe range

Anybody can help me to refresh my memory ?

Thanks in advance

Paolo
[Magisk] MatteCarra:
I would recommend to upgrade to the latest Magisk now that acc supports it.

Vr25 is working on a fix with the installer, please be patient.

Once it will be available I would recommend to re-download the apk from the same link and retry.

May I know what was your issue?
[Magisk] VR25:
This may be related to the PATH variable. Try running /sbin/acc. Which terminal emulator do you use? What's the output of echo $PATH?

Logs, please...

acc -l -e

Upload /sdcard/acc-logs*.tar.bz2.

See whether there are logs in /sbin/_acc/.
[Magisk] shayanb2004:
when i type the command acc --voltage :4000

it only shows the option "exit" for my control files

what can I do to add control files?

My device: galaxy s8 exynos 8895, android PIE
[Magisk] Macusercom:
/sbin/acc isn't available too. $Path shows nothing for me. It simply uses the root / folder.

Point is, acc and /dev/ works fine after a fresh install. No issues. But once I reboot it is gone and doesn't work at all nor can the folders be found. Reinstalling it always makes it work after a reboot.

Also simply "acc" should work after rebooting right? This command can't be found after rebooting.

The March version works perfectly fine for me though.
[Magisk] rayman128:
This is from my log when i open the app:

/system/bin/sh: <stdin>[97]: acc: not found
[Magisk] MatteCarra:
Try now with Magisk 19 and re-download the apk from the same link.

The bug has been fixed.

[MENTION=9909286]rayman128[/MENTION] you can try as well.
[Magisk] rayman128:
My Magisk is v18.1 and cant update since my phone cant update to the latest. The app doesnt show errors anymore but the Cooldown option just doesnt apply.

The March build with the ACC module of [MENTION=5228676]VR25[/MENTION] before all of this worked just fine.
[Magisk] Macusercom:
Same. I do not use the app simply command line but if I use it, I get the same after rebooting. Again, up until rebooting I can use the terminal and the app. After rebooting it's not found.
[Magisk] VR25:
Are you using the latest version? Check for updates to make sure. Does the file /sbin/_acc/acc-power_supply-* exist? If so, upload it.

Do you see "acc: exec [service.sh]" in Magisk log? Does /data/adb/modules/acc/ exist? Is is not empty? If so, does acc work after running "sh /data/adb/modules/acc/service.sh" as root?
[Magisk] VR25:
Why exactly can't you update to 19.1? Bootlop?
[Magisk] rayman128:
after installing the v19.1 update, when its booted gives me "magisk is not installed" and methods i try so far failed (flash in twrp, etc.) so im stuck at v18.1 till someone finds a workaround
[Magisk] MD500:
Log:
[Magisk] rayman128:
[MENTION=5228676]VR25[/MENTION] [MENTION=9731715]MatteCarra[/MENTION]

If its okay with you guys but I'm fine with sticking to the March Build for now, I need the March Build Module of ACC