One of the things that Apple and iOS can hold over the Android ecosystem is how fast OS updates on iPhones and iPad are installed. However, compared to the abundance of potential hardware available in the Android ecosystem, Apple is restricted to a relatively smaller set.
It has been a problem with Android from the start[1], and in 2017, Google took steps to make the update process smoother with Project Treble[2], which split the OS framework off from the low-level vendor implementation in each handset.
And it worked[3], to an extent.
As Google explained in a blog post[4] on Wednesday, when an Android OS release happens, Google publishes a generic image from the open-source version of Android that is guaranteed to be backwards-compatible with the prior three versions of vendor implementations. New devices must also have vendor implementations that are compatible with the generic images.
"This is the primary vehicle for reducing fragmentation within the OS framework," Google said.
"Besides the reuse of a vendor implementation across OS updates, the Treble architecture also facilitates the re-use of the same OS framework code across different vendor implementations."
However, this picture gets much murkier for a company like Qualcomm, who needs to support many of its different system-on-chip (SoC) products, and device makers purchasing the silicon.
"The result is that three years beyond the launch of a chipset, the SoC vendor would have to support up to six combinations of OS framework software and vendor implementations. The engineering costs associated with this support limited the duration for which SoC vendors offered Android OS software support on a chipset," Google said.
"The crux of