I’ve experienced this issue with waking up my brick twice today when briefly putting my device to sleep, putting it in my bag then resuming it a few minutes later.
After waking the device I can hear the game audio play but there is no output on the display even if I try putting it to sleep again and waking it. I ended up having to hold the power button to force a shutdown both times this happened. Closing games before putting it to sleep seems to be more reliable.
I use the stock MuOS settings.
Unfortunately I do not have issues with putting my Brick to sleep whilst playing content. Could you please let me know which content you were playing and on what brightness level you were currently on when this happened. Thanks!
Hello, thanks for the reply. I understand there isn’t much you can do if you aren’t having the issue yourself but ill still detail it just in case.
I was playing chrono trigger on the snes when it happened and my brightness would have been max. I had briefly put it to sleep for about 2-3 minutes and I had thought the brightness might have gone down but I tried raising the brightness and nothing happened. I was still able to change the volume and open the retroarch menu though, but to get the display working again I was forced shutdown and power it on again.
It did happen twice in a row if that matters as I had played a bit at the train stop after it happened before putting it to sleep again to get on my train, then it happened again and I had to force shutdown again and power on
Okay fantastic! I managed to replicate it on max brightness. If I use the brightness shortcut to bump it down a few notches and put it back up I get the display back.
I’ll investigate the brightness scripts and see what is going on! 
This is now fixed for the upcoming 2508.1 Canada Goose release. Thanks!
This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.