so i cant cast chrome tabs from my android phone and have to use PC?
thats pretty much lame and goes against googles policy of android ecosystem (having all your stuff available and connected on all of your devices)
whats with all the restrictions on this thing? did google mention casting from android chrome will be supported in the near future? if not, anything modders can do about it (altho i doubt they can mod chrome..)?
Yes, currently you can't cast Chrome tabs from Android and you have to use a PC. Google's policy is irrelevant - you still have all your stuff (bookmarks, whatever) - but that doesn't mean you can
do everything you can on desktop Chrome on mobile Chrome.
Despite the popular notion that Google is "the man" and holding you back, it's not the case here.
Casting a tab or the desktop requires
real-time compression to H.264 - that's a non-trivial amount of CPU power.
To put things into perspective,
Intel's Sandy Bridge and Ivy Bridge have specific hardware optimizations for accelerating H.264 compression.
NVIDIA CUDA and AMD Stream use the GPU to help accelerate H.264 (and other) compression.
This is all because except in rare super-high-performance server type configurations,
the desktop computer lacks the CPU power to compress to H.264 in real-time at reasonable framerates.
NVIDIA's ShadowPlay is the perfect scenario, but that uses
a hardware H.264 encoder on the graphics card.
For the sake of argument, let's say mobile Chrome was modified/upgraded so it could use the Google Cast extension.
The load on the device would be approximately 4x that of a Skype video call using the high-res camera (usually rear), perhaps even more (I'm not sure what compression Skype uses).
Even if the processor could keep up, you'd be out of battery quite quickly.
Not to mention having this load
in addition to whatever the load of what you're trying to do (play a video, play a game, etc) is.
So fact of the matter is, mobile platforms just aren't quite there yet.
That's probably why mobile Chrome doesn't support extensions to begin with - it's the user experience. If a user loads their mobile Chrome with a bunch of extensions, Android users will complain that their browser is slow and clunky, and the Apple zealots will do their thing. Doesn't matter which one can do more or less - if the user experience suffers, it hurts the platform.
Now, Google is working on Android screen mirroring (and so is Koush), and ultimately that would be
the solution, as it could be implemented in a lower level than the regular user app, which would provide some consistency in the casting quality while not bogging down the system so apps are sluggish or unresponsive.
But we'll have to wait.
Having the remote end compress UI and video to send to Chromecast is
not Chromecast's core competency or usage model. Chromecast is made to do what it currently does well - pull already-compressed streams from the Internet and play them.