[–] 1 point 3 months ago

I've not experienced the stream ending, but there disconnect is definitely an issue. Might be app specific?

When I tested Chromecast with google TV (5 years ago to be fair, it might be fixed now), if I casted from my phone, I then had to use the remote to choose my Netflix account and choose the show again from scratch. So it was two steps on two devices, for no good reason. It also didn't connect to WiFi properly and didnt have Ethernet, so that killed its functionality as well.

  • source
  • parent
  • context
  • [–] 39 points 3 months ago (6 children)

    Android Auto uses 5GHz WiFi direct, so your headunit needs to support that. If your headunit only supports 2.4GHz, you'll be a bit out of luck.

    Spotify streaming may be okay with the 2.4GHz or even just plain Bluetooth.

  • source
  • [–] 2 points 3 months ago* (1 child)

    There were definitely some shitty Chromecast apps. ABC in Aus had a terrible one. There are also some pretty shitty TV apps as well :/

    Ultra was good for connectivity, as it has an Ethernet port. Relying on wifi on a streaming stick behind a TV was tough. My TV behaves as a signal blocking wall, anything WiFi behind it is a dead zone.

    I also haven't tried the new Chromecast with google TV in a few years, but it was so terrible I returned it immediately and started scouring eBay for another Ultra. I am very sad Google killed the plain Chromecast line.

  • source
  • parent
  • context
  • [–] 2 points 3 months ago (3 children)

    Chromecast doesnt use your phone for decoding. It just tells the stick to play the video, and it plays it directly. It shouldn't drain your phone at all.

    The remote is a personal preference, but I was happy for the phone to be the remote. Having a second remote didnt gain me anything.

  • source
  • parent
  • context
  • view more: ‹ prev next ›