Low battery warning not working

Framework Laptop 13 Linux
1

I set the low battery warning to set off at 30%, when it drops it should decrease the screen brightness to 1%, it worked for a while (3/4 months) but now the brightness drops only when at critical level (automatic when at 1%).

It now says that the battery health is at 70%, I hope its some wrong readings because I just got this laptop (march 2026).

Ubuntu 26.04 LTS with intel core ultra 7 155H

Any suggestion on why it does this?

Thanks in advance

2

Would you add here a screenshot of what you’re looking at?

Has this always been an issue, since you’ve owned the device, or is a newly emerging problem?

3

What’s your desktop environment, different one has different way of setting the low battery warning

4

image
image1067×1046 112 KB

image
image695×295 20.4 KB

This has been happening only for the last couple of weeks, it used to work just fine.

As a desktop enviroment I have KDE plasma.

1 Like
5

Are you minded to think the low-battery behaviour is not kicking in as it should, or that the battery’s level is being misreported?

6

Hmm, I am wondering if a kernel update broke something. You could always try going back to earlier kernels to see if that makes a difference.

7

Mainly I am worried about the low battery behaviour, if it keeps dropping to < 1% the battery health will degrade faster and faster, I always try to keep it between 30-80.

The battery health problem is more a concern, after charging the laptop it got back up to 100%, maybe it was just a wrong reading.

8

Actually, discharging to a low percentage gives less wear than charging to a higher percentage i.e. wear level 50-100% > 0-100% > 0-50%. The “center” should be 20-70% rather than 30-80%. However, if the battery health is declining rapidly despite you keeping it between 30%-80% the battery might be faulty

9

I have waited yet another battery cycle to collect more details, and discovered that the low battery behaviour does not trigger because as soon as the battery drops from 30% it goes directly to 0% and the critical battery sequence triggers in, saying it will shut down in 60 seconds.

So it all comes down to the battery percentage readings that might be wrong.

Is that a battery problem or a software bug?

10

I see you are using KDE-Plasma. Go to the Energy - Info Center and observe the battery voltage. Take note of the voltages when reaching 30% and 0%.
Additionally, you can use framework-control Framework Control (Linux/Windows) - A tool for: Fan Control (Curve), Sensors, Power Control, Battery Information
This command framework_tool --smartbatterygives you the battery’s health status and voltages of each cell

11 
Manuf Date:    2025-11-11
Chemistry:     LION
Mode:          0x6001
Temperature:   32.0C
Voltage:       14.665V
  Cell 1:      3.661V
  Cell 2:      3.670V
  Cell 3:      3.671V
  Cell 4:      3.664V
Current:       -0.339A (avg -0.342A)
Charge:        40% (1054 / 2685 mAh)
Design:        3915mAh @ 15.480V
Bat Status:    0x00C0 [DSG (Discharging), INIT (Initialization)]
Cycle Count:   110

=== Battery Health Analysis ===

Status: GOOD (with notes)
  Note: Significant capacity degradation: 69%

Summary:
  Cycle count: 110
  Capacity: 2685 / 3915 mAh (69%)
  Current cell balance: 10mV spread

It does say 69% degradation but the Framework Control GUI says “charge to 100% to recalculate battery health”, I’ll update with the results later

In the info center:
14,50±0.2 V while above 30%
12.00± 0.2 V shortly after dropping below 30% (straight to 0%)
I also tried to record the 30 to 0% drop, but it instantly interrupts the screen recording. I guess it stops not system process

12

Your battery is balanced, which is good.

3.6V should be about 5% charge, not 40%

Because 12.0V (3.0V per cell) is the discharge cutoff voltage.

1 Like
13

Update after charging it to 100%
I feel like this should not be possible

Manuf Date:    2025-11-11
Chemistry:     LION
FW Version:    Device=0x0045 FW=09.03 Build=0x4900
Mode:          0x6001
Temperature:   36.9C
Voltage:       17.454V
  Cell 1:      4.352V
  Cell 2:      4.353V
  Cell 3:      4.355V
  Cell 4:      4.394V
Current:       2.086A (avg 2.073A)
Charge:        99% (4031 / 4072 mAh)
Design:        3915mAh @ 15.480V
Charging:      2.740A @ 17.600V
Bat Status:    0x0080 [INIT (Initialization)]
Cycle Count:   111

=== Battery Health Analysis ===

Status: HEALTHY
  No issues detected. Battery is operating normally.

Summary:
  Cycle count: 111
  Capacity: 4072 / 3915 mAh (104%) <-- ???
  Current cell balance: 42mV spread
14

Continue charging until this value hits 0.000A

15 
Manuf Date:    2025-11-11
Chemistry:     LION
FW Version:    Device=0x0045 FW=09.03 Build=0x4900
Mode:          0x6001
Temperature:   32.2C
Voltage:       17.580V
  Cell 1:      4.394V
  Cell 2:      4.395V
  Cell 3:      4.396V
  Cell 4:      4.395V
Current:       0.000A (avg 0.047A)
Charge:        100% (3920 / 3920 mAh)
Design:        3915mAh @ 15.480V
Bat Status:    0x40A0 [FC (Fully Charged), INIT (Initialization), TCA (Terminate Charge Alarm)]
Cycle Count:   111

=== Battery Health Analysis ===

Status: GOOD (with notes)
  Note: Terminate Charge Alarm active

Summary:
  Cycle count: 111
  Capacity: 3920 / 3915 mAh (100%)
  Current cell balance: 2mV spread

now what

16

It should be calibrated by now

1 Like