Search This thread

bmwbasti

Senior Member
Apr 29, 2011
379
44
I can't tell for sure, but it seems to work.
I've set the voltage to 4000mV but when I start charging ACC only shows a current of like 20mA and so the battery seems to get more empty instead of fuller while charging 😁.
 

amn1987

Senior Member
I can't tell for sure, but it seems to work.
I've set the voltage to 4000mV but when I start charging ACC only shows a current of like 20mA and so the battery seems to get more empty instead of fuller while charging 😁.
Do you mean you were getting 20mA without tweaking the max. charging current? That maybe possible if it was close to the max. charging level as per the 4V setting and it was in the tapering phase. Temporarily stop using ACC or any other app to manually stop charging and check.
If bypass charging is working in Ampere app it should show status as "Full" and "AC Charger" for Plugged state when battery has stopped charging. In F1 it certainly works as the built-in battery charge cycle counter has recorded only 8 charge cycles in the last 20 days(0.4/day) since I enabled bypass charging whereas previously the daily average over the last 20 months was 1.1. Also battery charge has never dropped once "fully" charged and plugged in.
I have now got rid of ACC, BCL etc and only use Terminal commands in Tasker to enforce voltage limit at every boot as it gets reset after booting. Don't need to specify a max. battery charge level as voltage takes care of that. Temps. are much better and rarely cross 40°C which was pretty common earlier.
 

Attachments

  • Screenshot_20210611-092803940.jpg
    Screenshot_20210611-092803940.jpg
    210.1 KB · Views: 38
  • Screenshot_20210611-092915309.jpg
    Screenshot_20210611-092915309.jpg
    202.4 KB · Views: 37

stavrosbin

Member
Mar 14, 2019
29
1
Xiaomi Poco F3
Guys I am a first timer here so I have a couple of questions about this module:
1. If let's say I let it charge through the night, will it stop charging after reaching the max %?
2. If I change anything from the app, would I need to restart my phone?
 

Zilla0617

Senior Member
Oct 25, 2016
149
39
Google Pixel 4 XL
Do you mean you were getting 20mA without tweaking the max. charging current? That maybe possible if it was close to the max. charging level as per the 4V setting and it was in the tapering phase. Temporarily stop using ACC or any other app to manually stop charging and check.
If bypass charging is working in Ampere app it should show status as "Full" and "AC Charger" for Plugged state when battery has stopped charging. In F1 it certainly works as the built-in battery charge cycle counter has recorded only 8 charge cycles in the last 20 days(0.4/day) since I enabled bypass charging whereas previously the daily average over the last 20 months was 1.1. Also battery charge has never dropped once "fully" charged and plugged in.
I have now got rid of ACC, BCL etc and only use Terminal commands in Tasker to enforce voltage limit at every boot as it gets reset after booting. Don't need to specify a max. battery charge level as voltage takes care of that. Temps. are much better and rarely cross 40°C which was pretty common earlier.
Is bypass charging the same as battery charge idle? If so, I selected the switch that supports it on my phone (Pixel 4xl). However, when it reaches my set max (80%), Ampere reads discharging not full.
 

amn1987

Senior Member
Is bypass charging the same as battery charge idle? If so, I selected the switch that supports it on my phone (Pixel 4xl). However, when it reaches my set max (80%), Ampere reads discharging not full.
They sound similar but I am not 100% sure. ACC still reports battery idle not working in my F1 despite bypassing charging AFAICT amply supported by the daily average cycle count falling to one-third of the original rate.
 

bmwbasti

Senior Member
Apr 29, 2011
379
44
I'm wondering, it anyone of the devs (or someone with knowledge of the application) is ever watching the thread🤔.

I don't know why but I can save as often as I want but after every charge the options for charging switch seems to get reset to "automatic" and "cycle through switches automatic" and I don't want that.
I found out that only the "charging enable 0 1" seems to correctly transmit the "battery is charged" command.
 

ricky56789

Member
Feb 24, 2011
45
10
Working again on Pixel 5 June update with EX kernel 1.07. Had to manually select sys/kernel/debug/google_charger/input_suspend 0 1 from the list, didn't work on automatic.
 

amn1987

Senior Member
How do I setup bypass charging on my Pixel 4xl?
Dunno. You have to hunt for the correct control file if it exists. In my Xiaomi devices tweaking the value in voltage_max located in sys/class/power_supply/battery does the trick. I have set it to 4V which causes charging to stop at ~70%. And if it works ACC, BCL and the like won't be needed. In fact they can actually prevent bypass charging from being triggered. I had limited max. charging voltage since the update to Q early last year but only found out how to enable bypass charging in the last month.
 
Last edited:
  • Like
Reactions: Zilla0617

skyfighter

Member
Jan 31, 2007
39
4
@amn1987
Your hints regarding "bypass charging" are very interesting - I'll definately try that! Do you happen to know:
When the bypass charging kicks-in and you do not disconnect the device from the charger: is the device still kept awake? This should be easily visible in the Details-View of the Android Battery stats. (Both of my xiaomi devices are kept awake even after charging is disabled via battery/input_suspend switch. Probably because auf wake-locks which are issued as soon as the devices get connected to a charger but don't get removed when charging is manually stopped tampering the kernel-parameters.)
 
  • Like
Reactions: amn1987

amn1987

Senior Member
Dunno. In my Xiaomi devices tweaking the value in voltage_max located in sys/class/power_supply/battery does the trick. I have set it to 4V which causes charging to stop at ~70%.

@amn1987
Your hints regarding "bypass charging" are very interesting - I'll definately try that! Do you happen to know:
When the bypass charging kicks-in and you do not disconnect the device from the charger: is the device still kept awake? This should be easily visible in the Details-View of the Android Battery stats. (Both of my xiaomi devices are kept awake even after charging is disabled via battery/input_suspend switch. Probably because auf wake-locks which are issued as soon as the devices get connected to a charger but don't get removed when charging is manually stopped tampering the kernel-parameters.)
No. Deep Sleep is always in the High nineties... despite which overnight idle drain is just ordinary. In bypass charging the device itself reports battery as fully charged. So I guess these wakelocks don't occur. By default bypass charging did work but only at 100% previously. The charging switch is the same in case of my Poco F1.
 
Last edited:

skyfighter

Member
Jan 31, 2007
39
4
[...] In bypass charging the device itself reports battery as fully charged. [...]
So the whole device/Android-OS switches from "charging" to "normal" mode (e.g. no green battery icon and no power-/thunder-icon in status bar)!?
...then it looks like I'm out of luck regarding bypass charging - at least in case of my first attempt @ Poco F3 (alioth) running rooted OEM-ROM (MIUI EEA v12.0.5.0.RKHEUXM , Android 11). It simply kept showing all signs of "Charging-Mode" (e.g. green battery icon with power-/thunder-icon in status bar), even some time after the charging current dropped <= 20mA (according to AccuBattery App).

Here is what I did:
1) stop accd ("accd.")
2) check kernel parameters for default values ("date ; uptime ; acc -i")
3) limit charging voltage to 4V ("echo 4000000 >/sys/class/power_supply/battery/voltage_max")
4) connect device to charger
5) occasionally capture "acc -i" ouptut

Comparing the "acc -i" ouputs of my test shows a few changing values:
CHARGE_TYPE=Fast ---> CHARGE_TYPE=Taper
CAPACITY=28 --> CAPACITY=41 --> CAPACITY=64 --> CAPACITY=65
TIME_TO_FULL_NOW=10995 --> TIME_TO_FULL_NOW=8228 --> TIME_TO_FULL_NOW=1385 --> TIME_TO_FULL_NOW=1
...but sadly this one never changed (which probably explains why the Android-OS still claimed "charging"-mode):
STATUS=Charging

That are the last two "acc -i" ouputs before disconnecting the charger:
Code:
:/sdcard # date ; acc -i
Sun Jun 13 01:19:55 CEST 2021

Battery Service
  AC powered: true
  USB powered: false
  Wireless powered: false
  Max charging current: 1150000
  Max charging voltage: 5000000
  Charge counter: 4632430
  status: 2
  health: 2
  present: true
  level: 64
  scale: 100
  voltage: 4001
  temperature: 255
  technology: Li-poly

Uevent
  INPUT_SUSPEND=0
  BATTERY_INPUT_SUSPEND=0
  STATUS=Charging
  HEALTH=Good
  PRESENT=1
  CHARGE_TYPE=Taper
  CAPACITY=64
  CHARGER_TEMP=274
  CHARGER_TEMP_MAX=800
  INPUT_CURRENT_LIMITED=0
  VOLTAGE_NOW=4001454
  VOLTAGE_MAX=4000000
  VOLTAGE_QNOVO=-22
  CURRENT_NOW=-146972
  CURRENT_QNOVO=-22
  CONSTANT_CHARGE_CURRENT_MAX=6000000
  CONSTANT_CHARGE_CURRENT=6000000
  CHARGE_TERM_CURRENT=-220
  TEMP=255
  TECHNOLOGY=Li-poly
  STEP_CHARGING_ENABLED=0
  SW_JEITA_ENABLED=1
  CHARGE_DONE=0
  PARALLEL_DISABLE=0
  SET_SHIP_MODE=0
  DIE_HEALTH=Cool
  DC_THERMAL_LEVELS=0
  RERUN_AICL=0
  DP_DM=0
  CHARGE_CONTROL_LIMIT_MAX=16
  CHARGE_CONTROL_LIMIT=0
  CHARGE_COUNTER=4632430
  CYCLE_COUNT=11
  RECHARGE_SOC=99
  RECHARGE_VBAT=-22
  NIGHT_CHARGING=0
  CHARGE_FULL=4609000
  FORCE_RECHARGE=0
  CHARGE_FULL_DESIGN=4520000
  TIME_TO_FULL_NOW=1385
  FCC_STEPPER_ENABLE=0
  BATTERY_CHARGING_ENABLED=1
  DP_DM_BQ=0
  TYPE_RECHECK=341
  WARM_FAKE_CHARGING=0
  STEP_VFLOAT_INDEX=0
  CAPACITY_LEVEL=Normal

  CURRENT_NOW=-0.146972 Amps
  VOLTAGE_NOW=4.00145 Volts
  POWER_NOW=-0.588101 Watts

:/sdcard #
Code:
:/sdcard # date ; acc -i
Sun Jun 13 01:55:46 CEST 2021

Battery Service
  AC powered: true
  USB powered: false
  Wireless powered: false
  Max charging current: 1150000
  Max charging voltage: 5000000
  Charge counter: 2766321
  status: 2
  health: 2
  present: true
  level: 65
  scale: 100
  voltage: 3999
  temperature: 255
  technology: Li-poly

Uevent
  INPUT_SUSPEND=0
  BATTERY_INPUT_SUSPEND=0
  STATUS=Charging
  HEALTH=Good
  PRESENT=1
  CHARGE_TYPE=Taper
  CAPACITY=65
  CHARGER_TEMP=271
  CHARGER_TEMP_MAX=800
  INPUT_CURRENT_LIMITED=0
  VOLTAGE_NOW=3999989
  VOLTAGE_MAX=4000000
  VOLTAGE_QNOVO=-22
  CURRENT_NOW=-38574
  CURRENT_QNOVO=-22
  CONSTANT_CHARGE_CURRENT_MAX=6000000
  CONSTANT_CHARGE_CURRENT=6000000
  CHARGE_TERM_CURRENT=-220
  TEMP=255
  TECHNOLOGY=Li-poly
  STEP_CHARGING_ENABLED=0
  SW_JEITA_ENABLED=1
  CHARGE_DONE=0
  PARALLEL_DISABLE=0
  SET_SHIP_MODE=0
  DIE_HEALTH=Cool
  DC_THERMAL_LEVELS=0
  RERUN_AICL=0
  DP_DM=0
  CHARGE_CONTROL_LIMIT_MAX=16
  CHARGE_CONTROL_LIMIT=0
  CHARGE_COUNTER=2766332
  CYCLE_COUNT=11
  RECHARGE_SOC=99
  RECHARGE_VBAT=-22
  NIGHT_CHARGING=0
  CHARGE_FULL=4609000
  FORCE_RECHARGE=0
  CHARGE_FULL_DESIGN=4520000
  TIME_TO_FULL_NOW=1
  FCC_STEPPER_ENABLE=0
  BATTERY_CHARGING_ENABLED=1
  DP_DM_BQ=0
  TYPE_RECHECK=341
  WARM_FAKE_CHARGING=0
  STEP_VFLOAT_INDEX=0
  CAPACITY_LEVEL=Normal

  CURRENT_NOW=-0.038574 Amps
  VOLTAGE_NOW=3.99999 Volts
  POWER_NOW=-0.154296 Watts

:/sdcard #

I guess leaving the device connected to charger over night / multiple days is not a good idea - at least if does not stop charging and keeps staying in this "Taper"-charging-mode (perhaps some kind of "conservation charge")!?

Anything I could try regarding bypass charging?
 
  • Like
Reactions: amn1987

amn1987

Senior Member
So the whole device/Android-OS switches from "charging" to "normal" mode (e.g. no green battery icon and no power-/thunder-icon in status bar)!?
...then it looks like I'm out of luck regarding bypass charging - at least in case of my first attempt @ Poco F3 (alioth) running rooted OEM-ROM (MIUI EEA v12.0.5.0.RKHEUXM , Android 11). It simply kept showing all signs of "Charging-Mode" (e.g. green battery icon with power-/thunder-icon in status bar), even some time after the charging current dropped <= 20mA (according to AccuBattery App).

Here is what I did:
1) stop accd ("accd.")
2) check kernel parameters for default values ("date ; uptime ; acc -i")
3) limit charging voltage to 4V ("echo 4000000 >/sys/class/power_supply/battery/voltage_max")
4) connect device to charger
5) occasionally capture "acc -i" ouptut

Comparing the "acc -i" ouputs of my test shows a few changing values:
CHARGE_TYPE=Fast ---> CHARGE_TYPE=Taper
CAPACITY=28 --> CAPACITY=41 --> CAPACITY=64 --> CAPACITY=65
TIME_TO_FULL_NOW=10995 --> TIME_TO_FULL_NOW=8228 --> TIME_TO_FULL_NOW=1385 --> TIME_TO_FULL_NOW=1
...but sadly this one never changed (which probably explains why the Android-OS still claimed "charging"-mode):
STATUS=Charging

That are the last two "acc -i" ouputs before disconnecting the charger:
Code:
:/sdcard # date ; acc -i
Sun Jun 13 01:19:55 CEST 2021

Battery Service
  AC powered: true
  USB powered: false
  Wireless powered: false
  Max charging current: 1150000
  Max charging voltage: 5000000
  Charge counter: 4632430
  status: 2
  health: 2
  present: true
  level: 64
  scale: 100
  voltage: 4001
  temperature: 255
  technology: Li-poly

Uevent
  INPUT_SUSPEND=0
  BATTERY_INPUT_SUSPEND=0
  STATUS=Charging
  HEALTH=Good
  PRESENT=1
  CHARGE_TYPE=Taper
  CAPACITY=64
  CHARGER_TEMP=274
  CHARGER_TEMP_MAX=800
  INPUT_CURRENT_LIMITED=0
  VOLTAGE_NOW=4001454
  VOLTAGE_MAX=4000000
  VOLTAGE_QNOVO=-22
  CURRENT_NOW=-146972
  CURRENT_QNOVO=-22
  CONSTANT_CHARGE_CURRENT_MAX=6000000
  CONSTANT_CHARGE_CURRENT=6000000
  CHARGE_TERM_CURRENT=-220
  TEMP=255
  TECHNOLOGY=Li-poly
  STEP_CHARGING_ENABLED=0
  SW_JEITA_ENABLED=1
  CHARGE_DONE=0
  PARALLEL_DISABLE=0
  SET_SHIP_MODE=0
  DIE_HEALTH=Cool
  DC_THERMAL_LEVELS=0
  RERUN_AICL=0
  DP_DM=0
  CHARGE_CONTROL_LIMIT_MAX=16
  CHARGE_CONTROL_LIMIT=0
  CHARGE_COUNTER=4632430
  CYCLE_COUNT=11
  RECHARGE_SOC=99
  RECHARGE_VBAT=-22
  NIGHT_CHARGING=0
  CHARGE_FULL=4609000
  FORCE_RECHARGE=0
  CHARGE_FULL_DESIGN=4520000
  TIME_TO_FULL_NOW=1385
  FCC_STEPPER_ENABLE=0
  BATTERY_CHARGING_ENABLED=1
  DP_DM_BQ=0
  TYPE_RECHECK=341
  WARM_FAKE_CHARGING=0
  STEP_VFLOAT_INDEX=0
  CAPACITY_LEVEL=Normal

  CURRENT_NOW=-0.146972 Amps
  VOLTAGE_NOW=4.00145 Volts
  POWER_NOW=-0.588101 Watts

:/sdcard #
Code:
:/sdcard # date ; acc -i
Sun Jun 13 01:55:46 CEST 2021

Battery Service
  AC powered: true
  USB powered: false
  Wireless powered: false
  Max charging current: 1150000
  Max charging voltage: 5000000
  Charge counter: 2766321
  status: 2
  health: 2
  present: true
  level: 65
  scale: 100
  voltage: 3999
  temperature: 255
  technology: Li-poly

Uevent
  INPUT_SUSPEND=0
  BATTERY_INPUT_SUSPEND=0
  STATUS=Charging
  HEALTH=Good
  PRESENT=1
  CHARGE_TYPE=Taper
  CAPACITY=65
  CHARGER_TEMP=271
  CHARGER_TEMP_MAX=800
  INPUT_CURRENT_LIMITED=0
  VOLTAGE_NOW=3999989
  VOLTAGE_MAX=4000000
  VOLTAGE_QNOVO=-22
  CURRENT_NOW=-38574
  CURRENT_QNOVO=-22
  CONSTANT_CHARGE_CURRENT_MAX=6000000
  CONSTANT_CHARGE_CURRENT=6000000
  CHARGE_TERM_CURRENT=-220
  TEMP=255
  TECHNOLOGY=Li-poly
  STEP_CHARGING_ENABLED=0
  SW_JEITA_ENABLED=1
  CHARGE_DONE=0
  PARALLEL_DISABLE=0
  SET_SHIP_MODE=0
  DIE_HEALTH=Cool
  DC_THERMAL_LEVELS=0
  RERUN_AICL=0
  DP_DM=0
  CHARGE_CONTROL_LIMIT_MAX=16
  CHARGE_CONTROL_LIMIT=0
  CHARGE_COUNTER=2766332
  CYCLE_COUNT=11
  RECHARGE_SOC=99
  RECHARGE_VBAT=-22
  NIGHT_CHARGING=0
  CHARGE_FULL=4609000
  FORCE_RECHARGE=0
  CHARGE_FULL_DESIGN=4520000
  TIME_TO_FULL_NOW=1
  FCC_STEPPER_ENABLE=0
  BATTERY_CHARGING_ENABLED=1
  DP_DM_BQ=0
  TYPE_RECHECK=341
  WARM_FAKE_CHARGING=0
  STEP_VFLOAT_INDEX=0
  CAPACITY_LEVEL=Normal

  CURRENT_NOW=-0.038574 Amps
  VOLTAGE_NOW=3.99999 Volts
  POWER_NOW=-0.154296 Watts

:/sdcard #

I guess leaving the device connected to charger over night / multiple days is not a good idea - at least if does not stop charging and keeps staying in this "Taper"-charging-mode (perhaps some kind of "conservation charge")!?

Anything I could try regarding bypass charging?
Remove ACC altogether and then check. Also first check if signs of bypass charging are present or not when left to sit at 100% for sometime or not. Could be MIUI to blame as well although I think that's not very likely. I don't use MIUI in any of my Xiaomi devices.
In my case the OS reports as fully charged but the charging symbol in the Statusbar persists and the battery charging LED is turned on always, probably as it's still drawing power from the charger. It doesn't denote battery charging alone is it? Similar behavior w.r.t. The charging symbol is exhibited by my Redmi devices in which bypass charging worked from the beginning w/o having to limit voltage.
FKM reports 0mA. Ampere as "Full". Also the battery cycle count has only increased by 8 since 22nd May, only 36% of the previous daily average. Also battery temps. are much better than before, despite being plugged in all day except when I am off to sleep, even compared to earlier when I had limited current to 20-40mA (anything lower didn't work and battery actually discharged by 1-2% a few times) and voltage to 4.1-4.15V but was also limiting battery charge level in Tasker which prevented bypass charging to kick in. Battery percentage doesn't drop at all. Voltage and temp. don't increase as well. If this isn't bypass charging then I have no clue.
 

Attachments

  • Screenshot_20210613-132457882.jpg
    Screenshot_20210613-132457882.jpg
    203.9 KB · Views: 19
  • Screenshot_20210613-132633234.jpg
    Screenshot_20210613-132633234.jpg
    278.3 KB · Views: 22
  • Screenshot_20210613-132250251.jpg
    Screenshot_20210613-132250251.jpg
    514.1 KB · Views: 21
  • Screenshot_20210613-132446166.jpg
    Screenshot_20210613-132446166.jpg
    210 KB · Views: 21
  • Screenshot_20210613-132641791.jpg
    Screenshot_20210613-132641791.jpg
    902.5 KB · Views: 19
Last edited:
  • Like
Reactions: skyfighter

skyfighter

Member
Jan 31, 2007
39
4
@amn1987
Your arguments sound plausible - thank you very much for the details! May I ask which ROM and Kernel you are using?

I'll disable the AAC Magisk-Module, reboot and do further tests in the next days... Let's see who laughs last - the damn charging logic/electronics or me. :)
 
  • Like
Reactions: amn1987

amn1987

Senior Member
@amn1987
Your arguments sound plausible - thank you very much for the details! May I ask which ROM and Kernel you are using?

I'll disable the AAC Magisk-Module, reboot and do further tests in the next days... Let's see who laughs last - the damn charging logic/electronics or me. :)
I have only ever used crDroid in my F1 except for a very brief dalliance with a couple of other ROMs. And since last year the stock OD kernel. I just wished I had stumbled across this sooner as that would have helped reduce greatly the reduction in battery capacity with usage. Currently it goes down 10% for every 300 cycles or so.
Edit: The file permissions for voltage_max get reset after every boot. Tasker can take care of that.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hello there.
    I just want to ask two questions.

    How can I get to the Therminal command list and detailed descriptions?


    How can I learn the health and other values of the battery.?
    Its usually located in sys/class/power_supply/battery. The file named "uevent" shows a boat load of details including battery cycle count if supported, max. and current charging voltage and charging current, original and current battery capacity, the charging control file in use etc.
    1
    Elleriniz
    Its usually located in sys/class/power_supply/battery. The file named "uevent" shows a boat load of details including battery cycle count if supported, max. and current charging voltage and charging current, original and current battery capacity, the charging control file in use etc.
    Don't be sick at all. Thank you.
    I want to ask one last question.
    My phone is Xiaomi Mi10 UMI.
    Designed battery capacity 4780mAh.
    It's been 1 year. I bought the device 1 year ago. Now the battery information is as follows.

    142 charging cycles.
    Maximum battery capacity with 4281mah.
    Healt looks good.


    It cannot be doal that my device's battery capacity is so low. This is ridiculous.
    I was using Iphone 8 Plus. The battery capacity was 83% in 2.8 years. Charging Cycle 500.

    Can this be a calculation error?
    I don't know how to calibrate the battery. Does it improve after battery calibration?
    How is the battery calibration done if possible? Can you tell me? So much to me
    1
    @amn1987
    I really can't tell you. I don't ever use quickchargers, as I still own some pretty "old" or "low-voltaged" charging adapters.
    So to say I really never use the chargers provided in the box.
    And I don't own a device to measure charging voltage.
    I don't know if there is a way to test it?
    1
    @amn1987
    I really can't tell you. I don't ever use quickchargers, as I still own some pretty "old" or "low-voltaged" charging adapters.
    So to say I really never use the chargers provided in the box.
    And I don't own a device to measure charging voltage.
    I don't know if there is a way to test it?
    If you have rooted the device it's pretty easy to accomplish all of that. Just a matter of tweaking the right control files as long as it exists and the ROM and/or kernel allow modifications.
    I am using the stock 18W charger but I have limited max. charging current and voltage to 1.6A and 4V respectively. In fact charging current can be reduced to as low as 20mA but occasionally the battery level dropped 1-2% even when plugged in. But just by limiting the max. charging voltage and not using any app to limit charging level, bypass charging is triggered when the peak voltage is reached. This is the best way although ACC still reports that battery idle mode isn't supported. Doesn't really matter anyway.
    1
    @amn1987
    I think you got me wrong 😉.
    You asked me, if it's possible for the Poco F3 to reduce voltage and current and I answered that I don't know how to test it.
    So what's the way to test it? Set some kind of low current and voltage and watch if charging takes longer 🤔?
    If limiting voltage really works then for ex. at 4V the device would stop charging at just under 70%. In my Xiaomi devices tweaking the value in voltage_max located in sys/class/power_supply/battery does the trick. Thereafter the OS should report battery as fully charged because that's how it infers it albeit at close to 4.4V normally.
  • 235
    Documentation (stable version)

    Documentation (beta version)

    Power Supply Logs - Help Needed

    Releases

    ACC App (AccA)

    XDA:DevDB Information
    Advanced Charging Controller (acc), Tool/Utility for the XDA Community Apps

    Contributors
    VR25
    Source Code: [url]https://github.com/VR-25/acc/[/URL]


    Version Information
    Status: Stable
    Current Stable Version: 2020.6.16
    Stable Release Date: 2020-06-16

    Created 2017-10-16
    Last Updated 2020-06-16
    73
    Archive
    Find newer zips here.
    40
    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.