-
Notifications
You must be signed in to change notification settings - Fork 6
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
Display timeout on latest Chromecast #229
Comments
#231 didn't fix it. The latest generation of Chromecasts seem to have a general issue w/ this... pending more investigation. |
Opened a bug report against the Cast SDK related to the timeout issue: https://issuetracker.google.com/issues/282046056 Reopening this to track the above bug report. Current status of WR-specific efforts:
|
John, sorry if this is completely stupid (my background is not in python programming so perhaps there is some reason it can't be done), but wouldn't the simplest way to avoid the time out be to just implement a simple heartbeat animation - ie put a square in a corner and change its colour every 5 seconds? |
@digilinCraig You're definitely thinking in the right direction. On the older Chromecasts, as long as you publish a new image before the timeout, the timeout will reset and all will be good. The code that makes that happen is: Lines 260 to 270 in feddf96
And the refresh interval is defined at the top: Lines 40 to 42 in feddf96
Unfortunately, the GoogleTV variants don't seem to reset their timeout when you display a new image. This probably wouldn't be an issue if the scoreboard were actually a video stream instead of static PNGs. However, I've resisted using a video stream because I'm concerned about load on the scoreboard computer plus having a good network connection between it and the Chromecast. So the best I've got is the current "stay awake" workaround. |
The current generation of "Chromecast with Google TV" seems to have a shorter timeout, so it returns to the screensaver if there is too much delay between races.
Workaround:
disable then re-enable the ChromecastEnable "developer options" and set "Stay awake"The text was updated successfully, but these errors were encountered: