yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (upstreamed kernel; webview: 83.0.4103.96)

Build 20200607

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 [MENTION=9998549]Galiis[/MENTION]' directions in posting #6.

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

Changelog (Last repo sync: 7 Jun 2020, 12:45:12 CEST / 7 Jun 2020, 10:45:12 UTC):

Patch up: P_asb_2020-06. — Nvertigo

NLOS: track our own external/chromium-webview. — Nvertigo

chromium webview with los and bromite patches

Update to 83.0.4103.96. — Nvertigo

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

kernel: upstreamed to https://source.codeaurora.org/quic/...8&id=f6cb7400e83b9e09c3d63c96b33dbb2e19353fd5 including https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=ASB-2020-06-05_3.18

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] karakanto:
A lot of these look to be only for the full Chromium browser and not the webview, unless there's something I'm not understanding.
[OnePlus 3 & 3T Cross Device Development] :
If you read the bromite system webview related postings in this thread, you'll find that I wondered how to use/configure the features described here:

Since the original bromite system webview at the time of the mentioned postings broke the abillity to install/use third party webviews as user app, I denied to include bromite system webview.

I don't know exactly which patches are bromite webbrowser only and which patches are used if the webview is build, I've used all patches:

for i in $(cat ../bromite/build/patches_list.txt); do
git am ../bromite/build/patches/$i
done

This doesn't break anything - so I included the patches.

You can always install bromite webbrowser from f-droid (https://www.bromite.org/fdroid ) to use all features in the patches.

[MENTION=9350973]All[/MENTION]: if anybody knows how to use/configure/enable the bromite system webview features (like ad blocking) system wide as promised on the bromite system webview web page, please let us know.
[OnePlus 3 & 3T Cross Device Development] Yndi:
Hi,

I switched from VF Germany to T-Mobile Germany(MCC/MNC: 262/1) and VoLTE is explicitly advertised as feature. Sadly it does not work.

Anyone here with working VoLTE in Germany?

I found this module ( https://xdaforums.com/oneplus-3/how-to/x-s-s-s-t3858254 ) in some older comments. Is anyone still using that? with success? (I had to uninstall Magisk to install a banking app a few months ago and did not really need it since so it's not yet installed again.)

Thanks in advance and special thanks to nvertigo for the ongoing support!

OT: I find it funny that still many operators here don't support VoLTE yet VF and TM will deactivate 3G within a year...
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Afaik OP didn't include the necessary volte configuration files for a lot of operators. ("carriers have not distributed OnePlus with the appropiate settings for VoLTE + VoWiFi")

I stumbled upon a guide on a now gone forum, which had a guide to enable it but you need to tinker with the EFS partition. I think there's no other method to make it work.

https://xdaforums.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542

This a "copy-paste" of the guide but all the mentioned links are down (It's written for OP5, can't remember if the OP3 was different)

Edit: Maybe check Post #1312
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=4337368]Yndi[/MENTION]

I'm on mcc=262/mnc=02 (vodafone.de), and I havn't managed to get get volte working for three and a half years now. The sim's data plan definetly suppprts volte (tested with pixel 5 over two years ago). The mentioned op5 thread doesn't help - see my posting there.

This is also true for oos.

As a rule of thumb: if volte is working for oos it should also work for los/nlos. I've always thought mcc=262/mnc=01 (t-mobile/telekom) is working. So I'm a bit confused.

Is your sim working with volte on oos 9.0.x? If so, try comparing apns-conf.xml from oos 9.0.x to nlos-16.0 (or use oos' apns-comf.xml on your nlos setup).

Some thoughts:

Don't expect a volte icon on nlos/los: it has been removed.

Did you reset network settings after changing the sim.

What configuration files do you talk about, that I havn't included? I ship all carrier profiles that are present in oos (https://github.com/nvertigo/android...lob/nlos-16.0/proprietary-files.txt#L872-L895 ). If I missed some accidently, which are they?

EDIT:

You can just add

persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.volte_enalbed_by_hw=1

to /system/build.prop from within twrp (e.g. with vim after system is mounted). That's exactly what the mentioned module does. Don't forget to reset network settings after booting the edited build.prop. Let me know, if that works.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
I send you a PM with the files I have, I didn't use them myself (yet)

Edit: I just saw your Post on my mentioned OP5 Thread #1192. Maybe the stuff I send you is different
[OnePlus 3 & 3T Cross Device Development] :
Did you use "OP" in the meaning of "Opening Poster" (usual meaning on xda) or as OnePlus?

If the first: even of I patch my efs partition, I can't ship it (since efs partition as some individual information like imei). If the latter: let's use "OP" as "Opening Poster" and refer to OnePlus as OnePlus. ;)

Thanx for the pm. I was looking for that, because when I decided to try it at the beginning of 2020, hubo was down.

I'll try that as soon as I found out how to "copy as item file" works and I find a timeslice to do so. I'll report back
[OnePlus 3 & 3T Cross Device Development] meiser:
I switched from LOS15.1 to NLOS16.0 on my OP3, and VoLTE and VoWifi works out-of-the-box here. I just activated it in the settings. I use "oxygenos-9.0.6-no-alipay-firmware-3.zip" as firmware.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Aahh.. I used "OP" as OnePlus.

You're right though, I shouldn't use it like that :silly:

Edit: FYI

I tried the Magisk Module out of curiosity and it does nothing for me. (Magisk 20.4)

I can't find the mentioned additions to /system/build.prop after flashing it and the module doesn't show up in Magisk Manager.

Edit2:

As expected adding the lines manually to build.prop also doesn't do anything for me.

(edit build.prop > reboot > reset network settings > reboot)

Tested in O2 Network with WLAN and Data. (On Data it switches to 3G / H+ immediately when calling)

Can't say if those lines are necessary or not if the EFS is edited, but we will probably find out sooner or later.

Edit3:

In the Mobile Network settings there are these 3 options regardless of the build.prop edit.

Enhanced 4G LTE Mode (checked ✔️)

Wi-Fi Calling (Wi-Fi preferred ✔️)

Carrier Video Calling (checked ✔️)
[OnePlus 3 & 3T Cross Device Development] Yndi:
Well Vodafone(Germany) had a whitelist for VoLTE for the longest time and there was no Oneplus phone on it. The whitelist is gone for a while now, don't know what they are doing now. But Resellers and Callya users (what I was) don't get it.

Which network settings are you talking about? The APNs where already new on boot. I switched forth and back all the settings in the network seetings anyway, also forcing LTE network, which makes calling impossible. I also tried everything in *#*#4636#*#*. And I deleted the data of a bunch of apps which have carrier- or similar naming.

Don't know about OOS. I'm on nLOS since whenever.

I'll try to edit built.prop in recovery on the weekend. I don't have anything setup for a remote console session right now. It's been a while since I connected the phone to my PC for something else than photo transfer. And it's save to modify build.prop this way? I thought only installation scrips may modify /system in order to maintain integrity!?

Btw.: you had a Pixel 5 2 years ago!? I guess time traveling IS real. (Nexus, right!?)

Are you on T-Mobile Germany? You mean that "Enhanced 4G LTE Mode" - or do you have another setting?

But nice to know anyway!

Hmm, interesting, I thought O2 uses VoLTE for all LTE enabled phones.

I feel like it takes longer to switch networks on TM than it did on VF. It really annoys me.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Modifying the build.prop is pretty easy and you can always revert the changes. A modified system partition is not a problem for custom roms which don't rely on delta updates over OTA. (someone pls correct me if I'm wrong about this)

My guess is that a build.prop edit won't fix VoLTE though, I already tried and it did nothing. (on O2 Germany)

I think nothing works except the modification of the EFS partition (aka adding working VoLTE profiles for our operators)

OnePlus didn't include a lot of the VoLTE configurations from the mayor (German) operators for the OP3. (Maybe because the operators didn't provides OnePlus with them). I wrote about that in a few posts above already. At least that's what I extracted from all the posts about getting VoLTE to work and the EFS modification guide.

I sent nvertigo67 the files I saved from the guide (now offline) to check them but if you insist I can PM you the files too. From what I read it worked for many users but I didn't test it myself yet.

Messing up the EFS will make your phone a permanent brick though and it's not as easy as a build.prop edit!

Edit: At what point is this considered as off topic? If we assume that it affects every OP3 with every Rom (at least for people with German operators)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You can back up your EFS using TWRP. That way you can restore it if you make a mess of it.
[OnePlus 3 & 3T Cross Device Development] :
Yep. Nexus 5 from a friend of mine. op3t and Nexus 5 on los 14. One mcc=272/mmc=01 (t-mobile) and one mcc=262/mmc=02 (vodafone) sim. To see if my vpdafone sim really is volte enabled and to check if los 14 on op3t supports volte at all.

op3t: t-mobile working with volte; vodafone doesn't.

nexus5: both sims working with volte.

Settings->Reset Options->Reset Wi-Fi, mobile & Bluetooth

You are right. Just a note: persist props won't disapear after deleting them from build.prop, they are written to /data/property/persistent_properties.

For mcc=262/mnc=02 it won't help.

May I kindly rememner that the original question has been volte for mcc=262/mmc=01 (t-mobile). I'd like to sort out that one first, because I still think mcc=262/mmc=01 should work with volte out of the box.
[OnePlus 3 & 3T Cross Device Development] meiser:
Yes, T-Mobile Germany and the option you mentioned.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Are you sure VoLTE and VoWiFi works? Nvertigo said he removed the indicators in the statusbar for them.

Can you please check if you keep the LTE connection during calls or if it drops to 3G / H+ like it does for me, or force LTE and see if you can make a call?
[OnePlus 3 & 3T Cross Device Development] Yndi:
hmm, well I know that a build.prop modification is not too hard, but as stated I need to keep integrity/no root detected, otherwise my banking app will lock itself. Or is it as easy as dirty flashing and clearing GApps data to regain integrity? On the other hand I could backup, delete the banking apps, play around and restore, I guess.

You can send them over so I could decide on trying something or not. Especially since [MENTION=2911853]BillGoss[/MENTION] said we can backup /EFS.

OK. (typo? mcc262/1 for t-mobile).

For completeness: I'm using fraenk (the new offer from t-mobile) on a OP3T

Reset those options today, no change.

I don't know how this quote appeared because I did not write it, but yes, we are talking about t-mobile. I just added some information I knew about Vodafone, because it came up.

OP3 or OP3T?

With WiFi off it should be easy to check, right? Even without a special VoLTE indicator the phone should keep the data connection while calling while it does not on other network types.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Just to be clear, there isn't an actual partition called EFS. When TWRP backs up EFS, it actually backs up:

Partition Name EFS

sdf1 modemst1 efs1

sdf2 modemst2 efs2

sdf3 fsc efsc

sde7 fsg efsg

You can see this if you look at the TWRP recovery log after backing up EFS.
[OnePlus 3 & 3T Cross Device Development] meiser:
Very sure.

OP3, as written.
[OnePlus 3 & 3T Cross Device Development] fhloston:
VoLTE and telekom.de

I am managing 4 oneplus3 devices in my household.

I have done the android-hubo procedure (editing EFS) on mine and it works with telekom.de (mcc=262/mnc=01) VoLTE - previously with NLOS 16, now with LOS 17. LTE stays on during call. No Magisk module or buildprop editing.

The other 3 devices run LOS 17 and VoLTE does not work, device drops to H+ as soon as call is setup or call is coming in.

All 4 devices have SIM cards for telekom.de and VoLTE is enabled on them.

All 4 devices have 9.0.6 firmware.

HtH
[OnePlus 3 & 3T Cross Device Development] Niob24:
I did the efs changes for o2 and vodafone. Both worked perfectly fine [MENTION=4405529]nvertigo67[/MENTION] [MENTION=7452106]SenseSei[/MENTION] .

I still have the files on my computer and can give a few tipps, if you are interested.
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Ok at this point I think I can just share the files.

Thanks to everyone for the confirmation that it should work (if done correctly)

VoLTE/VoWiFi for OP3(T) [EFS Partition modding]

The HowTo is in german and I copied everything 1:1 from the original Hubo Forum. The guide and everything related was made/collected by xda member Jamal2367 so all credits goes to him!

Maybe someone can upload/host the files somewhere else because I don't know how long I'll keep my Google Drive link shared. (probably long enough)
[OnePlus 3 & 3T Cross Device Development] :
https://drive.google.com/drive/folders/1GJ_9bz_t4Y2aPDrl8mlQhSvGkuPzPQkl?usp=sharing
[OnePlus 3 & 3T Cross Device Development] Yndi:
Must have overread that detail.

---

Well I did the edit and it worked. Does it make sense to translate this!? I mean it's only the 3 german networks + one netherland's. But maybe this can work with other operators as well idk what the key steps are!?

A few more things for those interested: If I did it again I would do it file by file via right click. I sweat (blood and water as we say) through the hole process because my first file transfers with drag and drop did not always show all the files. Even after switching folders back an forth it would not show me the files I just droped in, and if so, sometimes with a wrong filesize.

And: Be aware that the sorting in this EFS Explorer is case-sensisive. Files/items with capital letters are at the top and after their 'Z' the rest it starts at 'a'.

I also had a bunch of transfer errors which simply needed a retransfer. Maybe like 10 for all those files. One more thing that got to my nerves was: One of the new "items" exists on /efs as "file" I deleted the file and transfered the item. It works as I said.

Lastly: I'm somewhat disappointed that when you disable mobile data (I do this sometimes to force WiFi at home) VoLTE does not work. Stupid. Reminds me of my brazil vacation: I turned off mobile data yet got charged 3€ for the LTE protocoll data because even without mobile data enabled the phone was in an LTE network and appearently the cound the protocoll data as well.

Cheers and thanks to all of this discussion!
[OnePlus 3 & 3T Cross Device Development] Yndi:
A few more information:

-VoWiFi works as well, needs a bit longer to connect, though - more or less like the fallback from LTE to another network type

-both, VoWiFi and VoLTE use some better speech codec, probably AMR-WB, so it's nearly like using an app when calling (if the called device spupports it as well)

-VoWiFi handover only works to VoLTE. If you loose your WiFi connection and do not have LTE the call drops

And for the end a question:

Does anyone know what this 'VT' option is that the guide says we should enable? And does it stay active after moving away from OOS again? I did a very quick and short google and Virtualisation is what comes up. If so it might have a performance impact!? If anyone has the time and plans on following this guide, maybe do a benchmark before and after (on OOS).

OT: First time in years I ran OOS. I really like the design and everything.
[OnePlus 3 & 3T Cross Device Development] :
Corona Warn App (Germany)

To everybody using nlos in Germamy:

Though I'm really keen on security, I think privacy and security is good enough for now in the implementation of German Corona Warn app (I still think the near future will show if additional fixes are necessary, and the hotline-tan solution is far from perfect). Only if you've been tested postive for SARS-CoV-2 and decidd to tell the app data is transfered to a server (maintained by Telekom in courtesy of Robert-Koch-Institute).

The German Corona Warn app is working flawlessly with nlos and gapps (nano or pico).

I'm using the German Corona Warn app for 32 h now. The time the device is active while screen is off increased from 1 - 2 %/h (w/o German Corona Warn app) to 5 - 6 %/h (with German Corona Warn app installed and active). The battery usage while screen is off (aka idle drain) increased from ~0.6 %/h to ~0.7 %/h - especially the battery consumption is good.

If the German Corona Warn app is/will be usefull is now a matter of our participation!

Considering this I want to encourage all nlos useres in Germamy to download, install and activate the German Corona Warn app. Please report positive SARS-CoV-2 tests in the German Corona Warn app.

Using the German Corona Warn app as intended is a contribition to the German population.

Take care of each other and thanx for considering my thoughts!
[OnePlus 3 & 3T Cross Device Development] mk_1996:
That's a very great initiative. i hope it doesn't mess with privacy like the one which our country(india) uses (Arogya Setu). Even after many local and french hackers pointing towards the obvious privacy issue of the app,the government is reluctant to listen and tells everyone that their data is safe. While it only took 4hrs for the hackers to get access to the info
[OnePlus 3 & 3T Cross Device Development] m3adow:
While I totally agree with you, I wanted to add that the Corona Warn App does not work with microG.
[OnePlus 3 & 3T Cross Device Development] rohan164:
Will this work for indian telecom providers?

As in text file it is mention only for German providers.

Anybody from india has tried this?

I am on los 17.1 los recovery locked bl.

I want to try this
[OnePlus 3 & 3T Cross Device Development] :
https://xdaforums.com/showpost.php?p=82890055&postcount=1596

BTW: Crossposting is considered bad manner. This is the nlos-16.0 thread, not the los 17.1 thread. Thanx for considering these before next posting.
[OnePlus 3 & 3T Cross Device Development] :
Recommended recovery: twrp-3.4.0-0

FYI:

The new twrp-3.4.0-0 seems to have no issues. I've changed the recommendation in OP to twrp-3.4.0-0.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (July security patch; kernel upstreamed; qcacld updated; webview83.0.4103.119)

Build 20200710

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 [MENTION=9998549]Galiis[/MENTION]' directions in posting #6.

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

Changelog (Last repo sync: 10 Jul 2020, 15:57:50 CEST / 10 Jul 2020, 13:57:50 UTC):

Patch up: P_asb_2020-07. — Nvertigo

Update chromium-webview to 83.0.4103.119. — Nvertigo

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

kernel: upstreamed to https://android.googlesource.com/kernel/common/+log/c8f4639f759e4c04b56d64f5a5d9b583eeb0569e including https://android.googlesource.com/kernel/common/+/refs/tags/ASB-2020-07-05_3.18 — [MENTION=7929484]MSe1969[/MENTION]

Merge https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0 LA.UM.7.6.r1-07800-89xx.0 into merge-16.0 — 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] :
Pretty amazing patchlist for the webview you are using [MENTION=4405529]nvertigo67[/MENTION].

As I am pretty happy with my LOS17 setup and NLOS Q is not available yet, would it be possible to use your webview in my LOS17 setup?

Was thinking of replacing the default webview.apk by your package, but before I even try, I was wondering if I can expect issues with it related to other patches you have added to your NLOS setup and are ofcourse not available in LOS17.