Search This thread

bizkit_120

Senior Member
Feb 4, 2014
102
15
I've had success with the following switches.

dc/current _max xxxxxx 0
gcpm/constant_charge_Current_max xxxxxx 0

I used to use the gcpm one, but wasn't perfect. Switched to dc, and it's been much better. Wireless charging works, too, with the dc switch.

I'm currently on a Cheetah, but have tested it on Raven as well.
👍 Wonderful,glad to hear yours works fine now, I'm using OnePlus 9 it doesn't have those switches available. .going to sell my p7 I have had it..hate that damn fingerprint scanner....anyhow, my understanding it over charged because of daemon has been killed while sleeping, but how does that switch solve the problem...🤔
 
👍 Wonderful,glad to hear yours works fine now, I'm using OnePlus 9 it doesn't have those switches available. .going to sell my p7 I have had it..hate that damn fingerprint scanner....anyhow, my understanding it over charged because of daemon has been killed while sleeping, but how does that switch solve the problem...🤔
Not sure if a different switch can help if your phone's software keeps stopping acc.
 
I just installed acca app and keep it background active, will see if that help, tonight's test will tell.. what's annoying me is that problem can't reproduce during the day as it acc daemon always running..
I doubt that will make a difference, but doesn't hurt to try. If it happens at night, I would imagine a deep sleep state of the software kicking in after a certain minutes or hours of inactivity (of screen, accelerometer, etc.)
 

bizkit_120

Senior Member
Feb 4, 2014
102
15
I doubt that will make a difference, but doesn't hurt to try. If it happens at night, I would imagine a deep sleep state of the software kicking in after a certain minutes or hours of inactivity (of screen, accelerometer, etc.)
That's exactly what I thought, I installed acca lock it in background which internally invoke acc core , technically it should not be killed again if I already give background active permission.
 

knasiotis

Member
Aug 21, 2016
25
5
I also have wireless charging issues. It never stops charging.
Mi 11 Ultra (star)
I have also opened an issue on the github page and uploaded logs the way they recommend in the repo.
 

bizkit_120

Senior Member
Feb 4, 2014
102
15
Please keep us posted. I'm eager to know.
Very interesting result,I set pause at 95 ,from battery charging history graphics shows, I put it on wireless charger around 40% , it charged about 2hrs all the way till 95,it indeed stopped at 95 for about 30 mins ish, but acc daemon eventually stopped throw exit 7 error , and continue charging again... can't explain why..
 

Attachments

  • Screenshot_2023-01-20-07-27-16-11_84d3000e3f4017145260f7618db1d683.jpg
    Screenshot_2023-01-20-07-27-16-11_84d3000e3f4017145260f7618db1d683.jpg
    71.3 KB · Views: 67

eried1

Senior Member
May 27, 2016
434
68
Stockholm
Difficult to handle overnight issues. Guessing you're also allowing Magisk in the background? Think of all related processes.
 

bizkit_120

Senior Member
Feb 4, 2014
102
15
Difficult to handle overnight issues. Guessing you're also allowing Magisk in the background? Think of all related processes.
I didn't change permission of magisk since it installed,but it shouldn't matter either allowed background or what, it just a manager for module installation..acc should runs itself once set up
 

Fırat.ç

Member
Jul 9, 2012
43
5
Hi, I am using lastest version with AccA. However, it don't stop at my settings when I charge with wireless charger. "Daemon stopped with exit code 7!" warning is appeared in the notification bar. How can I fix this?
 

samhhmobil

Senior Member
May 25, 2017
473
239
Hamburg
ACC did work many years without issues on several devices (pioneer, gta4xlwifi, gauguin, etc.).

But since I switched to OnePlus8 (instantnoodle) running LineageOS20 (Android13) it does nothing. No charging control on this device.

Does someone know how to fix it?

Thanks,
samhhmobil
 

mwahahaa

Senior Member
Jun 27, 2015
155
36
Google Pixel 4a 5G
Google Pixel 7
acc works on my Pixel 7, both plugged in and wireless charging. However, the problem I have which prevents me from using it is at there moment is that it causes my screen to turn on every few minutes for a short period of time. At night this can lead to sleep disruption (not to mention it is annoying). I'm on 2022.7.30 dev and have tried other versions with no success. Any suggestions to address this problem?
 

Uluru25

Senior Member
Nov 27, 2016
399
154
Samsung Galaxy S7
Samsung Galaxy A6
Maybe (!) you have checked in the rom's (!) settings to activate the screen if unplugged from the charger and maybe (!) acc stopps due to your config the charging periodically and maybe (!) these stopps are misinterpreted as unplugging of the charger?
 
  • Like
Reactions: beeshyams

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    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.
    1
    ... there is a strong warning to never edit this file in windows:
    WARNINGS

    # Do not edit this in Windows Notepad, ever!
    # It replaces LF (Linux/Unix) with CRLF (Windows) line endings.

    # Nullifying values that should not be null causes unexpected behavior.
    # However, doing so with "--set var=" restores the default value of "var".
    # In other words, for regular users, "--set" is safer than modifying the config file directly.

    # Do not feel like you must configure everything!
    # Do not change what you don't understand.

    See here.

    Here you also find more background info to the module and some frontends.
  • 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.