yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Build 20210305

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 without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files

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 and without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

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.

If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.

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

Changelog (Last repo sync: 5 Mär 2021, 15:43:32 CET / 5 Mär 2021, 14:43:32 UTC):

Update webview to 88.0.4324.207. — Nvertigo

see https://bitbucket.org/nvertigo/android_external_chromium-webview/src/master/patches/ for a complete list of patches

kernel: patches mentioned in https://source.android.com/security/bulletin/2021-03-01?hl=en(ASB 2021 02):

ANDROID: xt_qtaguid: Remove tag_entry from process list on untag — Kalesh Singh

WG: squash WireGuard-linux-compat-1.0.20210219. — Nvertigo

op3/t: gps: use ntp.org auto-selection. — Nvertigo

op3t: gps: XTRA: use https and check for version 3. — Nvertigo

op3/t: use https for downloading gps XTRA data. — Nvertigo

Patch up: P_asb_2021-03. — 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] :
Additionally in the download area you find a build with "unlp" (instead of "release" in it's name. This buils allows to use UnifiedNlp with gapps - no need to use microg (of course you can still use this build with microg, but this is not covered by this guide).

This build is exactly the same as the release build, but with these two commits:

overlay: use org.microg.nlp. — Nvertigo

op3/t: remove qualcomm location stuff for UnifiedNlp. — Nvertigo

If you decide to get rid of the qualcomm location spyware (some call it qualcomm location stack ;) ), follow these steps:

Flash nlos-16.0-20210305_152653-unlp-oneplus3t.zip just as you always do.

Install f-droid: https://f-droid.org/

From f-droid install "UnifiedNlp(GAPPS)" (don't open the app).

Enable high accuracy for location and allow scanning wifi and bt.

Reboot!

In f-droid search for and install (at least, you may want more):

https://f-droid.org/en/packages/org.microg.nlp.backend.nominatim/

https://f-droid.org/en/packages/org.fitchfamily.android.wifi_backend/

Start UnifiedNlp and grant all requested permossions.

Tap on selftest.

Tap on the text "Permission to access approximate location". Don't tap on the checkbox. Grant all requested permissions.

Go back to the UnifiedNlp main page.

Enable the wifi backend in "Configure location backends".

Enable the nominatim backend in "Configure address lookup backends".

Reboot!

Start UnifiedNlp and tap Self-Check. All five checkboxes are checked now. Ignore the messages at the bottom stating there's no last known location and no location update - it's working.

Remember, that the wifi db is maintained locally on the device. I order to allow adding wifis to this db, gps needs to be active. Using already added wifis doesn't require gps (Battary saving location mode).
[OnePlus 3 & 3T Cross Device Development] :
@nvertigo67

This should be coming from the very next boot, white led freeze > pressing power+voldown+release both after warning bootloader then waiting (not pressing any) until it's booted to recovery

could you.. take a look? This is the 2nd time crash since march build
[OnePlus 3 & 3T Cross Device Development] :
Config?

Something about BassBoost seems to crash the kernel. This doesn't seem something shipped with nlos.
[OnePlus 3 & 3T Cross Device Development] :
I haven't found the exact way to reproduce it, I'm not sure about the 1st time, but the 2nd it was while watching yt.

No mods, only magisk for safety net and 3 modules, systemless hosts, wireguard, and yt vanced. March build, pico gapps.

It's a relief tho, i thought it was my emmc was done cause i read (blindly) many storage errors..

I'll post again if i found any leads
[OnePlus 3 & 3T Cross Device Development] :
JFYI:

The update will be delayed, due to some issues with repopick I havn't resolved, yet. I 'm working on it - I did not forget the April's update!

EDIT: fixed. Waiting for webview to finosh building. Updated rom probably tomorrow!

EDIT2: Rebuilding webview with yesterdays and todays patches (building webview takes 15 to 22 h, depending on the amount of changes). Updated build will be ready tomorrow.
[OnePlus 3 & 3T Cross Device Development] :
Build (nlos-16.0-20210411_080147-release-oneplus3t.zip) finally finished. Upload successfull. Patched up to asb 2021-04. Webview updated to 90.0.4430.59. Download available at the usual location. Detailed changelog and announcement post will follow.

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] MSe1969:
In many cases and for many devices, removing encryption is a pre-requisite to flash a Custom-ROM, e.g. if you are on Stock ROM and want to flash a Custom ROM or in some other cases, you want to upgrade from a previous Android release and encryption isn't compatible. In those cases, it is obvious, that you need to remove encryption, before you can flash a ROM.

Same applies, if it is recommended to "re-flash" the ROM after removing encryption - then also quite obvious in regards to the sequence. In general - this practice isn't wrong; even if you are unsure, this might simply be a good idea to be on the safe side.

EDIT: In all cases, where the flash process would need to access the /data partition, this partition needs to be accessible, and removing encryption could be necessary to make it accessible, if encryption isn't compatible.

If however you simply would like to remove encryption (and there is confirmed no necessity to re-flash the ROM), you format /data in recovery, reboot recovery and reboot the OS. If you just want to flash a ROM, you flash the ROM and don't tamper with the /data partition. Hence, if the two activities are entirely unrelated to each other, but you simply feel in the mood to do both, while you are in recovery, then it does not really matter, what you do first.
[OnePlus 3 & 3T Cross Device Development] :
Build 20210509

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 without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware without alipay and soter files

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 and without alipay and soter files

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster and without alipay and soter files

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.

If you want to use Alipay with fingerprint authentication, follow @Galiis' directions in posting #6.

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

Changelog (Last repo sync: 9 Mai 2021, 10:22:49 CEST / 9 Mai 2021, 08:22:49 UTC):

Update webview to 90.0.4430.204. — Nvertigo

see https://bitbucket.org/nvertigo/android_external_chromium-webview/src/master/patches/ for a complete list of patches

kernel: patches mentioned in https://source.android.com/security/bulletin/2021-03-01?hl=en(ASB 2021 02):

tty: Fix ->pgrp locking in tiocspgrp() — Jann Horn

WG: squash WireGuard-linux-compat-1.0.20210424. — Nvertigo

Patch up: P_asb_2021-05. — 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] :
Webview considerations

Matters of fact:

I've upgaded my build host to glibc-2.33, which deprecates mallinfo() for mallinfo2().

chromium webview (and therefor bromite) relies on mallinfo() and doesn't build on a host running glibc-2.33.

Using the los chromium webview prebuilts drops all additional bromite webview patches (of course).

Using the bromite webview prebuilts doesn't allow to select additionally installed webviews (like https://play.google.com/store/apps/details?id=com.google.android.webview or https://play.google.com/store/apps/details?id=com.google.android.webview.beta, etc.) in settings.

I hope glibc-2.33/mallinfo2() will be supported by chromium/bromite some day, but which prebuilt webview should I ship in the meantime?
[OnePlus 3 & 3T Cross Device Development] MSe1969:
As you know, I ship the Bromite webview in my builds. So far, nobody has complained about the fact that you can't select other installed webviews. I think selecting different webviews is truly a 'developer option' (to try things out) and nothing, a regular user would need normally... Further, I haven't so far ever experienced any Bromite webview bug affecting usability, with the exception of twice a nasty Chromium bug (which had affected all webviews including Bromite). As you have started shipping own webviews for a reason (as opposed to simply using the LineageOS stuff), Bromite would come closest to your intention, IMO
[OnePlus 3 & 3T Cross Device Development] :
@MSe1969:

I've just copied the bromite prebuilds over the prebuits in my repository. I'll try again with your Makefile (LOCAL_OVERRIDES_PACKAGES) and the original filesnames of the bromite prebuilds. Thanx for the input!
[OnePlus 3 & 3T Cross Device Development] :
The term "normally" in computing generates nights of work... ;)

My policy for nlos has always been not to include stuff that collides or breaks native features.

To illustrate the problem:

First pic: bromite prebuilts (no matter if I use your Makefile or mine)

Second pic: los prebuilts

Third pic: my last self build prebuilts with bromite and los patches
[OnePlus 3 & 3T Cross Device Development] MSe1969:
:) - I like your "computing meaning" of the term "normally" (and I agree). I've also well understood your dilemma.

In fact, you need to decide, what is the "least evil" for you as a temporary work-around

- Not upgrade webview this month

- Use LineageOS stuff and abandon the patches, you have added for better data privacy

- Use Bromite and hence block the option to try out e.g. beta builds (which, in my opinion -despite "breaking" the possibility of switching between webview builds - is the 'best' of the options)
[OnePlus 3 & 3T Cross Device Development] Yndi:
Although I do not fully understand the all possible problems that might arise, I always thought this ROM should use the privacy enhanced Bromite WV. But giving users the possibility to easily use another one is surely a decision of freedom.

Two questions come to my mind however:

- Bromite WV would have to be manually updated (if one doesn't use F-Droid/gets the update via your ROM update)?

- Are troubles with the ROM update to be expected when switching system WVs?
[OnePlus 3 & 3T Cross Device Development] :
After thinking one more night on this, I agree. So:

If anybody depends on selecting other installed webviews, let me know - otherwise the next build will be shipped with bromite webview prebuilds.

Yes. But you can't update from f-droid. You need to manually download, manualy generate a arm/arm64 multilib package and follow the bromite instructions for replacing the rom-shipped webview - it's easier to build an updated rom... ;)

Depending on the app using system webview you may need to update your login data. Otjer then that I've never expirienced any issue when changing the webview in the build - and I did so quite some times... ;)
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Sorry, but I am afraid, that I have to object here:

The Bromite repo is "plugged in" as external repo and the apk uses Bromite's signature (it is not signed with F-Droid's signature), so if you use the prebuilts from Bromite, as I do in my repository, or you directly download from bromite.org, it works w/o issue.

The instruction to replace webview assumes, that you don't have Bromite, yet - but updating works w/o issues.

However, I don't recommend it and advise to wait for the ROM update, otherwise, you may need to uninstall the update before flashing the new ROM to avoid issues caused by the new ROM's apk being newer than your installed update on the /data partition.
[OnePlus 3 & 3T Cross Device Development] Rammit:
Bluetooth not connecting to car system, earphones etc.

Pl find the logs.

https://drive.google.com/file/d/1rNP0vs9gImHvPQ10DGP-wcXKKL8gvZSH/view?usp=drivesdk

Disabled sub overlays...tried back it worked. Enabled Sub overlays back yet it works...don't know what is the role of sub overlay on Bluetooth connectivity
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (devopts: remove Night mode; PI: add version on update; kernel: wlan)

Build 20181230

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: 30 Dez 2018, 11:09:07 CET / 30 Dez 2018, 10:09:07 UTC):

current.pick.sh: Allow adjusting screen density to smaller sizes. — Nvertigo

current.pick.sh: fix derp in pie-qcom-wfd picks. — Nvertigo

current.pick.sh: update FDE picks. — Nvertigo

hotfix.xml: remove cryptfs_hw; readded upstream. — Nvertigo

NLOS: track our own PackageInstaller. — Nvertigo

Settings: remove "Night mode" from Developer options. — Nvertigo

Show versions when installing or updating packages — ezio84

Revert "Android.bp: Initial header export bp for Android (qseecom only)" — Ethan Chen

arm64/configs: op3: remove unused configs for Bluetooth — Ecco Park (los/lineage-16.0

ANDROID: ARM64: smp: disable preempt in backtracing across all cores — Wei Wang

op3: make savedefconfig — dianlujitao

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] hauckk@sfreserves.org:
Happy holidays

Thanks for this great stable rom!

Just an FYI

I dirty flashed from lineage is 15.1 official nightly 12-30 to nlos 12-30 only issue I had was Google fi app had to be deleted and reinstalled kept crashing on first boot of nlos 16.0 I haven't found any other issues yet so dirty flashing worked for me
[OnePlus 3 & 3T Cross Device Development] hauckk@sfreserves.org:
I use swift black substratum theme and it themes

blue tooth system app so maybe substratum themes that theme system apps broke it somehow idk, to be honest
[OnePlus 3 & 3T Cross Device Development] :
How do you know? The last user doing so was always asking on each glitch if other users expirience that, too. We can't know if it's working or not. Sadly, the userdata partition isn't signed with an production key since 15.1, otherwise the flash you did, wouldn't even be possible with an error message like "incompatible data". This wasn't removed by intent, but has just never been reeimplemented.

If you report a bug (or any other user beliving "dirty flashing across different roms" is working) which is related to that dirty flashing across differnt roms, not only my time is wasted, but the time I spend on that "dirty flashing across different roms"-bug I can't spend on developing or supporting users sticking to OP. Everybody is effected.

Frankly, you failed twice: the first failure was not sticking to OP, the second failure was posting the (not verifyable) claim "dirty flashing across different roms" is working...

[MENTION=9350973]All[/MENTION]: please stick to OP. This one has taken 25 minutes of my "rom time".

I guess it's just about saving the second reboot recommended in the swift dark/black instruction panel. I've also expirienced hickups on some themes (not with swit dark/black), if not uninstalled before a dirty flash...

What seems to be a shortcut will waste more time then it saves at the end of the day... ;)

Not all themes are pie compatible (even if the ps page of the theme states so). The swift themes behave realy nice with pie, others (i.e. DNA project) don't.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
[MENTION=4405529]nvertigo67[/MENTION]

Here's what you should help you add gaming tile into QS panel. For now, I have switched back to OOS as i was having 30-40% less battery than OOS on the balanced profile. No custom kernel, no custom mod or any other BS. Observations were made after 5 total cycles. Anyways, I'll switch back in future maybe as this is was the most stable and bug-free ROM I tried.
[OnePlus 3 & 3T Cross Device Development] :
The real links are lost (I guess you copy'n'pasted the shortened displayed link, instead of the link address).
[OnePlus 3 & 3T Cross Device Development] abhibnl:
My apologies. Here is second try:

https://gitlab.com/HolyDragonProjec...mmit/6e32ba915f20c38dd2f8a29432edb5606c6a0ba5

https://gitlab.com/HolyDragonProjec...mmit/2d71e9e507c0d1eb64042804e2ddba525693a25d
[OnePlus 3 & 3T Cross Device Development] karkiankit:
Happy new year to all of you

Can this room add AOSP ui option. So that we can switch from pixel ui to asop ui.
[OnePlus 3 & 3T Cross Device Development] :
You may want to elaborate this, please? I've no clue what you are talking about and the screen shot doesn't help me to understand.
[OnePlus 3 & 3T Cross Device Development] karkiankit:
Sure ill try to explain

I came to know that the round elements of quicksettings and notifications are from pixel phones amd AOSP pie doesnot have those round corners. As you can see on every rom notification are rounded along worh quick settings.

In last update havoc os has added an option to choose between Pixel UI or AOSP ui

When Pixel UI is selected then the QS and Noticifation have rounded corner

When AOSP ui is selected then theres no rounded corner in notification and in QS as shown in the screenshot

Hope you understood , english is not my native language
[OnePlus 3 & 3T Cross Device Development] karkiankit:
With Pixel UI option : You cam see that the edges are round

With AOSO ui option : Edges are not round like in Oreo/Nougat 2nd screenshot
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9350973]All[/MENTION]:

For yours and you: happy new year!

No reason to apologie - happend to all of us... ;)

Sadly, it's the same problem I had merging some similar commits to 15.1: this two commits relay on other deep changes in the frameworks. Those other commits are foreign rom related (this time Havoc ports to holydragon) and not compatible with lineage:

frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/GamingModeTile.java:109: error: cannot find symbol
Settings.Secure.HARDWARE_KEYS_DISABLE, 0) == 0;
^
symbol: variable HARDWARE_KEYS_DISABLE
location: class Secure
frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/GamingModeTile.java:112: error: cannot find symbol
Settings.Secure.HARDWARE_KEYS_DISABLE, 1);
^
symbol: variable HARDWARE_KEYS_DISABLE
location: class Secure
frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/GamingModeTile.java:115: error: cannot find symbol
Settings.Secure.HARDWARE_KEYS_DISABLE, 0);
^
symbol: variable HARDWARE_KEYS_DISABLE
location: class Secure
frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/GamingModeTile.java:162: error: cannot find symbol
return MetricsEvent.HAVOC_SETTINGS;
^
symbol: variable HAVOC_SETTINGS
location: class MetricsEvent
4 errors

Since I'm not willing to port Havoc settings, the gamig mode tile needs to be rewrittwn for lineage, which is behind my scope.
[OnePlus 3 & 3T Cross Device Development] :
The rounded corners are android 9 native. It's in the aosp pie sources. It's not pixel vs. aosp - it's pie vs. oreo.

I won't remove the rounded corners. (Before you ask: I won't make it switchable, because I don't want such "cosmetics only" stuff in the rom itself, this should be left to themes.)
[OnePlus 3 & 3T Cross Device Development] knpk13:
And this why I don't like a lot of other custom roms. They labelled the native pie style as the pixel style , and Oreo style as native pie style. Unnecessary feature and bloat, considering you can just use a theme as you said.

---------- Post added at 12:21 PM ---------- Previous post was at 12:16 PM ----------

I'm in the process of trying to figure out Tasker myself, but from what I know, what you want can be accomplished (as can much more complex tasks). If you're not able to create a script, perhaps there's a thread where you can request a Tasker script from someone else based on your specification.
[OnePlus 3 & 3T Cross Device Development] Halamadrid:
Can someone please share the link for the Op3 file? i am only seeing the op3t file through the link.
[OnePlus 3 & 3T Cross Device Development] :
What link are you talking about? There are many links in OP. If you talk of the rom's flashable zip filename: it's a unified build.
[OnePlus 3 & 3T Cross Device Development] Halamadrid:
yeah, the link for the rom.

i was getting error 7 while flashing the file.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Use the latest firmware
[OnePlus 3 & 3T Cross Device Development] :
Read the complete error message (the two lines before the red error 7 line). I can't make it easier.

BTW: los declined to merge this https://github.com/nvertigo/android...860d086#diff-62814b147a6a79a0c54ad012c51b89d8 because nobody would read it anyway, because no one is reading error messages... Sadly they were right.
[OnePlus 3 & 3T Cross Device Development] :
To my understanding you can only use the original bromite signature with the original apk files. But since your Makefile mangles the arm, arm64 and x86 original files in a new multiarch apk, this new file can't be signed with bromites original key (as long as you don't have access to the private part of the key, of course). To my understanding keeping the original key with "LOCAL_CERTIFICATE := PRESIGNED" does only work for unchanged apks and jars, but I may be wrong.