A Revolution in Custom ROMs: How Project Treble makes Porting Android Oreo a 1 Day Job

[ad_1]

A Revolution in Custom ROMs: How Project Treble makes Porting Android Oreo a 1 Day Job

"We may soon be seeing a revolution in custom ROM development thanks to the initial development efforts on this front by XDA Senior Member phhusson. After 20 hours of work researching, developing, and debugging with me, phhusson created a system image that can be booted on multiple devices from different manufacturers and with completely different SoCs. For example, the same system image that I booted on my own Huawei Mate 9 also boots on the Honor 8 Pro, Honor 9, Sony Xperia XZ1 Compact, and the Essential Phone. That’s 3 different OEMs (Huawei/Honor, Sony, and Essential) and 2 different SoCs (HiSilicon Kirin 960 and Qualcomm Snapdragon 835) where this single system image can successfully boot."

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. In order to encourage more development on this front, we’ve opened up a new forum dedicated to Project Treble enabled devices. The forum is geared towards developers at this moment.

Project Treble is most commonly described as an attempt by Google to modularize the Android OS framework to separate vendor specific code. All devices that launch with Android 8.0 Oreo or above must fully support Project Treble. All devices that upgrade to Android 8.0 Oreo are not required to fully support Project Treble. One of the requirements in the VTS is that a Treble-enabled device must be able to boot a raw, generic AOSP build. Because of this requirement, OEMs have to ship devices that can boot AOSP without any issues.

Google wasn’t kidding when they said that Project Treble was perhaps one of the biggest changes ever to the way Android works. We can see for ourselves, right here and now, just how much of an impact it can have. Treble might be the push the development community needs to revitalize the custom ROM scene.

See http://bit.ly/2jXhh0D

cbc895dd e882 45c4 80e6 16860dd88fe9

[ad_2]

Source link