The list of devices receiving an unofficial upgrade to Android Oreo is growing daily, and next up on our list to receive the awaited update are the OnePlus 3 and OnePlus 3T. These two devices are highly popular on our forums due to their price at launch and their friendliness to modifications, so it's no surprise to see them be part of the small group of devices to receive an unofficial update to Android Oreo.
The Android Oreo build is an unofficial, early LineageOS 15 alpha port, and as a result, there are many things broken. The camera doesn't work, which isn't too surprising. Camera blobs will need to be "shimmed" to work on Android Oreo. To briefly explain, shimming is the act of translating the device blobs from one previous Android version to another. Certain functions from a camera blob on Android Nougat may not work on Android Oreo, as Oreo changed the data it's looking for from the camera. The shim will take this data that Android Oreo can't read and translate it so that it can. If a camera blob from an Android Nougat device is run on Android Oreo, any changes to Android Oreo and how it uses the camera might not work as it is receiving data for an old version of Android. The shim will take this data and translate it for Android Oreo so that it works fine. This is an intensive process requiring a lot of work, and because there is no Android Oreo release for the OnePlus 3/T, it may be a while before we see a working camera on any device that's been brought up to Android Oreo unofficially.
The alert slider also doesn't work (again, a case of blobs), Bluetooth, and screen off gestures. Otherwise, it's a pretty solid first release. The things which don't work are the ones you would expect not to work for a first release, so there's nothing crazy that's been left out so far. Obviously, the camera is essential, but for a first port, we understand why it isn't there. You can check it out below, and install it if you wish!
Get LineageOS 15 (Android Oreo) for the OnePlus 3/3T
from xda-developers http://ift.tt/2w8zLeM
via IFTTT
No comments:
Post a Comment