Following topics gives an overview and basic Understanding on Android Project Treble
Topics:
1) Introduction
2) Why Treble introduced?
3) Typical Android OS release steps
4) Introducing VINTF layer
5) Before and After Treble Project Testing Treble
6) Summary
Introduction:
Basically it is android OS framework level change to enable easiest OS update for manufacturers. The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android.
Treble is for all new devices launching with Android 8.0 and beyond (the new architecture is already running on the Developer Preview for Pixel phones).
Treble is the one of the biggest changes introduced to Android Oreo, but one that consumers won’t even notice as it works primarily behind the scenes.
Why Treble introduced?
Following gives a pictorial representation of typical android OS release procedures.
1) New Android OS release
2) Silicon manufacture partner customize and add silicon specific codes.
3) Device makers customise the OS to achieve device specific GUI(EMUI, Samsung touchwiz).
4) Then device makers release the actual OS suite for each devices.
Typical Android steps OS release and introduction of project Treble:
In typical OS updates, silicon manufactures need to include their on code to support their hardware.
Then only the device makers can release the OS to costumers. This always be headache to device makers.
So the introduction of Treble to separate vendor implementation from HAL. Project Treble enables a modular base for Android software, to facilitate faster uptake of security updates and platform upgrade, by lowering engineering costs. Dividing software along lines of ownership, a well-defined interface (VINTF, HAL IDL) between the device-independent (Framework) and device-dependent part of the code (VINTF Implementation ), enforcement of the stipulated contract at the interface (VTS), a standardization of dependent libraries (VNDK), and a mechanism to update the platform and device specific code independently (OTA) are the core engineering changes that define Project Treble.
Introducing VINTF layer:
The Vendor Interface (VINTF) encapsulates a collection of versioned HAL interfaces, kernel interfaces exposed to the user space and other components that are segregated by ownership.
Before and After Treble Project:
n Android 7.x and earlier, no formal vendor interface exists so device makers must update large portions of the Android code to move a device to a newer version of Android:
With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers:
The below figure show the difference before and after the Treble project.
Topics:
1) Introduction
2) Why Treble introduced?
3) Typical Android OS release steps
4) Introducing VINTF layer
5) Before and After Treble Project Testing Treble
6) Summary
Introduction:
Basically it is android OS framework level change to enable easiest OS update for manufacturers. The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android.
Treble is for all new devices launching with Android 8.0 and beyond (the new architecture is already running on the Developer Preview for Pixel phones).
Treble is the one of the biggest changes introduced to Android Oreo, but one that consumers won’t even notice as it works primarily behind the scenes.
Why Treble introduced?
Following gives a pictorial representation of typical android OS release procedures.
1) New Android OS release
2) Silicon manufacture partner customize and add silicon specific codes.
3) Device makers customise the OS to achieve device specific GUI(EMUI, Samsung touchwiz).
4) Then device makers release the actual OS suite for each devices.
Typical Android steps OS release and introduction of project Treble:
In typical OS updates, silicon manufactures need to include their on code to support their hardware.
Then only the device makers can release the OS to costumers. This always be headache to device makers.
So the introduction of Treble to separate vendor implementation from HAL. Project Treble enables a modular base for Android software, to facilitate faster uptake of security updates and platform upgrade, by lowering engineering costs. Dividing software along lines of ownership, a well-defined interface (VINTF, HAL IDL) between the device-independent (Framework) and device-dependent part of the code (VINTF Implementation ), enforcement of the stipulated contract at the interface (VTS), a standardization of dependent libraries (VNDK), and a mechanism to update the platform and device specific code independently (OTA) are the core engineering changes that define Project Treble.
Introducing VINTF layer:
The Vendor Interface (VINTF) encapsulates a collection of versioned HAL interfaces, kernel interfaces exposed to the user space and other components that are segregated by ownership.
n Android 7.x and earlier, no formal vendor interface exists so device makers must update large portions of the Android code to move a device to a newer version of Android:
With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers:
The below figure show the difference before and after the Treble project.
Testing Treble:
To ensure forward compatibility of vendor implementations, the new vendor interface is validated by the Vendor Test Suite (VTS), which is analogous to the Compatibility Test Suite (CTS). You can use VTS to automate HAL and OS kernel testing in both pre-Treble and Treble environments.
The Android Vendor Test Suite (VTS) provides extensive new functionality for Android testing and promotes a test-driven development process. To help the Android development community interact with test data, Android O includes the following testing resources:
Systems Testing with VTS:- Describes how to use VTS to test an Android native system implementation, set up a testing environment, then test a patch using a VTS plan.
VTS Dashboard: - Web-based user interface for viewing VTS results. Includes details on:
Dashboard database: A scalable back-end to support the continuous integration dashboard.
Dashboard UI: A cohesive user interface that uses material design to effectively display information about test results, profiling, and coverage.
Dashboard setup: Instructions for setting up and configuring the VTS Dashboard.
Summary:
It’s possible that in the future, we could be seeing a single system image that can work on dozens of different Android smartphones, much like how Microsoft Windows can run on nearly any computer hardware.
Comments
Post a Comment