yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Dirk:
FK hasn't been updated to work with Pie Blobs, but i believe both the other two have. :good:

Worth pointing out for those that don't know, NLOS passes Safetynet out of the box. Perfect for people who don't want to mess about with either Magisk or Kernels just for the sake of passing it. (Of course, if you're not using Magisk and are only concerned with passing Safetynet, you can relock your Bootloader to acheive the same).

So many options! :)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
How to relock your BootLoader ?

Updated post :

==> https://xdaforums.com/showpost.php?p=79829810&postcount=2724

Now, it works fine with LOS su addon and Magisk !

Thanx [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
Ran out of thanx for now.

OT (take it with a grind of salt):

You havn't understood that. We are all part of a social and psychological experiment (I'm suspecting mice to be the supervisors). Each time we've managed to solve a problem, two new issues are presented out of the void... ...boss mouse is sill laughing since his psychologists have invented a sczenario called "the pie blobs with locked bootloader"-setting... 42 rulez...
[OnePlus 3 & 3T Cross Device Development] Dirk:
The Dolphins have had enough already. "So long, and thanks for all the fish" i think is what i heard them say on the way out.

There may be a scenario or two that is still untested. How about, restoring a Nandroid that was made on a decrypted 5.0.8, to an encrypted, BL Locked, Magisk Installed, 9.0.4 firmware build, NOT using TWRP, but the stock LOS Recovery?

:cool:
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4544860]osm0sis[/MENTION] is sure that magisk is acuatlly using the aosp keys. That would mean that VerifiedBootSigner-v8.01-aosp-key resigns with the same keys, which makes no difference. Our expirience is that signing with VerifiedBootSigner-v8.01-aosp-key makes a difference.

This should be reported in the Magisk thread - I'm out at this point.
[OnePlus 3 & 3T Cross Device Development] realtos:
okay so OTA should or could work manually :)

as of right now everything is default in magisk, i only use magisk cuz of youtube vanced, dont need or use it for anything else. so only installed youtube vanced so if i relock it will just stay as is? ( i just cant do anything else or new things with it relocked? )
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
"The Matrix is everywhere. It is all around us. Even now, in this device. You can see it when you boot to recovery or when you lock your bootloader. You can feel it when you try to use NFC... when you flash Magisk... when you use Google Pay. It is the world that has been pulled over your eyes to blind you from the truth.

Neo: What truth?

Morpheus: That you are a slave, Neo. Like everyone else you were born into bondage. Into a prison that you cannot taste or see or touch. A prison for your mind.”

― Morpheus The Matrix
[OnePlus 3 & 3T Cross Device Development] :
Make a nandroid and try - if you have trouble booting, or the bl automaticaly unlocks, see the last pages for a workaround with VerifiedBootSigner-v8.01-aosp-key.zip.
[OnePlus 3 & 3T Cross Device Development] Dirk:
"We have asked the same questions without searching the thread a thousand times, and we have become exceedingly good at it"

- Member, XDA.

:)

---------- Post added at 16:20 ---------- Previous post was at 16:13 ----------

There are multiple ways to get the ROM build onto your phone to flash it. The Integrated Updater is the least reliable method. Just browse to the download site using your Browser and install the zip manually. Simple.

If you already have Magisk installed why not configure it properly to pass Safetynet? Or ditch it completely, use the non-Root version of YT vanced, and then relock your Bootloader? Those are your options if you are staying on LOS.
[OnePlus 3 & 3T Cross Device Development] realtos:
thanks Dirk

my magisk is configued correcly to pass it i believe, everything is green but my issue isnt with magisk i think, the bank app has problem with unlock alone, tried to use it comin from OOS with only bl unlocked and nothing else and it didnt work there either so

i will remove magisk and install non root YT vanced and relock :) think thats the best option. i dont need magisk. only yt vanced which i downloaded as module in there :)

thanks again
[OnePlus 3 & 3T Cross Device Development] Dirk:
Are there no budding Kernel Developers here? We need a Caesium replacement. Just take the stock LOS Kernel and add the Verified Boot patches. Release with name, 'Radium', 'Unobtanium', or any of the '...ums'. Now you're a Kernel Dev. Keep it updated and learn your craft bit by bit.

I've got my hands full making enormous Boot Animations. Also i can barely even pronounce Linux, let alone work with it. Anyone need a new challenge? :p
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Long shot but are there any LastPass users here who haven't been able to install the app since going to LOS16? I was on LOS15.1 for a while and clean flashed (with latest firmware/modem) yesterday. Google Play Store now says my phone is incompatible with LastPass, which is a bit silly. Any ideas why this could be? I'm waiting on their support to get back to me but that's going to potentially be totally fruitless.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Does the method on this page work?

https://lastpass.com/misc_download2.php
[OnePlus 3 & 3T Cross Device Development] Doggie52:
It unfortunately just links back to the Play Store which says my phone is incompatible :/ . I see there are some APK mirrors out there but feel mildly happy about getting a password manager (out of all things...) from an untrusted source.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Softpedia should be fine. Up to you.
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Good shout - will use this for now but hoping it's a simple fix on their end.
[OnePlus 3 & 3T Cross Device Development] syntesys:
Hi,

Is there a possibility to increase in call Bluetooth headset audio? For the moment is very slow and the other person cannot hear me.
[OnePlus 3 & 3T Cross Device Development] :
Is your setup passing safetynet?

Is play store showing "Device is certified"?

What's the selinux status of the device?

What's the status of your bootloader?

---------- Post added at 19:31 ---------- Previous post was at 19:21 ----------

This is your chance to give back to the community - you all, of course, not just you Dirk.

Some weeks back, I was asked if I could build the nlos lernel as standalome version. I'm in the same position then Dirk: with my own rom and my efforts in this thread my spare time is used to 110%, so I denied to do so. If somebody wants to build a standalone kernel, but doesn't want to keep the sources up to date, he can use my sources - I try to keep it always up to date.

So, once again: this is your chance to give back to the community!

EDIT:

Reference: https://xdaforums.com/android/software-hacking/reference-how-to-compile-android-kernel-t3627297
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Safetynet: yes (checked through Magisk Manager)

Device is certified: yes, checked in Play Store

SELinux status: enforcing (checked in Trust in Settings)

Bootloader: unlocked (checked with fastboot oem device-info)
[OnePlus 3 & 3T Cross Device Development] :
Do you use anything (i.e. some Magisk modules) that changes the fingerprint of the build (not related to fingerprint sensor!)?

Does the app itself works, if installed from a different source then playstore?
[OnePlus 3 & 3T Cross Device Development] Doggie52:
No Magisk modules currently installed.

App works when installed as an APK from Softpedia.
[OnePlus 3 & 3T Cross Device Development] defi231:
i used OxygenOS 9.0.4 OTA to upgrade FW

https://xdaforums.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
[OnePlus 3 & 3T Cross Device Development] defi231:
doesnt matter when i flashed the aosp key it was always working, directly after flashing magisk or later

and something else, i flashed the 02.07update( over 01.07 ) with twrp and notized that i have to resign the image, if not i got bootloop while using magisk
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Also as of installing LOS16, Google Maps will neither share locations with friends nor store location history. I'm going back down to OxygenOS, I've had enough of this build. Also, why is the LOS15.1 no longer even downloadable? That was a perfectly nice build, very stable and where everything just worked. I get that you want to promote your 16.0 branch but preventing users to fall back to 15.1 means that rather than staying in your ecosystem when something goes wrong, they'll be forced out to some other build altogether.

EDIT: For those looking to go back to the 15.1 branch, there's this lovely mirror: https://www.celsoazevedo.com/files/android/oneplus3-lineageos/
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
Are you sure this is a LOS16 behavior? Have you tried other pie roms and test?
[OnePlus 3 & 3T Cross Device Development] :
Since the rom doesn't boot without resigining, it doesn't make sense to flash it later, though technically possible... ;) At least if the goal is a bootable setup.

Look at tne twrp console output when updating (aka dirty flashing): first the rom zip is flashed (which replaces the magisk patched and aosp signed boot image with the shipped one), then magisk is automatically reflashed by addon.d (which replaces the shipped boot image with the magisk patched one, which is signed with a key, the 9.0.x bootloader doesn't accept). At this point you need to manually flash the aosp key signer again in order to make the boot image booting again.

EDIT:

Will be fixed: https://xdaforums.com/android/softw...d-verified-t3600606/post79838315#post79838315

Then resigning will be obsolete.
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Well - I'm running a perfectly functioning modern device and I have clean flashed LOS16 onto it. I would be highly surprised if it's a general 9.0 issue - I don't think things like LastPass incompatibility and Google Maps location sharing problems would simply go under the radar for months.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI, I just shared (for the first time...) my Google Maps location (Angers - France) with one of my sons (Paris - France) on LOS 16 ... No sweat.

I didn't try the Lastpass (in)compatibiity on LOS 16.

My config: OnePlus 3T / FW 9.0.4 / TWRP 3.3.1-0 / ext4 / unencrypted / BL locked / LOS 16.0 build / open gapp pico / LOS addon su

Edit : Even if not specified in OP (inter alia), Open Gapp pico or nano is strongly recommended to avoid modifying system files.
[OnePlus 3 & 3T Cross Device Development] :
No problems at all with LastPass and Google Play

Latest Lineage OS (v.16 of course)
[OnePlus 3 & 3T Cross Device Development] :
For uNLP you need the "LP outside system"-patch and if you use uNLP on top of microg gms you need the "sig spoofing" patch.

For NLP the qcom stack relays on com.google.android.gms (https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-16.0/gps/etc/izat.conf#L52 ), so either gapps or microg gms needs to be present.

Nonetheless, gps without NLP should work without gapps or microg.
[OnePlus 3 & 3T Cross Device Development] ele95:
i know its open right away but for me i have some glitches whit animations idk why
[OnePlus 3 & 3T Cross Device Development] mumapizza:
Apps like osmAnd or transportr cant get my location, gps is turned on and permission is given.
[OnePlus 3 & 3T Cross Device Development] legendavey:
Definitely going to have to flash GApps, if you haven't already. You can try using a ROM that is patched with microG commits or do the modifications yourself. But doubtful that your GPS issues are going to go away without GApps.
[OnePlus 3 & 3T Cross Device Development] Halamadrid:
Is network traffic added in recent update? ?
[OnePlus 3 & 3T Cross Device Development] legendavey:
You can monitor this commit (and the related ones) if you want to know when the LOS team merges this feature in. ;)
[OnePlus 3 & 3T Cross Device Development] mumapizza:
[MENTION=4405529]nvertigo67[/MENTION] [MENTION=7134312]knpk13[/MENTION] [MENTION=7403273]legendavey[/MENTION]

Issue fixed! Lineageos 16.0 NO Gapps No root with the fairphone nlp zips. location working now for osmand and other apps.

https://github.com/WeAreFairphone/flashable-zip_microG/releases/tag/2018-08-17
[OnePlus 3 & 3T Cross Device Development] :
Just to get that straight: not gps wasn't working, but NLP was absent. For debugging and helping it's important to keep different things different. BTW: those two also have different peemissions.
[OnePlus 3 & 3T Cross Device Development] dimon2242:
Yes, I have it!
[OnePlus 3 & 3T Cross Device Development] knpk13:
I have lag when I open and close my eyes lol. Those few milliseconds of total darkness. Chilling..
[OnePlus 3 & 3T Cross Device Development] ileeba7:
Thanks for this amazing rom, I'm getting great battery life with it. There are some small hickups here and there, but overall amazing job
[OnePlus 3 & 3T Cross Device Development] ayysir:
is there a apn option in this rom?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can edit and add APNs from Settings>Mobile network, but I've not tried to use it.
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Thanks! After repo sync again I climbed through the barrier. However, I faced another obstacle again:

[ 97% 93458/96347] Hidden API: /a/16.0/t...bj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.ja
FAILED: /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar
/bin/bash -c "(rm -f /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar ) && (cp \"/a/16.0/soong/.intermediates/frameworks/base/test-base/android.test.base/android_common/dex/android.test.base.jar\" \"/a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar\" ) && (rm -rf /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi ) && (mkdir -p /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi ) && (unzip -q /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar 'classes*.dex' -d /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi ) && (find /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi -name \"classes*.dex\" | sort | sed 's/^/--dex=/' | xargs /a/16.0/host/linux-x86/bin/hiddenapi --light-greylist=/a/16.0/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=/a/16.0/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=/a/16.0/target/common/obj/PACKAGING/hiddenapi-blacklist.txt ) && (/a/16.0/soong/host/linux-x86/bin/soong_zip -o /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar -C /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi -D /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi ) && (/a/16.0/soong/host/linux-x86/bin/merge_zips -D -zipToNotStrip /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar -stripFile \"classes*.dex\" /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/javalib.jar /a/16.0/target/common/obj/JAVA_LIBRARIES/android.test.base_intermediates/dex-hiddenapi/classes.dex.jar /a/16.0/soong/.intermediates/frameworks/base/test-base/android.test.base/android_common/dex/android.test.base.jar )"
xargs: /a/16.0/host/linux-x86/bin/hiddenapi: terminated by signal 4

What should I pick? BTW I guess that the op build the rom under his/her own repository. The one on GitHub/LineageOS is not able to build with success...
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
BUGREPORT ( Build 15/12/18, stock kernel + Magisk 18.0 + Gapps stock package) Dirty flashed over 5/12/18 build

Google play download status doesn't show up on status bar.

SIM1 is HD capable notification. ( I'm using notificationsoff app as temporary fix)

Tested USB-C to headphone jack, it doesn't seem to work. ( Didn't have a USB-C headphones to test)

EDITED
[OnePlus 3 & 3T Cross Device Development] legendavey:
1 - This varies from user to user, you can try clean flashing the ROM. Could be random, magisk, or just the play store app messing up.

2 - Search the previous pages, someone has posted a "fix", until the notification is hidden 'officially'.

3- Are you talking about a USB-C to 3.5mm jack dongle? Or just USB-C headphones? Either way, doesn't seem like much of an issue since we have a physical 3.5mm port on the phone.
[OnePlus 3 & 3T Cross Device Development] realtos:
dude those things have nothing todo with the devs work here
[OnePlus 3 & 3T Cross Device Development] SpasilliumNexus:
This seems to always come up in ROM threads I lurk in....

It is not, I repeat, NOT a ROM problem. It is an issue with the Pie versions of Setup Wizard and/or the Transfer Tool that we are limited to use with GApps distributions. It happened with the Pixel versions of those apps when we used them, and it still happens with non-Pixel ones.

Disable the transfer tool named "Android Setup", package name "com.google.android.apps.restore" (not to be confused the Setup Wizard also named "Android Setup", package name "com.google.android.SetupWizard"), and reboot.
[OnePlus 3 & 3T Cross Device Development] realtos:
do some work and find out. its not here stuff are added to the rom. gerrit is good hint
[OnePlus 3 & 3T Cross Device Development] :
The actual error is missing from the log snippet, so nobody can tell you. If you need help with building, supply the complete build log.

For me building from plain los works (it's just not handling fde correctly), but that may have changed since 16.0 is heavy wip.

A good starting point is [MENTION=4329165]ivanich[/MENTION]'s posting some pages back. You can also look here: https://github.com/nvertigo/local_manifest/blob/nlos-16.0/current.pick.sh (don't run that, but use pick by pick - manual confict resolving may be necesarry). Don't get confused by the excludes added one line later with -P - it's necessary if you've replaced some repos.
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Interesting - can't even get the app to show up and install on LOS15.1 now. I'm at a loss, I've tried everything (different kernels, different GApps, full flash including media, etc.).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Unless I'm mistaken, your fw is 9.0.4, your recovery is TWRP 3.3.1-0 and your BL is unlocked ... so perform a clean install ... again :

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 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

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

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

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

Enjoy … Hope so.
[OnePlus 3 & 3T Cross Device Development] :
You have reported the app working if installed from third party source: https://xdaforums.com/showpost.php?p=79840400&postcount=2776

So the problem is not any app compatibility, but somethings wrong with the play stores detetction of compatible devices. Since you stated APP INCOMPATIBILITY in

https://xdaforums.com/showpost.php?p=79843765&postcount=2782

the answer from [MENTION=2044343]accuphase[/MENTION] here: https://xdaforums.com/showpost.php?p=79845276&postcount=2784

is completely correct: there is no app incompatibility, there's a problem with playstor.

The issue with maps location sharing is no general pie issue, nor a los issue but specific to your setup - and only your setup. That's why it hasn't shown up...

I wonder if you just want mock about los to get some attention or if you need help solve your issues. If the first: congrats, you've gotten quite a lot, so you can stop now. If the latter (and [MENTION=5092836]Dirk H[/MENTION]as already helped you to workaruond the playstore issue), a logcat from the failed location sharing in maps would be helpful.
[OnePlus 3 & 3T Cross Device Development] Doggie52:
Thanks for the detailed guide, I follow a similar process but even cleaner (no backups, no nothing). Still saw the same problem.

My fix for the Google Location Sharing "this device is not sending location updates" error was as follows:

Go to your Accounts in Settings and remove the Google account

Add the Google account back again

Clear the data & cache from the Maps app

Launch Maps, go to Location Sharing, you should see "FIX" instead of "HELP". Press "FIX"

Voila!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Quod erat demonstrandum !