yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Which ROM are you on and why do you want to change to LOS ?

If you want a perfect ROM for your device then I would suggest you stay on OOS, And if you're willing to try new things with minor bugs then you can try any custom rom.

As of LOS there's no bug for me, I'm using it as daily driver, my battery hold up good enough for almost a day.

If you really want to compare better try yourself these things works different for everyone.

Don't forget to search the thread for any queries you have in your mind.
[OnePlus 3 & 3T Cross Device Development] wojtek007pl:
I am on stock 5.0.8 and I had an idea to upgrade because of visual features of newer rom. I am asking here, because info I got from this thread is pretty inconclusive in my view. I guess I will stay on 5.0.8 as upgrade and potential downgrade would possibly cost me up to 6 hours of time.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Maybe you are facing this issue? https://gitlab.com/LineageOS/issues/android/-/issues/1805#note_358898400
[OnePlus 3 & 3T Cross Device Development] punio4:
So far there hasn't been any dev that has acknowledged this issue. Hope it gets sorted out soon.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
New build is up.
[OnePlus 3 & 3T Cross Device Development] LaDidac:
Lineage bootloop, please help.

Hi everyone. I have a problem I hope you can help me solve.

Last night, I tried installing this OS from the stock OS, following the instructions, from start to finish, found on the wiki page.

The problem is that the Lineage logo does bootloop for several minutes and then puts me back to TWRP. I have tried doing the reinstallation of Lineage, with no success. And I have tried installing the no verity zip 6.0 zip (because I thought dm-verity might be causing the bootloop), but I keep getting an error (Error: 1) when I try to install it.

I have searched for hours on how to fix this, but to not avail.

Can someone please help?

Thanks
[OnePlus 3 & 3T Cross Device Development] :
No idea about error code, you probably already did an extended search on that one?

But things I can imagine which went wrong:

- latest firmware (9.06) installed?

- latest twrp (3.4.0.0) installed?

- everything formatted to EXT4 including data using TWRP?

- pico or nano Gapps installed (or no Gapps of course)?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Just to mention that /data and /cache can also be on F2FS - just in case [MENTION=10971269]LaDidac[/MENTION] is, he doesn't need to reformat

[MENTION=10971269]LaDidac[/MENTION] did you install the TWRP app as systen app in TWRP. I'm not sure if the priv-app permission missing problem is still there, but this causes also bootloops. So just don't install the TWRP app :)
[OnePlus 3 & 3T Cross Device Development] :
Maybe you've ignored the last warning on the wiki page (https://wiki.lineageos.org/devices/oneplus3/install ) and installed twrp manager before rebooting the flashed system.

Considering you've followed the wiki page to the word, this can't happen. Please give the exact and complete versions of oos you've started from, twrp, los build and gapps.

EDIT: did you check validity of the flashed zips? (los: sha256; gapps: md5; twrp: md5 or sha256)
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
[MENTION=4405529]nvertigo67[/MENTION] same thoughts, posted almost simultaneously - could be a case of mental telepathy ;) :p

Edit: quite a bit OT, sry for that - but otherwise, it's funny ; )
[OnePlus 3 & 3T Cross Device Development] :
Maybe. But I belive this is more probable: if one fromats data and flashes los, there arn't many reasons to create a bootloop; plus teading this thread at the same time... I don't belive in telepathy (or homeopathy or ancient aliens or qanon for that matter)... On the other hand I belive in quantum physics, so quantum entaglement of neuronal atoms maybe another option... ;)

Sorry for OT, but SCNR.
[OnePlus 3 & 3T Cross Device Development] LaDidac:
Thank you all for your responses!

I did do an extended search for the no verity error zip, multiple times, but found nothing.

Also, I am a noob with a basic understanding of this stuff, but I have flashed custom ROMS before on a different phone. And I have watched several videos, read several posts regarding this OS and this phone, but to no avail. So I am totally bewildered right now.

[MENTION=10511117]Johan2020[/MENTION]

- Yes, I had the latest firmware (9.06) installed.

- Yes, I have the latest twrp (3.4.0.0) installed.

- No, I did not format everything to EXT4 (as it is not mentioned in the wiki page). At what point during the process should this be done?

- I have nano Gapps installed.

[MENTION=8423339]Johannes1098[/MENTION] Yes, I did let TWRP install itself. I am only supposed to boot it using fastboot?

[MENTION=4405529]nvertigo67[/MENTION] No, I didnt I ignore the last warning (and TWRP never asked me to install additional apps or services.)

- oos 9.0.6 (the latest update)

- twrp = twrp-3.4.0-0-oneplus3.img

- los = lineage-17.1-20200713-nightly-oneplus3-signed.zip

- gapps = open_gapps-arm64-10.0-nano-20200715.zip

No, I did not check the validity of the flashed zips. Could that be a reason for the bootloop? For the error regarding no verity zip?

EDIT : I just checked the validity of the los zip. I will continue to check the validty of the others.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=10971269]LaDidac[/MENTION]:

Don't use zips that flash with an error!

Let's fix the bootloop before dealing with verity bit (search the thread for "safetynet", "locked bootloader" and/or "verity").

If you skip the format data step from the wiki page (for the record: you didn't follow the wiki! It's not helpfull if you state you've done so, if it's not true. This wastes your time as well as mine and Johann's.), you need to wipe data (this leaves /sdcard/ untouched). You can't dirty flash los on top of oos.
[OnePlus 3 & 3T Cross Device Development] LaDidac:
I didnt know that the no verity zip would give me an error. Apparently it worked for other people.

Just to clarify, I did format the data as mentioned in the wiki (Wipe, format data, yes). However, I did not format to EXT4 using TWRP because that isnt specified in the wiki. I also did the Advanced wipe, as mentioned in the wiki.

I totally understand what you mean and I agree. I have absolutely no intention of wasting your time. I dont want to waste anymore of my time, which is why I decided to finally bite the bullet and ask for help. Believe me, Ive tried figuring this out on my own and it's driving me crazy.

This is mentioned on the twrp page for oneplus 3/3t : "This device uses dm-verity! This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."

This is the reason I started looking in to the no verity option. Is it necessary to install a custom kernel? I tried searching for kernels for this phone, but they seems to be out of date, and I wasnt sure if that was a good step to take.

Edit: Also, my bootloader is unlocked.

Edit again : A success!!!! Lingeage installed! I followed the wiki page again, this time formating to EXT4. (Also, upon verifying the zips, I had realized that the gapps wasnt good, so I installed it again.) Flashed the os and then gapps, adb reboot.... waited several minutes thinking it was bootlooping again, then a miracle, lineage loaded!!

Thanks to all of you that took the time to answer my questions. I wholeheartedly appreciate it.

Out of curiosity, it is necessary to format to EXT4 in order for the process to work?
[OnePlus 3 & 3T Cross Device Development] :
This is complete nonsense for source build custom roms. Maybe it's true for oos, but I doubt that (I've been using oos with magisk, unlocked bl and no verity zip - at least with this setup it's also nonsense for oos).

As long as the bl is locked the verity bit isn't tripped.

The berity bit is tripped by an unlocked bl.

To boot with a locked bl the recovery partition and the boot partition needs to be signed with aosp verity keys (los boot image and curtent twrp images are cortectly signed, magisk since 20.3 resignes the boot image after altering, if it was previously signed).

The kernel is part of the boot partion; fstab is on the rootfs in the boot partition up to los-16.1. For 17.1 (system-as-root) fstab resides in the system partition.

Hopefully I havn't overseen an error in the two sentences from the twrp wiki. Most probably the wiki page was copied from an other device and nobody cares about.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
As I mentioned before it isn't neccessary to format to ext4, f2fs is totally fine and is working for los 17.

Your problem was 100% the faulty gapps package.

My next idea would have been too, that you only flash los and nothing (and really nothing) else.

The only problem left now is the verity warning screen at booting, am I right?

Jip, I also don't believe in telepathy. Just a coincidence based on our same technical knowledge (at least here, if it goes more in details in android, roms, los, etc. - you know definitely much much more ) that we had the same idea how to fix it and reading at same time (email notification) as you already wrote. still a funny joke : )
[OnePlus 3 & 3T Cross Device Development] LaDidac:
[MENTION=8423339]Johannes1098[/MENTION];83103523

Ahhh, this will teach me to regularly check the sums of files.

The screen that I get at booting is the warning that the bootloader is unlocked. It is a bit of an annoyance. Ill have to read about how to get rid of it (if possible).
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can only get rid of it by relocking the bootloader. And that also requires the boot and recovery images to be signed (which is the case for Los and OOS).

---------- Post added at 09:56 PM ---------- Previous post was at 09:41 PM ----------

Fyi, getting thrown back into TWRP is done by Rescue Party (https://source.android.com/devices/tech/debug/rescue-party). A search for that would have given you some hits in this thread.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
xda added ) to the link, so here again working https://source.android.com/devices/tech/debug/rescue-party

At least there is no dm warning screen at bootup, got this one at oos some years ago, this is very annoying.

The "bootloader unlocked" warning screen for me isn't a bad thing.

You have short keys to BL, Recovery, Shut down - and I'm not rebooting the phone every hour, so I doesn't see it that often.

The only way to get rid of it, is relocking the BL, as [MENTION=2911853]BillGoss[/MENTION] mentioned before.

But if you like to flash via fastboot time to time, it's not the most practical thing to relock it.. your decision.

I'm always checking the sums for los and gapps after download. It can happen (although the chance isn't that high) that a file gets corrupted. Checking the sums can save you quite some time checking why xyz isn't working (as we saw from you now...)
[OnePlus 3 & 3T Cross Device Development] :
Good to hear you succeeded!

About the unlocked bootloader; when you are sure you want to keep using LOS you could lock the bl again, otherwise I would recommend not to. Some background and instructions: https://xdaforums.com/showpost.php?p=82204597&postcount=710

About the formatting; it was not explicitly needed to format to EXT4, though it is still the most used and stable file system, especially in combination with custom Roms. As far as I know, every custom Rom can handle EXT4, other filesystems will not give you any noticeable benefits so I would still recommend going for EXT4.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=10971269]LaDidac[/MENTION], [MENTION=10511117]Johan2020[/MENTION], [MENTION=8423339]Johannes1098[/MENTION], [MENTION=2911853]BillGoss[/MENTION] and myself:

May I kindly rememnber to honor xda rule #1?

No single bit of information given to [MENTION=10971269]LaDidac[/MENTION] after this posting is new. It's all in this thread and will be found by the queries suggested. This includes a guide to relock the bl, pros and cons of locked bl and pros and cons of twrp and los recovery.

[MENTION=10971269]LaDidac[/MENTION]: I know it's a pain in the arse to search and read some threads because of redundancy and noise - but this thread is quite readable with only some redundancy. Use it and help keeping it this way, please. As you can easily see [MENTION=10511117]Johan2020[/MENTION], [MENTION=8423339]Johannes1098[/MENTION], [MENTION=2911853]BillGoss[/MENTION] and myself tend to answer questions though they were answered before...

Some references for reading as starting points (not blindly unkonwingly flashing) outside this thread:

https://xdaforums.com/showpost.php?p=78433987&postcount=3

https://xdaforums.com/showpost.php?p=78433989&postcount=4

https://xdaforums.com/showpost.php?p=83092591&postcount=134
[OnePlus 3 & 3T Cross Device Development] pro_drive:
I met silent alarm bug again. It is annoyed!

version: lineage-17.1-20200713-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] punio4:
I recently noticed that the Always On Display gets enabled/stuck sometimes, even though I don't have it enabled. Waking the device fixes it.

This hasn't happened until 2020629 or 2020713
[OnePlus 3 & 3T Cross Device Development] RKS96:
You can somewhat fix it by changing silent (AKA slider top position) with the profile you use the most! I am starting to think that this might be a hardware problem since it isn't profile related, but slider switch related (top position).
[OnePlus 3 & 3T Cross Device Development] 0anas0:
SOT

How much SOT are you guys getting on this? With normal (browsing, social media, mobile data, dual sim) usage without gaming?
[OnePlus 3 & 3T Cross Device Development] mvalda01:
With normal usage but only one sim - and no tweaks, I'm getting 4 - 4.5 hours SoT. Very satisfying.
[OnePlus 3 & 3T Cross Device Development] Nixeus2:
Hello guys, i'm using the Mad Kernel with this rom. No problem, no issu ! I just wonder if some use and if yes, do you use some apps to use profil in order use over gouvernor ? Thanks !
[OnePlus 3 & 3T Cross Device Development] :
Please read and respect the OP of this thread. Conversation, tips & tricks and support belong to the kernel's thread. Thanx in advance.
[OnePlus 3 & 3T Cross Device Development] maniacbb:
Hello guys i have still problem with GPS. I use app Endomondo for running but GPS don't work. I clear A-GPS data but didn't help. Any suggeston how to fix that ? Or i must wait untill the next update ?
[OnePlus 3 & 3T Cross Device Development] :
Happy to hear I am not the only one.

Could you try my gps.conf (rename attachment gps.conf.txt to gps.conf) and copy it to your /system/etc/gps_debug.conf and /system/vendor/etc/gps.conf just to see if it makes any difference. Not sure which one is used, did not test that already so copied it to both. Probably not all settings are hundred procent optimized but it seems to give much faster results for me. Just testing at the moment though... ;)
[OnePlus 3 & 3T Cross Device Development] Triggerfinger68:
Hi, I also have still problems with gps, please let us know If the tests are succesfull. I don't have much experiance with the solution you wrote, so could you please explain how I copy gps.conf to system etc? Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
If you look at the two files you'll see that gps_debug.conf has only comments in it. So that's NOT the one to change.
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Where to find call waiting option ? I do not find anything to activate as it is not activated by default. Also, the missed call notification on screen or indication is not available

Edit update: Sorted the issue now.
[OnePlus 3 & 3T Cross Device Development] :
You are probably right but as said I did not check that before, as we had some discussion before about gps.conf and/ or gps_debug.conf and I just wanted to be sure...

[MENTION=4073185]Triggerfinger68[/MENTION]; unfortunately seems not to help. First lock is taking about one minute when enabling location again after a day. So seems not the solution.

Will look into it further when I have some spare time.
[OnePlus 3 & 3T Cross Device Development] sobhan06:
Lineage donwloads detected as virus

Lineage ROM downloaded now is detected as a virus in my system now anyone else is facing the issue.
[OnePlus 3 & 3T Cross Device Development] Hellera:
I have never had this kind of issue with any other ROM's either... depends on your antivirus solution...
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Never had something like thjs, you sure you have downloaded from the right source.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Check sha
[OnePlus 3 & 3T Cross Device Development] :
Where is the detection originating from?

What malware/worm/virus/coding pattern is reported?

Interesting statement at the same information level as the original posting.

Additionally to:

Where is the detection originating from?

What malware/worm/virus/coding pattern is reported?

The most important questions are:

How did you solve/examine it, or have you ignored it? Which risk level was the reported malware/worm/virus/coding pattern? False detection?
[OnePlus 3 & 3T Cross Device Development] sobhan06:
https://ibb.co/sPtD9jC

In Brave browser and Firefox, I can see the warning, moreover, I just use the Windows defender nothing else as Antivirus software. This is the first time windows is throwing up something like this for Lineage from the download.

I downloaded it but stopped it taking further due to the warning, as I thought of reporting it in XDA first. ROM today's release
[OnePlus 3 & 3T Cross Device Development] knpk13:
Has that ever happened to you before while downloading LOS zips? Maybe you're getting that warning based on the .zip file extension.

Try using https://www.virustotal.com to scan the file with multiple different engines.
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
[MENTION=5091734]dianlujitao[/MENTION] The qcacld-2.0 driver seems to have compilation issues while performing "eng" builds.

Weird because userdebug builds are just fine.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Maybe userdebug builds don't use the compiler option to make those warnings errors?
[OnePlus 3 & 3T Cross Device Development] :
Which toolchain are you using? For gcc 7 or later you need to remove the unneeded definition or disable the warning. The older aosp shipped gcc toolchain has the unused variable warning disabled by default.

---------- Post added at 16:19 ---------- Previous post was at 16:14 ----------

I can't see the warning in firefox. It's not from win defender. My questions havn't been answered. A picture of "the file is dangerois" is no information. Win defender would have given information on it's finding incliding a kb link.

Before all my questions from my previous posting are answered, it doesn't make sense for me to participate to this conversation.
[OnePlus 3 & 3T Cross Device Development] mvalda01:
Latest build has a really nice battery life
[OnePlus 3 & 3T Cross Device Development] bugrahul:
Serious Microphone Issues

Hello, this is mmrahul on gitlab. I noticed that one time with the 20th July 2020 build, I had the microphone work perfectly, even after a Whatsapp call and all. Google assistant worked, recorder worked, audio messages worked for days. I thought the July 20th build finally fixed the issue. I had a good 3 day run until the anti-climax happened, when I ran out of battery and the phone died. After the next boot, the issue was back. Not sure what happened in that particular utopia boot session. I didn't bother logging anything either.

I am updating Issue #1805 after every new build update. My latest observation includes the fact that Gitlab Issues #1765, #1804, #1805, #2005, #2082, #2275 are all the same. The striking part is that these are all reported by different people for different devices. So it's definitely not a OnePlus 3/3T specific issue, but more of a LineageOS 17.1 issue.

It is a really annoying issue, considering everything else is almost pristine. I am posting here only because I got a response on GitLab to post about it here. However, I see that I am already included in the talks, awesome.

My weekly updates on Gitlab seems to only be heard by others in the same situation and not the devs. I am personally a very technical/scientific person, I enjoy tinkering, but this is not my area of expertise. I can understand well how things fit & work together. I'm trying to help narrow this problem down with my professionally astute observations. But I am not a programmer and do not follow the nuances of most SDLC processes, except the ones that concern my job. Though I have sought great advice from countless xda forum discussions in the past decade, this happens to be my first post ever. Great to join in.
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
No custom toolchain. The one included in the repo by default. I'm guessing it would be something on my build system's end if the problem doesn't occur with others building the ROM.

Could be, I will have to read through the makefiles. I assumed it would be the other way round lol :p
[OnePlus 3 & 3T Cross Device Development] bugrahul:
[MENTION=5091734]dianlujitao[/MENTION]

Could you please go through Issue #1805 on Gitlab for LineageOS? It's a real pain in the neck that happens everyday to many people and we're learning that this is not just a OnePlus 3/3T issue. There are logcats and many other informative comments about the situation from me & others there.

It's easily replicable. Just make a WhatsApp or Telegram call and wait a minute, then try using a recorder app/audio message on WhatsApp/record video on camera/ use Google Assistant with voice...and you'll see that the OS behaves like the app is accessing the microphone however, the microphone doesn't capture anything. All the clips will be silence. Google Assistant reacts like it's not hearing anything.

The fix is to restart and things work fine until the first WhatsApp or Telegram call. And the cycle repeats. Restart again. I reboot my phone 3 or 4 times each day due to this.

(I do not believe that this has anything to do with the Bluetooth audio and connectivity issues that was in discussion. I personally have not been driving much in the past few months due to the pandemic, but the little driving I did was problem free with regards to Bluetooth connectivity and audio, haven't used any headsets lately as I'm home all the time, but I can't imagine I'll have any issues the way things have worked out for me on this front)
[OnePlus 3 & 3T Cross Device Development] lapirado:
It's safe to dirty flash this over tugapower (17.1 too)?
[OnePlus 3 & 3T Cross Device Development] :
A dirty flash over another OS is NEVER safe.

Please do a clean flash when you want to swtch and safe yourself a lot of trouble ;)

---------- Post added at 11:50 ---------- Previous post was at 11:46 ----------

All LOS builds do have a great battery life. Issues are always because of installed apps surging, installation issues or a broken battery.

During usage is depending on what you are doing with your phone, but drain of LOS without Gapps and GPS is <1% overnight ;)
[OnePlus 3 & 3T Cross Device Development] :
Please help keeping this thread a pleasure to read by sticking to xda rule #1.

The OP clearly states:

Posting without reading/honoring the OP demonstrates bad manner.
[OnePlus 3 & 3T Cross Device Development] l3g1oN:
I started to have this issue since my phone got some lake water ...

(Plus the upper glue dissolved before, maybe there's some dirt inside)

Besides that, my touch freezes from time to time for some seconds (not the phone itself, buttons work. Waiting or on-off fixes it for some minutes or hours).

Does anybody have this to?
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
Can confirm the touch freeze issue. I enabled show taps and saw there's a random touch on the bottom of the display.