Question about low battery capacity (~66/67%) after just 77 cycles

For what it is worth, you may have more than 77 cycles on your battery. There is a bug in the firmware[1] which results in the cycle counter wrapping around every 256 cycles.


  1. Note that despite it claiming it applies to the 7040-series, it applies to all extant Framework devices with batteries. ↩︎

You are not alone with this issue.

I only use my FW16 a few times a year, and I noticed my battery health dropped from 99% to 73%a few months ago after I removed the charge limit from 60%. It also coincided with the battery discharging to 0% because of sleep, so I am not sure which of these two events is the culprit. It is extremely disappointing as my battery has only 59 charge cycles.

native-path: BAT1
vendor: NVT
model: FRANDBA
serial: 0188
power supply: yes
updated: Tue 27 Jan 2026 00:43:48 AEDT (3 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
warning-level: none
energy: 61.7962 Wh
energy-empty: 0 Wh
energy-full: 62.4308 Wh
energy-full-design: 85.0007 Wh
voltage-min-design: 15.48 V
capacity-level: Normal
energy-rate: 9.89172 W
voltage: 17.162 V
charge-cycles: 59
time to empty: 6.2 hours
percentage: 99%
capacity: 73.4475%
technology: lithium-ion
icon-name: ‘battery-full-symbolic’

In my case I have a wf16 gen1. it have +18 month and it most of the time plug on power… I config the battery charge limit @60%…

Yesterday I get that

~$ upower -b
Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  vendor:               NVT
  model:                FRANDBA
  serial:               03E2
  power supply:         yes
  updated:              lun. 26 janv. 2026 21:20:53 (26 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               pending-charge
    warning-level:       none
    energy:              56,471 Wh
    energy-empty:        0 Wh
    energy-full:         80,5734 Wh
    energy-full-design:  85,0007 Wh
    voltage-min-design:  15,48 V
    capacity-level:      Normal
    energy-rate:         0 W
    voltage:             16,35 V
    charge-cycles:       40
    percentage:          70%
    capacity:            94,7915%
    technology:          lithium-ion
    icon-name:          'battery-full-charging-symbolic'

Then I change the charge limit for 100% charging, have a full discharge + a full charge (and wait >2h for full charge)

That way the qualibration is donne, and the cell re-balanced. After that I get:

~$ upower --battery
Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  vendor:               NVT
  model:                FRANDBA
  serial:               03E2
  power supply:         yes
  updated:              mar. 27 janv. 2026 19:57:34 (14 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               fully-charged
    warning-level:       none
    energy:              82,2452 Wh
    energy-empty:        0 Wh
    energy-full:         82,2452 Wh
    energy-full-design:  85,0007 Wh
    voltage-min-design:  15,48 V
    capacity-level:      Normal
    energy-rate:         0 W
    voltage:             17,64 V
    charge-cycles:       41
    percentage:          100%
    capacity:            96,7583%
    technology:          lithium-ion
    icon-name:          'battery-full-charged-symbolic'
  History (charge):
    1769540224	100,000	discharging
    1769540224	0,000	unknown
  History (rate):
    1769540254	0,000	fully-charged
    1769540224	3,421	discharging
    1769540224	0,000	unknown

Note: the full discharged battery reported:

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path:          BAT1
  vendor:               NVT
  model:                FRANDBA
  serial:               03E2
  power supply:         yes
  updated:              mar. 27 janv. 2026 01:50:13 (8 seconds ago)
  has history:          yes
  has statistics:       yes
  battery
    present:             yes
    rechargeable:        yes
    state:               discharging
    warning-level:       action
    energy:              1,87308 Wh
    energy-empty:        0 Wh
    energy-full:         83,1431 Wh
    energy-full-design:  85,0007 Wh
    voltage-min-design:  15,48 V
    capacity-level:      Critical
    energy-rate:         18,158 W
    voltage:             13,502 V
    charge-cycles:       41
    time to empty:       6,2 minutes
    percentage:          2%
    capacity:            97,8146%
    technology:          lithium-ion
    icon-name:          'battery-caution-symbolic'

So you can get a full battery cycle and after re-callibration / cell re-balanced you may get better capacity.

After that, may advise.

  • if you have mobility need, the “best” is to have a 20/80 charge (or 10/90 if need more…)
  • if you use it a home, keep it powered and limits charging @60% is the best.

Thank you to everyone who suggested a battery calibration.

I discharged my battery completely, waited a few hours and then charged it back to 100% before turning on my FW16 and the battery health/capacity is now updated to 94%. There also seems to be some other bug related to limiting the battery charge limit to and from 100 to any lower number, as when I limited the charge again to 60% with power adapter connected, within a few minutes of use the battery charge percentage went from 100% down to 61%. One would expect it to normally discharge to ~60% and stay there, not so drastically go down to 60%.

I hope Framework adds this in their knowledgebase/FAQs, and perhaps a future update can improve on this.

It is actually by design. I don’t exactly know why FW do it that way. But changing the limit from 100% to 60% actually forces a discharge of the battery even if the PSU is connected.

I even changed the EC firmware code on my laptop, so that it does not do that particular “feature”, and acts how you would have assumed it would, as you describe.

Also, on Lithium Ion batteries, do not do full charge cycles to recondition them. That damages them more. Just charge them to 100% for a few hours, they re-calibrate themselves and return to normal. Full charge cycles was appropriate for those old Nickel Metal batteries, but terrible for Lithium Ion batteries.

This makes sense to me. If you are setting the battery limit to 60%, most people will expect it to discharge down to that limit instead of staying at 100%, thereby ignoring the user’s request. I think @Asad1 is saying it jumped down to 61% faster than electrically possible so he’s wondering why.

And nothing wrong with a full battery discharge. These batteries have protection circuits to prevent discharging to damaging levels.

In my case at 2% discharge the battery cell what 3,3755V … it is really safe ! I can on most get down to 3V without damage.
There is some margin, the BMS will shutdown the power, and keep energy so you won’t damage if you did not charge it quickly. (I think…)

That makes sense, except that it dropped to 60% in like 10 minutes or so, which suggests a bug to me. I will note down the exact time it takes next time I charge it to 100%

The “force discharge” does just that, it discharges the battery as quickly as possible, even if the laptop is idle. Essentially wasting charge.
That is why I do not like it.