[Moto Maxx General] ChazzMatt:
It will take [MENTION=5747496]bhb27[/MENTION] coding the current Motorola Marshmallow Quark kernel to Oreo -- the same way he coded it to work for Nougat.

Our previous CM dev [MENTION=2228410]Skrilax_CZ[/MENTION] did the original work back in early 2015, first coding Quark Motorola Kitkat kernel to work with Lollipop. Then when Lollipop Motorola source code was finally published he used actual Lollipop kernel in the CM releases. Once CM had a kernel for Quark, THEN other devs could "port" ROMs and just plug in the CM kernel.

[MENTION=5747496]bhb27[/MENTION] started doing dev work about this time and released his own "custom" kernel with more features to complement the "stock" CM kernel [MENTION=2228410]Skrilax_CZ[/MENTION] coded. You could use 12.1 ROM (with Lollipop 5.1) with CM kernel or even RR Lollipop with CM kernel -- or use those ROMs and install [MENTION=5747496]bhb27[/MENTION]'s custom kernel. But all the ROMs uses the CM (now LOS) kernel as "stock" kernel. It's what makes ALL the Quark ROMs possible in the first place.

(For our Quarks, even AOSP ROMs -- ALL ROMs -- use the CM kernel. They have to. There are no others. When Sunshine unlocked the Droid Turbo bootloader [MENTION=2228410]Skrilax_CZ[/MENTION] re-coded the Quark CM kernel to also work with XT1254 -- otherwise these custom ROMs would NOT be compatible for all Quarks. The kernel is the foundation.)

Then, when Motorola Marshmallow got released in late 2015, same thing. First a Lollipop kernel was coded to work with Marshmallow, then MONTHS later (July 2016, for XT1225) when Motorola released Marshmallow for Quark and then the kernel source code (September, October?) finally an actual Marshmallow kernel to work with Marshmallow. (Lollipop custom ROM for Quark beat official Motorola Lollipop and Quark Marshmallow custom ROM beat official Marshmallow by MONTHS.)

By this time [MENTION=5747496]bhb27[/MENTION] had taken over all the kernel work, coding the basic "stock" kernel for all the Quark ROMs as well as his name-sake custom kernel.

When Nougat arrived, there was no official Nougat Quark kernel from Motorola -- so we had to keep using Marshmallow kernel. And [MENTION=5747496]bhb27[/MENTION] did the work to let Nougat ROMs use that kernel.

Will be the same thing with Oreo. But [MENTION=5747496]bhb27[/MENTION] still has to code it to work smoothly with Oreo.

Also, there is no more CM. We now have LOS as the "base". [MENTION=5747496]bhb27[/MENTION] does not release official LOS ROMs, but that's where the device kernel files go that all devs pull from.

So, [MENTION=5747496]bhb27[/MENTION] will use Marshmallow kernel in LOS Oreo tree to make a stock kernel for all ROMs. At that point he will release an Oreo ROM based on that work. (Right now he's the dev for both RR and crDroid ROMs. Last year he surprised us by releasing then-new Nougat crDroid first, whereas he had been dev for Marshmallow RR and Mokee, and RR was his favorite.)

[MENTION=5747496]bhb27[/MENTION] will also probably release an advanced "standalone" custom kernel with more options, like he does now, but it's that base stock LOS kernel which is most important.

After he releases his Oreo kernel work, then other Quark devs can use that stock LOS Oreo Quark kernel to release their Oreo ROMs.

The kernel will be the foundation of any Oreo ROMs and it will all depend on [MENTION=5747496]bhb27[/MENTION].

But don't pester him. It will be ready when it's ready.

__________

TLDR: [MENTION=5747496]bhb27[/MENTION] is the man. He'll do the Oreo-compatible stock kernel first and then the first Oreo custom ROM. Everyone else will then follow with other ROMs.