yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] SenseSei:
I can't answer the first part of your question because I didn't try anything other than the nano package.

(I always got errors in TWRP with it.)

But maybe I can help you with the second question:

You could flash again but this time with the nano package, it has the Google App included and it has native "Okay Google" and Google Search support.

Edit: do it like the person above me suggested and just wipe system this time.

You can compare them yourself:

Nano

Pico

You can also try to clear the app data of Google App first, but I think that's not going to help.

Good luck!
[OnePlus 3 & 3T Cross Device Development] knpk13:
What do you think about mods like this? I've seen several like this, AKT, L Speed, and more. I don't know if they really do anything or how I can check if it does anything, so I thought I'd try it out and see what happens. This was the log from it. I've read their threads and it honestly doesn't say much about how any of it works, other than what seems like jargon.

https://www.xda-developers.com/l-speed-magisk-module-gaming-performance/
[OnePlus 3 & 3T Cross Device Development] SenseSei:
If you use a Rom from a developer who's just halve his worth in salt, you shouldn't need to to use these mods. (if at all)

Imho they break more than they give you.

(if you choose to use them, don't report bugs)
[OnePlus 3 & 3T Cross Device Development] :
I completely agree to [MENTION=7452106]SenseSei[/MENTION].

If you look at the log you've attached: the read ahead (on relevant partitions) is already 128kb, most other settings I don't recall from memory, check yourself, if something is changed. Disabling the debugging makes a logcat nearly useless.

Some general thoughts on performance in games:

Like on pc hardware: if the new game lags, get faster hw - there's no substitute for the latest hw then even later hw... ;)

The most limiting factor regarding op3/t's gaming performance is thermal management. Ther are descriptions around on how to disable the thermal engine from los, which seems to make a big difference. Since this obviously doesn't break the hw immediatly, I doubt it makes the hw to last longer. Any other optimizations (besides thermal engine) may improve performance, but the performance gain is so small, that's barely more then placebo.

If you want the performance of a sd855, get a sd855 equiped device.
[OnePlus 3 & 3T Cross Device Development] :
Beta? Still?

As formerly a famous Danishman has asked, I've to ask now: "Beta or not beta, that is the question." (BTW: I don't recall which rom this Hamlet was working on... ;) )

Honestly: [MENTION=9350973]All[/MENTION]: what do you think, is it time to leave beta? Is it time for rc1? For my usecase it's time to leave beta state, but usecases are so different, that I prefer asking people with longer uptimes between reboots, then me.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
This has been production quality already for many months. No need to keep it in beta state in my opinion :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
Wonder what your use case is.

I have very long uptimes and I've been happily using your ROM since the very first NLOS 15 builds. Any minor issues, like all app permissions getting reset randomly (happened last week couldn't identify a cause. Edit: actually I can, it happened after I tried and uninstalled that dumb L Speed mod) probably don't have anything to do with the ROM, and I'd have called it stable months ago. Of course, if you want to go beta again, there's always (N)LOS 17 :silly:
[OnePlus 3 & 3T Cross Device Development] :
This is from about 2 weeks ago, i got a white led system freeze-must force reboot.

Clean flash from 07/11 build, haven't updated yet. i rarely reboot my device unless i want to update.

I'm not sure what causing it, it's already a week without reboot and i can't recreate the issue.
[OnePlus 3 & 3T Cross Device Development] knpk13:
This happened to me whenever I restored a system image from TWRP. So I went back to the file based system backups. I don't think I've ever had it while the ROM was running.
[OnePlus 3 & 3T Cross Device Development] :
Yep, it was while system is running in my case

I was hesistant though to report this lol, i can't re-create it

Same app, same condition (i was on off/home recent the device when the it happen because the app is so bad/slow to refresh things)

So i keep it just in case nvertigo feeling bored :D
[OnePlus 3 & 3T Cross Device Development] :
The pstore was fetched from a normal reboot after about 130 s from boot:

[ 127.116824] Going down for restart now

Most probably this wasn't fetched from the next boot after that which ended in white led of death, but the next-next reboot.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
For me it runs stable and smooth. I came directly from OmniDragon 8.1 to NLos so it was my first Pie experience and so far all good.

I usually charge 1 time a day from 15-20% to full and only restart after notable swift installer updates.

SOT is very good, there's no standby drain (curve is pretty horizontal when asleep)

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
I'm 80% sure recall it was on the very next boot

once the led lid, screen goes black with the status bar still on the screen, pressing on off button doesn't change anything, then i long pressed power+vol up button

If it was an app freeze, and then i long pressed those button, does it leave those line in pstore?

=====

The 130sec~ might mean i was in early stage of finishing my setup (after i flashed something via magisk/recovery). It was around 2 weeks ago, so yeah probably i mixed with other memories..

====

looking at the file details, yes it was taken on 11/11.....
[OnePlus 3 & 3T Cross Device Development] :
2 Minutes after reboot, I wouldn't call "it was while system is running in my case".

Anyway, the console-ramoops is from a normal reboot after the system has run for 130s. No kernel panic, no nothing. Perhaps those ugly 20%... ;)
[OnePlus 3 & 3T Cross Device Development] :
Geez, my mind being questioned right now about that "very next boot" acts crazy to convince me it was right. Nah screw it, let's just forget it since it's all ok right now :silly: :laugh:
[OnePlus 3 & 3T Cross Device Development] :
Don't worry, back in oneplus one times, it took me about 5 reboots or so, until I've realized, that if you have a kpanic with device pluged to a power source, the hard shutdown followed by the neet batt animation IS A REBOOT. last_kmesg is from the boot for the batt animation, not from the panic any longer... (yeah, I know, it's obvious if one thinks about) ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=4405529]nvertigo67[/MENTION] I didn't like that setting the build patch date to pass SafetyNet meant that I lost the actual build patch date. So I modified my Magisk script to swap the vendor and build date around. Now I should pass SafetyNet and see the actual security patch date.

And I do pass SafetyNet but to my surprise the About phone settings shows the same date for both vendor and build!

Yet a getprop shows correctly the swapped dates.

What's going on with the About phone into?
[OnePlus 3 & 3T Cross Device Development] :
Interessting! I don't know, my best guess would be the mismatch of what getprop shows and what's in /system/build.prop and /system/vendor/build.prop. Generally I'd think it's not too reliable to change a ro prop while booting (there must be a reason, why ro props exist at all... ;) ), but after the change files and getprop should report the same to exclude strange side-effects. Or it's just a strange timing side-effect of the resetting of the props and the gui... ;)

I've tested the exchange for nlos (on build time file basis, of course - and it worked the way you want), but decided against, because only changing (faking) one prop is less invasive then faking two props. Sometimes I feel so systematically.... ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Thanks for having a look. The swap is now working - I don't know why it wasn't working before.

I tested your patch zip on Los 17 and it works properly (updates build.prop).
[OnePlus 3 & 3T Cross Device Development] knpk13:
I've been using your old script for a while, and about phone often showed the actual patch date (November right now) instead of the faked one, but safetynet passed. I didn't really get it, but like I said safetynet worked so I didn't bother to mention it till now.

Edit: I was going to attached screenshots of about phone, get prop, safetynet check, and the script to make it clear, but safetynet is failing now. Maybe because I updated the firmware to 9.0.6?

I tried your new script (the swapping one) and got the same results as you on the first reboot (as you posted in your screenshots) and safetynet passes again.

You mentioned the swap was working in the about phone GUI after you rebooted again, but that isn't the case for me. Both dates are still November in the GUI, and safetynet passes. Getprop in a terminal shows the correctly swapped dates. Not sure why the old script stopped working. But I'm guessing the new script has the advantage of being universal, unlike the old one that needs to have some values modified depending on the setup? I read nvertigos post #3 and saw he pushed a new zip for 9.0.6 but I don't get if that needs to be used when the firmware is updated or when the ROM blobs are updated (since I don't know where the fingerprint comes from). I'm so confused.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Firstly, firmware updates have nothing to do with SafetyNet. The properties that SafetyNet uses come from the running system, which the firmware doesn't affect.

Secondly, I have no idea how the About phone display gets the information shown. It could use the getprop function of it could read the data from the property files (build.prop from /system and /system/vendor). But I thought that it was using the getprop function based on what was shown previously with my Magisk script.

Thirdly, my About phone is back to showing the same date in both fields! I have no idea what's going on with this.

Fourthly, the zip that [MENTION=4405529]nvertigo67[/MENTION] published for 9.0.6 is only necessary if the rom you're running has a 9.0.6 fingerprint (and is most likely using 9.0.6 blobs). I'm not aware that anyone has done this yet, but I may be wrong.

Fithly, I hadn't meant to create a universal script. I just wanted to see the true security date in the About phone screen. But, now that you've mentioned it, it is universal if the fingerprint and the vendor patch date are from a Google certified rom - which it is for Los.

Finally, I would be interested to know why the script you had been using stopped working. Did this happen after updating the rom, or had you added a Magisk module, or did you uninstall and reinstall Magisk. Something must have changed for it to suddenly stop working.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Ah I see. Well thanks for the very informative reply! I actually understood everything you said this time. I often get lost when nvertigo talks about more technical details; still trying to learn all this Linux, git, and Android stuff. And no, the only thing I changed is the firmware update. I don't think any of my magisk modules would interfere with your script (adblock, viper, fdroid, YouTube, substratum, and Google camera fixes) and I have made no changes to the modules I'm using. I might try the old script again to see if it works and I'll let you know then. One thing to note is that with the old script (as well) I had issues with what was displayed in about phone, sometimes it showed the faked patch date, and sometimes it showed the real one, but safetynet always passed.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I think you're right. I'm now running my "swap" script from post-fs-data (earlier in the boot process) and now I'm getting consistent values shown in About phone

Hmm, so still no reason for it to stop working.

Try putting the scripts in /data/adb/post-fs-data.d instead of service.d
[OnePlus 3 & 3T Cross Device Development] :
You havn't read closely enough: I havn't added just another script, but I've added a new script for a new fingerprint. Which script is needed is defined by what "getprop ro.build.fingerprint" returns. I think that the fp is defining, which script to use, is explained understandable in #3.

[MENTION=2911853]BillGoss[/MENTION]: The earlier, the better. The bootprocess timing is NOT always the same. If you compare dmesg outputs from a system to system reboot, a recovery to system reboot, a cache wiped recovery to system reboot and a cold boot, you'll find very small differences in the order of the boot process... This may or may not have impacts on the reset props and when the prop is read i.e. by the gui. This may also explain, why the script may fail in i.e. one out of 100 times - if so, knpk13 is an awesome tester: he hits this case... ;)

To avoid such hard to track down timing issues, you can try making a magisk module, that overlays the two build.prop files. This would change the props on file basis when system is mounted, which is before data is mounted (post-fs-data).
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yup same for me, it works. But um.. it killed all my substratum overlays. I'm gonna reboot and see if they come back. Or just install them again. Weird, hopefully there aren't any other side effects.

Edit: It borked some of my magisk modules too ( thrystill show up in magisk manager though), the YouTube vanced app disappeared, viper4android got borked, adaway stopped working. Should I put the script back in service.d or just reinstall my modules? I don't know what the difference in, guess I should read the magisk docs to try and wrap my head around it. Not sure what's going on. Here's the log if it helps.

Edit 2: Reinstalling didn't work. I'm putting the script back in service.d. Did you have any side effects? Oof, root requests from my file manager apps are very late as well. I have no idea how this is borking su.
[OnePlus 3 & 3T Cross Device Development] :
safetynet api

I've updated all sec-patch scripts to v02. They should work with any rom now. I've also updated posting #3.

Using these scripts to just set the sec patch date without messing with the build fingerprint is the only supported method to pass safetynet api for nlos-16.0.

For now nlos-16.0 (as well as los-16.0 and los-17.0) require sec-patch-2019-08-01_v02.zip.
[OnePlus 3 & 3T Cross Device Development] Ysfzone:
Great ROM

i juste missing 4G Tile and Game mode Tile..

You Can add them or just tell me how i can add them
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=78531237&postcount=138

The same (all commits needed) goes for 4g tile.
[OnePlus 3 & 3T Cross Device Development] votz11:
in los16 24/11/19 update + magisk + 9.0.6fw the sec-patch-2019-10-01_v02.zip , cts fail ,

but the sec-patch-2019-08-01_v02.zip ,work, cts pass...

anyone else have same results ?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
No, I have no side effects and my log is clean.

Your log, however, does has a warning and an error nearly at the end:

11-25 21:36:29.647 474 10680 W Magisk : su: request rejected (10124)
11-25 21:36:29.648 474 10680 E Magisk : write failed with 32: Broken pipe

But I doubt they are caused by the swap script. But you can test booting up without the swap script and see if those errors go away.
[OnePlus 3 & 3T Cross Device Development] Dirk:
This is two posts above yours:
[OnePlus 3 & 3T Cross Device Development] votz11:
thanks dirk i was misreading before, done :)
[OnePlus 3 & 3T Cross Device Development] :
That's the expected behaviour. Check the build fingerprint (adb shell getprop ro.bootimage.build.fingerprint) and read posting #3 closly, and you'll see that you need to flash sec-patch-2019-08-01_v02.zip to match the build fingerprint of los-16.0 as described in #3:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Hm, interesting. idk what's going on then. I rebooted with the swap script in postfs and the next time there were no errors in the log, but the borked mudules remained. Script is back in service.d and everything is working fine now.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Ah the joys of ignorantly tinkering with complex systems!

I wish I knew a lot more about Android and Magisk, but I don't have the energy or the inclination to go through the learning process. ☹️
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (blobs & firmware: 9.0.6; beta -> release candidate)

Build 20191125

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.6 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.6 firmware

Oneplus 3: OxygenOS 9.0.6 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.6. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.6 firmware, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 25 Nov 2019, 17:59:08 CET / 25 Nov 2019, 16:59:08 UTC):

NLOS: move on to release candidate 1. — Nvertigo

NLOS: bring up OOS 9.0.6 blobs. — Nvertigo

op3/t: regenerate blobs from OxygenOS 9.0.6 (op3t zip). — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
[MENTION=4405529]nvertigo67[/MENTION], I recorded a logcat with mobile data being in use and playing in Browser music from YouTube. Maybe you can see here something that can be related to that Mobile network standby drainage.

Thanks and waiting for you answer. Clean flashed latest version of NLOS, no Gapps.
[OnePlus 3 & 3T Cross Device Development] :
No. Debugging this is complex, just a log alone isn't sufficient. deepsleep and wakelock stats are also needed.

Since I'm not suffering from this drain, I'm not your man to guide you through debugging this.
[OnePlus 3 & 3T Cross Device Development] knpk13:
You can try posting a BBS log in one of the BBS threads to see if they can help.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE: drum roll... RELEASE! (December sec patch; per app firewall)

Build 20191205

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.6 firmware is required. At this point you have two options:

You don't care about loosing data on an unlocked bootloader and clean flash including format userdata according to the first time installation instructions in OP (recommended):

Oneplus 3T: OxygenOS 9.0.6 firmware

Oneplus 3: OxygenOS 9.0.6 firmware

You want to keep your current setup and like to dirty flash on top of beta builds:

I've created a firmware package from OxygenOS 9.0.6. To avoid issues due to an unlocked bootloader and/or encrypted userdata partition, I've kept the bootloader and and keymaster partition to OxygenOS 5.0.8. This allows to run the pie-blobs builds with native Oneplus OxygenOS 9.0.6 firmware, but you don't need to reformat the userdata partition (for details see: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 ).

Oneplus 3T: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

If you need to pass safetynet api flash sec-patch-2019-08-01_v02.zip from https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 .

Before you ask: though I've updated the blobs used in the rom to OOS 9.0.6, I've decided to stick with OOS 9.0.5 build fimgerprint, because 9.0.5 is the only version with identical fingerprint strings for op3 and op3t.

For a complete list of additional cherry picks see: current.pick.sh.

Changelog (Last repo sync: 5 Dez 2019, 16:04:39 CET / 5 Dez 2019, 15:04:39 UTC):

current.pick.sh: "Added policy based firewall in the security tab." — Nvertigo

Patch up: P_asb_2019-11. — Nvertigo

NLOS: ship release instead of beta or rc. — Nvertigo

NLOS-Bootlogo

nlos_bootlogo-v0.1.zip

back_in_black_bootlogo-v1.0.zip(pre ob16 OxygenOS Bootlogo)

[SIZE="+2"]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] shivangswain:
Thanks for the update. I'm having some issues getting CTS to clear in this build and also have app crashes (APKPure crashes at Updates Section). I tried to pull a log locally but MatLog also crashes at start. Is there anything on your side running this build. If not, I will try and get a adb log of the crashes, when and if possible.
[OnePlus 3 & 3T Cross Device Development] :
Goodbye afwall

If sec patch is already flashed, then you're on your own to figure out whats wrong

Clear cache or re-install the related crash app might help

So far no funny things happen on my end with dirty flashing
[OnePlus 3 & 3T Cross Device Development] :
Would you reconsider your quoting habbits (only quote what you are directly refering to), please. This helps to keep the thread readable and searchable. Thanx in advance.

On my side the build runs flawlessly. safetynet api works great with 2019-08-01.

Logcat and detailed setup information is mandatory.

Don't talk about warez, neither in my thread nor on xda in general:

https://xdaforums.com/android/apps-games/app-apkpure-ad-free-t3896598/post79061240#post79061240

Maybe, you've been hit by some malware or misbehaving app.
[OnePlus 3 & 3T Cross Device Development] shivangswain:
I'm sorry, I don't have access to my PC and doing this on mobile, I didn't pay attention to the length of the quoted post.

Now, I'm even more confused as this build requires the 9.0.6 firmware and that has the 2019-10 vendor patch and thus I used the 2019-10 patch. Am I supposed to use 2019-08? I don't understand.

I don't have the modded version of APKPure or any warez apps, so I don't know what that's supposed to indicate. The only sideloaded app on my phone is Flamingo for Twitter because that app has been pulled from the Play Store for new customers. I pay for legitimate paid/pro versions.

Thank you for your assistance.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It uses 9.0.6 blobs and therefore requires 9.0.6 firmware, but still uses 9.0.5 fingerprint, so you have to use the 2019-08 patch zip. The reason nvertigo67 gives for using the 9.0.5 fingerprint earlier in the thread is that 9.0.5 is the only build for which both the OP3 and 3T have the same fingerprint. I'm not sure why that's important and why it prevents us from using 9.0.6 fingerprint, but I haven't bothered questioning it yet since everything works for me.

Edit: also I just noticed, this is mentioned in the release post that you quoted, so I didn't need to rewrite it, rip.

Oh and congratulations [MENTION=4405529]nvertigo67[/MENTION] ?, finally a "release" build!
[OnePlus 3 & 3T Cross Device Development] :
That was my first gut, but i tried not to judge

It was mentioned yet he keep believing his believes lol

let's move on :laugh: