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

Search This thread

BillGoss

Senior Member
Sep 2, 2010
4,537
3,928
Sydney
OnePlus 3T
OnePlus 8T
If I install this can I stay decrypted please?
I've found that it will automatically encrypt the phone when I install it after doing a Wipe>Format Data in TWRP.

But if you use Magisk, you should be able to patch the boot image to NOT preserve force encrypt - but I've never done this because an unencrypted phone is a security risk.
Screenshot_20210421_073301.jpg
 
  • Like
Reactions: mk_1996

anttaz

Senior Member
Nov 1, 2009
1,349
280
Doncaster
www.facebook.com
I've found that it will automatically encrypt the phone when I install it after doing a Wipe>Format Data in TWRP.

But if you use Magisk, you should be able to patch the boot image to NOT preserve force encrypt - but I've never done this because an unencrypted phone is a security risk.
View attachment 5285535
Thanks but too late to use app if already encrypted during first boot. Shame I will have to go for a decrypted ROM
I've found that it will automatically encrypt the phone when I install it after doing a Wipe>Format Data in TWRP.

But if you use Magisk, you should be able to patch the boot image to NOT preserve force encrypt - but I've never done this because an unencrypted phone is a security risk.
View attachment 5285535
Thanks for the suggestion. But by time got to Magisk app too late as phone already booted and forced encryption, therefore Magisk app would be unable to decrypt an encrypted device. I shall find a ROM that does not force me to be encrypted. Thanks.
 

BillGoss

Senior Member
Sep 2, 2010
4,537
3,928
Sydney
OnePlus 3T
OnePlus 8T
Thanks but too late to use app if already encrypted during first boot. Shame I will have to go for a decrypted ROM

Thanks for the suggestion. But by time got to Magisk app too late as phone already booted and forced encryption, therefore Magisk app would be unable to decrypt an encrypted device. I shall find a ROM that does not force me to be encrypted. Thanks.
You could install the Magisk apk (which doesn't root your phone, simply installs the app) on your current setup and then use it to patch the Los 18.1 boot.img. Then when you flash Los 18.1 also flash the patched boot.img. That should keep the phone unencrypted. But, like I've said, I've not tried this.
 

[GER]Roxxor

Senior Member
  • Sep 5, 2010
    525
    303
    Nürnberg
    So does anybody else have issues with GPS? Like said in my post before, there is simply no satellites shown. Changing the NTP Server to Europe in the GPS config fixed it for a day. Now it doesnt work again. I also tested Oxygen OS to exclude an hardware flaw, I have no issues getting a fix in OOS.
    I now set set the logging level to verbose, an thats what is repeatedly shown:
    Code:
    04-21 08:18:17.370   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
    04-21 08:18:17.370   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 69
    04-21 08:18:17.371   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
    04-21 08:18:17.371   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
    04-21 08:18:18.372   581  1512 V LocSvc_api_v02: locClientIndCb:949]: Indication: msg_id=36 buf_len=18 pCallbackData = 0x7aa9aaa350
    04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeByEventIndId:2382]: event ind Id 36 size = 488
    04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeAndTypeByIndId:730]: indId 36 is an event size = 488
    04-21 08:18:18.373   581  1512 I LocSvc_ApiV02: <--- globalEventCb line 115 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
    04-21 08:18:18.373   581  1512 V LocSvc_ApiV02: globalEventCb:120] client = 0x7aa9aaa350, event id = 36, client cookie ptr = 0x7b39aaa110
    04-21 08:18:18.373   581  1512 V LocSvc_LBSApiV02: eventCb:61] client = 0x7aa9aaa350, event id = 36, event name = QMI_LOC_EVENT_POSITION_REPORT_IND_V02 payload = 0x79e4f0ea30
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: eventCb:3954]: event id = 36
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: Reporting position from V2 Adapter
    04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: reportPosition:2264 QMI_PosPacketTime  1779 (sec)  137992285 (nsec)
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase: flags: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   source: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   latitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   longitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   altitude: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   speed: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   bearing: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   accuracy: 0.000000
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   timestamp: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawDataSize: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawData: 0x0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   Session status: 2
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  Technology mask: 0
    04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  SV used in fix (gps/glo/bds/gal/qzss) :              (0/0/0/0/0)
    04-21 08:18:18.374   581  1512 D LocSvc_IzatAdapterBase: reportPositionEvent: default implementation invoked
    04-21 08:18:18.374   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
    04-21 08:18:18.374   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 70
    04-21 08:18:18.374   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
    04-21 08:18:18.375   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
     

    Jan_L

    Member
    Jan 15, 2021
    28
    24
    Samsung Galaxy S7
    OnePlus 3T
    If I install this can I stay decrypted please?
    I am using LOS for some years now, but can choose myself if I want to encrypt or not.
    On 18.1 I am not encrypted at the moment.

    Don't know if this is what you mean, but my phone is not forcing encryption.
    When this is not the default behaviour, I don't know anymore what I have done for that in the past unfortunately, but you are right; I want to choose myself ;-)
     

    Attachments

    • Encryption.png
      Encryption.png
      127.2 KB · Views: 59
    • Like
    Reactions: anttaz

    Jan_L

    Member
    Jan 15, 2021
    28
    24
    Samsung Galaxy S7
    OnePlus 3T
    So does anybody else have issues with GPS? Like said in my post before, there is simply no satellites shown. Changing the NTP Server to Europe in the GPS config fixed it for a day. Now it doesnt work again.
    I now set set the logging level to verbose, an thats what is repeatedly shown:
    Code:
    <CUT>
    For what it is worth.... I did not take any logs or whatever...
    I am using a gps config where I am using pool.ntp.org and let the auto selection decide.
    Normally this is only taking 3-5 seconds (no Google stuff on my phone and wifi and bluetooth scanning disabled).
    Though.... sometimes it is not. The work around for me then (take note of the order!) is starting the app using gps and then disabling gps >>> wait till icon in taskbar is gone, and enable gps again.
    This way in 3-5 seconds I have my gps back, not the other way around though....

    One of my apps is not working correctly with 18.1 gps, where it was with 17.1 gps. So it seems something is changed in between, but did not check already in the changelogs. For those who want to try: the route.nl app will take the right gps location on startup, after that gps is not refreshed anymore, where other apps are working correctly.
     
    • Like
    Reactions: JoeBar07

    votz11

    Member
    Mar 18, 2019
    20
    7
    I am using LOS for some years now, but can choose myself if I want to encrypt or not.
    On 18.1 I am not encrypted at the moment.

    Don't know if this is what you mean, but my phone is not forcing encryption.
    When this is not the default behaviour, I don't know anymore what I have done for that in the past unfortunately, but you are right; I want to choose myself ;-)
    how you update your vendor ?
     

    Attachments

    • IMG_20210421_104320.jpg
      IMG_20210421_104320.jpg
      136.9 KB · Views: 58
    • Like
    Reactions: anttaz

    [GER]Roxxor

    Senior Member
  • Sep 5, 2010
    525
    303
    Nürnberg
    For what it is worth.... I did not take any logs or whatever...
    I am using a gps config where I am using pool.ntp.org and let the auto selection decide.
    Normally this is only taking 3-5 seconds (no Google stuff on my phone and wifi and bluetooth scanning disabled).
    Though.... sometimes it is not. The work around for me then (take note of the order!) is starting the app using gps and then disabling gps >>> wait till icon in taskbar is gone, and enable gps again.
    This way in 3-5 seconds I have my gps back, not the other way around though....

    One of my apps is not working correctly with 18.1 gps, where it was with 17.1 gps. So it seems something is changed in between, but did not check already in the changelogs. For those who want to try: the route.nl app will take the right gps location on startup, after that gps is not refreshed anymore, where other apps are working correctly.
    Ah. That workaround helps. Worked for me. Yeah, but somethings not right.
    @dianlujitao
    Could you maybe have a look? I would be happy to provide more data if needed.
     

    votz11

    Member
    Mar 18, 2019
    20
    7
    i see... thanks... locked BL here, so no need to change build.prop as bank apps work perfect

    I am using LOS for some years now, but can choose myself if I want to encrypt or not.
    On 18.1 I am not encrypted at the moment.

    Don't know if this is what you mean, but my phone is not forcing encryption.
    When this is not the default behaviour, I don't know anymore what I have done for that in the past unfortunately, but you are right; I want to choose myself ;-)
    if u want to make encyption enable ( green )
    u must unlock BL
    twrp >> format data >> restart twrp
    twrp >> cache (ext4) , data (f2fs) , system ( ext4)
    twrp >> flash OOS 9.0.6 rom >> open the system
    twrp >> wipe cache-data-system >> restart twrp
    twrp>> flash los18+gapps >> open system
    set pin+fingerprint and u will see encryption enable in settings, and ask for password in bootloader when you restart your phone like OOS rom
    work at least for me in some tests i made
     
    Last edited:
    • Like
    Reactions: anttaz

    Jan_L

    Member
    Jan 15, 2021
    28
    24
    Samsung Galaxy S7
    OnePlus 3T
    <CUT>

    if u want to make encyption enable ( green )

    <CUT>
    I know how to encrypt (see attched, can enable it if I want), though do not want to.
    Using fstrim sometimes to optimise (yes I know; probably I do not even notice the difference), with encryption fstrim does not work.
     

    Attachments

    • Screenshot_20210421-124035_Settings.png
      Screenshot_20210421-124035_Settings.png
      138.4 KB · Views: 45
    • Like
    Reactions: anttaz and votz11

    mangokm40

    Senior Member
    Jan 13, 2019
    61
    13
    I clean flashed (incl format) 18.1 04.05 build on 04.05. I was running 17.1
    previously.
    TWRP 3.5.1, Magisk 22.0, no GApps. There's no encryption. BL is unlocked.

    I turned the phone on after several days off. Using GPS Test (chartcross),
    it got a 3D fix in 65 seconds. I am inside a single-story structure on a
    very miserable, rainy day.
     

    Jan_L

    Member
    Jan 15, 2021
    28
    24
    Samsung Galaxy S7
    OnePlus 3T
    Could anyone with the latest OOS on their phone get the original gps.conf file to compare it to the one in LOS?
    I know it is not exactly what you asked, though based on your previous posts it could be helpfull to compare your gps.conf file with mine. I do not have any issues with not finding satellites, just the one as mentioned before which has probably nothing to do with the conf file but the gps part in LOS 18.1 itself.

    My gps_debug.conf in /system/etc is completely empty, I am only using /system/vendor/etc/gps.conf for the setting, just as it should be.

    Enclosed my files for what it is worth ;-)
     

    Attachments

    • gps.zip
      2.6 KB · Views: 3
    • gps_debug.zip
      199 bytes · Views: 1
    • Like
    Reactions: snyperius

    Top Liked Posts

    • There are no posts matching your filters.
    • 5
      For what it is worth.... I did not take any logs or whatever...
      I am using a gps config where I am using pool.ntp.org and let the auto selection decide.
      Normally this is only taking 3-5 seconds (no Google stuff on my phone and wifi and bluetooth scanning disabled).
      Though.... sometimes it is not. The work around for me then (take note of the order!) is starting the app using gps and then disabling gps >>> wait till icon in taskbar is gone, and enable gps again.
      This way in 3-5 seconds I have my gps back, not the other way around though....

      One of my apps is not working correctly with 18.1 gps, where it was with 17.1 gps. So it seems something is changed in between, but did not check already in the changelogs. For those who want to try: the route.nl app will take the right gps location on startup, after that gps is not refreshed anymore, where other apps are working correctly.
      Ah. That workaround helps. Worked for me. Yeah, but somethings not right.
      @dianlujitao
      Could you maybe have a look? I would be happy to provide more data if needed.
      4
      Yes it helps,, But how to take my home screen or lockscreen is my Question, Some thing i like to show on Home screen or Lock screen , whats the way out??
      Well, for the home screen there's a way if you are rooted, have installed Termux, and are willing to put a widget on your home screen.
      Since this has nothing to do with Los 18.1, it's time to take the conversation elsewhere.
      Send me a PM if you want to try the above suggestion.
      3
      So does anybody else have issues with GPS? Like said in my post before, there is simply no satellites shown. Changing the NTP Server to Europe in the GPS config fixed it for a day. Now it doesnt work again. I also tested Oxygen OS to exclude an hardware flaw, I have no issues getting a fix in OOS.
      I now set set the logging level to verbose, an thats what is repeatedly shown:
      Code:
      04-21 08:18:17.370   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
      04-21 08:18:17.370   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 69
      04-21 08:18:17.371   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
      04-21 08:18:17.371   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
      04-21 08:18:18.372   581  1512 V LocSvc_api_v02: locClientIndCb:949]: Indication: msg_id=36 buf_len=18 pCallbackData = 0x7aa9aaa350
      04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeByEventIndId:2382]: event ind Id 36 size = 488
      04-21 08:18:18.373   581  1512 V LocSvc_api_v02: locClientGetSizeAndTypeByIndId:730]: indId 36 is an event size = 488
      04-21 08:18:18.373   581  1512 I LocSvc_ApiV02: <--- globalEventCb line 115 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
      04-21 08:18:18.373   581  1512 V LocSvc_ApiV02: globalEventCb:120] client = 0x7aa9aaa350, event id = 36, client cookie ptr = 0x7b39aaa110
      04-21 08:18:18.373   581  1512 V LocSvc_LBSApiV02: eventCb:61] client = 0x7aa9aaa350, event id = 36, event name = QMI_LOC_EVENT_POSITION_REPORT_IND_V02 payload = 0x79e4f0ea30
      04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: eventCb:3954]: event id = 36
      04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: Reporting position from V2 Adapter
      04-21 08:18:18.373   581  1512 D LocSvc_ApiV02: reportPosition:2264 QMI_PosPacketTime  1779 (sec)  137992285 (nsec)
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase: flags: 0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   source: 0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   latitude: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   longitude: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   altitude: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   speed: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   bearing: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   accuracy: 0.000000
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   timestamp: 0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawDataSize: 0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   rawData: 0x0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:   Session status: 2
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  Technology mask: 0
      04-21 08:18:18.374   581  1512 D LocSvc_LocApiBase:  SV used in fix (gps/glo/bds/gal/qzss) :              (0/0/0/0/0)
      04-21 08:18:18.374   581  1512 D LocSvc_IzatAdapterBase: reportPositionEvent: default implementation invoked
      04-21 08:18:18.374   581  1512 D LocSvc_GnssAdapter: reportPositionEvent]: fromUlp 0 status 2
      04-21 08:18:18.374   581  1512 D LocSvc_ApiV02: reportPosition:2512]: Ignoring position report with sess status = 7, fix id = 70
      04-21 08:18:18.374   581  1503 V LocSvc_nmea: Entering loc_nmea_generate_pos line 481
      04-21 08:18:18.375   581  1503 V LocSvc_nmea: Exiting loc_nmea_generate_pos line 979 0
      3
      I just want to drop a couple of lines on the subject of LineageOS 18.1, OnePlus 3T, and my status.

      First, thanks to lots of people on XDA in general and quite a few in this thread in particular.

      I stopped using my 3T sometime last year, since it hadn't had any updates from 1+ since late 2019, and I gifted my wife a new phone (Xiaomi Mi Note 10 pro, slow but great cam). So I took her old Nokia 8, which was fine and faster (got all important data off my 3T, got all important apps and connections running). But: it also didn't get updates since Oct/Nov 2020. And I desperately want a backup device, so I figured I should get the 3T up and running.
      Following instructions here and at the LineageOS device site, I unlocked the bootloader, installed TWRP - I still don't know if the LineageOS recovery would have been better, but it works - flashed LOS, MindTheGApps and Magisk.

      I didn't necessarily want to root my phone, but figured I'd give it a go. I have some old Galaxy S4's in the household running LOS 17, and with F-Droid with the background installation, getting updates is really much easier.
      I did have trouble with Magisk 22100, I think it's somewhere in this thread that 22104 will get the device past safetynet. So I got that one, forgot how I flashed it (within Magisk? Don't remember, must be getting old...) but it does work fine.

      All my banking apps work. Well, now they do, after getting Magisk to hide. I had one app that somehow detected something non-standard, but luckily the programmers just made it show a warning: "we don't support rooted Android devices, continue at your own risk [ ok ] [ cancel ]" so that was acceptable.
      I don't know how they could detect the device is rooted. Perhaps they detect the unlocked bootloader?

      I also missed how to get the device encrypted, I now read in this thread how to do it, but it will have to wait for another day.
      Yesterday I updated to the latest nightly, I wasn't quite sure if I would run into trouble, but all was fine, still rooted, banking stuff still working, etc.

      Like I said, the 3T is my backup device, but with all that I have used it setting it up, I can say that LineageOS feels snappy. Battery life is great, but I don't use it with my 2 SIM cards (so just WiFi).

      Next I'll update my N8 - sometime last year I got the unlock code when Nokia /HMD were still giving those out - but not until I have another redundant device.
      3
      Here's a graph showing the charging rates of OOS 9.0.6 (OOS 4/20), Los 17.1 (Los 4/20), and Los 18.1 (Los 4/21).
      Screenshot_20210417-080249_Excel.png
    • 40
      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
    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