Closed Bug 1222907 Opened 9 years ago Closed 9 years ago

RemotePlayer UI doesn't reflect the media status while controlled by TV controller

Categories

(Firefox for Android Graveyard :: Screencasting, defect)

defect
Not set
normal

Tracking

(firefox45 fixed)

RESOLVED FIXED
Firefox 45
Tracking Status
firefox45 --- fixed

People

(Reporter: schien, Assigned: schien)

References

Details

Attachments

(1 file)

http://techcrunch.com/2015/03/16/chromecast-now-lets-you-pause-and-play-with-your-tv-remote/ User can play/pause shared video via TV remote controller, if that HDMI-CEC is supported. However, VideoPlayCallback doesn't reflect this status change to MediaCastingBar. [1] I can reproduce this issue with latest Sony BRAVIA Android TV. [1] https://dxr.mozilla.org/mozilla-central/source/mobile/android/base/ChromeCast.java#87
This patch works correctly on real device. Not sure if it matches the coding convention of Fennec.
Attachment #8684843 - Flags: feedback?(mark.finkle)
I did some research on Roku support but didn't find any API / document reporting player status from Roku to Fennec. Therefore I only made modification on Chromecast support.
Assignee: nobody → schien
Comment on attachment 8684843 [details] [diff] [review] bug1222907-status-report-to-remote-player-ui.patch >diff --git a/mobile/android/chrome/content/CastingApps.js b/mobile/android/chrome/content/CastingApps.js > onRemoteMediaStatus: function(aRemoteMedia) { > if (!this.session) { > return; > } > > let status = aRemoteMedia.status; >- if (status == "completed") { >- this.closeExternal(); >+ switch (status) { >+ case "started": >+ Messaging.sendRequest({ type: "Casting:Playing" }); >+ break; >+ case "paused": >+ Messaging.sendRequest({ type: "Casting:Paused" }); >+ break; >+ case "completed": >+ this.closeExternal(); >+ break; Technically, the RokuApp.jsm code will forward status changes ("started" and "paused") here too. This should not cause a problem because you are just setting visibility of the player controls in MediaCastingBar. Let's land this and get someone to test on Roku for bustage. Nice patch. Thank you! r+
Attachment #8684843 - Flags: feedback?(mark.finkle) → review+
NI to me to help test on Roku
Flags: needinfo?(mark.finkle)
I have Roku in Taipei office as well. I can double check the behavior on Roku before check-in.
Sorry I couldn't find Roku in Taipei office today. It'll be helpful if @mfinkle can help test on Roku.
Ok I got one Roku today. The same issue affects Roku as well (Roku has its own remote controller) and my patch can fix it. Ready to land this patch.
Keywords: checkin-needed
something in this push https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=e23d0660a042 caused a perma regression in mulet tests like https://treeherder.mozilla.org/logviewer.html#?job_id=5714391&repo=fx-team and https://treeherder.mozilla.org/logviewer.html#?job_id=5714374&repo=fx-team to bring the tree back into a stable state i backed out all pushes from this checkin to find out if this clears the mulet bustage
My patch is not the root cause of those perma orange. Mark checkin-needed again.
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 45
Flags: needinfo?(mark.finkle)
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: