Project Treble: So Google wants to make Android updates faster

A persistent problem in the Android world remains the fragmentation.

android o project treble

Up to now, the developers in Mountain View had this sickening issue simmering side by side, while they were working on new features for the mobile operating system.

But apparently Google has finally found a solution: Project Treble promises to speed up the update process for all.

The update process for Android updates is a complex venture that hangs on more than just a bottleneck.

Any delays may occur in any of the necessary steps, and all subsequent work will be delayed.

As the following graphic shows, the chip producer must first adapt the update to its own hardware before the smartphone manufacturer can incorporate its own requirements.

This is inefficient, as Google has rightly recognized

The solution for this is basically quite straightforward: The step between manufacturer and provider can not influence Google, but probably between the chip designer and manufacturer.

With Project Treble, Android has been restructured and divided into modules at the lowest level. Instead of going through the above steps serially, some work can be carried out in parallel.

In the plain text, for example, LG no longer has to wait for Qualcomm to adjust the updated GOS version of AOSP for G6 .

Project Treble: “Vendor Interface” between manufacturer and chip designer

Sounds good. The whole thing Google uses with a so-called “vendor interface” as an interface between the Android framework module, which is interesting for the smartphone manufacturer, and the hardware module on which the respective chip producer must work.

The interface is almost a definition of all connections, which both modules have to each other.

After all, the manufacturer has to know only how he responds to the hardware, that is, the SoC, and can assume that it is able to respond to the predefined query.

In development, it is not necessarily the most recent commands the chip producer is working on as long as both parties adhere to the definitions.

If this is the case, there may be minor discrepancies, but they are usually repaired quickly – at a faster rate than when manufacturers and chip designers have to constantly wait for each other during (subsequent) changes or requests from the other.

The innovations around Project Treble are to come into force from Android O. To be precise, the current developer preview for the Google Pixel already has the “vendor interface.”

For those who are curious about Android O: The pixel smartphones will get the new version as usual months before models from other manufacturers. The prices have declined a little since the release.

For faster updates, companies should contribute to the AOSP

Project Treble: So Google wants to make Android updates faster

In the course of Project Treble, Google has also launched discussions with manufacturers and chip designers to get them to feed their individual features and adjustments into the Android Open Source Project (AOSP).

In this way, Google would work directly on the basis of numerous manufacturer and provider requirements, which would no longer have to be implemented again with every Android update.

For example, Sony and Qualcomm, according to Google, have already contributed dozens of features and hundreds of bug fixes to Android O, which are already on board in all subsequent releases and require no further work.

Further partners may be announced at Google I / O 2017 next week.