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

[Feature Request] ADB Disable Screen Standby Timeout #186

Open
Timocop opened this issue Jul 30, 2022 · 4 comments
Open

[Feature Request] ADB Disable Screen Standby Timeout #186

Timocop opened this issue Jul 30, 2022 · 4 comments
Labels
analysis needed enhancement New feature or request

Comments

@Timocop
Copy link

Timocop commented Jul 30, 2022

Recently i borked my screen timeout on my Quest 1 via the hidden android control panel. Once you do that you cant revert those changes to quest factory anymore (Unless you factory reset the whole device).
The maximum time you can set is 30min. So while you play games with the quest it would shut down the screen in 30min and go into standby. This is not the same as the Quest setting Inactive timeout you see in the Quest Control Panel!

However, i did some digging and found a useful ADB command to increase the screen timeout past 30min permanently.
I think this is very useful in combination with "Disable Proximity Sensor".

adb shell settings put system screen_off_timeout 999999999
Which is 16.666 hours until the device shuts down its screen. A value with -1 probably should also disable the screen timeout.

@sidequestlegend
Copy link
Contributor

This is really interesting, and the timing is pretty perfect.

@sidequestlegend
Copy link
Contributor

Can i ask, when you say play games do you mean like with 2d apps etc? Whats the use case here? DO you know the default value and can we detect the currently set value?

@Timocop
Copy link
Author

Timocop commented Aug 1, 2022

Can i ask, when you say play games do you mean like with 2d apps etc?

It's an android setting, it would work the same way as on any android phone. Touching the screen and volume buttons will reset the screen timeout. But since the Quest doesn't have a touch screen input or any input that the android software even detects, it will always timeout. So if you play Quest games or even PCVR via Virtual Desktop or ALVR streaming it will time out after some time (depending which settings you use). You can also pretty much brick your Quest as well if you set the timeout to the minimum 15 seconds. You wont even reach the hidden control panel settings in time before it goes to standby.


DO you know the default value and can we detect the currently set value?

You can read the screen timeout value with:
adb shell settings get system screen_off_timeout

the default "Disabled" value is -1.

Also keep in mind that changing the value is persistent! It will survive with Quest restarts!


Whats the use case here?

The only use case here that i know of are (very limited use cases):

  1. Have a fix and revert it back to the original value without factory resetting the whole Quest. Since there are absolutely no tutorials or posts of fixing this issue online.
  2. Having a predictable timeout. Kind of like a timed sleep. This could be useful when watching movies on the Quest using 3DoF mode that disables Quests Inactive timeout. So you could make it fall sleep after the movie ends (example).

@sidequestlegend
Copy link
Contributor

sidequestlegend commented Aug 3, 2022

It's an android setting, it would work the same way as on any android phone. Touching the screen and volume buttons will reset the screen timeout. But since the Quest doesn't have a touch screen input or any input that the android software even detects, it will always timeout. So if you play Quest games or even PCVR via Virtual Desktop or ALVR streaming it will time out after some time (depending which settings you use). You can also pretty much brick your Quest as well if you set the timeout to the minimum 15 seconds. You wont even reach the hidden control panel settings in time before it goes to standby.

Hmm this is interesting, I have never experienced this myself. I guess that's because its disabled by default if thats what you mean by

the default "Disabled" value is -1.

Have a fix and revert it back to the original value without factory resetting the whole Quest. Since there are absolutely no tutorials or posts of fixing this issue online.

This is an interesting use case, I'm not sure it warrants a UI button though, maybe a tutorial on our support system and even a video covering how to do it might make more sense since this might be only ever needed once for most people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analysis needed enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants