[ROM][Official][Nightly] LineageOS 16.0 for OnePlus 3/3T

Search This thread
Nov 8, 2010

Fpr the Eleven widget issue: did you try to disable battery optimization for eleven? Since I've disabled it, I can't reproduce the issue any more - even after the eleven notification has gone.

can confirm, on a quick testing this seems to be the solution, will test over the next days and will inform you if the issue still appears under different circumstances.

thank you very much again


Senior Member
Jul 19, 2017
phone shuts down and empty over night

I'm using the last official build LOS 16.1 from april.
Since 3 days (or nights) I've a strange issue:
I set up an alarm clock for the morning, and switch the phone to airplane mode.
In the morning, the phone is empty. Phone just buzzers, as it tries to boot for the clock.. Pluging in the cable: "Battery is empty, please charge".
It's really total empty. And it's not because of a drain from the battery, I attached the battery statistic. It's just like a "hard cut" and baam: phone off & empty
The battery level in the evening wasn't that low: 40%, 25% and 75%

I din't change anything on the software - only play store updates, as they're installed automatically.
Maybe a g-services update could cause it?

I've no clue why it's happening, does anybody else have this issue?

Edit: I also described it (in German) in the OP forum: https://forums.oneplus.com/threads/oneplus-one-schaltet-sich-von-alleine-aus.283295/#post-21633109
Another user also reported that problem this morning...
It seems it only happens with an activated clock?

EDIT: I switched to LOS 17.1 and it disappeared. Cannot say what was the reason for this and I hope it'll never appear again...


  • Screenshot_20200521-083425_Einstellungen.png
    132 KB · Views: 242
Last edited:


Senior Member
Dec 28, 2011
Hi - is there anywhere I can still access these builds? I'm running 20200325 but want to know if there are any more recent nightlies on 16.0.

As you can see in https://github.com/LineageOS/hudson/blob/master/lineage-build-targets 16.0 isn't build anymore for oneplus3.

You may want to have a look at
https://forum.xda-developers.com/on...m-hardened-lineageos-16-0-oneplus-3t-t4034869 (by @MSe1969 ) or
  • Like
Reactions: thomasnsr


New member
Dec 18, 2020

  • It seems I resolved my screen doesn't switch on, it was my quite crazy guess but it might be right:)Well, what I did is to swap qcom,mdss_dsi_samsung_s6e3fa5_1080p_cmd and qcom,mdss_dsi_samsung_s6e3fa3_1080p_cmd nodes in device tree. There is kernel parameter that passed from bootloader that is used by kernel module to choose right panel model node thus I did nearly the same as changing that parameter (I won't change bootloader, of course). And it worked. It very likely means one of:
    • My cheapest display replacement is made from initially OnePlus 3 display somehow adapted to be in 3T assembly. Or whatever crazy engineer mind could produce:) It could be some other models not fully functional or not passed QA or who knows what
    • There are still some differences in commands LOS issues and what stock outputs and when applied to this semi compatible hardware it creates such results
Sorry to pull back this old issue, but I have this problem with a 3T and LOS18.1 (screen sometimes doesn't switch on when pressing power button).
Can you explain in more details what you did to solve it so it can be adapted to los18.1 ?
Do you have to build LOS from source to solve it?
Thanks a lot

Top Liked Posts

  • There are no posts matching your filters.
  • 137
    LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.​
    #include <std_disclaimer.h>
     * Your warranty is now void.
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
    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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.

    Important information:
    This thread is for LineageOS 16.0 builds for OnePlus 3/3T. The following will not be supported here:
    • Custom kernels
    • Mods
    • Xposed

    We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
    • Flashed a custom kernel
    • Installed or did mods from untrusted sources
    • Modified system files

    • You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.

    First time flashing LineageOS 16.0 on your device, or coming from another ROM?
    1. Download the zip(s)
    2. Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
    3. Perform a nandroid backup of your current ROM (Optional)
    4. Wipe data/factory reset
    5. Flash LineageOS
    6. Optional: Install the Google Apps addon package
    7. Reboot

    Source code:

    • LineageOS Team & Contributors
    • Code Aurora Forum
    • ......


    XDA:DevDB Information
    LineageOS, ROM for the OnePlus 3

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.x

    Version Information
    Status: Beta

    Created 2018-11-13
    Last Updated 2019-08-12


    • 2018.11.13:
    • Initial release

    • Sync latest source
    • Fixed directly reboot to recovery when attempting to enter power on password when secure boot enabled
    • Downgraded kernel to LA.UM.7.5.r1-02500-8x96.0 due to CAF stability regression, but there's still a race condition which could cause random kernel panic, especially when attempting to wake up the device, I'm still debugging on this.
    • Improved GPS performance
    • Minor bug fixes

    • Sync latest source
    • Kernel baseline updated to LA.UM.7.6.r1-03600-89xx.0
    • Thanks to a clue provided by @markakash , the "random kernel panic on wake up" issue seems to be fixed now. The ROM is probably stable enough for daily use, so I call it "beta" instead of "alpha" now. Please report if you still have the issue.
    • Minor bug fixes

    • Sync latest source
    • IMS experiments, VoLTE is confirmed working, VoWiFi is untested
    • Battery life optimization
    • Fix fingerprint sensor not respond on first boot and after user switched
    • Minor bug fixes

    • Sync latest source
    • SELinux enforcing for now, let me know if there're any regressions
    • Minor bug fixes

    • Sync latest source
    • Fix some suspend issue
    • Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0
    • Minor bug fixes

    • Sync latest source
    • Slider key fix by @nvertigo67
    • App launch boost & touch boost, hope it helps reduce lagging

    • Sync latest source
    • Kernel baseline updated to LA.UM.7.5.r1-04000-8x96.0
    • WiFi display support
    • Bug fixes & improvements


    • Sync latest source
    • Add support for always-on-display
    • Minor bug fixes

    • Sync latest source
    • Fix touchscreen when gesture disabled
    • Fix whatsapp and CamScanner camera issue? Not sure, need feedback
    • Minor bug fixes

    • Sync latest source
    • Update kernel to LA.UM.7.5.r1-04100-8x96.0
    • Livedisplay & touchscreen gestures internal API migration
    • Allow disabling new USB gadgets when the device is locked
    • Minor bug fixes

    • Sync latest source
    • Fix weird color after boot? Need your confirmation
    • Performance optimizations
    • New offmode charging animation
    • Minor bug fixes
    • Note that some features/bugfixes will NOT be included in the upcoming official builds, be aware before switching from unofficial to official.

    The 0302 official build failed to boot due to a technical issue with signing, it should be fixed with the upcoming build. Sorry for any inconvenience that may have been caused to you.
    A warning on leaked Pie builds

    As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.

    After several experiments I finally figured out the cause:

    If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.

    I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
    Good news (maybe), after communicating with oneplus stuff they promised fw upgrading with unlocked bl will be fixed in future builds.