yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
These additional features are really mysterious. They are mentioned quite some times, but explained quite poor. The most detailed description on these is "the same features as bromite web browser has". If I look into the privacy features of bromite webbrowser, they all are configurable in Settings->Privacy. They are off by default and need configuration (i.e. secure DNS and adblocking).

Don't get me wrong, I appriciate your explenations and I'm always interested in privacy features. I'm still at the point of wondering what's the different/added features and how to utilize them (btw: secure DNS is much more fascinating, then adblockimg....)

BTW: I found an interesting comment in the nanodroid bromite zip: "# Bromite WebView needs to be installed as user app to prevent crashes" Confusing enough: the code folliowng the comment installs bromite wv as system app... The comment (without the following code) would explain, why you can update bromite wv, but I can't if the rom is compiled with bromite wv as system app.

The more information I get, the more confused I am.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (upstream: webview 79.0.3945.116; use QCOM loc. stack for fused loc.)

Build 20200115

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

Oneplus 3: OxygenOS 9.0.6 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.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

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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.

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

Changelog (Last repo sync: 15 Jan 2020, 10:53:50 CET / 15 Jan 2020, 09:53:50 UTC):

overlay: loc: add QCOM to Location Provider Names. — Nvertigo

overlay: loc: add QCOM fused Location Provider. — Nvertigo

overlay: config.xml: fix indent. — 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] :
UPDATE (WireGuard: 20200121; Webview: 79.0.3945.136; per app performance profiles)

Build 20200123

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

Oneplus 3: OxygenOS 9.0.6 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.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

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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.

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

Changelog (Last repo sync: 23 Jan 2020, 17:37:52 CET / 23 Jan 2020, 16:37:52 UTC):

current.pick.sh: "Update Chromium Webview to 79.0.3945.136". — Nvertigo

current.pick.sh: "Reimplement per-app performance profiles". — Nvertigo

WG: squash WireGuard-linux-compat-0.0.20200121. — 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] :
Slightly OT, but it's my thread...;)

Since so much people spreading nonsens and/or half baked information on "Error 7", I've added posting #5 for easier reference.
[OnePlus 3 & 3T Cross Device Development] vijay.ev:
[MENTION=4405529]nvertigo67[/MENTION] Master... Did you plan to move to Android 10 for op3/3t !??

Highly appreciate your hardwork :highfive:
[OnePlus 3 & 3T Cross Device Development] :
Currently I'm really enjoying to use a full featured, nearly glitch free rom without rebooting three times a day for testing. This may change at some point, but don't expect 17.1 in the near future.
[OnePlus 3 & 3T Cross Device Development] D3G0N:
Thank you for keeping pie relevant on this device. I do not mean to offend anyone by saying that the q roms out here are not exactly complete roms, but it is nice to use a recently updated rom with everything working as expected, and get meaningful updates. Every time I flash a relatively recently updated rom that just works completely, I feel like I got a new car. The last android 10 rom I flashed made my phone feel like a crashed audi. This rom makes my phone like a nice new tesla. Also thank you for all the useful information on the first page of this thread, very informative and nicely written.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Security Patches 2020-02-05; WireGuard 20200205; add PS/2/3/4 controllers)

Build 20200205

Attention, please:

I've added PS2/3/4 controllers to the kernel. I've no access to any of them. If you have hands on a PS2/3/4 controller test it and report back, please. Thanx in advance!

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

Oneplus 3: OxygenOS 9.0.6 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.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

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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.

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

Changelog (Last repo sync: 5 Feb 2020, 16:03:47 CET / 5 Feb 2020, 15:03:47 UTC):

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

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

op3/t: defconfig: enable PS2/3/4 controllers. — Nvertigo

Patch up: P_asb_2020-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] :
UPDATE (kernel upstreamed to caf LA.UM.7.6.r1-06700-89xx.0)

Build 20200211

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

Oneplus 3: OxygenOS 9.0.6 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.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

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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.

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

Changelog (Last repo sync: 11 Feb 2020, 11:34:46 CET / 11 Feb 2020, 10:34:46 UTC):

Merge tag 'LA.UM.7.6.r1-06700-89xx.0' from https://source.codeaurora.org/quic/la/platform/

vendor/qcom-opensource/wlan/qcacld-2.0 into linux-stable/merge-16.0 — Nvertigo

Merge tag 'LA.UM.7.6.r1-06700-89xx.0' from https://source.codeaurora.org/quic/la/kernel/

msm-3.18 into linux-stable/merge-16.0 — Nvertigo

current.pick.sh: "Refactor AUDIO_BECOMING_NOISY broadcast handling". — 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] knpk13:
What exactly does this do?
[OnePlus 3 & 3T Cross Device Development] :
Upstreaming against caf project msm-3.18 has some advantages, especially since kernel.org has droped the support for 3.18.y.

I've just added:

to OP. Hopefully this does not only clarify my intentions, but also allows to check my merges against upstream.

I will not list all contained single commits, but only the actual merge commit like I've done with kernel.org patches. If one is interested in all single commits, please check my kernel repository and the upstream sources as mentioned above.

Just to show the dimensions: when updating from LA.UM.7.6.r1-06700-89xx.0 to LA.UM.7.6.r1-07000-89xx.0 (next build) there will be 102 single commits. Though I maintain them in the git (no squashed commit), I don't think it makes any sense to show them in the changelog. The changelog will only show the merge commits:

Merge tag 'LA.UM.7.6.r1-07000-89xx.0' from https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0 into linux-stable/merge-16.0 — Nvertigo

Merge tag 'LA.UM.7.6.r1-07000-89xx.0' from https://source.codeaurora.org/quic/la/kernel/msm-3.18 into linux-stable/merge-16.0 — Nvertigo
[OnePlus 3 & 3T Cross Device Development] knpk13:
Oh ok, that makes a lot more sense now. Thanks, I honestly haven't seen a more communicative dev than you before. I didn't know CAF would be able to support a kernel if kernel.org dropped it.
[OnePlus 3 & 3T Cross Device Development] karakanto:
It's special in this case since the mainline kernel.org maintainers are still maintaining it, just only for AOSP/CAF.

https://lwn.net/Articles/788688/
[OnePlus 3 & 3T Cross Device Development] :
I've tried to merge https://android.googlesource.com/kernel/common/+log/refs/heads/android-3.18 and https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=ASB-2020-02-05_3.18 the complete weekend. Sadly, after finally getting the source to compile, it boots straight into a kernel panic. (If somebody is seriously interested in debugging/fixing this - I've to admit it's behing my abilities/knowledge - drop me a note: I can push my merges for https://source.codeaurora.org/quic/la/kernel/msm-3.18/tag/?h=ASB-2020-02-05_3.18 and have a nice set of pstore files.)

For now I stay with the LA.UM.7.6.r1-?????-89xx.0 tags.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel:LA.UM.7.6.r1-07000-89xx.0; WireGuard:20200215; Webview: 80.0.3987.99)

BUILD is pulled! It hasn't current.pick.sh applied. Making new build. Stay tuned.

Complete and fully working 20200218 build ready for download! Sorry for the inconvenience.

Build 20200218

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

Oneplus 3: OxygenOS 9.0.6 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.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

Oneplus 3: OxygenOS 9.0.6 firmware with 5.0.8 bootloader and keymaster

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.

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

Changelog (Last repo sync: 18 Feb 2020, 11:21:51 CET / 18 Feb 2020, 10:21:51 UTC):

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

op3/t: defconfig: add "LA.UM.7.6.r1-07000-89xx.0" to LOCALVERSION. — Nvertigo

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

Merge tag 'LA.UM.7.6.r1-07000-89xx.0' from https://source.codeaurora.org/quic/la/platform/

vendor/qcom-opensource/wlan/qcacld-2.0 into linux-stable/merge-16.0 — Nvertigo

Merge tag 'LA.UM.7.6.r1-07000-89xx.0' from https://source.codeaurora.org/quic/la/kernel/

msm-3.18 into linux-stable/merge-16.0 — Nvertigo

current.pick.sh: "webview_80.0.3987.99". — 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] :
OT: Android Auto

Completely OT:

I've a new (used) car since three weeks. This car is equipped with an Intellilink R4.0 supporting Android Auto (AA). It's working completely flawlessly with nlos on op3t.

I've used it for 2 hours, before I can't stand this software combo any longer.

Downsides:

Need to use usb cable. This suckz, because:

No dash charging.

I can't use it w/o cable, e.g. if the device is fully charged.

I can't use my favorite nvigation app, but I'm forced to use maps or waze. Besides the fact that both apps are generally inferior I see these drawbacks especially:

Maps: doesn't work reliable for routing if g's location services are disabled (that's a show stopper).

Waze: doesn't like running in German, when phone's system is set to English (I run my device mostly English, because of my suppport in this thread is English: screenshots, paths in setting; and I'm to lazy to switch languages).

Both: less additional information (e.g. traffic, parking).

Software updates for Intellilink arn't supported (need to additionally enable hotspot on op3t and connect Intellilink to it).

limited support for audio apps (e.g. no lastfm, Prime Audio, TumeIn - list is probably endless, these are the three I'm missing)

If using an AA audio app, the traffic news from Intellilink fm radio is suspressed (if I use bt for listening e.g. TuneIn, it's muted and the fm traffic news are played). Show stopper for me.

Advantages:

Larger Display and larger buttons.

Bottom line: as all gapps AA suckz. After all the hype on AA (and all the complains on not workimg AA on most q roms) I was looking forward to use AA myself. I was positive exited. But in the end I've just stoped using this bunch of sh!t after ~2 h. The bt connection serves my porposes better in any ways - being more flaxible and more comfortable at the same time.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I had very similar thoughts about AA... until I found this:

https://github.com/endyrubbin/AAStream

Full phone screen mirroring to the car display :)
[OnePlus 3 & 3T Cross Device Development] :
Looks promising. Will try tomorrow and report back. Thanx.

EDIT: Which Android Auto version are you using?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
As a typical update freak - always the latest :)

Edit: i.e. 5.0.500224-release

Edit2: this should not make any difference, but just for sake of full transparency in case there's any trouble with AA Stream on OP3/T - OP3T has recently become my backup phone instead of the daily driver and my experience with AA Stream is currently from the other phone (OP7T) only. Anyway, I see no reason for it not to work the same way on 3T (I used AA on 3T on a daily basis before upgrading the phone). I will test it on my 3T (NLOS based of course) in the coming days just to be sure it works just as flawlessly as on the 7T.
[OnePlus 3 & 3T Cross Device Development] :
Good to know. README.md (yeah, I'm one of those... ;) ) recommends ~3. I'll try tomorrow.
[OnePlus 3 & 3T Cross Device Development] :
I can't use the car's touchscreen - need to use the op3t screen (tested so far: Navigon, GpsTest). Sound from Navigon is played on the op3t - with audi focus enabled, the car's fm station is muted, but the directions come from the op3t's speakers (funny).

Have you tried https://github.com/slashmax/AAMirror?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I tested today and it worked just like on the 7T. I suspect permissions problem on your side. I think I saw somewhere that touch problems were related to some permission missing but I don't remember which one... I use https://play.google.com/store/apps/details?id=rikka.appops for checking permissions.

Not yet. I saw AA Stream was based on it, but then I noticed AA Mirror seems most recently updated... Will try when have time.

Edit: I just remembered - I think I had touch screen issues when using the "Force screen resizing" option. Since then I use it with all Force* options off.
[OnePlus 3 & 3T Cross Device Development] :
No need for a special app on los/nlos. Anyway, just checked the log, no android.permission.* denial, but "display over other apps" wasn't granted (and never requested); will try again with this perm granted.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Yup. That should be it. Good thing about rikka.appops is that it shows You when was the last time a permission was granted or denied. I saw there that this permission was denied and allowed it. In general getting this to work is not that straightforward, but when You finally get it working it "just works" and is fun to use when needed :)

I usually use it to play some YouTube cartoons for my kids, reply text messages (when safe) or use alternative navigation apps :)
[OnePlus 3 & 3T Cross Device Development] :
SCNR: ...as in los/nlos... ;)

If I get it to work, it's exactly, what I'm expecting from AA... ;)

For the audio: I had bt turned on all the time, maybe that interferes with AA. "Draw on top" (don't know, why it's named differently in app settings: "Display over otjer apps" - but it's the very same permission) is enabled for both apps, now. I'm going to continue testing the next days.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Damn... I already got used to OOS standards and forgot the NLOS goodies ;)

Let me prepare You for what You'll get - see the attachment :)

It shouldn't interfere. At least I also have it always on.

Edit: and once You're there... there's also this: https://xdaforums.com/general/paid-software/android-3-0-proxy-gateway-android-auto-t3813163 :) (but I haven't tried it)
[OnePlus 3 & 3T Cross Device Development] tonyark:
Feature Request

Can you add Smart Pixels and ability to change number of quick settings columns? I really miss it after switching from Havoc OS to NLOS.

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
No and no:

I really hate smart pixels. There are apps available on playstore to cripple the panel - I love every single pixel of op3/t's amoled.

The priorities of nlos are stability, battery life and performance - in that order. That's why I like to keep cosmetics and theming to the bare minimum. If you want to theme (like the number of qs tile columns) use substratum.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
That can be easily done with:

https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools
[OnePlus 3 & 3T Cross Device Development] pijas82:
Anyone here with no band 4? I don't received notification in my mi band with this rom, anyone help me, needed change anything? I love this rom
[OnePlus 3 & 3T Cross Device Development] :
This is not rom related, but model specific.

For unlocking additional bands see (only as example, there are many guides around - I havn't tested myself): https://xdaforums.com/oneplus-3/how-to/guide-unlock-additional-lte-bands-t3519563
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I believe he meant Mi Band 4 - "smartwatch".

I have no experience with Mi Bands, so I can't help with the notification problem.
[OnePlus 3 & 3T Cross Device Development] :
Thanx for the heads up.

I've no mi band 4. Aquick search brought up: https://help.mibandtools.com/knowledge_base/topics/notifications-are-not-working
[OnePlus 3 & 3T Cross Device Development] pijas82:
Solved ,thanks :good:

---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------

Can you help me with another thing, why Bluetooth symbol don't appear in status bar , it's no a bug or problem ,it's fine
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That's standard in Android 9 - the BT icon only shows if the phone is connected to a BT device.
[OnePlus 3 & 3T Cross Device Development] pijas82:
My op3 still connected with mi band and doesn't appear icon, but no problem, thanks for explain
[OnePlus 3 & 3T Cross Device Development] :
You should see the watch icon, if not configured otherwise in the mi band 4 tool app.

This is the nlos thread - not the thread for mi band 4 nor the thread for getting search assistance.
[OnePlus 3 & 3T Cross Device Development] pijas82:
Sorry, can you clean my messages?