zlacker

[parent] [thread] 3 comments
1. _puk+(OP)[view] [source] 2025-12-05 06:36:58
I imagine that's a big part of the drive behind discontinuing Chromecast support..

https://www.androidcentral.com/streaming-tv/chromecast/netfl...

replies(3): >>StrLgh+n3 >>kotaKa+lJ1 >>davidm+Ly4
2. StrLgh+n3[view] [source] 2025-12-05 07:22:59
>>_puk+(OP)
I doubt that. Netflix has an app on TVs as old as 8-10 years now. SoCs in such TVs aren't enough to decode AV1. They're stuck with H.264 for a long time.
3. kotaKa+lJ1[view] [source] 2025-12-05 17:08:58
>>_puk+(OP)
Nah, that's more "we can't get ad injection working on the old Chromecast client" because it still works on early Chromecasts for ad-free plans.
4. davidm+Ly4[view] [source] 2025-12-06 17:28:05
>>_puk+(OP)
I can't figure out an answer to why they'd do this. They're still supporting their custom Chromecast "receiver" app (for now?), which is a standard HTML app. But now they're detecting the Chromecast-capable device model, looking it up in an allowlist, then conditionally showing the device in the Netflix App's Cast UI.

This would mean if you have a new device and an old device in the same network the Netflix app might show only your old device! What?

Maybe I'm misunderstanding what they've done here?

[go to top]