• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

elgab

Member
Feb 1, 2016
7
1
Is anyone else having issues with the Vulkan API? In 3Dmark, the "Sling Shot Extreme" test first crashed and now it says "Your device is not compatible". AIDA64 and other tools say the device doesn't have Vulkan support and in general only OpenGL seems to work.
Hi, is Vulkan working in the ROM? i'm on Lineage 16 and planning to jump to 18.1
 

bar-aka

Senior Member
Nov 25, 2012
132
37
Just flashed LOS 18.1 on my OP3. All working fine, but I'm wondering is there a way to disable the capacitive buttons (recent/back) when in full screen mode e.g. gaming?
Oxygen OS has something like this (see attached)
 

Attachments

  • 2021-06-11 12_56_36-Screenshot.png
    2021-06-11 12_56_36-Screenshot.png
    94.2 KB · Views: 111

BillGoss

Senior Member
Sep 2, 2010
4,630
4,046
Sydney
OnePlus 3T
OnePlus 8T

CodeFinder

Member
Jan 4, 2016
43
44
Also installed this ROM on my old OnePlus 3T (according to https://wiki.lineageos.org/devices/oneplus3/install , flashed "lineage-18.1-20210621-nightly-oneplus3-signed.zip" and "twrp-3.5.2_9-0-oneplus3.img" via "adb sideload $FILE") and works REALLY well. No FCs or other issues observed so far (although not tested thoroughly). WiFi, Bluetooth (Audio streaming), NFC, calls, GPS, AOD/inactivity display, fast charging, double tap to wake/sleep, camera light, screen rotate, auto-brightness, Widevine L3 (as on OOS?), SafetyNet check, Android TV streaming (chromecast), ...all perfect. And really smooth, Google Maps is even smoother than on OOS 9.0.6. Used MindTheGApps.

Note, however, when relocking the bootloader (command: "fastboot oem lock"), I had to factory reset first (?) and (more importantly), I had to click "NO" in the confirmation to lock it (seems incorrectly labeled by OnePlus :-D , see also https://forums.oneplus.com/threads/not-able-to-lock-oem.1020173/#post-20587482 ).

Nice work! :) Highly recommended ROM! Will report here if I experience any bugs or issues. And also if there's something I found working. ;-)

Links for reference:
- adb and fastboot (Linux): https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- twrp-3.5.2_9-0-oneplus3.img: https://eu.dl.twrp.me/oneplus3/twrp-3.5.2_9-0-oneplus3.img.html
- lineage-18.1-20210621-nightly-oneplus3-signed.zip: https://mirrorbits.lineageos.org/fu...age-18.1-20210621-nightly-oneplus3-signed.zip
- MindTheGapps-11.0.0-arm64-20210412_124247.zip: https://androidfilehost.com/?fid=2188818919693781601

Edit: one question ...does anyone know if, given the nightly install and a re-locked bootloader, I can simply install or even automatically update LOS (without manually going through TWRP) if new nightly builds becomes available? And how does this relates to an encrypted phone, i.e., can it also be updated w/o issues?

Edit2: okay, I just upgraded to newest nighly (28-06-2021) and all went smooth and fine. Used the buildin LOS updater and all was done automatically - cool! Additionally, everything is working fine so far (especially GPS)! :)

PS: my phone is currently unencrypted (the default after install?).
 
Last edited:

150208

Senior Member
Dec 19, 2013
473
250
{Mod edit: Quoted post deleted}

Start a new thread on Q/A section, please.
I'd love to read that too, but this is LOS thread, not battery thread.
 
Last edited by a moderator:

ranjeet choudhary

Senior Member
Apr 16, 2015
82
40
Any suggestions on how to fix the bluetooth audio not playing on some device. Similar to what others have mentioned not able to play anything on VW polo android auto. Bluetooth connects but doesn't play. It is working fine with other ROMs
 

real_uplink

New member
Jun 8, 2018
2
0
Chemnitz
Tried to upgrade from LOS 17.1 to 18.1 without factory reset. --> Bootloop/endless boot time

My Setup:
- Old System: lineage-17.1-20200425-nightly-oneplus3-signed
- New System: lineage-18.1-20210621-nightly-oneplus3-signed
- Firmware: OnePlus3T_9.0.6-(20-11-19)-FIRMWARE


I use(d) MagisK v23 and already tried the following:
1. Flash new lineage zip and flash MagisK.zip directly afterwards without reboot, then rebooted
2. Flash new lineage, reboot -> Bootloop/endless boot
3. Remove MagisK on LOS 17.1 and then flash new lineage and reboot

Upgrade tried via:
- Lineage Recovery lineage-18.1-20210621-recovery-oneplus3 with sideload
- TWRP-3.5.2_9-0-oneplus3 with zip from both internal storage and sideload

I also tried to perform a clean install, successful boot and then restore /data via nandroid but I end in the same behavior as with the direct upgrade (bootloop to recovery/endless boot time)

None of the variants worked for me.

Failure symptomatic:
- I always be able to surpass the device encryption password prompt
- Then it shows a long time the moving LOS logo (never stuck)
- Then it:
-> either reboots into recovery
-> or it does endlessly show the moving LOS logo. I wait at least 15 minutes on each of the above tests and also tried for more than 1 hour in some tests

Restore of old system:
- Somehow even a nandroid restore back to 17.1 behaves a little weird:
- After nandroid restore of /boot /data /system /system-image the system is not able to boot.
- I have to:
-> restore /boot /data /system /system-image from nandroid backup
-> zip-install the lineage-17.1-20200425-nightly-oneplus3-signed in order to successfully boot
-> delete /data/system/locksettings.db in order to bypass the lockscreen which otherwise does not recognize my correct password anymore.
=> Then the old system (lineage-17.1-20200425-nightly-oneplus3-signed) is fully working with active MagisK and all settings, apps and app-settings being restored.

I tried this procedure also with lineage-18.1-20210621-nightly-oneplus3-signed without success -> Bootloop/endless boot time

Exclude defective nandroid Backup:
I checked for a corrupt nandroid by performing two other nandroid backups on different days and trying to restore them.

Recent upgrades:
I already successfully upgraded from LOS16 to 17.1. (Could this be a problem because the partition usage/formatting/... changed?)


Is there any possibility to upgrade with my data?
Is there a possibility to debug the boot in more detail?
Would be nice if you can give me a hint.
 
Last edited:

raulaguilare

Member
Feb 3, 2014
6
2
Tried to upgrade from LOS 17.1 to 18.1 without factory reset. --> Bootloop/endless boot time

My Setup:
- Old System: lineage-17.1-20200425-nightly-oneplus3-signed
- New System: lineage-18.1-20210621-nightly-oneplus3-signed
- Firmware: OnePlus3T_9.0.6-(20-11-19)-FIRMWARE


I use(d) MagisK v23 and already tried the following:
1. Flash new lineage zip and flash MagisK.zip directly afterwards without reboot, then rebooted
2. Flash new lineage, reboot -> Bootloop/endless boot
3. Remove MagisK on LOS 17.1 and then flash new lineage and reboot

Upgrade tried via:
- Lineage Recovery lineage-18.1-20210621-recovery-oneplus3 with sideload
- TWRP-3.5.2_9-0-oneplus3 with zip from both internal storage and sideload

I also tried to perform a clean install, successful boot and then restore /data via nandroid but I end in the same behavior as with the direct upgrade (bootloop to recovery/endless boot time)

None of the variants worked for me.

Failure symptomatic:
- I always be able to surpass the device encryption password prompt
- Then it shows a long time the moving LOS logo (never stuck)
- Then it:
-> either reboots into recovery
-> or it does endlessly show the moving LOS logo. I wait at least 15 minutes on each of the above tests and also tried for more than 1 hour in some tests

Restore of old system:
- Somehow even a nandroid restore back to 17.1 behaves a little weird:
- After nandroid restore of /boot /data /system /system-image the system is not able to boot.
- I have to:
-> restore /boot /data /system /system-image from nandroid backup
-> zip-install the lineage-17.1-20200425-nightly-oneplus3-signed in order to successfully boot
-> delete /data/system/locksettings.db in order to bypass the lockscreen which otherwise does not recognize my correct password anymore.
=> Then the old system (lineage-17.1-20200425-nightly-oneplus3-signed) is fully working with active MagisK and all settings, apps and app-settings being restored.

I tried this procedure also with lineage-18.1-20210621-nightly-oneplus3-signed without success -> Bootloop/endless boot time

Exclude defective nandroid Backup:
I checked for a corrupt nandroid by performing two other nandroid backups on different days and trying to restore them.

Recent upgrades:
I already successfully upgraded from LOS16 to 17.1. (Could this be a problem because the partition usage/formatting/... changed?)


Is there any possibility to upgrade with my data?
Is there a possibility to debug the boot in more detail?
Would be nice if you can give me a hint.
Always clean flash!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Nobody else seems to have this problem, so let's check the framework.

    Have you installed the latest firmware?
    Have you installed the latest TWRP?
    Is your Bootloader locked or unlocked?
    Is your device encrypted?
    Which filesystem are your partitions formatted in?
    Which GApps package did you install?
    Did you do a clean install?
    Do you have Magisk installed? If yes, which addons?
    Do you have Exposed installed? Or something like this?
    Which Apps do you have installed?
    Which Modifications have you done?
    Same here, weekly kernel panic on my 3T.
    I have the latest OOS firmware.
    I use LOS recovery.
    Bootloader unlocked because of Magisk (locking it used to cause bootloop).
    Device is encrypted.
    Filesystems: i have no clue. Whatever LOS recovery formats the partitions it uses to, plus whatever the factory used on the partitions that LOS doesn't format.
    Gapps: MindTheGapps, whateverer version was available when LOS 18.1 came out.
    Clean install. The issue started after the 2nd or 3rd OTA update (I only update when new security updates come out).
    I have Magisk installed. Only have Google Phone Recorder addon installed.
    No Exposed or anything like that.
    No modifications done (I don't know if using Nova launcher prime counts as a modification. I've been using it for years without any issues).
    The only thing different from when I used LOS 17.1 is I've ditched Chrome and started using Brave browser with Bitwarden.

    Could it be battery-related? I still have the original one; I still get around 4.5 hrs of SOT, but have to charge daily.

    I'll do a complete factory reset to the latest OOS (to get the original gps.conf file so that I can compare it with the one from LOS), maybe even with the unbrick tool, and do a complete clean install of LOS 18.1 when I have some time (hopefully next week)
    1
    I updated to the 20210726-nightly-oneplus3 build yesterday and have been having touchscreen responsiveness issues since where some presses or swipes aren't registered at all.
    This has made typing and scrolling news articles a bit frustrating. Beware! :p
    1
    For those that are curious, or being forced to switch devices because of the 3G sunset, VoLTE is working fine for me on T-Mobile US with the latest LineageOS and I did not need to do any extra configuration. Beforehand I had installed the latest OxygenOS available for this phone (9.0.6).
  • 42
    LineageOS is a free, community-built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
    Code:
    #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 18.1 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 an 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

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

    Installation:
    First time flashing LineageOS 18.1 on your device, or coming from another ROM?
    1. Download the zip(s)
    2. Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
    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:

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

    Changelog and Download:
    Known issues:​
    • This build is HIGHLY EXPERIMENTAL and NOT WELL TESTED.
    • Wifi display not work, don't ever attempt to use it or the system will crash.
    • VoLTE is not tested and I don't know if it ever works, please give feedback if you're able to verify.
    • Fixed the sensor_SMD wakelock
    • Fixed ringtone when bluetooth headset connected
    13
    Regarding the sensor_SMD wake lock:
    Generally, the rom can go for long periods without this wake lock showing up:
    View attachment 5215977View attachment 5215981
    But the wake lock can start at random times:
    View attachment 5215983View attachment 5215985
    And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.

    However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
    View attachment 5215983View attachment 5216001

    Fortunately, a reboot gets rid of the wake lock.
    Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
    13
    I've been running this rom for a week now. I've not had any problems with it - no system reboots, no system FCs, no performance lags or stutters (though I don't play games).
    Battery life is not quite as good as 17.1, but I still only charge the phone once a day. Of course this is with the fix for the sensor_SMD wake lock from https://forum.xda-developers.com/t/...s-18-1-for-oneplus-3-3t.4230665/post-84465491
    The only other minor annoyance than the issues I mentioned in https://forum.xda-developers.com/t/...s-18-1-for-oneplus-3-3t.4230665/post-84456483 is that there's no "Mark as read" option on SMS notifications.

    Great work @dianlujitao! This is now my daily driver. I look forward it becoming an official version.
    12
    Regarding the sensor_SMD wake lock:
    Generally, the rom can go for long periods without this wake lock showing up:
    Screenshot_20210210-044409_BBS.pngScreenshot_20210210-044354_BBS.png
    But the wake lock can start at random times:
    Screenshot_20210209-174523_BBS.pngScreenshot_20210209-174531_BBS.png
    And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.

    However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
    Screenshot_20210209-174523_BBS.pngScreenshot_20210209-202825_BBS.png

    Fortunately, a reboot gets rid of the wake lock.
    12
    I just built LOS 18.1 (see attached roomservice.xml for OP3/3T and OP5T) for testing (with the March security update - see attached screenshot).
    I successfully flashed LOS 18.1 on official LOS 17.1 via a dirty flash (wipe system/caches + flash build & MindTheGapps-11.0.0-arm64-20210220_140101).
    Note that I didn't flash Magisk and that safetynet passed (see attached screenshot - my BL is locked)
    Download :
    - Build 0312 : https://androidfilehost.com/?fid=2188818919693753932
    - MindTheGapp : https://wiki.lineageos.org/gapps.html

    Thanks for the great job @dianlujitao !
    DOWNLOAD:
    * Build type : unofficial ... daily or weekly ... it depends on LOS gerrit
    * Synced LineageOS sources
    * All credit goes to LOS Team and @dianlujitao
    ==> https://androidfilehost.com/?w=files&flid=323965&sort_by=date&sort_dir=DESC