Just adding my personal experiences with this issue to the thread…
I have a 2023 Framework 13 (12th Gen Intel) that I initially installed Ubuntu 22.04 on, and later upgraded to Ubuntu 24.04.
I’ve been having a similar issue with the battery charge sporadically reporting a value below 10% for a second or two before going back to 90+%. The graph of the charge (according to the “Power Statistics” application) looks like this.
I see this behavior whether I’m discharging the battery or have my power adapter connected. I have set my battery charge limit in the BIOS to 96%, which is why the graphs never get to 100%.
I changed my battery from the 55Wh unit to the 61Wh unit about 2 months ago, and have continued to see this issue.
I saw the issue when I was running Ubuntu 22, and have continued to see the issue after upgrading to Ubuntu 24.
I’ll have to check and see if I see the cros_ec_lpcs cros_ec_lpcs.0: packet too long error that others have reported seeing in dmesg.
Just want to report I’ve also been seeing this regularly on an 11th gen i5. I very rarely use my laptop without the charger plugged in. Max battery percentage is set to 85% and I use either the Framework charger or a Steam Deck charger which both keep the laptop at 84 or 85%.
Every 20 mins to half an hour I get a random single-digit battery percentage reported, asking me to shut down or hibernate, and the following messages:
[97327.451094] cros_ec_lpcs cros_ec_lpcs.0: bad packet checksum f7
[98371.937386] cros_ec_lpcs cros_ec_lpcs.0: bad packet checksum f7
I’ve had these or the “bad packet length” messages for the memorable past (at least a year, maybe 2) and I’m somewhat surprised it hasn’t been fixed yet.
I’m seeing this (Latest Kubuntu LTS, 15-1135g7 FW 13) too. sometimes KDE will just send me notifications about low power and the status bar icon will show a battery empty symbol. if i unplug something like an ethernet card it recalculates itself and seems to figure itself out but i definitely worry that it will shut down my computer at some point (and i suspect it already has a couple times when i wasnt around to react quickly enough)
I’m seeing a similar error on my AMD HX 370 Framework 13, where when I transition to battery power, I will get a battery critical warning, even though the laptop is at 90% charge.
This is with Fedora 42 and KDE Plasma 6.4.4, kernel 6.15.10-200
I have experienced this a few times in the last couple days as well. I have the Framework 13 with AMD Ai 350 cpu. And I am running arch Linux kernel 6.16.1. I don’t need to be transitioning from charge to battery. It has only happened to me while on battery power so far. Once when the battery was at around 70% it went to 0% and popped up a critical warning and was going to hibernate. I hit cancel and the battery went back to the proper reporting. Then it happened again around 23%
Looks like I’ve got the same issue (Bluefin, FW13 Ryzen AI 300 series). The laptop doesn’t shut down, but I get a popup saying the battery is empty… which disappears as soon as it pops up.
Luckily, the laptop doesn’t shut down, so it’s a purely visual bug in my experience so far.
Just to chime in, I’m having the same issue on CachyOS with kernel 6.17.7-2-cachyos running KDE Plasma. I’ve only had my framework 13 for a few days now, but it happened for the first time today. Not sure if it’s a regression regarding the fix @jubnut linked or something else entirely.
Same issue here on EndeavourOS running KDE Plasma, on a Framework 13 Ryzen AI 340. Took the laptop off the charger at 100% and was using it for a minute or two when the critical battery level popped up and the percentage dropped all the way to 0% and then back to 99% under 2 seconds.
I’m also having this problem with the “Battery is empty” notification popping up ever so briefly and then disappearing. So far the computer has not actually turned off when this happens. Only happens when the computer is not plugged in to power, and sometimes multiple times per hour.
Framework 13 with AMD Ryzen AI 7 350 running Bazzite with GNOME, updated to bios v3.05 shortly after it arrived a couple weeks ago.
I’ve got the same issue. It’s been happening every now and then since I purchased the Framework 13. Just happened 25 min ago again while just watching a youtube video on battery power. Mint shut down because of this and I pressed the power button to power the laptop back up again and here we are, running fine again with the battery discharge continuing where it left off, no charger connected at any point in the last 3 hours:
Maybe just maybe when I was still running BIOS V3.04 the laptop came with it didnt report as 0 percent when this happened but as a low number. Low enough to make Mint give a warning. Now it alwas just seems to go to 0.
If any dev wants me to run some diagnostics, even long term until it happens again let me know, I’d be happy to help to get rid of this annoying bug.
that seems like quite an old BIOS version. im currently on 3.24 with an intel FW 13 (although i do try and update occasionally in case it helps preserve battery life etc)
edit: unless the bios versions dont line up between intel and AMD
