Database Develop

miracast and xbmc

was thinking about this possibly being a sweet setup hopefully miracast will be implemented into the device or possible being implemented into xbmc having that along the airplay option on xbmc enabled would make this a pretty sweet device
i purchased(preordered one) but I was hoping it would be more so like a media center device kinda like google tv but no hdmi out so no google tv overlay. But if I could use this to do miracast with my 4.2 sgs3 and whenever friends come over can use xbmc to allow them to do airplay that would be really cool
reason i bring up miracast support is because supposedly is supported in tegra 3
i've been trying to figure/find out how you go about setting up a miracast server but the documentation doesn't seem to exist not saying that i have the ability to implement but i wouldn't mind taking a look into it
thoughts?

This is more of a question for xbmc team. I suggest you provide that feedback on their forum. There was a talk of xbmc supporting miracast but no eta.
Sent from my GT-I9305 using xda premium

As long as it supports PLEX, I am sold!

Keland44 said:
was thinking about this possibly being a sweet setup hopefully miracast will be implemented into the device or possible being implemented into xbmc having that along the airplay option on xbmc enabled would make this a pretty sweet device
i purchased(preordered one) but I was hoping it would be more so like a media center device kinda like google tv but no hdmi out so no google tv overlay. But if I could use this to do miracast with my 4.2 sgs3 and whenever friends come over can use xbmc to allow them to do airplay that would be really cool
reason i bring up miracast support is because supposedly is supported in tegra 3
i've been trying to figure/find out how you go about setting up a miracast server but the documentation doesn't seem to exist not saying that i have the ability to implement but i wouldn't mind taking a look into it
thoughts?
Click to expand...
Click to collapse
I've heard the documentation costs around $200 and that might not even be all of it. Or I might be pulling that number out of air, don't remember where I saw that, but did find this:
http://forum.xbmc.org/showthread.php?tid=147320
I am more interested in seeing the Android Transporter Player ported to Ouya, except that they haven't released their source code on the sending side yet...
https://github.com/esrlabs/AndroidTransporterPlayer
https://www.youtube.com/watch?v=lyoZoNA8U24
~Troop

I'm not from familiar with Miracast. All I know is what the Wiki page said. It really reads like DNLA. And from my experience, this has been something that can be app dependent. Since I have no experience with Miracast, I don't know if it's full mirroring or just certain apps.
That said, Miracast may just be work versus just installing individual apps. Unless there is something in the application code for specific devices, if you side load an APK, it should run on the Ouya. Doesn't mean it will run well or look correct. Thus, you may be able to just side load XBMC. I know I'll try it with Plex, Netflix, Hulu, various sports--MLB, NHL, NBA, etc--and so on.
I couldn't figure out what the end result you were suggesting about friends coming over and their mobile devices.

lovekeiiy said:
I'm not from familiar with Miracast. All I know is what the Wiki page said. It really reads like DNLA. And from my experience, this has been something that can be app dependent. Since I have no experience with Miracast, I don't know if it's full mirroring or just certain apps.
That said, Miracast may just be work versus just installing individual apps. Unless there is something in the application code for specific devices, if you side load an APK, it should run on the Ouya. Doesn't mean it will run well or look correct. Thus, you may be able to just side load XBMC. I know I'll try it with Plex, Netflix, Hulu, various sports--MLB, NHL, NBA, etc--and so on.
I couldn't figure out what the end result you were suggesting about friends coming over and their mobile devices.
Click to expand...
Click to collapse
I believe Miracast is primarily for screencasting - ie it just mirrors what is on the device's screen onto the TV or whatever is receiving. And I believe the previous poster was saying that it would be nice if it is easy to screencast from your phone to the TV and allow visiting friends to be able to easily screencast their content as well - so if one person has a video they want to show everyone, it's not a hassle to pull it up on the big screen. I think this is what a lot of us want.
~Troop

Trooper_Max said:
I believe Miracast is primarily for screencasting - ie it just mirrors what is on the device's screen onto the TV or whatever is receiving. And I believe the previous poster was saying that it would be nice if it is easy to screencast from your phone to the TV and allow visiting friends to be able to easily screencast their content as well - so if one person has a video they want to show everyone, it's not a hassle to pull it up on the big screen. I think this is what a lot of us want.
~Troop
Click to expand...
Click to collapse
yea this is exactly what i'm lookin for been keeping an eye on it have google alerts set up for pretty much anytime miracast is being searched on the net to possibly find any tidbit of info that might be helpful with this. thanks Troop

video streaming
Hi all. Bit late to the party but my ouya comes tomorrow
Assuming no problems on sideloading why not just use
twonky. Been using for ages bouncing files between my
nas drive, xperia s, xoom2 and Xbox. Even adhoc with
android.......jus puttin it out there..... It's spot on even with
playlists and web streams.

How can a chromecast have mirroring capabilities

Hello does a rooted and rom chromecast have mirroring capabilities, what apps can give the chromecast the ability to mirror the android devices it is casted from? thank you in andvance

wilspeak said:
Hello does a rooted and rom chromecast have mirroring capabilities, what apps can give the chromecast the ability to mirror the android devices it is casted from? thank you in andvance
Click to expand...
Click to collapse
Hi Wilspeak,
To the best of my knowledge there isn't any mirroring software available in the wild yet for the chromecast - google has placed mirrorcast code into the chromecast as of the latest OTA however there has been no available software to utilise this put forward as of yet. Hopefully we will see this out of Google shortly though as it looks like they've been prepping for it.

Well we know it can mirror is some respect because Googlecast extension pretty much does this already.
As @Kyonz said the issue is the software available not the actual CCast itself. Unless you want to say the Whitelist is preventing someone like Koush from re-implementing it in his All Cast.
I suspect whatever comes after KitKat will have Mirroring to the CCast in it's display settings.

Asphyx said:
I suspect whatever comes after KitKat will have Mirroring to the CCast in it's display settings.
Click to expand...
Click to collapse
Yup, or in some vendor-supplied add-on like how Samsung's AllShare Cast is.
Plus I expect ROM-level mirroring will be far more smart and efficient than Chrome's brute-force casting. Raster/bitmap content will probably still need to be transmitted, but standard UI stuff could/should be rendered by Chromecast itself.

bhiga said:
Yup, or in some vendor-supplied add-on like how Samsung's AllShare Cast is.
Plus I expect ROM-level mirroring will be far more smart and efficient than Chrome's brute-force casting. Raster/bitmap content will probably still need to be transmitted, but standard UI stuff could/should be rendered by Chromecast itself.
Click to expand...
Click to collapse
My only fear is they will implement it to work like a Miracast and require direct connection via Wireless.
That would be a shame.
I like some aspects of Miracast such as being able to add it as a display to a PC, But that whole Wireless only thing is not the way I would want to see this go.
I suppose instead of actually mirroring via Raster they could send a template package that contained most of the graphics needed to build thus not requiring a lot of bandwidth to update.
Will be interesting to see how they do it.

Android chrome to chromecast

Hey im new to this chromecast. I can see my chrome browser on the pc but not on android, how can I do that? Sijce here are very experienced users oj chromecast can someone describe the full working potentials this device has?
Sent from my GT-N8013 using xda app-developers app

You cant do squat with Chrome on Android yet for some odd reason.

Tab casting from Chrome uses the host CPU to re-encode the video and stream it to the Chromecast on-the-fly. Tablet and phone CPUs don't have enough processing power. That's why there's no Chromecast extension for Chrome on your portable device.

Well that sucks bc there is possibilities with this chromecast. I downloaded the allcast and obviously updated my google services. I cast a picture and it doesnt show normal, shows rotated to the left. Can you cast from the gallery vids and photos?
Sent from my GT-N8013 using xda app-developers app

The man problem is the fact that Android Chrome does not support Chrome Apps and Extensions.
Something I'm told Google is working on...

Asphyx said:
The man problem is the fact that Android Chrome does not support Chrome Apps and Extensions.
Something I'm told Google is working on...
Click to expand...
Click to collapse
Yea they better be working on it, this has been out couple months now they need to update more
Sent from my GT-N8013 using xda app-developers app

Google is working on a way to mirror your android screen to the chromecast and we know this because on kitkat roms theres an option to cast screen but isn't quite working yet. Its only been coded in but thats it.
Sent from my SPH-L710 using Tapatalk

tooblackforjack said:
Google is working on a way to mirror your android screen to the chromecast and we know this because on kitkat roms theres an option to cast screen but isn't quite working yet. Its only been coded in but thats it.
Click to expand...
Click to collapse
KitKat roms have Miracast, a different protocol.
Supported by HTC and Samsung since 2012 with their private dongles.
Not new, sorry.

EarlyMon said:
KitKat roms have Miracast, a different protocol.
Supported by HTC and Samsung since 2012 with their private dongles.
Not new, sorry.
Click to expand...
Click to collapse
Yeah ik, i was just informing in case he didn't know sorry.
Sent from my SPH-L710 using Tapatalk

EarlyMon said:
KitKat roms have Miracast, a different protocol.
Click to expand...
Click to collapse
Yes, but Google has renamed it to Cast Screen. Clearly, they will be adding support for casting to Chromecasts directly inside of Android. Otherwise, renaming it to match the Chromecast nomenclature makes no sense.

bozzykid said:
Yes, but Google has renamed it to Cast Screen. Clearly, they will be adding support for casting to Chromecasts directly inside of Android. Otherwise, renaming it to match the Chromecast nomenclature makes no sense.
Click to expand...
Click to collapse
Because MiraCAST isn't confusing enough?
I'm aware that a number of blogs not familiar with Miracast are spreading that rumor. I think it's wishful thinking but we'll see, won't we?
http://www.howtogeek.com/177145/wir...ed-airplay-miracast-widi-chromecast-and-dlna/
http://readwrite.com/2013/11/07/android-kitkat-developers-users
A side note, Android 4.4 KitKat devices can now be certified by the Wi-Fi alliance as being Miracast compatible. That is a big step for Android in being able to stream content from a device to a television by supporting more streaming standards. Now only if the Chromecast supported Miracast.
Click to expand...
Click to collapse
http://www.androidpolice.com/tags/miracast/
So, you believe that WiFi Direct is coming to the existing Chromecast?
Or that in addition to Miracast, they'll be providing a second protocol for phones, with a server (like Koush did)? And people will be able to figure out the two casting options on their devices?
I think that it's far more likely that rather than put both protocols on a phone or into the existing Chromecast, it's more likely that DIAL support plus Miracast *might* appear in a Chromecast 2.
Miracast dongles already exist, it's February and the SDK libraries still aren't out, and in July, Chromecast will be a year old.
Apple TV costs $100 with this feature, a Belkin Miracast dongle is $80, an HTC Media Link HD is $100, the Samsung Allshare Cast Hub was a hundred, is $65 on Amazon now.
It's possible that Google is going to pump this in to the existing Chromecast for the faithful for free, but I'm just not feeling it.
Either way, so far KitKat includes Miracast, not DIAL.

EarlyMon said:
Or that in addition to Miracast, they'll be providing a second protocol for phones, with a server (like Koush did)? And people will be able to figure out the two casting options on their devices?
I think that it's far more likely that rather than put both protocols on a phone or into the existing Chromecast, it's more likely that DIAL support plus Miracast *might* appear in a Chromecast 2.
...
It's possible that Google is going to pump this in to the existing Chromecast for the faithful for free, but I'm just not feeling it.
Either way, so far KitKat includes Miracast, not DIAL.
Click to expand...
Click to collapse
First part:
Since it's (Android) device mirroring functions appear to be in the SDK, but are limited only to OEM developers, my best-guess is that what we'll see is any Chromecast device mirroring will have to be "cooked" into a ROM rather than a loose bit (makes sense - that's how Samsung's AllShare Cast works too).
Hopefully the UX engineers win and make it so the Screen Mirroring option at least combines Google Cast and Miracast device options together, rather than having separate options for Screen Mirroring (Miracast) and Screen Mirroring (Google Cast).
Second part:
Yeah, not going to hold my breath. As I keep saying, screen mirroring is not the core competency of Chromecast.

bhiga said:
First part:
Since it's (Android) device mirroring functions appear to be in the SDK, but are limited only to OEM developers, my best-guess is that what we'll see is any Chromecast device mirroring will have to be "cooked" into a ROM rather than a loose bit (makes sense - that's how Samsung's AllShare Cast works too).
Hopefully the UX engineers win and make it so the Screen Mirroring option at least combines Google Cast and Miracast device options together, rather than having separate options for Screen Mirroring (Miracast) and Screen Mirroring (Google Cast).
Click to expand...
Click to collapse
Both together sounds like a bit much, but it's possible.
Samsung is likely going their own way.
http://www.slashgear.com/samsung-an...ultiscreen-and-overlay-capabilities-28303309/
Second part:
Yeah, not going to hold my breath. As I keep saying, screen mirroring is not the core competency of Chromecast.
Click to expand...
Click to collapse
Agree.

If you ask me any attempt to make CCast work like a Miracast would be a big waste, Even a downgrade!
No need for Direct Connection for Mirroring as Mirror over IP is far more flexible and less problematical. Not to mention requires no special software support like Miracast does. If they really wanted Miracast type direct mirroring all it would take is some additions to the rom cause hardware wise, the CCast has everything it needs
It may not be part of why the CCast was developed but I don't see Google being as smart as they are leaving that market open to Miracast dongles when they know full well the only thing inhibiting CCast from doing it (and better) is their lack of developing an App that does it for Mobile...
As for the Casting support in the SDK for OEM use I suspect that is more generic in nature and just an exposure of the display system to support Miracast, Perhaps CCast Mirroring and any other 2nd screen tech that comes down the pipe.
I think mirroring feature is a bit overrated myself, it's good for an audience but not for an operator's use.
It's easier to do than what CCast is trying to do because there is no need for a control protocol...Just a simple transcoder for Video and Audio the rest is all done on the Master Display device.
As for that Samsung option I don't expect it to take off due to proprietary concerns. It's meant for Samsung SmartTVs and I bet LG and Sony won't support it. Samsung would be better off building that capability directly into the TV itself.
DIAL is still in its infancy and I expect the protocol to expand as support and adoption of it grows...
Whatever lessons they learned from Chromecast I expect to be addressed whenever they get around to making the second gen CCast.
Wired Networking or at minimum 5Ghz Wireless support is to be expected as would a more robust Video playback Compatibility.
It's not likely that any app that adds CCast support is going to remove it in the future which means as the Apps list grows so too does the chance we have of seeing this supported without the need for a dongle at all.
TV over the Web will work the way it was supposed to and remove the biggest hurdle to achieving full IPTV to date...
The Navigation and Channel Guide no one could figure out how to do....
And who knew the Web Browser was the answer all along.

Samsung is still the largest supplier of flat screen TVs in North America, is it not?
Besides, they've never been shy about adding interfaces to support the future. I have a Samsung TV with a specialized iPod interface as proof. (And I believe that the article did say clearly that Samsung was going to build the new casting into their TVs.)
And none of the TV makers think twice about adding fragmenting features, and Samsung certainly doesn't for their mobile devices.
As for the claim that it's just about making a mobile app and declaring victory for screen casting, you might want to review the API changes that have been evolving for months.
Doing that without library support and not differentiating DRM vs non-DRM cast calls may seem simple to you but it doesn't to me.
Last published, Netflix and YouTube accounted for over 50% of North American broadband traffic.
Screen casting may be an emerging market, or it could just be a flash in the pan.

EarlyMon said:
Samsung is still the largest supplier of flat screen TVs in North America, is it not?
Besides, they've never been shy about adding interfaces to support the future. I have a Samsung TV with a specialized iPod interface as proof. (And I believe that the article did say clearly that Samsung was going to build the new casting into their TVs.)
And none of the TV makers think twice about adding fragmenting features, and Samsung certainly doesn't for their mobile devices.
As for the claim that it's just about making a mobile app and declaring victory for screen casting, you might want to review the API changes that have been evolving for months.
Doing that without library support and not differentiating DRM vs non-DRM cast calls may seem simple to you but it doesn't to me.
Last published, Netflix and YouTube accounted for over 50% of North American broadband traffic.
Screen casting may be an emerging market, or it could just be a flash in the pan.
Click to expand...
Click to collapse
Well I guess Samsung is the largest supplier of Flat Screens in NA just like Apple is the biggest supplier of Smart Phones in NA...
Until you realize combine all the NOT Samsung Models into an US vs THEM and they are not the Majority by any means...Same with Apple vs Android as opposed to Apple vs Samsung itself.
As for the DRM you forget that DIAL doesn't care and leaves using or not using up to the content provider. It's there if you want it and if not you only have to support the DIscover and Launch capabilities.
Is Sony (who owns a majority of content compared to Samsung) going to cut out DIAL for Samsung's proprietary system?
Doubtful!
And since the CCast and DIAL supports ANY TV with HDMI input it has a far better chance of being adopted as a standard than Samsung's device is.

IMO most of the current desire for screencasting is really a "backup plan" for content that is currently not supported via DIAL. "___ isn't supported so I want to mirror my screen/tab."
So the mainstream correct solution would be to get the desired content providers on-board with Google Cast.
That would leave non-"canned" content for screen mirroring (games in a second screen model, general browsing, presentations, Skype, etc).
I'd love to see a native Skype for Chromecast using the microphone and controls on my tablet/phone with video on the TV but keeping it in sync might be nontrivial engineering on the Skype end.

Asphyx said:
As for the DRM you forget that DIAL doesn't care and leaves using or not using up to the content provider. It's there if you want it and if not you only have to support the DIscover and Launch capabilities.
Click to expand...
Click to collapse
I can only invite you, again, to look at the actual casting API rather than rely on assumptions.
It's NOT the same as that last July and it absolutely, positively does recognize casting DRM content.
Start here -
https://groups.google.com/a/chromium.org/forum/m/#!topic/apps-dev/emlKA4C-c90
And then Google for what's happened since, along with Koush's commentaries.
Is Sony (who owns a majority of content compared to Samsung) going to cut out DIAL for Samsung's proprietary system?
Doubtful!
And since the CCast and DIAL supports ANY TV with HDMI input it has a far better chance of being adopted as a standard than Samsung's device is.
Click to expand...
Click to collapse
Did you even read the article to discover that Samsung is using a superset of DIAL and support by Sony, LG, and Panasonic TV sets is expected?
---------- Post added at 04:14 PM ---------- Previous post was at 04:07 PM ----------
bhiga said:
IMO most of the current desire for screencasting is really a "backup plan" for content that is currently not supported via DIAL. "___ isn't supported so I want to mirror my screen/tab."
So the mainstream correct solution would be to get the desired content providers on-board with Google Cast.
That would leave non-"canned" content for screen mirroring (games in a second screen model, general browsing, presentations, Skype, etc).
Click to expand...
Click to collapse
Have you checked out what Vbukit is planning on supporting with Chromecast?
Pretty interesting, I think.
Not sure about getting Skype sorted out.
It seems like every time Skype updates, it's a step backwards, but that's just my off-topic opinion.

EarlyMon said:
Have you checked out what Vbukit is planning on supporting with Chromecast?
Pretty interesting, I think.
Not sure about getting Skype sorted out.
It seems like every time Skype updates, it's a step backwards, but that's just my off-topic opinion.
Click to expand...
Click to collapse
Yes, Vbukit is a little rough around the edges, but I can definitely see it being useful for presenters and educators especially.
Agree with you on Skype...
Back on-topic, there isn't a lot of technical copyright/DRM concern regarding casting anything you see on the screen - after all, if you can see it on the screen, you've seen it already. It's just that the legal types are not technical, highly likely to make crazy conclusions and assumptions, and get paid no matter what they do - so it's in their best interest to make issue of little things. I've personally seen warnings from the copyright hunters complete with ISP traces down to the router endpoint too, so they are watching and waiting to pounce.
I still hope an optimized device mirroring comes as something deeper within the Android OS itself.
Something akin to RemoteX in the Windows space, which is a "remote render" or offload of the graphic drawing functions. Anything that's not reliant upon a local bitmap could be rendered on Chromecast, rather than sent as large/inefficient bitmap data or CPU-intensive compressed data. That would make some "twitchy" games playable, especially if Chromecast has enough memory/storage to cache bitmaps that it does end up needing. Full-screen video, of course, doesn't benefit, nor does typical FPS games since the entirety of the screen is being updated with bitmaps.
For fun, I played a video on my phone and watched it on my computer (no audio) via TeamViewer. It took me back to the early 90's.
We've waited for apps and other optimized content this long, let's see what Google delivers.

Content providers have been successfully inhibiting HDMI and MHL output from their apps running on Android devices.
I believe that the casting API changes may have them in mind, but that's pure conjecture on my part.
I think it's ridiculous but so long as people check the boxes and agree to the terms of service, they're free to enforce it.

Chrome cast appearing under cast screen

When I go to settings, then display then Chromecast instead of getting no nearby devices found I see the chromecast!
If I click it it says casting failed, but surely thats a sign it's definitely happening very soon?
It does it on my unrooted stock Nexus 7 and Nexus 4. And my CC is stock as well.

generationgav said:
When I go to settings, then display then Chromecast instead of getting no nearby devices found I see the chromecast!
If I click it it says casting failed, but surely thats a sign it's definitely happening very soon?
It does it on my unrooted stock Nexus 7 and Nexus 4. And my CC is stock as well.
Click to expand...
Click to collapse
Yes it will get here in time...
As of now I expect that the Android side is done or almost done and it will only work for Google who have a developer version that either has the Mirror App built into the CCast or a Whitelist that allows it.
There is a lot more work on the Android side to get it to work than there would be on the CCast side so it makes sense the Android side of the support would show up first and the CCast side will be unavailable to public until they announce it as officially supported.
And from what I read only Google Experience (aka Nexus) devices will have it at that time....

I definitely hope/suspect Google is making firmware changes in Chromecast to head in that direction. Likely right now it's simply sending an mDNS/Bonjour advertisement that the built-in Miracast support can see.

bhiga said:
I definitely hope/suspect Google is making firmware changes in Chromecast to head in that direction. Likely right now it's simply sending an mDNS/Bonjour advertisement that the built-in Miracast support can see.
Click to expand...
Click to collapse
I think the finding of the unit is already part of the Media Router Library in Android...Thats what most of the Apps are using I believe to find the Available devices.
What may be missing is the code to make a screen for the CCast or if that is done the actual Player side of the CCast which Google could have access to but User CCasts do not either due to it not being included in the latest updates or not white listed to work.
The Cast Screen already shows for Miracast. The MR Library already has what it needs to find the device and it probably also has the code to list in cast screen (since it has to find the device first) so it may be the stuff that happens AFTER you select the device that isn't finished or hidden from public use at the moment.
I'm hoping they put the player app into the ROM so that it will work without the need for internet load because not every place you might want to do a presentation has Internet access.

Chromiumcast OS

Since Chromecast OS is basically a cut-down version of Chrome OS, shouldn't the code be in Chromium OS codebase?
If so, we should build a Chromiumcast OS and port it to those MiniPC's on them market (if we have the kernel sources and drivers).
Can anyone check the possibility of the above?
However, since Chrome OS uses a different kind of boot image, we should ask Chainfire for help, since he is working on the Chromebook Pixel, as it has such a boot image.
It is funny thought, Google puts Android on a Chromebook, and we may put Chrom(ium) OS on Android devices.
Update 1: Sorry for posting this here, XDA Labs isn't letting me reply to my own thread, but why not port it?
We should make it a full Chromium OS (with the abilities to make a local owner account and recieving casts, as well as casting to another device), while we're at it.
Update 2: Apparently it's a known XDA Labs server API issue, they're working on though, for now I need to wait for there to be a 2nd page to be able to post seperately from the opening post.
If it's just a webpage, then how about packaging it for the different systems (Windows, OS X, Linux, Android, Ubuntu Touch, Firefox OS, iOS, Windows Modern (8/8.1), Windows Universal (10), Sailfish, Unix, Chrome OS, etc.)?
Yes, I'm aware that half of these technically (via ports, for example) are either Linux or Unix (and that Linux is a port of Unix).
I would have included SkyOS, however it appears to have been discontinued before even graduating Alpha... several years ago.

It's not really a cut down version of Chrome OS but more of a cut down version of the Chrome Browser sans any ability to run Chrome OS Apps.
Similar to the chrome browser you find in an Android Phone.

It has nothing to do with what the OS is based on, the important part isn't the OS, but the actual cast receiver application. I was tinkering around with it for a little while and ended up with a not-entirely-functional APK file that implemented a cast receiver, using actual google code and libraries. Installed it on a Nexus 7, which was discoverable as a cast receiver on the network. More important thing to work on led to ignoring the project for a while.

doitright said:
It has nothing to do with what the OS is based on, the important part isn't the OS, but the actual cast receiver application. I was tinkering around with it for a little while and ended up with a not-entirely-functional APK file that implemented a cast receiver, using actual google code and libraries. Installed it on a Nexus 7, which was discoverable as a cast receiver on the network. More important thing to work on led to ignoring the project for a while.
Click to expand...
Click to collapse
The Cast Receiver is usually not much more than an HTML5 webpage.

Asphyx said:
The Cast Receiver is usually not much more than an HTML5 webpage.
Click to expand...
Click to collapse
The cast receiver is a LOT more than a webpage.

doitright said:
The cast receiver is a LOT more than a webpage.
Click to expand...
Click to collapse
you can browse them all in just about any browser.
Want proof
Look at the linkage in the whitelist and go to the URLs for any receiver...
Example....
https://www.gstatic.com/cv/cast/apps/receiver/webrtc/stable/receiver1.html
They may call them HTM5 Applications but when it comes right down to it there is no difference between that and a webpage. Only in rare cases will they put security that denies a browser from loading them and in most cases if it fails to work it is only because they require and use some firmware code (i.e. Video Player) to function.

Asphyx said:
you can browse them all in just about any browser.
Want proof
Look at the linkage in the whitelist and go to the URLs for any receiver...
Example....
https://www.gstatic.com/cv/cast/apps/receiver/webrtc/stable/receiver1.html
They may call them HTM5 Applications but when it comes right down to it there is no difference between that and a webpage. Only in rare cases will they put security that denies a browser from loading them and in most cases if it fails to work it is only because they require and use some firmware code (i.e. Video Player) to function.
Click to expand...
Click to collapse
That web page does absolutely nothing.

doitright said:
That web page does absolutely nothing.
Click to expand...
Click to collapse
Except load the receiver app that is waiting for linkage information from the app that was supposed to launch it when it connected to the CCast!
99.9% of the work is done at the controlling device not the receiver app.
That is the only thing the CCast actually loads the rest is sent to that receiver by the Controler app!
When you connect to the CCast from an app that's all the CCasts loads. Once loaded you can then send content to that Receiver.
Here is the receiver app Plex tells the CCast to load when you first connect their App to the CCast....
https://chromecast.plex.tv/production/index.html
The receivers are nothing more than webpages with various media players and java applications.

Asphyx said:
Except load the receiver app that is waiting for linkage information from the app that was supposed to launch it when it connected to the CCast!
99.9% of the work is done at the controlling device not the receiver app.
That is the only thing the CCast actually loads the rest is sent to that receiver by the Controler app!
When you connect to the CCast from an app that's all the CCasts loads. Once loaded you can then send content to that Receiver.
Here is the receiver app Plex tells the CCast to load when you first connect their App to the CCast....
https://chromecast.plex.tv/production/index.html
The receivers are nothing more than webpages with various media players and java applications.
Click to expand...
Click to collapse
Just keep telling yourself that it actually does something. :good:

doitright said:
Just keep telling yourself that it actually does something. :good:
Click to expand...
Click to collapse
There really is no teaching the ignorant....
That page is the only thing the CCast loads!
The rest is done on the mobile device and that receiver does nothing without the mobile device connecting to that page you say does nothing...
Tell me did you try reading the source code of that page or was that too difficult for you?

Asphyx said:
There really is no teaching the ignorant....
That page is the only thing the CCast loads!
The rest is done on the mobile device and that receiver does nothing without the mobile device connecting to that page you say does nothing...
Tell me did you try reading the source code of that page or was that too difficult for you?
Click to expand...
Click to collapse
Let me make this very clear;
1) Install https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en
2) Run it.
3) hit the chromecast button. Oh, there is none! Too bad.

doitright said:
Let me make this very clear;
1) Install https://play.google.com/store/apps/details?id=com.netflix.mediaclient&hl=en
2) Run it.
3) hit the chromecast button. Oh, there is none! Too bad.
Click to expand...
Click to collapse
Took you long enough to find the ONE RECEIVER APP (and it is the ONLY APP) that doesn't get loaded from the WEB because it is part of the CCast Firmware!
I find it interesting that in a discussion of RECEIVER APPS you show something from the play store where there are no receiver apps to try and prove your wrong point.

Just look at the Chromecast firmware, there's custom ROMs here. In theory you could just look at it and experiment...

I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?

moriel5 said:
I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?
Click to expand...
Click to collapse
That would be awesome!

I think it could be a perfect combo to turn a Raspberry Pi into a casting device. Chromium OS already exists for Raspberry Pi, but it still has to be improved. http://www.chromiumosforsbc.org/

DaniPhii said:
I think it could be a perfect combo to turn a Raspberry Pi into a casting device. Chromium OS already exists for Raspberry Pi, but it still has to be improved. http://www.chromiumosforsbc.org/
Click to expand...
Click to collapse
I agree, but I would love if someone managed to remove the mandatory Google login, otherwise I won't use it.
Deleted my account some time back, don't want to open another one.

moriel5 said:
I understand that there is no point in porting ChromiumOS, but what about the AndroidTV UI, with Cast Recieving built-in?
Click to expand...
Click to collapse
I was searching online for this b/c i figured someone would have done it by now. I'd really like to see android TV on chromecast

x000x said:
I was searching online for this b/c i figured someone would have done it by now. I'd really like to see android TV on chromecast
Click to expand...
Click to collapse
But the Google log-in should be optional, not mandatory.