[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I'm gonna post this here as well as add it to the "Release Notes" section in post #2 for the just-published 10.2 official, because I want to set some expectations:

I probably need to make a 10.2 "hotfix" build soon, since all lot of things have changed since I created this build (including probably yet another spoofing device fingerprint). But sitting on it longer won't help anything either. So off we go to release!

I'm busy af right now in real life. It never seems to stop. That makes it really hard to keep up when things like this are going on that will impact our devices dramatically going forward:

This build was made just before the official promotion of LineageOS to Android 14.0.

There's a lot changing in crDroid ROM sources, and it seemed like things were unstable for a couple weeks after I made this build. Some of that is due to...

The release of "lineage-21.0" officially upstream in LineageOS, and associated changes there. I had actually synced my build tree BEFORE this went live, so I don't know how many of the "new" Lineage 21 apps I have included. It effectively became a mid-month rebase for the crDroid dev team however, in order to reconcile so many changes within LineageOS (which we are based upon very closely).

With 14.0 QPR2 & March ASB just around the corner, that might force us to migrate to using the 4.19 kernel base & associated patches that EdwinMoq has been working on for months & months. I've got it working pretty well here, but it's time-consuming to deal with, there's a lot of things like DeviceExtras that I haven't brought up yet using my 4.19-based trees, and "time to work on this volunteer hobby" is what I don't have right now.

Unfortunately, you actually can't just apply a 4.19 build over a 4.9 installation without a factory reset; the FBE encryption driver is set up differently in the newer kernel and requires a factory reset/wiping userdata. So figuring out how to make that break is yet another thing to deal with; and I don't have time.

So I don't know what the future holds. I'd love to put out kernel 4.19-based builds, but I might literally have to create new "enchilada-4.19" and "fajita-4.19" devices in order to make sure that nobody gets their installation killed by a 4.19 OTA being released for a 4.9 device. And it takes time (and a lot of drive space!) to implement that properly and keep the namespaces separated and everything.

It might be good that I don't have TIME in my life for the next 2-3 weeks to worry about doing all the busywork to create new devicenames entirely for 4.19 builds, so I'll be cruelly forced to wait & see what they do in official LineageOS; since the awareness that all sdm845 kernel 4.9 devices are about to hit a wall seems to be rising and there's growing discussion about making some coordinated decision about what to do with them when March hits... which makes it easier for me to follow along with instead of pulling my hair out trying to figure out how to preemptively rework my own infrastructure here without breaking existing 4.9-based build capability.

Anyway, I'm about to disappear for another 2-3 weeks, but I might be able to resurface with an updated 10.2 release 2 in the next week (I guess the crDroid devs have already updated the PPU spoof fingerprint, and I might have a fix for some wifi-related & bluetooth-related issues in some edge cases).