From my experience with lithium batteries it’s more like a lot initially and then tapers off and then a lot later a lot again, kinda s-curve ish. But anyway I’d be very careful extrapolating.
I’m sitting at just over 200 cycles and a wear level of 6%. Battery is about 2.5 years old (Batch 4 11th gen Intel). I mostly use it as a mobile workstation when I’m away from the office, maybe a couple hours a day 2-4 times a week, otherwise it’s plugged in intermittently set to 80% battery charge threshold, with the charge threshold disabled when I’m traveling. Can’t really complain with how it’s held up in my use case.
energy-full-design: 55.0088 Wh
energy-rate: 0 W
voltage: 17.336 V
charge-cycles: 26
capacity: 86.0582%
i guess not bad for a 2 year old laptop that i have used wildly and continuously. 26 cycles are a lie, it definitely reset after the mobo upgrade.
Just handed my 2021 batch 5 i5 off to a friend. Did a full battery cycle just to check everything out before it went to it’s new owner.
charge_full was 3042 , or ~47Wh / 55Wh available, ~85% of original capacity
After ~27 months in service, many partial but very few full cycles, 100 percent charge limit at first until BIOS allowed lower, 60 percent most of the time at that.
I think it needs to be restated that the wear is not exactly linear, and often measured incorrectly by the laptop!
How did you get the history?
for windows, that’s powercfg /batteryreport
Done any full change/discharge cycles lately?
You may need to fully discharge it in this case, like won’t turn on without the power adapter discharge.
If that doesn’t improve the readings it may be time to hit up support.
Not necessarily. Most laptops, at least all laptops I used previously, have their lower calibration point at 7% i.e they will either discharge suddenly to 7% or stay at 7% for a long time if the laptop is unplugged and the battery’s capacity meter has drifted
What’s the voltage of the battery at 5% assuming you are not running resource intensive task
Never had one do that at 7% all the laptops I have previously done the full discharge/charge dance with have tended to hang in there below 5%, usually 0 or 1%.
Ideally they should implement an explicit battery re-calibration in the ec like the thinkpads have where it discharges and charges the battery while connected to power.
It is a bit ironic that charge limits that reduce battery wear also tend to make the wear readout look a lot worse than it actually is XD.
Sorry, my memory must be incorrect. Will do my own research in a few days. Stay tuned
Has anybody here got more than 255 cycles recorded on their battery?
My 11th gen 13" battery cycle count seems to have been “reset” and now shows single digit cycles after reaching 255 cycles and while it could be a coincidence I think that value could be a clue (0-255 values per byte).
I’m at 232 cycles. Remind me in 2025
I’m now at 7 “cycles”, down from 247, interestingly, without the count passing through any of the other numbers that you would expect.
I’ve had a script logging some stuff from /sys/class/power_supply/BAT1/
since January, and the cycle count has been weird. It’ll pick a number, stick to it for several days, and then jump to a later number, skipping some range of integers that you’d have expected to see.
… went from 198 to 207. 217 to 229, 232 to 247.
that calculation doesn’t seem to have enough precision behind it to count individual cycles. I didn’t think I was using the battery that much, either… wonder what it’s counting.
Alright, gotcha. No flying elephants, only pink pigs. or flying pigs. I’ll make sure to avoid thinking of at least one of those. might have to concentrate on Floyds for prophylaxis.
Now there are at least 2 of us!
My cycles would only updated after a reboot or shutdown, does this track with your experience?
Since my “reset” cycles climbed as expected but got stuck at 29 and currently 42 regardless of reboots or shutdowns so I decide to contact support:
We took a quick look at our EC code, and it looks like this value is read as the full 32bit value which is then mapped into the host. You can see: GitHub - FrameworkComputer/EmbeddedController: Embedded Controller firmware for the Framework Laptop - Which value is read from the battery and saved into a MMIO region at EC_MEMMAP_BATT_CCNT using 4 bytes. With this, we do not believe it is a rollover bug.
The point at which the value reset is quite similar however so something seems to be going on. Are you also an 11th gen user?
Keep a sharp eye on the land as well as the sky for a pink pigface to save your battery from hallucinating it’s cycles.