[ROM][UNOFFICIAL][dumpling] LineageOS 15.1 [AOSP][8.1][16 FEB]

Search This thread

kylothow

Senior Member
Jan 3, 2014
1,011
1,727
Brescia
http%3A%2F%2Fi.imgur.com%2F2okPze5.png

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:
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).
Sources:
 
Last edited:

kylothow

Senior Member
Jan 3, 2014
1,011
1,727
Brescia
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.
 
Last edited:

kylothow

Senior Member
Jan 3, 2014
1,011
1,727
Brescia
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?

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.
 
  • Like
Reactions: ps000000

bucefalo.mso

Member
Jul 16, 2014
34
8
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
 

OhioYJ

Senior Member
Feb 25, 2011
1,463
731
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.
 
  • Like
Reactions: Schrotty35

Kookitza

Senior Member
May 21, 2010
1,008
506
Holon
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?! :eek:
 
Last edited:

BitOBSessiOn

Senior Member
Feb 12, 2015
1,736
3,127
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?! :eek:

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.
 
Last edited:

Kookitza

Senior Member
May 21, 2010
1,008
506
Holon
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.
This is something that we can change on build.prop or we should wait for the dev?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 74
    http%3A%2F%2Fi.imgur.com%2F2okPze5.png

    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:
    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).
    Sources:
    37
    Is Amartinz going to be the official lineage OS maintainer?

    Yes, at least one of them.
    My 5T will be delivered straight after christmas days.
    We're working on 5 and 5T since those are not much different.
    27
    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.
    18
    Good news fresh from Lineage's GitHub: a wild dumpling tree has been created.
    Looks like things will become even more exciting soon :)

    https://github.com/LineageOS/android_device_oneplus_dumpling
    15
    Didactic Break N°1

    I want to add a didactic note, not really related to this particular build, but definitely interesting and useful (especially if you are interested to Treble).

    Yesterday morning I have noticed an interesting commit in the Lineage Gerrit. I'm talking about commit 205186. The first line of the commit message is self-explanatory: "msm8998: unlock vendor partition".
    Yup, that's what you think: it enables the vendor partition, the very same partition Treble-enabled devices use to store the proprietary drivers and framework.
    So I thought: "Well, that's kinda cool. Why not trying it out?". I've taken over codeworkx's work and I have rebased the patches over the AnyKernel2 backend (after removing all the stuff that wasn't useful for the patch and rewriting part of the script to take advantage of the functions the AnyKernel2 backend provides).
    Eventually I came up with a working standalone flashable zip of the patch.
    Basically after reworking the code I jumped to TWRP, flashed the zip and observed it doing its job. Spoilers on the ending: it worked perfectly and now my OnePlus 5T has a suitable vendor partition.

    # # #
    "How does this magic work? Wasn't it risky and could brick the devices?".
    - No, the risk is close to zero and there's no magic. Both OnePlus 5 and 5T already have a partition (yup, no repartitioning to do) located at /dev/block/sdf6, named last_parti and with a descriptor set to 0000 (the partition is hidden to the userspace). With a size of 1.5GB it looks perfectly suitable for the purpose.
    "So, what does this script do?"
    - It changes the partition descriptor to 8300 (Linux filesystem) and the name to vendor. Voilà. The partition is not hidden anymore and is detectable by name as vendor.
    "Can we run Treble ROMs?"
    - No, the partition is empty.
    "Does this mean OnePlus will support Treble in the future?"
    - Nothing is certain, but OnePlus already publicly refused to support Treble for any of its current devices, so I wouldn't hold my breath.
    "So.... why enabling it?"
    - This could eventually allow developers to develop a community solution for the lack of official Treble support. On other devices this already happened with pretty good results.
    "Can you give us any more information? Is anyone already at work?"
    - Nope, I just found this out and wanted to share my findings.
    # # #

    EDIT: added screenshots of the first test of the script (yeah, the output text is kinda orrible and not very useful but quite explanatory anyway).
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone