• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

VR25

Senior Member
Apr 20, 2013
1,864
4,570
github.com
Archive
Find newer zips here.
 

Attachments

  • mcs-2018.10.11-beta.zip
    25.8 KB · Views: 2,485
  • mcs-2018.10.12-beta.zip
    25.8 KB · Views: 222
  • mcs-2018.10.12.1-beta.zip
    25.8 KB · Views: 576
  • mcs-2018.11.5-beta.zip
    27.5 KB · Views: 180
  • mcs-2018.11.7-beta.zip
    27.6 KB · Views: 113
  • mcs-2018.11.8-beta.zip
    27.6 KB · Views: 90
  • mcs-2018.11.8.1-beta.zip
    27.5 KB · Views: 127
  • mcs-2018.11.9-beta.zip
    28 KB · Views: 108
  • mcs-2018.11.10-beta.zip
    28.9 KB · Views: 129
  • mcs-2018.11.12-beta.zip
    28.9 KB · Views: 146
  • mcs-2018.11.13-beta.zip
    28.8 KB · Views: 144
  • mcs-2018.11.15-beta.zip
    29.1 KB · Views: 295
  • mcs-2018.11.22-beta.zip
    29.6 KB · Views: 156
  • mcs-2018.11.23-beta.zip
    30.8 KB · Views: 238
  • mcs-2018.11.24-beta.zip
    31.3 KB · Views: 2,850
  • acc-2019.1.24.zip
    32.8 KB · Views: 1,475
  • acc-201902270.zip
    57.9 KB · Views: 334
  • acc-201903031.zip
    58.8 KB · Views: 274
  • acc-201903070.zip
    59.7 KB · Views: 385
  • acc-201903071.zip
    59.7 KB · Views: 8,723
Last edited:

VR25

Senior Member
Apr 20, 2013
1,864
4,570
github.com
nice that someone else knows how li ion works for once too, the question is, does the board have this feature already baked in a little bit, is there any over provisioning of the battery?
Not sure what the exact number is. What I can say is some devices have it (mine does, obviously). You have to test and see whether the switch works on yours.

About over provisioning...
I believe indeed there is (at least in modern batteries); otherwise, these would last much less.
 

Nitram08

Member
Mar 30, 2015
23
7
Not sure what the exact number is. What I can say is some devices have it (mine does, obviously). You have to test and see whether the switch works on yours.

About over provisioning...
I believe indeed there is (at least in modern batteries); otherwise, these would last much less.
Hello! With your module you can program the load at night, so that it will charge up to 50% and after 2 or 3 hours it will charge the other 50%?

Enviado desde mi MI 5s Plus mediante Tapatalk
 

Kimbo82

Senior Member
May 23, 2013
374
120
Stockholm
Thanks for this module. Will future update add the option to erase battery statistics?

Sent from my Nexus 6P using Tapatalk
 

VR25

Senior Member
Apr 20, 2013
1,864
4,570
github.com
Great module but i don't know how to install and change settings.

Thx
You use a terminal emulator for that. Instructions are on the README (from the OP or zip file). I always try to make everything as simple and user friendly as possible. Note that the terminal must be running (either in foreground or background) till the process is complete. I recommend Termux terminal emulator.

Hello! With your module you can program the load at night, so that it will charge up to 50% and after 2 or 3 hours it will charge the other 50%?

Enviado desde mi MI 5s Plus mediante Tapatalk
Interesting idea...
That's not currently one of the features, but I can implement it. Wait for the next version.

Thanks for this module. Will future update add the option to erase battery statistics?
Sure. I can add that too.
 

Loader009

Senior Member
Jul 6, 2012
711
198
There was a command in android for checking battery status and stop charging. But, and that's the point, as soon as charging has been stopped manually, the battery status won't be updated.
If you reset it (so it charges again), the battery status is also updated.

Does this tool have the same behavior or are we able to stop charging while the battery status is still being updated?
 

phantom146

Senior Member
Apr 30, 2015
1,081
1,127
Malabon
@VR25
It seems that my terminal cant recognize the command cs or any other commands for this app. Succesfully flashed with no errors..

Also, I'm waiting for erase of battery statistics when charged to desired % atm keep doing a good job.. hope it functions on my magisk soon

EDIT: was able to make it function but I manually copied "cs" to /system/bin /xbin to make it work.
 
Last edited:

Kimbo82

Senior Member
May 23, 2013
374
120
Stockholm
Hi again, is it necessary to write the desired charging level each time I charge? On my last charge it charged to 94%, but I had set 85% as goal earlier.

Sent from my Nexus 6P using Tapatalk
 
Last edited:

Kimbo82

Senior Member
May 23, 2013
374
120
Stockholm
I get this when I try some commands.

I run stock Oreo on nexus 6P,with magisk 14.
e9f77b5d908a96c2ab5ebce9d70bdb0e.jpg


Sent from my Nexus 6P using Tapatalk
 
  • Like
Reactions: frdc0410

ghbuur

Senior Member
May 24, 2013
717
763
getting error too on s7 edge with s8 port installed. screenshot attached. wanted to test 10sec charging stop but didn't work. would be nice to ist this module..
 

Attachments

  • Screenshot_20170913-230501.png
    Screenshot_20170913-230501.png
    128.1 KB · Views: 2,781

Kimbo82

Senior Member
May 23, 2013
374
120
Stockholm
Sorry for a bad screenshot last time. However, when I do su before I get the same result as above.

Sent from my Nexus 6P using Tapatalk
 

VR25

Senior Member
Apr 20, 2013
1,864
4,570
github.com
Those facing issues -- your devices/systems are incompatible.

Please run the attached script as follows:
Code:
su
source /scrip/path/cs_debug.sh.txt
After that, upload here the file /sdcard/cs_debug.zip.
 

Attachments

  • cs_debug.sh.txt
    220 bytes · Views: 313

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    **v2022.1.8 (202201080)**
    - `acc -p` finds even more potential switches;
    - Enhanced charging status detection;
    - General fixes & optimizations;
    - Improved idle mode support;
    - New charging switches;
    - Optimize system performance and battery utilization, by forcing `bg-dexopt-job` on daemon [re]start, if charging;
    - Support for Qualcomm SnapDragon 8 Gen 1 devices, Nokia 2.2 and more;
    - Updated documentation.
    3
    **v2021.12.20 (202112200)**
    - [accd, misc-functions]: prevent unwanted crashes related to `eval` and `set -eu`;
    - [batt-info]: filter out the unreliable `POWER_SUPPLY_CHARGE_TYPE` property (note: this change makes AccA always display "unknown" charge type);
    - [batt-info]: fixed current reading issue;
    - [batt-info]: round current and voltage values to two decimal places;
    - [ctrl-files]: added `battery/op_disable_charge 0 1` switch;
    - [README]: updated troubleshooting section;
    - General optimizations.
    3
    v2022.1.6 (202201060)
    - acc -p finds even more potential switches;
    - Additional charging switches;
    - Enhanced charging status detection;
    - General fixes & optimizations;
    - Improved idle mode support;
    - Support for Qualcomm SnapDragon 8 Gen 1 devices, Nokia 2.2 and more;
    - Updated documentation.

    This is a pre-release. Anyone who's facing major issues is encouraged to try it.
    Please provide feedback!

    Not satisfied? acc -b undoes the upgrade.
    2
    Results of acc --log tail

    354: >pca9468-mains/current_max
    354: eval echo '$on'
    354: echo 0
    355: sleep 0.5
    260: 2>/dev/null
    260: shift 3
    260: exxit
    87: exitCode=1
    88: false
    88: set +eux

    And after restarting the daemon (if this is helpful)

    141: set +eu
    142: eval ''
    143: eval ''
    145: '[' -n '' ']'
    171: true
    205: false
    210: false
    214: '[' -n '' ']'
    266: cooldown=false
    267: sleep 10
    Try the attached build.
    1

    Back to the combination of Custom Max Charging Voltage with a max Capacity in %.​


    What I think could go wrong is that over time the set maximum charging capacity becomes associated with the set voltage limit. That can possibly lead to rapid drops at the lower end.

    My initial observations suggest that all the above may be the case.
    Readme > troubleshooting > custom max charging voltage and current limits reads:

    WARNING: limiting voltage causes battery state of charge (SoC) deviation on some devices. The battery management system self-calibrates constantly, though. Thus, as soon as the default voltage limit is restored, it'll start "fixing" itself.

    Limiting current, on the other hand, has been found to be universally safe. Some devices do not support just any current value, though. That's not to say out-of-range values cause issues. These are simply ignored.
  • 75
    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.