Before anyone asks, I would like to remind MIUI peeps that vbantom is OSS only! Please do not flash vbantom on MIUI.

I may do something like this for the next upcoming STRIX-Revived update BUT it'll strictly support OSS only* as the whole lineage-maphide thing is useless in MIUI where such custom ROM detections do not exist

*As in it'll not ask you during installation if OSS or MIUI, it'll automatically install OSS dtbo

Although, that depends on how many AOSP ROMs work and boot fine with it

Links to the ROMs if anyone interested to try any of what I listed
A15 EvoX / Derpfest GSI
A14 HyperOS
A11 ShapeShiftOS
A14 OxygenOS
A15 HyperOS
Did you seriously think I'll link stock ROM?

I'll end poll when I'm feeling lucky 🍀

Okay, time to boot A15 EvoX/Derpfest then

If both fail to boot, then basketball 🏀: [MISS] I'll move on to the runner up option (HyperOS 2.0 ☠️)
[IN] Get scammed, I'm flashing A15 Pixelage
If either one of them successfully booted, then next in me flash queue is 3rd runner up option (A14 HyperOS)

But before that, time to publish new STRIX-Revived and vbantom updates
SUSFS 1.5.2!
vbantom: only KSU builds will be updated

STRIX Kernel Revived 20241202

"When the FS is SUS!"

Changelog:
(from 20241125-STAGING) [MIUI] Fix display glitch issue that occurs randomly or when switching refresh rates
Fixed soft bootloops when charging
Fixed disconnect and reconnect while charging issue
Added BORE Scheduler 5.1.0
Picked fixes and changes from unmoved's STRIX-inline fork
—————————————————————
rsuntk's KSU fork 12002 (required manager apk!) + SUSFS 1.5.2 (module)

The difference between [KSU] and [KSU-NEXT] is that the NEXT build has lineage map hiding which should help hide custom ROM detections if using the recommended linked susfs module, however, not all ROMs like it and can cause bootloops on those ROMs, in that case, please switch to the [KSU] build
[KSU-NEXT] build supports OSS only!! DO NOT INSTALL ON MIUI!!! Use [KSU] build if MIUI instead

Kernel Source (a15-ksu branch for ksu changes, a15-ksu-next for ksu-next changes)
🤓 diffs since last release
⚠️ Disclaimer
Credits:

@itsshashanksp for the eBPF A15 commits
@aryannn999 for scripts and fixes from vantom that are very useful
@unmoved21 for fixes and changes from own STRIX-inline fork
@xfirstnamelastname and @sidex15 for BORE Scheduler
@RooGhz720 for the 90Hz refresh rate
@fiqri_ardyansyah for the kernel everyone loves ❤️

@RissuDesu for their KSU fork
@changhuapeng for the SUSFS 1.5.2 commits
@xfirstnamelastname for the lineage maphide and ksu commits
@simonpunk for SUSFS

vbantom Kernel 20241202

"When the FS is SUS!"

Changelog:
None, same as 20241129. Thus, NO-SU build has been skipped (it has only been 3 days dawg 😭)
———————————————————————
rsuntk's KSU fork 12002 (required manager apk!) + SUSFS 1.5.2 (module)

The difference between [KSU] and [KSU-NEXT] is that the NEXT build has lineage map hiding which should help hide custom ROM detections if using the recommended linked susfs module, however, not all ROMs like it and can cause bootloops on those ROMs, in that case, please switch to the [KSU] build

Kernel Source (and rebased-15-ksu for KSU changes, 15-ksu-susfs-next for KSU-NEXT changes)
⚠️ Disclaimer
Credits:

@itsshashanksp, @RooGhz720, @fiqri_ardyansyah and @xfirstnamelastname for tweaks and features from sleepy, aghisna, strix and westcoast respectively
@aryannn999 and @Vantom for bes kernel

@RissuDesu for their KSU fork
@changhuapeng for the SUSFS 1.5.2 commits
@xfirstnamelastname for the lineage maphide and ksu commits
@simonpunk for SUSFS

Before anyone asks, no, the known issues are still NOT fixed