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:

Labels:

Comments

Post a Comment

Popular posts from this blog

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi
Post a Comment
Read more

Android Beginners Guide

                                                                                                               Android Operation System: Android is an operating system based on Linux with a Java programming interface. It provides tools, e.g. a compiler, debugger and a device emulator as well as its own Java Virtual machine (Dalvik Virtual Machine - DVM). Android is created by the Open Handset Alliance which is lead by Google. Android uses a special virtual machine, e.g. the Dalvik Virtual Machine. Dalvik uses special bytecode. Therefore you cannot run standard Java bytecode on Android. Android provides a tool "dx" which allows to convert Java Class files into "dex" (Dalvik Executable) files. Android applications are packed into an .apk (Android Package) file by the program "aapt" (Android Asset Packaging Tool) To simplify development Google provides the Android Development Tools (ADT) for Eclipse. The ADT performs automatically the conversion f
2 comments
Read more

Android Pi migration(28 API support)

I am here to give some inputs on android PI migration. .  Apps must target at least API level 28 to ensure it is built on the latest APIs optimized for security and performance . From August 2019, new apps must target at least Android 9.0 (API level 28) . The objective here is to make sure that your existing app works as-is on Android 9. Because some platform changes might affect the way your app behaves, some adjustments might be necessary, but you do not need to use new APIs or change your targetSdkVersion. Android Service Problem On Oreo, startService() will throw IllegalStateException. This can be fixed by changing it to startForegroundService(). but it also stops the service immediately if you don’t bind to the Notification with Service.startForeground() within 5 seconds. For other background service we decided to use the WorkManager . Implementation: Since we have minSdkVersion 19, We migrated to workmanger for scheduled tasks and we still use JobIntentSer
1 comment
Read more