yashsingh1/xdaforums huggingface dataset:
[Magisk] dingolino:
Hi,

just started with AccA

I have a question on the DJS addon.

Wthin the AccA app always when I tap on the "clock" in the right corner I got the meassage that DJS is neccessary and I can install it.

BUT: It is installed I see it in Magisk Manager.

Can I use DJS from the AccA app? or do I need to edit the settings file with a editor? Or start it manualy?

Best regards,

dingolino
[Magisk] Eckyx:
Hi all,

Running a Pixel 3 with the latest Magisk Canary (beta would not work). ACC seems to work, but when I tap the clock icon and get the "DJS is Required" message, tapping install causes "Installing DJS" to appear for a split second, then "DJS is Required" reappears.

I installed DJS using Magisk, but it still doesn't seem to be detected/recognized by ACC.

What am I doing wrong?
[Magisk] dingolino:
Did the same, but no effect, that´s why I was asking
[Magisk] jaggillararla:
Is acca good to use now ? @VR25
[Magisk] BostonDan:
I use it daily. DJS doesn't install for me, but ACCA starts on boot and I have no issues.

Hope this helps.

Cheers,

B.D.
[Magisk] baldybill:
Is that the most recent ACCA that you use?

I thought it had issues?
[Magisk] BostonDan:
I haven't had issues, but ymmv.

Cheers,

B.D.
[Magisk] brackenhill_mob:
I've just bought one of these phones and battery/input_suspend works for me

What ROM are you running? I'm on MIUI Global 12.0.4.0 (QJGEUXM)
[Magisk] SouthOkanagan:
Yeah, I'll try the reset, but I installed it the first time and just started playing with it and put some settings in there which I believe change my default so if I if I reset it it's just going to reset to the settings I said right I'll try it and I'll let the forum know here what happened.

Thank you for your help much appreciated
[Magisk] Chester47:
Can anyone help me out. Acc runs at default 70 75, but when it gets to 75, it starts dropping and charging, and if I leave it plugged, it can charge upto 100%, while doing that. I don't fully know the best way to set it up. M device is pixel 3xl. Android 11, no custom kernel.. please help me out.
[Magisk] R9xy91:
En qué parte ouedo agregar el comando y que comando puedo poner para ponerle pausa a la carga y evitar el recalentamiento es decir que cargue a 50 % y luego reanudar 20 minutos después para completar la carga establecida
[Magisk] killer23d:
I have the same behavior on Pixel 5, wired or wireless charging makes no difference. I am tailing the log and I can see it is dropping but it will still charges to 100%.
[Magisk] srslye:
Acc/AccA not working with any Android 11 ROM so far. Anyone have any workarounds?
[Magisk] brackenhill_mob:
Working just fine for me. Have you changed kernel? And poked around in /sys/... to see if you have an unknown switch?
[Magisk] srslye:
Always change to Stardust when possible.

Thanks, I'll give it a try. It's the ACCA daemon that stops running.
[Magisk] kokos76:
Please can you share you working config for poco x3?
[Magisk] brackenhill_mob:
No need. Use battery/input_suspend switch. I've not made any other changes from stock installation. Hth
[Magisk] kokos76:
Thank you!

Which version ACC and ACCA are you using? The latest versions do not work for me stably.
[Magisk] brackenhill_mob:
AccA is 1.0.29 and ACC is 202010150
[Magisk] Jirachilover:
The only switch that works for me on stock pixel 4a is input_suspend 0 1 with no battery idle mode (battIdleMode=false). So there's no way to get battIdleMode with swapping out the kernel for one that supports battery off power? :oops:
[Magisk] ricky56789:
Pixel 5 sometimes reports that it is plugged in when it is not charging using default settings in the app - charging this device via usb notification appears.
[Magisk] bjdaye:
works fine at my Redmi K20 Pro

but can't work at XiaoMi 11

miui 12.5. 21.1.13 beta

android version 11

magisk 21.4

acc v2020.11.20

acca 1.0.29（33）
[Magisk] killer23d:
I am using the bundled version in ACCA settings on my P5, so far I have not have issues. When I changed to 11.20 in ACCA, it just keep charging until 100%.
[Magisk] Sp33d_:
On my Pixel 5 when I test the switches via App i get "Selected charging switch works!"

but via terminal i get this:

(i) Alright, this may take a minute or so...

(!) [/sys/devices/platform/soc/soc:google,charger/charge_disable 0 1] won't work

(!) [battery/charge_charger_state 0 1] won't work

(!) [dc/input_suspend 0 1] won't work

(!) [sm7250_bms/charge_disable 0 1] won't work

Effectively the phone charges to 100%.

(Pixel 5, Stock A11, only rootet via Magisk)

Maybe somebody has an idea how to fix this?
[Magisk] sandronejm:
Deleted
[Magisk] warrencoakley:
Can't get this working on my Google Pixel 4a (5G) Keeps charging pass the threshold.
[Magisk] warrencoakley:
Any reason after setting it for 80 75 that it's not working?
[Magisk] ghbuur:
thx. i tried that but it didn't work properly (something about unzip error) . but at least it created a file. does it help?
[Magisk] VR25:
Yes, it contains what I need. -- Thanks

Update: [MENTION=5279101]ghbuur[/MENTION], your device is set up way too differently from the standard/stock Android. I need more information to determine whether this module can really work with it.

Please, run the new debugging script (attached) as per the following instructions set:

su

source /path/to/script

1. While charging (USB)

2. While charging (charger)

3. While unplugged (not charging)

3 Zip files will be generated in /data/_cs_debug (one on each run). Upload these here.

Update 2: [MENTION=5279101]ghbuur[/MENTION], I found out where the incompatibility relies on. Forget the info above if you've not done so already. I have to make a few significant changes to the module. This will take a while.
[Magisk] RokCruz:
Working good for me, no issues

Edit: I found this app that does the same but automatically

Battery Charge Limit (Stops charging at a desired level) - https://f-droid.org/app/com.slash.batterychargelimit
[Magisk] VR25:
I've tried it. It's awesome -- though with a few limitations. You can't enable/disable charging on demand & you have less control over the whole thing.

One particular feature that interested me quite a lot is the ability to start charging again when battery level drops below a set percentage. I'll add that to the module!
[Magisk] Taracair:
Permission denied.

Any workaround?

Would be great to use this app

Using lg g3, LOS based rom, custom kernel.

Tried to move cs file to bin and xbin but it was already there

Edit

Got it working, had to set 777 permissions for the cs file.

What set of commands should be used for the combination:

Charge to 100%, then stop charging for the next 8 hours.

cs 100 && cs -d 8h?

Well I got sth like this

d855:/ $ cs 99 && cs -d 8h

/system/bin/cs[14]: can't create /data/.cs_sON: Permission denied
/system/bin/cs[163]: can't create /sys/class/power_supply/battery/charging_enabled: Permission denied
rm: /data/.cs_sON: Permission denied
/system/bin/cs[193]: can't create /magisk/cs/.history: Permission denied
/system/bin/cs[193]: can't create /magisk/cs/.history: Permission denied

/system/bin/cs[196]: can't create /sys/class/power_supply/battery/charging_enabled: Permission denied
Desired charge % reached!
S/OFF --> Sat Sep 30 07:13:19 CEST 2017
- Press RETURN to re-enable charging & exit.
cd system
/system/bin/cs[201]: can't create /sys/class/power_supply/battery/charging_enabled: Permission denied

/system/bin/cs[14]: can't create /data/.cs_sON: Permission denied
/system/bin/cs[160]: can't create /sys/class/power_supply/battery/charging_enabled: Permission denied
Charging disabled for 8h.
S/OFF --> Sat Sep 30 07:13:48 CEST 2017

Any ideas?
[Magisk] gloeyisk:
Keep up the good work! I'll try this cool module.

Trying to be kind man, if anything else (bad things) was happen to me, i promise to be respectful member as i say i'll report to you slow but sure. Thanks.
[Magisk] VR25:
[MENTION=4252833]Taracair[/MENTION], the syntax is correct, but you don't seem to be running as root.

EDIT: [MENTION=4252833]Taracair[/MENTION], actually, "cs 100 && cs -d 8h" won't work as expected. The scrip has a bug -- it'll stop charging at 100%, but then it'll wait for user input to re-enable charging & exit. Only afterwards, the shell will run the next command. I'll fix that & add features.
[Magisk] Taracair:
Got it working after second attempt.

Charging to 99%...
S/ON --> Sat Sep 30 09:01:09 CEST 2017

CHARGING_ENABLED=1
CHARGING_TYPE=Fast
TECHNOLOGY=Li-poly
VOLTAGE_MAX_DESIGN=4350000
VOLTAGE_MIN_DESIGN=4350000
VOLTAGE=4346000
LEVEL=99%
CURRENT=-400
CHARGING_FULL_DESIGN=3000
TEMP=245
PSEUDO_BATT=0
EXT_PWR=14
SAFETY_TIMER=1
VALID_BATT_ID=1
USB_CURRENT_MAX_MODE=0
STORE_DEMO_ENABLED=0

Desired charge % reached!
S/OFF --> Sat Sep 30 10:15:23 CEST 2017
- Press RETURN to re-enable charging & exit.
[Magisk] jimbob_sf:
I've read and now see I have to find a rradme... Can you simply put in the module description in MM and op that you need to use terminal? Forcing us to bounce from MM, to xda, to search the thread, to find the readme...
[Magisk] Eng.Raman:
Didn't work for me .

Zenfone 2 / stock 6.0.1
[Magisk] Taracair:
Well actually it's fine. It charges to demanded value and stops charging after that. That's what I wanted. The -d 8h isn't needed actually.

Edit

cs -d 6h && cs 100 works even batter. I wake up with fully charged phone which wasn't overcharged few times during the night. When it's charged it stops and that's the point.

Thank you for this great module.
[Magisk] frdc0410:
I am very new to this. I tried using the termux terminal emulator but it says there "no command 'cs' found". I already successfully flashed this through magisk, but I'm not sure how to make this work :(
[Magisk] VR25:
Well, the OP is the README itself. Not sure how you missed the "terminal" part. It's not explicitly there, but there are commands... and you run those on terminal. Also, "cs --help" gives you all the help & usage tips you need. So...

Sorry if I missed something. Will work on a more user-friendly reference.

The only thing standing between me and a new version is time. I've been quite busy these days. Will add support for more devices or possibly make the module universal.

You may not be running the commands as root. That's the most obvious reason. Else, let me know.
[Magisk] Taracair:
The command cs -d 6h && cs 100 doesn't work.

It doesn't finish the -d 6h at the required time, nothing happens after the 6h. So actually cs 100 is enough, because after charging to 100 it hangs up and doesn't charge after I wake up and press enter.
[Magisk] VR25:
Alright, in the next version, cs will give you the option to start charging again after battery level drops to a set percentage. So, essetialy the user will have the ability to define a charging and recharging threshold (i.e., charge to 80%, pause. If battery level drops below 20%, resume charging). That's much better than "cs -d #% && cs #" IMO. Thanks for the report.
[Magisk] zakyakr:
Any idea of this problem? Permission denied

land:/ $ cs -i

/system/xbin/cs[14]: can't create /data/.cs_sON: Permission denied

Battery Info

/system/xbin/cs[160]: cat: /sys/class/power_supply/battery/uevent: Permission denied

land:/ $

---------- Post added 04-10-2017 at 12:12 AM ---------- Previous post was 03-10-2017 at 11:52 PM ----------

Never mind I forgot to type 'su'
[Magisk] Cpt.mactavish:
an user interface app would be best.. :(
[Magisk] lioux:
I'm using Magisk v14.2 on a Pixel XL stock Oreo with October security update. Unfortunately, this module is not being mounted by magisk.

I get no errors on either installation or after reboot. However,the cs binary isn't at /system/xbin

It's only available at /magisk/cs/system/xbin/cs

Let me know if there's anything I can do to help.

--------- beginning of main

I( 469: 469) Magisk v14.2(1420) daemon started

I( 469: 471) ** post-fs mode running

--------- beginning of system

I( 469: 623) ** post-fs-data mode running

I( 469: 623) * Mounting mirrors

I( 469: 623) bind_mount: /system_root/system -> /dev/magisk/mirror/system

I( 469: 623) mount: /dev/block/platform/soc/624000.ufshc/by-name/vendor_a -> /dev/magisk/mirror/vendor

I( 469: 623) bind_mount: /data/magisk -> /dev/magisk/mirror/bin

I( 469: 623) * Mounting /data/magisk.img

I( 469: 623) * Running post-fs-data.d scripts

I( 469: 623) * Running module post-fs-data scripts

I( 469: 623) magisk-foldermount: exec [post-fs-data.sh]

I( 469: 623) * Loading modules

I( 469: 623) busybox-ndk: constructing magic mount structure

I( 469: 623) cs: constructing magic mount structure

I( 469: 623) magisk-foldermount: loading [system.prop]

I( 469: 623) magisk-foldermount: constructing magic mount structure
[Magisk] RMarques:
Have anyone successfully installed and ran this module using Magisk on OP5?
[Magisk] RMarques:
Ok then, latest version successfully flashed and mounted by Magisk, Termux installed and given SU rights.

I've tried the following inputs:

cs-c 80 2m

cs -c 80 2m

However, I'm getting the following errors:

See attached SS

...can anyone shed some wisdom over here?
[Magisk] VR25:
Ok, [MENTION=7721744]__riptide__[/MENTION], [MENTION=8010004]guest4711[/MENTION], thanks for the feedback. Perhaps Auto-run is not working properly for you. Does "cs -d" stop the charging?

[MENTION=5990744]Younex[/MENTION], definitely auto settings weren't working properly in build 2017.11.15. Now that's fine. If you just install and reboot, cs will automatically set "90 10" settings and run on its own as previously stated. If you want to change that, simply run "cs [pause_value] [resume_value (default 10)]" -- i.e., "cs 80 20".
[Magisk] __riptide__:
Just noticed a pretty weird behavior. Before writing my earlier reply I had already tested with cs -d to no avail (I use Tasker for automation but have it disabled so that it doesn't interfere with the testing). After your reply I did a reboot and now, cs -d works but cs -e doesn't!!!!! Going to reboot again...

UPDATE : [MENTION=5228676]VR25[/MENTION] after more testing here's what i found out:

doing cs -d seems to set the target percentage to 70 ie below 70 charging is enabled and above it charging is disabled. Also this goes on without any effect from cs -e until the device is rebooted. after reboot everything works normally until i do cs -d again
[Magisk] psychoela:
[MENTION=5228676]VR25[/MENTION] please help,thanks
[Magisk] VR25:
# 2017.11.19 (201711190)

- "cs -a" --> re-enable charging on service resume for better performance

- Fixed cs service not running

Ok, so... I've found and bashed several bugs preventing normal cs operation. Some of us faced more issues than others. In fact, I've heard a few people almost died... :p

Anyway, hopefully this version works, especially for those who have already been aboard for a while.

A Note to Samsung Users

- There are two possible (identified/well known) charging control files for Samsung devices: "store_mode" and "batt_slate_mode". If your device is supported (i.e., cs doesn't display the "unsupported device" message) and you're facing other issues, open /data/media/cs/cache & swap the control file.
[Magisk] michaelcrossland:
Well just tried the new version from the manager. It told me to upload the zip file. Says device unsupported. Hope you get this working because the other stay alone app that does the samething as your module does. The app would work but had to remove it because it keep cussing the OS and some other programs to kept crashing because of the qpp.
[Magisk] Younex:
[MENTION=5228676]VR25[/MENTION] thanks, I have one more question please :

Is it normal to see battery level 100% ?

When I run the cs -a it says

$ su
$ cs -a

grep: /magisk/cs/.config/cs: No such file or directory
sed: /magisk/cs/.config/cs: No such file or directory
(i) cs service ON
- Reboot to apply change.

Didn't know it would require a reboot :/
[Magisk] VR25:
Oh, of course! I forgot your device's manufacturer in build.prop has been renamed from Samsung to HTC. That's why cs isn't working.

Run "cs -c", paste the following config on terminal, hit ENTER twice -- and you're done:

/sys/devices/battery.98/power_supply/battery/store_mode 0 1

If you encounter other issues, replace "store_mode" by "batt_slate_mode".

Edit: that won't work (yet). There's something I need to change first.

Those errors are odd...

Are you on the latest build (2017.11.19)?

What did you mean by "... see battery level 100%"? I didn't get the context.
[Magisk] michaelcrossland:
Okay can you keep me posted once you have the fix up on here or on the manager. Thanks for all your hard work.
[Magisk] guest4711:
20171119-1 is running fine now. I just tested "cs 65 65" to keep battery charged while on AC and it was floating from 64% to 67% which is ok for me. :good:

Thanks again for your hard work!
[Magisk] Younex:
If the charging is set to stop at 90, shouldn't I see lbattery level 90% instead of 100 when unplugging the charger ? ?

I believe I was on build 2017.11.19, not 2017.11.19-1

I think I needed a reboot after installing the newer zip and before running the command , that's why :) will reboot and try again
[Magisk] VR25:
# 2017.11.19-2 (201711192)

- Ability to keep/maintain battery power at a constant level (cs -k LEVEL)

- Enhanced "auto" (cs service) & debug (cs debug) functions

Those with still unsupported devices, please upload an updated cs_debug zip. That file will contain richer data -- thanks to the new debugging engine.
[Magisk] FighterBoyZ:
Is "cs 80 && cs -d 5h && cs 100 20" possible? Meaning pause at 80, stop for 5h, pause at 100 and resume at 20. "Cs #" should start the charging again after "cs -d 5h" ends? Also does it matter where I put the 20 for resuming the automated process?
[Magisk] VR25:
If you run cs 80 alone, you'll notice that it does pause at 80. Since you didn't specify a "resume value", cs uses the default (10). That means, it stays on a loop until you exit/abort the process.

If you were to actually use this, the 20 should always be on the last instance (exactly where it is now), since cs % % overwrites settings.

So, currently, this usage scenario is not possible. The good news is: next version will let you accomplish that.
[Magisk] Nordblum:
For some reason, battery stats don't reset on my system neither automatically (on pause) nor manually (cs - r). Upon sending the cs - r command, this is what the output looks like.

su
bacon:/ # cs -r

Error dumping service info: (Unknown error -2147483646) batterystats
bacon:/ #

The debug archive is attached below.
[Magisk] psychoela:
:confused:
[Magisk] VR25:
That's a known issue of "dumpsys batterystats --reset". Either this command is not a universal solution itself, or something else is blocking its normal function (ongoing investigation).

Yeah... I should've provided some info. "zzz-cs-service", as weird as it may sound -- is what makes cs service work as intended. Without it, there's no proper automation sans MacroDroid/Tasker or alike. You can think of it as a cs add-on.
[Magisk] iluvatrix:
It's mentioned in the op that the terminal app has only to be unoptimized but does not have to be open or running in background.

However on my Robin on Los 14.1 after many days of testing it's confirmed that only when I leave the terminal app open then the cs -k 80 will work.

Is there a fix for this?

Will terminal app left running consume more battery?

Does the choice of terminal app affect?

I am using Terminal Emulator from fdroid store
[Magisk] VR25:
No.
[Magisk] Sreekantt:
been away for long time.....terminal isn't required in notification for stopping charge automatically ?? ....

Edit- made terminal as system priv app ...blocked notifications of that app...working perfectly as of now in 1st test
[Magisk] DeeZaster:
I've been trying to locate any information on why I can't getbthis module to work but I couldn't find any information on this message I'm getting. Any help would be appreciated. Here is whats happening:

$ su

n2awifi:/data/data/com.termux/files/home # cs 60 40

"cs": error: only position independent executables (PIE) are supported.

n2awifi:/data/data/com.termux/files/home #

I'm on the latest 7.1.2 resurrection rom

Samsung Tab Pro 10.1
[Magisk] KaMyKaSii:
Run "acc -t" to test the avaliable charging switches and then try the ones that works with "acc -s s"
[Magisk] warrencoakley:
No sure what to do. Here are the results
[Magisk] chomsky55:
I set my config with acc 75 65 and checked that the daemon is running. The charging switch mode I selected is supported. When I plug my device in the charger (or wireless) it starts charging though my battery is at 69% I checked it with acc -w and dumpsys battery (see attach)

Is there some kind of delay before acc "kicks in" or am I doing something wrong?

I presume that the acc settings don't need to be set again after a reboot?
[Magisk] swangjang:
Install cleanslate kernel. Then you'll get an additional switch option called "/sys/kernel/debug/google_charger/input_suspend 0 1"

This one works.
[Magisk] RCSixes:
I have the Pixel 4a 5G and got the exact same results for "acc -t" . None of the switches work and it appears no one has discovered the correct switch yet. I am unfortunately not skilled enough to find the correct switch.

If anyone can find the right switch, we will love you!
[Magisk] ghiblies:
When ACC is enabled in Magisk, the "Edxposed framework" is disabled.

If you disable ACC in Magisk, the "Edxposed framework" will be enabled again.

How can I enable both?

OS : Android 10

Magisk : 21.4(21400)

MagiskManager : 8.0.7(4834)(15)

ACC : v2020.11.20

Riru : 23.4

Edxposed : v0.5.2.0_4672-master
[Magisk] EvillNooB:
Oneplus 7T, Acc stopped working after updating to Android 11(continued to charge beyond 75%)

reinstalling both acca app and acc magisk module solved this issue
[Magisk] X4c3:
Hello,

Will this work on Redmi k30?
[Magisk] v.konvict:
Does it reset tge battery stats as well when it gets to 75%. Since the android 11 am seeing battery stats only reset at 100%
[Magisk] amn1987:
Can anyone please tell for the duration that the device is being charged and in use is current (for powering the device) still being drawn from the battery or directly from the charger?

Edit: I checked with an external USB Power Tester and that seems to be the case. Similar to pseudo battery idle mode perhaps?
[Magisk] IUse_Android:
Since 2 days I have been using this module which seems really interesting.

My setup isn't that crazy I think; I just installed it and ran acc 85 80. Stop charging at 85% and start again when it reaches 80% (while connected).

Below is the config.txt

configVerCode=202011120
capacity=(0 60 80 85 false)
temperature=(40 60 90 65)
cooldownRatio=( )
cooldownCurrent=
cooldownCustom=()
resetBattStats=(false false)
chargingSwitch=()
applyOnBoot=()
applyOnPlug=()
maxChargingCurrent=()
maxChargingVoltage=()
language=en
runCmdOnPause=()
ampFactor=
voltFactor=
loopCmd=()
prioritizeBattIdleMode=false

However, my phone doesn't charge higher than 69% (nice) now, and I can't seem to understand why.

I hope that someone can tell me what I am doing wrong. Or what other step I can take to debug it.

I just found the info on the GitHub about a 70% issue, I should look into that first before continuing to asking help here.
[Magisk] gilgamesh0808:
You can try stitch

"/sys/class/qcom-battery/input-suspend 0 1"

It works on mi 11 EU rom (android 11)
[Magisk] oguzatagan:
Hello everyone i using Huawei mate 9. İ trying disable this module. İ delete module in magisk.but now charging is slowly. Not work Fast charge what can i do?
[Magisk] -SKYLINE-:
I have been using ACC magisk module on my Razer Phone 1 running on LineageOS 17.1 (2021-02-13) for 2 days now. I have left ACC settings as default.

On (1) a Samsung charger (Model EP-TA20UWE) which I received with a Samsung Galaxy C5 Pro and (2) a Xiaomi 10,000mAh QC3.0 and PD power bank, ACC works as it should (i.e. cooldown at 60%, pause charging at 75% and continue charging at 70%).

However, when using (3) the OEM QC4.0 charger that came with the Razer Phone, the phone shows "discharging" after 75% but continues to charge to 100%.

I understand that Github says this is the worst case charging switch scenario and should enforce a working switch. However, does this recommendation apply where certain chargers (1) and (2) behave correctly but others (3) do not?