OKAY, Jan ACTUALLY FIGURED OUT WHATS GOING ON WITH STRIX AND PULKIT TREE ISSUE
Another staging build to hopefully and finally fix this issue for once

Unfortunately the fateful day that nobody wanted has arrived, today Google still
has NOT sent me an email forcing me to discontinue bad appel on action project.
Thanks to all of you for the support I have received during all this time.
Let's hope higher FPS can be done

https://github.com/backslashxx/bad-apple-ascii/

Moving on...
Due to recent changes (and more on the way) now breaks stuff for MIUI (more specifically A15 OEM ports like HyperOS 2.0 and ColorOS/OxygenOS) and expected to be only get worse from
I'm planning to soon make STRIX-Revived OSS only and yVy MIUI only (I'm sorry I'm not gonna go through the poll made regarding OSS support for yVy)

Okay
So the current OSS problems with STRIX-Revived are
> I can fix pulkit tree issue, but then it'll break support for any non-pulkit tree AOSP ROMs and MIUI ROMs

> I can add A15 QPR1 support (i.e to boot on Project Pixelage 2.3 and Lineage 22.1) but then <= A14 is broken again (see this STRIX-Revived release where that was a problem with initial A15 support)

I really don't know how to go on with this other than to have much more build variants which is just unmanageable 😵‍💫

Thanks to all who tested the staging builds... I hope I can see how I can figure this out

STRIX Staging build 20241231
Fix Pulkit tree issue by offering it as a 3rd option after you choose OSS/AOSP dimensions during flashing
* I have updated the AK3 installation script to include the alternative dtb and dtbo for pulkit tree, it will ask you after you choose OSS/AOSP dimensions if this is an AOSP ROM compiled with Pulkit's tree, as well as advising you to choose no (Vol Down) if unsure. Simply press Vol Up to install the alternative dtb and dtbo images if you are in a pulkit tree ROM to fix no camera and audio issues. If you choose MIUI dimensions this option should not show up for you and it should install MIUI dtbo

Picked 5.4 bpf backports to support A15 QPR1+
Merged @xfirstnamelastname's 4.14.355+3 brickport upstream
* This time I re-picked the bpf commits properly so I hope it boots just fine for <= A14 🙏

Happy new year! 🎉
Even though it's still 8 PM for me (GMT+2) but I'd like to thank you all for a wonderful year 2024 has been

KSU Build because why not?
Now switched KSU base to @ksunext!
SUSFS 1.5.3!
Merged lineage maphiding into normal KSU variant as it won't do anything or introduce any detection points for MIUI. So yeah, no more KSU-NEXT variant
Manager APK direct dl link (or go to the tagged channel and grab nightly manager release. Whichever suits you)

Again, if you're coming from previous magic mount KSU builds. Please back up your modules!
Alrighty then, happy new years!

@ksunext has now switched back to magic mount with the removal of susfs too
Needless to say, I won't be upstreaming to that, and I'll be using the legacy ksu-next branches (and maintaining them if needed)

And unfortunately, I have now received reports that specifically for A13 and A14 QPR1 it does not boot
I guess I'll have to drop the 5.4 ebpf backports and on-hold A15 QPR1 support until further notice 😓

One last poll before stable STRIX-Revived release
It's regarding 90hz, I have now made a hacky fix to it where fixes the brightness twitching as well as sudden brightness increases (especially when switching from 120 to 90)

However, it doesn't fix the green tint and weird gray colouring, but rather, makes it worse! As you lower the brightness with this fix in 90hz, it'll not lower, but actually be very greenish and washed colours. You can workaround that by disabling automatic brightness, set brightness to 50% or more and then lower the brightness only via extra dim feature.

So I'll give you guys 3 choices to vote for
1. Merge this fix and have you all work around it with extra dim
2. Do not merge this fix aka do nothing
3. Drop 90hz altogether