yashsingh1/xdaforums huggingface dataset:
[Magisk] MatteCarra:
AccA pre-release

This is a pre-release before the app is published on F-Droid and Google Play Store.

There are over 150 new commits and it's difficult to include everything in the changelog.

The most notable changes are:

Added back support for schedules and added the ability to schedule profiles on boot (the default profile for example)

Added a dark theme

Added a settings screen

AccA tries to detect current/voltage units of measure on first boot: all the measures will be consistent with it and can be changed in the settings #35

Added prioritize battery idle in the Acc config editor

Many design changes

An about section with the installed acc version and app version

The ability to choose the acc version in settings

Many bug fixes and optimizations

We need your help to finalize this update!

If you find any bug please report it to us at https://github.com/MatteCarra/AccA/issues .

It's vitally important that you make easy for us to reproduce the bug with a detailed description and include logs.

We have Crowdin page to translate the app in most languages and we need your help!

The goal of AccA is to empower anybody to control the charging cycle of their phones and we don't want language barriers to be an issue in this process.

The translation process requires people to translate and other people to check and improve translations when needed.

You can find the page here: https://crowdin.com/project/advanced-charging-controller

Thanks in advance for the collaboration!

Download: https://github.com/MatteCarra/AccA/releases/download/v1.0.15/app-release.apk
[Magisk] cantenna:
[MENTION=5228676]VR25[/MENTION]

You know that saying "less is more"

I love your work and mcs but acc is just too complicated and doesn't work for me as intended...

the frontend app doesn't seem to help either.

i just want to go back to a simple mcs 95 90 and be done with it.

with acc, it intermittently stops charging when above 85%. I can get it to take more charge if I quickly unplug/re-plug charger. I've disabled cool down.

would you be open to updating an old veraion of mcs from Oct 2018 to be compatible with new magsik?
[Magisk] lm089:
This is a great update, big thanks to the devs!

First impressions: love the app's new design and dark mode.

'about' page is a big help really. Only has a minor bug, at least on my op6 (oos 9.0.8): the page's 'back' arrow doesn't do anything at all, the nav bar's back button works, though. So that's cosmetic.

Will do more testing over the weekend
[Magisk] MatteCarra:
Thanks a lot for your kind words!

[MENTION=4752144]squabbi[/MENTION] had a great impact on the new design!

You are right about the back arrow in the about section.

I will fix it!

Thanks

What problems do you have with the app?

Regarding the acc issues, you should export a log and send it to vr25.
[Magisk] cantenna:
update; I've manually pushed the old magisk charging switch and have set that up, will see if my issue is resolved.

i think both the app and the module itself have evolved into a far too technical state; i think you guys should go back to mcs roots and continue the simplicity that project accorded. perhaps even maintain both projects for both kind of users.

Update2: mcs working as expected here, so Ill stick with that as I just wanted a simple charge until 95%, resume charge at 90%.
[Magisk] zputnyq:
Hi [MENTION=9731715]MatteCarra[/MENTION],

I'm new user of AccA.

So far no big problem with the latest version, only a little problem on design side, back button & home is not shown with light theme.

I want to know about notification

Is there any notification such as sound when charging stop ?
[Magisk] zgfg:
Sorry if a noob question:

I didn't have ACC Magisk module installed but installed the latest app-release.apk from Github (released half a day ago)

It asked for root privilege, granted, it popped up installing ACC, and in the GUI it's showing that Deamon is running.

However, I checked again in Magisk Manager, ACC module was not installed

So my question is, does APP work without ACC module or I must also install the module?

If both are needed, are their latest versions (module from Magisk repo) compatible?

Even if module is not required, is there an advantage to install both or they may conflict each other
[Magisk] zputnyq:
I installed the latest AccA without Acc module & It could work, charging stop at desired precentage. However I don't really know whether some function will need module or not. Probably someone who has already used it for longer time/experienced knows about it.
[Magisk] MatteCarra:
Acca does all It needs to work at first start.

No more action is required from the user.

A compatible version of acc is automatically installed and the user DOES NOT have to install it from magisk manager.

As simple as any other app :)

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

The app can very well just do that.

You should just try it.
[Magisk] ant0ni084:
Hello, since I've install ACC, my smartphone doesn't charge anymore. I really don't know how it happens and how can solve the problem. Could somebody help me please? I've a Motorola Xt1762. Thank you.
[Magisk] lm089:
Sounds interesting as my OP6 doesn't support battIdleMode (we chatted about that). But I'm not sure whether I really get the concept. From what I understand I's need to do this:

from config.txt copy the value from "chargingVoltageLimit" and set it as a new value for "chargingSwitch". Then add a default voltage and a stop voltage value.

In my case that would be

chargingSwitch=bms/constant_charge_voltage DEFAULT STOP

note: ACCA tells me that 'bms/constant_charge_voltage' is working, and I set it to 3950 mV; while charging ACCA returns a charging voltage of around 4.05 V; I assume that is somewhat "within tolerance". Right?

What I don't get is what values I should enter for DEFAULT_VOLTAGE and STOP_VOLTAGE. For DEFAULT I probably should have used my limiting value (= 3950). But what is the STOP value then?

I tried with DEFAULT = 3950 and STOP = 3500 this morning which resulted in the phone being charged to 100% instead of 80% (I set capacity to '2,101,75,80'). And yes: after making those alterations in config.txt I stopped then restarted the daemon.

Bottom line is: I assume I got this thing completely wrong...
[Magisk] afr33sl4ve:
Ah, shoot. Didn't catch this until after I jumped ship to a 1+6T.

I'll definitely install it on my 6T, seeing as the battery isn't user replaceable. I'll update as necessary.
[Magisk] lm089:
Had some time to waste over the past weekend so I re-thought what I wrote above. Started experimenting with the various voltage control files offered by ACCA; no matter what I tried, ACCA kept telling me always the same in regards to charging current / voltage. I also observed that - after setting a different file and restarting the daemon - ACCA's main battery panel would constantly switch between "status charging" and "status not charging". OK. But then after having decided to leave it at that I started to realize a *huge* battery drain; I litterally could watch the percentage values ticking down. I disabled voltage control through ACCA, completely stopped the daemon, then restarted the phone and - just to be sure - deleted all caches through TWRP. Back at system everything appeared to be normal again.

OK, lesson learned: don't fool around with that stuff if you're not 100% sure you know what you're doing :p.

But that's not the end of the story:

after havin re-enabled acc through ACCA, but voltage control still being disabled altogether I'm now observing a charging voltage of 3,95 V, and that is quite constant. I double-checked and indeed inside config.txt the setting for "chargingVoltageLimit" is empty.

Now, this is confusing me completely: while I had tried to limit voltage to 3950 mV using voltage control files ACCA always reported back values between 4.03 and 4.07 V. Now that I abandonned that I'm apparantly down where I always wanted to be. Of course I don't know how accurate that reading is in the end. But it looks as if there was a measurable difference.

How can that be?

I kind of agree with [MENTION=4778658]cantenna[/MENTION] (although I don't have a clue what you mean by 'mcs', I guess I got the idea...)
[Magisk] cantenna:
i did. but its wasn't working for me.
[Magisk] pepit0grillo:
Hi,

If I install AccA app, do I need ACC magisk module too? Does AccA include ACC module?

Regards
[Magisk] Droid_JD:
Nope. App installs the mod upon first launch.
[Magisk] alispeedsport:
Hi [MENTION=5228676]VR25[/MENTION]
[MENTION=9731715]MatteCarra[/MENTION]

Thank you for great job,

On 1.0.15v app or 2019.7.21 zip , mt6735

It was not detect charge connected.

Battery icon makes green but notify led is turn off and not charging.

Logs says not charging.

Thanks.
[Magisk] vinnievegas:
Why does it say charging fast in the app but says charging slow on lock screen?
[Magisk] zputnyq:
So there's notification ? ?

I don't get any notification.

What about sound notification when charging stop, is there any ?
[Magisk] Ixioon:
Install it on s10plus and cause boot loop so not working yet
[Magisk] G0bl1n:
Hi [MENTION=5228676]VR25[/MENTION] [MENTION=9731715]MatteCarra[/MENTION]

First of all, thanks a lot for the GREAT app, really appreciate all the features and the efforts put into the development!

What I think can still be improved:

1) If charging is set to stop say at 80% would be better to check the ">" condition and not just "=". If I manage to charge the phone to 81% (over 80% when the condition to stop is met) it will not stop chargning and will charge to 100%.

2) On my Huawei Mate 20 X the charging doesn't stop if I use fast charging. If I use the regular charging ACC works OK.

Thank you again for the great app!
[Magisk] PhonePenguin:
I have one important question, does the app install acc systemlessly? If not I'll probably have to stick with magisk module only.
[Magisk] ktmom:
I was worried about updating to ACC after seeing your post. I used MCS in Tasker for a long time, with some convoluted logic to decide how to charge depending on what I was doing with the phone.

However, I find ACC with the app to be easy to install and use. Also, all I had to do in my Tasker tasks was change "mcs" to "acc". The command line is very similar if not identical, not counting the newly added bits.
[Magisk] Audioboxer:
Pixel 3 on Android 10 with magisk.

Tried installing and using the app version and it just comes up saying "No Root". Only option is to click OK and the app closes.

I am rooted :)

edit: Installing version v1.0.15 first worked.
[Magisk] MrKapper:
So you're saying that, when you install any mod for an unsupported android version, there is a chance of your phone not behaving as expected?
[Magisk] KitsuneFoxy:
Is there a charging voltage control file for the nexus 4?

It doesnt support battery idle. And if theres no control voltage file, whats the best cool down settings?

Running android 6.1 quanta v20 kernel with 5, 60, 70-80 charge set
[Magisk] :
I am trying to use scheduling with ACCA but it doesen't work.

I set a 75% charge profile and then i schedule a 90% charge profile for the early morning, but when i wake up the phone just stays at 75% without switching profiles... Any ideas?
[Magisk] ktmom:
I'd start with making sure all battery management done by your device is off for ACC. https://dontkillmyapp.com
[Magisk] :
I'm using AospExtended on a Z5 Compact.

Also, acc works, it's only the scheduling that doesen't
[Magisk] Benik3:
Hello.

Does anyone tested ACCA on Lenovo tb3-730x?

Acca still report Discharging(unknown), current Now 1mA and Temp -1°C.

For some reason I'm not able to get logs out. The logs are not made automatically and after running acc -l -e they export to sdcard, I see them in Fx manager, but I can't open them (file not found) and in PC they are even not visible :/

There are at least standard logs

EDIT: I got the logs from /sbin/.acc
[Magisk] Benik3:
Well it looks like I will have to reinstall system, because now the tablet doesn't charge at all and even after acc uninstal :(
[Magisk] VR25:
ACC is installed as a module of the app. The Magisk module is automatically removed. For some reason, the module folder (/data/adb/modules/acc/) wasn't removed.

While there are more advanced features, the roots haven't chanced much. In fact, acc 95 90 works just like mcs 95 90.

The thing is, many issues appeared at first. These affected compatibility and user experience. Now things are much better, and I test new versions more before releases. You can see that the latest version (attached) is from September 1st - and I still haven't pushed it to the repo.

Regarding simplicity: it didn't die - at all.

If you clean install acc and make no changes to the config, you don't have to worry about extra/advanced/unwanted features. These are all disabled by default. It you want to feel just the mcs experience, only use acc 95 90 and forget about all the rest. You don't even have to read any technical stuff.

ACC is installed by the app as an AccA module. The Magisk module is automatically removed. The attached zip and future releases automatically determine the appropriate install variant. You don't have to worry about any of this. If a new acc version is up and you want it ASAP, simply upgrade from Magisk Manager - even if you're using the app.

AccA installs acc as its back-end.

Magic is real!

Isn't your charging switch still set to "voltfile default stop"?

Install the attached update from Magisk Manager.

If the problem persists, run acc --log --export and upload /sdcard/acc-logs-*.tar.bz2.

The app gets the info from acc, which in turn obtains it from the battery management system itself.

"Fast" doesn't necessarily mean fast every time. This is a kernel related thing.

That's not a notification. It's charging status within the app.

I worked on this with another S10. Install the attached version from Magisk Manager and you should be good.

1) ACC already checks for ">=" conditions.

2) Fast changing may be unstoppable.

Try the attached version.

If the issue persists, provide logs as described above.

Yes, it does install it systemlessly (/data/data/mattecarra.accapp/files/acc/).

Yes, there is a charging control file for mako. If "acc -s s:" shows you nothing, please provide logs.

I don't know if there's a voltage ctrl file for it too. Check with "acc -v :" - but upgrade to the attached version first.

Your current cool down capacity (60) is the default and what I would use myself.

There's a new version of the app (unreleased) that includes an updated schedule back-end (djs, attached) and other changes. See if upgrading djs helps. Install the attached zip from Magisk Manager. No reboot needed.

Try the attached version and provide logs as described above.
[Magisk] KapilNagpal01:
[MENTION=5228676]VR25[/MENTION] how can I make it work with OnePlus 7. I tried a lot but haven't been able to restrict voltage at 4 V, is there any alternate to control voltage in OnePlus 7. Please support. Thanks for your help in advance
[Magisk] VR25:
Charging voltage control support depends on the kernel.

If you tested "acc -v 4000" and all control files failed, your kernel doesn't support this feature.

Ask kernel devs to put their hands on it. I tried that - no updates from them for a long time. Perhaps if more people showed interest, devs would be more likely to take this "consumer rip off" issue seriously.
[Magisk] Benik3:
Thanks for the reply.

I installed attached zip with magisk and still the same (no charging).

Here are logs.

Thank you!
[Magisk] KapilNagpal01:
Thabks a million for your response. I shall try to garner support. Hope we all together can solve this rip off. Have a great day sir ?
[Magisk] alispeedsport:
[MENTION=5228676]VR25[/MENTION]

On last version 2019.0.9.10 zip , problem is still persist.

(Android mm.) log file is here:

Thanks.
[Magisk] iamjimmy:
Quick question: I have Pixel 3XL and using the latest version of the app.

The battery level displayed in the app does NOT match the Android battery %. In the ACC app, It is 10-13% lower than reported by the system. (ex: Acc app is 62% and Android says 73%).

I calibrated the battery using a software app, and it still shows different.

Lastly, I had a question about STOP and RESUME charge % in the profiles. If I have Stop at 85% and Resume at 75%. This means that the phone will NEVER charge after 85%. And it will resume charging if the battery is below 75%?

What if the battery is 78% will it charge? And what if the battery is 68% - will it charge?

I guess I'm not able to understand the meaning of "RESUME" charge. Does it mean that the battery only charges when the battery % is above the resume % or is it BELOW the resume %?

Thank so much in advance for the help.
[Magisk] ktmom:
Using an app to "calibrate" the battery is not the same as the full discharge then charge process I linked to in the other thread.

From the ACC App documentation, Troubleshooting section

From the FAQ

Think of the battery levels as trigger points. At 85%, ACC stops the battery from charging. Nothing else happens until the next trigger point is reach; at 75% resume charging.

If the last "command" was a stop charge, then a discharge cycle is started and charging will not resume until the lower set point is reached. In this case, at 78%, no, the device will not charge. However, in your example, at all times, at 68% charging will resume the next time it's plugged in (or it's put on a wireless charger).

Conversely, if the last "command" was a resume charge, but the device is not on a charger, the battery will continue to discharge until plugged in (or it's put on a wireless charger). If the device is on a charger, the charge resumes at the low set point, charges to 83% and the device is now taken off the charger, then plugged in again with the battery at 78%, yes, charging will resume. The last command was to resume charging and the device never reached the upper set point.

High set point: greater than or equal to >=

Low set point: less than or equal to =<
[Magisk] iamjimmy:
Perfect. That makes a lot of sense. I will go through full discharge cycles and try to calibrate the battery per that link.

Charge thresholds finally seem to make sense to me. So for resume charging at 75% and Stop charging at 85% - if connected to a charger then the battery will NOT charge over 85% and will not resume charging until the battery drops BELOW 75%

What if the phone is removed from the charger? So in the above example, I observed that If I remove the phone from the charger and then again connect to a charger it will charge at any batter level below 85% (Ex: 78%, 68%, 73% etc). Is that expected behaviour? I was thinking that maybe it will NOT charge if the phone is between 75% and 85%.

Finally: Last question - In the app, is it just enough to select a profile (until it turns green). Will ACC follow that even if the phone reboots? Basically I want to have one profile for home and one for the Car. Say at home, I don't want the phone to charge over 85% and in the car - I never want the phone to charge over 90%. So if I have 2 profiles for these, I can tap one for home. And then in the car I can tap the other (until it goes green). Does that work? Or is something else needed.

This is a blessing for Android Auto in cars. Previously my phone would keep on charging and go to 100%. Thanks again for helping me with my questions.
[Magisk] ktmom:
Read my post again. It's dependant on what the last command sent to ACC was.

Yes it's enough to change profiles.

Do you use Tasker? If so (and you ask for help in the Tasker forum [emoji6]), you can set tasker up to manage charging limit/resume charging based on conditions.
[Magisk] iamjimmy:
I re-read that and I think I can understand now. Just wanted to make sure I understand what "last command" exactly is. So let's say in the same charging thresholds (resume at 75% and stop at 85%).

CASE 1: If the phone is charged to 85% then removed from charger. In this case the last command is Stop Charge.

Now if the battery level discharges to 78% - I put it on the charger, the phone should NOT charge? Since the last command was stop charge and the lower threshold is not reached. Is that correct?

If the battery level is 71% (below 75%) - then the phone would charge, since it's below the lower threshold.

Case 2: If the phone is charged to 83% and then removed from charger. In this case the last command is Resume charge.

Now at any charge % - let us say at 78% - the phone will still charge until it reaches the upper threshold (of 85%) as the last command was Resume charge. Is this correct?

Sorry for the repetition. Just wanted to make sure I understand.

Thank you. I DO need to explore Tasker. Always heard great things about it, but never tried as I was afraid of it taking up system resources of bricking the phone with a mistake.
[Magisk] ktmom:
Yes, you got it.

I've been using tasker since circa 2010. Never had it be the cause of device problems. Though, it's a commitment to learn. There are plenty of written and video tutorials geared towards beginners. You just have to do the work. It's like snowboarding (water skiing? Riding a bike?), once you get it, you get it.
[Magisk] KitsuneFoxy:
Sorry for the VERY late reply to this.

I don't use Djs, But, I have installed the unreleased update.

It does have a charging control file yes. PM8921_charger.

as for voltage ctrl file this comes up after doing acc -v : it says "default" If i do the same thing with acc -v : it is just blank.

Im not sure what Default means.
[Magisk] Zaxx32:
Hello all...I'm fairly new to using a rooted phone as well as Magisk

I have a Moto G5+ on stock Oreo 8.1.

Trying to uninstall...first I deselected, rebooted then ticked uninstall icon, rebooted but ACC is still listed. Since there's no UI, I dunno if it's for sure still installed and active or turned off...or what.

Any suggestions? Like I said...I'm a 'root noob', so go easy.

My phone says it's charging to 100%...dunno if it's 'actual' or adjusted and is really 80%...:eek:
[Magisk] zputnyq:
Del
[Magisk] zack483:
Can u make AccA have a function to display battery info like temperature,charging mA, in notification drawer or a small battery info as overlay at bottom screen.. i know so many apps at playstore have this, but i dont want install multiple battery apps in my phone.
[Magisk] Mumtaz77:
This app/module is perfect to me, but brakes OTG devices. If i plug my endoscope or other device to my phone usb port, it's won't working if ACC installed.

Any suggedtion?

Honor 8 with Android 8.0
[Magisk] metaxda:
FK Kernel Manager has this function.

-- https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_AU

It's very nice to see the notification drawer, with instant statistics about battery discharge rates, battery information, etc.
[Magisk] ktmom:
It would probably help if you provided logs captured when this problem occurs. You can use an app like MatLog. Start logging, then recreate the problem with the device connecting to the phone. You can then return to MatLog and stop the recording and save the log.

Take the time to look at the resulting log yourself. You may be surprised that there is a bit of information that allows you to solve your problem.
[Magisk] El_Diabolical:
Definitely recommend installing this everyone and showing the Dev some support

,I use this as the only Battery-Related app on my ROM

Even though it's still in beta it's beastly.
[Magisk] sfairmm:
Hi guys,

I installed in Poco F1 and works very fine. My battery was unbalanced and now works fine.

Many thanks!!
[Magisk] sudanking:
I tried to upgrade to latest version, but I get this errors

My device OnePlus 7 Pro with custom kernel

View attachment 4834821View attachment 4834827
[Magisk] ktmom:
It's working fine on my rooted, stock Pixel 3XL. Maybe try pinging the domain from inside the terminal. If it fails, grabbing a logcat while doing that, may give you insight as to what's happening.
[Magisk] guest4711:
Perhaps your firewall (like AfWall) is blocking internet access for terminal/termux?
[Magisk] What a coincidence.:
Installed the Magisk version on a Nokia 3.2 two days ago, and it seems to work perfectly.

Thank you for this module. :)