yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S21 Ultra] mtm1401:
Thanks for the response, must say I'm a tad disappointed, as some of those voltages we're talking like a 6% deficit in voltage for same performance.

That said I've been pretty happy with it so far, haven't had the battery issues others seem to have suffered from.

i got pre-ordered a 256gb phantom black - was yours pre-order?
[Samsung Galaxy S21 Ultra] zoowoo:
Yeah, S21U 512gb phantom black from pre-order. It would be interesting to see more data points, from other people to actually see the range of bins and voltages.

But this might explain big variations of results from different reviewers.
[Samsung Galaxy S21 Ultra] mtm1401:
Interesting, I'll post a new thread earlier with a poll on it or something.

Hopefully 4 is the highest bin or I'll be very disappointed! That's said I don't think the binning would explain all of the issues people have been having, as I've not had any heating or performance issues :unsure:
[Samsung Galaxy S21 Ultra] zoowoo:
Maybe there are worse bins, and maybe there are other factors to consider, like cooling. But yeah, the best thing we can do is to collect more data.
[Samsung Galaxy S21 Ultra] mtm1401:
Question - Exynos Chip Bin/Performance Survey | XDA Developers Forums (xda-developers.com)

Bins	Difference in Volts at max freq
CPUCL0 (Little)	2 vs 4

6.49%​

CPUCL1 (Mid)	2 vs 3

5.45%​

CPUCL2 (Big)	2 vs 4

5.33%​

G3d (GPU)	1 vs 1

2.52%​
[Note 7 Questions & Answers] Note7_FE:
Hello,

I need some screws for my Note 7, my question is: are the S7 Edge screws "compatible"? or from the Note 8?

Thanks!
[OnePlus 3 & 3T Cross Device Development] 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?

Download the zip(s)

Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)

Perform a nandroid backup of your current ROM (Optional)

Wipe data/factory reset

Flash LineageOS

Optional: Install the Google Apps addon package

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
[OnePlus 3 & 3T Cross Device Development] 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
[OnePlus 3 & 3T Cross Device Development] 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?
[OnePlus 3 & 3T Cross Device Development] josepmaria:
Yes, you should
[OnePlus 3 & 3T Cross Device Development] Deleted member 11396015:
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...
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Yes, the key for signing the build doesn't matter.
[OnePlus 3 & 3T Cross Device Development] 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.
[OnePlus 3 & 3T Cross Device Development] raz123:
Nap time by Franco mostly solved this for me.
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Sideload TWRP 3.5.0, wipe dalvik & cache, flash 18.1. All good
[OnePlus 3 & 3T Cross Device Development] josepmaria:
Update to official build requires a clean install and an unlocked bootloader
[OnePlus 3 & 3T Cross Device Development] Andrea224:
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
[OnePlus 3 & 3T Cross Device Development] BillGoss:
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.
[OnePlus 3 & 3T Cross Device Development] Deleted member 4405529:
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://xdaforums.com/t/rom-officia...or-oneplus-3-3t.3990061/page-60#post-82568467
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
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.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
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!
[OnePlus 3 & 3T Cross Device Development] 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... :)
[OnePlus 3 & 3T Cross Device Development] Deleted member 4405529:
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/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
[OnePlus 3 & 3T Cross Device Development] Deleted member 11396015:
Thanks for the clear explanation nvertigo!
[OnePlus 3 & 3T Cross Device Development] unnilinux:
Does this rom support encryption?
[OnePlus 3 & 3T Cross Device Development] yy688go:
Thank you for your hard work and look forward to the arrival of offical los18.1.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
All the tests on LOS 18 that I did were done with LOS recovery ... Sorry, I forgot to mention it ... (I just modified my previous post) ... I didn't have time to do these tests with TWRP recovery yet.

Some time ago (month?), Magisk had some survival issues after updating (manual or OTA) an official build (LOS 17) via TWRP or LOS recovery with a locked BL.

If the Magisk installation via TWRP does not lead to a bootloop, it will be possible to root the device with a locked BL... To be confirmed !

EDIT : I just tested ...

- Lock your BL with TWRP, LOS 18 and Magisk installed = success but bootloop

- Lock your BL with TWRP and LOS 18 without Magisk installed = success

- Flash Magisk with TWRP, LOS 18 (clean or dirty flash) and a locked BL = bootloop

- Manual or OTA update with TWRP and a locked BL without Magisk installed = success

So no root with a locked BL and LOS 18 ... unless I am wrong !
[OnePlus 3 & 3T Cross Device Development] erOzeOz:
I have been running the latest 18.1 (20210405) for the last 2 days, installed as a clean flash, with Open GApps 20210130-test nano and Magisk 22.0.

I haven't notice any major bug so far, and phone is successfully rooted and passes SafetyNet and runs banks apps with no issue, which is great.

However I find the overall experience to be way less smooth than LOS 17.1 on which I was before.

I often observe lags / delays between touching the screen and the corresponding actions, such as launching apps or even within everyday's app (Whatsapp, Google Maps, so nothing heavy).

Is it something that others have also observed ? Could it be linked to a not yet optimised LOS or GApps version (in my case Open GApps test version)?
[OnePlus 3 & 3T Cross Device Development] defi231:
same result, root with magisk only with unlocked BL
[OnePlus 3 & 3T Cross Device Development] gladiac:
I guess the problem exists because of Magisk issue #4147. @dianlujitao is obviously aware of the problem. Let's hope topjohnwu can fix it :).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Thanks @gladiac and hope so !

FYI : Tested with my OP bullets Wireless Z, AAC codec is selected but grayed out in dev options (same behaviour with my OP5T) ... It seems like AptX and AAC are broken in 18.1 according to several posts ... To be confirmed !?
[OnePlus 3 & 3T Cross Device Development] JoniKatita:
Hello,

On my 3T the bluetooth in-band ringtone does not work with my car. The first call I receive works fine (the car infotainment rings) but after that I get no ringing. Is there any way to disable in-band ringtone? Or any fix?

Thank you.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Well, you're wrong 😊

As was mentioned in issue #4147, the solution is to patch the boot image using the Magisk app and then install the resulting boot image file in TWRP.

That's what I did (coming from a locked bootloader with unrooted 18.1) and now I'm rooted and the bootloader is still locked.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Well, I'm wrong ... :giggle:

I did not perform this procedure.

That would require manual intervention after every system upgrade due to missing addon.d support (as mentioned).

Did you try a manual or ota update ?

Thanks @BillGoss !
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I never do ota updates automatically - I always manually install them. The main reason for that is:

- I like to take a backup before installing an update so that I can revert the change easily if necessary.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Let's forget about OTA update.

My question was: did you try to do a manual update after patching your boot image with a locked BL?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
A dirty flash update resulted in a boot loop. Installing a patched boot image (I created it before flashing the update) fixed the problem.

I noticed that the Magisk add-on script execution had an error but finished successfully:

sh: 21: unknown operand
! Unable to detect Magisk Manager APK for BootSigner
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
I really think it's the job of topjohnwu to fix this. His root-solution in unusable without surviving an update or -even much bader- breaking the phone after an update.

At least in the past it was already working. Why don't keep up with that?

Alternatively, like dianlujitao was asking topjohnwu, to let the maintainers maintain this part.
[OnePlus 3 & 3T Cross Device Development] christantoan:
Nope. topjohnwu already said that using Magisk with locked bootloader is unsupported. It might work in the past but if it's unsupported then changes may happen that breaks it.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
And I would agree with this. There's no need to have a locked bootloader if you're using Magisk.

Also, there are very few phones (to my knowledge) that allow you to run custom ROMs and recoveries with a locked bootloader.

I only locked my bootloader to see what it's like to not use Magisk. It's been ages since I've used an unrooted phone.
[OnePlus 3 & 3T Cross Device Development] lugamar:
Same here
[OnePlus 3 & 3T Cross Device Development] felixchris:
Just went from @Eric_Lev's build to the latest nightly (05.April), wiping System and Caches, reflashing MindTheGapps and latest Magisk. Data retained, no issues so far.

For me NFC Payments via GPay are working. Selected all my Banking Apps, GPay , PayPal and the entire Play Services in Magisk Hide. I had it working with not all of the Play Services - but then it randomly stopped working - so I am selecting all again. Note that I use Magisk to pass SafetyNet because I keep my BL open.

Weirdly enough my push-tan app" tan2go" from the DKB (German Bank, same push-tan as Sparkasse and some others that use Starfinanz) refuses to work again. I need to find out again what it is detecting.
[OnePlus 3 & 3T Cross Device Development] malerocks:
I am a bit confused from all the comments I have read, but if I got it right:

With lineageos 18.1, its possible to have the ROM on the oneplus 3t without having the BL unlocked - As long as you don't want to use Magisk?

Is so:

- Do you have unlock to flash recovery and ROM for the 1st time and after that, you can lock it again? Or do you don't need to unlock at all?

- Does the recovery have to be TWRP or you can use the one provided by lineageos
[OnePlus 3 & 3T Cross Device Development] rohan164:
well, its individual choice. and it also has pros and cons.

BL lock/unlock doesn't matter since you are installing cutom rom.

you can lock BL using both TWRP and LOS recovery.

i am using LOS with locked BL and with LOS recovery.

with twrp recovery i really don't know how to lock BL.

some literature is available in LOS 17.1 rom thread. but i am not sure whether it applies for LOS 18.1

may be @BillGoss can through some more information on this topic.

as he said he is using twrp with Locked BL and magisk ON.
[OnePlus 3 & 3T Cross Device Development] malerocks:
Thanks. I understand its individuals choice. I am trying to understand the options that work.

I am still not clear if the recovery and ROM can be flashed without unlocking the bootloader
[OnePlus 3 & 3T Cross Device Development] rohan164:
yes, you have to unlock the bootloader to flash recovery. but rom can be flashed on both locked and unlocked BL
[OnePlus 3 & 3T Cross Device Development] felixchris:
To put it simply:

If you have a stock Oneplus 3 or 3t and you want to install Lineageos, you need to unlock the bootloader. Then install one of the two recoveries to flash newest firmware (if needed), the ROM and Gapps. You can lock the bootloader afterwards. The only benefit is potentially passing safety net without Magisk.

But as you have said, you cannot install a custom ROM without unlocking the bootloader at least once.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Assuming you're already using a custom ROM, the questions you need to answer is:

- Do I want to use Magisk to get access to root functions?

If the answer is Yes, then keep the bootloader unlocked because this will avoid getting boot loops when you flash Magisk.

If the answer is No, then ask the following question:

- Do I need to pass SafetyNet?

If the answer to this question is Yes, then lock the bootloader.

If the answer is No, then the choice is yours: either locked or unlocked is ok.

And my plug for security: Always encrypt your phone and set an on-boot password - say Yes on this screen:
[OnePlus 3 & 3T Cross Device Development] malerocks:
Thanks all for your responses. Helps a lot.

My main reason for asking all of these questions is because i intend to pass the phone to my father. He does not have a lot of requirements from the phone barring a handful of apps.

He certainly won't be comfortable having to handle magisk/root or updates and he is the kind who would get worried if an app suddenly told him that it thinks the phone is rooted and hence potentially unsafe.

Hence I was interested in all of the info to decide the best configuration for him. I think I'll probably do the no root and locked bootloader thing.
[OnePlus 3 & 3T Cross Device Development] johngare:
I clean installed this rom. Installation and setting up the device was a success. As soon as the screen goes off, i tried turning it on by pressing the fingerprint scanner and the screen flickers, so I tried the power button and same thing. I restarted my phone and it went okay, after the screen went off i opened it again using the power button this time but same issue persists, screen won't turn off but just keeps on flickering. Now I'm back with A10 rom with no screen flickering issue. It seems that all the A11 roms that I installed are giving me the issue with screen flickering and not turning back on.
[OnePlus 3 & 3T Cross Device Development] rohan164:
Can someone share patched boot image for magisk?

@BillGoss

I am on los recovery and it is not allowing me to push and pull system files. Or I don't know how to do it.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I always use TWRP in recovery.

And you can create your own patched boot image by taking the boot.img file in the rom zip file and then patching it with the Magisk APK.
[OnePlus 3 & 3T Cross Device Development] mike.sanders:
Well, I intend to stick to OpenGApps since it served me well during the last years. Even if that means I have to wait a little longer till I can make the transition to 18.1.

You did not explicitly answer my question(s), but I assume that by the very omission your description means that updating to TWRP 3.5 or unlocking the bootloader is, indeed, unnecessary and that I should be able to update without data loss. Yay!

To me, the only real difference between the sideloading procedure described at https://wiki.lineageos.org/devices/oneplus3/upgrade and your directions (flashing downloaded ZIPs - LOS, GApps, FDroid - directly on the device via TWRP) seems to be that you advise to explicitly wipe system (and cache) beforehand?

- Mike
[OnePlus 3 & 3T Cross Device Development] vettayyan:
I already write this Query a While ago, facing issue of parallel running of this 3 Apps...

While keeping ROOT BASED ADBLOCK on ADAWAY , hiding the AMAZON on MAGISK, hiding the Magisk Manager done all ,, Still AMAZON stucks out saying not working... Any Solutions !! ??????
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Your BL : locked or unlocked ?

Root = magisk = BL unlocked = TWRP (recommended)

OpenGapps = currently not compatible with LOS 18.1 ... soon available ?

About I did not explicity answer ... Sorry, I have a real life !

Any solutions ????? ... Lock your BL !!!!!!

As reminder :

https://xdaforums.com/t/rom-officia...for-oneplus-3-3t.4230665/page-9#post-84789977

https://xdaforums.com/t/rom-11-0-official-lineageos-18-1-for-oneplus-5-5t.4173997/post-84770085
[OnePlus 3 & 3T Cross Device Development] rohan164:
Los recovery with locked BL.

This means I have to install now twrp recovery and unlock BL.

😔
[OnePlus 3 & 3T Cross Device Development] vettayyan:
So will the safetynet pass after locking Bootloader ??
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Yes !

Please read my response before posting:

https://xdaforums.com/t/rom-11-0-of...or-oneplus-5-5t.4173997/page-17#post-84770085
[OnePlus 3 & 3T Cross Device Development] rohan164:
can some one tell me how to edit build.prop on los 18.1

i am on los recovery, locked BL = no root & no magisk.

i tried adb push pull method on los recovery, but i don;t know how to do it or los recovery does not allow it.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Did you enable USB debugging and Rooted debugging in dev options ?

==> https://xdaforums.com/t/rom-official-nightly-lineageos-17-1-for-oneplus-3-3t.3990061/post-82169973