So I’ve been using my FW16 for a little while now (around 2ish months) and, having switched over to KDE plasma, I just noticed that my battery health is at 88% already. I limited the max charge capacity to 80% almost all the time since I’ve gotten it, but I have put it though a lot of charge cycles due to it overheating significantly while charging. The strange thing is literally just yesterday it reported the battery health as 93%. Is this a KDE/battery health sensor issue or something I genuinely have to worry about?
(Also is there a way to bypass the battery entirely ie not charge it? Seems the overheating is located in the battery so directly powering the system might help idk)
The only way I know of to “bypass” the battery entirely is to physically disconnect it. Which might be a good idea in your case, since it sounds like it’s defective – I have two FW16s, and have had one of them for well over a year, and have never felt a significant amount of heat from the battery.
My recommendation would be to talk to Framework’s support people. They’ll be able to tell you what’s normal, and if your battery isn’t (as I suspect), can authorize a warranty replacement.
My battery health is at 65% with the charging limit at 90% since half a year.
I am not quite sure whether that is a bug or if the battery really lost 1/3rd of its capacity since I got the laptop.
I’m gonna check that by setting the charge limit to 100%, fully charge it and have a look at the reported capacity.
Edit: Interestingly, I had set the limit to 85% but KDE showed a charge of 90%…
I checked battery health using the KDE Information Center (or however it is called in english), inxi --battery and upower -i /org/freedesktop/UPower/devices/battery_BAT1
According to upower the battery only has 65 cycles but only is at 64,5% capacity
I changed the charging threshold to 100% in the bios, but it kinda stopped charging at 96%.
I then disconnected the battery, long pressed the power button and started charging it again.
