yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Have you tried inital boot without an usb device attached?

What I see in the log:

[ 134.510438] ------------[ cut here ]------------
[ 134.510448] WARNING: CPU: 0 PID: 340 at ../../../../../../kernel/oneplus/msm8996/drivers/staging/qcacld-2.0/CORE/SERVICES/HIF/PCIe/hif_pci.c:3204 hif_pci_runtime_pm_warn+0x100/0x170()
[ 134.510468] Call trace:
[ 134.510525] ---[ end trace d615879e8d969a1d ]---

I have no clue why this happens, nor why the trace is empty... :confused:

Which exact fw package did you flash last? Can you boot a clean flash (wipe system, data and caches) without gapps? Something strange in the recovery.log after a clean flash - before the initial reboot?
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (November Security Patch)

Build 20191107

Note: 20191022 removed because of incomplete patching (curtent.pick.sh wasn't run). If you use 20191022 update as soon as possible to 20191024.

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, 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.5 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

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

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

Changelog (Last repo sync: 7 Nov 2019, 09:36:35 CET / 7 Nov 2019, 08:36:35 UTC):

Patch up: P_asb_2019-11. — 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] KostisTTT:
I flashed last the complete OOS 9.0.5., Firmware OnePlus3T_9.0.5-(08-08-19)-FIRMWARE-flashable.zip

After that, I had a big problem installing even the OOS.

I was flashing the OOS after wipings and I was booting in bootloader (not even in TWRP)

The only OS i managed to install was Havoc OS.

From this point, what I can do?

1. Wipe cache, data, system

2. Flash nlos-16.0-20191107_085907-beta-oneplus3t.zip

3. Flash open_gapps-arm64-9.0-pico-20191107.zip

(??)

Sorry for the many questions, but I dont know what to do to install NLOS...

I didnt noticed something strange after a clean flash - before the initial reboot.

I am going to try a clean flash without Gapps and without USB Stick..

Thanks again...
[OnePlus 3 & 3T Cross Device Development] :
Use the package from the announcement.

OOS is shipped WITH fw included. If you flash oos after fw package you have the fw from oos, not the one from the fw package. If you want to use a different fw from oos with oos you need the flash the fw package AFTER oos, as explained here:

https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164 (section OxygenOS)

Keep in mind that oos tries to flash stock recovery on initial boot, maybe something went wrong...

In the first place: answer all questions and try all hints, before asking: "From this point, what I can do?"

That means:

Install and boot official twrp-3.3.1-0

flash as recommended:

save a recovery log and copy (twrp terminal or twrp filemanager) /sdcard/recovery.log to /sdcard/recovery-fw.log

reboot to recovery after disconnecting all usb devices

wipe system, data and caches

flash nlos rom

save a recovery log and copy (twrp terminal or twrp filemanager) /sdcard/recovery.log to /sdcard/recovery-rom.log

reboot to system without any other packages installed after disconnecting all usb devices

if you end up in twrp again, get pstore

supply both recovery logs as well as the pstore zip
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=6898425]KostisTTT[/MENTION]

I would advice to start fresh, again if you previously had

Download latest oos full rom from oneplus web. reboot to twrp, format data then install oos only

Use msmdownloadtool if flashing oos full rom via twrp is failed

let oos boot until you get a setup wizard

reboot to twrp, wipe everything, then install nlos only, let it boot

if it's succeed, reboot back to twrp and flash anything you like

if something funny happen after that, you can blame any zip you flashed after the rom

If internal storage isn't accessible, you only have to reboot to twrp again in order for it to be visible on the pc

if it's not booting on nlos, then follow [MENTION=4405529]nvertigo67[/MENTION] advice
[OnePlus 3 & 3T Cross Device Development] :
If we want to het to the cause, it's better to go from the more specific probable fixes to the more general fixes. If starting from scratch with msmdownloader (aka unbricktool) fixes the situation we have no way to tell what exactly has caused it. I often call msmdownloader/unbricktool the LAST resort, because it's the last step if everything else fails.

On the other hand: if msmdownloader/unbricktool fails, it makes no sense at all, to walk my suggested debugging way, because all I've sughested (but the single step logs) is also done by msmdownloader/unbricktool.

I'm strongly recommending to follow my suggestion first and try installing oos eventually followed by msmdownloader/unbricktool second, if the first fails.
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
[MENTION=4405529]nvertigo67[/MENTION]

Okay.. I finally settled with nlos even though so-called airtel volte doesn't works[ I gave up].

Smooth experience with very good battery life. Kudos to you :highfive:

Feature request: Gaming mode

Thanks.
[OnePlus 3 & 3T Cross Device Development] :
A quick thread search gives: https://xdaforums.com/search/thread/3879405?query=Gaming mode

If you look at https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78564019#post78564019 you see, where you can help me porting it.
[OnePlus 3 & 3T Cross Device Development] :
I agree, but my post suggest to use msm if he can't even boot the oos.

There's no point to debug if it isn't your rom faults, right? or do you want to debug everything? i'm rather confused here :laugh:
[OnePlus 3 & 3T Cross Device Development] :
Oh, ok, got your point.

The reason, why I want to get to the cause of this is the OP: I'd like to provide a [euphemism]fail[/euphemism]proof installation routine. The same goes for the modded fw thread.
[OnePlus 3 & 3T Cross Device Development] :
He's likely to confused about the fw flashing, ended up flashing many different things along with things causing some funny things happen

From a rookies perspective, searching firmware alone in this forum brings you so many files, diff thread diff files

Also knowledge that format/wiping doesn't wipe fw, and you only have to flash it once until new ver comes out or only when you downgrade to older custom rom based isn't easy to get

That's why i like to see if it's boot the oos first, to ensure that you have a proper working fw :)

This is going too far,

BTW, how sound control (gain) goes? I see audiofx is fixed, and the only things prevent you from adding the sound control is audiofx bug if i recalled correctly
[OnePlus 3 & 3T Cross Device Development] :
No. I've removed it again because of no rom intergration and hickups:

https://xdaforums.com/showpost.php?p=80230482&postcount=1033
[OnePlus 3 & 3T Cross Device Development] Yeshas Prabhakar:
[MENTION=4405529]nvertigo67[/MENTION] Great work!

Thank you for keeping our device still alive :victory:

The Rom is so smooth and minimalistic!

1) Is there anyway I can enable navigation bar and hardware buttons at the same time?

2) How much overnight battery drain % is normal?

3) If I want to test other custom kernel, what is right way to back up current kernel and revert back?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
1) Set qemu.hw.mainkeys=0 in build.prop

2) For me it's 0% overnight.

3) A normal TWRP backup includes the kernel (boot partition). So you can use TWRP to backup/restore the kernel
[OnePlus 3 & 3T Cross Device Development] Yeshas Prabhakar:
1) I have already set it to 0 but still it's not working, any idea why?
[OnePlus 3 & 3T Cross Device Development] :
I don't know. It has never come to my mind to try. For me it's an "one or the other"-type decission.

What is "normal"? The idle drain heavily depends on your setup, i.e. which bg active apps are installed and allowed to keep the device active? It also depends on curtent degradation of the battery itself. Idle drain for my setup with a three years old battery is about 0.6%/h. If I use whatsapp-web it's 0.8%/h.

Just dirty flash the rom and all boot partition altering packages, or use twrp's backup/restore, or make your own image backup with dd.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
But it IS working. You have on screen navigation buttons showing.
[OnePlus 3 & 3T Cross Device Development] Yeshas Prabhakar:
Navigation bar and hardware buttons were not working at the same time!

I had to sacrifice one for the other, but got it working now after build prop edit and disabling the enable on screen nav bar option!

Thank you for your help!
[OnePlus 3 & 3T Cross Device Development] :
https://review.lineageos.org/q/topic:%22button-shrink%22 will be in the next update.
[OnePlus 3 & 3T Cross Device Development] :
MINI-UPDATE (add button setting for one hand mode)

Same as 1107, but with https://review.lineageos.org/q/topic:"button-shrink"+(status:open OR status:merged) picked.

Usual Download directory. Build 20191109.
[OnePlus 3 & 3T Cross Device Development] rituj_b:
[MENTION=4405529]nvertigo67[/MENTION] Am I missing something, or something as basic as VOLTE is not working.

Jio Sim doesn't work at all with calls.

With airtel 4g, it falls back to 3g/gsm and then places or receives a call, which takes atleast 3 4 seconds.
[OnePlus 3 & 3T Cross Device Development] :
Honestly, I don't know. Since some carriers work with volte I'm pretty sure volte is generally working, but broken for some carriers. As a rule of thumb: if volte is working for a specific carrier in oos it should be possible to make it work on los/nlos.

If you read this thread, you'll find that volte on i.e. 404/49 isn't working. I've tried several additional settings, for the latest (https://github.com/nvertigo/local_manifest/commit/a412167e51cce064135c6ad4ba8b31d753be9126 -> https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/242686 ) I did not receive any feedback until your posting. Thanx for the feedback.

Since I'm not using any 404/* carrier (I'm on 262/02 vodafone.de, which isn't supported by the the vendor's blobs), I can't test myself, which makes debugging something between impossible and pain in the arse.

Considering all this, I suggest bringing up airtel and jio volte in the official los-16.0 thread, hoping to reach more airtel/jio users and eventually a dev on airtel/jio.

I'll happily add or change something for airtel/jio isers, but I've completely run out of ideas, other then those I've already tried.
[OnePlus 3 & 3T Cross Device Development] rituj_b:
https://www.mediafire.com/file/64mb...-OB_VoLTE-VoWiFi_Enabler_v1.0-signed.zip/file

I found this module on xda. The author does not describe how he did it. But this fixed VOLTE for me.

Do take a look and hopefully you will be able to fix this.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I use Jio too right now, and I reset network settings (like you asked us to) whenever you merge any volte commits. It hasn't worked till now, but I'll let you know if it does. I still need to test it on OOS. I suspect it doesn't work on OOS either since I bought the US model of the phone when I was in the US. Still don't really get why there's different regional models with bands as the only difference.
[OnePlus 3 & 3T Cross Device Development] :
Do you say this module for oos on op2 makes volte on nlos-16.0 on op3/t working?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I'm using JIO and VoLTE works flawlessly for me. However, I've never seen the VoLTE indicator in status bar, and I honestly don't care as long as VoLTE works fine, but it works regardless.
[OnePlus 3 & 3T Cross Device Development] rituj_b:
I found it in op3 forum.

https://xdaforums.com/oneplus-3/how-to/x-s-s-s-t3858254/amp/

---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------

Hmm. Weird. Mine shows call ended on Jio immediately. And airtel switched to 3g to make the call.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Do you have the Asia model? And did you do anything specific, or did it work out of the box?

Same. Only works with the JioCall app.
[OnePlus 3 & 3T Cross Device Development] Yeshas Prabhakar:
[MENTION=4405529]nvertigo67[/MENTION] I can confirm that Airtel Volte is working after flashing this magisk module!
[OnePlus 3 & 3T Cross Device Development] karakanto:
Well, I finally managed to break free from the G using a clean install of the ROM and microG (nanodroid).

Just wanted to say how smooth things are and how well that works! THANKS!
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the feedback.

SCNR: Long screenshot has been brought to this rom... ;)
[OnePlus 3 & 3T Cross Device Development] knpk13:
I tried the module and it doesn't work for me, I'm guessing because US model, although mobile data works so idk. What model do you have? Did you do anything else to get it to work?
[OnePlus 3 & 3T Cross Device Development] Yeshas Prabhakar:
Well mine is Asian model, I just flashed above model nothing more.
[OnePlus 3 & 3T Cross Device Development] Jigneshg:
Volte will not work on US model. My sister has a OP3 US model Jio Volte doesn't work on OOS too.
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
How come airtel volte works for you.. No luck here after flashing the magisk module. Network setting reset & restarted. Airtel Hyderabad
[OnePlus 3 & 3T Cross Device Development] Jigneshg:
Ok here is the thing

Jio Volte - This should work out of the box for any ROM. 1-2 cases out of 100 there will be issue.Jio's implementation of Volte is better than Airtel.

Airtel Volte - Airtel Volte has some serious issue on Custom ROMs, it's a hit or miss.Currently I have seen it work only perfectly fine on OOS. For custom ROMs it might work in some cases or it doesn't. There is some apn /ims setting but not sure why it works perfectly on OOS and not on most custom roms. You can do/hope is to Clean Flash OOS enable Volte in OOS and clean Flash this rom don't root it and check if it works..even this might or sometimes doesn't. The magisk Module which was flashed is just to enable Volte in build.prop.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I have the Indian/Asian model, yes.

I didn't do anything special either. Just flashed this rom on top of oos 5.0.8. I also flashed the 9.0.5 firmware with 5.0.8 keymaster to avoid formatting internal storage. Like i said, Volte indicator doesn't appear but calls connect fine and quality is great too.

However, native video calls don't work and I'm fine with that since they never worked in oos either
[OnePlus 3 & 3T Cross Device Development] rituj_b:
If all it takes is some prop lines in build.prop to enable VOLTE for me, I don't mind.
[OnePlus 3 & 3T Cross Device Development] karakanto:
To scratch that itch... ;)

Location is working, but looks not to be UnifiedNLP. Possibly due to this issue? https://gitlab.com/LineageOS/issues/android/issues/1270
[OnePlus 3 & 3T Cross Device Development] :
No, because config_enableNetworkLocationOverlay and config_enableFusedLocationOverlay are set to true on op3/t (nlos and los) builds:

ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $ grep -e 'name="config_enableNetworkLocationOverlay"' -e 'name="config_enableFusedLocationOverlay"' ../../../frameworks/base/core/res/res/values/config.xml overlay/frameworks/base/core/res/res/values/config.xml
../../../frameworks/base/core/res/res/values/config.xml: <bool name="config_enableNetworkLocationOverlay" translatable="false">true</bool>
../../../frameworks/base/core/res/res/values/config.xml: <bool name="config_enableFusedLocationOverlay" translatable="false">true</bool>
ingo@adler /usr/local/src/los16/device/oneplus/oneplus3 $

Did you check the log? Is the signature spoofing working? Any selinux denials?
[OnePlus 3 & 3T Cross Device Development] karakanto:
Spoofing is on, and looking at logcat does seem to suggest the UNLP is working (no mention of com.Qualcomm.location either), no mention of selinux too. It's a mystery, but not anything that's really an issue from what I can see.

Thanks again!
[OnePlus 3 & 3T Cross Device Development] :
As long as it works...

sepolicy denial log entries doesn't mention selinux or sepolicy. They look typically like this

11-11 17:20:16.214 8156 8156 W IntentService[W: type=1400 audit(0.0:33354): avc: denied { read } for name="wakeup_sources" dev="debugfs" ino=22 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:debugfs_wakeup_sources:s0 tclass=file permissive=0

If I want to see the current denials, I do something like:

adb logcat -d |grep avc:
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
[MENTION=4405529]nvertigo67[/MENTION]

I have some problems with the browsers cookie.

All browsers (Chrome, Firefox, the integrated browser) say that i haven't enabled third party cookies, but in browsers settings they are enabled.

I downloaded some browsers to verify that isn't a chrome issue but since the problem is present also on other browsers, it could be a problem with the rom. ( I checked also privacy guard but I couldn't find anything related to cookies)

This situation happens on WiFi (i tried not only one wifi) and also on mobile data.

You can verify if you third party cookies are enabled through this site: https://www.whatismybrowser.com/detect/are-third-party-cookies-enabled

I hope you can help me.
[OnePlus 3 & 3T Cross Device Development] :
I'm not sure, if this is the smartest way to ask. The two first lines of your posting suggests, that you want me to answer, which in turn cuts you off from the community knowledge, because everybody lays back, thinking nvertigo has to answer this.

Don't say "but there are threads the op only reads if mentioned", this is the nlos thread and nothing like this has been claimed.

The shipped browser doesn't have a setting for third party cookies, so you can't have enabled it. Third party cookies are rejected by intend. Rejecting tpc by default is a good idea.

Firefox is working. See attached screenshots.

Chromium (I prefer the opensource flavour of chrome) is working, too. See attached screenshots.

I can't verify your claim. See attached screenshots. Obviously, it's not rom related but setup related. Do you use ad blockers and/or anti-malware apps or mods?

Rejecting tpc is a good idea!
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Ok, sorry I didn't mean to be rude.

You are right, Firefox is working (I tried the preview version before) and also chrome (non beta version) is working.

Yes is good to block tpc but i need them to use a University video player (without them it gives me an error)

and that's way I asked there.

Thank you for your reply, and thank you for your work, this rom works very well.
[OnePlus 3 & 3T Cross Device Development] :
I see. Perhaps you can report this to the devs of Universiy video player. Regarding to best security practise, the player should have abandoned using javascript in favour of html5 quite some years ago... Anyway, this doesn't help on tje short track.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Hi, do you think that is possible to implement these in the rom?

https://gerrit.aospa.co/c/AOSPA/android_frameworks_base/+/6717

https://gerrit.aospa.co/c/AOSPA/android_frameworks_base/+/6742

I think this is the Oxygenos implementation of alert slider. It could be cool and useful to have an ui like this for it.
[OnePlus 3 & 3T Cross Device Development] :
No.

You've referenced the q patches, if you look at the corresponding p coomit, you'll find that it's not merged because of a broken method needed to be redone.

This commit isn't compatible with lineage theming.

This commit isn't compatible with our extended volume panel.

The part of implementing this in Settings is missing (and I'm too lazy to search), and will be most probably incompatible to our LieneageParts.

As explained in the 14.1 thread I don't like mixing audio manager with dnd.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20191119

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.5 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.5 firmware

Oneplus 3: OxygenOS 9.0.5 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.5. 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.5 blobs, 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.5 firmware with 5.0.8 bootloader and keymaster

Oneplus 3: OxygenOS 9.0.5 firmware with 5.0.8 bootloader and keymaster

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

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

Changelog (Last repo sync: 19 Nov 2019, 18:00:59 CET / 19 Nov 2019, 17:00:59 UTC):

current.pick.sh: button-shrink. — Nvertigo

op3/t: overlay: Dialer: adjust to upstream. — Nvertigo

Revert "op3/t: add some overlays." — Nvertigo

I'm not at home for the next 10 days. Don't panic if answers are delayed, or if 9.0.6 blobs/fw will not appear as fast as usual.

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] SenseSei:
FYI if you want to clean flash this build:

The opengapps nano build from yesterday (19.11.) doesn't work. It says wrong architecture and something with busybox missing when flashing it in TWRP.

The opengapps build from 16.11. works

Thanks for the new build! :)
[OnePlus 3 & 3T Cross Device Development] kendrick9199:
Forgive me for being half-witted but would this apply to 19.11 pico ? I did a clean flash and everything was perfectly working but now google app is crashing. Again sorry if this a dumb question im still learning ...is there anything i can do other than flashing the rom again with differnt gapps?
[OnePlus 3 & 3T Cross Device Development] knpk13:
If its a gapps issue, you could try just wiping system and reflashing the ROM with a different gapps package, that way you keep your data.