I’m a 12th Gen Batch 3. My charge-cycles should definitely not be 8. So, as others have found, maybe it’s 263?
11th Gen, Batch 2, original battery, almost daily use since November 2021:
DESIGN CAPACITY | 55,009 mWh |
---|---|
FULL CHARGE CAPACITY | 46,354 mWh |
Remaining battery capacity: 84.266%
Device: /org/freedesktop/UPower/devices/battery_BAT1
native-path: BAT1
vendor: NVT
model: 5 Framewo
serial: 0205
power supply: yes
updated: Tue 14 Jan 2025 06:17:50 PM
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: discharging
warning-level: none
energy: 38.6242 Wh
energy-empty: 0 Wh
energy-full: 53.0048 Wh
energy-full-design: 55.0088 Wh
energy-rate: 11.5346 W
voltage: 15.947 V
charge-cycles: 131
time to empty: 3.4 hours
percentage: 73%
capacity: 96.3570%
technology: lithium-ion
icon-name: 'battery-full-symbolic'
about 1 year old AMD FW 13… usually plugged in, set battery charge limit to 80%
Purchased January 2022, battery level kept between 75 and 80%, used daily, mostly plugged in at a desk. Swapped mainboards from the 11th gen i7 to an AMD board, so I expect that the cycle count is at least 1.5x-2x this.
Not bad I don’t think following a full drain and charge to 100%.
89% capacity left. My Framework is a little over a year old (AMD Batch 2). Daily use for multiple hours, no charge limit.
I think the battery is capable of retaining 80% after 1000 cycles as long as you don’t 100% for a year or but your computer in a hot place. However the battery management might do some shenanigans to negatively affect the capacity
I found the answer, the “drop” is likely due to the BMS deliberately lower the limited charging voltage after some time or cycle to use only a part of your battery’s capacity, this makes the user think the battery has degraded. The motivation of this is yet to known. If you have the opportunity could you please fully charge your laptop and read the voltage(while still plugged in)? If that voltage is significantly lower than 17.6V(such as 17.4V), then this is the exact problem. My 61Wh battery decided to “degrade” 9% by limiting the voltage from the original 17.8V to 17.6V. The same 0.2V drop is witnessed here(55Wh, 17.6~17.4V).
Note that the full voltage of the battery is no longer 17.6V but only 17.4V. If the original voltage is restored, your actual capacity is likely going to be 52~53Wh.
And here’s the graph, almost two years later, after less than 3 years of use:
You can see it never went back up to 100% after those drops, but the capacity oscillates between 78% and 88% in march. Here’s a zoom of the last month:
anarcat@angela:~> cat /sys/class/power_supply/BAT1/voltage_now
17380000
I guess that’s 17.38V? And would confirm your hypothesis. The battery is not fully charged right now though, I’m at 93% and charging, will try to remember to update this post when it’s fully charged.
My battery’s an 11th gen batch 5, and my capacity is at 84%. The FW battery has help up much better than any of the Thinkpads, so I can’t really complain.
I borrowed a 3y/o 55Wh battery and here are my readings, the hypothesis is confirmed.
ectool, note the low Desired Voltage
$ sudo ectool battery
Battery 0 info:
OEM name: NVT
Model number: Framework L
Chemistry : LION
Serial number: [redacted]
Design capacity: 3572 mAh
Last full charge: 3026 mAh
Design output voltage 15400 mV
Cycle count 1344
Present voltage 17173 mV
Present current 2480 mA
Remaining capacity 1469 mAh
Desired voltage 17400 mV
Desired current 2500 mA
Flags 0x0b AC_PRESENT BATT_PRESENT CHARGING
tlp
$ sudo tlp-stat -b
--- TLP 1.8.0 --------------------------------------------
+++ Battery Care
Plugin: generic
Supported features: none available
+++ Battery Status: BAT1
/sys/class/power_supply/BAT1/manufacturer = NVT
/sys/class/power_supply/BAT1/model_name = Framewo
/sys/class/power_supply/BAT1/cycle_count = 64
/sys/class/power_supply/BAT1/charge_full_design = 3572 [mAh]
/sys/class/power_supply/BAT1/charge_full = 3026 [mAh]
/sys/class/power_supply/BAT1/charge_now = 1474 [mAh]
/sys/class/power_supply/BAT1/current_now = 2476 [mA]
/sys/class/power_supply/BAT1/status = Charging
/sys/class/power_supply/BAT1/charge_control_start_threshold = (not available)
/sys/class/power_supply/BAT1/charge_control_end_threshold = (not available)
/sys/class/power_supply/BAT1/charge_behaviour = (not available)
Charge = 48.7 [%]
Capacity = 84.7 [%]
upower
$ upower -i $(upower -e | grep battery)
native-path: BAT1
vendor: NVT
model: Framewo
serial: [redacted]
power supply: yes
updated: Thu 13 Mar 2025 01:19:44 PM AEDT (13 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: charging
warning-level: none
energy: 22.638 Wh
energy-empty: 0 Wh
energy-full: 46.6004 Wh
energy-full-design: 55.0088 Wh
energy-rate: 38.1766 W
voltage: 17.168 V
charge-cycles: 64
time to full: 37.7 minutes
percentage: 48%
capacity: 84.7144%
technology: lithium-ion
icon-name: ‘battery-good-charging-symbolic’
History (charge):
1741832384 48.000 charging
1741832324 47.000 charging
1741832294 46.000 charging
History (rate):
1741832384 38.177 charging
1741832354 38.192 charging
1741832324 38.146 charging
1741832294 37.853 charging
A 95% health battery is “degraded” to 85% due to the max voltage lowered from 17.6 to 17.4
Despite this, the battery still has 84.7% capacity after 1344 cycles.
I hope this isn’t offensive, but the forum won’t let me remove my like from your post. I liked the numbers, but the idea that Framework’s lowering battery capacity artificially because the charging voltage is lower doesn’t follow.
Companies sometimes pull that kind of thing – printer manufacturers come to mind – but there’s nothing remotely suspicious here.
I don’t think Framework is the one who lowered battery capacity artificially. I think it’s just Framework didn’t know the battery supplier doing this because it’s being done very subtly
I acknowledge your attempt of removing a like from my post, and I agree that undoing likes(and votes) is slightly better in a forum as sometimes the person who liked the post changed their mind or sometimes the post got an edit and no longer likable.