yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] kryzeK:
[MENTION=4405529]nvertigo67[/MENTION] I'm using latest LOS 16 beta, can I move to NLOS 16 with a dirty flash?
[OnePlus 3 & 3T Cross Device Development] matrixisreal:
Thanks for clearing this up.

No, obviously enforcing selinux should be standard.

I would like a better alternative obviously. At least restoring data only works. So I can still work with it.
[OnePlus 3 & 3T Cross Device Development] :
A foss alternative to titanium would be great!

I doubt oandbackup sets up the sepolicy context correctly. Therefor I would recommend:

Don't restore the data od system apps.

After installing an apps data reboot before using the app (or run as root:

restorecon /data
restorecon --recursive --skip-ce /data

If you run into trouble with an app with restored data, uninstall, reboot and reinstall the app in question witht restoring data.

If you expirience strange behaviour of /data/: clean flash

I always prefer foss over closed source apps. But especially for backup/restore solutions the software should have proofed to be working. Nobody can tell the impacts and side effects of a broken backup/restore software.

Sidenote1: clean flashing and setting up the device again is a time consuming pain in the ess. We spend a multiple of the time we feel we would save with any shortcut, on debugging this very shortcut!

Sidenote2: clean flashes often resolves issues, which the current (broken) setup has developed over time due to inconsistent (app-)settings. If we restore these settings after a clean flash...

I strongly recommend clean flashing if you come from any other rom. "Other rom" includes all versions of los and nlos-15.1. If you try to dirty flash, it's mandatory to reproduce an issue on a clean flashed setup before repprting it here.

Sidenote1 from above also applies here.
[OnePlus 3 & 3T Cross Device Development] Sakkalis:
Hey, is it possible to add the option to make the notifications dark/black?

And if you could add screenrecord as well that'd be awesome ?
[OnePlus 3 & 3T Cross Device Development] :
No. I don't want to have many unrelated gui settings for every single taste. Use a substratum theme, that has dark nitifications like swirft dark/black, pitch black or flux - just to name a few.

Ok. Done. ;)

(look at the Recorder app...)
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: 3.18.132, add AOD to doze)

Build 20190113

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

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

Changelog (Last repo sync: 13 Jan 2019, 15:43:25 CET / 13 Jan 2019, 14:43:25 UTC):

current.pick.sh: add AOD to doze. — Nvertigo

Revert "current.pick.sh: "power: Handle launch and interaction hints for perf HAL platforms"." — Nvertigo

Revert "current.pick.sh: "power: Add specific powerhal for msm8937"." — Nvertigo

Revert "current.pick.sh: "power: msm8937: Update power profile settings"." — Nvertigo

Revert "current.pick.sh: "power: Build with with BOARD_VNDK_VERSION"." — Nvertigo

Revert "current.pick.sh: "config: Add Deskclock to power whitelist"." — Nvertigo

Revert "current.pick.sh: "Disable art debug and enable minimize debug info"." — Nvertigo

Revert "NLOS: track our own chromium-webview." — Nvertigo

op3: doze: Match Pie settings UI — Joey

op3: Add priv-app permissions whitelist from LA.UM.7.6.r1-03900-89xx.0 — dianlujitao

Merge tag 'v3.18.132' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/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] hattorihansou:
First of all thank you [MENTION=4405529]nvertigo67[/MENTION] for your work und supply with builds!

Since the latest build the qs-menu for sounds moved to the left side. Is this something done on purpose or maybe a result of dirty flashing?
[OnePlus 3 & 3T Cross Device Development] 9Lukas5:
That was done on purpose. Can't find the post where it was discussed atm, but intention was that the slider appears next to the volume buttons.

L
[OnePlus 3 & 3T Cross Device Development] :
In Releasenotes I always suggest you check current-pick.sh for the currenty used cherry-picks. I also report each change in current-pick.sh in the changelogs:

https://xdaforums.com/showpost.php?p=78491290&postcount=100 (it's also in the postings title!)

https://github.com/nvertigo/local_manifest/commit/053f461d9280bbaf429229f434f1640e5c1e9d71

https://github.com/nvertigo/android...mmit/95e6af62ff025442f68c230ad349d930e7427a5a

This has been discussed in this very thread, too:

https://xdaforums.com/showpost.php?p=78472822&postcount=73

Every newcomer has one shot for using me as his personal search engine. For the future: please, search and read before posting.

For you other question: whenever you wonder if it's time for a clean flash, the answer is: yes. Also true for car tires and underwear. ;)
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Sorry, thought it was new in LOS and not an cherry-pick/ NLOS feature.

Thanks for the explanation and links!

:laugh: I'll keep that in mind.
[OnePlus 3 & 3T Cross Device Development] :
Can someone confirm whatsapp video calls are lagging?
[OnePlus 3 & 3T Cross Device Development] Mata99:
Yes, it lags
[OnePlus 3 & 3T Cross Device Development] fashion_live:
Can i download the rom file from this link for my Onepuls 3 (not 3t)?

https://drive.google.com/drive/folders/1bV5ViyIhh-AwZcjWQDTfHOy2zBSqNVRK
[OnePlus 3 & 3T Cross Device Development] :
Yes, it's a unified build.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
it's unified!!! so it'll work for 3/3T
[OnePlus 3 & 3T Cross Device Development] Syssx:
Alright, I'll try to finish it asap, my time schedule is really tight last couple of days.

I'll probably try and do something about that first part where it transitions from the OnePlus logo, and just make it not transition from OP logo, so it can be usable on both old and new OP bootlogo.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Yes, they do.
[OnePlus 3 & 3T Cross Device Development] :
Would you check this build regarding wa video calls lagging, please?

ROM: https://drive.google.com/open?id=1522qg_yPdm2DyrsPXS0SzA3JqcqX7TLl

MD5: https://drive.google.com/open?id=1wItInJoJb8GBU6hMdyvqrwOnxal4DNip
[OnePlus 3 & 3T Cross Device Development] omair2005:
Is it possible to add date in clock and high brightness mode
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Based on the first very quick test - it seems to be working correctly now! :)

Thanks a lot!
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
This build have network traffic indicator in the centre of the status bar. Idk if its a known bug.

Installed nlos for the first time. I'll be happy to provide logs if you want.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Apparently it's in the centre by design. So technically not a bug. Btw isn't it hard to use your phone with that dpi? Everything is so tiny. The LOS default was a bit too big, but the default NLOS value (400 or 411 I don't remember) seems perfect to me. Of course, it's personal preference, but I'm just curious whether you don't find it too small.
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
Ahaha i have 6/6 eye sight. ??
[OnePlus 3 & 3T Cross Device Development] :
Next nlos build will come with f/b patches:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/239179

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/239180

instead of the f/a patch in the test build:

https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/239182
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Only one last doubt, so the current NLOS features are:

* MicroG Ready

* Substratum without root/reboot

* Volume panel on left

* WireGuard support

Did I forget something? Btw just reading I'm loving the idea, basically it's a LOS with everything it should have (without bloat or radical changes that make it stop being LOS).
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (fix whatsapp video calls; caf updates for audio, display and media)

Build 20190115

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

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

Changelog (Last repo sync: 15 Jan 2019, 13:44:02 CET / 15 Jan 2019, 12:44:02 UTC):

current.pick.sh: "StatusBarSignalPolicy: Fix missing provisioned in equals and copyTo". — Nvertigo

current.pick.sh: introduce a safer repopick. — Nvertigo

current.pick.sh: Camera: Force HAL1 for predefined package list; op3: Force HAL1 for WhatsApp. — Nvertigo

current.pick.sh: LA.UM.7.6.r1-03900-89xx.0. — Nvertigo

Revert "current.pick.sh: add AOD to doze." — Nvertigo

op3: Restore better load balancing after boot — Thomas Shum

op3: Enable AOD — Luca Stefani

op3: doze: Check if AOD is enabled after boot — Luca Stefani

op3: doze: Move Utils.checkDozeService in an handler — Luca Stefani

op3: doze: Make AOD preference not persistent — Luca Stefani

op3: doze: Add AOD support to Ambient Display — Bruno Martins

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] pedritopl:
WhatsApp confirmed to be working properly.

Although I liked the previous (test build) generic solution more than hardcoded package list :-p
[OnePlus 3 & 3T Cross Device Development] :
Me too. Until [MENTION=221757]dian[/MENTION]lijitao explained to me , that the generic solition is the opposite of android's default behaviour. On the long run changing android's default behaviour wil lead to trouble.

Another upside of the prop solution is, that it has been in caf since - at least - marshmallow, so it's quite well tested (not only for our devices).
[OnePlus 3 & 3T Cross Device Development] knpk13:
A file (named current.pick.sh) containing the list of cherry picks is in the OP (and linked in every release post) for your reference. A major one you forgot is SDCLANG. Also, currently you need root for substratum.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Sorry but... [MENTION=5091734]dianlujitao[/MENTION]

;)
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Sorry but what's sdclang? And if root is still needed for substratum, what is the advantage? Themes properly applied (no hardcoded problems)?
[OnePlus 3 & 3T Cross Device Development] Itachi_Uchiha:
how much would be the average drain with always on vs no ambient display?

also any way to hide hd notification?
[OnePlus 3 & 3T Cross Device Development] 186Y:
Change the notification to 'silent minimized '.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Seems to me that colors in sRGB are much more satured in the latest build (20190115).

Anyone experiencing the same?
[OnePlus 3 & 3T Cross Device Development] :
Please read the OP: substratum service mode is NOT implememted! Because:

https://substratum.review/#/q/branch:p

https://xdaforums.com/apps/substrat...um-support-t3606400/post78377987#post78377987

Your list is far from complete. Sadly I'm only allowed to have 30000 characters in OP, so I need to remove older changelogs from the history. You need to check these repos (at least):

https://github.com/nvertigo/local_manifest

https://github.com/nvertigo/android_device_oneplus_oneplus3t

https://github.com/nvertigo/android_kernel_oneplus_msm8996

https://github.com/nvertigo/android_vendor_nlos

https://github.com/nvertigo/android_build_soong

https://github.com/nvertigo/android_build

https://github.com/nvertigo/android_frameworks_base

https://github.com/nvertigo/android_packages_apps_PackageInstaller

https://github.com/nvertigo/android_packages_apps_Settings

https://github.com/nvertigo/android_packages_apps_NLOSWallpaperPicker

https://github.com/nvertigo/android_frameworks_av

Since I always rebase my changes it's easy to see, what nlos has additionally to los.

The difference are these:

https://substratum.review/#/q/branch:p

The changes topics explain quite well, what additional themimg is made possible.

Please help us to keep this thread readeble by searching before posting:

https://www.google.com/search?q=sdc...1l3j69i59l2.4769j0j4&sourceid=chrome&ie=UTF-8

Second or third result is:

https://developer.qualcomm.com/software/snapdragon-llvm-compiler-android.

Each newcomer has one free shot for abusing me as his personal search engine - for the future please search before posting. Thanx in advance.

I prefer ambient over always on, so I havn't really tested much. But for the few hours I've tested it was around 1.1%/h of additional bat usage.
[OnePlus 3 & 3T Cross Device Development] sharath_babu:
Can someone comment on PUBG gameplay with this ROM?
[OnePlus 3 & 3T Cross Device Development] knpk13:
Looks like our device finally got always on display. Seems to work, but is there any way to change the brightness for AOD? It's way too bright for me right now. Also I'm starting to understand how to properly read Gerrit, which makes it a lot easier to understand changes in LOS.
[OnePlus 3 & 3T Cross Device Development] :
To my knowledge there is no brightness setting for AOD/Ambient display.

Perhaps you also understand now, why it is a pain in the 0ss cherry-pick8ng without gerrit's relation chain column... git alone isn't helpfull in such cases. The same goes for topics.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
Nobody else having problems with oversaturated colours?

I even did a factory reset and clean flash of the latest build.

Changing values in live display>advanced>colour calibration/ picture adjustment also don't have any effect for me.
[OnePlus 3 & 3T Cross Device Development] darthchicken:
I'm not having any issues with color. One thing you might want to check is your color temperature under live display, maybe it needs adjusted... or was adjusted at one point and needs reset to default
[OnePlus 3 & 3T Cross Device Development] :
Something is broken in livedisplay: display profile, colour calibration and pic adjustment seems to be broken. Which is the last build it was working for you?
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
The last build that worked for me was the one from 13.01.2019.
[OnePlus 3 & 3T Cross Device Development] :
Will be fixed in the next build (https://review.lineageos.org/c/LineageOS/android_hardware_qcom_display/+/239057 comment from 5:04 pm).

Thanx to [MENTION=8635696]darthchicken[/MENTION] for noticing the srgb issue, but in the first place for knowing the last good build - that saved me from spending a night on this!
[OnePlus 3 & 3T Cross Device Development] :
Off screen gestures

With AOD the off screen gestures work.

I would like to have this behaviour (gestures working) also with Ambient Display. Sadly, when examing the code in https://github.com/nvertigo/android...los-16.0/doze/src/org/lineageos/settings/doze I can't find the difference in off screen gesture behaviour between AOD and Ambient.

If somebody with expirienced java eyes would review the code and guide me on getting off screen gesture to work with Ambient, I would be more then happy.
[OnePlus 3 & 3T Cross Device Development] darthchicken:
Wasn't me, thank hattorihansou.. I did a dirty flash from the 13th to the 15th and didn't experience the issue.

So far, this ROM for me has been rock solid, and is probably the fastest Pie ROM out there.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Huh? I'm on the latest build. There are three options in livedisplay calibration settings. Standard, srgb, dci-p3. I notice a difference in the colours when I switch between them. So I'm assuming calibration works and that it's not broken for me. Latest build, dirty flash.

Edit: what was the issue with srgb that your commit fixed? I can't check the accuracy of the calibration with a colorimeter but I can definitely see a difference in the colours when I switch profiles. So idk if the bug is affecting me.
[OnePlus 3 & 3T Cross Device Development] Syssx:
[MENTION=4405529]nvertigo67[/MENTION] so I sat down and finished the bootanimation. I liked the rotating "+" so much that I just couldn't get rid of it. Final version is this one: https://streamable.com/u1mik

I did two versions of this, one with old and narrow oneplus logo and one with new and thick logo. Both rendered at 30fps as 24 fps was not looking really fluid (i hope that 30fps wont be slow anymore like 60, otherwise i will render it at 24fps). Zips are not comprimed, used "storage" 7zip method - 3.18mbs for new logo and 2.98 for old logo.

View attachment 4689470 - thick one

View attachment 4689471 - narrow one
[OnePlus 3 & 3T Cross Device Development] :
You arn't talking of calibration, but of color profile. Having three options IS the error! (See attached screenshot)

Is calibration and pic adjustment working for you? I'm pretty sure they arn't working.

For srgb: most people are like the two of us: the difference can only be seen in a direct compare (when switching), but arn't able to tell slight differences from dirty flash to dirty flash. I just trust the color saturation perception of [MENTION=1194693]hattorihansou[/MENTION]. If not using LA.UM.7.6.r1-03900-89xx.0 fixes color profiles, calibration and adjustment, it's save to assume the srgb saturation is fixed, too.
[OnePlus 3 & 3T Cross Device Development] hattorihansou:
I also have three different colour profiles (standard/sRGB/DCI-P3) to choose from and i can see a difference in the profiles. On the other hand adjusting values in colour temperature, colour calibration and pic adjustment don't work for me.

I'm using sRGB as my default profile since it's available in CM/ LOS. So i'm kind of used to it and therefore recognized a sginificant difference in saturation between the last two builds.

Thanks [MENTION=4405529]nvertigo67[/MENTION] for your work. I'll report as soon as the new build is available.
[OnePlus 3 & 3T Cross Device Development] :
Thank you very much.

I'd prefer the the old logo. Sadly there's a nasty jump in the position of the animation.

For the fps: 30 fps makes the effect of starting slower less perceptable, but it's still there. I don't think 24 fps will make it better (actually I guess it would make it even worse, because our display comesmwith a refresh rate of 60Hz. Calculating 30fps to 60Hz is less expensive computing then getting 24 fps to 60Hz. I also think, this speed thingy is somehow related to load balancing and cpu scheduling then to the animation. The only chance to reduce the needed cpu power would be using a smaller animation (i.e. 300x300 instead of 1080x1920), but I like the fading out of "powered by android", wich is only possible with 1080x1920 (with i.e. 300x1000, we will run into trouble with positioning and "nlos least annoying..."-moving out). I think we have to live with it (the difference in speed is less then with 60fps), for the benefit of "powerd by android" and "nlos least annoying..." fading and movement.

[MENTION=9350973]All[/MENTION]: It's safe to copy these files over /system/media/bootanimation.zip. Please check them out and comment which one you'd like more. Remeber to flash back_in_black logo for the old (narrow) one. [MENTION=5396529]Syssx[/MENTION] is low on time, and before asking him to iron out the position jump in the old (narrow) animation, I'd li,e to read your feedback.
[OnePlus 3 & 3T Cross Device Development] Syssx:
What do you mean by a jump? I had to go back to OxygenOS as I found out that flashing ROMs simply isn't for me anymore, I just want my phone to be a phone and make calls without me checking for new versions etc.(lol).

Is the position of Android and OP logo misaligned? Where does it happen?

//edit//: i tried to render it in different style, could you please try this one? It's a little bit bigger as it has more frames, but I turned on some compression for PNGs so it isn't that big: View attachment 4689604
[OnePlus 3 & 3T Cross Device Development] :
Compare part0/00095.png with part1/00096.png.

Curently I'm trying to update the sdm blobs to see if I can get the LA.UM.7.6.r1-03900-89xx.0 patches working and push an new build. (BTW: with the newlogo animation) If that's done, I'll lokk into this one.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (fix livedisplay; bootanimation; maintainance)

Build 20190119

Releasenotes:

NLOS-16.0 relays on OxygenOS firmware. OxygenOS 5.0.8 firmware or later is required:

Oneplus 3T: OxygenOS 5.0.8 firmware

Oneplus 3: OxygenOS 5.0.8 firmware

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

Changelog (Last repo sync: 19 Jan 2019, 11:38:18 CET / 19 Jan 2019, 10:38:18 UTC):

Revert "Revert "current.pick.sh: LA.UM.7.6.r1-03900-89xx.0."" — Nvertigo

Revert "current.pick.sh: "StatusBarSignalPolicy: Fix missing provisioned in equals and copyTo"." — Nvertigo

Revert "current.pick.sh: LA.UM.7.6.r1-03900-89xx.0." — Nvertigo

NLOS: track our own LineageParts. — Nvertigo

NLOS: track our own lineage-sdk. — Nvertigo

current.pick.sh: remove pie-battery-styles. — Nvertigo ; it's now merged to nlos-16.0 sources:

SystemUI: Network Traffic [1/3] — Sam Mortimer

SystemUI: Add Lineage statusbar item holder — Sam Mortimer

lineagesdk: Refactor battery icon options — Hendrik Hagendorn

StatusBarSettings: Hide battery preference category based on icon visibility — Bruno Martins

LineageParts: Bring back and refactor battery icon options — Hendrik Hagendorn

op3/t: Update SDM blobs from LA.UM.7.5.r1-03700-8x96.0. — Nvertigo

op3/t: sepolicy: remove ssr nodes. — Nvertigo

Update SDM blobs from LA.UM.7.5.r1-03700-8x96.0. — Michael Bestas

bootanimation: use bootanimation_newlogo.zip. — Syssx

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] pedritopl:
I love the new bootanimation!

On an unrelated note - I just found something related to the camera.

I am using an app called CamScanner to "scan" paper documents with the phone camera. I was able to use the in-app camera with OxygenOS long time ago, but after switching to LOS-15.1 last year and ever since (on NLOS-15.1 and now on NLOS-16.0) I have to first take photos with Google Cam and then import them in the CamScanner, because the in-app camera takes very blurry pictures.

It just occurred to me, to check if the generic fix which You included in the 20190114 test build helps here. And it does! There's a huge difference!

I attach example "scans" taken under the same conditions with the current build (20190119) and with the 20190114 test build. Please note the huge blurriness on the right side of the picture (especially notable on the lower right part). Not sure in which order the pictures will attach, but You will notice the difference without any problems.

Summarizing... [MENTION=4405529]nvertigo67[/MENTION] - Could You please add the CamScanner app to the exception list (same as WhatsApp)? I believe this change should go to LOS-16.0 too.

CamScanner = com.intsig.camscanner
[OnePlus 3 & 3T Cross Device Development] knpk13:
Oh wow. I didn't realize this until now then. That's why a lot of pics in a lot of my apps (in app camera) look so blurry. I know that you chose the hardcoded method over the generic fix for some reason, I'm not sure why. But maybe the generic fix would be better. Because this has happened to me on a LOT of apps. Right now I just clean flashed so don't have many apps installed, so can't give you a list after testing.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I just edited my /system/build.prop on 20190119 build and can confirm that it fixes the CamScanner camera :)

vendor.camera.hal1.packagelist=com.whatsapp,com.intsig.camscanner

[MENTION=7134312]knpk13[/MENTION] - whichever app has the same problem - just test it by editing the build.prop in the similar way and report if it helps so that the devs can add it to LOS builds (or even better - submit the patch by yourself if you can) :)