yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] raphael.e:
Thanks [MENTION=4405529]nvertigo67[/MENTION] for the update!

I did dirty flash coming from 10.08 I guess. sRGB (via livedisplay) seems not to be sticking after reboot. Anybody else experienced it? Other than that the rest seems to be working great so far.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are absolutly right: it's a little difference from Remderkernel to los, I decided to address via device-trees overlay in a way, that works for both, this will also bring back the voided dci-p3 setting. But after fixing the cam and making the announcment, I've completely forgot about. Thanx. Consider it as fixed.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
ob13 firmware package and uniblobs are uploaded and ready to flash.

If you flash the uniblobs, you can use [MENTION=5438598]RenderBroken[/MENTION]'s Render Kernel.

Since the OP states I will not support custom kernels one or another may think the pedantic old man has finally gone despotic - on the other hand: hey, that's the kernel from the guy, who made the eas patches for our kernel. It's only pragmatical to define Render Kernel as non custom kernel. ;)

EDIT:

#3 (Why 3t-only) and #5 (Camera Mods) updated. The packages are updated (removed uneeded libs) and fixed as well.

EDIT2:

[MENTION=313982]home[/MENTION]builders: 141-eas is working as is firmware/141-work (in local_manifest).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Colomonster:
HOLY SMOKES!!!!! that is all I can say besides THANK YOU THANK YOU THANK YOU!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
The latest download zip on Google drive is not there. The latest one is dated 20170816.

Has anybody got a copy or mirror please.

Edit, when I open through chrome, the file is there!

Not there when opening with the drive app. ?

Crisis averted.

Thanks for all the hard work and late nights.

Great ROM
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Colomonster:
https://drive.google.com/drive/mobile/folders/0B_f72wz8rwc6MUIzV1E5b2JENjg?usp=sharing

It's at the bottom on the left. 20170823 clock the little I in the corner to see fill filename
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I get a boot loop every time I soft restart on the latest build. Does anyone have the same issue?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nan0s7:
Nope - it's working fine for me. Are you doing a clean install with Beans Gapps?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
Yes. I did clean flash and installed Beans Gapps Mini. Gonna try clean flash again.

Edit: Just did a clean flash with Beans Gapps only, no root or any other app installed. Still got a boot loop when soft restart.

Edit 2: I may be confused what a boot loop is and what happened to me might not be it. To be clear, what happened is that I get stuck at boot animation whenever I do soft restart, but I can force shutdown by holding power button and it will boot normally after that.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I flash dirty wiping system and installing original gapp and working great
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nan0s7:
Well if you wiped everything besides the "internal storage", then flashed the new ROM zip file, and then followed by Bean's Gapps, the only thing that comes to mind is that you don't have the right firmware somehow (it should be included in the zip) or you're using a weird version of TWRP, or the Gapps version you're using is old. I'm personally using one of blu_spark's custom versions.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I wiped everything except internal storage and USB OTG. I'm using latest Beans Gapps Mini (20170725) and latest blu_spark TWRP (v41).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Confirmed.

Honestly this was the first time I used soft restart: if an app misbehaves, I force close the app. If I want a clean rom bootup I shutdown and wait some secs (complete shutdown and wait really drops all power on most soc parts - reboot (the real one, not the soft one) does not drop the power, but triggers a reboot.

I don't see any usecase (but I admit, that my device is more often soft bricked then yours - at least I hope my testing department only ships mainly working roms... ;) ), that makes this a show stopper for eas.

It would be great, if you could do a cross check against RenderKernel: flash uniblobs-ob13, followed by RenderKernel and cache-/dalvik-wipe. I'm preparing the next update atm.

I'll try to remove that option for now and making softrebbot work ismlow priority. Or is anybody depnding on soft reboot?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Uploaded.

When I started my screen session I saw I had typed "git push"... Surprise: after pressing ENTER the upload beguns... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Most important: did you receive your rom's zip, finally? (no need to answer, if so - if not it would be nice, if someone could make a mirror).

Not sure, if related:

From time to time my carrier delivers cached pages via http (which is ok, but not for dynamicly generated pages). Chrome, Jelly and dolphin are aware of this, and are sending the non-page-cache field in the header. If you receive cached http content in an app, that has no reload button and is not requesting non cached content... Maybe... I tried to discuss that on the hotline... You do not want to do this!

"Don't try to teach a pig to sing; it wastes your time and it irritates the pig." Anthony de Mello
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I tried that and result was the same.

It's okay. It's not a big issue and I don't think many people use it. I only use it after I install a theme anyway, cuz it a little bit faster. :p

Apart from this issue, this rom is working great. :good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Thanx.

Sadly, this is one, I know from the beginning, it takes time... (for each test one reboot + one recover boot from loop, with encryption and pin enabled that's adds up easily to two nights... (it would involve quiet some trail and error, because adbd is constantly restarted in that bootloop, avoiding getting logs). I'm sure we find a more important topic I can spend time on... ...same for [MENTION=6745491]joshuous[/MENTION] and [MENTION=5438598]RenderBroken[/MENTION].

And perhaps it is something different like ShutDownListener - oneplus useses its own classes here, which is implemented differently on los)

"Soft Reboot" will be removed from the next build on.

Thanx for testing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
the installation script unmounts system on its own why we have to uncheck it in twrp? and you say flash firmware before installing rom but the scripts installs rom and then firmware
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
THE PROCEDURE IN OP IS FAILSAFE.

umount: doesn't work allways. If you flash a rom with 3.0.4.1 with system mounted in about 1/3rd of the flashws end up in a corrupted /system file system. And it doesn't hirt for all other usecases.

fw: For the only acceptable reason: it works. For firmware containing builds as well as for firmware-less builds. I can't know, when and from what state a user is starting using this rom.

THE PROCEDURE IN OP IS FAILSAFE.

Before you ask: it is neccessary to wipe system (you could argue: the unconditional patch is writing a binary image containing the fs infos, nothing can persist...) to avoid, that addon.d contains incompatible apps or mods, which would be restored if you don't wipe system.

THE PROCEDURE IN OP IS FAILSAFE.

I bet the the vast majority of issues after clean flashes (on all roms, not only on this one) is related to fail to follow this procedure!

THE PROCEDURE IN OP IS FAILSAFE.

I expect an OP to give a procedure resulting in a runable rom, no matter from whicht state/previous rom/fw I'm starting.

Let me say a last word:

THE PROCEDURE IN OP IS FAILSAFE.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] yannmrt:
I think I never use either the soft reboot, so not a big lost on my side. :good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Graphics Artist wanted!

Now, with "Nvertogo UNOFFICIAL LineageOS 14.1 build" renamed to NLOS-14.1 it's time to think about a logo for a screens background and perhaps later a NLOS specific boot animation.

Sadly, I'm in regards to graphics art absolutly talent-free. What do I think of?

should be awesome on amoled.

large scale in 16:9 (should be usable on Samsung Galaxy Tab S T800).

my favorite color is red - my favorite non-color is black (that doesn't mean it has to be in that colors - but I wouldn't mind, if so... ;)

If I would steel art pictures in MOMA I would go for Magritte, Dali, Picasso or Klimt - Chagall would be save. (Again: nothing that really matters...)

I could think of playing with the four Characters (please no version information in a logo), the O could be a circle, that groups the other three chars). (Perhaps like a painted Anarchie A - but I have no idea what to do with the additional two letters...)

Perhaps additionally saved in a format, which supports layers. I think it would be easier to make an animation later... But that's only a guess: I'm noob on graphics and therefore I have never reallymworked with gimp or photoshop, and I don't even know other apps.

I'm not in a hurry on this. But I think it would be "nice to have". And if I don't ask, I'll never know, if there is somebody around willing to contribute on a non-technical topic.

I'll attach one of my best tries. (And: yes, it's not only allowed to laugh about - it's obligatory... ;)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Since I've never used soft reboot til today, I have not the slightest idea, if this has been working on the latest eas-less builds.

Can anybody confirm it was working some time ago?

If so: when did it break exactly (last build working and first build broken)?

Thanx in advance.

I would be very interested in your personal ux. What has changed for you with introducing eas? For the good or bad? Is ther a perceptable difference (I'm not interrestwd in benchmarks, but in your expirience!) If there is a difference for the good, what is it? Keeping sources up to date takes time on my side (not 8 nights - that was only the first bringup - but if I'm the only one liking eas (I like it because of it's clean design and openness for future additions) I can spend my time on other topics. I'm absolutly willing to do this work and spend this time, if you like it - but keeping it only for my (or your) ego(s) (so we can claim: hey, it's an eas enabled rom), is not worth the efford.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] hypnoc:
I was using build 20170810 before coming to this build. I think it worked fine.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
I think, at least for me, microstuttering is less. Much smoother. Still some stutters occasionally, which doesn't happen on vertexos for some reason. I'd keep EAS. Most modern hardware is going to switch to it anyway.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vip57:
Can someone post screenshots of the rom

I'm really interested in flashing it
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lapapunk:
What did they'll give you? It's quite clean android with new eas things, without a ton of bugs and unusefull features.

Just do it. Flash it and feel happiness.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
[MENTION=4405529]nvertigo67[/MENTION] any plans for introducing Color Engine? :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This is los based. As you can read from the first three or for paragraphs, the changes are under the hood (eas, oms, microg and toolchain), so you can assume you get the graphical los expirience.

There is one exeption: this rom will show lte in the status bar instead of 4g.

OT: Background: at least here in Germany the carriers are allowed to call hsupa/hsdpa "LTE", what is technicaly inaccurate but legal, because "Long Time Evolution" is a kind of topic, but not a defined set of specs. The specs and protocols are defined in 2g, 3g and 4g. (For reference: https://en.wikipedia.org/wiki/High_Speed_Packet_Access)

I'm not a lawyer, nor a sales manager - I'm techi. From this point of view I feel sick, if hdupa connections are shown as 4g, what is obviosly a 3g protocoll.

My carrier has funny and misleading names for real 4g stuff: VoIP or LTE+.

Again: I'm techy and no lawyer. As a techy I call this fraud. A lawyer would call it marketing.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Not surprising at all: the frameworks of vertexos are not only caf based (instead of lineage, which is aosp based with caf commits merged).

This is just maths: we are talking about probabilities (like quantum physics: I'm not here in my home, but the propabillity of being at home is very much higher, then being anywhere else). That being said, assume you have 100 lines of code doing X. Now you add another 50 lines to add a feature and 50 more lines to support specific hardware. Now you have 200 lines of code.

In terms of probability you have doubled the chance to delay things (btw: you doubled the probability of introducing bugs, also).

As a rule of thumb:

more features (like customizations) ~ slower

more features ~ more bugs

more complexity (true for all layers from hardware to user level) ~ more code ~ slower ~ more prune to issues ~ more difficult to analyse (debug)

Some of these relations aren't proportional but exponential. If you add up all mores, there you are.

If you want a clean, systematically straight forward caf based build, from a dev open minded enough to add i.e. Camera from stock, I've to ask you to change to vertex.

The very first build I've done for myself was OSS. My idea was to start from there, and add some features I want on top (with this in mind, reread vertex OS). This was bak in early January. At that time I found only one caf based rom. I tried to get in contact with the dev - to no advance. Sadly, I was not happy with OSS implementation of app ops, and wasn't sure, if I can do this alone. At this point I decided to return to cm/lineage.

I'm pretty sure, if I had known of vertex and [MENTION=6745491]joshuous[/MENTION] and [MENTION=5438598]RenderBroken[/MENTION] and their plans, this rom wouldn't exist. Though I like every single user of this rom, I can recommend to change to vertex with one smiling and one crying eye.

Last word on probabilities: the probability of regressions introduced by the dev in the kernel is higher if one single medium talented kernel hacker is doing so, compared to two talented and expirienced kernel devs. This is just basic maths.

Honestly: I'm still surprised (and sceptical about) how awesome our eas kernel is running. I've expected me to put in some serious regressions... ...but it's working... with the patches from [MENTION=5438598]RenderBroken[/MENTION] "medium talented" seems to be enough...:):p:good::angel::)

;) thinking vs. knowing: the difference between red eyes in the morning or a night of sleep... Thanx anyway. Opted out "soft reboot" for now.

As a sales manager I would put this in a high color sales paper:

User claims:

"NLOS is always shipped with buid-in happiness!"​

Let me finish the integration of eas. Please remember: atm I have to take every minute to keep us up with los, to answer questions or to add something from my sleep time. The chance to get something important for you implemented is higher if you link ready to use patches, instead of just throwing a keyword (this is black and white, if you look closely you'll find all rainbow colors in between).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xpissio:
Oh yeah, sorry. I'm not very good with GitHub, I found only this (https://github.com/AOSPA/android_frameworks_base/commit/2cd619e7b6eb58600e1a6f95482ed2ff5f2b33ef).

Little note, Color Engine is a Paranoid Android feature. :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
I can only agree with you. Stay on substratum/oms. It's working fine without any issues.

[MENTION=3456089]nvertigo[/MENTION] I'm a little bit confused, what is the difference between your oos camera and the by [MENTION=4837394]siankatabg[/MENTION]?

Btw: oos camera the working much better than the included snap cam.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
I don't know: I included OnePlusCamera v1.4.0 half a year ago. When realozing, that the libs doesn't have to live under /system, I decoded to put the libs inside the apk to make it just another installable cam apk. It's the callback freed version from @kxzxxx. I've done so to give more freedom of choice to the user - so my job is done, with removing it from the rom; your job is to use this freedom to choose and tell me...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vip57:
the rom is great

it is smooth and no problems till now

i will wait to check the battery life

but overall amazing rom
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Dhairya:
the only issue i am facing is front snap cam fc with media server denied :( rest is amazing oos cam doesn't have the issue and gcam is missing 1080 60fps rest in love with the rom
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mcdachpappe:
gcam 4.4.020 60fps will work with the attached media_profiles.xml if its different to yours (System/etc).

slowmotion is working as well..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Are you talking of the well known one, or any other ffc issue? The issue wirh constantly ffc crashing is fixed in last build.

Perhaps some persistent settings.

Grrr... Just finished, what I thought would be the next updated build... ;)

I'll put it in the upcoming build, if you can confirm that it has no impact on Snap and OnePlusCamera.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No, it's not different:

ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $ colordiff -u ../../../out/target/product/oneplus3t/system/etc/media_profiles.xml /mnt/export/data/Downloads/incoming/media_profiles.xml
ingo@adler /usr/local/src/cm14/device/oneplus/oneplus3t $

This can only be placebo. (Or you attached the wrong file) The one you posted is exactly the profile shipped with this rom...???

What is the source of this file.

BTW: Sadly, this took the time I've planned for the update. Stay tuned, but I don't know, if I get it uploaded and announced today... :(
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Dhairya:
yes the well-known issue of front cam fc with snap cam sultan fixed it in his build

https://github.com/sultanxda/android_device_oneplus_oneplus3/commit/ffa7f74fec608419a70e1c5a9213e2d2e92ce1b0

rest is amazing loving it snap cam is working fine with slow motion and stuff thanks for the rom just that issue :)

Regards,

Dhairya
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
UPDATE

Build 20170828

Releasenotes:

This build requires firmware OpenBeta 13 (aka ob12). An archive of all firmwares can be found below in the firmware section of Downloads.

[MENTION=6745491]joshuous[/MENTION] and [MENTION=5438598]RenderBroken[/MENTION]deserve all credits and honor for the current EAS implementation. For reference and/or own attempts to build a kernel and a rom with EAS support see https://github.com/EAS-Project/msm8996-eas and VoxPopuli.

I've changed the file names of the display blobs to the names unifoed roms use and most custom keenels are expecting. This means, uniblobs is obsoleted by this build and future builds.

This means also: This rom would run on op3, too - if the assert on display.seriws is removed. If anybody, who has his hands on a op3 is willing to do the support and build testing on op3, drop me a note and we'll see what's possible....

Changelog:

sepolicy: surfaceflinger.te: allow to set diag max size. — nvertigo

blobs: use the hacked firmeware layout for unified builds. — nvertigo

blobs: remove perf-profile[1-6].conf. — nvertigo

sepolicy: init.te: remove dublicate permission. — nvertigo

remove_packages: change CMUpdater to Updater. — nvertigo

overlay: disable soft reboot for now. — nvertigo

EAS: op3t: set cpu max freqa according to SnapDragon 821 specs. — nvertigo

Call me NLOS! — nvertigo

op3: Set config_sustainedPerformanceModeSupported — Srinath Sridharan

EAS: livedisplay: add DCI-P3 setting, fix sRGB for EAS patched kernel. — nvertigo

op3: Add permissions for accessing thermal-engine — Philip Cuadra

op3: thermal-engine: Add thermal client library header — Steve Pfetsch

op3: Kang thermal HAL from marlin — dianlujitao

op3: Kang marlin thermal config file — dianlujitao

op3/t: add conservative, interactive, ondemand and userspace governors. — nvertigo

Revert "Revert "ARM: dts: 15811: Target different GPU firmware image name"" — nvertigo

op3/t: defconfig: enable WALT and make it default. — nvertigo

op3/t: defconfig: fix some doubles and inconsistencies. — nvertigo

EAS-patchup: binder: add two lost lines. — nvertigo

remove perf-profile[1-6].conf. — nvertigo

op3/t: use the hacked firmeware layout unified kernels expect. — nvertigo

Camera- and Gallery-Download (fixed versions)

[SIZE=+2]DOWNLOAD[/SIZE]​

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] vikkut:
Wrong file link (lineage-14.1-20170805-UNOFFICIAL-nvertigo-firmware-oneplus3t.zip.md5sum).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Dhairya:
Is it calibration issue? Heavy drain :( using 23rd aug buid
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] DrBajwa:
Soft Reboot works on Aug 16th build

I am still on the 20170816 build, I use soft reboot frequently and it has been working flawlessly. I use it as a workaround for v4a not processing audio when headphones plugged in for some apps (spotify). I plug in my headphones, soft reboot and have working v4a within 10-15 secs
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] wistlo:
new schedulers

Any guidance now on which of these governors would be ideal for this ROM? "schedutil" looks like the new default. Earlier this summer, "conservative" was favored over "interactive".

Does EAS affect which scheduler to choose? I manage my governor through Kernel Aduitor. Both "schedutil" and "conservative" work well with 20170829 NLOS.