|
|
|
|
|
by yjftsjthsd-h
1308 days ago
|
|
Yeah, I wondered about the Android situation; Android itself is semi-standard, in that once you get the hardware support and a way to run your image it's not too hard to build AOSP for nearly any phone. On the other hand, that bit about getting a way to run your own ROM is, on average, awful and device-specific. Still, I suspect that it's better than TVs that run completely different OSs to start with. Edit: Oh, and AFAIK a lot of those OSs aren't FOSS in the first place, which makes things harder; at least with Android the vendor is legally obligated to give you the kernel source and then you can stick that in AOSP and probably get a working image. Other than WebOS, I don't think TVs have an equivalent. Agreed that content support and DRM are a difficulty. I know that the ink price gouging is part of why printers are weird, but that results in the default firmware being user-hostile in a way that I would have expected to make people want aftermarket firmware all the more. I suspect that the difficulty there is also something about fragmentation and perhaps a lack of devices that even try to be open (Google publishes all the documentation and source to build AOSP for a Pixel phone; I'm aware of zero printer vendors doing so). |
|