yashsingh1/xdaforums huggingface dataset:
[Magisk] VR25:
Yeah, you should...

Right now, that's the best messenger overall.

Which acc version were you upgrading from?

EDIT

Nevermind, I just found out what went wrong.
[Magisk] squabbi:
Hello fellow ACCApp users! We've been working on spicing up the UI design of ACCA. Currently we've done the the Status and Battery cards.

Here's a sneak peak of the new design. Let us know your thoughts and comments. :D:good:

[IMG="ACCA New Status and Battery Card"]https://i.imgur.com/co78ytI.png[/IMG]

Currently I've worked on the ACCD status and battery details card. More to come later on!

If you want to try out this build, you must uninstall ACCA (you will lose all profiles & scheduled jobs), and then install this unofficial build of ACCA with the new UI components.

Make a backup of your existing ACCA installation via Titanium Backup or Swift Backup.

https://github.com/squabbi/AccA/releases/tag/1.0.1-u1

You can report any suggestions on GitHub (on my fork), or here. :)

If you use this build, do NOT report any issues to the main/original ACCA repo, nor about ACC.
[Magisk] bbender716:
I keep getting it unable to connect to the internet error. What am I doing wrong here?
[Magisk] nogaff:
Both cards look nice and I like the circular battery indicator.

However, with the Status card, it's not immediately obvious that you can actually tap on the card to reveal the Stop and Restart buttons. Also, when you tap the settings icon, the grey background is not vertically centred so it looks a bit weird:

I kinda feel like the options for the charging switch and the stats reset should be moved to the settings screen as well.
[Magisk] squabbi:
Good mention about that, I'm thinking of an indicator of some sorts, or another button next to the settings cog. The padding clipping issue has been sorted out already in this morning's commits.

That sounds like it makes sense, I think our settings activity will have to go through a bit of a touch-up as well, functional and just visual too.

Thanks! :good:
[Magisk] elahn:
Uninstall, reboot, install fixed that issue for me.
[Magisk] Ahugari:
Anyone having this issue: I charge up the phone in the morning, when I get home from work the phone won't charge (it starts and then completely stops - this takes less than a second). I try to restart the daemon but to no avail. I only have to restart the phone to get it to charge again. Oh, and if I just leave it for a couple of minutes to charge before the restart, it only drains the battery even more. The previous version before the latest update worked well.

Is there a way I can get the previous version back. Restarting the phone every morning cause it won't charge is not nice. Am using version 2019.2.27. Just found out there's an update.

Thanks
[Magisk] metaxda:
i get the same error too.

i have uninstalled the Magisk module, installed ACCA, got the error, uninstalled ACCA, reinstalled it...

and same following error:

"

INSTALLATION FAILED

Something went wrong while installing acc.

Please ensure that you have a working internet connection.

If you continue to see this message, please contact us on XDA

"
[Magisk] MatteCarra:
Sorry guys.

Squabbi was not supposed to release it just yet, because some commits are not compatible with current acc.

Please wait until the next version of acc is ready.

A new version with his mods to the UI will be available soon after.
[Magisk] VR25:
**2019.3.7 (201903070)**

- `acc --log` commands determine the target log file based on verbose state.

- Enhanced self-upgrade.

- Fixed instalation error faced by some users.

- Generate `/dev/acc/installed` after successful install/upgrade.

- Include version code in log files.

- New (experimental) charging switches (in `switches.txt`)

- Reduced installer verbose.

- `resetUnplugged` doesn't apply within `coolDown` loop.

- Updated documentation (mainly the troubleshooting section).

- Updated installation instructions in `install.sh` (for app developers).

- Use regular `reboot` commands instead of the unreliable `am bla bla` for system reboot and power off.

- `vNow=mV_pauseSeconds` - monitor `voltage_now` as part of `coolDown` (experimental, default: null (off)).

Enforce one charging switch (acc -s s) and test how it holds up. It's best trying the first one last.
[Magisk] MatteCarra:
Acc app has been updated too!

This version is compatible with latest and greatest acc module!

[MENTION=4752144]squabbi[/MENTION] worked on some awesome new UI parts! More to come!

Download: https://github.com/MatteCarra/AccA/releases/download/1.0.2/app-release.apk
[Magisk] paolocorpo:
Dear

Let give a look to the dimension of character

The phrases are not correctly showned

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] MatteCarra:
That's true but the settings screen is shared for creating profiles and schedules and it doesn't make sense to change it these two parameters for profiles and schedules.

I've a solution in mind.

I will think about it.

Thanks for the suggestion
[Magisk] shouk_1987:
Tried it and it is superb

Actually manufacturers should consider applying this nativly to stock roms but ofcourse they want you to change your device at the soonest while we care about battery life or time span :)
[Magisk] danicadanicadanica:
UI bug on 320 dpi
[Magisk] squabbi:
Thank you for you report! It'll be fixed in the next release. :D:good: and for yours as well [MENTION=6696306]danicadanicadanica[/MENTION] !
[Magisk] Tommytommy1234:
In the ACC 1.0.2 , any difference between the settings from the "Status" and "Profile" settings? I mean they look to do the same thing.
[Magisk] MatteCarra:
They parameters are exactly the same.

The setting icon next to "Status" changes acc parameters IMMEDIATELY.

Profiles are used to save a particular config you want to apply LATER and are used to apply the config multiple times when needed.
[Magisk] MatteCarra:
A new update of Acc app is available!

Be sure to update!

Download: https://github.com/MatteCarra/AccA/releases/download/1.0.3/app-release.apk

Changelog:

I've spent quite some time on refreshing config editor UI.

Now it's way more user friendly, nice and better organized.

I've also added on plugged option.

[MENTION=4752144]squabbi[/MENTION] fixed problems with low resolution devices in the home screen.

This version fixes a major bug when rotating the device while editing config: previously every unsaved mod was reset after rotating.

Feedback is very welcome!
[Magisk] LLoTE:
Just installed this and the app and when the daemon is running my charger makes a really weird buzzing noise and also every time the battery goes up a % it stops charging then waits a few seconds to start again can someone tell me if im doing something wrong or is this just not compatible with my phone.
[Magisk] Equals_Android:
Hey all, I just installed this module through magisk and I have a few questions. When I put my phone on charge it would disconnect and reconnect charging. Is this a feature that I can disable to stop the frequent disconnections? Thanks!

I have a Op5t and running the latest magisk module version 2019.3.7-r1
[Magisk] elahn:
In AccA, it says the charging speed is 1mA while charging at 1800mA on my Galaxy S5 (kltedv), SmartPack kernel, LineageOS 15.1.

Thank you, devs, for all your great work on acc and AccA.
[Magisk] danicadanicadanica:
Yes it always happening i really want to ask if this is normal or it is intended to be that way.
[Magisk] wilsonhlacerda:
Install the Acc App (github links on earlier posts/pages) and check its settings.

Also read OP.

Tip: cool down.
[Magisk] danicadanicadanica:
I guess temperature and cooldown setting is redundant.
[Magisk] paolocorpo:
Thanks all sounds great

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] Camerado:
[MENTION=5228676]VR25[/MENTION] At latest version: cyclic reboot if rebootOnPause is active/enabled and achieved pause capacity. After disconnecting the charger everything works as expected.
[Magisk] Tommytommy1234:
I guess that if you disable "cool down" and "temperature check" in ACC App to charge your phone constantly.
[Magisk] kenpri:
Does this work well with default settings? The model is mi 6, but is there any setting required?
[Magisk] MatteCarra:
It works well for sure, but it's very easy to customize: https://github.com/MatteCarra/AccA/releases/download/1.0.3/app-release.apk

I will fix it. Thanks
[Magisk] kenpri:
thank you for your reply. I will try it.
[Magisk] kenpri:
Dleted
[Magisk] wilsonhlacerda:
By the way, same happens on S4 running LOS 14.1. AccA (I haven't checked if it is app itself or Acc that feeds it wrongly) shows 1mA when actual current is 1000mA....1900mA and shows 0mA when actual is 460mA.....800mA.

Thanks.
[Magisk] quicktrick:
Hello! I've found this module just today. I'm trying to use it on Xiaomi Mi Mix 2S under LOS 16. Default config.

There is a strange behavior after 60% of charging on the running phone. The display wakes up about every minute and then ones again after turning to sleep. Then again it wakes up in about a minute and then just after turning to sleep. And so on.

I don't think this behavior is normal. How can I fix that?
[Magisk] MatteCarra:
Download the app and disable cool down.
[Magisk] abs0lut3z33r0:
How do i uninstall this module completely ? I uninstalled it from magisk on Oneplus 5t and the phone often does not charge unless restarted . the phone is also charging slow . how do i restore my phones default charging behaviour
[Magisk] VR25:
The module is gone already. There's nothing, but /sdcard/acc/ left. The presence of that folder and its contents doesn't interfere with charging in any way.

Instead of simply rebooting, power down your system and wait a minute before powering it up again.
[Magisk] LLoTE:
Flash boot.img again it will get rid of root and stuff but it will set everything back to normal
[Magisk] abs0lut3z33r0:
I will have to flash magisk again? How to flash boot.img using twrp?
[Magisk] LLoTE:
Well first you have to extract the boot.img from the rom zip and then just flash it trough twrp and reboot and then if you want to again just flash magisk after
[Magisk] elimiriel:
I think you might be already reported same issue with me, but my lack of search cannot find. On the HTC10 stock oreo based custom rom(I'm using Viper10 6.0.0, cleanslate kernel 3.7.14), it seems ACC runs as set. But when after the phone is fully charged(reached 'stop charging at' values), phone just act as always at the full battery when I plug chargers; it seems just draw power directly from the external power, don't recharge it's battery again before being reseted the daemon.
[Magisk] Camerado:
[MENTION=5228676]VR25[/MENTION]

Latest repository version. What I've done:

1. Disabled coolDown (set 101)

2. Enabled rebootOnPause (set 60)

3. Reboot

capacity=3,101,70-80

Other perameters not changed.

After reaching pause capacity and 60 seconds of standby the smartphone rebooted (determined by the unlock password request), but after disconnecting the charger the smartphone restarted again. Please fix it.
[Magisk] sfairmm:
Hi guys,

I use the Pocophone F1, Mi Max 3 and 2 both with MIUI 10.

Both work 100%.

Thank a lot.
[Magisk] VR25:
[MENTION=2733111]abs0lut3z33r0[/MENTION], did you solve that issue?

Could you elaborate a bit more?

What exactly is happening?

1) Battery doesn't charge unless acc daemon is restarted.

2) White plugged in, battery capacity remains constant, after the upper limit is reached.

Ok, I'll work on that.

P.S., capacity=3,101,70-80" won't do much if your battery temperature tends to reach 40°C+ (default) while charging. The best way to disable coolDown is setting it to null (acc -s coolDown).
[Magisk] elimiriel:
1 AND 2, AFTER 1st charge was done well and tried to 2nd recharge.

After fresh reboot or reset the daemon, 1st charge is ok, runs as what I set(take rest when too warm, etc). After 1st charge is full(reached stop charging at values), it draws power from charger as normal.

But after I unplugged that and used, 2nd charge just draws power like it was at 100% or 'stop charging at' values(even actual battery was near 30%), so I have to restart the daemon to charge.
[Magisk] VR25:
Intriguing... ?️

Could you reproduce that again, then share both /dev/acc/acc-daemon-* logs?

Meanwhile, what's the output of "acc -s s:"?
[Magisk] ubergeek77:
Does anyone else have a very inaccurate battery percentage in their status bar?

My statusbar currently reads 32%, but acc -i, and the AccA app, shows that the actual capacity is currently at 42%.

That's a whole 10 percent that the statusbar is off by.

I've tried resetting my battery stats and rebooting, but it seems stuck like this. I know this is a somewhat recent change (<2 weeks, probably), but I've only just realized what was going on, so I don't know exactly what caused this.

Is there anything I can do to fix the percentage indicator in my status bar?
[Magisk] elimiriel:
(I'm using it with controller app)Screenshot was the output when input the command. Names of subfolders are descriptions when I copied from the logfolder.
[Magisk] VR25:
https://github.com/MatteCarra/AccA/issues/9

Read that.
[Magisk] ubergeek77:
Ok, I think I get it. Since this only just became a problem, I'm assuming Acc switched to a more accurate measuring scheme somewhat recently. If I'm understanding this correctly:

I always had Acc set to keep my battery at around 41%. Since Acc was going off of a different measurement previously, until Acc behaved this way, I was actually keeping my battery at around 51%, since it displayed as 41% on my statusbar. Now that Acc is able to do more accurate battery readings, the actual battery is being kept at 41%, like I always wanted, but it appears as 31% due to my phone's 10% capacity difference.

Did I get that right?
[Magisk] VR25:
Yes, but the way acc works in this regard never changed. It's been displaying battery information from the same source (battery management system) since day one. Your "smart" battery may need calibration (a full discharge and recharge cycle). It may calibrate itself if you give it a reasonable break (e.g., don't use your device for a while, or use it very lightly for a longer while). It may still self-calibrate if you continue using your device normally - but this may take much longer.

Regarding the mismatched capacity readings, as you read already, in next version, you'll benefit from capacityTolerance=+10. This will essentially make acc work with and display realCapacity + 10.

P.S., setting other possibilities aside, this capacity mismatch may have to do with programmed obsolescence. :rolleyes:
[Magisk] ubergeek77:
Ok, thanks. So long as I'm doing the best for my battery, if acc is using the more accurate measurements for itself, I can live with the statusbar being incorrect.

I think you're right about planned obsolescence though. Or at the very least, this was an intentional decision by Google for some reason. My SO's Pixel 3 XL is doing exactly what mine is doing, where the status bar is off by 10%. So I think Google silently snuck this in to the March update, since that's the only explanation that makes sense to me at the moment.

I'm not sure why they did this, but I would prefer to have the more accurate battery reading there, rather than have acc pretend my battery has 10% less capacity than it normally does. Because in that case, I would really be keeping my battery at ~51%, and not ~41%, where I actually want it.
[Magisk] VR25:
Sneaky way of saying, "Get ready for the next Pixel; yours is getting old (fingers crossed). You should upgrade asap." :D
[Magisk] ubergeek77:
I'm assuming no, but are there any fancy terminal commands I can use to force the statusbar to use the correct reading?
[Magisk] svbarbosa:
Maybe naming it CapacityOffset will be more meaningful.
[Magisk] VR25:
Not that I'm aware of... ?️

Btw, could check whether "acc -i" and "dumpsys battery" commands show different battery capacity values.

Definitely...

Thanks!
[Magisk] ubergeek77:
They do!

dumpsys battery gives the same number shown in the statusbar (level: 31)

acc -i gives what is presumably the "real" capacity (CAPACITY=41)

Does this mean anything?
[Magisk] N1NJATH3ORY:
HI i can't get none of the commands to work ? For example i su first, then I type in cs –i

i get not found :( My question is, if i remove the magic charger controller from Magisk! Will it set my battery to default charging settings ? Or do i need to somehow get the commands to work first before i remove it ?

i have set charge only up to 90% that work fines! Thanks
[Magisk] Camerado:
[MENTION=5228676]VR25[/MENTION]

Default config (nothing has changed).

After reaching coolDown capacity the screen of the smartphone starts to blinking (cyclical awakening to the lock screen and the extinction). Can start at any time in the interim coolDown-pause.

After re-connecting the charger (the battery charge is in between coolDown-pause) exactly the same cyclical screen blinking.
[Magisk] ubergeek77:
In a previous comment, I let you know that acc -i and dumpsys battery produce values that do not match for whatever reason.

For reference, I'm on a Google Pixel 3 XL, and this only started happening to me since the March update. I'm nearly convinced this is either a bug or intentional measure by Google. Charging to 100 did basically nothing (it actually made things worse, the difference is now 12% less for me instead of 10% less)

Since then, I found out you can force the status bar battery level to match the actual battery level by running this command:

dumpsys battery set level $(cat /sys/class/power_supply/battery/capacity)

However, the number will stick if you do this. The command will have to be run frequently in order to keep the status bar battery level accurate. Otherwise, it will just stay at that level, presumably until the battery depletes.

To undo that change, you can issue:

dumpsys battery reset

The battery level will drop down to the "false" value.

In order to combat Google lying to us about our battery level, would it be possible to have accd periodically set the battery level via dumpsys? This would be an extremely welcome change. It's extremely frustrating to lose 10%-12% of usable capacity, especially since I keep my battery at 41% or less at all times. This gives me way less breathing room in terms of usable power, since I only have 29% of battery to work with instead of 41%.

Having accd "fix" this would prevent you from having to set a battery level offset like previously proposed, since the battery level would always be up to date according to the values in /sys/class/power_supply. This could of course be something that is disabled by default. If the accd daemon is ever disabled, the reset command can be issued before it is disabled. Or perhaps even more cleanly, this functionality can be moved to djs.

I hope this helps improve development. I'm losing my mind trying to get my battery level to be "correct," so having this in accd would make me, and I'm sure plenty of others, very happy.
[Magisk] Meisterchef:
Hi there [MENTION=5228676]VR25[/MENTION] (:

acc is not working for me when screen goes off. No led flashing and no warm on the back. I checked also the status with accubattery, no charging since 10 minutes and accu is on normal temperature so no cooldown is required.

I also used the 2 available switches I get. Not working. I disabled aggresive doze in greenify.

Device is redmi note 4 (mido). Los 15.1 - oreo. franco custom kernel.

Anyway - thank you
[Magisk] Demodroid:
My Note 4 works fine on stock Lineage kernel. Try reinstalling acc.
[Magisk] Meisterchef:
I did it three times^^
[Magisk] Demodroid:
Did you delete the config file as well?
[Magisk] Meisterchef:
Yes
[Magisk] skyfighter:
Hello all! I've just decided to try acc on my new Xiaomi Mi Mix 2S (running MIUI Global Stable v10.2.2.0.PDGMIXM) (after using Charge Battery Limit for a long time on other devices).

Installed acc via MagiskManager followed by a reboot. Connecting the phone to a charger lead to weird behaviour: It charged for around one minute, stopped charging for a few seconds, began to charge again for around one minute, stopped charging for a few seconds and so on...looked like a infinite loop to me. Just disabled coolDown (acc -s coolDown) and the loop is gone (read that on the last pages).

Is this charging start-stop loop an intended result of the coolDown Feature? Does "coolDown=50/10 # Charge/pause ratio (in seconds)" mean acc tries to charge for 50 seconds, then interrupts charging for 10 seconds and so on?

When does acc apply the coolDown-config-rule (I guess only if battery level is above the second parameter of the capacity-config-rule)? Okay, got it - coolDown starts (by default) at 60% and slows down charging by stopping charging for 10secs every 50secs. That my device turns on its display and plays a notification sound (each time charging is switched off or on) is probably device-dependant... might have a look at the suggested switches over here.

And another question: tried to run "acc -v :" to get a list of the available charging voltage control files, but I'm just getting a "grep: /data/media/0/acc/logs/acc-power_supply-*.log: No such file or directory". I've read somewhere that acc should be reinstalled (in this case), but even after

a) removing magisk module, rebooting, reinstalling module, rebooting and

b) just install the ZIP again (via MagiskManager -> Module -> +-Button)

there are no files under /sdcard/acc/logs/ (the directory is empty). (Although I can't see any errors in the Magisk Install-logs.) Anything else I could try?
[Magisk] skyfighter:
Thanks to the penultimate line of the Magisk InstallLog-Copy I've found the missing acc-power_supply-*.log under /data:

mv: can't rename '/data/acc-power_supply-polaris.log': Operation not permitted

***EXIT 0***

...copied it to /sdcard/acc/logs/ and "acc -v :" seems to be happy:

polaris:/ # acc -v :
./pc_port/voltage_max
./main/voltage_max
./usb/voltage_max
./battery/voltage_max
./bms/constant_charge_voltage
./parallel/voltage_max

I have no clue why the move at install time failed...installed the module multiple times and all Magisk-Install-Logs show the same last two lines. :confused:
[Magisk] jeezygarceezy:
Voltage control on OP6?

Sorry to post this question, but I read through a lot of the thread and couldn't find a definitive answer.

Does this allow limiting the voltage on a OP6?

Thanks!
[Magisk] guest4711:
Try it yourself and report your findings here so others could find your answer.

BTW it also depends on your kernel (not only on your device) wether it works or not...
[Magisk] jeezygarceezy:
it doesn't on a stock kernel, in case anyone is wondering. capacity and temp controls work though, so that's cool.
[Magisk] guest4711:
Thanks for reporting. So other users of an OP6 may find the info.
[Magisk] skyfighter:
battery stats

Is it possible to disable the automatic reset of the battery stats (when it reaches maxCapacity% and acc disables charging)? I'd like to have a look at the stats after 2-3 days (= prevent acc temporarily from resetting the stats) and couldn't find a way to achieve that.