• 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

dianlujitao

Senior Member
Jan 27, 2013
727
4,808
Chengdu
www.dianlujitao.com
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
 
Last edited:

BillGoss

Senior Member
Sep 2, 2010
4,802
4,252
Sydney
OnePlus 3T
OnePlus 8T
My initial testing of this rom is that everything is working (based on my usage): WiFi, phone calls, SMS, NFC (Google Pay) all work.
I had a bit of problem setting the wallpaper initially (FCed), but the problem went away on its own after waiting a bit of time.
I'm missing the settings option to specify the duration of the capacitive key backlight, but that's no big deal.

I'm using Opens Gapps pico 210130 and Magisk 21047.

I've seen evidence of the sensor_SMD kernel wake lock issue that I've seen on all Android 11 roms I've tested previously. I'll post more details on this once I've captured a logcat of the problem.
 

josepmaria

Senior Member
Apr 3, 2007
140
84
Would updating to official builds be possible later on, based on the fact public keys are used?

Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...

Update to official build requires a clean install and an unlocked bootloader
 

BillGoss

Senior Member
Sep 2, 2010
4,802
4,252
Sydney
OnePlus 3T
OnePlus 8T
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.
 

Attachments

  • 210209-174541-log.zip
    124.9 KB · Views: 12
  • Screenshot_20210209-202832_BBS.png
    Screenshot_20210209-202832_BBS.png
    166.6 KB · Views: 438
  • 210209-202851-log.zip
    115.5 KB · Views: 6
Last edited:

nvertigo67

Senior Member
Dec 28, 2011
6,029
12,340
Update to official build requires a clean install and an unlocked bootloader
If the plattform key is changed a clean flash is highly recommended (though not required if you use a migration script or zip - NOT!!! recommended). Since los recovery (as well as current twrp for that matter) and los boot image are signed with aosp verity key, you don't need to unlock bl if you run any version of los with a locked bl.

I've explained the three different keys and signatures used in a single build in depth in the llos 17 thread: https://forum.xda-developers.com/t/...or-oneplus-3-3t.3990061/page-60#post-82568467
 

dianlujitao

Senior Member
Jan 27, 2013
727
4,808
Chengdu
www.dianlujitao.com
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.
 

BillGoss

Senior Member
Sep 2, 2010
4,802
4,252
Sydney
OnePlus 3T
OnePlus 8T
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.
I set the property as you suggested. After more than 12 hours, including a full recharge, there's no sign of the wake lock. It's looking good.
Thank you!
 

Jan_L

Senior Member
Jan 15, 2021
58
42
Samsung Galaxy S7
OnePlus 3T
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?

It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....

You see, no idea what I am talking about; I hope someone can clear things up... :)
 
Last edited:

nvertigo67

Senior Member
Dec 28, 2011
6,029
12,340
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?

It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....

You see, no idea what I am talking about; I hope someone can clear things up... :)
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.

/default.prop is read first and contains settings necessary for basic boot (historically this file has been part of the root partition which has been ramfs contained in the boot image as cpio archive prior to system as root, which allows to set these props before system was mounted - obviously that's not longer the case with system as root.

/system/vendor/build.prop is read as second source containing vendor specific props. Systematically this should contain settings specific to the vendor(s) of the device and the actual os (which are the same, as long as you use stock roms, but obviously differ if you use an custom source build rom like los).

/system/build.prop is reaf as third source and should contain general android settings.

If the same prop is set in more then one file the last one wins as long as it's no read only prop (ro.*). For ro.* prop the first one wins, because it can't be changed after setting. Exeption: if you use magisk, you can alter ro.* props (by command from the commamdline or a script).

Additionally to these three sources some props are set by init (first os process started by the kernel and controlling the boot process). See:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi there, anyone knows wich would be the best Gcam available for 18.1? No config files for Oneplus 3T in the latest versions.
    Many thanks
    Download latest BSG-Gcam8.1 here https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/f/dl59/
    Download and apply this XML in the attached file (done by me for tuning a bit the lib), then apply this lib (done by MWP) https://t.me/gcamlibs/46
    2
    Hi there, anyone knows wich would be the best Gcam available for 18.1? No config files for Oneplus 3T in the latest versions.
    Many thanks
    Answering to myself, if someone cares, using Arnova8G2 (GCam 7.3) with op3-base-arnova7.3.xml with very good results
    1
    I have replaced my screen before. Just clear the cache and all is good.
    I tried that. Thanks for tip anyways. I tried other roms like pixel experience doesn't have this issue.

    @nvertigo67 thanks for additional suggestions. Will debug see what display is since I don't know if it's original.
    1
    My battery drain without any use
    1
    Did you check the downloaded zip's sha256 checksum? Whats the complete error message in the recovery log?
    Good idea, I didn't see the checksum there. I can verify the checksum is correct.

    Edit: I see what you mean, here is the relevant recovery log:

    Code:
    Patching system image unconditionally...performing update
    blockimg version is 4
    maximum stash entries 0
    creating stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524
    234991616 bytes free on /cache (0 needed)
    /cache/recovery/last_command doesn't exist.
    erasing 320699 blocks
    writing 1024 blocks of new data
    writing 1024 blocks of new data
    ...
    writing 1024 blocks of new data
    writing 1024 blocks of new data
    Decompression failed with BLOCK_LENGTH_2
    missing 2136618 bytes of new data
    failed to execute command [new 2,271343,272367]
    script aborted: E1001: Failed to update system image.
    E1001: Failed to update system image.error: 1001
    Updater process ended with ERROR: 1

    It's failing to decompress the image. So either the download is corrupt or the internal storage is corrupt.

    Edit 2: SUCCESS! I formatted the internal storage and copied the image over new. It flashed successfully first time. I guess somehow that internal storage filesystem had become corrupt.

    Your prompting to find the full recovery log led me to the solution. Thank you so much, I really appreciate your help!
  • 45
    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