this post was submitted on 08 Jun 2023
8 points (100.0% liked)
Technology
37717 readers
470 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's quite sad that Google never figured out a way around this issue. The real problem is that they push the responsibility of updating to OEMs, which have no interest in updating their "old phones" (1 year old in most cases) because a new shiny one has been released.
I think the only way to really solve this is to make Android like Windows used to be back in the XP days. OEMs get a base system and they can customize it to their hearts content, but the updates to the base always come straight from the OS developer, no matter if the "OEM customizations" are ready for it or not.
This is really how Google should have built things in the beginning. Provide a stable driver API for hardware then upgrade the OS as needed without OEM cooperation. They are just now getting around to it with things like Treble, IIRC.
Even with things like Treble the updates still have to come from the OEM, so unfortunately I don't see the situation changing any time soon.