yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
I've deleted the 20190204 build. I'm currently uploading the exact version I'm using currently with the correct md5sum file.(*) I found them on my usb mass storage device and uploadimg directly from the usb drive (sandisk 128 GB) - so we can consider OTG working. Perhaps the physical connector is just dirty...?

I've decided to reupload the 20190204 build, because it's currently the last build with srgb/dci-p3. Please read the comments here: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/240575 livedisplay 2.0 doesn't support the srgb/dci-p3 currently (I don't know more of the plans of the los team, then what is mentioned in the comments of 240575.)

With 20190204 srgb/dci-p3 is still working (with the known limitations with boot passphrase set) - see attached screen shots.

(*) [MENTION=8089303]ersandeepkr[/MENTION]:

If you download the rom's zip together with it's md5sum file, just check the md5sum checkbox in twrp's flash page and twrp does the comparing for you.

https://en.wikipedia.org/wiki/Md5sum

https://linux.die.net/man/1/md5sum
[OnePlus 3 & 3T Cross Device Development] 64ashg:
This sounds daft but is it possible to ignore/skip these changes going forward?

But thats counter productive as this is not a permanent solution to this abandoned wip issue..

Edit1: this won't affect the los and nlos 15.1 branch right?
[OnePlus 3 & 3T Cross Device Development] :
Hardly: I'd need to revert https://review.lineageos.org/q/topic:%22lineagehw-hidl%22+status:merged, which would us cut off from all updates to any hidl based service. "Counter productive" is the euphemism to use... *lol*

As far as I've seen when checking lineage-15.1 in gerrit, there are no traces to switch to livedisplay 2.0.

I'm quite sure sometime the in-kernel modes will be brought back - I just don't know when...
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (Februar Security Patch; kernel: 3.18.134-rc2; livedisplay 2.0)

Build 20190205

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.

livedisplay 2.0 has currently now switch for in-kernel srgb and dci-p3 modes. This doesn't mean srgb and dci-p3 modes are gone, but only that there's no switch in livedisplay. You can sill echo 1 to the sysfs nodes (/sys/devices/virtual/graphics/fb0/dci_p3 respectively /sys/devices/virtual/graphics/fb0/srgb) or use a kernel manager.

Changelog (Last repo sync: 5 Feb 2019, 16:20:27 CET / 5 Feb 2019, 15:20:27 UTC):

android-9.0.0_r31.sh: guess what: pick aosp 9.0.0_r31 changes. — Nvertigo

current.pick.sh: "op3/t: migrate to livedisplay-2.0.". — Nvertigo

Merge branch 'linux-3.18.y' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc into 134-rc2 — 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:
That resets after a reboot right?

What are the options to run that command automatically every time after boot? I don't have experience with any kind of scripting or running automated scripts after boot. I do have Tasker installed if that's an option (though I never got around to using it for anything.)

Tried looking through the 15.1 thread for instructions specific to DCI-P3 and sRGB because I recall it being mentioned there but thought I'd ask about scripting/automating in general as well since I know nothing about it.

Also heads up, dirty flashing the 20190205 over the new 20190204 (which was dirty flashed over the old 20190204) changed some of the other system settings for me for some reason. For example, my battery circle went back to being a battery portrait lol. And one of my home screen icons disappeared. I changed those settings back, but I was wondering if I should clean flash just in case, since idk if I should be worried about minor changes to system settings.

Edit: Found this in the 15.1 thread. I don't know how to use any of those methods. Can you post or pm me with some info so I can learn how to do it? Even running echo 1 /sys/devices/virtual/graphics/fb0/dci_p3 like you said doesn't change anything for me. cat on the node returns 0 even after echoing 1. Is my syntax for the command wrong? Sorry I'm new to this and coding/scripting/shell commands (idk the correct term lol) in general. I tried reading the man pages for echo but still couldn't figure out what I did wrong and whether the man pages apply to Android :(

https://xdaforums.com/oneplus-3/one.../rom-nlos-15-1-20180223-t3754855/post78380336
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Here's a file that you can use which runs each time the phone restarts. The comments (lines starting with a #) tell you where to put the file and the permissions it needs (755).

Remove the ".txt" from the file name which I added so that I could attach it to this post.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Exactly the same build flashing order and same problem with battery icon, only that in my case it changed from Text only to Vertical icon with text inside.
[OnePlus 3 & 3T Cross Device Development] :
On the battery icon:

Due to changes in the LineagSettingsProvider regarding a completely unrelated topic (related to on screen navbar), the database version has been updated. This needs a change in the battery options commit (not a classical rebase, but a partly rewrite), too:

https://review.lineageos.org/c/Line...os/lineagesettings/LineageDatabaseHelper.java

This resets the battery icon setting. Don't worry, just reapply your favored settings.

On vanished icons on start screen:

I have no idea where to look. I guess the canonical name of the app(s), which icon(s) disappeared has changed.

On srgb/dci-p3 sysfs nodes:

Make sure you set the color mode in livedisplay settings to "Standard". Make sure you only set one (srgb xor dci-p3) node to 1. If you want i.e. srgb:

echo 0 >/sys/devices/virtual/graphics/fb0/dci_p3
echo 0 >/sys/devices/virtual/graphics/fb0/srgb #just because I'm paranoid, doesn't mean they aren't behind me...
echo 1 >/sys/devices/virtual/graphics/fb0/srgb

To actually write to the node, you need root previlegs, of course.

Sidenote: next build will have userinit.sh fixed again.
[OnePlus 3 & 3T Cross Device Development] :
My answer on this question hasn't changed:

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] :
UPDATE (kernel: 3.18.134; fixed: userinit.sh & settings --lineage)

Build 20190207

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.

livedisplay 2.0 has currently now switch for in-kernel srgb and dci-p3 modes. This doesn't mean srgb and dci-p3 modes are gone, but only that there's no switch in livedisplay. You can sill echo 1 to the sysfs nodes (/sys/devices/virtual/graphics/fb0/dci_p3 respectively /sys/devices/virtual/graphics/fb0/srgb) or use a kernel manager.

From this build on /data/local/userinit.sh is fixed and working. This means you can execute arbritary commands from userinit.sh, which can be very handy. This also means, everybody with access to /data/local/userinit.sh (no matter if remotely or via physical acces) can execute arbrita4y commands on the next reboot, which can be a security hazard. Watch out. Act mature and responsible! Don't use your device without secured boot!!!

Changelog (Last repo sync: 7 Feb 2019, 18:17:37 CET / 7 Feb 2019, 17:17:37 UTC):

current.pick.sh: rewrite pie-battery-styles picking. — Nvertigo

Revert "current.pick.sh: remove pie-battery-styles." — Nvertigo

Revert "current.pick.sh: Revert "AOSP/Messaging: bump targetSDK to 28"." — Nvertigo

Revert "current.pick.sh: force picking "Revert "AOSP/Messaging: bump targetSDK to 28""." — Nvertigo

current.pick.sh: fix picking pie-network-traffic. — Nvertigo

current.pick.sh: "settings: Allow accessing LineageSettings via settings command". — Nvertigo

Merge tag 'v3.18.134' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable into linux-stable/merge-16.0 — Nvertigo

Set seclabel for service sysinit to sudeamon. — Zackptg5

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] :
userinit.sh: set srgb or dci_p3

Attached you find a sample userinit script to easily set srgb or dci_p3 mode.

Unzip the attached zip, copy the contained userinit.sh to /data/local/userinit.sh and make it executable (0755, -rwxr-xr-x), set MODE to (exact!) either srgb or dci_p3 and reboot.

Since livedisplay doesn't know about dci_p3/srgb, you can only use either the sysfs nodes xor the livedisplay's color profile setting. The script ensures that the color profile is set to "Standard" in order to make the sysfs node method work properly.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Please [MENTION=4405529]nvertigo67[/MENTION], create a telegram channel to notify new updates. And as you use GDrive to store the updates this would be perfect for use with IFTTT! You only have to do this once and forever this will be automated.

Btw I even created a channel that does this (https://t.me/nlosupdates), it works but it's not very satisfactory. I use a Chrome extension to monitor changes in your folder and send me an email, this email will have a unique label that will serve as a trigger to notify on my telegram channel. If you create your channel with your own accounts, everything would be simpler, agile and useful (the message could for example contain the uploaded file name and the direct link to download it).

PS: If you do, obviously I'll delete my Channel and you can use that link for your Channel. But please consider this.
[OnePlus 3 & 3T Cross Device Development] simthadim:
With all due respect, let's not fragment the community with channels on other social media. Starting channels somewhere else will fragment error reports, requests and questions. XDA is the 'de facto' developer forum for android, and all know where to find it.

I for one only want use Signal, others will want a WhatsApp group and hardline oldschool developers will desire Gitthub and a mailing list. To each his own (agile is a somewhat subjective term) ;)

Note, I by no means speak for Nvertigo67, this is just my opinion.
[OnePlus 3 & 3T Cross Device Development] DeryckNS:
The idea of a channel for update notifications is great, and is not fragmenting the community, since a telegram channel only serves to notificate to anyone who's subscribed that a new update is available. As a subscriber you can't write messages, give bug reports or anything in a channel, just read the automated notifications. So you are not forced to subscribe to it.

Enviado desde mi ONEPLUS A3000 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] kryzeK:
I understand your position but with all due respect, you do not have to use that. I'm a fan of the telegram, but other than that I just want this because the ROM does not have OTA support. I think IFTTT would be perfect in that case, the developer would not have any work on manually notifying that there is a new version as long as it's all automated.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Hi, nvertigo67 already answered to such requests before... Please use search before posting. Most recent answer:

https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post78486462
[OnePlus 3 & 3T Cross Device Development] kryzeK:
Hi, I am aware of this response. That's exactly why I'm suggesting IFTTT, it's very simple and functional: IF new file in GDrive folder THEN post on telegram channel.

You do not have to do anything else after creating this applet.
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (livedisplay knows srgb/dci_p3 again; maintainance)

Build 20190209

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.

[MENTION=5091734]dianlujitao[/MENTION] has ported the in-kernel modes to livedisplay 2.0 (great job of a real coding jedi!) in a way, that it now sticks through reboots with secured boot! Don't forget to delete userini.sh if you've used it to set a 8n-kernel color profile.

Changelog (Last repo sync: 9 Feb 2019, 16:15:44 CET / 9 Feb 2019, 15:15:44 UTC):

current.pick.sh: lineagehw-hidl. — Nvertigo

current.pick.sh: "op3: livedisplay: Support sysfs backend display modes". — Nvertigo

current.pick.sh: "op3: Migrate to livedisplay 2.0". — Nvertigo

current.pick.sh: "op3: Convert KeyDisabler to touch HAL". — Nvertigo

current.pick.sh: "op3: Convert TouchscreenGestures to touch HAL". — Nvertigo

NLOS: track our own packages/apps/Messaging. — Nvertigo:

Revert "AOSP/Messaging: bump targetSDK to 28" — Nvertigo

Revert "Messaging: improve notification channels" — Nvertigo

Revert "Switch to JobIntentService" — Nvertigo

op3: Build Trust HAL — Joey

op3: overlay: Update fingerprint dot location — Michael W

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:
Is it only me or the boot process always stays quite a few seconds (~45s) on the "Starting Android..." screen right after entering the boot PIN?

I'm not sure when that started. Might be it was always there since I moved from NLOS-15.1 to NLOS-16.0 with the last build from December.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
...might be something with my FS? See the logs from 15:09:27 and afterwards...

Any tips? Filesystem check in TWRP?
[OnePlus 3 & 3T Cross Device Development] :
I have no idea. for me it's about 5 s on p. It has been 2 s on o. It's longer, but not 45s. I'd suggest doing a clean flash following OP. When and with which twrp was the format of data done?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Not sure what TWRP, but probably it was 3.2.3.0.

I have to think about clean flash... Thanks.
[OnePlus 3 & 3T Cross Device Development] :
If you decode to clean flash, use fix3 (the one I linked in OP) and format data instead of wiping only.

How full is your data? If it's 95%+ it may take that long for decrypting (though ext4 is not as prune to this effect, then f2fs). You can easily see, when decryption has finished: It's exactly when the led starts it's second happy dance (the first time after entering boot passphrase).
[OnePlus 3 & 3T Cross Device Development] pedritopl:
I'm about 55% full and on ext4.

I am on fix3 TWRP since I moved to NLOS-16.0 at the beginning of January.

I think I'll try full backup (with TiPatch), format and restore. See if that helps...
[OnePlus 3 & 3T Cross Device Development] :
Check for the issue BEFORE restoring!!!

If it's not the fs ( and it seems that fs is ok), and if it's not the rom (and it seems that the rom is ok), probability is high, that the issue is in what you have backuped...
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Sure. Thanks. That much was obvious for me, but thanks for reminding :)
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Restored from backup. "Starting Android..." screen now appears for only 6-7 seconds :)

Data formatted with fix3 TWRP and encrypted with NLOS-2019-02-09.

Oh, and before restoring from backup the delay was slightly lower, but then there was no data on the phone compared to ~80Gb right now.
[OnePlus 3 & 3T Cross Device Development] S4turno:
Telegram channels are like RSS feeds, not group chats. Two examples: I use them to send alerts about new uploads while the Paranoid Android team uses their channel to inform about new builds.

I agree with you about fragmentation, but it would be just a RSS feed for Telegram users. It would automatically share a message when a new build was uploaded to nvertigo67's folder. Users then would receive a notification.

I follow the thread and don't need update notifications. Just explaining the difference between channels and telegram/signal/whatsapp groups. :good:
[OnePlus 3 & 3T Cross Device Development] simthadim:
Thank you for the clarification (and for taking the time to do so, much appreciated). I agree that for those that use Telegram it could be helpful. My main point is, however, noting nvertgo67's answer in the beginning of this thread: where would you stop with adding channels until (one day) OTA will work? Those that do not (want to) use Telegram might desire a different method for now. This is where we as a community can chip in on the one-man show that is NLOS (in part two man show: Nvertigo67 and dianlujitao, who is doing great work on the basis of LOS16).

It's up to nvertigo67 whether he wants to include these additions in the OP (such as the telegram channel made by [MENTION=4745774]kryzeK[/MENTION], kudo' s for doing so btw). I could come up with arguments in favor of doing so (it may be convenient for those that want to use it) but also to oppose it (to keep things official and in control, for now). We could argue and talk about this for days, though let' s fix these minor things ourselves if needed (I myself use the build number in the title of this thread, so wouldn't need anything else).
[OnePlus 3 & 3T Cross Device Development] :
First of all: this is very true, and I can't emphasize enough, that los for op3/t wouldn't be what it is without dianlujitao's efforts and genius!

I'm still in the process of considering:

I always accept a helping mind/hand. And if a telegram channel for updates is, what users want, and someone os willing to maintain that, let's go.

On the other hand: nlos is beta and highly wip. It's mandatory to follow the thread to make the most of nlos.

If one follows the thread, the update channel is redundant.

I wonder if such a channel makes sense or if it encourage reading-lazy users to read even less...???
[OnePlus 3 & 3T Cross Device Development] cukierkas:
Even I, following the thread, with 5t in hand, and reading it with smile and full eyes with curiosity. It's nice watching someone's job, who knows what he's doing! 3t was a great device, so still having nice memories about it.

Telegram is not needed at all. Who wants to use nlos - will find the ways to say thank you.

Regards.

Ot: selfish question : [MENTION=4405529]nvertigo67[/MENTION], when you're going to support 5t?:D
[OnePlus 3 & 3T Cross Device Development] :
UPDATE (kernel: qcalcd-2.0 updates; statusbar: solve centered clock traffic race)

Build 20190212

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: 12 Feb 2019, 15:38:22 CET / 12 Feb 2019, 14:38:22 UTC):

Revert "current.pick.sh: libril: Fix manual network selection with old modem & op3: Enable workaround for old MCC/MNC format." — Nvertigo

Revert "current.pick.sh: "op3: Migrate to livedisplay 2.0"." — Nvertigo

Revert "current.pick.sh: "op3: livedisplay: Support sysfs backend display modes"." — Nvertigo

current.pick.sh: add "parts: don't allow clock and network traffic to be enabled at the same time\* to pie-network-traffic. — Nvertigo

Revert "current.pick.sh: "op3: Convert TouchscreenGestures to touch HAL"." — Nvertigo

Revert "current.pick.sh: "op3: Convert KeyDisabler to touch HAL"." — Nvertigo

op3: Enable workaround for old MCC/MNC format — dianlujitao (los/lineage-16.0

op3: livedisplay: Support sysfs backend display modes — dianlujitao

op3: Migrate to livedisplay 2.0 — dianlujitao

op3: Move perfboostsconfig.xml to vendor — dianlujitao

op3: Convert KeyDisabler to touch HAL — dianlujitao

op3: Convert TouchscreenGestures to touch HAL — dianlujitao

op3: Supresses NFC 1.1 denials — dianlujitao

Merge remote-tracking branch 'los/lineage-16.0' into linux-stable/merge-16.0 — Nvertigo

msm: camera: Fix compilation — dianlujitao

add toggle for disabling newly added USB devices — Daniel Micay

wlan: qcacld-2.0 updates (many) — dianlujitao

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] :
Most probably: never. I'll check my bank account end of the year ('till then I definetly use my 3t), and have a look at the market places then. Perhaps used 6t, perhaps new 7 or 7t, perhaps something completely different (xiaomi, honor, poco - they all have interesting devices), but - most probably - not a 5t.
[OnePlus 3 & 3T Cross Device Development] cukierkas:
I'll follow your thread just to know your choice.

Take care.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Let us know in advance so we know what device to get next lol. I say lol but I'm serious xD. Though I'll probably stick to my 3t for quite some time; it's still as good as new.
[OnePlus 3 & 3T Cross Device Development] phoberus:
I have two bugs with the newest build (can't say in which build it started, dirty flashed from a January build):

1. My display profile (DCI-P3) doesn't work after a boot. If I lock the phone and unlock it again, it works. But before, it looks more like srgb or an other profile

2. if audiofx is enabled: sometimes the audio on spotify or a video on youtube is very low. Pause and restart fixes the problem and the volume is back to normal. after disabling audiofx: no problem

Do you want logs? Or does it need to get fixed in Los first?

Usually taking logs with the app "MatLog", but last time you said that logs aren't complete, so I can do it with the terminal this time.

adb logcat > logs.txt

right?
[OnePlus 3 & 3T Cross Device Development] :
Yes. No. Yes, I'd add -d.

For 1.) Have you checked tne sysfs nodes? If rebooting with with dci_p3 set, the srgb node should read 0, the dci_p3 node should read 1. What about other livedisplay settings, like night mode? For me all livedisplay settings gets apploed between the end of the bootanimation and the sim pin dialog (sim pin is already with livedisplay settings applied).

For 2.): on what output device? Audio mods installed? Most audio mods dooesn't play nice with audiofx (expectable). If using audio mods disable or freeze audiofx.

Anybody else suffering from the above issues?
[OnePlus 3 & 3T Cross Device Development] phoberus:
1)sysfs is right (srgb: 0 and dci_p3:1)

Other settings: using only day mode with custom kelvin and dci-p3 profile. No other things like calibration used.

2) headphone jack. I disabled audiofx for speakers. Can't say something about bluetooth devices. I'm not using any audio mods, only some tuning in audiofx.

logs attached
[OnePlus 3 & 3T Cross Device Development] :
I've meant: are other settings applying correctly?

If the nodes are set as you confirm, everything seems to work. I see the same in the logs: no issues with livedisplay.

I use bt and have no such issues. I can't find anything in the log - looks like it's working.

Do you use any equilizer equipped audi app? I belive to remember there were issues...

Have you tried a clean flash without restoring backups and only basic apps (gapps nano/pice + youtube + spotify) freshly installed?
[OnePlus 3 & 3T Cross Device Development] phoberus:
I don't know because it looks very different as dci-p3 profile and calibration.

No, spotify and youtube have no EQ, I haven't any other audio apps.

If nobody else have this issue, I think a clean flash would help. But it's not a big problem for me to live with these two things. Livedisplay working great after one time locking the phone and I can also disable audiofx.
[OnePlus 3 & 3T Cross Device Development] Itachi_Uchiha:
I'm Loving this rom, using this from the last month or so. Keep up the good work!