Advanced Charging Controller (acc)

Search This thread
By:
Advanced…
W

wolfenstein3de

Senior Member
Feb 27, 2014
76
9
Kraków
Hello, does anybody have any idea how to set ACCA so it won't show charging icon, when connected&not charging? I would like to see to be able to check when the phone has stopped charging during the night, exactly.
 
gorilla p

gorilla p

Recognized Contributor
Nov 30, 2011
3,698
2,854
STL
Xiaomi Mi Pad 4
OnePlus Nord N10 5G
gorilla p said:
Running initial test on wireless charger provided
:/ $ su :/ # acc --test (!) Charger must be plugged to continue... (i) Alright, this may take a minute or so... (!) [/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/mmi_charging_enable 1 0] won't work :/ #
Click to expand...
Click to collapse
After latest update, I now get
[/sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/mmi_charging_enable 1 0] works
- battIdleMode=false

Will see how it works tonight
 
A

Ascii3

Senior Member
Sep 17, 2015
230
66
VR25 said:
Unfortunately, Android is a mess when it comes to standards.
Only a handful of devices/kernels actually offer fairly well defined intefaces for those features.
Nonetheless, I'm exploring ways of abstracting as many control interfaces as possible.
Keep an eye on release changelogs.
Click to expand...
Click to collapse
I shall keep an occasional watch for the changes.

VR25 said:
Meanwhile, as workarounds, you can disable/enable charging on demand with acc -d and acc -e, respectivelly - and limit the max charging current to 500 mA.
Click to expand...
Click to collapse
Thanks. Right now disabling and enabling online charging manually is what I oftentimes do.
 
gorilla p

gorilla p

Recognized Contributor
Nov 30, 2011
3,698
2,854
STL
Xiaomi Mi Pad 4
OnePlus Nord N10 5G
VR25 said:
That's one of the recently discovered charging switches.
There might be more, according to the output of acc -p.
Click to expand...
Click to collapse
Acc -p came back with the following. Wireless charging is still charging to 100%. Seeing if latest update helped.
Code: 
:/ $ su
:/ # acc -p

/sys/class/qcom-battery/moisture_detection_en 0 1
battery/hwmon4/waiting_for_supplier 0 1
battery/cycle_count 0 1
battery/waiting_for_supplier 0 1
wireless/hwmon7/waiting_for_supplier 0 1
wireless/waiting_for_supplier 0 1
usb/hwmon6/in0_input 0 1
usb/hwmon6/waiting_for_supplier 0 1
usb/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/camera_on 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/ship_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/cycle_count 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/battery_notify_code 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/deviated 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/trx_power_vol 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/rx_power 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/adapter_type 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/factory_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/tx_power 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/fod_cal 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/trx_power_en 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/quiet_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/adapter_sid 0 1/sys/devices/virtual/devlink/f000000.pinctrl--soc:qcom,pmic_glink:qcom,battery_charger:oplus,pm8350b_typec/sync_state_only 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:qcom,pmic_glink:qcom,battery_charger:oplus,pm8350b_typec/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:oplus,chg_intf:oplus,wireless-charge/sync_state_only 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:oplus,chg_intf:oplus,wireless-charge/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:oplus,chg_intf:oplus,wireless-charge/sync_state_only 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:oplus,chg_intf:oplus,wireless-charge/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:qcom,pmic_glink:qcom,battery_charger/sync_state_only 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:qcom,pmic_glink:qcom,battery_charger/waiting_for_supplier 0 1
/proc/charger/hmac 1 0
/proc/charger/passedchg_reset_count 0 1
/proc/tbatt_pwroff 1 0
/proc/touchpanel/charge_detect 0 1
/proc/touchpanel/wireless_charge_detect 1 0

:/ #
 
G

Gibsonflyingv

Senior Member
Jul 28, 2011
378
62
I'm curious if anyone has had success with this on the Pixel 6. I read this on the acc github but I'm not sure how to make use of that in the configuration (I'm a noob with this module/config app).

It mentions:
Code: 
/sys/devices/platform/google,charger/charge_start_level:100
/sys/devices/platform/google,charger/charge_stop_level:0

I'm confused on how to create the commands to set this up. It's clearly a "acc -s" command, but where does the "charger/charge_start_level:100" go? I'm assuming "/sys/devices/platform/google" is the switch file?
 
Last edited:
  • Like
Reactions: zee3are0
VR25

VR25

Senior Member
Apr 20, 2013
2,015
4,932
github.com
You ca
gorilla p said:
Acc -p came back with the following. Wireless charging is still charging to 100%. Seeing if latest update helped.
Code: 
:/ $ su
:/ # acc -p

/sys/class/qcom-battery/moisture_detection_en 0 1
battery/hwmon4/waiting_for_supplier 0 1
battery/cycle_count 0 1
battery/waiting_for_supplier 0 1
wireless/hwmon7/waiting_for_supplier 0 1
wireless/waiting_for_supplier 0 1
usb/hwmon6/in0_input 0 1
usb/hwmon6/waiting_for_supplier 0 1
usb/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/camera_on 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/ship_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,common-charge/oplus_chg/common/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/cycle_count 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/oplus_chg/battery/battery_notify_code 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/deviated 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/trx_power_vol 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/rx_power 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/adapter_type 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/factory_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/waiting_for_supplier 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/tx_power 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/fod_cal 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/trx_power_en 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/quiet_mode 0 1
/sys/devices/platform/soc/soc:oplus,chg_intf/soc:oplus,chg_intf:oplus,wireless-charge/oplus_chg/wireless/adapter_sid 0 1/sys/devices/virtual/devlink/f000000.pinctrl--soc:qcom,pmic_glink:qcom,battery_charger:oplus,pm8350b_typec/sync_state_only 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:qcom,pmic_glink:qcom,battery_charger:oplus,pm8350b_typec/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:oplus,chg_intf:oplus,wireless-charge/sync_state_only 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:oplus,chg_intf:oplus,wireless-charge/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:oplus,chg_intf:oplus,wireless-charge/sync_state_only 0 1
/sys/devices/virtual/devlink/f000000.pinctrl--soc:oplus,chg_intf:oplus,wireless-charge/waiting_for_supplier 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:qcom,pmic_glink:qcom,battery_charger/sync_state_only 0 1
/sys/devices/virtual/devlink/c440000.qcom,spmi:qcom,pm8350c@2:pinctrl@8800--soc:qcom,pmic_glink:qcom,battery_charger/waiting_for_supplier 0 1
/proc/charger/hmac 1 0
/proc/charger/passedchg_reset_count 0 1
/proc/tbatt_pwroff 1 0
/proc/touchpanel/charge_detect 0 1
/proc/touchpanel/wireless_charge_detect 1 0

:/ #
Click to expand...
Click to collapse
You can place those lines into a file (e.g., acc -p /sdcard/my-list.txt) and run acc -t /path/to/file to test all.
Perhaps you may want to filter the output a bit - i.e., remove lines that don't remotely resemble a charging switch.
Sometimes, certain lines may trigger a reboot. ACC remebers to skip those next time, so that one can continue testing by simply running the same command again until all lines get tested.
 
  • Like
Reactions: duttyend
VR25

VR25

Senior Member
Apr 20, 2013
2,015
4,932
github.com
Gibsonflyingv said:
I'm curious if anyone has had success with this on the Pixel 6. I read this on the acc github but I'm not sure how to make use of that in the configuration (I'm a noob with this module/config app).

It mentions:
Code: 
/sys/devices/platform/google,charger/charge_start_level:100
/sys/devices/platform/google,charger/charge_stop_level:0

I'm confused on how to create the commands to set this up. It's clearly a "acc -s" command, but where does the "charger/charge_start_level:100" go? I'm assuming "/sys/devices/platform/google" is the switch file?
Click to expand...
Click to collapse

zee3are0 et al.,​


I've been experimenting with botth.
So far, those control files seem to behave very inconsistently.
Perhaps Google released non-production quality software.
Have you tried the current/voltage approaches? (Readme > tips > idle mode and alternatives)


Anyway, here's how to test and and set those two switches:


1. /sys/devices/platform/google,charger/charge_stop_level and /sys/devices/platform/google,charger/charge_start_level

Test: acc -t /sys/devices/platform/google,charger/charge_stop_level 100 5 /sys/devices/platform/google,charger/charge_start_level 0 95

Set: acc -s s="/sys/devices/platform/google,charger/charge_stop_level 100 5 /sys/devices/platform/google,charger/charge_start_level 0 95"


2. Just /sys/devices/platform/google,charger/charge_stop_level

Test: acc -t /sys/devices/platform/google,charger/charge_stop_level 100 5

Set: acc -s s="/sys/devices/platform/google,charger/charge_stop_level 100 5"
 
  • Like
Reactions: duttyend, zee3are0 and Gibsonflyingv
Darth Bidder

Darth Bidder

Senior Member
May 11, 2017
185
39
Xiaomi Redmi 7
Redmi Note 12 4G
Should I update the Magisk module even though I'm using the AccA or should I only update the AccA through the apk?
Last update for AccA was from a few months ago while the Magisk module was just last updated back in the 1st week of November.
 
VR25

VR25

Senior Member
Apr 20, 2013
2,015
4,932
github.com
Darth Bidder said:
Should I update the Magisk module even though I'm using the AccA or should I only update the AccA through the apk?
Last update for AccA was from a few months ago while the Magisk module was just last updated back in the 1st week of November.
Click to expand...
Click to collapse
The general rule of thumb is updating things only if you absolutelly need to.
Don't fix what's not broken.

That's not to discourage anyone.
Being a bit adventurous won't hurt.
I don't intruduce breakng changes without notice.
Besides, acc has a rollback feature - acc -b command reverts everthing (including the config) - no reboot required.
 
  • Like
Reactions: duttyend and beeshyams
gorilla p

gorilla p

Recognized Contributor
Nov 30, 2011
3,698
2,854
STL
Xiaomi Mi Pad 4
OnePlus Nord N10 5G
VR25 said:
You ca

You can place those lines into a file (e.g., acc -p /sdcard/my-list.txt) and run acc -t /path/to/file to test all.
Perhaps you may want to filter the output a bit - i.e., remove lines that don't remotely resemble a charging switch.
Sometimes, certain lines may trigger a reboot. ACC remebers to skip those next time, so that one can continue testing by simply running the same command again until all lines get tested.
Click to expand...
Click to collapse
After testing, I found the following 2 reporting "works" on my OP9.

sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/chg_enable 1 0

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0

For each, I entered acc -ss /path/to/switchabove.

Ill see of it works nay better.
 
Last edited:
VR25

VR25

Senior Member
Apr 20, 2013
2,015
4,932
github.com
gorilla p said:
After testing, I found the following 2 reporting "works" on my OP9.

sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/chg_enable 1 0

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0

For each, I entered acc -ss /path/to/switchabove.

Ill see of it works nay better.
Click to expand...
Click to collapse
To set switches, run acc --set charging_switch="file on off file2 on off --"

As you can see, more than one switch can be set at once, but most of the time, one is enough. The trailing " --" ensures the switch is not unset if it fails (i.e., prevents falling back to "automatic")

acc --set charging_switch= can be shortened for faster typing: acc -s s=
 
  • Like
Reactions: gorilla p and duttyend
gorilla p

gorilla p

Recognized Contributor
Nov 30, 2011
3,698
2,854
STL
Xiaomi Mi Pad 4
OnePlus Nord N10 5G
VR25 said:
To set switches, run acc --set charging_switch="file on off file2 on off --"

As you can see, more than one switch can be set at once, but most of the time, one is enough. The trailing " --" ensures the switch is not unset if it fails (i.e., prevents falling back to "automatic")

acc --set charging_switch= can be shortened for faster typing: acc -s s=
Click to expand...
Click to collapse
Ran again with a better usb charger and found another working switch. Applied first and third. Now Daemon is back to stopping while charging. Both with battery idle mode=true cause the daemon to stop almost immediately after starting charging.
I tried the one with battery idle mode=false and the profile didnt work. It didnt throtttle charging or enable cooldown and kept charging past the set threshold of 90%.

/sys/devices/platform/soc/soc:eek:plus,chg_intf/oplus_chg/battery/chg_enable 1 0

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/chg_enable 1 0 works
- battIdleMode=false

/sys/devices/platform/soc/soc:eek:plus,chg_intf/soc:eek:plus,chg_intf:eek:plus,wireless-charge/oplus_chg/wireless/batt_chg_enable 1 0]
works
- battIdleMode=true
 
Last edited:
A

Alaunus

Senior Member
Jan 25, 2015
68
26
Hello everyone!

I've got a Galaxy M21

After installing ACC, I used the setting "acc 3920" but for some reason the values do not set to 3920/3870 but to 3920/3820.

Is this change a bug or something made on purpose? If it's on purpose, why is a 100mv difference better than 50mv?

Is there a list of known charging witches which support idle mode?
 
Last edited:
You must log in or register to reply here.

Similar threads

T
  • Sticky
Magisk General Support / Discussion
Replies
58K
Views
6M
P
pndwal
Jaymin.0.1910
[Magisk][System] Battery Life Extender
Replies
922
Views
161K
O
okotzak
K
  • Poll
[MODULE] LKT - Insane Battery Life | Fast | Buttery Smooth ?
Replies
1K
Views
407K
A
andray750
T
  • Locked
[CLOSED][DEV] Magisk Canary Channel - Bleeding Edge Builds
Replies
3K
Views
738K
FerryAr
FerryAr
Didgeridoohan
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
Replies
7K
Views
1M
T
_tyler_

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 2
    Uluru25
    Uluru25
    Macro to write some values like batt. temperature, charging current, charging voltage, batt. percentage, selected acc-config parameters, etc. to a. txt file during charging

    This post is an update to a previous post here, providing a MacroDroid macro to monitor during charging some related parameters over the time depending on the respective acc settings.

    If you want to use the macro, download it, rename it to .macro and import it. It will start automatically when the charger is plugged.

    First, read the explanations already given here.

    Then, see the long comment at the very end of the macro, trying to explain the used variables and which / how to modify.

    Since I haven't logged all changes I made since the last release, the following summary might be too long / too short, sorry:

    - different output directory can be defined in the variable

    - output directory is created if not already present

    - macro checks if charging follows the config or follows an acc -f command

    - even for a charging following an acc -f xx -s yy command the defined values (like target capacity xx or additional limits defined in the yy term) are reported

    - variables to be reported can be (dis-)activated in the array variable

    - loop to repeat reading of charging voltage if reading was not successful

    - configurable warning if charging was started but macro has detected that acc daemon is not running

    - configurable auto-activation of acc daemon if if charging was started but macro has detected that acc daemon is not running

    😉
    View
    1
    A
    alnosr
    Hello,

    I woud like to use acc to bypass battery, so that the phone runs off the charger instead of the battery, to conserve it's life esperance.
    I do stuff that makes my battery runs very hot, I thought with this method since it bypass the charger I could not only reduce the temperature, but also reducing the number of cycle.
    I have a motorola 40 edge pro phone, which do posses that "bypass battery" functionnality. It's called "Battery optimisation" under motorola stock rom, and basically, it learns your phone charging pattern, so that when you plug in at night, it charges only up to 80%, and use the charger to run the phone (I could tell because it's constantly 0mAH in accubattery). Then, when you're supposed to wake up, it charges till 100%. Thefore the functionnality is indeed present, but do not allow much user control.

    Anyway, I'm trying to reproduce that through acc. At first, even the basic core functionality didn't work for me, I had to switch to switch 1. Now it's fine, but I still can't get battery idle (the 0mAH ) to work.
    I tried emulated "idle mode", but I feel it's not very satisfactory? I set acc 65 64, and what it does it that it simply charge to 65, discharge to 64, and continusly. Considering my usage (let's say gaming), does that makes any difference from just running on battery to 30% and then charging to 60%? Basically a lot of small cycle vs a bigger one (but not as big as 100 0), the impact on the battery should be quite similar? Also, when running high CPU usage process, the battery does get hot. But then, even with small cycles, I'm still charging it therefore increasing temperature?

    Would like your opinion on that please, also if you have any idea how to make idle battery work (since my phone does support the functionnality), I would also be very happy to hear your feedbacks.

    Thank you !
    View
    1
    Uluru25
    Uluru25
    O. K.
    I would have recommended you
    1) deinstall all front-ends
    2) update in the terminal via acc -u -f dev
    3) try if it works
    🤠
    View
    1
    A
    alnosr
    Thanks for the link. Just installed, still can't get true idle mode to work :/ only one switch with has battery idle=true, I selected that one but then I still get the continuous discharge and not 0mah.
    View
    1
    Uluru25
    Uluru25
    ACC- Front-End // Your help is appreciated!

    I have made (for fun) a MacroDroid* based front-end for ACC and consider to make it available for others who are interested.
    Before doing so, I would need two or three guys for testing to get feedback how the front-end works on other devices than mine.

    You should:
    - have already some experience with configuring ACC via the terminal
    - have no issues with your actual ACC configuration
    - have installed the MacroDroid app (or are willing to do so which requires to grant root access** to it) - Pro-version is not needed

    edit:
    * take note that Jamie, the developer of MacroDroid, is also an XDA member having an own thread for MacroDroid
    **if granting root access is a concern for you: root is needed since MacroDroid has to pass acc commands to the shell as ACC does (which also requires root as you know 😁); however internet access of MacroDroid can be prohibited with a firewall (e. g. AFWall+) and is nevertheless working fine.

    If this fits and if you want to help me, please send me a private message.

    Features of the Front-End:
    - read / modify most acc variables (30+)
    - directly see the default values
    - get dev's help text for the acc variables
    - backup / restore your config
    - return to default config
    - background / manual acc update checks
    - direct upgrade / rollback of acc builds
    - start / stop the daemon (idle mode)
    - enhanced one-time charging (acc -f)
    - add / modify /delete time profiles
    - test / set all or selected charg. switches
    - (de-)activate selected charg. switches
    - get static / dynamic (dis-)charging info
    - show full / filtered config info
    - create full / short acc logs
    - execute pasted terminal commands
    - write outputs / results into files
    - define directories for output writings

    🤠
    View
  • 280
    VR25
    VR25
    Repository
    Source Code and Documentation
    Releases

    Front-ends (outdated -- no longer supported)
    ACC App (AccA)
    ACC Settings
    View
    79
    VR25
    VR25
    Archive
    Find newer zips here.
    View
    55
    VR25
    VR25
    **Releases**
    View
    41
    VR25
    VR25
    Those who are worried about other projects of mine not being updated for a long time, possibly abandoned...
    Stop worrying.
    After the next stable ACC release, I'll focus more on the other Magisk modules (fbind, Migrator, Systemless GApps, etc.).
    The current ACC framework is the base of all the other projects - meaning, making it rock stable it priority #0.
    View
    29
    VR25
    VR25
    A new stable release is up.
    It can be downloaded from Magisk Manager > Downloads as well.
    Refer to the readme for a full list of changes, features and recommendations.
    Now I'll be focusing more on the other projects (migrator, fbind, systemless GApps, daily job scheduler...).
    Until these reach satisfactory status, acc will only get occasional maintenance updates (bugfixes, optimizations, new charging control files...).

    Edit: the installer enforced by Magisk Manager is not playing nice with acc. Until I fix that, use the zip from GitHub (release link above).

    Edit 2: fixed.
    View

New posts