yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] MSe1969:
I have used the following setup to test:

https://github.com/ViRb3/wgcf - I downloaded the binaries in the releases section to my Linux PC and executed the two commands as indicated in the README to get the wgcf-profile.conf file generated.

Basically, this generates a random "account" for Cloudflare 'Warp' and a wireguard config file. I copied that config file to my device and imported into the WG app. Good enough for testing.

In fact - it "works", also with the newest kernel (you switch on, are routed through clownflare and are able to connect to the internet), but . . .

. . . it lags, "waves" of slower speed interrupted by 2-3 second lags, also in regards to your entire phone's reactivity

. . . you cannot shut down the WG tunnel through the app

. . . you can force-close the WG app and then it's shut down

. . . but then your device starts to behave weirder, and if you attempt to start the WG tunnel again, you have no connection to anywhere any longer and you will see that your device "begs for a reboot" (unless you have a masochistic attitude ;))

In general - I will be glad to fix it, if I find the solution or if somebody points me to it. However, in fact, I find the approach of having to grant root access to use a native kernel feature a bit disturbing.

And, since WG also works fine in the WG app as "regular" non-root VPN, I

do not

consider the possibility to simply drop the native WG support again from my kernel as "the end of the world" . . .
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=7929484]MSe1969[/MENTION]: Ok. I can reproduce the issue the way you'be described. Did you check the previous kernel?

I'm low on time tomorrow and Wednesday. What I'm fpund so far: the wg, wg-quick and ip processes all issued by the wireguard app are hanging forever.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Yes - as described in my thread: I have flashed the boot.img from my previous build and all worked fine again.
[OnePlus 3 & 3T Cross Device Development] :
I've accidently deleted my logs from yesterday. No problem, I thought. Just fired up the wireguard cloudflare wrap tunnel to get the log, waited for 5 minutes and disabled the tunnel again. To my complete surprise the tunnel ended succesfully, no hanging processes - it was just working... (I don't want to know how my face expression has been in this second).

What has changed?

After my test from yesterday, I thought about these wise man's words:

I've always run wg as root (though I've theoretically known that wg with kernel module doesn't need root access, I've always allowed root for wg if rrquested out of a habbit). After reading and realizing the above, I revoked root previlegs for wg and rebooted the device yesterday before going to sleep...

The wgcf-profile tunnel is running now for ~60 min withou any lagging and/or increased batt drain.

Can anybody confirm this, please?

Note: This is only a workaround, and I've not the slightest clue, which kernel commit effects wg to trigger the lagging when root access AND kernel wg support is present at the same time.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I also used to think you didn't need root to use the kernel backend, but it looks like that isnt true. The WG app seems to need root to use the kernel backend (in addition to the kernel commits). If you don't grant root, it falls back to the userspace backend, which does not use the kernel backend (and also doesn't have the issue you're trying to reproduce, so there's no lag). The about section in the WG app shows which backend is being used. I am unable to get it to use the kernel backend without granting root.

I'm pretty sure mse1969 was trying to say the same thing in the section you quoted.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Exactly! I learned that in a private conversation with knpk13.

In fact, the following applies, based on my observations (haven't really studied the source code of the wireguard app):

Case A:

No WG kernel support present. It does not matter, whether you grant root access or not. The WG app simply triggers an 'ordinary' VPN channel, which you will find in the VPN section in network settings and when enabled, you see the "key" icon in your notification bar indicating an active VPN session. This happens, because the WG app brings its own WG user-space non-root module along. This setup works on any device.

Case B:

Kernel provides native WG support, but you

don't

grant root to the WG app. Result:

See case A

!

Case C:

You have granted root access to the WG app. The WG app calls the command cat /sys/module/wireguard/version to see, whether native wireguard support is present and what version.

If it does not find anything, see case A. If it finds, what it is supposed to find, it executes the wg binaries to establish the WG tunnel via the kernel.

The result is, that connections are directly routed and you don't see any VPN symbol in the status/notification bar. This is supposed to be faster.

Additional observations:

The wg binaries are executed from here: /data/user/0/com.android.wireguard/code_cache/bin/wg and /data/user/0/com.android.wireguard/code_cache/bin/wg-quick

In the logs however, a comparison is made to see, whether those binaries are also present in /system/xbin, not sure, why this is done
[OnePlus 3 & 3T Cross Device Development] :
This is done for the "Install command line tools" settings item: if wg and wg-quick are present in /system/xbin the item is grayed out, if not the item is selectable.
[OnePlus 3 & 3T Cross Device Development] MSe1969:
Wireguard Kernel Fix

I managed to fix the WireGuard issue, see this post for more details.
[OnePlus 3 & 3T Cross Device Development] :
WireGuard support in kernel

Does anybody need a fixed kernel?

I'm planning to build an updated webview and push a new rom build at the coming weekend. If anybody wants a boot image with wireguard fixed before the weekend, drop me a note.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Kernel Wireguard Fix; Webview: 86.0.4240.99)

Build 20201018

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: 18 Okt 2020, 10:29:44 CEST / 18 Okt 2020, 08:29:44 UTC):

Update webview to 86.0.4240.99. — Nvertigo

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

kernel: Revert "net: disable netpoll on fresh napis" — [MENTION=7929484]MSe1969[/MENTION]

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] :
Update (kernel upstreamed; webview: 86.0.4240.181)

Build 20201108

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: 8 Nov 2020, 10:38:17 CET / 8 Nov 2020, 09:38:17 UTC):

Update webview to 86.0.4240.181. — Nvertigo

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

kernel: upytreamed to https://android.googlesource.com/kernel/common/+/615b80a592975c54d01062854ea2e7f69ca0fb20 which includes https://android.googlesource.com/kernel/common/+/refs/tags/ASB-2020-11-05_3.18 — [MENTION=7929484]MSe1969[/MENTION]

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] :
The new interface is unusable for me. I can't even jump to the last page. I can't find e.g. posting #2.

I can't use labs anymore on my mobile.

Hopefully it get fixe in the future. For now I stop using xda (no support; no announcments) and look back in some weeks.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
When I first checked about four hours ago, I also couldn't get to the last page of a thread, but now it seems to be working.

Change is always difficult at first until one becomes used to the new ways.
[OnePlus 3 & 3T Cross Device Development] knpk13:
The new app is out. But it sucks. It's just a webview wrapper for the mobile site. The upside is that the site is a lot faster, but I can't find any thread search option and the appp feedback thread is full of issues.
[OnePlus 3 & 3T Cross Device Development] xdam57733:
Took me a while to find out as well, but search target can be chosen like this:

You click the magnifier and then you need to click on the gear icon. Then you can choose from a drop down (Everywhere, Threads, This thread, ...)
[OnePlus 3 & 3T Cross Device Development] :
First of all: Updated build will be shipped later today.

Now some lazy questions:

For pc-browser view: how do I jump from the forums thread view directly to the first new (aka unread) posting? How do I remove the menu on the left side (IMHO waste of space)?

For the new mobile app: how do I switch to a dark theme? How do I change the font size?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
User icon on bottom bar>Settings>Use system settings>on (if on Android 10+)

or

User icon on bottom bar>Settings>Use system settings>off and then choose Dark mode
[OnePlus 3 & 3T Cross Device Development] knpk13:
I found the answers to all those questions except the moving directly to first unread post, in this thread.

[CLOSED] [Index] XDA 2021: Navigating the New Forum App

Note: 29 Feb 2024 Because the Official XDA (Playstore) app no longer is supported Please see these other options. [UNOFFICIAL] XDA Forums App by @ZG089▼ Fixed version of Official XDA App by @dr.ketan [App][5.0+] ReLabs - Unofficial XDA Client...

xdaforums.com

@xdam57733 mention autocomplete is nice, but I can't find this magnifier icon you talked about for in thread search. Do you have a screenshot of where it is?
[OnePlus 3 & 3T Cross Device Development] :
Arrgh...

As you may know, I'm using the upload to test wifi-tethering of the new build. Today it was so damn slow, I thought tethering has been broken by the update (estimated time over 2 h; some complete stalls), after deciding to upload via my homes wired connection (which is working great, except for gdrive today) the estimation is the same... stay tuned...
[OnePlus 3 & 3T Cross Device Development] :
Upload completed. OP ****ed up (Enter sends the edits instead of adding a linefeed at the cursor's position.

I've updated webview @MSe1969 updated the kernel to https://android.googlesource.com/kernel/common/+/refs/tags/ASB-2020-12-05_3.18. zip amd md5 can be found in the usual location. Sorry, but I don't like making a nice OP and a nice posting currently with this new &$)!@%.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
See screenshots

View attachment 5156471View attachment 5156473
[OnePlus 3 & 3T Cross Device Development] knpk13:
Looks like that's only available on the website for now. This is what I get when I click on the magnifier icon in the app (the icon is available in the home and forums tab, but it's not available when I view a thread).

Edit: also found a search option tucked away in the hamburger menu for redundancy, but its not in thread search either.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, search in thread is only available in the web browser at the moment.
[OnePlus 3 & 3T Cross Device Development] :
Updated uploaded. After editing the OP and announcement, the web ui throw away my edits. So again no announcment. Anyway: build is in the usual location. webview, wireguard and asb updated.
[OnePlus 3 & 3T Cross Device Development] :
Are you also ready to move to 10 @nvertigo67 ?

I just wish the enchanced call block function will still available, anything else i can make the adjustment.
[OnePlus 3 & 3T Cross Device Development] :
Answered many times. Search the thread.

Call blocking is in the shipped phone app: three dot menu->Settings->Call blocking
[OnePlus 3 & 3T Cross Device Development] :
For the homegrowers:

Python 2.7 vs. 3.x

Python 2.7 is mandatory to build android 9 based roms. Most linux distros have droped or are about to drop Python 2.7 support. Though it's possible to keep Python 2.7, keeping it blocks other cruical system updates.

To get rid of this dilemma I've created a full-fetured Python 2.7.18 build:

GitHub - nvertigo/prebuilts_python_2.7.18

Contribute to nvertigo/prebuilts_python_2.7.18 development by creating an account on GitHub.

github.com

You can easily integrate this prebuild in your source tree, by adding something like this in your local manifests:

Add full-featured linux x86 64bit Python 2.7.18. · nvertigo/local_manifest@c54ec24

For building android 9 based nlos-16.0 on linux hosts running distros, which doesn't support Python 2.7 any more.

github.com

To use this prebuild Python 2.7 on a Python 3.x (and Python 2.7 free) build host, make sure to add the absolute path of the bin dir of the prebuild Python 2.7 as leading item of the PATH variable before sourcing envsetup.sh (your absolute path may differ from mine):

Use freshly added full-featured linux x86 64bit Python 2.7.18. · nvertigo/local_manifest@5c1074d

Use prebuilt Python 2.7 by adding "/usr/local/src/los16/prebuilts/python/linux-x86/2.7.18" as leading item in the PATH environment variable.

github.com

Now you can still build android 9 based roms without the need to have Python 2.7 installed on your build host.

Happy building!

EDIT: works for linux x86_64 - darwin isn't supported (but should work the same if you build your own Python on darwin.
[OnePlus 3 & 3T Cross Device Development] :
Build 20210207

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: 7 Feb 2021, 14:00:53 CET / 7 Feb 2021, 13:00:53 UTC):

Update webview to 88.0.4324.152. — 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-02-01?hl=en(ASB 2021 02):

WG: squash WireGuard-linux-compat-1.0.20210124 — Nvertigo

usb: dwc3: ep0: Return from handle_status if ep0_delegate_req succeeds — Udipto Goswami

msm: kgsl: Remove VM_MAYWRITE flag to restrict mprotect — Indira Biruduraju

current.pick.sh: use prebuilt python-2.7 instead of system python. — Nvertigo

Revert "current.pick.sh: system/nfc: SDCLANG-6: fix declaration." — Nvertigo

Add full-featured linux x86 64bit Python 2.7.18. — Nvertigo

Use freshly added full-featured linux x86 64bit Python 2.7.18. — Nvertigo

Patch up: P_asb_2021-02. — 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] phoberus:
@nvertigo67

Is battery calibration still necessary with newer Android versions?

I have installed a new original battery and sometimes at 1, 2 or 3% the smartphone suddenly runs out of power. When charging, I get a message for about 5 minutes that it needs to charge before it starts again.

I have calibrated it with an app in the Playstore, but that has done nothing. Could it still be the calibration?
[OnePlus 3 & 3T Cross Device Development] :
Calibrating shouldn't be needed. This sounds like wearing (do you know, when the replacement bat was manufectured?), or impatiendness: a new bat needs around 5 charging cycles to get to maximum performance.

As a last resource you can backup and delete /mnt/vendor/persist/bms/batt_info.txt (from twrp, if the device isn't rooted(*)) and reboot.

(*) you may mount persist manually in twrp. Persist partition is /dev/block/sda2.
[OnePlus 3 & 3T Cross Device Development] :
I mean this

It's not shipped by default on any rom based on the newest los/aosp, it's should be baked when building the rom as far as i know
[OnePlus 3 & 3T Cross Device Development] :
I've answered that:

See shipped phone app: three dot menu->Settings->Call blocking

Please check yoirself. You'll find:

numbers not in contacts

private callers

calls from payphones (they still exist)

unknown callers

This rom has enhanced call blocking since August of 2019! Remember that I always rebase my changes on top of the current los code base, to make it easier to check for nlos addotions (I've explained that many times over the last 4 years):

https://github.com/nvertigo/android_frameworks_base/commits/nlos-16.0 (4th commit) + https://github.com/nvertigo/local_manifest/blob/nlos-16.0/current.pick.sh + https://github.com/nvertigo/local_manifest/blob/nlos-16.0/current.pick.git.sh

I always use this script to rebase nlos additions: https://github.com/nvertigo/local_manifest/blob/nlos-16.0/update_repos.sh
[OnePlus 3 & 3T Cross Device Development] :
I explained about that feature isn't on any official los rom yet you answered about this rom, yea i know it sounds rude, but belive me, i'm shorts on words trying to explain this lol

What i mean is i wish it's on your

future

plan...

I don't know maybe you tried to answer for more broad people, but it's just a strange way to communicate you know

Just a suggestion, try to understand the words first, if you can't, there's no shame in asking for clarity

No need for reply though, i get it
[OnePlus 3 & 3T Cross Device Development] :
I really don't understand. What future plans are you asking for? What are you asking regarding the call blocking commit? If you ask in this thread, I answer for this rom. If you want answeres for other (official) roms, you need to ask in the other threads... I'm completely confused, now...
[OnePlus 3 & 3T Cross Device Development] :
it's your future, i don't know lol

I just predict that you'll never building this nlos 16.0 forever, so i'll ask in advance to consider the "feature" to be carried over

i'm not asking anything related to the call blocking commit

That's why i said "i'm shorts on words"

I mean to say "i'm sorry for bringing that up, but i can't think any better words to explain it to you"

Are we clear now, chief? :p
[OnePlus 3 & 3T Cross Device Development] :
I've answered that many times. But one more time: As long as asb patches for los/aosp and for the 3.18 kernel are availble, I'll build los16. One Exeption: if I change devices. I don't plan to change devices currently. My op3t is just over 4 years old, so I consider it nearly brandnew... ;) Honestly: as long as the battery is working (perhaps 15% wear by now) I see no reason to switch.
[OnePlus 3 & 3T Cross Device Development] :
I've already answered that too, i get it :p

People forget, and it's acceptable. Don't be annoyed
[OnePlus 3 & 3T Cross Device Development] :
Is anybody interested in a build ready to use UnifiedNlp alongside with gapps and without the need to use microg?