But Asus didn't let that stop it from releasing an Android Oreo - based update for the Asus Zenfone 4 that brings Project Treble support without
a separate vendor partition.
Since these devices already ship without
a separate vendor partition, it means that they would have to re-partition existing devices to include space for the vendor partition.
Project Treble compatibility requires that a device ship with
a separate vendor partition in order to store the vendor HALs.
Not exact matches
As I explained in my previous article, the gist of how Project Treble works is that all of the
vendor - specific code is
separated from the Android OS framework into its own
separate partition.
At the basic level, Treble
separates the
vendor implementation from the Android OS framework using a new
partition layout.
It involves
separating vendor Hardware Abstraction Layers (HALs) from the Android Framework into a new vendor partition, and having the HALs communicate with the Android Framework through a new Vendor Interface via what's called the HAL Interface Definition Language (
vendor Hardware Abstraction Layers (HALs) from the Android Framework into a new
vendor partition, and having the HALs communicate with the Android Framework through a new Vendor Interface via what's called the HAL Interface Definition Language (
vendor partition, and having the HALs communicate with the Android Framework through a new
Vendor Interface via what's called the HAL Interface Definition Language (
Vendor Interface via what's called the HAL Interface Definition Language (HIDL).
Specifically, the requirement to have a
separate partition for the
vendor implementation can not be done through a simple OTA update.