Skip to main content

Treble : Manufacturers to update devices to a new version of Android very easily

I am happy that google has introduces new framework where manufacturer can update OS very easily & test with new OS.

> The Android 8.0 release includes Project Treble.

> Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android.

> Treble separates the vendor implementation (device-specific, lower-level software written by silicon manufacturers) from the Android OS framework via a new vendor interface.

> 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


For details on the new Treble architecture, see the following sections:

  • HAL Types. Describes binderized, passthrough, Same-Process (SP), and legacy HALs.
  • HIDL (General). Contains general information about the HAL interface definition language (HIDL, pronounced "hide-l"), which is an interface description language (IDL) to specify the interface between a HAL and its users.
  • HIDL (C++). Contains details for creating C++ implementations of HIDL interfaces.
  • HIDL (Java). Contains details about the Java frontend for HIDL interfaces.
  • ConfigStore HAL. Describes the ConfigStore HAL, which provides a set of APIs for accessing read-only configuration items used to configure the Android framework.
  • Device Tree Overlays. Provides details on using device tree overlays (DTOs) in Android.
  • Vendor Native Development Kit (VNDK). Describes the VNDK, which is a set of libraries exclusively for vendors to implement their HALs.
  • Vendor Interface Object (VINTF). VINTF objects aggregate relevant information about a device and make that information available through a queryable API.
  • SELinux for Android 8.0. Details SELinux changes and customizations.

Hopefully manufacturers provide the updates as early as possible.

References:

Comments

Popular posts from this blog

  Mastering Per-App Language Preferences: From Android 10 to Android 13+ One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper o...

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...