[Guide]Using the Advanced Charging Controller (ACC) Magisk Module with Pixel 3a/XL

[lpcysmi]

Hello:

If Using Android auto, would it still work after reaching the 80% (or whatever value you chose) or if the charging stops android auto stops?

I haven't been able to try it, but was legitimately wondering. I don't want to do a long trip and get my google maps deactivated halfway trip

Regards

 

[ktmom]

Hello:

If Using Android auto, would it still work after reaching the 80% (or whatever value you chose) or if the charging stops android auto stops?

I haven't been able to try it, but was legitimately wondering. I don't want to do a long trip and get my google maps deactivated halfway trip

Regards

When I am using maps on long trips, I have the device stay at about 42%. Using some Tasker scripting, when I'm about an hour out from my destination, it charges back to 80%. Since I don't use Android Auto, I don't have personal experience, but I would be surprised if it closed on charge pause.

 

[sic0048]

When I am using maps on long trips, I have the device stay at about 42%. Using some Tasker scripting, when I'm about an hour out from my destination, it charges back to 80%. Since I don't use Android Auto, I don't have personal experience, but I would be surprised if it closed on charge pause.

Any particular reason you do this?

The Pixel 3a devices support "Battery Idle" mode which basically says anytime the phone has reach a "full" charge and is still plugged into a power source, the phone will bypass the battery and draw power directly from the power source. So whether you tell the phone that a full charge is 42% or 80% or 100%, once it hits that number it bypasses the battery completely. There is no harm is letting the battery charge to 80% and then leaving it plugged in for extended periods of time.

Phones that don't support "Battery Idle" mode will draw power from the battery while also charging the battery - even when the battery is fully changed. So I can see the benefit of your method with those phones.

Phones that support "Battery Idle" mode at full charge and still plugged in:

Power supply --> Phone​

Phones that don't support "Battery Idle" mode at full charge and still plugged in:

Power Supply --> Battery --> Phone​

 

[ktmom]

Any particular reason you do this?

The Pixel 3a devices support "Battery Idle" mode which basically says anytime the phone has reach a "full" charge and is still plugged into a power source, the phone will bypass the battery and draw power directly from the power source. So whether you tell the phone that a full charge is 42% or 80%, once it hits that number it bypasses the battery completely. There is no harm is letting the battery charge to 80% and then leaving it plugged in for extended periods of time.

Phones that don't support "Battery Idle" mode will draw power from the battery while also charging the battery - even when the battery is fully changed.

Phones that support "Battery Idle" mode at full charge and still plugged in:

Power supply --> Phone​

Phones that don't support "Battery Idle" mode at full charge and still plugged in:

Power Supply --> Battery --> Phone​

Fair question [emoji846]

There are two reasons. I've had my Tasker setup since ~2015. The P3XL (not P3aXL) is the first device I've owned that supported battery idle mode. I'm too lazy to tweak a working Tasker project. Additionally, the battery is happiest at ~42% and the extended days I have when driving allows the battery to live there. Obviously, it's not practical if the device can not be plugged in all day.

Also, when I post here, I try to keep in mind that there many different devices. Many do not support battery idle mode and especially in those cases, I believe the battery is better served to be cycled at ~42% if plugged in for extended periods.

(Even though this is a device specific forum, it will be read by many people without the device)

 

[Skittles9823]

Fair question [emoji846]

There are two reasons. I've had my Tasker setup since ~2015. The P3XL (not P3aXL) is the first device I've owned that supported battery idle mode. I'm too lazy to tweak a working Tasker project. Additionally, the battery is happiest at ~42% and the extended days I have when driving allows the battery to live there. Obviously, it's not practical if the device can not be plugged in all day.

Also, when I post here, I try to keep in mind that there many different devices. Many do not support battery idle mode and especially in those cases, I believe the battery is better served to be cycled at ~42% if plugged in for extended periods.

(Even though this is a device specific forum, it will be read by many people without the device)

Huh. I didn't know about battery idle mode, thats great to know tbh.

Sent from my Pixel 3a XL using XDA Labs

 

[abialic]

Current/voltage limits not working.

Hello.
I have set current and voltage limits but AccA shows same values when accd is running or not.
Looks like those limits have not effect.
Does it mean that my kernel is not supporting it?

Device: Samsung Galaxy A51

Regards.

 

[Uzephi]

Hello.
I have set current and voltage limits but AccA shows same values when accd is running or not.
Looks like those limits have not effect.
Does it mean that my kernel is not supporting it?

Device: Samsung Galaxy A51

Regards.

Limits work on my Pixel 3a, so it might be kernel related or something else. This section is for the 3a. The main app thread is here: https://forum.xda-developers.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427

You might get a better answer there.