Related
This might sound crazy but what if we can eventually hack the Chromecast to cast the actual phone/tablet screen (such as you can currently with the desktop of a computer) and play Android games on an HDTV. Yes, we can just get the Ouya but this would be awesome. Now I have no idea if hacking something like this will make it possible, but this would be pretty cool down the road.
Edit: Something like this actually would be perfect. Had no idea this existed:
Miracast:
http://www.youtube.com/watch?v=BYx9YNoD014
tanw42 said:
This might sound crazy but what if we can eventually hack the Chromecast to cast the actual phone/tablet screen (such as you can currently with the desktop of a computer) and play Android games on an HDTV. Yes, we can just get the Ouya but this would be awesome. Now I have no idea if hacking something like this will make it possible, but this would be pretty cool down the road.
Edit: Something like this actually would be perfect. Had no idea this existed:
Miracast:
http://www.youtube.com/watch?v=BYx9YNoD014
Click to expand...
Click to collapse
I think that the accessibility of this device and it's price are 2 things what will greatly help the community develop on this. Just like Samsung's All-Share Dongle, i do think it's only a matter of time before we can mirror our screen
I don't think you will be able to play local games from your table or phone in the near future for the simple reason that everything is being streamed from the cloud. Even Chromecasting the current tab or the full desktop, what happens is google sends your full desktop or tab to their cloud and then streams it back up. That adds the 1 second delay between what you see on your screen and what appears on your TV. Trying to play a real time game with a 1 sec delay will be nearly impossible. Maybe in the future when everyone will have a fiberoptic connections, if they can cut that delay down to 10ms, then I would say yes/maybe. But that much fast bandwidth is still out in the future.
The thing though about Chromecast is that Google has the right idea on where things are headed. This is by far the best innovation out there for your TV.
larryvand said:
I don't think you will be able to play local games from your table or phone in the near future for the simple reason that everything is being streamed from the cloud. Even Chromecasting the current tab or the full desktop, what happens is google sends your full desktop or tab to their cloud and then streams it back up. That adds the 1 second delay between what you see on your screen and what appears on your TV. Trying to play a real time game with a 1 sec delay will be nearly impossible. Maybe in the future when everyone will have a fiberoptic connections, if they can cut that delay down to 10ms, then I would say yes/maybe. But that much fast bandwidth is still out in the future.
The thing though about Chromecast is that Google has the right idea on where things are headed. This is by far the best innovation out there for your TV.
Click to expand...
Click to collapse
I think the most likely avenue for this would be to write an app that turns the phone (or laptop) into a "local cloud" that is streaming just like Netflix or Play Music. It would obviously take some development but I don't think it's too outlandish.
The problem with screen mirroring is lag. From what I have seen 250ms lag is the norm with Miracast. There is just no way around it with current tech. I think that is part of the reason for chromecast. It partially eliminates the need for screen mirroring. Chromecast gives the same ability of using your phone/tablet to browse and select content as does Miracast, but you get a full-screen experience with the best possible resolution depending on internet bandwidth. It is also not depending on your device to be the streamer as is the case with Miracast.
I expect to see another Google TV type device with the new Jellybean update and Chromecast that will be more geared towards gaming on the big screen. I predict we will see it in Q4 or Q1 of next year.
Lag might be there on some level, but it definitely doesnt have any impact the probability of chromecast and screen mirroring. Its not about how well it does it, it's about if i can. Its a 35$ gadget, lets not overthink this. If it's at all possible, 250ms lag would still be more than acceptable. Of course, thins would never be a gaming device where real time information in crucial
larryvand said:
I don't think you will be able to play local games from your table or phone in the near future for the simple reason that everything is being streamed from the cloud. Even Chromecasting the current tab or the full desktop, what happens is google sends your full desktop or tab to their cloud and then streams it back up. That adds the 1 second delay between what you see on your screen and what appears on your TV. Trying to play a real time game with a 1 sec delay will be nearly impossible. Maybe in the future when everyone will have a fiberoptic connections, if they can cut that delay down to 10ms, then I would say yes/maybe. But that much fast bandwidth is still out in the future.
The thing though about Chromecast is that Google has the right idea on where things are headed. This is by far the best innovation out there for your TV.
Click to expand...
Click to collapse
While I'm unsure of how it exactly works, I don't think everything is necessarily streamed through the cloud. Using your phone or tablet to play netflix or youtube videos from the cloud - yes...
...but I was able to stream a local mkv video in a chrome tab on my desktop to the chromecast. I doubt it makes the round trip through google since I know my upload speeds are pretty bad. My guess is that google just executes the handshake and the video streams through your intranet directly.
pjsnyc said:
While I'm unsure of how it exactly works, I don't think everything is necessarily streamed through the cloud. Using your phone or tablet to play netflix or youtube videos from the cloud - yes...
...but I was able to stream a local mkv video in a chrome tab on my desktop to the chromecast. I doubt it makes the round trip through google since I know my upload speeds are pretty bad. My guess is that google just executes the handshake and the video streams through your intranet directly.
Click to expand...
Click to collapse
You are correct about chrome tab mirroring. It goes straight over your local network, but the native codec support of the current Chromecast device is lacking which may be improved by savvy developers found right here. However, since tab mirroring only works from PCs, I think it is a step backwards.
007shark said:
You are correct about chrome tab mirroring. It goes straight over your local network, but the native codec support of the current Chromecast device is lacking which may be improved by savvy developers found right here. However, since tab mirroring only works from PCs, I think it is a step backwards.
Click to expand...
Click to collapse
My understanding is that if you have the correct codecs installed on your desktop/laptop with chrome, you should theoretically be able to play any file type. I saw a video of it working with plex or simply navigating your local drives with chrome. Whether or not native codec support is lacking on the chromecast is moot imho. Tab mirroring on a phone or tablet should eventually come, I just think the devices need more horsepower so to speak.
polish_pat said:
Lag might be there on some level, but it definitely doesnt have any impact the probability of chromecast and screen mirroring. Its not about how well it does it, it's about if i can. Its a 35$ gadget, lets not overthink this. If it's at all possible, 250ms lag would still be more than acceptable. Of course, thins would never be a gaming device where real time information in crucial
Click to expand...
Click to collapse
I am with you. I think this little device will be one of the more popular developer projects on xda.
---------- Post added at 01:45 PM ---------- Previous post was at 01:36 PM ----------
pjsnyc said:
My understanding is that if you have the correct codecs installed on your desktop/laptop with chrome, you should theoretically be able to play any file type. I saw a video of it working with plex or simply navigating your local drives with chrome. Whether or not native codec support is lacking on the chromecast is moot imho. Tab mirroring on a phone or tablet should eventually come, I just think the devices need more horsepower so to speak.
Click to expand...
Click to collapse
Okay, so it is transcoding on the fly. I agree with you on not yet on the phones because of lack of processing power. Miracast is still the better option with portable devices even with the minor lag.
I guess I am dreaming for, because Google surprised me with this gadget and I was unable to get one before they were all sold out, an all encompassing gadget that has DLNA, Miracast, and Chromecast in the same form factor. I think the DLNA might be able to be added to this. I doubt Miracast would be able to, though.
007shark said:
...
I guess I am dreaming for, because Google surprised me with this gadget and I was unable to get one before they were all sold out, an all encompassing gadget that has DLNA, Miracast, and Chromecast in the same form factor. I think the DLNA might be able to be added to this. I doubt Miracast would be able to, though.
Click to expand...
Click to collapse
I kinda like it the way it is. While DLNA has been around for a while, I honestly havent seen a simple implementation of it yet (unless you lock yourself into one brand/ecosystem). I am excited that the hacking community is already tearing this thing apart, but the simplicity of setting it up and just getting it to work for the masses is ridiculous at this price.
I lucked out in getting mine - my coworker was able to arrange a pickup at bestbuy and sold it to me at price when he realized he couldn't mirror a mobile chrome tab.
pjsnyc said:
I kinda like it the way it is. While DLNA has been around for a while, I honestly havent seen a simple implementation of it yet (unless you lock yourself into one brand/ecosystem). I am excited that the hacking community is already tearing this thing apart, but the simplicity of setting it up and just getting it to work for the masses is ridiculous at this price.
I lucked out in getting mine - my coworker was able to arrange a pickup at bestbuy and sold it to me at price when he realized he couldn't mirror a mobile chrome tab.
Click to expand...
Click to collapse
I like the DLNA for getting photos, videos, and music from my device to the TV. Samsung's AllCast from their phones/tablets work great this way even with non-Samsung DLNA devices. If Google implemented DLNA with Chromecast then a phone/tablet's native gallery and video apps could seamlessly work as the Netflix and YouTube apps do without a normal consumer understanding how it works. And also without having to sync everything to the cloud.
007shark said:
I like the DLNA for getting photos, videos, and music from my device to the TV. Samsung's AllCast from their phones/tablets work great this way even with non-Samsung DLNA devices. If Google implemented DLNA with Chromecast then a phone/tablet's native gallery and video apps could seamlessly work as the Netflix and YouTube apps do without a normal consumer understanding how it works.
Click to expand...
Click to collapse
I guess this is where you and I disagree. The 'understanding how it works' part. For example - once you get chromecast set up with your laptop on your couch, sharing photos and videos with other people in your livingroom from facebook is easy to understand for anyone. 'Native' for the masses is what is currently showing in the browser tab.
pjsnyc said:
I guess this is where you and I disagree. The 'understanding how it works' part. For example - once you get chromecast set up with your laptop on your couch, sharing photos and videos with other people in your livingroom from facebook is easy to understand for anyone. 'Native' for the masses is what is currently showing in the browser tab.
Click to expand...
Click to collapse
That is exactly the difference. I don't use a laptop in my living room. I use my tablet and/or phone. I think that is also the growing trend at least from my circle of friends and family.
EDIT: I use to watch TV with a laptop in my lap, but haven't done that in a couple years since I got a tablet.
For games we could see some games go to cloud based solution. This could work by your phone/controller sending information to the server that in turn sends back appropriate results to the Chromecast. So games aren't played on the phone but on the server the phone just sends commands.
Yeah miracast is sick
Sent from my SPH-L720 using xda premium
pjsnyc said:
I kinda like it the way it is. While DLNA has been around for a while, I honestly havent seen a simple implementation of it yet (unless you lock yourself into one brand/ecosystem). I am excited that the hacking community is already tearing this thing apart, but the simplicity of setting it up and just getting it to work for the masses is ridiculous at this price.
I lucked out in getting mine - my coworker was able to arrange a pickup at bestbuy and sold it to me at price when he realized he couldn't mirror a mobile chrome tab.
Click to expand...
Click to collapse
http://elinux.org/DLNA_Open_Source_Projects ?
007shark said:
I am with you. I think this little device will be one of the more popular developer projects on xda.
---------- Post added at 01:45 PM ---------- Previous post was at 01:36 PM ----------
Okay, so it is transcoding on the fly. I agree with you on not yet on the phones because of lack of processing power. Miracast is still the better option with portable devices even with the minor lag.
I guess I am dreaming for, because Google surprised me with this gadget and I was unable to get one before they were all sold out, an all encompassing gadget that has DLNA, Miracast, and Chromecast in the same form factor. I think the DLNA might be able to be added to this. I doubt Miracast would be able to, though.
Click to expand...
Click to collapse
I don't see any hardware limitations for Mircacast at this moment, still digging through the tech specs and kernel though
I would love to see a physical remote used with the chromecast. I feel that is a major item missing when it comes to controlling a set top box. This wouldn't be all that helpful with casting, but for netflix/hulu use and other apps it would be great. I like having dedicated/physical buttons for things.
Not sure where to begin on this journey. Anyone else feel the same way I do?
Possible options:
WiiMote - Bluetooth?
Keyboard - bluetooth
Is this someones attemp at a wiimote + chromecast?
https://code.google.com/p/chromecas...entation/ABI/testing/sysfs-driver-hid-wiimote
Don't know what you'd control with that.
You can use a wiimote/dualshock 3 with your android device to control YouTube, if that's what you mean.
Sent from my XT907 using xda premium
Leraeniesh said:
Don't know what you'd control with that.
You can use a wiimote/dualshock 3 with your android device to control YouTube, if that's what you mean.
Click to expand...
Click to collapse
I think they're after a physical implementation of RemoteCast
Closest thing I can think of would be to see if RemoteCast's dev would support some kind of paired Bluetooth controller like a Wiimote, but its function would still be tied to a phone/tablet somewhere.
If Chromecast does well, I wouldn't be surprised if Google releases some firmware that enables the Bluetooth part of its WiFi chip and sells us a remote and/or provides Bluetooth functionality in the SDK. But first things first, they need to release the SDK...
I would be much more interested in some IR Control myself...
Not just for when I'm using the Chromecast but for when I'm not as well.
If implemented it could automatically change your TV to the chromecast input when you cast something to Chromecast and when your not casting it would allow the Chromecast to serve as a conduit to using your tablet/phone as a full IR remote for your TV, Set Top Boxes and whatever else you have at your Home Entertainment system.
Asphyx said:
I would be much more interested in some IR Control myself...
Not just for when I'm using the Chromecast but for when I'm not as well.
If implemented it could automatically change your TV to the chromecast input when you cast something to Chromecast and when your not casting it would allow the Chromecast to serve as a conduit to using your tablet/phone as a full IR remote for your TV, Set Top Boxes and whatever else you have at your Home Entertainment system.
Click to expand...
Click to collapse
Mine already changes the channel and turns the TV on if it's off.
Unless you have an unusual setup, all you need to do is enabled HDMI-CEC in your TV's settings, and make sure Chromecast has power when the TV is off (if you want it to turn the TV on).
IR would be quite complicated, mainly because something has to receive the IR and process it.
You'd probably be better off getting a network-enabled IR receiver/blaster like the GlobalCache GC-100 to do network-triggered IR blasting.
bhiga said:
Mine already changes the channel and turns the TV on if it's off.
Unless you have an unusual setup, all you need to do is enabled HDMI-CEC in your TV's settings, and make sure Chromecast has power when the TV is off (if you want it to turn the TV on).
IR would be quite complicated, mainly because something has to receive the IR and process it.
You'd probably be better off getting a network-enabled IR receiver/blaster like the GlobalCache GC-100 to do network-triggered IR blasting.
Click to expand...
Click to collapse
I don't have that option on my TVs...
As for receiving IR.... no not what I am asking...Just for the chromecast to SEND IR and act as the globalcache device does.just on the Tx side.
I don't want to use a IR remote I want to be able to control the Home Ent system (Ir devices) via my Tablet. All I need is Tx for that and if CC had a mini plug for IR transmitter lead and some IR emitter circuitry it could do it. IR Codes would be set via the Tablet App.
Asphyx said:
I don't have that option on my TVs...
As for receiving IR.... no not what I am asking...Just for the chromecast to SEND IR and act as the globalcache device does.just on the Tx side.
I don't want to use a IR remote I want to be able to control the Home Ent system (Ir devices) via my Tablet. All I need is Tx for that and if CC had a mini plug for IR transmitter lead and some IR emitter circuitry it could do it. IR Codes would be set via the Tablet App.
Click to expand...
Click to collapse
Ahh, I see. Well, I was working within the constraints of what could potentially be done with software development and existing hardware.
Adding an IR minijack to Chromecast is well outside of that.
bhiga said:
Ahh, I see. Well, I was working within the constraints of what could potentially be done with software development and existing hardware.
Adding an IR minijack to Chromecast is well outside of that.
Click to expand...
Click to collapse
Yes but I'm already thinking towards Chromecast II! LOL
Or would they call it Chromecast 2014 like they did with the Nexus by adding rear facing camera and LTE! LOL
Asphyx said:
Yes but I'm already thinking towards Chromecast II! LOL
Or would they call it Chromecast 2014 like they did with the Nexus by adding rear facing camera and LTE! LOL
Click to expand...
Click to collapse
I'm hoping more along Chromecast 2015 - at least give the current one a full year before making it obsolete!
bhiga said:
I'm hoping more along Chromecast 2015 - at least give the current one a full year before making it obsolete!
Click to expand...
Click to collapse
Maybe we both should just hope we get rid of the whitelist before 2020! LOL
Doesnt have to be an IR remote. Could be wireless like on the Roku, or bluetooth like on the Wii.
An IR blaster on the ChromeCast would be helpful for learning remotes, so you could have 1 remote to control all of your devices.
I just prefer the physical feel of a remote. Not having to fumble around looking for capacitive buttons.
Im trying to find a cheap alternative to a Roku 3.
$35 Chromecast + remote would be cheaper than $75+ for the R3.
Why the hell do you need a physical remote when its all network based anyways? IR remote is not needed for any of the apps and an IR remote wouldn't handle all advances functions seamlessly anyways. What do you want an apple TV remote which is about worthless and constantly getting lost anyways? Perhaps and hdmi-cec network based remote might be cool but HDMI cec is still wonky though its a lot better than a few years ago.
sent from my sm-9005.
Asphyx it might be that it is not named HDMI-CEC as the diffrent vendors like to call it there own name. Here is a list over the most well known names of HDMI-CEC and it is something that have been in flat screens the last 5-6 years now so as long your tv is not older then that you should have it.
Code:
Branding Vendor
Anynet Samsung
BRAVIA Sync Sony
KURO Link Pioneer
NetCommand Mitsubishi
REGZA-LINK Toshiba
RIHD Onkyo
SimpLink LG
I am just hoping for more implementation of HDMI-CEC. I would like to use the atual tv remote to play/pause or fast fwd etc. I would also like the ability to NOT turn on the tv when i fire up google music. Now if it could turn on my receiver that would be great
ParanoidDK said:
Asphyx it might be that it is not named HDMI-CEC as the diffrent vendors like to call it there own name. Here is a list over the most well known names of HDMI-CEC and it is something that have been in flat screens the last 5-6 years now so as long your tv is not older then that you should have it.
Code:
Branding Vendor
Anynet Samsung
BRAVIA Sync Sony
KURO Link Pioneer
NetCommand Mitsubishi
REGZA-LINK Toshiba
RIHD Onkyo
SimpLink LG
Click to expand...
Click to collapse
Yes but I'm almost certain that standard was made more recently than the TV I have...
I pretty much have a first Gen HDTV and believe the CEC Protocal was not part of HDMI 1.1
It wasn't available until HDMI 1.2a if I'm not mistaken.
I could check for a firmware upgrade but merely changing the channel on the TV to Chromecast is only part of what I would like it to do.
I suppose I will have to spring for the $200 IRoverIP blaster to get it.
scoobdude said:
I am just hoping for more implementation of HDMI-CEC. I would like to use the atual tv remote to play/pause or fast fwd etc.
Click to expand...
Click to collapse
Many would find that handy - so it is a bit strange that it has not yet been implemented. One reason might be that the chromecast team want to emphasise that a remote is not necessary and that controlling using a mobile device is preferable. I guess that it will be added down the road (just like the delete button was added to gmail).
Arne S said:
Many would find that handy - so it is a bit strange that it has not yet been implemented. One reason might be that the chromecast team want to emphasise that a remote is not necessary and that controlling using a mobile device is preferable. I guess that it will be added down the road (just like the delete button was added to gmail).
Click to expand...
Click to collapse
Actually the most likely reason is they wanted to keep the cost down at it's current $35 and adding any IR or extra CEC support would have driven the price up another 10-20 dollars.
These things we are hoping for may all show up whenever Chromecast II comes along.
Right now they are competing with Miracast dongles that can be had for around the same price point.
I think the target with this initial version was to do Miracast better because it can work over wired networks as well and frees the device that initializes the stream to do other things..
Not possible with Miracast!
Asphyx said:
Actually the most likely reason is they wanted to keep the cost down at it's current $35 and adding any IR or extra CEC support would have driven the price up another 10-20 dollars.
Click to expand...
Click to collapse
The chromecast is already using some CEC functions so additional HW would be probably not be required to implement support for using the TV remote to control the dongle.
Arne S said:
The chromecast is already using some CEC functions so additional HW would be probably not be required to implement support for using the TV remote to control the dongle.
Click to expand...
Click to collapse
Big difference between adding a Transistor or two to a chip that will make a contact to switch to the current input or Power On than it is to put an entire set of them that can do much more complex functions. Just the TV compatibility alone would add to the price.
I agree it should be possible to do easily but these things all need to be added to the silicon which would make it cost more.
This is SOP for any new device you're trying to get adopted. The Next gen will probably add a ton of things to inspire upgrading to it.
Remember the Nexus7 (2012) came with no Rear Facing Camera or LTE to keep the price down as well....
Fast Forward to 2013 and Nexus 7 (2013) has BOTH included!
This version we have now is a proof of concept device, Gets us hooked and serves as a starter platform to get 3rd Party support for it's innovative streaming methods.
And now that is done so the 3rd parties can start making it useful while Google thinks up what the next generation can do that the first gen doesn't do but probably should!
Just a matter of time of you ask me...And don't be surprised to see some Chromecast functionality built into your smart TV that has the full blown IR and CEC support your looking for.
Here is a list of all the functions CEC does most of which have no useful application regarding Chromecast until such time as they decide using Chromecast as an IP Remote device is something they really want to do. And most are not applicable other than play stop and pause.
One Touch Play allows devices to switch the TV to use it as the active source when playback starts (Currently Supported I believe)
System Standby enables users to switch multiple devices to standby mode with the press of one button
Preset Transfer transfers the tuner channel setup to another TV set
One Touch Record allows users to record whatever is currently being shown on the HDTV screen on a selected recording device
Timer Programming allows users to use the electronic program guides (EPGs) that are built into many HDTVs and set-top-boxes to program the timer in recording devices like PVRs and DVRs
System Information checks all components for bus addresses and configuration
Deck Control allows a component to interrogate and control the operation (play, pause, rewind etc.), of a playback component (Blu-ray or HD DVD player or a Camcorder, etc.) (This is what your looking for I sure wouldn't mind having this)
Tuner Control allows a component to control the tuner of another component
OSD Display uses the OSD of the TV set to display text
Device Menu Control allows a component to control the menu system of another component by passing through the user interface (UI) commands
Routing Control controls the switching of signal sources (Currently Supported)
Remote Control Pass Through allows remote control commands to be passed through to other devices within the system (I want THIS!)
Device OSD Name Transfer transfers the preferred device names to the TV set
System Audio Control allows the volume of an AV receiver, integrated amplifier or pre-amplifier to be controlled using any remote control from a suitably equipped device(s) in the system (You and I would BOTH like this!)
Asphyx said:
Big difference between adding a Transistor or two to a chip that will make a contact to switch to the current input or Power On than it is to put an entire set of them that can do much more complex functions. Just the TV compatibility alone would add to the price.
I agree it should be possible to do easily but these things all need to be added to the silicon which would make it cost more.
Click to expand...
Click to collapse
That might be. I do not know. The Chromcast is powered by the Marvel Armanda 1500-mini chip which is also used in other devices. I do not know what CEC capabilities this chip has but according to its documentation it supports HDMI v1.4 while CEC was introduced in v1.3. I think that both the fact that this is a "standard" chip also used in other devices and the fact that it uses HDMI v1.4 points in the direction that the HW in the Chromecast dongle supports more CEC functions than the ones currently exposed.
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.
Can I buy a cheapo ($49 or less) Android 7" tablet to use as a remote for my Chromecast?
It will be a slow low-res tablet, but if it is KitKat 4.4 or higher will it do the job?
Remote control You mean? Installing apps to send to chromecast? It depend of the cores of the tablet and the tablet ram
As long as the Chromecast SDK continues to support the Android version mostly yes.
You'll be able to tell the chromecast to launch youtube, netflix, etc. You won't be able most likely to stream videos from the tablet to the Chromecast.
This all depends on the software you're using continuing to work with your version of Android however. Most applications all they do is tell the Chromecast what method to play a video and request status updates for where they are in the video. If Netflix, for example, decides that KitKat has a severe vulnerability in it and they are risking breaking their movie streaming contracts, they may bump up the minimum required Android version which would mean it would no longer be useful as a remote for you.
If Google stops supporting the older OSes for Chromecast, it would no longer be useful for you.
Right now, yes, it'll most likely work for you. Two years down the line, who knows.
I have a Nook Tablet running @amaces AOSP 7.0 and my husband has an HD running CM 11. The "cast" feature, as far as I can tell, does not seem to do anything. It doesn't see my Win 10 laptop and does not see a generic Miracast dongle I just picked up (the Win 10 PC does see the dongle...).
Does the cast feature support Chromecast? If so, what's the experience like? The main reason my husband's HD is still on CM 11 is to maintain functionality of the HDMI out. But we've run into issues with our local newspaper app (of all things) after an update and are now looking at trying the last CM 13 build to support HDMI out.
It would be simpler if the cast function worked (I.e., cast the entire screen) as well as the really simple HDMI out. I get it, people don't like wires. But for the price (now $10 online at B&N), that cable is pretty sweet.
So...what works for whole screen casting? We don't have smart TV's and don't use any streaming services. 90% of the video material is local, played with either MX player or Kodi. Occasional streams via Kodi.
I added an entry in the FAQ addressing some of these concerns.
nmyshkin said:
Does the cast feature support Chromecast? If so, what's the experience like? The main reason my husband's HD is still on CM 11 is to maintain functionality of the HDMI out. But we've run into issues with our local newspaper app (of all things) after an update and are now looking at trying the last CM 13 build to support HDMI out.
Click to expand...
Click to collapse
Yes, full screen casting definitely wants a Chromecast receiver. I think it works pretty well, especially for static content; highly dynamic content might have slight delays, or out of sync audio. Movies should be fine, but really, you should send video, YouTube, etc using in-app casting, so all A/V processing is done on the receiver (rather than full screen re-encoded on tablet).
nmyshkin said:
It would be simpler if the cast function worked (I.e., cast the entire screen) as well as the really simple HDMI out. I get it, people don't like wires. But for the price (now $10 online at B&N), that cable is pretty sweet.
So...what works for whole screen casting? We don't have smart TV's and don't use any streaming services. 90% of the video material is local, played with either MX player or Kodi. Occasional streams via Kodi.
Click to expand...
Click to collapse
While full screen casting works, for the above reasons, it's always better to use in-app casting, if available. Even with local content, finding an app that processes only the actual media (rather than capture/encode entire screen) is usually preferable. I looked at HDMI intermittently, but no idea what's broken yet.