SteamOS
SteamOS copied to clipboard
ValveSoftware
Legion Go S fails to resume properly from suspend
Your system information
- Steam client version:1749753892
- SteamOS version: 3.7.9
- Opted into Steam client beta?: Yes
- Opted into SteamOS beta?: Yes
- Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen.
After device suspends (either with power button or from the menu), it will not resume, just a black screen and no sound or indication that any of the inputs are working. If resume is attempted right after suspend, it will sometimes work.
Steps for reproducing this issue:
- Suspend device
- Wait more than 5s
- Tap power button to resume
So far I've been unable to reproduce this on my Legion Go S with SteamOS 3.7.9, the device has consistently been suspending/resuming without issues. Are you using any external plug-ins or other modifications to the system? Also, can you grab a SteamOS system report (Settings -> System -> Advanced -> System Report -> Create Report) after it happens? The report will include logs from your previous boot and your current boot.
I had the same problem, super frustrating. Tried some things like triggering the boot animation when waking up from sleep but it didn't help. Suspected it had something to do with the _Animation Changer_plugin in Deckly loader, but couldn't find the problem.
I was on stable, but updated to the beta version and the wake/suspend problem went away. Maybe you could do the reverse? The audio crackling does seem to be worse now though...
Issue dissapeared just as randomly as it appeared. For reference, it was happening on a vanilla install, with all the latest updates pulled up to the time of posting. Currently I've added most of decky's plugins, including HueSync to control the LEDs, and sleep and resume work flawlessly. I tried to create a report the last time the device didn't wake properly, but when I read the report, it was only events from the current boot. Will be on a lookout if the issue appears again in the next week. If not, hope this issue can be closed.
Please submit a report then so we have some insight into what's going wrong