-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[BUG]: App preventing TV Box to enter sleep/hibernate #4128
Comments
I have the same issue on nvidia shield for a while now, There have been several issues created about this. The device just doesn't sleep with a video loaded, Paused or not. |
Same here: #3876 |
Similar issue, here is how it presents for me. Summary: Google TV can't shut off during power off timeout, it just turns right back on and blares the most recent SmartTube video.
The issue is happening in v24.71 , not sure what other versions are affected. This didn't used to happen in the version from a couple of months ago. Thank you. |
On my nvidia shield I was able to change the sleep timeout in screen saver settings in my nvidia shield to 5 minutes and it would sleep with a video paused in SmartTube. It doesn't wake up after. But 5 minutes is the only setting that works with SmartTube opened and a video loaded and paused. Any other time frame higher will result in the device not sleeping. |
Checklist
Affected version
24.71 stable and beta
Device Type
Smart TV/Box
Affected Android
android 9
Steps to reproduce the bug
Actual behavior
The TV box start to enter sleep/hibernation but after a second it turn on and start playing the video.
Additional information
The normal behaviour is to have the tv box to "turn off", and when we turn it on again it have to play the video where it left.
The issue only happens if a video is playing. Even pausing and click OFF make the box to turn on again after a second.
If I clean the data of the ST app the behaviour is normal, but after restoring the settings the problem return.
V23.30 is the last version that I found that have the correct behaviour.
The text was updated successfully, but these errors were encountered: