[OnePlus 6 & 6T Cross Device Development] Terminator.J:
9.3 (Android 13.0_r35 with QPR2 merged) seems to be moving into "okay these are worth putting out there for testing" status now, so I'm starting to make testing builds available. You can check out my "TJ-Releases" GH repo or join the TG group to find testing builds while we hammer out the kinks in what will be the next official release.

And while those test builds are not *currently* being compiled on the Deck, I *did* finally get the last bits I've been waiting for ordered in so I can put in the replacement 1TB nvme storage drive, and upgraded thermal interface material & pads, and we'll hopefully be able to get some "after" numbers for temperatures, i/o performance, fan speeds, compile times, etc. 🤓

Maybe the April (March ASB still I guess) release will still end up being compiled on the Steam Deck after all...

Meanwhile, I'm working with Nikhil Menghani to get a perpetually-updated config for NikGapps set up for crDroid for OP6-series, so I can just point folks to that on SourceForge to always get a Google Apps package that should fit in our tiny little system partition properly and work properly.

Let's see, other news...

- Everything major in 9.3 seems to be working for us (RIL, IMS, SMS/MMS, WiFi, Bluetooth including transition to officially-provided apt-X and apt-X HD encoders from Qualcomm, NFC at least for contactless payment same as before on 13, Camera, real fp sensor on enchilada & UDFPS on fajita, etc etc) without the horror stories that some XIaomi devices seem to have had the last few weeks, and I've been daily-driving it without any real issue.

- Still haven't switched to using dynamic partitions yet, because Nik Core + addons and MindTheGapps still fit in non-dynamic system/ without failure to copy properly during OTA update. If/when Android just gets too big, I'm not going to make it read-only, because the performance difference isn't worth it. You'll be able to install GApps or microG or just not and stay vanilla, as you see fit, if we ever make that jump. You'll know when it happens, there's just no need yet.

- OnePlus Camera & Gallery keep working, with watermark, actual HDR exposure stacking, and 60fps video record. You're welcome, @optimusprime9811 😘 glad you've been enjoying the work AB & I put into making it possible. Thanks to bananafunction, we're making progress on narrowing down a couple camera-related commits that seemed to be responsible for a handful of Qualcomm Crashdump mode crashes when heavily using the camera. It's always been a *little* iffy on this device with custom ROMs though, so if you need to use something heavily (with exposure bracketing for HDR), your most stable experience will be avoiding OnePlus Camera & Gallery altogether, and use a v7.3 or v7.4-based GCam mod like DMGC v4.5 or even Urnyx, rather than one of the new v8+ based mods. Personally I do use my camera a lot, and have had *one* Crashdump in the last 6 months, which ... I don't even remember if I had been using the camera at the time. Think it was actually MMS-related, because my carrier is ****e.

- Battery life continues to be amazing, especially if you run vanilla (no Google Apps installed), and still very responsive. I've got a user with a magic fajita that seems to have won the silicon lottery with his SoC and display panel, who has logged just over 24 hours SOT on one full charge this weekend.

- Any bootloops back to recovery when applying updates are most likely due to Magisk versions (and unofficial forks like "Magisk Delta") with build numbers newer than 25206. There's a huge argument right now about addon.d support, and there are some changes in 25210+ that cause problems when trying to run the booted OTA "Updater" activity that calls the Magisk addon.d OTA survival script. Most any bootloops after updating, whether due to Magisk or Google Apps can be solved by rebooting to recovery and manually adb sideloading the ROM zip, rebooting to recovery again, and flashing your Google Apps (or microG, or none) package + Magisk. If you accidentally "upgraded" to Magisk newer than 25.2 stable, then do the dirty flash install method from recovery, but DON'T flash magisk. Reboot to system, uninstall the Magisk app, reboot back to recovery, then adb sideload 25.2 stable, reboot to system, and don't update it.

I know v26 just got released and there are now canary builds at 262001 and possibly newer. Maybe they work, but I haven't tested yet. If you feel like testing, try installing one of those, then doing a local update from Settings > System > Updater, and let us know. If you're still getting boot loops even without Magisk, you probably used a huge-ass Google Apps package that won't fit in our small system partition. Please read the 2nd post in this thread, and clean flash with the recommended bundle instead.