chromecast

Is it possible to screen sharing from root adb shell without user interaction over mircast or chromecast in Android >= 5? I'm looking for the command that enables/disables this https://support.google.com/nexus/answer/2865484?hl=en You can try the Media Router - Secondary Output APIs from Android SDK: The Android media router APIs are designed to enable media display and playback on these secondary devices. There are two main approaches you can use to play content using these APIs: Remote Playback — This approach uses the receiving device to handle the content data retrieval, decoding, and

If there is a Chromecast around and: If the html5 video controls are enabled, the cast buttons shows up in the control bar. If the html5 video controls are disabled, the cast button shows up on the top left. I'd like to disable the native controls, but also include my own cast button, kind of what video.js-chromecast does, but the native button still shows up. Is there anyway to reposition the Cast icon over the html5 video? or completely hide it ? After searching the Chromium source code, I figured out how to do it: video::-internal-media-controls-overlay-cast-button { display: none; }

I have recently updated to com.google.android.gms:play-services 9.2.0 and am attempting to use the new Chromecast library and Firebase Analytics but am receiving the error "com.google.android.gms.internal.zzsj$zza: No acceptable module found. Local version is 0 and remote version is 0." in the Activity onCreate method at com.google.android.gms.cast.framework.CastContext.(Unknown Source). Any ideas if this is due to the Cast functionality not working with the emulators or if it's a version issue? The emulators I am testing with are running 5.0 and 5.1. protected void onCreate(Bundle

The problem I made a receiver application that is just showing a video in loop on the Chromecast. The problem is that the Chromecast doesn't seems to be caching the video in it's cache. So the video keeps getting downloaded every time it finishes a loop and it takes a lot of bandwidth. The video will be hosted on external server so the Chromecast will have to download it from internet every time (I cannot change that spec). Just for you know, when debugging the receiver application on a desktop chrome application, the video is cached by the browser, so the problem doesn't seems to come from

I have a custom receiver app (html page + js and css) that contains just an iframe for testing. I load the receiver app locally on the same Wi-Fi network as the ChromeCast. The thing is, it connects fine, then loads the iframe and everything is cool, but after a fix time of 21 secs (everytime), I get a error code 15 timeout. I've tried and set the maxInactivity to 6000 in appConfig, but made no difference. Any ideas what could possibly be wrong? Worth mentioning is that I've also tried to put the receiver app on a domain and made no difference. Edit: Adding some receiver logs, as requested.

I am looking to build a sample app that has the capability to just cast my android screen on to the TV screen. Most of the sample applications(including googles official sample cast applications) I see have the capability to cast audio and video as well. I know their is google's chromecast app which does the same(screen mirroring), but I need to integrate same functionality in my app. So any kind of code example or tutorial that point me in the direction of screen mirroring using cast SDK will be much appreciated. You cannot programmatically initiate mirroring your phone screen outside of your

I am trying to play an HLS stream on my chromecast custom receiver. However i'm having authentication issues fetching the m3u8 files because my server requires a cookie. The request to get the root m3u8 file has a 'Set-Cookie' header which needs to be considered when fetching the sub-m3u8 files in my stream (to pass server authentication). I would like to know if its possible to have cookies set when the receiver app fetches the media. Try something like: window.mediaHost = new cast.player.api.Host({ 'mediaElement': window.mediaElement, 'url': url }); window.mediaHost.updateManifestRequestInfo