Originally Posted by mustbepbs View Post
Thanks. Seems like a huge oversight considering the desktop Chrome is capable.
Design decision, I'm sure.

The desktop Chrome does real-time encoding of the tab (or desktop), in addition to whatever rendering is going on. That's how it achieves tab casting - and that's why tab casting doesn't work well on underpowered machines. It's also why there's lag.

Makes more sense for them to pursue screen mirroring built into the kernel, rather than an app, to reduce latency and ensure a good user experience.
-- Brandon // Google Chromecast threads: FAQ - READ THIS FIRST! || Rootable Serial Numbers
Mini-FAQ: What's the big deal with root? || Mini-FAQ: Rooting with FlashCast || Assemble a powered OTG cable
WiFi Bandwidth and Router considerations || Not all 1080p/720p is created equal
Follow the rules / Use 'Search' before posting / Post in the correct sections / Do not spam the board / Press thanks, don't post 'Thanks'