I have a mousepad glued to one of the spacers, so my screen doesn’t close enough to trip the “closed” sensor.
That is a very interesting and very niche edge case XD
If so, there’s enough space that the keyboard can’t be pressed by the screen
Yes and yes, to both counts ![]()
I don’t believe the keyboard is the issue anymore, that got fixed with the update. The issue that I found is that the touchpad wasn’t addressed and is still active when the laptop is closed unless I have a bug in my bios/firmware that keeps it on. Can you check if it’s not just me and is a issue effecting all framework 16 gen1s?
I can confirm that with my FW16, the screen can definitely be wakened by the trackpad even if the lid is shut.
I simulated a screen shut event by placing a magnet on the lid sensor (I don’t recommend doing this for extended periods of time just to be safe). Then, I typed on the keyboard and nothing caused the laptop to wake. Then, I pressed on the trackpad and it *almost instantly woke up. I double-checked this to make sure it wasn’t a fluke.
We need to make a new post about specifically the trackpad potentially waking the laptop when it’s in a bag with gen 1 top cover.
I hope that maybe it can’t happen in real conditions because the trackpad is more indented compared to the keyboard, but I still think Framework should address this just to be safe!
_Snapshots of the MP4 video that I took demonstrating the issue_
Pressing Trackpad:
Letting off the Trackpad:
You are a mensch! Thank you!
@Eagle seems like another firmware, this time for a touchpad, is needed.
I think it’s easier then you think, especially when you stuff the laptop(even with a sleeve) into a bag filled to the brim like for example for a flight. And the very flexible gen1 lid doesn’t help.
Thx for verifying
I can confirm that this disables the touchpad and keyboard fully as wakeup devices. Nicely done, thanks!
Hey @Arcadiy_Ivanov1
Thanks for the ping. I’ll get this documented and up to the firmware engineers today.

