Search This thread

Schroeder09

Senior Member
Nov 6, 2017
1,119
208
Google Pixel 7 Pro
Btw there is a link to the releases and the documentation in the OP.
Yes. I saw those and browsed them. There are dev builds but no "dev-u" build as you originally mentioned. That's what I was asking about.

Did you use this latest dev build?

Jacc_v2022.6.4_202206040.zip

Are the settings of file or did you enter those through a terminal or the application that is also a download on the OP of this thread?
 
Last edited:

mochamoo

Senior Member
Oct 16, 2010
559
151
Google Pixel 7 Pro
Yes. I saw those and browsed them. There are dev builds but no "dev-u" build as you originally mentioned. That's what I was asking about.

Did you use this latest dev build?

Jacc_v2022.6.4_202206040.zip

Are the settings of file or did you enter those through a terminal or the application that is also a download on the OP of this thread?
The terminal command is acc -u dev (acc -upgrade dev) to download the latest dev build from the build you referred to or you can get it directly from the link on the OP. I use termux for the terminal app that you can get by doing a web search or from the google play store. I think it is recommended to get it through fdroid. All the acc commands and config info is in the documentation. I am no expert with the commands but did read the documentation to try to figure things out. I recommend that you do so as well before asking more questions. Vr25 spent a lot of time writing up the documentation. It answers a lot of your questions. You can try the default settings. And after you are more familiar with what those do you can tweak them as I have done.
 
Last edited:

Repear88

Senior Member
Aug 29, 2014
82
24
Google Pixel 7 Pro
Hi @mochamoo
I have a pixel 7 pro as well.
I went through the doc and I tried acc yesterday (uninstalled for now). With the command acc -t I noticed one that was working, it looked like the one you mentioned in post #4732. (gcpm/constant_charge_current_max 1866420 0) but was slightly different : gcpm/constant_charge_current_max 1933090 0.
So first idk where this difference come from, is it a custom switch from you ?
Plus with this switch the screen of the phone was always on (lock screen) even if it was always showing as charging. Did you have the same issue ?

Second thing is the battery percentage that was changing every 3 or 4 seconds (53% / 56%)
I did read about capacity_sync and capacity_mask but I am not sure I understand how to use it. So if you had the same issue and know how to fix it (ie display the real value).
 

mochamoo

Senior Member
Oct 16, 2010
559
151
Google Pixel 7 Pro
I think those 2 switches are very similar and probably depends on what charger or cable is used for testing. I used my wireless stand since that is what I use the most. Sounds like your battery might be idling if it is switching off like that. What is your pause / resume set at? Can you see what the current is doing via one of the acc frontends or ampere? If it's hovering near 0 then could be idling.

Or just out of sync with the Pixel. I wouldn't be too concerned about that. If you want you can calibrate the battery to see if it helps. I did do that at some point as well as some of my readings were quite a bit different between what was in the status bar and what acc settings gui was showing. The variance is minimal now.

I don't have the screen on issue. Perhaps a phone setting or another app interfering. I got rid of any battery related apps (like accubattery) and turned off adaptive battery at least until I got acc working.
 
Last edited:

Repear88

Senior Member
Aug 29, 2014
82
24
Google Pixel 7 Pro
Thx for your answer. I spent most of my day reading different topic and stuff about ACC :LOL::LOL:
So, I now have a better idea of how things work (slightly ^^)

my pause/resume was at default value, and the SoC was below (56%) It was charging, but the screen was always on. And if I would press the on/button, it would turn on right after ... anyway. I'll try again. and this time maybe not the dev version but the latest one + with an app (acc settings I guess) I will also remove betterbatterystat.

I still don't really understand where switches come from: I mean the syntax, and why are they different when the source is different ?

I'm very interested by the idle thing ! when I keep my phone plugged-in during long trip, or gaming. I love the tip from @VanGray https://forum.xda-developers.com/t/advanced-charging-controller-acc.3668427/post-86751991
To be able to switch idle on/off just with a QStile !
 

mochamoo

Senior Member
Oct 16, 2010
559
151
Google Pixel 7 Pro
Thx for your answer. I spent most of my day reading different topic and stuff about ACC :LOL::LOL:
So, I now have a better idea of how things work (slightly ^^)

my pause/resume was at default value, and the SoC was below (56%) It was charging, but the screen was always on. And if I would press the on/button, it would turn on right after ... anyway. I'll try again. and this time maybe not the dev version but the latest one + with an app (acc settings I guess) I will also remove betterbatterystat.

I still don't really understand where switches come from: I mean the syntax, and why are they different when the source is different ?

I'm very interested by the idle thing ! when I keep my phone plugged-in during long trip, or gaming. I love the tip from @VanGray https://forum.xda-developers.com/t/advanced-charging-controller-acc.3668427/post-86751991
To be able to switch idle on/off just with a QStile !
I know that this can be a bit of a rabbit hole trying to get to what is optimal for a particular situation. I am not sure about the charging switches myself and would be nice if there was some explanation about that. In the meantime I just tried to find one that worked. I wouldn't be afraid of the dev version. It is the one that is in the OP and also pinned on their telegram channel. (Not sure why it hasn't been "released" but it seems stable enough (at least for the pixel 7 pro). I stuck to the default config other than the charging switch and the pause /resume. (I know that can be automated day /night) but I mostly just set it based on need (acc pause% resume% in termux). I ***think*** that you can use the front end gui for some things but figure I need to learn termux/shell commands so try to use that. I prefer acc settings lately for quick tweaks and to observe the current, voltage effect.

I DO save a working config somewhere just in case I screw something up when trying something out. Honestly the current config is working well enough for me so will try to leave it alone :)
 

BarrettBear

Senior Member
Jun 16, 2009
94
8
I've been searching for ages now and hope someone can help me - does anybody know where custom profiles are located?

I know where the default one is, but I'm on a Pixel 6 Pro (Android 13) and cannot modify the file, as the system is force-locked to read-only.

I'm trying to find the location of the custom profiles so I can check the file itself and see if my settings look okay.

I'm getting an issue wherein the Pixel charging animation comes up every minute or so; I've tested with a variety of switches after trying acc --t, and the charging animation continues to pop up, even after restarting the Daemon between each switch test :'(


*****Edit*****

Please ignore above, I already solved this myself a short while ago on a prior device (Pixel 6, not Pro). Here's a link to the thread for anybody else encountering this issue.

 
Last edited:

Lada333

Senior Member
Feb 7, 2016
1,453
490
22
Budapest
OnePlus 3T
Google Pixel 6a
Hi, I have a question about idle mode. Supposedly, my kernel supports it and acc reports it as working. My question comes after reading this in the FAQ:

My phone when reaches this idle state stays locked on:

Is this healthy/safe?
The phone never gets over 35°. I like to let the phone charge over night at 1A and when it's done, it just stays there at 80% on idle mode.
Just making sure I'm not stressing the battery without a reason.

Thanks!
Hey!

Did you achieve that by setting the max charge level to 80% and then simply just enabling 'prioritize battery idle mode'?
I'm trying to achieve a very similar setup where I slow charge the phone overnight but then it's at 80% (or as close as it can be, since the "unplugged" battery discharge nominal) when I unplug & start my day.
 

jakito

Senior Member
Aug 9, 2016
132
72
OnePlus 7 Pro
Hey!

Did you achieve that by setting the max charge level to 80% and then simply just enabling 'prioritize battery idle mode'?
I'm trying to achieve a very similar setup where I slow charge the phone overnight but then it's at 80% (or as close as it can be, since the "unplugged" battery discharge nominal) when I unplug & start my day.

Hey. Yeah, I just set ACC to prioritize idle mode. That was enough with my kernel. Your experience may be different
 
  • Love
Reactions: Lada333

BarrettBear

Senior Member
Jun 16, 2009
94
8
I've now come across a new issue; it appears that ACCA service is killed in the background.

Phone: Pixel 6 Pro, Android 13, TP1A.221105.002
Magisk: App & Root (v25.2 (25200) 33)
ACC Module: v2022.7.4-dev by VR25
ACC App: v1.0.35

The app seems to work fine when it's open and in the foreground, and for a short while after that, however about an hour or so after it is sent to the background (or swiped away), the daemon service must stop, because my limit of 80% on battery is ignored, and the phone will charge all the way up to 100%.

I don't believe this is a charger issue, as when the app is active in memory, it will happily bounce between 70% - 80%, and properly function.

I've set the app to be "Unrestricted" in its battery usage, so I'm unsure why it's being force-closed in the background.

Does anybody know how I can keep it in memory? Or has come across this before and solved it?
 

Lada333

Senior Member
Feb 7, 2016
1,453
490
22
Budapest
OnePlus 3T
Google Pixel 6a
I've been reading the documentation for hours now, trying to find out where I went wrong, but I just can't seem to be able to.

I'm on a Pixel 6a, unofficial crDroid, Android 13, stock kernel.
On my previous devices, I've always used either AccA or ACC Settings, but none of them seem to function now for whatever reason. I want to set up ACC in a way that it limits the maximum charge level to 80% (which seems to be working fine the way I configured it using Termux) and to limit the maximum charge current to 1000mA.
I've tried:
  • Setting the charging switch to automatic
  • Setting the charging switch to whichever ACC deemed working (using acc --test)
  • Setting the max charge current to 1000 using both acc -s c 1000 and acc --set mcc 1000
None of these seem to be throttling the charging speed.

I saw in the documentation how it's recommend to limit the charging voltage instead, but then there's the fact that not all kernels support that feature.

Could anybody help me out here?
Thanks in advance


EDIT:
Okay so using acc --set mcv=4000 kinda does what I want it to do? It's around 1250-1300mA instead of 1000mA, however using any value below 4000mV just results in the phone constantly popping up the "just plugged in" screen? Like it charges for a second, then stops for a few, then charges again for a bit, and so on. (I am using the currentWorkaround thing).


EDIT 2:
Alright, so somehow setting any value as max charging voltage no longer works either (regardless of cw being true or false). I cannot seem to be able to limit the charging speed at all. Could that be a kernel issue?
 
Last edited:

vurtomatic

Senior Member
Mar 22, 2015
545
114
This worked pretty well but I found a better solution for my Pixel 7 Pro. I updated acc to the latest dev build (acc -u dev). Then tested configs. The first one I chose to try is (gcpm/constant_charge_current_max 1866420 0). It is working perfectly. Pausing and charging as it should. Idles too. I didn't change max current or voltage. The one above kind of missed the target pause / charge and had to play with mcv, mcc. Not with this new setup.

Does anyone know what gcpm stands for? Just out of curiosity.
Hi @mochamoo , can you share your config file? I'm new to ACC. I followed your steps of uninstalling ACC, the front-end, disabling Adaptive Battery. Then reinstalling ACC (stable) and ACC Settings.

I also installed Termux, and navigated to /data/adb/vr25/, but can't run any "acc" command.
 
Last edited:

vurtomatic

Senior Member
Mar 22, 2015
545
114
You needn't navigate to any folders. After launching Termux, type "su," hit enter, then you can use all "acc" commands.
Thanks for the suggestion! I already ran "su" and couldn't run "acc". Termux is telling me it can't find the command. But ACC is installed, I know where the folder is, and I have Acc Settings installed too.
 

vurtomatic

Senior Member
Mar 22, 2015
545
114
You needn't navigate to any folders. After launching Termux, type "su," hit enter, then you can use all "acc" commands.
Thanks for the suggestion! I already ran "su" and couldn't run "acc". Termux is telling me it can't find the command. But ACC is installed, I know where the folder is, and I have Acc Settings installed too
Have you rebooted since flashing the Magisk module?
Well this is weird. It worked. I'd rebooted the phone previously but literally following your suggestion and rebooting it one more time and "acc" worked from Termux. TYSM. I'm going down the rabbit hole with the command suggestions here for P7P.
 
  • Like
Reactions: Lada333

BarrettBear

Senior Member
Jun 16, 2009
94
8
just results in the phone constantly popping up the "just plugged in" screen? Like it charges for a second, then stops for a few, then charges again for a bit, and so on. (I am using the currentWorkaround thing).

I had this yesterday (Still have an issue where it will charge past my max), but installing the following magisk module stopped the screen flashing. I used that package on my current Android 13 and it works okay.

 

Top Liked Posts

  • 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.
  • 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.