Battery level not managed on ASUS VivoBook / Ubuntu 24.04

[yveshu]

Hello,
Previously this extension worked file. Thanks!

But recently (I don't know exactly when), the battery level climbs up to 100%. I don't see any message or error. Can you solve this issue? If you need it, I can help you with informations or tests. My current version is 79.

Thanks again!

Yves

Rapport d’informations du système

Détails du compte rendu

• Date de génération : 2026-03-11 17:01:21

Informations liées au matériel :

• Modèle du matériel : ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop M1605XA_M1605XA
• Mémoire : 56,0 Gio
• Processeur : AMD Ryzen™ 9 7940HS w/ Radeon™ 780M Graphics × 16
• Carte graphique : AMD Radeon™ 780M Graphics
• Capacité du disque : 1,0 To

Informations liées au logiciel :

• Version du micrologiciel : M1605XA.308
• Nom du système d’exploitation : Ubuntu 24.04.4 LTS
• Construction du système d’exploitation : (null)
• Type de système d’exploitation : 64 bits
• Version de GNOME : 46
• Système de fenêtrage : Wayland
• Version du noyau : Linux 6.17.0-14-generic

[maniacx]

Apologies for the late reply.

We need to check if the problem is caused by the GNOME extension or by the system (kernel update or firmware update).

Please follow the steps exactly. Copy and run the commands in a terminal.

STEP 1 — Find your battery power supply name

Run the command:

ls /sys/class/power_supply/

You will see several names. Example:
AC0
BAT0
BAT1
BATC

Your battery name is usually BAT0 or BAT1.

In the next commands, replace BAT0 with the battery name you found.

Example:
If your battery name is BAT1, replace BAT0 with BAT1 in all commands.

STEP 2 — Check the current charging threshold

Read the current threshold value:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

Note the number that appears.

Now open the GNOME extension settings and set the charging mode to:

Balance (80%)

After changing the mode, read the value again:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

Check if the number printed by the command matches the extension setting.

For example:
Balance mode should show 80.

Now repeat the same process for the other modes.

Set mode: Maximum Life (60%)

Run:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

Expected result: 60

Set mode: Full Capacity (100%)

Run:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

Expected result: 100

If the numbers match the extension settings, then the GNOME extension is working correctly.

STEP 3 — Test setting the threshold using the command line

Now we test if the system accepts threshold changes directly.

Set threshold to 60:

echo 60 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Read the value:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

The result should be 60.

Now set threshold to 80:

echo 80 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Read again:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

The result should be 80.

Now set threshold to 100:

echo 100 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Read again:

cat /sys/class/power_supply/BAT0/charge_control_end_threshold

The result should be 100.

If all values change correctly, continue to the next test.

STEP 4 — Test real charging behavior

Unplug the charger.

Drain the battery until the level is around 85%.
Anywhere between 82% and 87% is fine.

Check the battery state:

upower -i /org/freedesktop/UPower/devices/DisplayDevice | grep -E "state|percentage"

Now plug in the charger.

Immediately run this command to set the threshold to 80:

echo 80 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Check the battery state again:

upower -i /org/freedesktop/UPower/devices/DisplayDevice | grep -E "state|percentage"

Expected result:
state should show "discharging".

This means charging stopped because the threshold is 80%.

Now change the threshold to 100:

echo 100 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold

Check the battery state again:

upower -i /org/freedesktop/UPower/devices/DisplayDevice | grep -E "state|percentage"

Expected result:
state should show "charging".

Result Interpretation

If setting threshold to 80% still shows "charging", the problem is likely caused by the kernel or firmware.

This sometimes happens after BIOS or firmware updates.

One possible solution is to reset BIOS settings to factory defaults. Some firmware updates can leave incorrect values in the Embedded Controller (EC).

Optional Extension Settings

You can also try enabling the setting:

Skip threshold verification

Some ASUS users reported that the threshold does not apply after resuming from suspend, sleep, or hibernation. Enabling this option helped them.

[ChrisHul]

Hi, having similar problems with an ASUS Zenbook (running Debian Trixie):
description: Notebook
product: ZenBook UX434DA_UM433DA
vendor: ASUSTeK COMPUTER INC.
version: 1.0
serial: xxx
width: 64 bits
capabilities: smbios-3.2.1 dmi-3.2.1 smp vsyscall32
configuration: boot=normal chassis=notebook family=ZenBook uuid=80070084-a7a8-b049-8fa6-43aaf58b5783
*-core
description: Motherboard
product: UX434DA
vendor: ASUSTeK COMPUTER INC.
physical id: 0
version: 1.0
serial: xxx
slot: MIDDLE
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: UX434DA_UM433DA.309
date: 10/09/2021
size: 64KiB
capacity: 8MiB
capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification uefi

Did reset BIOS to default. No settings available for "smartbattery".

Using the "skip threshold verification" activated.

I executed( I have AC0, BAT0): echo 60 | pkexec tee /sys/class/power_supply/BAT0/charge_control_end_threshold
Returned back: 60. The GUI also reflects that.

upower -i /org/freedesktop/UPower/devices/DisplayDevice | grep -E "state|percentage" returns:
"pending-charge" when percentage < 90 - native battery indicator says not charging
"discharge/fully-charged" when percentage >= 90

The 90 percent limit seems to be governed by the native battery control. Currently I have it set on a health charge scheme, but when I change it to maximum charge it will charge until reaching 100%.

Previous experience has shown that eventually the battery will end up at 100%, and my impression is that it happens during hibernation. Once it gets there it will not go down unless power is disconnected.

upower -m:
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
[12:36:13.266] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:13.267] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:13.267] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:13.267] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:43.305] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:43.305] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:43.305] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:43.305] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:36:43.305] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:37:13.341] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:37:13.341] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:37:13.341] device changed: /org/freedesktop/UPower/devices/battery_BAT0
[12:37:13.341] device changed: /org/freedesktop/UPower/devices/battery_BAT0

It appears to me that the module has lost control of the charging unit and its thresholds. I'll be happy to carry out further testing if requested to do so.

Regards, Chris

[maniacx]

Thank you @ChrisHul

Yes above 90% UPower will report pending-charge as fully-charged

I did some searching. And it seem like latest model / firmware updates they have remove the option for 60%.
So setting any values below 80% does not work I guess on these models.

In you system, setting charging threshold to 60% still charges battery up to 100%. correct?

Could you set charging threshold to 80% and check if battery level stay at at 80%?

If that too doesnt work try resetting Embedded Controller using this method.

https://www.asus.com/support/faq/1050239/

It may take a little longer to boot the first time after this procedure.

[ChrisHul]

Thank You @maniacx for prompt response,

I went another route and made a few discoveries.

First of all: "discharge" is not supported on my computer. It means that the only way to get the power level downis by disconnecting the mains power. Other computers with "discharge" option will be able to regulate the power level in a more efficient way.

upower seems to have default values 75/80%( charge-start-threshold/charge-end-threshold), which would be active until set otherwise.

I actually got everything working by doing the following:

I uninstalled the "tlp" module (which I believe was installed to do the same thing as the extension, possibly creating glitches):
sudo apt purge remove tlp

Setting upower start/end values to 40/50 with configuration file (following https://linuxconfig.org/using-custom-charge-thresholds-with-gnomes-preserve-battery-health-feature):
sudo nano /etc/udev/hwdb.d/61-battery-local.hwdb
adding the following:
battery:::dmi:*
CHARGE_LIMIT=40,50

rebooting, and now it works (also 60%). However, the extension does not seem to detect resumption from suspend/hibernate, so upower will restart with 40/50 values instead of extension settings. Maybe worth looking into ( I have no experience with extension programming).

Answering your question about if the battery ended up fully charged: Yes, but only over time, a week or so, treacherously, like trickle charging. I believe it was due to glitches from other software (maybe tlp) with 100% end-value. The effect of not having a discharge function made the charge level to stay high.

Hopefully all this makes sense to you. Will gladly clarify if needed.

Best regards.

Edit:

Forgot to mention the built-in battery control ( Gnome >= 48; release date March 20, 2025 - and said to be included in Ubuntu 25.04 ->). The control is found in Settings->power->general. Two radio buttons make up the choice betwen 'full charge' and 'preserve battery health'. It is recent enough to account for some racing effect with the extension. At some point I probably found the control (it available in my Debian distro) and I set it to the preservation mode. Still, it may try to compete with the extension and produce erratic behaviour.

In any event I'm happy with the extension because it has more setting options and after the modifications cited above the charge level stays at 60% as requested.