Live data from Hacker News

Google TV

tv.google

281–290 of 448 posts

Re: Google TV

#281
post #255

"Chromecast with Google TV requires a TV with an HDMI port" How come nearly all video dongles want you to plug them into an HDMI port on your TV? Wouldn't it make more sense to plug them in to an HDMI port on your A/V receiver? Unless you have a fairly recent TV and receiver, the TV can only send up to 5.1 DTS or Dolby compressed audio to the receiver, due to bandwidth limits of ARC. You need a system with eARC if yo…

Because of HDMI-CEC. The dongle can control things on the TV via this technology. This product specifically has a remote that I believe only interacts via HDMI-CEC. I don't know if it's possible for the HDMI-CEC to pass through a receiver to the TV itself for this purpose.

Yes, that’s a feature in many receivers. My older Chromecast turns on the receiver, sets the receiver input, and turns on the TV. I’m guessing this new one would work perfectly fine, too.

Re: Google TV

#282

Earlier quoted context omitted.

The last time I checked, Netflix was capped at 720p on non-Android Linux machines, but it's been a while since I've actually checked. I think the sentiments and conclusions in this thread[1] reflect the state of streaming HD content from Netflix on Linux, still. [1] https://www.reddit.com/r/Ubuntu/comments/c26pc0/netflix_1080...

720p is High Definition by definition.

You got me there.

Re: Google TV

#283
post #246

Earlier quoted context omitted.

I don’t know if Google TV is just a launcher, but I can answer the question "what is a launcher?" On Android systems, a launcher is the home screen plus a little more. iPhone doesn’t have this concept as there's only one "launcher": the home screen. On android, however, you can install apps to radically change your home screen layout. Some are terminals, some are just A-Z lists of your apps, etc. A launcher on Androi…

Thanks for the reminder about why I don’t use Android. I definitely don’t want to be screwing with my phone more than I already do.

You don’t have to, it’s completely optional.

Re: Google TV

#285
post #255

"Chromecast with Google TV requires a TV with an HDMI port" How come nearly all video dongles want you to plug them into an HDMI port on your TV? Wouldn't it make more sense to plug them in to an HDMI port on your A/V receiver? Unless you have a fairly recent TV and receiver, the TV can only send up to 5.1 DTS or Dolby compressed audio to the receiver, due to bandwidth limits of ARC. You need a system with eARC if yo…

You definitely can plug it into a receiver's HDMI input port and work well. That quote only means if you still have a TV that only takes analog inputs or something, then you won't be able to plug the Chromecast in.

Re: Google TV

#286
post #283
post #246

Earlier quoted context omitted.

Thanks for the reminder about why I don’t use Android. I definitely don’t want to be screwing with my phone more than I already do.

You don’t have to, it’s completely optional.

For my phone I just prefer fewer things to mess with in general, and a smaller API surface, since I don’t want to be tweaking and untweaking shit on a device which is already so unergonomic. On my desktop I prefer Windows and Linux to mess with stuff.

Re: Google TV

#288

Google just deprecated Android TV as well: https://9to5google.com/2020/09/30/android-tv-replaced-google...

Google's product team is just clueless, yet I am sure they are 'laser focus' on the metrics.

It is laughable yet sad.

Re: Google TV

#289
post #286
post #283

Earlier quoted context omitted.

You don’t have to, it’s completely optional.

For my phone I just prefer fewer things to mess with in general, and a smaller API surface, since I don’t want to be tweaking and untweaking shit on a device which is already so unergonomic. On my desktop I prefer Windows and Linux to mess with stuff.

I don’t want the ability to modify things and make them better because they already aren’t great...

Re: Google TV

#290
post #269

Earlier quoted context omitted.

The only issue I have with OG Chromecasts is that YouTube channels with 1080p60 videos tend to make the system stutter like crazy. Other than that the original Chromecasts I bought still work pretty much flawlessly.

This infuriates me. Google must know about this, and can surely lower the bitrate for these old Chromecasts, yet have chosen not to. Every time I encounter this on my old Chromecasts it reminds me of how they ruined the Nexus 7 with its final major os update. Blatantly trying to get people to buy new devices. Do no evil, my arse.

Chromecast Gen 1 never supported 1080p@60 and was advertised upto 1080p@30 or 720p@60. So I don't know how is it okay to expect a device that continues to function after 7 years(I have 2 still functioning) to support something it was never intended to in the first place.
Post reply on HN