Hacker News Reader

Comment by roneythomas6 | Hacker News Reader

My Chromecast from 2013 still works.

Mine still "work" but something changed around 2017 and they became so unreliable I don't bother any more.

The Chromecast to Device connection is lost after about 10 minutes, making all controls not work. Can't pause, skip, select a new episode, etc.

The fix is seemingly random - maybe 50% of the time recasting from the app (Netflix, Hulu, etc) works. 30% of the time mucking around in the Google Home app will work, and 20% of the time I just have to unplug it.

Near as I can tell it's agnostic of client device, casting app, Chromecast gen (I've got 3 different versions around), or router.

We've kindof just given up and gone back to Roku.

Had the same problem. The solution seemed to be a stronger WIFI signal. Adding an extension cable to move the chromecast further away from the TV prevents the tv from blocking signals.

I had a similar problem, turns out my router was dropping bonjour/upnp packets. I think that was preventing my devices from properly discovering what services were available on my network. I never found a solution for the problem (OpenWRT+WRT3200ACM), but bought a different router and the problem magically went away (OpenWRT+R7800).

Could be any number of reasons why you are having issues unfortunately.

Interesting. Thanks for the information. Might be a project for a cold night this winter, or we just are pretty happy with Rokus now.

I'm certain the onset of the problem didn't coincide with a new router, and I've gone through a couple since it started so I assumed that wasn't the issue.

Yeah, who knows. In my case it worked for 1 to 72 hours after rebooting the router, then would drop 100% of the packets until the next reboot. It took some time to figure out what was going on.

I had the same problem, including the deteriorating performance when it used to be reliable (I don't know if the timing is the same but sounds about right), and the router fixed it for me as well. Maybe there were protocol / firmware changes that increased the demand on the router?

I went from a bargain router to a nicer mesh setup this spring and the problem just vanished overnight.

The fix for this is supposed to be go to into your Android settings and turn off battery optimization for Google Home and each app you cast.

It didn't work for me but loads of people reported success with it. It's a shame because I loved the Chromecast but had the exact same issue as you describe.

I bought two of them and loved them for a couple years, at least for the content it opened up.

However casting was unreliable. I never figured it out but I remember posting on HN about it years ago and other people had the same complaint.

Then the YouTube app on my android phone would hang or crash. My Android phone kinda rotted after 4 years or so. I had a dedicated one for chromecast.

Now I just use a wireless keyboard and an Ubuntu box connected to the TV. Works quite well, I can get all the apps and content I want through the browser.

Are you able to do Netflix in HD?

Yes, although the frame rate really sucks. I think that is a separate issue though. (You really notice it on action scenes)

I don't see why there would be any problem with Netflix in HD in the browser on Ubuntu ?

This PC is also from 2012 or so, so I think I should upgrade and maybe the frame rate will improve... I haven't isolated the issue. It's fine for most shows.

But I suspect Netflix encoding quality also sucks, because most people don't care as much as I do, so I haven't debugged it.

> I don't see why there would be any problem with Netflix in HD in the browser on Ubuntu ?

Because there isn't a browser released on Linux that has the right DRM capabilities to run Netflix's DRM, and thus Netflix on Linux is limited to less-than-HD, hence why I asked if you were able to get it working.

I just use Firefox on Ubuntu and it seems fine? Doesn't seem SD. Maybe I'm missing something -- is there a way to check?

The thing I notice is more the frame rate than the resolution. The resolution looks HD to me -- I can tell the difference with offline videos.

Hm I suppose it is possible I am getting some degraded quality from Netflix. I always thought it was because of the old PC and/or their bad encoding quality.

I mainly watch non-demanding video on Netflix, like a cooking show or standup comedy ... YouTube is definitely HD for me.

https://android.gadgethacks.com/how-to/netflix-caps-video-qu...

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.

I use a useragent changer to look like Edge and that seems to be all it takes to get the full-scale HD on Linux. Doesn't seem like Netflix go out of their way to disable it, though useragent sniffing is... Something you should never be doing.

Interesting. I'm going to give this a shot, thanks.

Search for the video "Test Patterns". There's several different resolutions and framerates some with HDR too. That should help you figure out what you're getting.

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.

The 1080p60 bug can be fixed by cutting the plastic lid off the Chromecast and adding a fan.

> The 1080p60 bug can be fixed by cutting the plastic lid off the Chromecast and adding a fan.

I can't tell if you are serious.

I can imagine circumstances where this would work, but... they involve the chromecast having a temp sensor and software to lower the clock speed to prevent overheating, resulting in skipped frames, but at the same time somehow not be able to lower the bitrate of the video stream.

Seems... mildly improbable.

Pretty much every single processor made in the past decade, if not two, has a core temperature sensor along with overheating regulation. Even the Raspberry Pi.

So the overheating regulation is part of the firmware, rather than whatever software is running?

Typically embedded linux systems use the linux CPU frequency scaler, which uses various inputs including CPU temperature to scale the CPU clock frequency.

There is an extra element here... All of what you said is true, but the actual issue is not with the video decoding, but with the thread that feeds data from the network to the video decoder. That thread has some long running stuff running on it, which causes the task to enquire data to the video decode hardware to be delayed.

It used to work years ago, but as more and more software bloat has been added to run in this thread, the delays have increased to the point of stutteryness.

Some videos are jumpy because they have fewer seconds buffered in the hardware decoder.

So, in that scenario, how does the fan help?

Fan leads to the CPU throttling less, so the long-running events on the main thread run faster and delay the tasks that load data into the video decoder less.

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.

Can't YouTube serve up the videos in formats that the original Chromecasts can consume? Surely either YouTube can know which Chromecast is making the request, and serve up an appropriate quality, or allow the Chromecast to request a lower quality version of the video. To be clear, I don't expect to be able to see videos in higher quality than was available at the time of purchase. I expect to be able to 'watch YouTube' as was advertised on the device's box.

I have an occasional issue where the chromecast just doesn't show up on wifi. You have to power it off and then on again. Has happened with a couple of different ones in a couple of different houses (i.e. different wifi networks).

i feel so sorry for your wireless network. They used an ancient chip that totally soaks airtime.

Reply on news.ycombinator.com