As for the vendor interface, that’d be the driving school where the driver learned the standard way to operate the steering wheel and brakes. Continuing with this analogy, the driver of the car is the operating system since they send the commands to the HALs (by turning the wheel or pressing the brakes) to make the car move. The steering wheel and brakes are HALs in this analogy, since they control the movement of the car without the driver needing to understand how the car’s hardware works. Think of a car and its basic components, like the steering wheel and brakes. If that doesn’t make sense to you, here’s an analogy that might clear things up. Thus, by reducing the system image down to the OS framework, moving all HALs to a new vendor partition, standardizing the communication between the OS and HALs, and mandating new compliance tests, Project Treble succeeded in rearchitecting Android to make it more modular and updatable. In order for the OS framework to communicate with HALs, Google worked with its OEM and silicon vendor partners to define a vendor interface (VINTF) with standardized code written in an interface definition language like HIDL (pre-Android 10) or AIDL (post-Android 10). This vendor-specific software code consists mostly of hardware abstraction layers (HALs) that interact with the device’s specific hardware components. How exactly did Project Treble change the way Android is architected? Put simply, it began the process of separating vendor-specific software code from the Android OS framework contained within the system image. How Google rearchitected Android with Project Treble It’s been nearly four years since the first proof-of-concept, so for this week’s Android Dessert Bites, I’ll provide a broad overview of Project Treble and showcase some of the work on GSIs done by community developers. However, members of the Android community had another idea in mind for the GSI: to use it as a base for developing custom ROMs that can boot on any Treble-supporting hardware. The GSI contains the unmodified OS framework from AOSP and is intended to be used to speed up compatibility testing of hardware components during the bring up of a new OS version. With the architecture introduced by Project Treble in 2018, which Google frequently cites as the reason new OS versions are being adopted more quickly, the system image on Android devices can be genericized, resulting in what’s called a generic system image (GSI). Android 11 has the fastest adoption rate of any OS version, according to this chart provided by Google.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |