Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto Enable on Restart #12

Open
Chromagram opened this issue Apr 25, 2024 · 2 comments
Open

Auto Enable on Restart #12

Chromagram opened this issue Apr 25, 2024 · 2 comments

Comments

@Chromagram
Copy link

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.

@djspatule
Copy link

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.

@Chromagram
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants