Search This thread

Zaxx32

Senior Member
Mar 23, 2019
510
195
Morgantown
Moto G5 Plus
Moto G7
Use the latest pre-release.
I have the P6a and otherwise the same setup, it works just fine.
Test charging switches then set it with acc -ss.
The "main charger some number 0" and "usb some number 0" work the best for me.
I'd recommend to use them over the similar ones that have another number instead of the 0 as those appear to sometimes support Idle mode and Idle mode is just kinda wanky.
I can share my AccA config if you want.
I also have the P6a...I'd be interested in checkin' out your AccA config. Wish I understood the inner workings of the P6a battery maint. & charging etc. and didn't need a frontend app...:rolleyes:
 

mwahahaa

Senior Member
Jun 27, 2015
156
36
Google Pixel 4a 5G
Google Pixel 7
try using a switch that doesnt support Idle mode, as well as setting "prioritize_batt_idle_mode=false" in config.
usb/current_max <number> 0 or main charger/current_max <number> 0 don't support Idle mode for me and work on my P6a.
Then I won't have access to idle mode! I like that feature because it keeps my charge level right at the peak set point and puts less strain on the battery. I suppose a compromise has to be made.
 

G5-User7080

Senior Member
May 31, 2018
124
32
Then I won't have access to idle mode! I like that feature because it keeps my charge level right at the peak set point and puts less strain on the battery. I suppose a compromise has to be made.
from my experience Idle mode doesn't really work anyway.
When I tried it it kept slowly charging or discharging my phone over a few hours anyway.
If you don't use your phone and just have it sitting on usb it's better to disconnect it anyway, it seems like being connected to usb prevents the cpu to go in sleep state so the battery drains a lot faster when connected to usb than when it's disconnected.
 

G5-User7080

Senior Member
May 31, 2018
124
32
I also have the P6a...I'd be interested in checkin' out your AccA config. Wish I understood the inner workings of the P6a battery maint. & charging etc. and didn't need a frontend app...:rolleyes:
Thats my acc config, set with using f.e. acc -s cooldown_capacity=101.
You can leave most things on default, you only need to set the ones marked with a # (the # is not normally part of the config).
Set cooldown_capacity to 101 to disable it, max_temp works independently from that.

For your charging switches, first run acc in elevated adb shell, then select the "test charging switches" option, then exit the interactive menu and run acc -ss and it should display a bunch of switches that work with that charger.
The ones mentioned in my previous post should work well for the P6a.
Type in the number to apply the one you want and then restart acc, either with acc and then 4th option or in AccA.
Whenever you switch your charger (e.g. from wall charger to pc) you need to change your charging switch accordingly, so re-run the test and select one that works, they'll probably be similar, but f.e. for charging from usb pc its usb/current_max 900000 0 for me but usb/current_max 1500000 0 when I connect it to my powerbank.

max_charging_voltage depends on how far you wanna charge it, the charging voltage obviously needs to be higher than the voltage of the battery in order to charge it, so if you put in 4100 you probably can't charge it further than 65% - 70% ish.
If you use a voltage for your pause_capacity (e.g. 3980) then max_charging_voltage doesnt matter as it will stop when the charging voltage reaches the pause_capacity value.
If you use a percentage, e.g. 60% then you can limit the max_charging_voltage and you'll be able to see the current drop and charging slow down after it hits the max_charging_voltage. And charging will eventually stop completely when the difference between the battery voltage and the charging voltage is too low, so set your max_charging_voltage accordingly.
I use 4100 cause for some reason the real charging voltage appears to be 20mv below that, so 4080mV which is about what it would reach on its own at 58% battery level. And I have it set to stop charging at 63%, normally it would be at about 4100mV - 4120mV at that percentage, but since it's limited to 4080mV it'll just charge a little slower at the lower voltage. If I didn't set the pause_capacity to 63% it would probably stop at 65-70% anyway.

For more details refer to the acc github https://github.com/VR-25/acc#default-configuration
Code:
bluejay:/ # acc -s

amp_factor=
batt_status_workaround=true

capacity_mask=false
capacity_sync=auto

#cooldown_capacity=101
#cooldown_charge=
#cooldown_current=
#cooldown_pause=
#cooldown_temp=35

current_workaround=false
discharge_polarity=+
force_off=false
idle_threshold=40
lang=en

#max_temp=30
#max_temp_pause=90

off_mid=true
#pause_capacity=60
#prioritize_batt_idle_mode=false
reboot_resume=false

reset_batt_stats_on_pause=false
reset_batt_stats_on_plug=false
reset_batt_stats_on_unplug=false

#resume_capacity=45
#shutdown_capacity=15
#shutdown_temp=45
temp_level=0
volt_factor=

apply_on_boot=

apply_on_plug=

batt_status_override=

#charging_switch=usb/current_max 900000 0

cooldown_custom=

#max_charging_current=1000

#max_charging_voltage=4100

run_cmd_on_pause=

loop_cmd=

You can just import those profiles, but you might want to change the uid and profileName, so they don't double with your existing profiles.
Also since you probably use a different charger you should test your charging switches in adb shell acc and select one that works for you.

Code:
[{"profile":{"uid":6,"profileName":"3960","accConfig":{"configCapacity":{"shutdown":15,"resume":44,"pause":4080},"configVoltage":{"max":4120},"configCurrMax":1000,"configTemperature":{"coolDownTemperature":35,"maxTemperature":30,"pause":90},"configResetUnplugged":false,"configResetBsOnPause":false,"configChargeSwitch":"usb/current_max 900000 0","configIsAutomaticSwitchingEnabled":true,"prioritizeBatteryIdleMode":false}},"mIsChecked":true},{"profile":{"uid":4,"profileName":"4000","accConfig":{"configCapacity":{"shutdown":15,"resume":42,"pause":63},"configVoltage":{"max":4080},"configCurrMax":1000,"configTemperature":{"coolDownTemperature":35,"maxTemperature":30,"pause":90},"configResetUnplugged":false,"configResetBsOnPause":false,"configChargeSwitch":"usb/current_max 900000 0","configIsAutomaticSwitchingEnabled":true,"prioritizeBatteryIdleMode":false}},"mIsChecked":true}]
 

mwahahaa

Senior Member
Jun 27, 2015
156
36
Google Pixel 4a 5G
Google Pixel 7
from my experience Idle mode doesn't really work anyway.
When I tried it it kept slowly charging or discharging my phone over a few hours anyway.
If you don't use your phone and just have it sitting on usb it's better to disconnect it anyway, it seems like being connected to usb prevents the cpu to go in sleep state so the battery drains a lot faster when connected to usb than when it's disconnected.
Idle mode actually works perfectly for me. Ever since I found the right switch I wake with my phone at the top level of the charge range, when previously I would often find the phone had drifted down close to the bottom range after reaching peak charge. The down side apparently is that it causes my phone screen to keep turning on periodically, which means I can't use my wireless charging stand at night. That's something I can live with I suppose.
 

bizkit_120

Senior Member
Feb 4, 2014
110
16
Set stop at 70% , checking charging history in the morning, it didn't stop but switch to very slow speed charging. Tested 3days in a row,same results.

Does anyone know why and how to resolve this?

OnePlus 9 oos13 stock ROM and kernel

View attachment 5851791

Logs look good,daemon is running
.View attachment 5851815
Case dismissed... damn it..after a month, I finally figured out my att wireless charger is the culprit.. 😑😑😑

Everything works fine now after switched to another wireless charger... 👍

P.S. OnePlus 9 stock oos13
 

kiwigi

Senior Member
Oct 4, 2012
183
26
LineageOS
Google Pixel 6
Use the latest pre-release.
I have the P6a and otherwise the same setup, it works just fine.
Test charging switches then set it with acc -ss.
The "main charger some number 0" and "usb some number 0" work the best for me.
I'd recommend to use them over the similar ones that have another number instead of the 0 as those appear to sometimes support Idle mode and Idle mode is just kinda wanky.
I can share my AccA config if you want.
Thanks @G5-User7080 for your feedback. I will reinstall and follow your suggestion within the next few days.
 

angus6969

Senior Member
Nov 10, 2010
53
8
For me not working properly on oneplus 8t aicp 17.1. Stop charging at set value but it continues to hold the charge at that value even if it should recover from 50%. Any ideas
 

TAirForce

Member
Aug 25, 2012
7
1
OnePlus 5T
Hello,

I have a OnePlus Nord which was recently updated to Android 12. Since than ACC doesn't work. Even though I set the limit at 80%, the phone charges up to a 100% every night.
I'm using the latest dev version. I'll attach the logs. Thanks very much for your help!

Marton

I have a OnePlus 7T and I'm facing the same issue after updating to android 12. Have you got an answer?
 

vip5912

Senior Member
Jun 20, 2017
187
137
My config for acc on Samsung S4 (I9505) with Optimized LineageOS 19.1:
Code:
chargingSwitch=(battery/batt_slate_mode 0 1 --)
applyOnBoot=(/sys/kernel/fast_charge/force_fast_charge::2::1 /sys/kernel/fast_charge/failsafe::1::0)
applyOnPlug=()
maxChargingCurrent=(1000 /sys/kernel/fast_charge/ac_charge_level::1000::1900 /sys/kernel/fast_charge/usb_charge_level::1000::1600)
maxChargingVoltage=()
 

guglicap

Senior Member
Apr 1, 2017
185
45
OnePlus 6
I have a OnePlus 7T and I'm facing the same issue after updating to android 12. Have you got an answer?
Hi!
Not OP but I also have a OnePlus Nord. I also don't have acc installed yet (was actually trying to find out if it has issues on this phone before using it) but I noticed in Settings -> Battery -> Advanced Settings there is a switch labeled something like "Optimized Night Charging". Maybe you could try disabling that? Assuming you have it and it is enabled.
Let me know if you get it to work, thanks!
 

gamer1987fla

Member
Jan 24, 2023
47
0
I use ACC Setings for battery charge control but when I connect the smartphone to the charger after a few seconds the charger disconnects from the smartphone and I replug it to charge up to 100% is this some ACC Setings or magisk configuration problem? do they have some setting that is causing this?

i uninstall acc settings and problem solved more i need acc settings

i use redmi note 7 arrowos 12.1
 

iamthechickengod

Senior Member
Jan 12, 2011
62
1
OnePlus 7T Pro
ASUS ZenFone 8
I use ACC Setings for battery charge control but when I connect the smartphone to the charger after a few seconds the charger disconnects from the smartphone and I replug it to charge up to 100% is this some ACC Setings or magisk configuration problem? do they have some setting that is causing this?

i uninstall acc settings and problem solved more i need acc settings

i use redmi note 7 arrowos 12.1
This happens to me on my OP 7TPro when I use the original charger. Try using a different generic charger. I estimate this is because the charge is controlled by the charger and not the battery management chip on the phone.
 

gamer1987fla

Member
Jan 24, 2023
47
0
This happens to me on my OP 7TPro when I use the original charger. Try using a different generic charger. I estimate this is because the charge is controlled by the charger and not the battery management chip on the phone.
I use the original charger and I've used several usb cables it's the best and I wanted to solve this problem but I need to use ACC Settings without this problem

if i uninstall accsettings the problem disappears

ACCA has no smartphone shutdown setting at 30%
 

iamthechickengod

Senior Member
Jan 12, 2011
62
1
OnePlus 7T Pro
ASUS ZenFone 8
I use the original charger and I've used several usb cables it's the best and I wanted to solve this problem but I need to use ACC Settings without this problem

if i uninstall accsettings the problem disappears

ACCA has no smartphone shutdown setting at 30%
Try a different generic charger.

You can edit the shutdown percentage in ACCA. I don't use ACC settings do I can't provide more information about it.
 

gamer1987fla

Member
Jan 24, 2023
47
0
Try a different generic charger.

You can edit the shutdown percentage in ACCA. I don't use ACC settings do I can't provide more information about it.
generic chargers are unreliable reduce battery life or may expose manufacturer recommend only original charger

ACCA in the shutdown configuration appears at a maximum of 20% does not appear 34% is it possible to insert 34% in the ACCA configurations?

Does ACCA have the same behavior as stopping charging at start?
 

Uluru25

Senior Member
Nov 27, 2016
443
194
Samsung Galaxy S7
Samsung Galaxy A6
generic chargers are unreliable reduce battery life or may expose manufacturer recommend only original charger

ACCA in the shutdown configuration appears at a maximum of 20% does not appear 34% is it possible to insert 34% in the ACCA configurations?

Does ACCA have the same behavior as stopping charging at start?
Try editing the config.txt (in /data/adb/vr25/accu-data) directly via a root file manager as shown in the screenshot. My value is 5 so change it to 34.
 

Attachments

  • Screenshot_20230330-071630_Trebuchet_1.png
    Screenshot_20230330-071630_Trebuchet_1.png
    367.4 KB · Views: 32
  • Like
Reactions: iamthechickengod

gamer1987fla

Member
Jan 24, 2023
47
0
Try editing the config.txt (in /data/adb/vr25/accu-data) directly via a root file manager as shown in the screenshot. My value is 5 so change it to 34.
is ACC module magisk or ACCA app? what app i download for modifications? Is it possible to perform this procedure on the PC and then transfer it to the smartphone?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Just a heads up for everyone - ACC(A) works perfectly for me with kernelsu (a kernel based rooting system which, in my view, is better than Magisk)
    2
    Hello Folks,

    I have a cheap wireless charger. No issue with my Mi 10 : I put my Mi 10 on the wireless charger in the evening and then it's 100% charged in the morning.

    I ve just fixed my LG V50.
    Last night I put my V50 on the wireless charger. It got charged 100% in about an hour or a little more but then the wireless charger automatically turned itself off and then in the morning I had only 88% of charge in my V50.
    I think acc can help me get a higher charge when I wake up in the morning after about 8 hours of charge. Like for example set the ampere limit to 100ma when the charge is above 90-91% (the usual amperage with the charger is about 900ma) so that the charger will keep charging but very slowly and I should have like 95-96% of charge in the morning ...

    What do you folks think ??

    Anybody got a similar issue/need ?? I would appreciate some help if somebody has a solution/an idea :) thanks !!


    EDIT : SOLVED (I Think) :

    Just set acc to charge until 99% so that "my V50 won't ask the wireless charger to turn off"
    and to resume charging below 98% so that it will charge above 98%

    and it seems to work : when the charge reaches 99% :
    • the wireless charger won't turn off and it seems to consume about 2.1W (about 4.5W before) and charges intermittently according to the charge indication displayed on the lock/standby screen (I am on Corvus ROM). The AccA app also tells me that my phone is on WiPower but is not charging.
    • I guess if the charge ever goes lower than 98% the charge will start again ...
    that was easier than I thought ;) ... good tool ! thanks !

    (I will report if I was wrong)
    ... but you know that charging to 100 % and recharging at 98 % is not at all the behaviour acc was developed for?
    Most acc users aim to extent the lifespan of their battery by avoiding to charge their phone to elevated levels (i. e. higher than 70 or 75 %) and to prevent too frequent re-chargings as well as too deep dischargings (i. e. below about 20 %).

    If you want to read more, you can visit acc dev's homepage with very valuable info or start here.
    🤠
    2
    I know. Currently I'm on Alpha but planning some change when back from work. Btw official or Thestrechh ?
    Official, but Nick uses Stretch tree I believe
    2
    Hi all. I hope you wouldn't reply RTFM 😉

    I am using an older acc that was included by default when I installed AccA from F-droid. The front end mostly works but I also have issues with OP5T 'dumpling' and Xiaomi 'sweet'.

    Now I've got another 'sweet' device and wanted to try the newest acc, that I found on GitHub.
    I am reading https://github.com/VR-25/acc#readme for the second time and still not sure.

    1. Is there any other/recommended front end apart from AccA?
    2. Can I flash the newest acc .zip file from Github in Magisk and then install Acca from F-droid? Will that work?

    PS.
    PC with Linux Ubuntu, ADB, and Fastboot working. Devices rooted with Magisk 26.1

    Any advice is appreciated.
    Here's the latest front end app, which also hasn't been updated in a while. https://github.com/CrazyBoyFeng/AccSettings

    I'd experiment with different builds of ACC though, I've had better compatibility on some devices with older builds than newer ones.

    If I remember correctly, acca installs it's bundled acc version upon install, however, it also gives you the option to use different builds of the mod. Be aware of which version you flash, and if you use acca, make sure you select that version in the settings. The other app, acc settings, I do not believe has the ability to select and flash different versions of the mod, it'll just use whichever is installed.

    Hope that helps!
    2
    No. If you want to use Acca as frontend, install it. Then flash via Magisk the newest acc.zip. Your acca frontend will recognize the new version of acc.
    Surely, I would recommend you to use the terminal commands and not the frontend.
  • 77
    Archive
    Find newer zips here.
    41
    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.
    29
    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.