yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] alleykat2561:
For the record, what was the last nightly that didn't expect you to be on the latest firmware?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
lineage-16.0-20190615-nightly-oneplus3-signed.zip

==> https://www.lineageoslog.com/16.0/oneplus3 or https://lineageos.mirrorhub.io/full/oneplus3/

[MENTION=1763460]Dirk[/MENTION]: Seems to be 50/50. Eric was unlocked and encrypted but needed to clean flash.

==> https://xdaforums.com/showpost.php?p=79737571&postcount=2385
[OnePlus 3 & 3T Cross Device Development] Dirk:
Misread that, thanks.

I'm feeling pretty pleased that i haven't encrypted my phone now. The firmware update should work without issues.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Migrate to 9.0.3 fw via a clean install with backups for the noob

Step 1: Backup

Boot in TWRP and perform a Nandroid backup

Copy all data from External storage to PC (your backup)

Optional: Boot to System and Setting > Google > Backup > Back up now (Google backup)

Optional: use Migrate app to backup your app and sms (play store - see my signature)

Step 2: Copy the following files to your PC

Latest TWRP: https://twrp.me/oneplus/oneplusthree.html

Download official 9.0.3 fw:

OP3: https://www.celsoazevedo.com/files/android/oneplus3-modem-firmware/

OP3T: https://www.celsoazevedo.com/files/android/oneplus3t-modem-firmware/

Latest build: https://www.lineageoslog.com/16.0/oneplus3

Gapps (ARM64 pico or nano … only): https://opengapps.org/

LOS SU addon (optional): https://download.lineageos.org/extras

Step3: Time for flashing zip fles

Boot to TWRP (optional: flash TWRP 3.3.1-0 and reboot to TWRP)

Wipe all partitions (FULL WIPE: cache/Dalvik/system/data/external storage)

(Optional (if encrypted): advanced wipe ... format data by changing file system as ext4 or f2fs)

Reboot to TWRP

Copy 9.0.3 fw from PC to external storage

Flash 9.0.3 fw

Reboot TWRP

(if userdata is not decryptable anymore, hit "cancel"

wipe system, cache and dalvik

advanced wipe ... format data by changing file system to remove encryption

reboot to TWRP)

Copy from PC to External storage and flash the latest build + gapps (pico or nano ... recommended !) + su (if needed)

Reboot to system

Optional: Restore your Google backup from the cloud when you activate your Google account

Copy all data (your backup) from PC to External storage

Optional: flash Migrate zip in TWRP to restore settings of your apps

Enjoy …
[OnePlus 3 & 3T Cross Device Development] gianni281:
Is anyone able to confirm whether the ril/ims issues have been resolved on the latest build? Last time I tried flashing the build from the 16th had issues with SIM/data services and phone app crashes/reboot to recovery during initial setup (clean install)
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Thanks!

And you should not re-enable encryption after updating am I right ?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Yes, you can re-enable encryption after updating ...
[OnePlus 3 & 3T Cross Device Development] :
You can always easily check in gerrit - it's just a click away:
[MENTION=5091734]dianlujitao[/MENTION] doesn't like https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250329 - that's why it is abandoned. https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250376 is merged by now (9:52 UTC+2).

If you check the builds on gitlab: https://gitlab.com/LineageOS/builder/android/-/jobs/233284185 you can see that the next build is still pending. Now you can conlude, that the next build will have the fix.

...and after userdata is encrypted, set a passphrase for secured boot! (credits: [MENTION=1763460]Dirk[/MENTION] aka Statler ;) )
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
ANT+ will be back in the next build (20190618)

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250375

Thanx [MENTION=5091734]dianlujitao[/MENTION]

Edit: The commit I've mentioned doesn't bring back ANT+, but updates the present ANT+. ... Credit : [MENTION=4405529]nvertigo67[/MENTION] (see the following post)
[OnePlus 3 & 3T Cross Device Development] :
ANT+ is there since the native pie bl8bs update: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250109

The removal of ANT+ has been canceld: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/245236

The commit you've mentioned doesn't bring back ANT+, but updates the present ANT+.
[OnePlus 3 & 3T Cross Device Development] gianni281:
Thanks, appreciate the heads up and will check both Gerrit and Gitlab going forward for the status of builds/updates on fixes
[OnePlus 3 & 3T Cross Device Development] ciarpame:
What is the more compatibile/canonical/trouble-less format between the two for user data partition?

Why not just disable screen lock before beginning the whole process?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I tried both (ext4 & f2fs) and I didn't really see the difference. Now I am on EXT4.

Yes, you can simply disable the screen lock beginning the whole process.

Edit: See an old post and the following ones.

==> https://xdaforums.com/showpost.php?p=79180137&postcount=1431
[OnePlus 3 & 3T Cross Device Development] knpk13:
I checked Gerrit and saw dianlujitao cited a bunch of errors in the comments as the reason to not use this commit and use a different one. But I didn't really understand what it meant. Can you explain why he didn't like this solution?

*I read the discussion in the NLOS thread too
[OnePlus 3 & 3T Cross Device Development] :
The errors are from the log in the nlos thread. These errors are fixed with https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250329 as well as with https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250376 .

[MENTION=5091734]dianlujitao[/MENTION]: where did you get the LA.UM.7.5.r1-04000-8x96.0 prebuilts from? I've searched source.codeaurora.org because of the version string, but havn't found anything, maybe I've a brainlock here.
[OnePlus 3 & 3T Cross Device Development] rlees85:
If your running LOS don't let your phone sleep in airplane mode (unless you like kernel panic, very flat battery and no alarm in the morning).... maybe the new RIL stuff fixes it
[OnePlus 3 & 3T Cross Device Development] haelmchen:
with new blobs and new firmware, will slow-motion camera work now?
[OnePlus 3 & 3T Cross Device Development] :
Is this just a bit mocking on los, or do you want to help ironing out an issue?

If the first: I hope you feel better now.

If the latter: please try to get the content of /sys/fs/pstore one the very next reboot (if i.e. the kernel panic results in a rwsue party, save 0store from within the recovery; if you boot to system from recovery pstore will have the dmesg from the recovery boot, not frommthe kernel panic).
[OnePlus 3 & 3T Cross Device Development] Imnoa:
There's a magisk module that makes slow motion camera work called Oneplus 3/3t slow motion fix.

https://github.com/Magisk-Modules-Repo/op3slowmofix

Works fine for me
[OnePlus 3 & 3T Cross Device Development] rlees85:
No, not mocking LOS. I'm very appreciative of all the LOS developers and OnePlus 3 is very lucky to have some great supporters also. I've donated to LOS a few times now.

I am just weighing in on people who are having the "to upgrade or not to upgrade" debate.

I've gone back to stock now, I'm too old and have too many responsibilities for an unstable phone (though I already miss LOS features). Sorry I was not aware of the /sys/fs/pstore trick, otherwise I would have done it and reported it.

Its very easy to re-produce. Turn on airplane mode, wait ~30 seconds for screen to go black, wait ~30 seconds and the white led will light up. At this point phone is dead and only way to turn off is long-press power button.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No such issue on my side (I waited 4-5 minutes)... and I'm also too old and have too many responsibilities for an unstable phone... ;)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I tried the same on NLOS-16.0-20190616. Also no bug reproduction.
[OnePlus 3 & 3T Cross Device Development] :
Tried that three times. No sweat at all.

I'm using ambient display, but have AOD disabled (first run). The second time I've tried with AOD on (expectable, since AOD avoids deepsleep). The third run was with ambient display completely disabled.

I'll switch to airplane mode over night, and report back tomorrow.
[OnePlus 3 & 3T Cross Device Development] haelmchen:
update for people who are about to upgrade their firmware.

my setup: BL unlocked, decrypted device

I just flashed the new firmware, wiped dalvik/cache/system and flashed the latest rom. All works fine. No data was lost
[OnePlus 3 & 3T Cross Device Development] mumapizza:
I have my phone in airplane mode every night and never had issues with alarm clock or any other issues whatsoever. Maybe a bad app is causing your issues
[OnePlus 3 & 3T Cross Device Development] pro_drive:
I can confirm SIM/data works on build of 20190618
[OnePlus 3 & 3T Cross Device Development] :
I tried airplane mode the first time. After [MENTION=892424]rlees85[/MENTION]'s report on airplane mode, I've used an backup alarm clock.Sadly, I've forgotten to adjust to dst - so los saved my day... :)
[OnePlus 3 & 3T Cross Device Development] Subho1999:
Since the past several builds I've noticed that Google Assistant has stopped working for me and instead the Google app opens up (with Google feed and search bar on top)

I generally clean flash. From 0608 build and all the subsequent LOS builds that I've tried, Google assistant simply won't open. On long pressing the home button (the shortcut is present, I've checked) the Google app opens up instead of assistant. I've downloaded the assistant app from play store (that's supposed to be a shortcut to assistant) also opens the Google app.

My flash procedure is same as always for clean flashing (wipe system, cache, dalvik, data) flash ROM, Gapps, Magisk.

While setting up the during the first boot after clean flash, the assistant set-up page does open (it shows "assistant already recognises your voice")

It happens with both pre-pie fw and post-pie fw builds. So i don't suppose that's the problem here.

I checked with other AOSP and LOS based ROMs, there isn't any issue with other ROMs just LOS, by the looks of it.

I've tried almost all of the settings options available in the Google -> Assistant section. Any help will be highly appreciated. Thanks
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Pico or nano Gapps ? ... Maybe, install Google Assistant.

Please read this post ... https://xdaforums.com/showpost.php?p=79557704&postcount=2047
[OnePlus 3 & 3T Cross Device Development] rlees85:
Right well I owe a lot of you an apology I think for wasted time. I have been running 9.0.3 completely stock with locked bootloader and everything and still have exactly the same issue.

There must be something about my device that does not agree with these new firmwares unless I've got a hardware problem that just happen to develop when I first upgraded the blobs. I have EDL'd back to 5.0.8 and will run the LOS 15/06/2019 nightly until I replace the device. Either way its a OnePlus issue not a LOS one. Again apologies.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I got leaked BSP source
[OnePlus 3 & 3T Cross Device Development] me.home:
Did you use the orig. Firmware or oxygenos-9.0.3-bl-km-5.0.8-firmware-3T ?

I had to revert back from 9.03 to 5.08 on my open BL+encr. 3T.
[OnePlus 3 & 3T Cross Device Development] Dirk:
He was unencrypted. You were encrypted. Results match expectations.

Eric_Lev posted a method whereby you could possibly decrypt your phone without Data loss. From there you could dirty flash Official 9.0.3, update ROM and then re-encrypt. Read back a few pages for his guide to decrypt.
[OnePlus 3 & 3T Cross Device Development] rg_gapa:
"Disable lockscreen, then TWRP backup, then wipe everything, then TWRP restore" procedure to remove encryption without losing data is pretty well known at Android forums but somehow I can't find information is it really recommended and trouble free method.

What makes me doubt in it is a hunch that some files (system settings for example) related with previously encrypted filesystem might be present (but they should not be) at some partition after restoring the backup.

Does anyone has any clue about presence of files like these that might make trouble and should be deleted or modified?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
He who doesn’t fail, doesn’t try...
[OnePlus 3 & 3T Cross Device Development] :
If you've never bricked a device, you havn't flashed hard enough...

Flash hard!
[OnePlus 3 & 3T Cross Device Development] Flippiej:
Rescue party loop.

I've just got a rescue party TWRP loop after using the updater to go from a clean 16-6 build to 19-6. (TWRP 3.3.0-1, Opengapps nano, Magisk 19.3, OOS 9.0.3 FW, encrypted, open BL)

Tried dirty flashing back to my old build, with or without Magisk (although it automatically flashes it anyway), installing TWRP 3.3.1-0 and flashing both today's build, yesterdays and 16-6 again to no result.

I've attached a log from TWRP but I don't know if you can get anything useful from it.
[OnePlus 3 & 3T Cross Device Development] :
Did you change the fw from 5.0.x to 9.0.x?

If so, boot to twrp, flash twrp 3.3.1-0 and reboot to recovery. Format (not wipe!!!) data. Install rom, gapps and magisk from an usb stick, or transfer the zips with adb push to /cache.
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
what about fw?

Is it not needed after formatting before the ROM flash or fw is inbuilt in lineage ROM?
[OnePlus 3 & 3T Cross Device Development] nurlan555:
Can you do rom via fastboot?
[OnePlus 3 & 3T Cross Device Development] :
Why do you think that?

If you read the OP or think about unification (one zip for different models, needing different firmware), you'll find that there is no fw included in the rom.

Try to be as accurate as possible in your questions. Many questions answer them self, if asked precisly. In this case:

If the userdata partition (/dev/block/bootdevice/by-name/userdata) is formated, will this effect the fw partitions like modem (/dev/block/bootdevice/by-name/modem)? I'm sure you can answer that yourself.
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
I am not so knowledgeable like you and I did not understand about what you said "If the userdata partition (/dev/block/bootdevice/by-name/userdata) is formated, will this effect the fw partitions like modem (/dev/block/bootdevice/by-name/modem)?"

I thought formatting the device format everything in the phone including modem but as I am understanding from your post that after formatting only user data is deleted but modem is reserved. Correct me if I am wrong.

after this discussion I am curious to know that is this command "fastboot format userdata"

will delete both the modem and userdata.

in that case has it become necessary to flash firmware. Am I right? Guide me please.
[OnePlus 3 & 3T Cross Device Development] mesziman:
Does that leak this regularly?
[OnePlus 3 & 3T Cross Device Development] :
If you don't understand the concept of partitions, and don't understand, that only partitions can be formated, and don't see that userdata partition is a different partition from modem, I can't help you.

This could relate to a lack of reading.

If you don't know, that you can't format "the device", but only partitions, I can't help you.

This could relate to a lack of reading.

If you don't understand that "fastboot format userdata" formats the userdata partition and not the modem partition, I can't help you.

This could relate to a lack of reading.

Considering that you've run into trouble because you've updated your firmware without any preperation and that you've run into trouböe, which is described and discussed many times in this thread, I can't help you, because this is definetly a result of lack of reading.

Most important: https://xdaforums.com/announcement.php?a=81 especially the first rule.

None of the above is secret knowledge. It's all in this thread and the official twrp thread.

Your last posting suggests - at least - three possibilities:

You are trolling (by far most probable). In that case: congrats you really fooled me. We all laugh for 30 seconds, because I blindly steped in the trap. Good job!

You are just unwilling to read. In that case let's stop here, because the communication in a forum relies on reading before posting. This is also a rule you've accepted, when signing up to xda: https://xdaforums.com/announcement.php?a=81

You lack the cognitive abilities to search, read and understand. In that case I strongly recommend returning your device to stock and never touch a custom recovery again.
[OnePlus 3 & 3T Cross Device Development] Flippiej:
I already changed the firmware before my clean flash to 16-6, so I didn't need to repeat it for the updater to 19-6.

I didn't try the format option, but if it happens again I will ? I went for the wipe options, which didn't do much and a clean install again to get it working. Thanks for your reply.
[OnePlus 3 & 3T Cross Device Development] sandeep_kumar:
Instead of describing so much that you cannot help me, you may leave a website link where the information can be gone through.

Any way thanks for the quick reply and I will gather the knowledge on internet about everything.
[OnePlus 3 & 3T Cross Device Development] :
That's why I started with "if so"... If you have done the fw change and it was already running with 9.0.3, you can forget everything after "if so"... Then it's the ota bug (widely discussed some pages back): just manually flash the updated zip.

---------- Post added at 11:17 ---------- Previous post was at 11:06 ----------

I was sure you are able to find "this thread" and "the official twrp thread" yourself...

When explaining, why I cant't help you, I've given important information. I.e.:

This means: you can't format "the device" but only partitions.

This means: "fastboot format userdata" formats the userdata partition and not the modem partition.

I suggest you reread my last posting.
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
You're holding a Linux system in your hands, there's plenty of documentation you can Google for. Just search for a noob guide, that should tell you all you need to know about it.

Cheers

Kurt
[OnePlus 3 & 3T Cross Device Development] 666biker:
hello, which exactly 9.0.3 firmware for 3T you are using? I have installed 9.0.3 and fingerprint not work. any idea how to fix it? I am on latest LineageOS 16 nightly version. thx

EDIT: works with oxygenos-9.0.3-bl-km-5.0.8-firmware-3T.zip
[OnePlus 3 & 3T Cross Device Development] bian_ki:
In order to fix fingerprints I had to delete all of these files:

/system/data/locksettings.db
/system/data/users/0/fpdata/user.db
/system/data/users/0/settings_fingerprint.xml
[OnePlus 3 & 3T Cross Device Development] 666biker:
correct, after installing new firmware I also deleted locksetting.db because of PIN was not accepted.

another question, it is possible somehow to see ringer volume during adjusting after this new update? (narrow is visible to show other levers) but exist some way to see ringer volume as default? button mapper not works after this update for me. thanks
[OnePlus 3 & 3T Cross Device Development] Dirk:
Mission accomplished. Nice!

Thanks for the guide. :good:
[OnePlus 3 & 3T Cross Device Development] :
Thank you for this great guide!:good:

[sarcasm]

Do you say some reading and thinking about the starting point and the the end point of the journey combined with a plan to go that way, helps to save your data? Strange and surprising...

[/sracasm]

Again: great job!

[MENTION=5091734]dianlujitao[/MENTION]:

May I suggest to link that one in the OP - at least temporary?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Reading and understanding a thread... It always pays off!

Thank you M. [MENTION=8423339]Johannes1098[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Question:

NFC doesn't work anymore. It's greyed out in Settings and in StatusBar you cannot click on it.

There were changes on 1606 build.

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/244333

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/244332

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/244331

Does anyone else have this problem?
[OnePlus 3 & 3T Cross Device Development] Mustkeg:
Same here. Can't toggle NFC active...0619 version.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No such issue on my side (see attached screenshot).

Edit: Build 20190621 - LOS SU addon
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Are you sure you don't have the NFC SIM Magisk module installed or something? That module broke NFC just like you describe it, grayed out. Working without it here on 0619.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Zelete:
Yep

Although I only have it on custom kernels. I flashed the new modem firmware after it was required and did a clean install. With the Lineage kernel the switch is working (just flashed the newest build).

The switch isn't greyed out here though, Pay keeps asking me to turn on nfc and the switch is just acting weird also...

Other than that my SELinux also has a problem. Can't get it set as enforced.
[OnePlus 3 & 3T Cross Device Development] :
Quite useless. Many causes for broken nfc are filtered out, like missing libs or sepolicy denials, to name only two.
[OnePlus 3 & 3T Cross Device Development] Mustkeg:
Post can be deleted, I'll try some other stuff first. Sorry for bothering you with useless logs.
[OnePlus 3 & 3T Cross Device Development] Rated R:
Same issue with SELinux
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
With the idea that the issue happens on other kernels - and I have the stock kernel - I removed Magisk.

Because it patches the boot.img and I thought it could be the issue

( [MENTION=4415965]Mustkeg[/MENTION] has got the issue and Magisk - [MENTION=9708417]Eric_Lev[/MENTION] hasn't got the issue with the LOS SU Addon)

I formatted /system and installed LOS 20190620 with OpenGapps (Super with own config)

But the error still exists - so it's not Magisk relevant I think..

I'll capture a complete logcat and provide it here...

Edit: Added screenshots from the settings app and status bar (in German - hope it's ok for you :) ) and a logcat.
[OnePlus 3 & 3T Cross Device Development] mr-cook:
Working fine for me on latest build.
[OnePlus 3 & 3T Cross Device Development] wistlo:
Super OpenGapps might be the issue. Best practice now is to use only Pico or Nano, so as not to affect system files. Check this post (and others) in this thread.
[OnePlus 3 & 3T Cross Device Development] Rated R:
Today, I have tried to wipe everything + format data, reinstall 9.0.3 fw, but SElinux is always permissive.
[OnePlus 3 & 3T Cross Device Development] :
NFC and custom kernels

This is part of the op3-pie-blobs topic: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8996/+/244364

All kernels without this patch are breaking nfc, of course, since the new blobs expect an other name of the nfc devices.

Perhaps we have more then one issue here, but a kernel without this commit can't work with current nfc blobs.

---------- Post added at 09:23 ---------- Previous post was at 09:18 ----------

Please set log to 4 Mio, reboot and get a complete, uncrippled, unfiltered logcat.

EDIT: Is trust complainimg about selinux isn't enforcing?
[OnePlus 3 & 3T Cross Device Development] helderfp:
On lineageOS, is there any way to once your face is recognized, unlock to home screen without a swipe?
[OnePlus 3 & 3T Cross Device Development] Rated R:
Yes, trust and getenforce command with terminal (i have installed magisk for this)

EDIT: log

https://paste.ee/p/0XlIf

https://paste.ee/p/64UXe
[OnePlus 3 & 3T Cross Device Development] :
Both logs are incomplete. I forgot to explicitly mention to perform a reboot after increasing the logbuffer and before getting the logs.