Op-ed: It’s time for Google to take responsibility for Android’s security updates | Ars Technica

Op-ed: It’s time for Google to take responsibility for Android’s security updates | Ars Technica

Op-ed: It’s time for Google to take responsibility for Android’s security updates | Ars Technica

Last Friday, Google announced a major new initiative that promises to solve one of the many problems that keeps Android phones from being promptly updated. Coming as a part of the forthcoming Android O, Google will soon begin separating the Android operating system from the hardware-specific drivers and firmware on each individual Android phone in a move called ”Project Treble.” If successful, Project Treble will prevent a repeat of what we saw last year with Android Nougat, when Qualcomm’s unwillingness to support the update on older hardware made it impossible for companies to release the update on older devices even if they wanted to.FURTHER READINGWhy isn’t your old phone getting Nougat? There’s blame enough to go aroundBut as we wrote last week, this is still just a solution for one of Android’s many update problems. Treble can help OEMs support older hardware for longer and with less effort, and that’s unquestionably a good thing. But the core issue remains: wireless carriers and phone makers are still the gatekeepers for updates, and since they all make their money primarily from selling new hardware, they have little incentive to offer continued support for stuff they’ve already sold—especially once it’s no longer on store shelves.

Källa: Op-ed: It’s time for Google to take responsibility for Android’s security updates | Ars Technica

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.