yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (March Security Patch; WebView: 80.0.3987.119)

Build 20200304

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: 4 Mär 2020, 10:28:04 CET / 4 Mär 2020, 09:28:04 UTC):

msm: mdss: xlog: Disable panic on error by default — dianlujitao

current.pick.sh: "webview_80.0.3987.119". — Nvertigo

Patch up: P_asb_2020-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] punio4:
So, tried NLOS but Google Pay doesn't work :\ No root. Do I need to go the Magisk Hide route + MagiskHideProps?
[OnePlus 3 & 3T Cross Device Development] :
Is your setup passing safetynet api checkers? If not: read the Releasenotes.

Please always read/search the thread bfore posting! This helps keeping the thread readable and searcheble. Thanx.
[OnePlus 3 & 3T Cross Device Development] punio4:
Whoops! Not sure how I missed it. Anyway, fixed with the magiskHideProps.

And I know this might sound weird, but what are the differences compared to LOS16? The only ones I could find were one-handed mode, proper back/recents button defaults and wireguard.

I was hoping that bugs related to the display (sRGB not being applied on boot, night mode low intensity) would be fixed, but alas, it's probably up to dianlujitao
[OnePlus 3 & 3T Cross Device Development] :
Read the current-pick script and look at the repos: all changes to los are always rebased on top of los for easier telling.

BTW: nightmode has dobled the color temprature compared to plain los:

https://github.com/nvertigo/android...d2d69c#diff-380e537acdaedd487ca1adb49d020f7e; the livedisplay colorprofile is apllied after on/off - it gets really nasty to program around that with pie api and fde, so don't expect any change from my side: I really hate changing the default api.

EDIT: if the maximum color temperature for nightmode is still too cold, I can increase it even more - shouldn't be much of a problem, since everybody is free to set it lower.
[OnePlus 3 & 3T Cross Device Development] punio4:
Oh my please do!

I use the following in Tasker to set the temperature, which matches around 2300k:

settings put --lineage system display_color_adjustment "1.0 0.54 0.24"

Is it possible to completely disable LiveDisplay and put in KCAL perhaps?
[OnePlus 3 & 3T Cross Device Development] :
Let's unwind things to avoid misunderstandings:

Current night mode implementation is aosp and is NOT part of livedisplay (which is sad, because I've liked the livedisplay night mode over the aosp one).

Bringing back livedisplay night mode has too many side effects since it's spread all over the sources (kernel, fw/b, Settings, LineageParts, lineage-sdk...); for ease of keeping up with (future) code improvements, I've decided to stick with the aosp stuff.

kcal is not part of the nlos kernel and I don't plan to add it.

I like livedisplay.
[OnePlus 3 & 3T Cross Device Development] :
nlos-16.0-20200307_174413-release-oneplus3t.zip is basically the same as nlos-16.0-20200304_144225-release-oneplus3t.zip. The only difference is that aosp night mode is disabled again and LiveDisplay night mode is reintroduced.

Since all development has been switched to 17.1, I hope that this (partitially) reverting doesn't need to be done again and again.

If you dirty flash this build make sure to disable night display in Display's main settings page before rebooting to twrp to flash this build!

Please test and let me know what you think: aosp night mode or LiveDisplay night mode (including day time color temperature setting) - what do you prefer?

(Edited sources arn't pushed yet - I'll push if a decission has been made.)

ROM (Build 20200307): https://drive.google.com/open?id=1u8QUSfF6wvhyRYCF47uVc68h_uWcX_k1

MD5: https://drive.google.com/open?id=1W5Yqu0J2DybaOTfLUtgIEYo2R4TosNsy

Happy flashing, testing and reporting!
[OnePlus 3 & 3T Cross Device Development] punio4:
I'm honestly a bit afraid to test it now since I just spent a whole day trying to fix a botched LOS16 update (which is why I decided to try out NLOS!)

No need to beat yourself up with LiveDisplay then if just modifying config_nightDisplayColorTemperatureMax will do.

As for LiveDisplay, I found out that unless I set "Display mode" to "Disable all adjustments" and toggle off the "Reduce power consumption", I get nasty brightness/color shifting depending on the screen context. The only thing I use it for is to automate the RGB sliders via Tasker ?
[OnePlus 3 & 3T Cross Device Development] :
No need to be afraid as long as you disable night mode before flashing (most probably even without this precaution - I recommend disabling just because I'm paranoid and that's what I've tested before pushing the build).

When playing around with config_nightDisplayColorTemperatureMax and config_nightDisplayColorTemperatureMin I found the more degrees kelvin are set the colder the color becomes. Values over 10,000 K doesn't seem to work properly at all with aosp night mode. Before bringing back LiveDisplay night mode, I've planed this:

git diff
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index a9b4979..b79db04 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -432,7 +432,10 @@
<!-- Whether the display blanks itself when transitioning from a doze to a non-doze state -->
<bool name="config_displayBlanksAfterDoze">true</bool>

+ <!-- Minimum color temperature, in Kelvin, supported by Night display. -->
+ <integer name="config_nightDisplayColorTemperatureMin">1</integer>
+
<!-- Maximum color temperature, in Kelvin, supported by Night display. -->
- <integer name="config_nightDisplayColorTemperatureMax">8164</integer>
+ <integer name="config_nightDisplayColorTemperatureMax">10000</integer>

</resources>

Your original question has remembered me, how much I like the LiveDisplay night mode with temperature setting for day time over the crippled aosp implementation. I also prefer the slider direction of Livedisplay (left: low value; right: high value) over the aosp direction (left: high; right: low).

Did I mention that I like LiveDisplay? ;)

Can you give me exact steps on how to reproduce, please? I've never expirienced that.
[OnePlus 3 & 3T Cross Device Development] punio4:
Higher numbers are colder. You should probably set it to lower. The default 4k one seems about right, but you want to drop it to the 1k-2k range. https://en.wikipedia.org/wiki/Color_temperature

If you enable the reduce power consumption, and have dark mode enabled and swap apps, or go to homescreen (just a brightness change is needed), you can see the brightness acting crazy and lagging. It's because it behaves like non-buffered dynamic contrast.
[OnePlus 3 & 3T Cross Device Development] :
I'm lazy: LiveDisplay= LD; night mode=nm.

Yes. Due to the "wrong" slider direction a brainlock has been injected to my mind... ;) Did I mention that I like the "correct" direction of the LD sliders? *lol*

I can't reproduce this (I havn't used the "Reduce power consumption" with aosp nm, and I'm too happy with LD nm to flash 0304 again :) ) with LD nm neither with sRGB nor with Standard - maybe some other setting is needed to reproduce this or it's fixed with LD nm.

[MENTION=9350973]All[/MENTION]: please test 0307 thoroughy - I tend to keep LD nm.
[OnePlus 3 & 3T Cross Device Development] :
I've tested every options under live display, it's working (means my screen is changing it's color temp/brightness) except for the "reduce power..." I hardly see any differences between modes after switching it on/off (in terms of color temp, sharpness, brightness, etc).

No testing about the actual power reduction

1 day of use

Which i prefer? I switch it off for both ld/aosp. i don't like the change, i like it stable through the day
[OnePlus 3 & 3T Cross Device Development] hellcat50:
This is the best ROM for the oneplus 3, it runs superb!
[OnePlus 3 & 3T Cross Device Development] pijas82:
Can I update to last version with dirty flash?

I'm on 18/02 build all perfect

Thanks
[OnePlus 3 & 3T Cross Device Development] :
Most probably yes. General rule of dirty flashing: if it works without issues, you are good to go - if issues show up: clean flash. (Remember to reset night mode if you use 0307)
[OnePlus 3 & 3T Cross Device Development] xuser_:
[MENTION=4405529]nvertigo67[/MENTION],

Waiting for nlos-17.1 ...

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
Nah, stay with P

Q suckz :silly:
[OnePlus 3 & 3T Cross Device Development] :
Alipay & WeChatPay

Does anybody here use Alipay and/or WeChatPay with fingerprint authentication?

I stumbled across the ifaa, soter, alipay, tencent [exaggerated]spyware[/exaggerated] the first time here: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post81639427#post81639427 . Then I forgot to do further investigations.

Then [MENTION=534547]Peach[/MENTION]4x not only rememnered me of the tencent privacy hazard, but also pointed out that the modem fw itself has traces of this (IMHO unwanted) software: https://xdaforums.com/oneplus-3/how-to/guide-deblob-alipay-ifaa-tencent-soter-t4064893#post81994837 .

Apart from making a zip that removes this software from system and modem for all roms (it's not that trivial as it looks on a first view: https://xdaforums.com/showpost.php?p=81990631&postcount=2 ), I'm planning to remove ifaa, soter and alipay completely from nlos-16.0 and provide either a zip removing the soter and alipay files from the modem partition, or a modified fw package with the soter and alipay files removed (or both).

To make an educated decision I hope I get the question in the first line of this posting answered, as well as this question: https://xdaforums.com/showpost.php?p=81994837&postcount=4 .

Please comment on my above thoughts!
[OnePlus 3 & 3T Cross Device Development] SenseSei:
Not me. I guess these apps are mainly/only used by Chinese?

I won't miss these blobs personally.
[OnePlus 3 & 3T Cross Device Development] :
If it's stable, i think it's better to build without one rather than using debloating zip and maybe provide add-on for those who need it

I already have 5 zips between dirty flashes, it's not so "flash" anymore...
[OnePlus 3 & 3T Cross Device Development] punio4:
https://www.lineageoslog.com/16.0/oneplus3

Oh my! They added an option to disable LiveDisplay!
[OnePlus 3 & 3T Cross Device Development] :
https://review.lineageos.org/q/topic:"hide-livedisplay-lineage-16.0"+(status:open OR status:merged) is a compile time option, of course! I don't plan to disable livedisplay on nlos. Did I mention that I like livedisplay?
[OnePlus 3 & 3T Cross Device Development] punio4:
Oh. I thought it was a system-wide setting.
[OnePlus 3 & 3T Cross Device Development] punio4:
What do you mean by "reset Night Mode"?
[OnePlus 3 & 3T Cross Device Development] :
Disable aosp Night mode (Settings->Display) before flashing the 20200312 build - it's gone after update and you don't want to have it set to something. In doubt: clean flash.
[OnePlus 3 & 3T Cross Device Development] :
Completely off topic, but extremely perfidious:

https://fossbytes.com/fake-coronavirus-maps-are-infecting-pcs-with-malware-to-steal-passwords/

Use the official information from goverment or health service of your country.

Please share especially with non-nerds in your family, peer group etc.
[OnePlus 3 & 3T Cross Device Development] mr-cook:
Just a heads up if anyone has trouble. I tried this with the 2/22 nano gapps and it was a nightmare of FC's. Re-wiped and used the 3/11 nano and everything is good.
[OnePlus 3 & 3T Cross Device Development] :
Rework (edit) your quoting, please. Only quoze, what you are reffering to: this keeps the thread searchable and readable.

Thanx for thd heads up! As always: if you have found a working gapps package stick to it (it gets auto updated anyway).

gapps suckz... ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I very rarely update my Gapps package because the apps will get updated by Play Store. So, for example, I used 190211 all last year on all my Android 9 ROMs and I never had a problem.
[OnePlus 3 & 3T Cross Device Development] Galiis:
I'm using both of them. With removing ifaa/soter components, fingerprint authentiacaion for payment (Alipay and Wechatpay) not working anymore.

Since Alipay fingerprint authenticaion not working on my device (a week after migrating to nlos), I switched typing password for payment earlier (2w ago).

Indeed, pressing on home button is easy.
[OnePlus 3 & 3T Cross Device Development] :
First of all: I see your problem. I've curtently no solution, but I'd prefer a solution which leaves the choice to the user and I'm still thinking of such a solution.

One question though: do you say alipay fingerprint authentication has stoped working BEFORE I've removed the ifaa, soter and alipay stuff from 20200312 build?
[OnePlus 3 & 3T Cross Device Development] Galiis:
Yeah, It stopped working before the ifaa removal. After I migrated to nlos (20200218 bulid), It works fine for a few days.

I have reported the problem of fingerprint payment failure to alipay staff (without log), they said it will be fixed in the next release.

Edit: Find some interesting stuff, there is magisk module implement third-party fingerprint payment for alipay (using payment password), it works on 20200312 build.

https://github.com/eritpchy/Fingerprint-pay-magisk-alipay (also for wechatpay in another repo).
[OnePlus 3 & 3T Cross Device Development] :
I'd highly appriciate, if you report back once the new alipay version is released. If the new version works for fingerprint authentication with the mentioned magisk module, you may want to write a short guide. I'll link it in the releasenotes.

Thanx for heads up and testing!
[OnePlus 3 & 3T Cross Device Development] Galiis:
Install Fingerprint-pay-magisk-alipay module

If you are addicted to Alipay or Wechat pay, I'm highly recommend you switch to other ROMs (like OOS/LOS) which have ifaa and soter components.

Without ifaa and soter components, but your fingerprint sensor is working. There is a 3rd-party method using magisk module implement fingerprint payment for Alipay and Wechat pay. (Use at your own risk!)

Test environment:

ROM: nlos-16.0-20200312 build

Firmware: oxygenos-9.0.6-firmware-3T

Bootloader: Locked

Alipay: 10.1.88.5821 (Google Play)

Magisk: v20.3

Requirements:

Magisk

Rooted Android 6.0+ devices

Installation (for Alipay):

Download Riru-core (v19.7) and Fingerprint-pay-magisk-alipay (v3.9.9) modules. (Links below)

https://github.com/RikkaApps/Riru/releases

https://github.com/eritpchy/Fingerprint-pay-magisk-alipay/releases

Install modules in magisk manager, then enable them and reboot.

Usage:

Open Alipay app, go to the settings, enable it in fingerprint and type your payment password (see attachments).

Pay for a drink to test if it works.

References:

https://github.com/RikkaApps/Riru

https://github.com/eritpchy/Fingerprint-pay-magisk-alipay

https://github.com/eritpchy/Fingerprint-pay-magisk-wechat

PS:

1. This module stores your payment password at your local device (encrypted).

2. It may not work after Alipay or Wechat update.

3. I didn't test Wechat pay module, you can have a try (see references).

Thanks to those module developers for their work.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=9998549]Galiis[/MENTION]:

Wow, that was quick!

Don't be surprised if your posting is moved the next days: I've asked the moderators if it's possiböe to move it to #6 on the first page. Even with the amount of users not reading the first page of a thread is growing, I want that all users reading the first page find all relevant information to install nlos on the first page.

Thanx for your efforts!
[OnePlus 3 & 3T Cross Device Development] Oswald Boelcke:
[MENTION=9998549]Galiis[/MENTION] [MENTION=4405529]nvertigo67[/MENTION] The post two lines above (#1511) has been copied to the first page as post #6.
[OnePlus 3 & 3T Cross Device Development] :
Thank you very much!

I've adjusted the announcement in the OP to this (additions marked red):

The first additikn in the ATTENTION paragraph will be removed after two or three more builds within the complete paragraph. The secomd addition (after the safetynet paragraph) will be added permanently!

All credits for running Alipay with fingerprint authentication belong to [MENTION=9998549]Galiis[/MENTION]! Thanx.
[OnePlus 3 & 3T Cross Device Development] Galiis:
[MENTION=4405529]nvertigo67[/MENTION]

Thanks, I'm just a end user. Modules author already wrote how-to in README file in Chinese.

And I'm appreciate your work, NLOS is awesome!

Otherwise, [GUIDE][DEBLOB][OP3/3T] Deblob alipay, ifaa and tencent soter by Phaech4x is great. More details in there.
[OnePlus 3 & 3T Cross Device Development] punio4:
Not sure if this is NLOS related, but Gboard started having this gap at the bottom the height of the navbar, even tho it's off.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It's not on my OP3T on NLOS or LOS, but the OP7T I just got has it even with no navbar.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I've also got it on Los 17.1 (hadn't noticed it until I read your post). But it disappears in single-handed mode. And the space is still present if I downgrade Gboard to the previous version. I'm using buttons not navigation bar.
[OnePlus 3 & 3T Cross Device Development] :
First of all, most important and never ever forget: gapps suckz!

Second: I'm in the same position as [MENTION=7134312]knpk13[/MENTION]. I can't reproduce the "gboard-gap", see attached screenshot.

Considering the second point, I guess it's settings dependend. I don't use spyware (aka gboard). So I needed to install (uninstalled right after taking the screenshot) gboard first. The two actions I'd try first are deleting gboards data and if that doesn't remove the gboard-gap uninstall and reinstall gboard.

As a last point: Though gboard seems to be just comfortable, gboard transfers all your typing, swiping and writing to google - this data is not only usable to make ux more comfortable, but also for completing your profiles. As proofed by facebook and cambridge analytica all profile data can be used to manipulate you and a complete society. Everything about you that can be misused will be misused - it's not a matter of if this happens, it's just a question of when this happens. Keep your private data private!

Take care of each other!
[OnePlus 3 & 3T Cross Device Development] :
Firewall+PG :p

Though i'm not sure it's suffiecient, well it's user app though. Be damned G if they put backdoor on a user app

I get used to gesture delete/move, if only aosp keyboard has them

However, mine doesn't have the problem too

I tried mess with it's setting and no luck
[OnePlus 3 & 3T Cross Device Development] BillGoss:
So I have the space and I did the following:

- wiped storage for Gboard: made no difference

- restored the data using TB: made no difference

- uninstalled Gboard: problem disappears totally!

- reinstall Gboard using TB: no space down

- restored the data using TB: still no space

Excellent result, but doesn't explain why the space appeared in the first place.

Edit: a short while later: space is back! Boo!

So I deleted and reinstalled Gboard again. No space for longer this time, but eventually it came back again.

So I'm now using one handed mode and that's fine.
[OnePlus 3 & 3T Cross Device Development] :
SCNR:

The answer has been given:

;)

Seriously: my best guess is the g services sqlite database: when updating the sqlite version, some setting of gboard is rendered incompatible, but not updated/removed. Uninstalling gboard removes all entries of gb in the db, and the first start of gb after reinstalling reinitializes the gb entries... Since all gapps are closed source, this is just guessing.
[OnePlus 3 & 3T Cross Device Development] punio4:
Noticed a problem on NLOS vs LOS16. My USB headset's microphone isn't working except in calls. On LOS16 I could record audio via my microphone, while on NLOS it always defaults to the built in microphone, until I enter the call. And then it often says "Audio hardware was unable to initialize". My SO's OP3 running LOS16 still works fine.
[OnePlus 3 & 3T Cross Device Development] :
I can't verify this - I need to get hands on an usb headset first. Since los and nlos uses the same audio and usb setup and sources, I'm clueless, yet.
[OnePlus 3 & 3T Cross Device Development] Zaphod_B_1:
Hi,

Does anyone here have the same problem like me?

I'm not able to get an IPv6 in NLOS16 for the mobile network. I'm on Vodafone Germany and they introduced it at the end of last year.

I've changed the APN protocol to IPv4/IPv6 in my APN settings, but no luck.

After changing the ROM (Nitrogen 10 in this case) it works... But I'd prefer to use NLOS, of course... ;)

Thanks and cheers

Zap
[OnePlus 3 & 3T Cross Device Development] :
I'm trying to get volte for vodafone.de for three years now. While digging in this, I found that ipv6 is not working, but I never thought about it, because I'm also running a router with an vodafone.de stick, which can't get a ipv6 connection to the apn, neither. Honestly, I've no clue at all how to fix it on both devices. :(

If anybody has an idea how to fix either the opv6 issue or the volte issue, please let me know - I've run out of ideas.

BTW: ipv6 on wifi works, so we can assume it's not kernel related.

EDIT: ipv6 works on both devices, now. For opt3: in apn settings enable ipv4/ipv6 and set MVNO type to SPN. Press save (three dots), enable airplane mode for some seconds and disable it again (or reboot).

EDIT2: MVNO should be none - too much testing at once...
[OnePlus 3 & 3T Cross Device Development] punio4:
Sadly didn't help my case. :/
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, I know. After a while the space in Gboard came back. I'm now using one handed mode and that's been fine.

It seems to me like something that happens by being connected to Google because of I'm not connected to the internet after I restore Gboard, the space doesn't show up.
[OnePlus 3 & 3T Cross Device Development] :
Other roms are hit as well: https://xdaforums.com/showpost.php?p=82067027&postcount=3062

BTW: I've another cosmetic glitch with gapps (did I mention that gapps suckz?): I'm using the dark mode (non-black). If I force stop playstore and delete it's data, on the next start pöaystore is dark, after a reboot or after another force stop, play store is white again... With airplane mode on playstore stays dark after a forced stop, though playstore without ip conmection doesn't make sense... ;) Interesting finding.