[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Don't assume I know everything. Took me 10 minutes to find out it's a theme engine. Before this elemantal information, I found many articels and postings full of enthusiastic credos stating this is "the future of android". Besides from making me feel noob (really no information, which purpose this "future of android" feature is to serve - I realy thought I missed something important while not sleeping and ignoring my environtment...), this reminded me of the overrated hype about oms/substratum some months ago.

When I first read color engine is a theme engine I had to laugh. I will always be surprised how different I'm from that, what google thinks I am - sometimes it feels for me I'm different from the rest of the world... This is true for theme engines. Different or not, I've always been very clear on theme engines:

I HATE THEME ENGINES.​

They just add multiple ugly sources of issues and increased work to keep all sources up to date when preparing a build. The probability of issues is increasing exponential from each newly introduced source of error:

the introduced source itself.

the way the patches are generated (minimized but not excluded by git)

errors introduced when the patches are ported from the sample implementation (or the one from an other device) to the roms base.

same as above, when implemented on on THIS rom (using Nathan's wonderfull work).

Errors in Substratum.apk.

Errors in the applied theme.

A real pain in the ass is debugging. If I receive an issue report here and can reproduce it, the very first thing I do is: Making a build without oms, reproduce it on that oms-less build and dubug from here...

I agreed to put oms in, when I found Nathan's lineage prepared patches and his merge script, because this saved time when creating an updated build, because really many people requested that constantly over a longer period (makes me think it's more then a hype) of time. Since my first priority in making NLOS is - was - and always will be - stability! I've always been as clear as possible, that oms is immwdiatly droped, if one of these three points becomes true:

if Substratum or theme's issues appear in this thread.

if oms patches cause any issues on the rom, other system apps or anything related to instability or bat drain.

if lineageos decides to implement a theme engine.

This is not object to be changed.

BTW: If you look at aospa.co they are promoting:

Here on xda I found:

https://www.xda-developers.com/paranoid-android-substratum/

What does that mean? substratum integrated in color engine - or vice versa? One enhanced by the other?

Which way will lineage go?

What will be the next "future of Android"?

I think for the most users NLOS with root-less OMS7 support is a comfortable seat awaiting "the future of Android", while watching relaxed at the next theme hype...

This is like with vertexos for a "cleaner" rom, just the opposite (and I've always been clear on that, too): if you are looking for always the newest izzybizzytweaky feature, or the most customization options, NLOS is just NOT your rom of choice.

EDIT: https://www.xda-developers.com/android-oreo-command-line-themes/

Besides all hype, OMS seems to be the most plausible choice, atm.

EDIT2: https://www.xda-developers.com/android-oreo-rootless-system-theme/

You know, that quite some themes - if not most - comes with an option to change the ascent colo, don't you?