• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

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.

Upgrade with data is supported by both Vanilla Android and LineageOS:

I want to find the bug in the upgrade process.
 

highdiver_2000

Senior Member
Aug 10, 2012
1,538
341
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.
I am just upgraded my 3T. There isn't any Magisk.zip file. It is now an app that you sideload. Thereafter using the Manager you need do something (sign) the boot.img file.

You should always flash the ROM and the Gapps in 1 go and reboot ( Except may be for XiaoMi.). If all is stable then continues.
 

parkedraccoon

Senior Member
Sep 23, 2012
154
303
Dirty flashed all the way from LineageOS 15.1, went pretty smoothly!

One small issue I noticed - the Swap Capacitive buttons option doesn't properly persist after a reboot. Turn on, works fine. Reboot, goes back to default behavior, have to re-toggle the setting for it to work. This is on today's nightly, haven't tried any others.
 
  • Like
Reactions: Johannes1098

snyperius

Senior Member
Oct 4, 2018
54
25
I am just upgraded my 3T. There isn't any Magisk.zip file. It is now an app that you sideload. Thereafter using the Manager you need do something (sign) the boot.img file.

You should always flash the ROM and the Gapps in 1 go and reboot ( Except may be for XiaoMi.). If all is stable then continues.
You can change the extension of the Magisk apk to .zip and install it from the recovery just like in the good old days
 

giovanniro98

Senior Member
Mar 17, 2014
92
50
Anyone use Zoom here?
Zoom is unusable with Lineage 18.1, it freezes when I'm in a meeting and I have to force reboot the phone.
I tried to install 17.1 (I used that last year for zoom calls, no problem), but I discovered that also Los 17.1 has the same issue.
@dianlujitao could you look into it?
 

[email protected]

Senior Member
Jul 2, 2012
250
93
Hi everyone,

For many weeks, at least once a week, I'm getting a kernel panic. Every week, I flash the weekly drop.

The issue has finally climbed up my priority list that I've finally captured a console-ramoops.

What I don't know is whether my previous kernel panics are the same issue as the captured log. Now that I know how to capture the logs, if need be, I can snarf them.

Attached is the tail end of the file. I've preceded the panic with, I hope, sufficient context.

This is the head of the attached file:

Code:
[60587.858258] synaptics,s3320: all finger up
[60589.444620] synaptics,s3320: all finger up
[60590.073706] state: 0
[60590.102542] q6asm_callback: payload size of 8 is less than expected.
[60590.102875] q6asm_callback: payload size of 8 is less than expected.
[60590.108820] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x
0d1300c8 OPER:0x00000090
[60590.108870] pn544_dev_write : i2c_master_send returned -107
[60590.111090] q6asm_callback: payload size of 8 is less than expected.
[60590.111887] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[60590.148152] trigger:1(0:stop 1:start)
[60590.149040] q6asm_callback: payload size of 8 is less than expected.
[60590.229394] pn544_dev_ioctl bad ioctl 1074325765
[60590.229880] Call trace:
[60590.259469] Call trace:
[60590.264927] Call trace:
[60590.265113] ffs_function_bind_config: ffs_function_bind_config(): usb_add_function() fails (err:-12) for ffs
[60590.265117] android_bind_enabled_functions: android_bind_enabled_functions: ffs failed
[60590.265142] android_enable: android_enable: usb_add_config failed : err: -12
[60591.288038] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[60591.288168] Call trace:
[60591.288471] ffs_data_clear: ffs:0000000000000000 ffs->gadget= 0000000000000000, ffs->flags= 2
[60591.288498] ------------[ cut here ]------------
[60591.288515] Kernel BUG at ffffffc00077b628 [verbose debug info unavailable]
[60591.288532] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[60591.288557] CPU: 3 PID: 10785 Comm: adbd Tainted: G        W      3.18.124-lineageos-g04ff888 #1
[60591.288573] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
[60591.288592] task: ffffffc15d4ece00 ti: ffffffc011bb0000 task.ti: ffffffc011bb0000
[60591.288612] PC is at ffs_data_clear+0x130/0x138
[60591.288631] LR is at ffs_data_clear+0x98/0x138
 

Attachments

  • snip.log
    36 KB · Views: 5
Last edited:

[email protected]

Senior Member
Jul 2, 2012
250
93
What rotten luck, another crash and to my untrained eye, it looks similar to the previous.

Code:
[131502.547406] synaptics,s3320: all finger up
[131504.149749] synaptics,s3320: all finger up
[131504.938613] state: 0
[131504.959312] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131504.965529] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[131504.965590] pn544_dev_write : i2c_master_send returned -107
[131504.974487] q6asm_callback: payload size of 8 is less than expected.
[131504.974841] q6asm_callback: payload size of 8 is less than expected.
[131504.982969] q6asm_callback: payload size of 8 is less than expected.
[131504.985766] trigger:1(0:stop 1:start)
[131504.986514] q6asm_callback: payload size of 8 is less than expected.
[131504.992872] enable_store: android_usb: already disabled
[131505.074898] pn544_dev_ioctl bad ioctl 1074325765
[131505.140175] Call trace:
[131505.155711] Call trace:
[131505.158738] Call trace:
[131505.158921] ffs_function_bind_config: ffs_function_bind_config(): usb_add_function() fails (err:-12) for ffs
[131505.158926] android_bind_enabled_functions: android_bind_enabled_functions: ffs failed
[131505.158949] android_enable: android_enable: usb_add_config failed : err: -12
[131506.176376] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131506.176437] Call trace:
[131506.176551] ffs_data_clear: ffs:0000000000000000 ffs->gadget= 0000000000000000, ffs->flags= 2
[131506.176565] ------------[ cut here ]------------
[131506.176570] Kernel BUG at ffffffc00077b628 [verbose debug info unavailable]
[131506.176576] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[131506.176585] CPU: 3 PID: 4721 Comm: adbd Tainted: G        W      3.18.124-lineageos-g04ff888 #1
[131506.176590] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
 

Attachments

  • console-ramoops.log
    37.3 KB · Views: 1

Not-Aus

Senior Member
What rotten luck, another crash and to my untrained eye, it looks similar to the previous.

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?
 

snyperius

Senior Member
Oct 4, 2018
54
25
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)
 
  • Like
Reactions: [email protected]

[email protected]

Senior Member
Jul 2, 2012
250
93
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?

Thx for your response. I'm about to head out for the weekend so I'll respond in detail early next week.
 

Johannes1098

Senior Member
Jul 19, 2017
161
177
Dirty flashed all the way from LineageOS 15.1, went pretty smoothly!

One small issue I noticed - the Swap Capacitive buttons option doesn't properly persist after a reboot. Turn on, works fine. Reboot, goes back to default behavior, have to re-toggle the setting for it to work. This is on today's nightly, haven't tried any others.
I can confirm this, happened to me 2 days ago, but also with the 0705 ( - but I also didn't try out the new 0712 yet..)

What rotten luck, another crash and to my untrained eye, it looks similar to the previous.

Code:
[131502.547406] synaptics,s3320: all finger up
[131504.149749] synaptics,s3320: all finger up
[131504.938613] state: 0
[131504.959312] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131504.965529] i2c-msm-v2 75b6000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[131504.965590] pn544_dev_write : i2c_master_send returned -107
[131504.974487] q6asm_callback: payload size of 8 is less than expected.
[131504.974841] q6asm_callback: payload size of 8 is less than expected.
[131504.982969] q6asm_callback: payload size of 8 is less than expected.
[131504.985766] trigger:1(0:stop 1:start)
[131504.986514] q6asm_callback: payload size of 8 is less than expected.
[131504.992872] enable_store: android_usb: already disabled
[131505.074898] pn544_dev_ioctl bad ioctl 1074325765
[131505.140175] Call trace:
[131505.155711] Call trace:
[131505.158738] Call trace:
[131505.158921] ffs_function_bind_config: ffs_function_bind_config(): usb_add_function() fails (err:-12) for ffs
[131505.158926] android_bind_enabled_functions: android_bind_enabled_functions: ffs failed
[131505.158949] android_enable: android_enable: usb_add_config failed : err: -12
[131506.176376] dwc3 6a00000.dwc3: ep0out: Unable to dequeue while in LPM
[131506.176437] Call trace:
[131506.176551] ffs_data_clear: ffs:0000000000000000 ffs->gadget= 0000000000000000, ffs->flags= 2
[131506.176565] ------------[ cut here ]------------
[131506.176570] Kernel BUG at ffffffc00077b628 [verbose debug info unavailable]
[131506.176576] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[131506.176585] CPU: 3 PID: 4721 Comm: adbd Tainted: G        W      3.18.124-lineageos-g04ff888 #1
[131506.176590] Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
Clean flash LOS 18 or dirty from LOS 17 (or even lower)?
 

Gaurav Shahu

Member
Nov 26, 2016
27
3
24
Nagpur
I'm having screen wake up issues. I have to press power button several times to wake up the screen. And the wake up is random, sometimes the screen turns on fast sometimes it takes a long time to turn on. I came back to lineage OS today after using Arrow OS for months. This issue was there too. It was fixed once in an Arrow OS build in March. But after that build, the issue was in every single build and not fixed till date. I thought I will not have this issue here but it's here also. Some others were having this problem there too. Please fix it, it's really annoying at times when I have a call or something important I can't wake the screen on time. And if it helps some devs there told me a long time ago that it had something to do with the boot image??? Maybe... idk help plz🙏🙏🙏
 
Last edited:

JoeBar07

Member
Jan 7, 2019
14
4
OnePlus 3
OnePlus 3T
This whole random reboot business reminds me of when my phone did that on OOS 8. Couldn't get to the bottom of it so I ended up nuking it with an unbrick tool, it's fine ever since. So your reboot issue might not be ROM related.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Anyone knows how to get VoLTE working for Telefonica/O2 Germany? Tried a different build prop, didnt work for me. Now that all 3G is shutting down, I experience horrible call experiences.
    2
    Hi,
    I can't find the gps.conf file, well I don't know how to look for it and edit it. 😅
    Could you tell me how to do it?
    I am using LOS 18.1 on my OP3 without any google apps and the GPS takes a lot of time to find me (like 5-10 minutes and sometimes it doesn't find me at all). And my phone is rooted.
    Thanks!
    Just like Hemuli said.
    Although I have a few things to add:
    I use Total Commander (it's as lightweight as a root file explorer can be and does everything I need without any unnecessary extra features; you can also download it from apkmirror and install it manually, although that way it won't update automatically).
    And if you don't travel abroad much, you can find the active NTP servers in your country on https://www.ntppool.org (active servers list on the right-hand side of the page). I find it even faster than letting the pool come up with the correct server. Navigate to your country's servers and copy-paste their address to the top of the NTP server list in your gps.conf file in the same format as the addresses that are already there (NO '#' AT THE BEGINNING OF THE ADDED LINES!). Don't forget to save the file.
    This way my phone gets a GPS fix in less than half a minute indoors (outdoors it just takes a few seconds) with the "GPS test" app. (The "GPS status & toolbox" app used to be better, but now it takes ages for it to get a fix for some reason.)
    Also, make a backup of the modified gps.conf file so that you don't have to edit it after every system update. Just copy it in /system/vendor/etc/ and overwrite the original file.
    1

    Is Airtel (india) Volte work?
    yes, working, you need to add some code in build.prop file every time when you do an OTA update.

    the code is available in this thread, search for it, you will get it.

    volte will not show in status bar after adding the code to buidld.prop. but it works.

    to test it, turn on the data & make a voice call, if data is not disconnected during your voice call, that means VoLTE is working.
    1
    Usually lineage cannot boot with locked bootloader.
    That´s basically not working because the bootloader will check the rom for a genuine signature.
    Obviously only official OOS has this signature so with a locked bootloader, the device won´t boot up.
    This is actually the intention behind all this bootloader locking and unlocking.

    However safetynet should pass.
    I´m rooted with magisk and haven´t changed the rom fingerprint so safetynet should work.
    However i´ve seen cases with two identical devices running the same software configuration but one of the two simply failing safetynet for no reason: After a fully clean flash it was fixed so i suggest trying this first.
    Thats wrong for this device. LineageOS can boot with locked bootloader, as the key is known.
    1
    Hello I would like to know about a very stable ROM to play since I will buy this phone in a short time there is a compatibility problem of some ROMs with the OnePlus 3T
    I don't think it is worth buying the 3T. This phone is too old.
  • 43
    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