yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] tshredder:
Upgrade summary 15.1 to 16.0 on OnePlus 3T

I just upgraded successfully from 15.1 and though I'd post my summary. Perhaps it can save others some time finding the right links.

Thanks for an awesome OS, I love Lineage.

Background:

- OnePlus 3T

- LineageOS 15.1 official

- Encrypted with pattern unlock at boot

- Upgrade without loosing any data

Download:

- Download latest firmware from github.com/nvertigo/firmware-3t

- Download twrp 2.3.2-10 from link in header of this thread, androidfilehost.com/?fid=1395089523397907195

- Download GApps (9.0, ARM64) from wiki.lineageos.org/gapps.html

- Download addonsu 16.0 from download.lineageos.org/extras

- Download latest LineageOS 16.0 from download.lineageos.org/oneplus3

Install:

- boot to recovery and flash latest firmware from zip

- reboot and verify that all is working

- boot to recovery and flash latest twrp image to recovery (install->install image)

- reboot and verify that all is working

- boot to recovery

- format /system (wipe->advanced wipe in twrp)

- flash LineageOS 16.0, lineage-16.0-20190322-nightly-oneplus3-signed.zip

- flash GApps, open_gapps-arm64-9.0-stock-20190323.zip

- flash addonsu-16.0-arm64-signed.zip

- wipe cache/dalwik

- reboot and verify that all is working

(takes a long time, like 10 minutes, the first time to reboot after upgrade)

(on first boot touchscreen takes time to wake up, so it takes a few seconds before it works to draw the encryption unlock pattern)

- OTA updates does not work for me. I have to install manually from twrp after exporting the update from Updater.

- Launcher is reconfigured so I have to add all my widgets and app folders to the launcher again. This is the only work I had to do after the upgrade.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About OTA Updater:

==> https://xdaforums.com/showpost.php?p=79172768&postcount=1383

==> https://xdaforums.com/showpost.php?p=79181764&postcount=1443

Please, if you have time, could you confirm the issue below? Thank you in advance.

First, perform a Nandroid backup before testing.

Second:

- Go to Settings … Networks & Internet … SIM cards

- Select SIM slot 1 or 2 ... but use only one SIM card ... not two.

- Change the colour of SIM card … Confirm by OK

- Go back to home page of Settings

- Restart

Question: is the PIN code input screen enabled at restart?

Related post : https://xdaforums.com/showpost.php?p=79177084&postcount=1418
[OnePlus 3 & 3T Cross Device Development] WookieCookie:
Hey,

I discovered that the ambient display only works properly for me if both ambient display and pop-up notifications are enabled. If I switch off pop-up notifications, the ambient display won't turn on briefly when I get a notification. Seems like a bug to me...

Did anyone else observe this behaviour?

BTW I clean flashed the ROM yesterday, so that didn't make a difference.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Update: I realized that I could have the very same issue on a Huwaei M5 tablet, running the Huawei Oreo flavour, bootloader still locked and unrooted . Being a 10.8" tablet with a battery twice as the OP3T one and never running hot, I didn't have any clue about this issue, just a suspect after my experience with the OP3T.

I checked and captured the CPU usage (via adb shell top) before and after changing the Assistant language from my own native language to English: the user CPU went from 159% (with Audioserver and other "unusual" processes being on the top of the top processes list) to 21%.

So it seems this issue is totally unrelated to LOS or Oneplus and, being "just" a Google app bug, it could be widespread among non-English speaking Android users.

Moreover, the increased restrictions to easily check the CPU usage on unrooted devices (because of justified security reasons, I guess) do not help to investigate and being aware of such issue.
[OnePlus 3 & 3T Cross Device Development] felipefp:
Sorry if this has been discussed before, I searched the thread and found nothing. Is the camera2 API broken? I tried several manual camera apps and none of them let me adjust shutter speed reliably, or had weird bugs. I did a clean flash.
[OnePlus 3 & 3T Cross Device Development] kpmohamedhussain:
Same issue here, found any fix??
[OnePlus 3 & 3T Cross Device Development] ZVNexus:
I assume its a user issue. On a build from March 25th and no issues.
[OnePlus 3 & 3T Cross Device Development] Stier16:
I have been on each of the nightlies and have had no issues. I think having a log would help the experts here to pinpoint what the issue is.
[OnePlus 3 & 3T Cross Device Development] jerryhou85:
Dear all,

I have to remove some off topic posts to keep this thread focused. Please remember that users here are all real life human beings from different parts of world, so please post a clear message and be kind in your comments.

A little rule refresher:

2. Member conduct. 2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules.

3. Post using a clear and descriptive subject and message.

You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.

Should you see any violation to our rules, please report to mod team immediately. Thanks for your support.

Regards

Jerry

Forum Moderator
[OnePlus 3 & 3T Cross Device Development] Milka78:
Hi folks,

I would like to switch from unofficial to official nightly builds.

But dianlujitao states in his last changlelog:

Is there still anything missing in the last official builds (20190325) in comparsion to the last unofficial (2019.3.1)?

Milka
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
See this post ... https://xdaforums.com/showpost.php?p=79163821&postcount=1353

Try the latest official build, you won't be disappointed.
[OnePlus 3 & 3T Cross Device Development] npeersab:
is there any option to change the position of Network traffic monitor?
[OnePlus 3 & 3T Cross Device Development] helderfp:
Closed beta pie for op3/t leaked, cam we use the firmware from that?
[OnePlus 3 & 3T Cross Device Development] :
Closed beta is not public, but closed. Every participant signs an nda and is not allowed to give the rom or parts to the public. In quite some otjer threads xda moderators have explicitly explained, that it's prohibited to share the rom or parts of it.
[OnePlus 3 & 3T Cross Device Development] camdadeye291:
I get what you are saying but the unofficial rom is not updated as regularly as the official. I was thinking the unofficial was something like the developers recommended build for stability and the official is cutting edge, fringe tech.

Can you help us out here [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The unofficial version was the precursor to the stable/official version. You'll notice that there's been no work done on the unofficial version since the official version went live. Also, the title of this thread changed from [unofficial] to [official]
[OnePlus 3 & 3T Cross Device Development] michie:
[Deleted]
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm talking about the unofficial Los 16 that dianlujitao produced (this thread). There's is no update since the Los 16 official came out - check out https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
[OnePlus 3 & 3T Cross Device Development] Dirk:
Alpha->Beta->Stable

Unofficial->Official

A New Hope->Empire Strikes Back->There were no more Star Wars movies after this except for a Holiday Special and some furry porn.
[OnePlus 3 & 3T Cross Device Development] helderfp:
As sayd on rule 12 of forum and sayd by a moderator we can share leaked links.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
A warning on leaked Pie builds

As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.

After several experiments I finally figured out the cause:

If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.

I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Would your build + Pie Firmware install okay if /Data had been formatted first to remove encryption, prior to install?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I would expect every custom ROM flasher enthusiast to always keep in mind that flashing custom ROMS come with the risk of data loss. Especially in the case of these leaked beta builds, the non-developer users should not rush to flash.

Also, a question for you [MENTION=5091734]dianlujitao[/MENTION] , Would this ROM work on unlocked bootloader if it wipes internal storage and re-encrypt it? I can take a backup and try flashing it this weekend but if this fails to boot on an unlocked bootloader, I don't any reason to rush and would rather wait for official ROM release.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
BTW I shared this on OP forums and the OP stuff confirms this as a "bug". The SW team is aware of it and is working on to fix it. :) :good:
[OnePlus 3 & 3T Cross Device Development] michie:
My bad (again).

Thanks for the heads up ?
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Are you one of the closed beta testers? And can you provide the link where OP confirmed this "bug"?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello

No, I am not a closed beta tester. I posted dianlujitao's warning to the users there flashing closed beta build. One OP staff member replied and said the SW team is aware of this bug and is fixing it.
[OnePlus 3 & 3T Cross Device Development] camdadeye291:
Thanks [MENTION=2911853]BillGoss[/MENTION] is it possible to update to official from unofficial or should I clean the slate?
[OnePlus 3 & 3T Cross Device Development] ivanich:
I'm using this script https://wiki.lineageos.org/signing_builds.html

Simply download script from https://raw.githubusercontent.com/LineageOS/scripts/master/key-migration/migration.sh

and follow Los guide.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The recommendation is to do a clean (wipe data and system) install, but there's no harm in trying a dirty install. You may find "bugs" with a dirty install which are not present with a clean one.

Just make sure you've backed up your current setup.

I can't comment on migrating keys (see post by [MENTION=2517790]ivanch[/MENTION]) as I've never done that.

I did a clean install because I already had issues on the unofficial version as a result of dirty flashing since the first unofficial release.
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Alright, can you please provide a link? I couldn't find this post. Moreover, there are morons filled on the OnePlus forums who are there to reply to each & every post with their high level sarcasm. OP Forums has been a disaster since the CB leaked...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
We really shouldn't be talking about OOS betas in this thread as it's off topic unless dianlujitao produced a Los 16 version based on the OOS update.

In the meantime feel free to talk about the beta on this thread https://xdaforums.com/oneplus-3t/how-to/android-p-official-coming-to-op3-t-t3822982
[OnePlus 3 & 3T Cross Device Development] DarkSJ1998:
Sorry my bad [emoji14]

But the discussion was started after a warning was issued by dian regarding the OOS Pie leaked CB. Sorry again as I went a little bit off topic :)
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
What is that? An upcoming April fool?

Should we stop installing nightlies until 3rd of April? :rolleyes:

Last years April fool was a really bad and not funny thing.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
I found a weird issue that maybe is just affecting me, since I don't see it mentioned here or in a bug report on gitlab:

1 - go to a scrollable list (the system settings list for example)

2 - then press the power button twice (so you will turn the screen off and back on)

3 - check if the scrollable list still works

4 - again, press the power button twice (so you will turn the screen off and back on)

5 - at this point the scrollable list become unresponsive and does not scroll anymore, while other GUI elements are still working (the search box dialog on top in the system settings list, for example)

Edit: "power buttons instantly locks" should be disabled and "automatically lock" set to "5 seconds" or higher
[OnePlus 3 & 3T Cross Device Development] Rittmeister123!:
Can confirm, UI freezes for ~2sec
[OnePlus 3 & 3T Cross Device Development] Uqbar:
Not here!

I am on 190327 nightly but I have "PIN unlock" in place.
[OnePlus 3 & 3T Cross Device Development] ciarpame:
It happens only if "power buttons instantly locks" option is disabled and "automatically lock" is set to "5 seconds" or higher (my choice is 30 minutes).
[OnePlus 3 & 3T Cross Device Development] John2146:
Shuld we lock bootloader from next build?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Do you want a bricked phone?

Sent and edited from my Pixel 3 using XDA Labs
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Same issue on my side.

****

Please, if you have time, could you confirm the issue below? Thank you in advance.

First, perform a Nandroid backup before testing.

Second:

- Go to Settings … Networks & Internet … SIM cards

- Select SIM slot 1 or 2 ... but use only one SIM card ... not two.

- Change the colour of SIM card … Confirm by OK

- Go back to home page of Settings

- Restart

Question: is the PIN code input screen enabled at restart?

Related post : https://xdaforums.com/showpost.php?p=79177084&postcount=1418
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/245235

Does this remove the "your bootloader is unlocked" message on device boot ? I was told that wasnt possible cause it was embedded in the qualcomm chips
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Thank you for checking

Looking at the related posts, I understand that the issue is about the SIM pin code. I always had issues with SIM pin code and LOS (and CM too) and now the first thing I do when I have to use a new SIM card is to remove the PIN (and the last time I was unable to do it with LOS15.1, had to use an iPhone) and rely on the system PIN only (with "secure start up" enabled), I think it's safer.

If I understand the related posts, I could end up in a dead end white testing the issue, and the only way out would be a nandroid restore. I will try to check the issue in the weekend, when I have more time to deal with backups and restores.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Does it relock the bootloader if you flash the leaked build with a unlocked Bootloader?
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Thank you for checking, for me UI freezes forever, on your device does scroll works again after two seconds?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Build 0328: successful update via OTA updater.
[OnePlus 3 & 3T Cross Device Development] :
+1

Remark: today's build size increased about 37mb ...
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I've gotten used to exporting the update from the OTA and manually reboot into recovery and flashing because I had to flash magisk afterwards to keep root, but today, for the first time it on updating, it looks like the addon.d script actually ran itself and restored magisk when the update completed. Huzzah! Is this something that was changed in 3/27 or 3/28 nightly?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
==> https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/245235
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Is that what allows the addon.d scripts? If I'm not mistaken though, magisk patches the boot.img and would be a bad idea to use with a locked bootloader. Correct?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Yes.... unless I'm mistaken.
[OnePlus 3 & 3T Cross Device Development] helderfp:
This means that we can lock bootloader with lineage instaled?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I think that that's what the commit is saying. But it's also saying it's not recommended: "This doesn't mean using custom ROMs with locked bootloader is suggested."

Also, as [MENTION=2954806]counterfeit187[/MENTION] mentioned, Magisk modifies the boot image so there's a question as to whether you can lock the boot loader if you're using Magisk or custom kernels.

I'm also wondering if it has an impact on TWRP. Does it also need to be signed?

I would like [MENTION=5091734]dianlujitao[/MENTION] to comment on this.
[OnePlus 3 & 3T Cross Device Development] John2146:
Oh a good answer and not a flame. Thank you sir :victory:

PS. Yes I'm looking at you [MENTION=6849132]laupuy[/MENTION]
[OnePlus 3 & 3T Cross Device Development] helderfp:
As i do not use magisk i ask if it is safe to lock bootloader using lineage, and to would like to know the impact on twrp.

And thank you for your answer.
[OnePlus 3 & 3T Cross Device Development] :
I'm throwing a not-so trusted source here, based on experience and limited knowledge

Locked bootloader means you will have as far as a temporary root, it will be gone in the next reboot

With Magisk in this current state, and somehow you are able to install it on top of locked bootloader, i'm sure you will never even see a lockscreen

And i'm sure TWRP functionality will be limited in locked state

This locked bootloader with custom rom is just for people who doesn't feel happy with their OEM rom

and maybe it also benefit some groups (more likely dealers) who just wanted to milk as much money as they can by selling a modified phone included adware as system apps
[OnePlus 3 & 3T Cross Device Development] OTAx1:
OTA 0328 failed; update magisk to 19.0, retry OTA 0328, failed.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Build 0328: successful update via OTA updater.

==> with LOS addon su
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Which one? Link?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
addonsu-16.0-arm64-signed.zip

https://download.lineageos.org/extras
[OnePlus 3 & 3T Cross Device Development] Rittmeister123!:
Exactly!
[OnePlus 3 & 3T Cross Device Development] ciarpame:
Does your scrollable list freezes forever or just for a couple of secs, as reported by Rittmeister123?

Thanks
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Forever on my side.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Mine freezes for a second or so, then back to working properly. I'm still on the 23rd of this month's build though.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Magisk modifies boot and resigns it with testkey which is different from verity key so there'll be a 5s warning on boot when bootloader locked, it still boots.

TWRP needs to be signed as well.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I was wrong. It seems that addon.d script does not run if you use OTA to install, but does if you export and manually reboot recovery and flash.
[OnePlus 3 & 3T Cross Device Development] An68:
Hi , I'm update to lineage 15.1, clean installation how the OP, last Magisk, last firmaware 5.0.8, but I can't recive call or message, the phone is always off, OTA works, please help me. It's works changing network from automatic(4G)to 3G, why?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Try to put the SIM card in the other SIM slot.
[OnePlus 3 & 3T Cross Device Development] OTAx1:
OTA update stills fails.

-wipe caches, manual install 0328 build, then 0329 OTA update = fails

-----------------------------------------------------------------------------------------

OnePlus 3T / FW 5.0.8 / TWRP 3.2.3-10 / cache & data on ext4 / official LOS 16.1 / encrypted data / Magisk 19.0 / official LOS addon SU
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Magisk 19.0 or official LOS addon SU ?

cache/data as ext4 or f2fs ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think, both. :eek:
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
[MENTION=1763460]Dirk[/MENTION]

:D

[MENTION=9794780]OTAx1[/MENTION]

Please, use only one SU.

Uninstall Magisk 19 (Latest Beta) via Latest Uninstaller (https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

Try again OTA updater

Note OTA updater fails if cache/data as f2fs (https://xdaforums.com/showpost.php?p=79172768&postcount=1383)
[OnePlus 3 & 3T Cross Device Development] Calum 2:
I'm not getting text notifications right away, often times they only come in when I open the phone. Presently I'm on the nightly from the 23rd, using the stock messaging app. Is there a setting I'm missing, or is this a bug?