yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I occasionally find the the home button stops responding. If I turn the screen off and on by pressing the power button, then the home button works again.
[OnePlus 3 & 3T Cross Device Development] DaveHD2:
Thanks for the response and tip BillGoss, will give that a go.
[OnePlus 3 & 3T Cross Device Development] RKS96:
Do LineageOS have performance profile quick toggle? If no is there any solution to quickly switch between them?

Thanks
[OnePlus 3 & 3T Cross Device Development] lobotomize:
I've had the same issue, and I think I've noticed a pattern: If you're using the fingerprint scanner to unlock from an off screen and a pattern/PIN is required to unlock the phone (the additional security required message, or whatever the wording is), then the home button won't work after the phone is unlocked. Turning the screen off and then back on fixes the issue as you mentioned.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That's not the case for me. I'll be using the phone and suddenly the home button stops working. But it only happens rarely.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I can confirm, as I use the nav bar I noticed the fingerprint scanner randomly stops working and responding when the device is locked, after unlocking it works again. The lock screen does not say to unlock with the pin only as after a reboot so it's not intended.

Hard to catch a log as it's quite random and happens once/twice a day.
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
wallpaper app crash

los wallpaper is crashing for me. I have included the log file here
[OnePlus 3 & 3T Cross Device Development] :
The log is pretty useless. It looks like you serached for background, missing the actual crash logging... :(
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
sorry actually I am using an app to take logs. I am sending it again
[OnePlus 3 & 3T Cross Device Development] :
Did you look at the so called log before posting it? It lacks the same as the first one. Get a complete log - your log is filtered. If you don't know how to get a log with "an app", use "adb logcat -d >logcat.txt".
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
I apologize for the wrong log. I didn't have access to my pc that time, so bad app choice for logcat, I guess. I think this will work-
[OnePlus 3 & 3T Cross Device Development] DaveHD2:
The workaround definitely seems to be lockscreen related. While I said toggling wifi helped for me in my original post, I now realise it's more about the lockscreen. I use system profiles to disable the lockscreen when I connect to my access point at home.. Turning wifi off activates the leave home profile and re-enables the lock screen. If anyone is interested I tried disabling the on screen nav bar and using the hardware buttons and the same issue persists. Unfortunately it seems to be a daily occurrence for me.
[OnePlus 3 & 3T Cross Device Development] :
I'm sorry to say that: this is a perfect log - but this time no backgrounds (the app) is contained...
[OnePlus 3 & 3T Cross Device Development] kridster:
Hey guys,

recently my volume keys are not working anymore. First the volume down button didn't react and now the volume up button as well.

Pressing the button still feel the same.

I startet the boatloader but they are not working there too. Seems to be a hardware issue.

Does anyone have experienced something like this? I wonder, whether changing the volume buttons is actually going to work?!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Migration from 9.0.5 fw to 9.0.6 fw :

Before :

==> OnePlus 3T / FW 9.0.5 / TWRP 3.3.1-0 / ext4 / unencrypted / BL locked / LOS 16.0 build / open gapp pico / LOS addon su

Note that my 9.0.5 fw was unmodified ( https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.5-firmware-3T.zip)

How to proceed:

- Boot to TWRP 3.3.1-0

- Flash Stable9.0.6 Firmware+Modem_OnePlus 3T.zip

==> https://xdaforums.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066

- Reboot to System

After :

==> OnePlus 3T / FW 9.0.6/ TWRP 3.3.1-0 / ext4 / unencrypted / BL locked / LOS 16.0 build / open gapp pico / LOS addon su

Right now: No issue.

As reminder : Modded fw ... https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Hey there i´ve magisk installed and after the last two updates i did the this week i can´t pass safetynet anymore.

Is this related to the rom or anything else?

I´ve unrooted my phone by wiping /system and flashing the rom + gapps only and it still doesn´t pass at ctsProfile.

I had this issue on my shieldtablet once when i randomly lost safetynet pass even with magisk hide and everything and only a clean flash helped me out getting safetynet back.

So i´m not sure now and i really don´t want to do a full wipe since i can´t enable any more devices in google play music and also can´t unauthorize any so i wouldn´t be able to listen to music on the go.
[OnePlus 3 & 3T Cross Device Development] Dirk:
As you are already using Magisk you might as well just use the Magisk Props module, which is made for this purpose. Just Google it for the XDA thread and follow the instructions.
[OnePlus 3 & 3T Cross Device Development] :
If you search this thread, you'll find it's a changed check by google. For details and workaround see: https://xdaforums.com/showpost.php?p=78433987&postcount=3 Works unrooted, too.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Check this post:

SafetyNet Api: Restrictive Fingerprint matching (by Nvertigo67)

Edit: I took to long to type my post and Nvertigo67 was faster
[OnePlus 3 & 3T Cross Device Development] Dirk:
Just as an aside, it occurs to me that things get easier soon in relation to fixing the CTS Profile problem. 9.0.6 is supposed to be the last OOS build, right? So that Build Fingerprint, (which all Custom Roms will be using soon enough), will be the last. So we only need one more flashable .zip, with the Security Patch Date as October.

As Magisk users will probably be using the Props Module, this is only relevant for the rest of us. I'm sure [MENTION=4405529]nvertigo67[/MENTION] will have a .zip available when the time comes. I'm happy to do it myself, but honestly i'm still not sure how to adapt the script to take into account Android 10's System As Root. Logically i would think the install path just changes to system/system/build.prop or whatever, but it might not be that simple. Aren't the mount points all funky now too?
[OnePlus 3 & 3T Cross Device Development] multiwirth:
But the rom comes with a valid fingerprint i guess since it worked without any mods or modifications on my phone.

Also my other devices with their offical builds and fingerprints pass safetynet so i don´t think google has changed anything recently.

In this case something went wrong by updating to the latest build.

I also went back to an older build but that doesn´t fix it.

But well thank you all i´ll take a look into the links maybe i can fix it without wiping everything (as i did on my shieldtablet for example which fixed safetynet)

EDIT: Since the provided threads are already pretty old (from 2018) i guess that current lineageos build actually should be able to pass safetynet as they did a few days ago without editing any security patch dates.

It must be some kind of a bug and due to the fact the exact same thing happened on my shieldtablet earlier, i think this must be true.
[OnePlus 3 & 3T Cross Device Development] Dirk:
You are very mistaken about this, but honestly i can't be arsed to explain it once again when a simple search will suffice.

BTW every ROM build comes with a "valid fingerprint". That isn't what's happening, but feel free to waste your time restoring backups or clean installing. It's your time after all.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
For an Android 10 install you could just use /system/system. But the issue comes when you want one script to work both with Android 9 and Android 10 ROMs.

Then you have to use something like this (taken from a Gapps installer):

mount -o rw /system

# Remount /system to /system_root if we have system-as-root
if [ -f /system/init.rc ]; then
[ -L /system_root ] && rm -f /system_root
mkdir /system_root 2>/dev/null
mount --move /system /system_root
mount -o bind /system_root/system /system
fi

Notice that the last line leaves you with a mount point of /system which points to /system_root/system if it's Android 10. The rest of the script now works for both older ROMs and Android 10 ones.
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Yeah okay you´re right it´s total normal that safetynet is invalid from one day to another ?*♂️
[OnePlus 3 & 3T Cross Device Development] Dirk:
That's really helpful, thanks.

I did consider the need for two zips, but i don't think we'll see any Pie ROMs using the newer fingerprint. Most have moved development to Android 10 now, and even they might not update the fingerprint for a while.

Google moved the goalposts. That's what they do. You have two solutions, both posted here in the last hour or two. Pick one.

The only thing that surprises me is that they haven't yet made Encryption a requirement for Safetynet. I'm sure it will happen one day.
[OnePlus 3 & 3T Cross Device Development] multiwirth:
So from what i understand the fingerprint changed so there was a new oos build?

And if I'm right this happened the last few days since my safetynet was valid last week.

I don't think google has changed anything the last few days since some other devices running lineage still pass safetynet without mods.

I also mentioned my shield tablet because i had the exact same issue but after wiping it and flashing the exact same nightly that was installed earlier, it passed safetynet again.

So I'm wondering if that's the case on my oneplus too.
[OnePlus 3 & 3T Cross Device Development] :
No.

Why not search or - at least - read the posting, you've been pointed to:

If you don't understand, that this has happend without any changes to the rom, but due to changes on G's side, no one can help you, no matter how often you claim the same.
[OnePlus 3 & 3T Cross Device Development] :
Thx for this shell script as magisk module. It's running great with my op3 and fw9.0.5.

It would be fantastic if you could modify this script to latest fw9.0.6 ... many, many thanks in advance for supporting our great op3/3T. :)
[OnePlus 3 & 3T Cross Device Development] djplus:
[MENTION=4405529]nvertigo67[/MENTION]

In Nitrogen Os based on Android 10 Build date 22/11/2019

Safetynet passes without magisk module or security patch.

The rom also shows android security patch date November. How is it possible?
[OnePlus 3 & 3T Cross Device Development] Dirk:
What's the Build Fingerprint?

I know how i'd do it. Just use the Build Fingerprint from any Official ROM that has the Nov Security Patch. You don't have to use a Build Fingerprint specific to the device. Any matching Fingerprint/Patch will do it providing it is CTS Certified. (That's how the Props Module works).

Edit: To answer my own question:

https://github.com/nitrogen-project/android_device_oneplus_oneplus3/blob/10/nitrogen_oneplus3.mk

"Use 8.0 fingerprints to pass SafetyNet"

Actually, i don't know why everyone isn't doing this.

https://github.com/Magisk-Modules-R...E.md#matching-the-android-security-patch-date

So the requirement to match the Fingerprint and Patch is only being enforced after the date mentioned above. Use an older Fingerprint and the Patch date doesn't matter.

Clever!
[OnePlus 3 & 3T Cross Device Development] :
It's not fw related but fingerprint related. You need an adjustment, when the fingerprint in the rom is updated.

I don't know. Have you checked the gui or the prop? Which fp is used (again: in the prop and in the gui)?Maybe the prop is set to match the fp and the date for displaying in the gui is something else - only guessing here, I've never read something of the nos 10 sources.

---------- Post added at 15:04 ---------- Previous post was at 14:47 ----------

Though this will most probably pass saftynet, I'm afraid this is asking for trouble lazer on: hpw does the g device manager recognise the device with the "foreign" fp? If it's still op3/t, it may collide sooner or later with the device used to trick the safetynet api (latest, when g makes the api even more restrictive next time), if it's the foreign device, you'd be aware, that you may get offered apps needing the hardware of the device you've taken the fp from...

I think faking the sec patch prop is the least invasive way to get a rom to work with safetynet and g services in general (i.e. certified playprotect).
[OnePlus 3 & 3T Cross Device Development] :
Great!

I've never been on a 10 rom, so excuse me, if this is noob:

If a 10 rom is installed, and one types in the twrp console "mount /system", what do you see on "ls -la /system", "ls -la /system/system" and "cat /system/system/build.prop"?

My idea:

if /system/build.prop exists

set PROP_FILE to /system/build.prop

else if /system/system/build.prop exists

set PROP_FILE to /system/system/build.prop

else print some funny error msg on the console and exit

sed -i -e foobar $PROP_FILE
[OnePlus 3 & 3T Cross Device Development] BillGoss:
No need to do that. You can keep using the same script indefinitely irrespective of the firmware you have installed or the firmware blobs used by the rom or the fingerprint set by the rom.

All that matters is that it's a Google certified fingerprint and patch date.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Your suggestion should work. I've attached the output you asked for (taken from the latest Los 17.0 191120).
[OnePlus 3 & 3T Cross Device Development] djplus:
Thanks.

---------- Post added at 03:09 AM ---------- Previous post was at 03:07 AM ----------

Nope. I haven't checked. I assume its what dirk have explained before.
[OnePlus 3 & 3T Cross Device Development] :
In deed, it is asking for trouble: https://xdaforums.com/showpost.php?p=80993353&postcount=8816 ff.

Faking the date to match the latest fp seems the most usefull workaround to me.

---------- Post added at 10:15 ---------- Previous post was at 10:09 ----------

I'm going to prepare such a zip without the remount - your magisk script or the flashable zip seems the way to follow, because these have less side-effects, then using the oreo fp.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I agree with you.

I don't like solutions that have side effects (in this case, using an Oreo fingerprint) because you never know what else may depend on this, or the side effect simply gets removed and you're left wondering what's wrong.

Solutions are best when they are clear and visible.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
- Update 9.0.5 firmware to 9.0.6 went fine (ext4 encrypted, I was on the original firmware and NOT on the modded one (but this should also work if you update the modded firmware to a modded firmware again...)

- I know that the original script from [MENTION=2911853]BillGoss[/MENTION] would also work, but for cosmetic, I updated the magisk "myprop3/T" script to 2019-10-01 sec patch with the fingerprint from the 9.0.6 build.

Works all fine.

I've attached both scripts as .txt here too, maybe someone wants to use them :)
[OnePlus 3 & 3T Cross Device Development] :
Attached you'll find a flashable zip with this script:

#!/sbin/sh

OUTPUT=/proc/self/fd/$2;

ui_print() {
until [ ! "$1" ]; do
echo -e "ui_print $1\nui_print" >$OUTPUT;
shift;
done;
}

ui_print "***********************************";
ui_print "Settting ";
ui_print "ro.build.version.security_patch to ";
ui_print "2019-08-01 matching OOS 9.0.5";
ui_print "(c) 2019 nvertigo67@xda ";
ui_print "***********************************";

ui_print "mount system";
system_mounted=$(mount | grep "system")
if [ -z "$system_mounted" ]; then
mount -o rw /system;
else
umount /system;
mount -o rw /system;
fi

if [ -e /system/build.prop ]; then
PROPFILE=/system/build.prop
ui_print "using /system/build.prop";
else
if [ -e /system/system/build.prop ]; then
PROPFILE=/system/system/build.prop
ui_print "using /system/system/build.prop";
else
ui_print "Can't locate the build.prop file,";
ui_print "nothing will be changed!";
exit 1;
fi
fi

# uncomment the next line to set the build.prop file manually
# PROPFILE=/system/build.prop

ui_print "setting ro.build.version.security_patch=2019-08-01";
sed -i -e 's/ro.build.version.security_patch.*/ro.build.version.security_patch=2019-08-01/' $PROPFILE

ui_print "unmount system";
umount /system;

I've tested this with no-system-as-root (android 9; los-16, etc.) and with removed build.prop. Both works like expected. Now I need people testing this in a system-as-root environment (android 10; experimental los-17, etc.).

Thanx in advance!
[OnePlus 3 & 3T Cross Device Development] pedritopl:
No umount if build.prop can't be found? Just asking. Not sure if it makes any difference.
[OnePlus 3 & 3T Cross Device Development] :
You are right, and I add the umount before the exit. Sadly, it doesn't work anyway: system is always mounted after flashing something (i.e. a full rom flash, which even doesn't mount system during flashing ends with system mounted...). I guess it's some minor twrp bug.
[OnePlus 3 & 3T Cross Device Development] :
I've added some debugging:

ui_print "unmount system";
umount_msg=$(umount /system 2>&1);
if [ -z "$umount_msg" ]; then
ui_print "no msg from umount";
else
ui_print "$umount_msg";
fi
system_mounted=$(mount | grep "system")
if [ -z "$system_mounted" ]; then
ui_print "system safely umounted";
else
ui_print "system still mounted";
fi

In the recovery log I see:

Installing zip file '/sdcard/Download/sec-patch-2019-08-01-unsigned.zip'
Checking for Digest file...
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
***********************************
Settting
ro.build.version.security_patch to
2019-08-01 matching OOS 9.0.5
(c) 2019 nvertigo67@xda
***********************************
mount system
using /system/build.prop
setting ro.build.version.security_patch=2019-08-01
unmount system
no msg from umount
system safely umounted
I:Updater process ended with RC=0
I:Install took 0 second(s).

When I go to twrp's mount tab, I see system mounted.

Anyway, thanx for the heads up! No matter what twrp does, we have our workspace cleaned up... ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Slight problem with the myprop3 script: you can't use the 3T fingerprint and just remove the T. That doesn't result in a valid OnePlus 3 fingerprint. You have to use the correct fingerprint from the official 3 OOS rom - which isn't available yet.

I suggest you remove the 3 script from your post.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Oh okay, I'll remove it. I used the fingerprints from [MENTION=4405529]nvertigo67[/MENTION] s post https://xdaforums.com/showpost.php?p=78433987&postcount=3

I didn't know that the OP3 fingerprints is wrong.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Lol! His zip only changes the patch date.

But your scripts change the patch date and the fingerprint.

I tried both of them and they both fail to pass SafetyNet. I think you've got some more testing to do.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=220012]johannes[/MENTION] & [MENTION=2911853]BillGoss[/MENTION]:

When messing with the fingerprints, never forget it's all these props:

getprop|grep 1907311932
[ro.bootimage.build.fingerprint]: [OnePlus/OnePlus3/OnePlus3:9/PKQ1.181203.001/1907311932:user/release-keys]
[ro.build.description]: [OnePlus3-user 9 PKQ1.181203.001 1907311932 release-keys]
[ro.build.fingerprint]: [OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1907311932:user/release-keys]
[ro.vendor.build.fingerprint]: [OnePlus/OnePlus3/OnePlus3T:9/PKQ1.181203.001/1907311932:user/release-keys]

Also note that "ro.build.description", "ro.build.fingerprint" and "ro.build.description" are set by init (https://github.com/LineageOS/androi...b/lineage-16.0/init/init_oneplus3.cpp#L61-L62 and https://github.com/LineageOS/androi...b/lineage-16.0/init/init_oneplus3.cpp#L70-L71) before system is mounted and before "ro.bootimage.build.fingerprint", "ro.vendor.build.fingerprint" and "ro.build.fingerprint" are set from build.prop and default.prop.

Since the 9.0.5 fp (and the 9.0.6 fp for that matter) are the same for op3 and op3t but the "T", the problems to avoid are mismatches between all four props and/or the values in build.props and default prop.

The more I read of your tries to fake more then just "ro.build.version.security_patch", the more I prefer the least invasive change directly in build.prop. With all additional changes, you are asking for trouble and strange side-effects.

Bottom line: just change "ro.build.version.security_patch" to the date of the fp the rom offers. Period.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
For me on my 3T it's working.

And I know that [MENTION=4405529]nvertigo67[/MENTION] s script only change the patch date, but in his post are the fingerprints I used - and that's what I wrote in my last post. Nothing more :confused:

So my myprop3.sh wasn't wrong.

I don't know why it's failing - it's EXACTLY your script, just with the new fingerprints and the patch date.

As soon as the 9.0.6 fingerprints and firmware are integrated in LOS, I'll remove the setprop for the fingerprints.

You're right, changing the less is the best way.

But for the moment, my script from page 351 is working - so I don't see any reason why I shouldn't use it :)
[OnePlus 3 & 3T Cross Device Development] :
Look at this thread and the nlos thread for possible side-effects, when messing with fp.

Why do you want to fake the fp? You have absolutly no benifit (but feeding the narcism to have always the highest/newest, I suffer from this myself, sometims) from doing so. It's clearly not the least invasive way. Saying "You're right, changing the less is the best way." and still messing with fp is oxymoron.

On each issue with gservices and/or apps from playstore you will wonder, if it's the app, the rom or one of the mismatches I've discussed in my last posting.

There are good reasons to leave the fp alone, even though it seems to work for now.

BTW: los is still based on the blobs from 9.0.4. When I've pushed the fp commit 9.0.5 (https://github.com/LineageOS/androi...b810b6d#diff-ef8370d541c0f9bca2db4941b64f8475 , which updated the fp from 9.0.3 to 9.0.5), I've expected the blobs would be updated, too. If I would have known, that [MENTION=5091734]dianlujitao[/MENTION] would like to stick to 9.0.4 blobs, I would have used the 9.0.4 fp instead.

One last time, then I'm quiet on this topic: just change "ro.build.version.security_patch" to the date of the fp the rom offers.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=4405529]nvertigo67[/MENTION] ah, but sometimes is fun to find out why things don't work and how to fix them :)
[OnePlus 3 & 3T Cross Device Development] :
I'm wrong here. Only for 9.0.5 this is true - all otjer 9.0.X releases differ in more then the "T"... Maybe we should stick with it, since https://github.com/LineageOS/androi...us3/blob/lineage-16.0/lineage_oneplus3.mk#L36 is always set to op3 (without the T). Just an idea, after finding it's only equal for the 9.0.5 fp.