Can't wake closed FW13 from sleep with mouse

Brand new Framework 13 running WIN 11 Ryzen BIOS 3.05

Trying to figure out how to wake up the laptop from sleep when it is being used in clamshell
(closed) mode with something like a mouse click or keystroke.

I have a usb wired mouse and a bluetooth keyboard hooked up to the laptop and it refuses to wake when I click the mouse or hit a key on the keyboard. External Monitor hooked up via HDMI. Nothing crazy here.

I have “what to do when lid is closed” set to “do nothing”

Many articles online say to change power settings for the USB devices but that power management tab is totally missing.

I have to physically open the screen every time to wake the machine up. Dumb and annoying.

Am I dumb? 2024 and we still can’t figure this out. Shouldn’t this just be default behavior out of the box? What gives?

Hi and welcome to the forum

Check the BIOS for wake on Power | USB etc.

Bluetooth is usually disconnected in sleep, on my phone too.

1 Like

I’m not sure what you mean. I went through the BIOS options and there is nothing there regarding power to USB devices.

1 Like

Maybe read this topic

Hmm, not the same issue. That guy is asking how to wake the computer up when he plugs something into it.

This is way more simple. I just want to wake the computer up when it is closed and connected to an external monitor by clicking my mouse or hitting a key on the keyboard. This is an extremely basic function…

What is interesting is that it appears to now be functioning as expected, but I had to switch my port adaptors around… so that seems like a hardware issue that I’ll be reaching out to framework about.

1 Like

Which port adapters?

1 Like

The little adaptors that go on the bottom of the laptop to adapt the USB-C slots to something else…

And actually, I was wrong.

My wired mouse attached to the USB-A port adaptor doesn’t seem to be waking the machine, but my bluetooth keyboard for whatever reason, is able to wake the computer.

F*cking annoying but whatever. As long as I don’t have to to open the lid every damn time I want to use my machine.

People normally want sleep to save power. This involves shutting down most, if not all, internal and external devices. And often powering down ports, unless there is an explicit option to keep certain ports powered & one has enabled the option. And also powering down the normal hardware that processes usb communications.

1 Like

That’s really a strange response. Almost everyone when using a laptop in clamshell mode would expect that an input from a keyboard or mouse to wake the machine.

Wouldn’t you then want bluetooth powered off too? Bluetooth wakes the thing up.

People use their computers in a range of different ways. The computer doesn’t know how you want it to behave. Even if one tried to give it some limited intelligence, and it tracks how it’s usually used, it doesn’t know your future plans.

One user may put their laptop to sleep, disconnect it from their thunderbolt hub, put it in their bag & head to the airport.

That’s not me normally, but for my use I still wouldn’t want ports to remain powered during sleep. I want peripherals to be turned off. I don’t know why Bluetooth remained on. I’d usually want that off as well.

I do think options to wake from sleep (other than the power button) are lacking. But it’s not just Framework, options seem to be missing from many many computers. I think the majority don’t have it. Wake-on-USB, Wake-on-BT (which luckly FW has from your report), Wake-on-Ethernet, these should all be absolutely standard options that one can enable in the BIOS of every computer. Unfortunately, it’s not so. And we’re not able to expect that.

I am experiencing the same issue on a Framework 13 Intel 12th Generation running Windows 11.

The clumsy workaround is to disable sleep when connected to a power source and make sure it gets connected to the power adapter and monitor before closing the lid.

I am not sure about other PC laptop vendors / BIOS OEMs but this is something Apple does really well with the Mac.

So after trying a few different mice, it appears that this was a firmware issue with the specific mouse peripheral I was using (Endgame Gear OP1 wired). I purchased their wireless one that uses a USB-A transmitter plug and it wakes the machine perfectly.

1 Like