[ROM][UNOFFICIAL][dumpling] LineageOS 15.1 [AOSP][8.1][16 FEB] - OnePlus 5T ROMs, Kernels, Recoveries, & Other Dev

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's special about my build:
Sometimes I pick a few patches from the Lineage Gerrit before they are approved and merged into our trees.
The kernel is based on Lineage's one, but I have upstreamed with the latest patches from linux-stable, added a few things such as performance and battery tweaks, security and stability fixes, SafetyNet spoofing, additional kernel controls.... This kind of things
The device trees will also be improved overtime with various improvements from mixed sources (for example better presets, different HAL solutions and so on).
All the rest is kept as recommended in the maintainer's manifest (including the optional patches).
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
NFC
Camera
Video Playback
Audio (Record and Playback)
Fingerprint (with gestures)
Sensors
Flash
Notification LED
SELinux
SafetyNet
What's not working:
VoLTE calls are currently not working
With February security patches, TWRP is unable to decrypt data. The only way to be able to access it is removing any lockscreen PIN or password before entering recovery. This will be addressed by the TWRP guys soon.
Instructions:
Before instaling, make sure you are running the latest Open Beta 3 firmware.
If you are unencrypted take a full backup of all your data, because this ROM enforces encryption and so you will have to format your phone.
If you are encrypted and running an AOSP ROM (8.0 or newer) you're fine. If you come from OOS (both Nougat and Oreo) take a full backup of all your data as there's currently not way to change masterkey without formatting, sorry you should be able to go ahead and flash without formatting the internal storage, just make sure to remove any screen lock before switching ROM.
Download the latest build and GApps (both links are below).
Reboot to a custom recovery (latest unified codeworkx's build works perfectly and supports masterkey3 encryption).
If you are coming from any other ROM (even LineageOS 15.0 or 15.1) wiping /data is strongly recommended
Flash the latest build and GApps.
If you want root, flash it afterwards. If you plan to use Magisk, let the first boot happen and flash it later!
Reboot and enjoy :good:
Downloads:
ROM: lineage-15.1-20180216-UNOFFICIAL-kylothow-dumpling.zip
Google Apps: OpenGapps 8.1 (UNOFFICIAL)
Reporting bugs:
Grab a logcat right after the problem has occurred (please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
If it is a random reboot, grab /proc/last_kmsg (do not bother getting a logcat unless you can get it just before the reboot, a logcat after a reboot is useless).
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log (only applies to SELinux enforcing builds).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Credits:
This is a very important note: I am NOT the original developer of the device trees I'm using. Despite I do my best to fix bugs, improve security, stabilty and the performance of the ROM, it's not thanks to me that this is up and running now.
Please, be sure to thank and donate to the developers behind the device trees.
Huge thanks and credits to the NastyAndroidDevs team (https://github.com/NastyAndroidDevs).
@amartinz: https://github.com/amartinz
@codeworkx: https://github.com/codeworkx
@jrizzoli: https://github.com/jrizzoli
@jumoog: https://github.com/jumoog
Sources:
Device Trees (Reference): LineageOS
Kernel Tree (Reference): LineageOS
Manifest (Reference): NastyAndroidDevs
Device Trees (Custom): EvilDumplings
Kernel Tree (Custom): EvilDumplings
Manifest (Custom): EvilDumplings

---

Announcements/News:
20 December 2017:
The official LineageOS 15.1 dumpling and cheeseburger device trees are being uploaded on LineageOS' official GitHub account.
31 December 2017:
The fist working unofficial LineageOS 15.1 builds are going live
I made all my changes to NastyAndroidDevs' sources public. See the "Sources" section in the OP.

---

Thanks

---

kylothow said:
mine
Click to expand...
Click to collapse
Thnks for your hardwork and time. ?

---

Thanks:good:
downloading

---

Will you become the official maintainer for lineage OS for the oneplus 5t in the future?

---

Colday96 said:
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Click to expand...
Click to collapse
As I said in the OP, I'm not the developer behind the device trees, it's all thanks to the NastyAndroidDevs (with pretty known names, if you know CyanogenMod/Lineage) who are unifying the OnePlus 5 and 5T sources (with a common tree with most stuff); it's likely one or more of them will maintain the device.

---

good morning first of all thanks for putting the ROM looks very good pinta.queria know if facial recognition works to unlock with the face. Thanks and greetings
Enviado desde mi ONEPLUS A5010 mediante Tapatalk

---

Great! It's finally coming to op5t

---

This is great news. Will we get a LOS 14.1 build then too? LOS 15 is still missing a lot of features unfortunately. It would be nice to have LOS 14.1 until things like the privacy manager and such get incorporated into LOS 15.

---

Nice to see this here, even if some basic features are still missing.

---

YAAAAASSS

---

CommanderROR said:
Nice to see this here, even if some basic features are still missing.
Click to expand...
Click to collapse
The biggest one is camera.

---

I think I should be able to fix Camera and NFC soon...

---

Great!
Thanks for your hard work on this.
I'd love an aosp rom on the BEA5T!!

---

I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!

---

Kookitza said:
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Click to expand...
Click to collapse
That's because in device tree, ro.product.device property has been set as "dumpling", @kylothow , perhaps, it should be set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
EDIT:
In device tree, file BoardConfig.mk:
Code:
TARGET_OTA_ASSERT_DEVICE := [B]dumpling[/B]
...I get a little annoyed because not unified criteria about naming OP5T.

---

BitOBSessiOn said:
That's because in device tree, ro.product.device property has been set as "dumpling", perhaps, it should set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
Click to expand...
Click to collapse
This is something that we can change on build.prop or we should wait for the dev?

---

Kookitza said:
This is something that we can change on build.prop or we should wait for the dev?
Click to expand...
Click to collapse
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...

---

BitOBSessiOn said:
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
Click to expand...
Click to collapse
Can you upload the right file (Updater-script), cause i think i messed it :/