Steam Hardware
A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to Steam Hardware or Steam OS in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
view the rest of the comments
If it is a fundamental bluetooth driver implementation problem, it would basically happen no matter what game you are playing, gaming mode, desktop mode, any apps/programs open, etc.
Right, I just know the past issue with sleep failing would happen like 75% of the time with non-steam games, but almost never with steam games. Not sure what the cause was, but I had to wait 5-10 seconds after putting the deck to sleep to see if it would wake back up.
Would you be able to link to ... a changelog or something along those lines, for when that older, similar problem got fixed?
I'm trying to look for it, but having trouble finding it.
I vaguely want to say that it was also maybe related to having pending downloads. It was like if you were playing a non-steam game, the sleep process would trigger the deck to start downloading again, interrupting the sleep. Once sleep was interrupted the game would start running again and downloads would be paused, making it seem like the deck failed to sleep for no reason. If you didn't have any downloads pending, the deck would go to sleep fine even in a 3rd party game. Unfortunately the deck frequently has a couple mini-updates available whenever you close a game, so this bug happened pretty often.
Once again steam games didn't seem to have the same issue, and downloads would stay paused through the sleep process so it didn't get interrupted.
This might have also been related to the decky plugin "pause games" actually, the more that I think of it.
I believe they reverted the power-up on Bluetooth activation (for LCD models) previously, but they reimplemented it in a recent patch.