Thanks. Please let me know when you’ve created the support ticket and I’ll grab it and put it in my queue.
FYI for those still on Windows 11 23H2. there is a pretty nasty bug in this month’s KB that causes the devices to power on. There is an updated Jan patch to fix this behavior but I had a lot of people take out toasty laptops at work because of this KB before we pushed out the fixed version.
Behavior is that S4 or S5 states result in a power on signal to be generated often within 60 seconds of entering said state.
Why would you still use 23H2? Makes no sense since support is ending or has ended on 23H2 and you should update to 25H2.
Enterprise, Education, Government. 23H2 is still in support and being actively used by organizations as much as I wish it wasn’t so.
I just wanted to give the shout-out to @Eagle and FW team:
- They cared enough to work to retrieve the offending battery from UBreakIFix for further breakdown and analysis.
- They refunded my new battery purchase!
Thank you so much, your help is greatly appreciated!
So you got new battery for free? If so that is great to hear.
Any comment or resolution on the root cause?
Root cause for the battery puffing up will take a long time as once it’s secured from UBreakIFix it’ll go to Taiwan to be taken apart. As far as the spurious wakeups that’s up in the air.
so if they find a hazard problem with battery, then they have alot of work todo to ship out a battery replacement to everyone with a framework 16, so they are not using a hazard battery.
But that is only if they can find a cause to battery that flags hazard alert.
Also they got a design a new battery that has hazard fix as well before they can ship a new battery out to everyone.
What are you guys on about? The battery puffed up because it overheated. That part is obvious. No design flaw with the battery.
you don’t see point, there can still be a design flaw, since if a battery should not puff upp like that just because of some heat then it is a design flaw or a hazard, that is why battery was sent for inspection to make sure it does not have a sign of hazard/design flaw.
In this case a battery should handle heat at specific temp, if temp was not reached and it puffed up earlier than it should, then they have a flaw some where that needs to be solved.
Yea typical laptop batteries have internal temperature sensors. Exceeding allowed temperature should result with BMS cutoff. It’s quite scary what happened here.
I think the BMS temperature usable range is set too high, probably due to Kelvin to Celsius conversion calculation error. For example, the battery will charge very slow due to very cold, however the “very cold” is as high as 20 Celsius, and the “very hot” to stop charging is as high as 70 Celsius. The temperature range should be moved downward about 10C, i.e. 10~60C
Hi everyone,
I had a similar issue with it waking in my bag. Thankfully I didn’t have my battery off itself like op. Anyway I just wanted to comment that I believe this issue is with the touchpad still being active even when the lid is closed. You guys can reproduce this by firmly pressing where the touchpad is on the lid when closed.
Framework 16 gen1: AMD Ryzen 9 7940HS + AMD Radeon RX 7700S
bio: 4.03
OS: Fedora Linux 43
Laptop 16 Keyboard Module: 0.31
@mat0uz
The bios and keyboard firmware you have there is supposed to fix the wake up bug. Do you still see the wake up bug?
You say you have the following:
bio: 4.03
Laptop 16 Keyboard Module: 0.31
I suspect you’re right because I’m on the latest keyboard firmware as well.
I’m on latest both BIOS and keyboard firmware.
The bios and firmware updates were supposed to stop waking via keyboard inputs XD not the touchpad. Unless I’m mistaken and I have an actual bug that keeps the touchpad on. Can you guys also wake your laptop how I described with the latest bios and firmware?
I don’t have a way to get the lid to register as closed, so idk if that makes a difference, but I’m able to wake the device using the touchpad when the device is open. As a side note, my device had an issue where the touchpad would click if the laptop was twisted, which I fixed by adding some paper under the midplate.
Waking the laptop with the lid open, with the touchpad from what i can tell is normal. Also what do you mean by you can’t get the lid to register as closed? Do you mean you can’t verify if it’s asleep or the laptop can’t tell if it’s closed?