Project Treble is pretty great and allows for a Generic System Image (GSI) to boot on supported devices While previously only devices from the likes of Huawei and Essential were supported, as more and more devices launch with Android Oreo they too will have to support it. Xiaomi, a company whose devices have seen huge success in the developer community, updated the Redmi Note 5 Pro to Android 8.1 Oreo, complete with Project Treble support. There's a huge amount of interest in developing GSIs as more and more devices are updated to support them. Thanks to XDA Recognised Developer phhusson, there are now generic LineageOS 15.1 and Resurrection Remix ROMs available for all supported devices.
phhusson also created the first Project Treble AOSP ROM that booted on the Huawei Mate 9, and ever since then has been continuously improving his release of AOSP. He has improved its compatibility across devices tenfold, with it even booting on an obscure MediaTek device which has no kernel sources available. His work has been phenomenal and is a testament to the talent of the developers here on the XDA forums.
As for bugs, really everything should work. Hardware keys that aren't natively supported by AOSP won't work. In a future Project Treble-supported OnePlus device, the alert slider likely won't work in a generic build of Android. Anyone getting a Project Treble supported device will be able to enjoy custom ROMs from the get-go. So long as the bootloader can be unlocked. Recent devices like the Samsung Galaxy S9/S9+ and upcoming devices like those announced by Sony at MWC 2018 can already boot the most popular custom ROMs around. It's not just limited to these devices either. Anything launching with Android Oreo will now be able to boot LineageOS 15.1 or Resurrection Remix if the bootloader can be unlocked. If you're interested then check out the download links below and give them a shot!
Download LineageOS 15.1 Project Treble Enabled
Download Resurrection Remix Project Treble Enabled
from xda-developers https://ift.tt/2pE2Ai2
via IFTTT
No comments:
Post a Comment