Battery mot charging past 54%

[StickyPine]

Hello,

I juste got the PinePhone but the battery does not seem to be charging past 54%.

I saw on the wiki that some OS' limit the maximum charging percentage in order to improve the longevity of the battery. Because I'm having this issue on different OS' it got me thinking that it is a hardware problem, but it might not be.

Is it a known issue ? What can I do about it ?

Many thanks !

[dsimic]

I'm not aware of this being a known or already reported issue.  To aid in debugging, you could check the battery voltage when charged to 54%, which is available through /sys, and report back here.

[8bit]

Code:

cat /sys/class/power_supply/axp20x-battery/uevent
cat /sys/class/power_supply/axp20x-usb/uevent

[dsimic]

Actually, @8bit , those aren't the correct paths.  See below for the right ones:

Code:

/sys/class/power_supply/axp20x-battery/capacity
/sys/class/power_supply/axp20x-battery/voltage_now

For example, battery voltage on my PinePhone was reported as 4015000, while the battery capacity was reported as 79.  After the reported capacity dropped to 77, the reported voltage dropped to 3999600.

[8bit]

Does the output of uevent not match the individual readings on your device?

Code:

cat /sys/class/power_supply/axp20x-battery/uevent
POWER_SUPPLY_NAME=axp20x-battery
POWER_SUPPLY_TYPE=Battery
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_VOLTAGE_NOW=4224000
POWER_SUPPLY_CURRENT_NOW=205000
POWER_SUPPLY_CONSTANT_CHARGE_CURRENT=1200000
POWER_SUPPLY_CONSTANT_CHARGE_CURRENT_MAX=1200000
POWER_SUPPLY_HEALTH=Good
POWER_SUPPLY_VOLTAGE_OCV=4203100
POWER_SUPPLY_VOLTAGE_MAX_DESIGN=4200000
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3000000
POWER_SUPPLY_CAPACITY=89

cat /sys/class/power_supply/axp20x-battery/voltage_now
4224000

cat /sys/class/power_supply/axp20x-battery/capacity
89

[dsimic]

Ah, you're right, @8bit, sorry...  I have a small shell script that pulls and displays a few parameters, and I run it using "watch -n 1", so I need the paths to the exact parameters for the script.  Thus, I somehow mentally disregarded the paths to the group/device parameters you've posted earlier.

[StickyPine]

I'm not aware of this being a known or already reported issue.  To aid in debugging, you could check the battery voltage when charged to 54%, which is available through /sys, and report back here.

Thanks for the quick reply !

I left the phone charging for more than 24h and this issue seems to be gone. I don't know how to replicate it. But now when the phone reaches ~90% it starts discharging, although the cable is still plugged in.

I'm getting a bit confused about this...

[marcih]

I'm not aware of this being a known or already reported issue.  To aid in debugging, you could check the battery voltage when charged to 54%, which is available through /sys, and report back here.

Thanks for the quick reply !

I left the phone charging for more than 24h and this issue seems to be gone. I don't know how to replicate it. But now when the phone reaches ~90% it starts discharging, although the cable is still plugged in.

I'm getting a bit confused about this...

The discharging is intentional; If I remember correctly, the charging rate slows down at 80% and stops completely at 90%.

[dsimic]

I left the phone charging for more than 24h and this issue seems to be gone. I don't know how to replicate it. But now when the phone reaches ~90% it starts discharging, although the cable is still plugged in.

It's a bit strange that the battery initially didn't charge past 54%, but let's grudgingly accept that it got resolved spontaneously.  Maybe the battery needed some time to start accepting full charge, although it's still a bit strange.

Stopping the battery charging around 87-90% is the expected behavior, as it improves the longevity of the battery.  Also, that prevents the battery from overheating while charging, although there's very small possibility for the overheating in the first place.

[StickyPine]

Also, that prevents the battery from overheating while charging, although there's very small possibility for the overheating in the first place.

Is there a way to change this behavior ?