-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
CastReceiver does not work play/pause from the remote #2730
Comments
Unfortunately, we don't have access to an Android TV for debugging or reproing at this time( |
The problem is not only on Android TV, but also on Chromecast - I checked the Chromecast ultra on the device |
Well, if this also happens with Chromecast, then I can look into it. |
Can confirm. I enabled HDMI-CEC, so that I could use my remote to control the Chromecast, and I was not able to pause or resume. |
@theodab I thought it might be a problem of us not using the lastest version of the Chromecast SDK (v2 vs CAF? I vaguely remember another issue mentioning this), but the fact that it also affects Android TVs make me doubtful. |
I checked in with the Cast team, and they suspect it has to do with our using an old SDK and not using the preferred method of creating a media receiver app. See also #2635. I'm working with the Cast team to find a migration path for Shaka's receiver apps to CAF. We'll keep both issues updated as we make progress. |
@alex2844 Faced something similar and it was solved by adding a tabindex attribute to the play button and then focusing it. Hope this helps. Shaka V3.1.0 |
Our effort must go along the lines of implementing #4214 so I am going to close this issue. Sorry! |
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
v3.0.1
Are you using the demo app or your own custom app?
demo
What browser and OS are you using?
Chrome OS, Android TV
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Xiaomi mi box S, Android TV 9
The text was updated successfully, but these errors were encountered: