2 ms·
> Updates for Android continue to be a huge problem. As is being pointed out elsewhere, this isn't a vulnerability in an "Android" product. These are TVs runn
by ajross 2y ago
> Updates for Android continue to be a huge problem.
As is being pointed out elsewhere, this isn't a vulnerability in an "Android" product. These are TVs running vendor-maintained AOSP builds. They get updates when and how the vendor decides to do it. It's not related to the (fairly reasonable, though often spun) arguments about updates in the phone licensee ecosystem.
- jmyeet 2y agoThis is a distinction without a difference. It's not like you can take your Android hardware and move to a different software supplier. You're stuck with whatever your OEM chooses to do or not do. It's also something you don't necessarily have knowledge of when you purchase a phone. It's one reason why people (myself include) prefer Apple. You know you're going to get 4-5+ years of updates.
- ajross 2y ago> This is a distinction without a difference. No? For a licensed Android phone there's a clean split between OEM and OS updates, a clear declaration for support period and a OS-managed tracking of updates with clear visibility to the customer. I get that there are constant platforms flames about whether this is acceptable or inferior to Apple's offering, yada yada yada. But the point is that none of that is relevant here, because these aren't phones and aren't running a licensed "Android" variant. They're just TVs running vendor-custom firmware that happens to be based on AOSP, and clearly can't be expected to conform to any update regime except whatever the integrator put together. Basically, the story here is saying "I hacked product A" and you're trying to have an argument like "That's because this unrelated product B is bad". It's a non-sequitur.