yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
But I'm using LOS with the stock kernel - and so the patch should be merged since 16.06

But NFC doesn't work.

SELinux is in enforcing in my system - if you can trust "Trust" :)

Does the logcat help here? Or is it also incomplete?

You can transfer the folders separately.
[MENTION=3242790]wistlo[/MENTION] explained it here: https://xdaforums.com/showpost.php?p=79774684&postcount=2546
[OnePlus 3 & 3T Cross Device Development] Dirk:
I think it's safe to say that the recommendation for this Firmware update is a Clean Install. Anything else, all bets are off.

I don't think we have a single issue mentioned by anyone who went the clean route, do we?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Fully agree with you ... (I performed a clean install and now, no sweat but unlocked BT and unencrypted)

I was thinking of a noob who wants to install LOS 16 on his OP3/3T, coming from the official OOS (version 5.0.8 not 9.0.3).

==> https://www.oneplus.com/support/softwareupgrade/details?code=6

Following the official guide will lead to error 7 when installing the zip ...
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
With this assumption I wiped my /data partition (withouth internal storage).

So my filesystem is still encrypted F2FS with boot password (encrypted with clean LOS 20190620)

BL unlocked

Then I booted clean LOS (with complete 9.0.3 firmware) from 21st June - without Magisk and OpenGapps (just to be sure that this is not the issue - but we already knew that is's not.. )

And I can confirm: NFC is working on stock clean LOS

SELinux is still in Enforcing mode
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I think that the real issue is the OnePlus update from 5.0.8 to 9.0.3, not the installation of Los.

If you have a working installation of 9.0.3 then installing Los is simple, right? Irrespective of your bootloader status, right?

So, in my opinion, this OP is fine.

The problems start when you're using Los on a 5.0.3 system and want to update the firmware to 9.0.8. But that's not really a Los problem - it's an OOS problem.

And OnePlus made it clear that updating from 5.0.8 to 9.0.3 with an unlocked bootloader (update: and encrypted) would require a format of the data partition.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
And in reallity, this seems to only apply when using encryption. As long as you don't, you just flash the 9.0.3 firmware in twrp with your unlocked bootloader and then delete lockscreen, fingerprint settings and database and you're done. At least this worked fine on mine and my gf 3t. Only thing that did broke was my Swedish BankID e-ID, solved by factory resetting the app and downloading new e-ID.

Skickat från min Nexus 7 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Celphor:
9.0.3 Blobs, OTA after fresh install and fresh encryption

A warning to everybody upgrading to 9.0.3 blobs for LOS updates after June 19.

If you encrypt your OP3 AFTER the update a following OTA update will crash your system. I'll ended in a boot loop.

This means: It's not only a one timer during transition to 9.0.3, it's a permant problem.

Even restoring the unencrypted data (I wisely did a nandroid backup before) partition didn't help, I had to format system to get it working again.

So keep your hands of encryption until this has been offically fixed.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks. I'll update my post to clarify this.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
NFC not working - the FIX

As NFC is working in a clean installation, the isse had to be somewhere in a file in /data

So I started to discover all NFC relevant files in /data and renamed them one after another to find out which file is the faulty one.

And I had success:

The problematic file is /data/nfc/nfaStorage.bin1

Just rename it (to .bak) or delete it.

Then just reboot the system (or wait a bit) - a new nfaStorage.bin1 gets generated. That inlcudes the new nfc device name "nq-nci"

(change from 16th June, see gerrit here: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_msm8996/+/244364)

Now you're able to enable NFC back again with all functions like Google Pay, Android Beam etc.

Have fun!
[OnePlus 3 & 3T Cross Device Development] MuckiM:
Can confirm, this is working. Thanks
[OnePlus 3 & 3T Cross Device Development] :
Please read before posting. The ota bug has been present before the fw/blobs update... Flash the ota manually and you are good to go.
[OnePlus 3 & 3T Cross Device Development] Celphor:
?? I never had any problems before with OTA updates. And I did them really often (~once a week). And the phone was always encrypted
[OnePlus 3 & 3T Cross Device Development] :
Updating los is an OOS problem? Really?

I can't agree less.

After updating los to 9.0.x blobs and fw, it has become a los problem, and the OP should provide (at least) one working migration path (relocking the bootloader doesn't work for some users). If the solution is a clean flash, it should be in OP. If the solition is formating data, it should be in OP. If the solution is installing OOS 9.0.3 first and then clean flashing los later then 0616, it should be in OP.

Someone else claimed, that issues only occurs on unlocked bootloader AND encrypted userdata. That is not true: the nfc issue (see [MENTION=8423339]Johannes1098[/MENTION]'s analysis(*)) appears also on unencrypted data (and to my understanding even with bl locked and data unencrypted).

At least one user is reporting selinux is running permissive mode with userdata unencrypted.

The claim that issues only show up if the bootloader is unlocked AND userdata is encrypted is just wrong.

(*)this should be mentioned in OP.

This is all introduced with the OnePlus pie update, but updating los is completely los' responsibility; therefor all of the above should be addressed in OP, as long as the recommended way is not "format and clean flash without restoring data"(**).

(**) When restoring data, the "bad" nfc config is also installed.
[OnePlus 3 & 3T Cross Device Development] srcLegend:
Yubikey Authenticator still doesn't work, though I can read the OTP now
[OnePlus 3 & 3T Cross Device Development] Celphor:
Ok, I searched for OTA in the thread ;) It's also possible that TWRP 3.3.1 is the culprit. I had to update TWRP because the old one (3.2.1?, I don't remember) had a bug with formatting data (format -r option unknown).
[OnePlus 3 & 3T Cross Device Development] :
Read before posting!!!

I.e.: https://xdaforums.com/showpost.php?p=79632279&postcount=2127

Before you answer again without reading the thread: try flashing manually (with twrp-3.3.1-0) to solve your issue!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Fully agree !

As reminder: https://www.lineageos.org/Changelog-22/

Upgrading to LineageOS 16.0

(Optional) Make a backup of your important data

Download the build either from download portal or built in Updater app

You can export the downloaded package from the Updater app to the sdcard by long-pressing it and then selecting “Export” in the popup menu

Download proper addons packages (GApps, su…) for Android 9.0/Lineage OS 16.0

Make sure your recovery and firmware are up to date

Format your system partition

Follow the “Installing LineageOS from recovery” section on your device’s installation page

Please note that if you’re currently on an official build, you DO NOT need to wipe your device.

If you are installing from an unofficial build, you MUST wipe data from recovery before installing.

A question: What is the official OnePlus firmware for OP3/3T? 5.0.8 fw or 9.0.3 fw ...

==> https://www.oneplus.com/support/softwareupgrade/details?code=6
[OnePlus 3 & 3T Cross Device Development] ChrisLane:
OnePlus 3

9.0.3 firmware

lineage-16.0-20190624-nightly-oneplus3-signed.zip

TWRP 3.3.1

Magisk v19.3

I wiped my phone (system, data, dalvik, cache) after issues with the kernel upgrade to 9.0.3, everything worked fine after that.

I've just attempted to install the latest update via the system settings and found that my phone is no longer able to boot into lineage os. After the initial lineage os load icon and then typing in my decryption password, the system returns to TWRP after a short while of the lineage os logo again.

I thought that perhaps Magisk was causing the issue and so I uninstalled that and then reinstalled lineage os through TWRP, unfortunately I'm getting the same results.

Any help/suggestions and ideas for more information I can give would be appreciated.
[OnePlus 3 & 3T Cross Device Development] :
It seems you're using the build-in ota-updater ... Please read the post two (!) before yours ... at least!
[OnePlus 3 & 3T Cross Device Development] :
This is ambiguous. It's not possible to wipe a phone. Therefor this information is useless, since guessing and/or assuming is needed to fill that phrase with content.

Something completely different:
[MENTION=2911853]BillGoss[/MENTION]: I was wrong, when claiming the updated firmware is a problem of los. The real problem are users not reading... I was also wrong with suggesting to compile a migration guide or mentioning the issues in OP. Users not reading, will for sure not read another guide or a chenged OP...

In deed every information needed to migrate is already in this thread. Everybody can find this information.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Did you reboot the phone?

And maybe you have to wipe the app data.

I also needed to wipe Magisk app data to use it there back again.

And for PayPal Login and Google Pay I registered it also again.
[OnePlus 3 & 3T Cross Device Development] srcLegend:
Rebooted and app data cleared, still the same
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Here is my LineageOS 16 thread started in the german OnePlus forum:

https://forums.oneplus.com/threads/op3-op3t-lineageos-16-0-offizielle-nightlies.1005819/

And here is a google translation for people who doesn't speak german:

https://translate.google.com/transl...-lineageos-16-0-offizielle-nightlies.1005819/

I've tried to capture all relevant things in terms of migrating firmware. And there are also solutions listed for the issues with NFC, wrong pw and fp not working.

Then I can help you no more, sorry. I don't have this app and anything else relating to NFC is working for me now.
[OnePlus 3 & 3T Cross Device Development] hammer-is:
I don't know if it's a new issue introduced by OOS9.0.3 firmware as I just tested LOS16 a few days ago on my 3T (going from stock OOS9.0.3), but at least I had the same issue that OTA updating while encrypted broke my OS as the phone was unable to boot into LOS16 after updating (using the build-in updater in LinageOS that reboots and flashes without asking for decryption password).

Updating/flashing of nightlies manually from TWRP worked perfect (but that also required to enter decryption password when booting into TWRP, but if that is related I have no idea).

I did several attempts of resetting and setting up the phone to pin point the issue and OTA updating also worked fine before being encrypted.
[OnePlus 3 & 3T Cross Device Development] srcLegend:
I see. Still, thanks for the initial fix. Fixed the most important issue of reading OTP off of the key. I'll just have to use the desktop app for the authenticator function for now
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Two alternatives:

1- keep your encryption but use another "OTA updater" (to avoid entering decryption password when booting into TWRP): Lineage Downloader app (Play Store)

2- decrypt your encrypted device: https://xdaforums.com/showpost.php?p=79745493&postcount=2451
[OnePlus 3 & 3T Cross Device Development] :
This is discussed on the same page 5(!) postings before yours. It's discussed three(!) times on the last 2(!) pages, This is ignorance on a high level.

This behaviour makes the thread no fun to read. It also makes the thread less searchable.

Why don't you reed before posting? You've confirmed to do so, when signing in. Why do you intentinally violate xda forum rules?

This ignorant behaviour really suckz! Stop it!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Issue reported by [MENTION=256559]hammer-is[/MENTION] (unless I'm mistaken):

- LOS 16 has been installed from stock OOS 9.0.3

- if unencrypted, ota updater works otherwise ota uptader fails.

I must have missed something because I'm tired but I didn't know it had already been reported.

Sorry!
[OnePlus 3 & 3T Cross Device Development] hammer-is:
I was just trying to confirm the findings by the [MENTION=3406553]Celphor[/MENTION] - that's all.

I read the thread I was just trying to be friendly.

I posted my findings a few days ago on the twrp issue tracker - but I don't know if it's LOS16 or TWRP related.

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1478
[OnePlus 3 & 3T Cross Device Development] :
And I'm waiting since end of may to debug this (that's why I expirience to read always the same - log missing - stuff as especially anoying):

https://xdaforums.com/showpost.php?p=79695015&postcount=2281

Anyway, obvisously my expectations are a way off. I should stop spending my time here. Better for you and for me.
[OnePlus 3 & 3T Cross Device Development] :
Don't [MENTION=4405529]nvertigo67[/MENTION], your input and knowledge is appreciated here ;)
[OnePlus 3 & 3T Cross Device Development] :
Don't leave us!!! I'll miss you and your expertise!!!
[OnePlus 3 & 3T Cross Device Development] uresh.kuruhuri:
Is ANT+ working on OP3 with LineageOS 16 on it?

I am currently contemplating about installing LineageOS and I use ANT+ for my bike S&C sensor and HR sensor. Currently on Oxygen OOS 5.0.8 and using ANT+ with the "ANT Radio Service" and "ANT+ Plugins Service" installed.

So, can anyone confirm if the ANT+ is working on OP3 with Lineage OS 16 installed?

Also, if it is working - do we need to install the "ANT Radio Service" and "ANT+ Plugins Service" from the Play Store or is everything included with the LineageOS build?

Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
[url="https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-nlos-16-0-t3879405/post79764060" ]It could be helpful[/url] ;)
[OnePlus 3 & 3T Cross Device Development] punio4:
Wrong URL
[OnePlus 3 & 3T Cross Device Development] punio4:
Here it is on a OP3 with latest build
[OnePlus 3 & 3T Cross Device Development] uresh.kuruhuri:
Thanks punio4. That helps. From your screenshot, it seems that installing the ANT Radio Service and ANT+ Plugin Service will make the ANT+ devices communicate with the device.
[OnePlus 3 & 3T Cross Device Development] aashiq10:
Guys is their an option to change default font of LOS without flashing zip file or rooting the device. Any help would be much appreciated.
[OnePlus 3 & 3T Cross Device Development] ceanth:
I tried flashing latest nightly through the update option after not flashing any for over a week and TWRP now asks me if I want to allow system modifications.

This wasn't happening before. What's the best option if I want to keep installing nightly? Regardless if whether I allow or not allow system modifications in TWRP the update doesn't install and I am taken to the main menu of TWRP.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Nope, it's NOT!

"...ANT+ is there since the native pie blobs were updated, plus recently updated with the lacked LA.UM.7.5.r1-04000-8x96.0 "

Updated on June 18, 2019, replied by me on June 20, 2019
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
I there. The slide buton os ok or nota?
[OnePlus 3 & 3T Cross Device Development] archcry:
Yubico Authenticator app doesn't work over NFC, is there anything I can do to help troubleshoot this problem? Let me know!
[OnePlus 3 & 3T Cross Device Development] Imnoa:
There's an NFC fix posted a few pages back, search bar is your friend
[OnePlus 3 & 3T Cross Device Development] archcry:
I saw, but the folder /data/nfc isn't present on my device and a few posts further somebody else says Yubico Authenticator still isn't working after the fix.

Edit: my fault, /data/nfc is present and I deleted the file, but as said above, it doesn't fix the issue. It does work on the oneplus 3 stock pie firmware.
[OnePlus 3 & 3T Cross Device Development] :
Has it worked on los prior to the blobs update?

Does Yubico Authenticator use the safetynet api? If so:

Do you use magisk to get safetynet api to work?

Is you playstore certifoed?
[OnePlus 3 & 3T Cross Device Development] archcry:
I am not sure, I've been running LOS since last week because I did not like the official OxygenOS build.

Prior to OxygenOS I was running Ressurection Remix Pie (LineageOS 16 wasn't released at the time I installed this ROM).

I migrated away from Ressurection Remix on the 3th of June.

When were the new blobs you are talking about integrated in LOS 16?

How do I check this? When I search in de source code available on github I don't really see an indication of safetyNet being used.

I am using Magisk and when I do the in-app safety net check the output is:

SafetyNet Check Success
ctsProfile: true
basicIntegrity: true

Yes, the google play store says "Device is certified"
[OnePlus 3 & 3T Cross Device Development] :
June, the 16th. See lineageos changelog.

I assume you have checked it's not this issue and it's not matching your logs:

https://github.com/Yubico/yubioath-android/issues/95

which led to:

https://gitlab.com/LineageOS/issues/android/issues/256

Even if this isn't matching your issue, it shows the direction:

Check the logs of your issue with the app dev, if it's los related open a los ticket.
[OnePlus 3 & 3T Cross Device Development] srcLegend:
In case you may be able to help me further, yes, not sure, yes and yes. As I mentioned earlier, I can read the OTP off of the key by NFC after the fix, but the authenticator still isn't working

E: Just saw your last post. I'll look more into it
[OnePlus 3 & 3T Cross Device Development] archcry:
With "reading the OTP key" you mean putting the Authenticator app in "Read NFC NDEF mode" right? Because that's the only thing I get working. When I try to read the actual one time password I am getting "Error in yubikey communitation!"

It was working in LOS15.1, I think I should obtain a logcat and see if it matches the issue described on the LOS gitlab.
[OnePlus 3 & 3T Cross Device Development] :
If it was working before the pie blobs, especially check your logs for sepolicy denials.
[OnePlus 3 & 3T Cross Device Development] legendavey:
If you want a working system that you can manually update without issues, whether going from 5.0.8 firmware to 9.0.3 and with daily updates:

(1) Flash your stock OOS ZIP

(2) Then flash recovery 3.3.1

(3) Then flash latest LOS zip with pico or nano OpenGapps

(4) Then fastboot oem lock and reboot to recovery

(5) Format /data (not simple wipe)

(6) Reboot

(7) Setup

(8) Encrypt

(9) Profit!

When updating, download the OTA ZIP to your /sdcard/ and flash it manually by rebooting the recovery yourself. Reboot when finished.

I have been using this updating method for 2.5 months without issues now, including going from 5.0.8 FW to 9.0.3 FW.
[OnePlus 3 & 3T Cross Device Development] :
What's the rusulting difference to

optional - only if you havn't done so: flash twrp-3.3.1-0 and reboot to recovery

flash firmware corresponding to "your stock OOS ZIP"; i.e. for OOS 9.0.3 on op3t https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.3-firmware-3T.zip

flash latest LOS zip with pico or nano OpenGapps

?
[OnePlus 3 & 3T Cross Device Development] srcLegend:
There's basically 2 functions on the Yubikey I have. A newly generated OTP by the key that is used as 2FA on services that directly support Yubikey, and a generic authenticator (like Google's). There are 2 apps by Yubico that enable these functions on the Play Store, YubiClip for the first part, and Yubico Authenticator for the second part.

Now, the first part works just fine after the fix, no further settings needed. The second part does not work, whether I set "Use NFC reader mode" or not. It gives the same error (Error in Yubikey communication!) as you have

"Read NFC NDEF mode" works, but it's basically the same thing as what YubiClip does
[OnePlus 3 & 3T Cross Device Development] icedTricky:
I also have problems with NFC and SELinux.

NFC can be toggled (deleted the file mentioned earlier) but I can neither get a successful read of my Yubikey with Keepass2Android and ykDroid nor a successful read of my public transport ticket with the app mytraQ. So this is not a yubikey only problem!

SELinux is reported as 'disabled' by Trust as well.

I have a 3t did the upgrade with wipe instead of locking the BL.

I installed the latest TWRP

took a nand backup

reformatted /data to f2fs to remove encryption

wiped system and caches

flashed new firmware

flashed 2019-06-26 + gapps pico + su

booted into the system and did initial setup w/o accounts or backup

at this point SELinux already reported as disabled

reencrypted /data

restored /data backup from twrp

deleted screenlock and fingerprint databases, fingerprint config and NFC file

set a new screenlock password and required the password at boot

rebooted the device

Is there any good reason to force upgrade all users to this broken firmware? I.e. does it anything better than 5.0.8?
[OnePlus 3 & 3T Cross Device Development] archcry:
I made a logcat from the NFC tag touching event with the yubico authenticator app open. The problem for me personally is that the logfile is more than 2500 lines long and I don't really know what I am looking for.

Could you guys help me a little bit on this?

Logcat can be found here.

I also made an issue on the Yubico github.
[OnePlus 3 & 3T Cross Device Development] :
I'd suggest to solve the selinux isuue first, before debugging anything else.

Before you ask: no, I've no clue.

In your position I would try finding a user, which succeeded with reformatting with unlocked bl, and find the differences.

Maybe something you've done long ago to your bl (i.e. get rid of dm-verity). But that's just guessing.

IMHO debugging anything else before fixing your setup doesn't make sense. I also belive that running a device with selinux disabled (or permissive) is dangerous.

---------- Post added at 10:32 ---------- Previous post was at 10:12 ----------

Please try to add

ISO_DEP_MAX_TRANSCEIVE=0xFEFF

directly after

NFA_POLL_BAIL_OUT_MODE=0x01

in /system/vendor/etc/libnfc-nxp.conf and reboot.
[OnePlus 3 & 3T Cross Device Development] archcry:
This worked! Awesome. What would be the course of action for me to get this in LineageOS install images?
[OnePlus 3 & 3T Cross Device Development] :
I'll push a commit to gerrit later today.
[OnePlus 3 & 3T Cross Device Development] archcry:
Thank you! I really appreciate the help :D
[OnePlus 3 & 3T Cross Device Development] :
If so, just use the thanx button.
[OnePlus 3 & 3T Cross Device Development] archcry:
Ah yeah ofcourse, I just did.

Could you post a link to Gerrit when you submitted the change request?
[OnePlus 3 & 3T Cross Device Development] :
Done:

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250917/1
[OnePlus 3 & 3T Cross Device Development] srcLegend:
Yep, this one did it. Thanks a lot mate

E: Yo, why is my tags not working?

E2: Never mind, it does work, just not on the XDA app
[OnePlus 3 & 3T Cross Device Development] zezinho7:
On my 3T Lineage OS 16 is only booting with Selinux permissive mode if default 9.0.3 Firmware is used. If I use modified 9.0.3 with Bootloader and Keys frim 5.0.8 it's booting in enforced mode.

Any idea?

What I already tried locking and unlocking bootloader (had to decline the device message unlock yes/no -> no to get it locked again !?)

Format data each time

Flashed OOS community build 9.0/2 and updated to 9.0.3 using stock recovery. Even OOS is booting in permissive mode....

Have no more ideas....hope one of you
[OnePlus 3 & 3T Cross Device Development] mumapizza:
What is nfc extended length? https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/250917

Can't seem to find any information on it? Does it mean the nfc devices dont have to be touching each other, for a connection to be established?