3 ms·

I switched to iPhone, in part, because Chromecast's casting protocol was so unstable. It just... stopped working consistently. AirPlay seems to still work rathe

I switched to iPhone, in part, because Chromecast's casting protocol was so unstable. It just... stopped working consistently. AirPlay seems to still work rather well, but it was substantially more expensive and doesn't really work with non-Apple devices (though the remote mostly alleviates this). Idk, I think the real issue was it was probably "too complicated" for the average consumer. The type of person who is sitting at a TV probably wants something with a remote that behaves independent of their phone, not relies entirely on it for it to work. I love Chromecasts, but I can see why they're going away even if it makes me sad.

cubefox 2y ago
> I switched to iPhone, in part, because Chromecast's casting protocol was so unstable. It just... stopped working consistently. I had a similar problem with some (Android phone) apps. Casting a movie, and after half an hour or so the app would lose its connection to the Chromecast. Which meant you couldn't control (e.g. seek backward/forward) the movie anymore without restarting it (the movie). This didn't happen with some other apps though, e.g. the Google TV app. Apparently it is easy to not properly implement the Chromecast connection. Perhaps the connection gets terminated when the phone goes to idle mode, unless you do something to prevent that.
- packetlost 2y ago
  Yeah, that was a common issue with me. I had significantly worse issues though, my chromecast would hard lock and/or have very strange visual glitches that required a reboot to fix, typically about 10-20 minutes into playing something. That's if I even got to that point because half the time it would just refuse to actually play anything without a reboot 95% of the time I went to use it.