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

[dianlujitao]

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.

#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:

• https://github.com/lineageos

Credits:

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

Changelog and Download:

2021/2/8 (Initial release): https://androidfilehost.com/?fid=17248734326145731516​

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.

2021/4/2: https://download.lineageos.org/oneplus3​

• Fixed the sensor_SMD wakelock
• Fixed ringtone when bluetooth headset connected

 

[gaizkaxda]

Wow !!! , i'm on LOS 17.1 Official now but waiting for LOS 18.1 Official
OP3 is my daily driver..
Thank you @dianlujitao

 

[Keyvannn]

Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?

 

[josepmaria]

Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?

Yes, you should

 

[Deleted member 11396015]

Yes, you should

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...

 

[dianlujitao]

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...

Yes, the key for signing the build doesn't matter.

 

[BillGoss]

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.

 

[raz123]

sensor_SMD kernel wake lock issue

Nap time by Franco mostly solved this for me.

 

[OTAx1]

Sideload TWRP 3.5.0, wipe dalvik & cache, flash 18.1. All good

 

[josepmaria]

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

 

[Andrea224]

Nap time by Franco mostly solved this for me.

Last time I used NapTime, it drains more battery than it should and my phone was almost all the time in idle untouched with WIFI and everything else off

 

[BillGoss]

Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:

But the wake lock can start at random times:

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.


Fortunately, a reboot gets rid of the wake lock.

 

[nvertigo67]

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]

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]

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!

 

[Deleted member 11396015]

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...

 

[nvertigo67]

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:

android_device_oneplus_oneplus3/init_oneplus3.cpp at lineage-18.1 · LineageOS/android_device_oneplus_oneplus3

Contribute to LineageOS/android_device_oneplus_oneplus3 development by creating an account on GitHub.

github.com

 

[Deleted member 11396015]

First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.

Thanks for the clear explanation nvertigo!

 

[unnilinux]

Does this rom support encryption?

 

[yy688go]

Thank you for your hard work and look forward to the arrival of offical los18.1.