You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Am I safe in assuming that restarting the Steam Deck for any reason (including software updates) disables the script and requires re-enabling it in the Konsole? It seems to work smoothly until I do have to do those random restarts, but standby seems to be okay.
That asked, is there a way the script can always enable itself (with user permission enabled first) upon a power cycle? Considering you have to go into the desktop mode to get it running each time, it'd be nice to just let it fire up by itself.
The text was updated successfully, but these errors were encountered:
I guess the same happens for every steamdeck update ?
Maybe the reboot topic could be solved with adding a line to "crontab -e" : @reboot /bin/bash curl -sSL https://raw.githubusercontent.com/scawp/Steam-Deck.Auto-Disable-Steam-Controller/main/curl_install.sh | bash ?
I'm not so sure and haven't tested....Just suggesting and would be happy to have @scawp's opinion on that.
Just to chime in, yes, updates are included in this issue. If the Steam Deck has to fully power down in any way- system reboot, system update, or shut down, you have to go back into Desktop mode and re-enable the script for it to work again.
For further clarification, it looks like switching from Game Mode to Desktop mode does not constitute a full power down, so the script does stay running when doing this.
Hello,
Am I safe in assuming that restarting the Steam Deck for any reason (including software updates) disables the script and requires re-enabling it in the Konsole? It seems to work smoothly until I do have to do those random restarts, but standby seems to be okay.
That asked, is there a way the script can always enable itself (with user permission enabled first) upon a power cycle? Considering you have to go into the desktop mode to get it running each time, it'd be nice to just let it fire up by itself.
The text was updated successfully, but these errors were encountered: