I used it fully on-charge at no cap for a month or so, capped at 80 and fully on-charge for around six months, and then the past few months back at no cap with daily on-battery use.
SleepStudy says my effective capacity is 94%, so I’m very impressed. I typically get 6 hours of note taking/web browsing and then charge it back up for some more use before leaving it charging overnight. The battery life itself has been pretty consistent in that respect, but I’d still be first in line to buy a drop-in battery upgrade.
So my battery wear has taken a pretty drastic turn the past few months. My batch 4 1135 running Win 11 went from 4% to 2% from last October to this August, but the end of September gave me 7%, which I think is fine and within likely error, but today it checked in at 12.1%. I did a calibration 5%-100% charge the last few checks to try to be consistent. Anyone else have “sudden” wear like this?
I haven’t checked on a consistent basis like @anon81945988 and can’t say how many cycles I’ve been through, but my use (4-6 hours on battery workdays) hasn’t changed drastically.
I have an 11th gen framework from 11/2021(1.25 years old). My battery stats are:
80 cycles
capacity of 96.0246%
BIOS charge capped at 80%
It’s on 24x7, and most of the time it’s plugged in. The usage is mostly light(web browsing/text editing/email) a couple hours a day.
Everything seems fine so far. I surely worry about the battery far more than I need to. Especially considering it’s so inexpensive and easy to replace if there’s ever a problem with it.
I took the battery out of the laptop to look for a manufacturing date on the bottom(I couldn’t find one). It was securely held in with screws and plastic tabs instead of god awful adhesive. The screws were numbered and captive(impossible to loose). It’s hard to imagine a significantly more user friendly experience!
12th gen i7-1260p here.
After 4 months (received 13 Oct. '22) my battery capacity is currently reading as 98.5162%.
Only 9 charge cycles used.
Plugged into mains power > 95% of the time.
Charge limited in UEFI settings menu to 65%.
In the first week to 10 days I used it regularly off mains power and was charging it to 100 %; within the first week the battery capacity dropped to about 94.5%.
I did a bit of reading up on the battery here and did a couple of full discharge/recharge cycles and set the charge limit in the UEFI settings. Since then the laptop is rarely used off mains power and with the 65% charge limit the capacity reading has climbed back to about were it was when first used at about 98.5%.
12th Gen i7-1260p. I’ve found that the indicated battery wear is completely inaccurate. It goes up to 10% or so when gaming, and drops back down to 2% when idling. Currently indicating 4% while I’m typing this.
Part of the reason is that it seems to miscalculate battery wear when the laptop is drawing more power than what the charger can provide.
I have had a Pixelbook for 4 1/2 years. When I first got it I researched this
question but found no decisive answer as to constant vs nonconstant
charging, so I keep my computer charging during the day and off at night.
After 853 cycles the battery health is 79%. The length of retaining a charge
when not plugged in has dropped somewhat, but has never been an issue
for me. When the battery dies, I intend to replace it or buy a Framework.
Both the battery health and wear counts are inaccurate so there is no real use in graphing it as it may cause fear to newcomers thinking that the batteries are very low quality.
After a bit more than 1 year of ownership used mostly plugged in with a 75% charge limit I’m down to 90.3% capacity. My reported cycles are 104 but my cycles were stuck for some time so it is hard to estimate that accurately but I would put them closer to 120 than 104.
I have not done a full charge very recently but I will try that and see how much this value changes.
I don’t have records of the initial capacity however I remember it was below 100% (54.XX Wh). I have a record two months after purchase with a value of 98.4%, 9 days later 97.3% and 40 days after that 97.1%.
Edit: Seems I made a prior post before forgetting my OOTB value.
Let’s see if I’m wrong and in 2 months time have fallen below the 80% mark did I get a bad battery or is the charge limit behaviour causing some degradation? I’m very carefuly to not stress the battery with heat or deep cycles/fully charging it… My old iphone 3GS had 86% after 500 cycles…
We use Kustomer as our ticketing system and have since our inception. Any frame.work domain linking to support is simply a mask as we’re utilizing Kustomer’s cloud platform. This is common practice. Knowledge Base/Support Tickets… Kustomer. Guides… Dozuki. Bugs… Jira. Welcome to 3rd Party tooling and platforms for business.
Here is a good video I found awhile back explaining the various ways that lithium ion batteries undergo physical damage and degradation. Very thorough, but I do not know for sure how many of these processes are applicable to the lithium polymer batteries sold by Framework.
I just did a deep discharge and recharge cycle, followed by a couple of more 90-100% cycles to see if it would get any more in the top end. /sys/class/power_supply/BAT1/charge* reports 3084000/3572000 = 86.3% SOH. 1.4 years in service, usually charged to 75%, not sure how many full cycle equivalents but I’m going to guess maybe 300ish.
Glad replacement batteries are available-ish in the marketplace. Will be looking forward to upgrading to the 61Wh and moving this battery to the router/wireless AP/NAS unit instead.
I think you are reading too much into this. This data is mostly within measuring tolerances and by undercharging so much you really should not have any measurable wear jet.
Since I don’t exactly know how your full charge process works I’ll just have to guess you don’t discharge to complete empty with a constant load so the zero point of the fuel-gauge in the battery just keeps drifting downwards with every time which explains your graph.
And even if you do discharge till the battery turns off if you have different wear you’ll get different 0 points because the voltage sag is different.
Would be neat if the framework ec got the battery re calibrate mode thinkpads have where you can leave the laptop plugged in and it discharges and then fully charges the battery itself giving very consistent results.
Sorry in advance, this may turn into a bit of a semantic debate but in this case it’s important to define terms accurately so we are not talking about different things.
Yeah but not HOW you do a full discharge, this part is important because if you don’t go all the way to empty those watthours will be missing in the total. If you just discharge till the is shuts down that would pretty nicely explain your graph creeping downwards each time.
There is 2 was to look at it, for one there is actual wear (the one I am talking about) where the battery cells loose capacity and get higher internal resistance and self discharge and then there is the wear reported by whatever tool you are using which is the difference between the design capacity and the capacity the battery controller thinks it has (which I think is what you are talking about).
The fuel gauge in the battery basically works like this, it has a coulomb counter so it basically counts the energy that goes in and out and updates the “capacity now” value based on that. when it is charging it increments, when discharging it decrements. Of course that process isn’t perfect and so that drifts over time and might over and under report. when you fully discharge (like fully fully) it counts down till it is at zero and then keeps going until the cell voltages reach the cutoff point, which is why when you re-calibrate a really confused thinkpad battery or a battery where you swapped the cells the battery percentage stays at 0% for a long time. Once it actually emptied it starts counting from actual zero and you should get a pretty accurate capacity. Note that the actual capacity of the battery did not change just the measurement of it. And even that may not be exactly the same run to run if you don’t control the discharge rate because the battery voltage sags based on load which makes it reach the min faster on higher loads. Also some battery controllers get confused if the actual capacity is higher than the programmed design capacity XD, I once put 120wh worth of cells onto a 24wh thinkpad battery and boy was that controller a dick about it, it just capped the measured capacity at 24wh and then just stuck at 0% for hours.
Never going to 100% or fully empty does lead to accumulation of errors in the measured capacity but it does cause less actual wear.
I bet your test cycles put more wear on your battery at this point than your normal use XD
