Steam Deck - Controller Input Doesn't Work After Wake From Sleep (SteamOS 3.6.24)
Device: Steam Deck
SteamOS Version: 3.6.24
OS Build: 20250313.1
Kernel Version: 6.5.0-valve23-1-neptune-65-g385b5e207ae2
BIOS Version: F7A0131
Steam Version: 1745876290
Steam Client Build Date: April 29
Controller ID: MEDA22007807
Serial Number: FWAA22106D2F
Description:
After putting my Steam Deck into sleep mode while a game is running, then waking it up, the game no longer responds to controller inputs. The Steam button still works, and I can open the overlay and return to the main menu, but the game itself does not detect any input from buttons or sticks. To fix this, I need to completely quit and relaunch the game.
Steps to Reproduce:
- Launch a game (e.g. Batman: Arkham City, Assassin’s Creed II).
- Confirm controls are working normally.
- Let the Steam Deck go to sleep automatically or close the screen.
- Wake it up after a few minutes.
- Try to resume playing.
Expected Result:
Game resumes normally with input.
Actual Result:
Game appears active, but no buttons work until I exit and relaunch the game.
Temporary Workarounds:
- Disabling “Use as Wake Movie” in the Customization settings.
- Restarting Steam Deck.
- Changing Steam Input settings (e.g. “Forced On”).
- Switching Proton version (when using Proton).
- None of these fully solve the issue reliably.
Notes:
This issue has been reported by multiple users on forums and Reddit. It affects a wide range of games and seems tied to how input focus or controller binding is restored after waking from sleep. The problem appeared after recent SteamOS or Steam updates.
Severity: Medium (high annoyance, breaks game continuity, no crash).
This happens for me with Steam games only, not non-Steam. Has that been the case for you?
This happens for me with Steam games only, not non-Steam. Has that been the case for you?
I haven’t tried it with non-steam
I am having the same issue, and disabling wake mode/forcing steam input/restarting do not solve the issue whatsoever. Very annoying lol
EDIT: Switching to beta updates fixed this for me
I encountered the same bug after updating to the latest STEAM client on ROG ally, which was normal before the update
The beta client does seem to fix this.