yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (mainly maintainance)

Build 20190802

Releasenotes:

This build relies on OxygenOS firmware. OxygenOS 9.0.4 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.4 firmware

Oneplus 3: OxygenOS 9.0.4 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.4. 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.4 blobs, but you don't need to reformat the userdata partition.

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

Oneplus 3: OxygenOS 9.0.4 firmware with 5.0.8 bootloader and keymaster

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

Changelog (Last repo sync: 2 Aug 2019, 17:08:20 CEST / 2 Aug 2019, 15:08:20 UTC):

op3: Disable ALMK and PPR on all targets — Artem Borisov

Enable enhanced call blocking by default. — Tyler Gunn

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] DamienCassou:
Clarify documentation

Hi,

the first message of this thread includes:

you might want to get rid of this part if the official TWRP is now good enough (which seems to be the case according to the installation instructions in the same post).
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the heads up - I've only chamged the recommendation in the first time instructions and forgot about the download section.

Fixed:

EDIT:

I really wonder, if it makes sense to revert the recommendation to 3.2.3-10 again: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post80009239#post80009239
[OnePlus 3 & 3T Cross Device Development] :
Just flashed the rom. working good with my setup :good:

ed is working too, much stabler than NOS while using it (sometime i lost it over reboot with NOS). but any dev (especially [MENTION=4405529]nvertigo67[/MENTION]) would yelled at me if i bug them with it. So yeah, it's nobody faults except myself :laugh:

Thank you for the rom
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Security Patchlevel & Vendor Security Patchlevel for August; blobs&fw: 9.0.5)

Build 20190808

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.

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

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

Changelog (Last repo sync: 8 Aug 2019, 17:58:17 CEST / 8 Aug 2019, 15:58:17 UTC):

current.pick.sh: "fix-hwc2-outdoor". — Nvertigo

Patch up to android-9.0.0_r46. — Nvertigo

Revert "NLOS: track our own packages/apps/Messaging." — Nvertigo

NLOS: bring up OOS 9.0.5 blobs. — Nvertigo

op3/t: regenerate blobs from OxygenOS 9.0.5 (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] derbestimmer:
as always thanks for the release. looks like i still did not fully understand the firmware-upgrade-decryption issue and f****d up big time... i flashed the modified 9.0.5 and without reboot the 0808 nlos release and ended up with "correct password but corrupt data -> factory reset" message during boot (paraphrasing here) and "pattern incorrect" in twrp. although i am sure my data is lost. i'd like to know what i did wrong and how to do it correctly in the future .

i already was on oos 9.0.4 before when switching to nlos (so there actually was not 5.0.8 to 9.0.x scenario) should i have taken the unmodified firmware in order to avoid loosing my data? how to upgrade correctly when already on v 9.0.x? and is there perhaps still a chance of recovering my data (no this is not the device i trashed) thanks i advance
[OnePlus 3 & 3T Cross Device Development] :
Please help us to keep this thread readable and better searcheble by only quoting the relevant parts (what you are exactly refering to) of a posting. I'd appriciate editing of you posting.

You need to use either the 5.0.x bootloader or (execlusive or!) the 9.0.x bootloader. When ever you change the bootloader, you need to reformat/reencrypt the data partition.

For more in depth and detailed information see additionally: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] derbestimmer:
i see. thx
[OnePlus 3 & 3T Cross Device Development] :
JFYI

Though I havn't expirienced higher battery drain after the latest play services update, I think it may be usefull to know about this "present" from g:

https://fossbytes.com/notice-any-high-battery-drain-this-android-bug-is-at-fault/
[OnePlus 3 & 3T Cross Device Development] :
biometric security

OT

If a company wasn't able to secure their user's data, the custumers are asked to change their passwords. But what's the recommended action if biometrics are compromised? How to change fingerprints or face geometrics?

Just something to think about: https://www.vpnmentor.com/blog/report-biostar2-leak/
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That's why you should never store passwords (or biometric data) but only the hashed value. That way you can verify the supplied information but can't reverse engineer the source data.
[OnePlus 3 & 3T Cross Device Development] :
Yes. That's why I posted the link:

"This makes fingerprint data theft even more concerning. Fingerprints are replacing typed passwords on many consumer items, like phones. Most fingerprint scanners on consumer goods are unencrypted, so when a hacker develops technology to replicate your fingerprint, they will gain access to all the private information such as messages, photos, and payment methods stored on your device."

BTW: if you have offline access to i.e. pasword hashes (like the widely spread unix shadow file) you can start brute forcing against. I'm pretty sure this can also be done against fingerprint hashes or face geometrics hashes - it just needs more flops...
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: see changelog; maintainance)

Build 20190816

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

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

Changelog (Last repo sync: 16 Aug 2019, 10:28:33 CEST / 16 Aug 2019, 08:28:33 UTC):

kernel update: [MENTION=5091734]dianlujitao[/MENTION] has redone the los kernel. The old los kernel can be found at: https://github.com/LineageOS/android_kernel_oneplus_msm8996/tree/backups/20190816-0308/lineage-16.0 . The new kernel is just https://github.com/LineageOS/android_kernel_oneplus_msm8996/tree/lineage-16.0 . The latest common commit of bot branches is https://github.com/LineageOS/androi...mmit/0061e6d1850db8a7f932c946ab847d401599561f .

Based on this work I've upstreamed the los kernel to v3.18.140: https://github.com/nvertigo/android_kernel_oneplus_msm8996/tree/linux-stable/merge-16.0

Finally I cherry-picked the nlos changes on top of the upstreamed merge: https://github.com/nvertigo/android_kernel_oneplus_msm8996/tree/linux-stable/nlos-16.0

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] :
If you look at my last posting (the update announcement), you can see pretty good what's the dfference. Since I rebase the nlos additions always on top of the uptreamig, everything later then the last common commit of linux-stable/merge-16.0 and linux-stable/nlos-16.0 (https://github.com/nvertigo/android...mmit/e5d0f834d900f6bd25139f59eb737ce775e4c971 ) are nlos additions.

EDIT: No, there is no standalone package. (see also: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post79624410#post79624410 )
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (automatic call recording; maintainance)

Build 20190823

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

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

Changelog (Last repo sync: 23 Aug 2019, 10:51:50 CEST / 23 Aug 2019, 08:51:50 UTC):

Revert "NLOS: add for reference /vendor/xiaomi." — Nvertigo

current.pick.sh: "Dialer: Add autorecord feature". — Nvertigo

Revert "current.pick.sh: "fix-hwc2-outdoor"." — Nvertigo

op3/t: Remove config_tether_upstream_types — Sam Mortimer

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] dogmatism:
edit , Honoring OP
[OnePlus 3 & 3T Cross Device Development] :
The original question is from 2nd Feb. 2019.

Only very few people expirienced this.

The los kernel (nlos kernel is based on) has been rebased 2 times since then. I havn't seen any complains about lod for many months.

Custom kernels arn't supported in this thread - see OP.

If you still think your advice is usefull, you should honor OP and tell that the setup is not supported in this thread.

To be as clear as possible:

I don't say don't use a custom kernel. I just state that if you use a custom kernel and encounter any issues, do a clean flash and reproduce the issue before getting logs, saving pstore and reporting it here.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I am back in India for a while after staying in the US for 3 years. And sorry if this isn't the right thread to ask, I'm not sure where to post this.

I have a OP3T, A3000 (American Model)

My dad gave me a Reliance Jio SIM card, and when I looked up the bands, only 1 of the 3 bands for 4G LTE was on my device. I didn't expect it to work, but it's working, although the default dialer and SMS apps don't work, and I have to use the JioCall app for calls and SMS. But I don't know why I have to do that and the app is kinda clunky. Is it because of something related to VoLTE? Basically my question is what do I need to do to use a Jio SIM properly with my device (if possible with my model) ?

I remember [MENTION=5868698]64ashg[/MENTION] talking about Jio earlier and I searched the thread but didn't find much helpful information. The information on the Jio website was also of limited use.

Unrelated question, what's the best website to look up detailed device specifications?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I use https://www.gsmarena.com/
[OnePlus 3 & 3T Cross Device Development] 64ashg:
I would suggest you to dial *#*#4636#*#* and select the phone option.

Select the lte only option in the dropdown in front of you and then in the three dot menu, try changing the bands, first option and enable volte provisioned.

Then goto settings and select network & internet, mobile networks and set enhanced 4g mode enabled and preferred network type to lte.

Yes this is a volte issue as i remember using my opo a0001 the app way, which is rubbish.

I have an a3003 btw. I would suggest you to switching the stock rom to verify the volte issue although i think thats the issue.

But volte protocols should work even if you don't have all the bands supported, am i wrong?
[OnePlus 3 & 3T Cross Device Development] knpk13:
I've never used that dial code before, can you tell me more about them? I followed your instructions but it still doesn't work. I don't really know much about Volte or this stuff so I can't say if it's supposed to work. I can try the stock rom later. What should I do if there's a volte issue?
[OnePlus 3 & 3T Cross Device Development] :
I don't know about jio. For volte on vodafone.de: though my data plan allows volte there is NO WAY to get volte to work, but editing the efs partition - I've never tried, because I want to have the same efs setup as most other users.

If volte is working on oos, you need to compare apns-conf.xml from oos and nlos - which is a pain in the arse since oos has linebreaks and los/nlos hasn't.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Ah ok. Sounds complicated. I'll try it on OOS. How do I know if Volte is working? Google says there should be a Volte icon but I've never seen that before. I only see a LTE icon.
[OnePlus 3 & 3T Cross Device Development] :
Currently the history in OP is complete (wasn't forced to delete the oldest by size limit, yet ;) ): apart from not knowing what's picked in current los 16 beta, both changelogs + the content of current-pick.sh represents all changes on top of los 16 code base.

Selinux is running enforcing like on los 16 beta.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Thank you for your answer.

Last question before i switch to your rom: is NLOS more battery friendly/optimized than LOS?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Honestly every ROM or kernel I've ever used on the same device seems to have about the same battery life to me, unless there's a serious bug.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
which rom do you use?

I'm on LOS 16 and very satisfied... But want to try NLOS 16...
[OnePlus 3 & 3T Cross Device Development] knpk13:
NLOS obviously lol. I like the small thoughtful additions to LOS in this ROM a lot. Other custom roms are too bloated and weird with unnecessary features and branding.

The battery life aspect I speak from experience. EAS, custom kernels, different ROMs, all give me the same battery life as far as I can tell.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Worth a look in to it. Best rom I've ever used. Starting from support, finishing with attitude.
[OnePlus 3 & 3T Cross Device Development] Mata99:
I suppose you will need also this commit

https://github.com/nitrogen-project...mmit/724f6c685162e2ff8032deca46c6c1c9017a92a2
[OnePlus 3 & 3T Cross Device Development] Syssx:
[MENTION=4405529]nvertigo67[/MENTION] do you have any other channels than XDA to notify users when you make a new update? Like telegram or something like that. That would be really nice :)
[OnePlus 3 & 3T Cross Device Development] :
No. No ota updates.

NLOS is a one man show. One channel for documentation and notification to maintain is enough for me.
[OnePlus 3 & 3T Cross Device Development] :
Thanx.

And this one, too: https://github.com/nitrogen-project...54bcb4b#diff-9daf209692c7b3b51a0446148f95a884
[OnePlus 3 & 3T Cross Device Development] knpk13:
What is the expected behavior of the volume panel in the next update? From what I read, I'm assuming it's ALWAYS on the left (in portrait and landscape mode) and aligned to the position of the volume buttons (only in portrait mode).

This is the behavior on the current latest build with the only difference being that the volume panel is ALWAYS on the right.

My question regarding the new behavior is, would the volume panel shift to the top or bottom depending on the orientation in landscape mode so that it is aligned with the volume buttons, or would it still just ALWAYS be on the left?
[OnePlus 3 & 3T Cross Device Development] :
What's top after shift? Relative to the orientation of the device it's always left.
[OnePlus 3 & 3T Cross Device Development] knpk13:
The volume panel. I see, so the only change is that it goes to the left. I was expecting/hoping that in landscape mode, the volume panel would move to the bottom if the volume buttons are at the bottom, and same for the top. Since that would make the position of the volume panel always aligned with the the position of the volume buttons, which is what I thought the new commits would do.

This is what I'd expect the intended behavior to be on devices with official AOSP Pie, though I'm not sure, since again, I don't have a reference device to check.
[OnePlus 3 & 3T Cross Device Development] :
Why should one expect this? You don't need a reference device, because you have reference code. In https://android.googlesource.com/pl...android/systemui/volume/VolumeDialogImpl.java you can see that "always right relative to the device's orientation" is to be expected.

Considering the thumbs are (relative to the device's orientation) always at the side it doesn't make sensemto rotate the vol panel and put it at the top or botton. The vol panel should not stick to the vol buttons nommatter of orientation, but the panel should be easy to use (aka near your thumbs).
[OnePlus 3 & 3T Cross Device Development] Syssx:
Oh I see. If I'm not mistaken here, doesn't XDA have announcement function ? View attachment 4671134

It would be easier for end users (like me) to track new updates :)

This is just my suggestion, if you don't have time for this, just don't do it as just maintaining this ROM has to be really time consuming.
[OnePlus 3 & 3T Cross Device Development] :
This is devdb, isn't it? I'll look into.

On the other hand: I'll always add the last builds date to the thread title...
[OnePlus 3 & 3T Cross Device Development] knpk13:
If it is more convenient for you, DevDB can also host the actual builds instead of an external site. I don't personally have a preference, just mentioning it if you weren't already aware.
[OnePlus 3 & 3T Cross Device Development] :
I'm working on 16 for a week now. I sleep only 2 -3 h per night to get this up, documented and supported. the devdb fprm is always crashing with a timeout for me. in 50% of the cases it destroys the OP (last time when I tried to change alpha to beta) and I need to redo. If this whole thing with additional announcements is about "convenoent for me", I would say: leave me alone!

No offense meant, but I hate devdb.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I have no issue with it then. I'd say do what is most convenient for you, especially since you're doing it for free and don't even seem to have a donation link lol. I don't see any lapses in quality. Actually quite the opposite. I've never met a solo dev for any device who communicates so openly and does so much work for both upstream and his own personal builds, and for that, I'm very thankful. Might wanna get some more sleep though :P
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Kernel: 3.18.131; WireGuard 20121218; fix alert slider; vol panel left)

Build 20181223

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

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

Changelog (Last repo sync: 23 Dez 2018, 08:23:37 CET / 23 Dez 2018, 07:23:37 UTC):

current.pick.sh: "power: Handle launch and interaction hints for perf HAL platforms". — Nvertigo (HEAD -> nlos-16.0

current.pick.sh: fix derp. — Nvertigo (nvertigo/nlos-16.0

current.pick.sh: "SystemUI: allow devices override audio panel location". — Nvertigo

current.pick.sh: pie-hide-night-display. — Nvertigo

current.pick.sh: "configpanel: replace "Alarms only" with "Vibration"". — Nvertigo

op3/t: overlay: Relocate volume dialog to the left. — xyyx

Merge tag 'v3.18.131' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-16.0 — Nvertigo

WG: squash WireGuard-0.0.20181218. — 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] :
If you can use lte for data while callimg, volte is active. If data is 3g or not available at all while calling, you have no volte.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Ok thanks. I checked it and I can call with the JioCall app and use LTE data at the same time. So I'm guessing volte is working. I don't get why I have to use the app then and can't use my dialer. I'll check on stock OOS. Thanks and sorry about the OT!

Edit: btw Jio is an LTE only network, there's no 2g or 3g.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Try calling from your dialler app with lte, ie voice over lte, aka volte, if you can do that you have volte, if not and you see that the app is the only way to call, you are doing voip calls because thats what you are ending up doing..
[OnePlus 3 & 3T Cross Device Development] :
20190831 build available.

Changelog follows when web interface is working again - please understand that I don't like editing OP and announcement via xda-labs.