Notes:
The first option would still be separate ZIPs for both MIUI and AOSP, just that the kernel base supports both without issues
It'll also be my very own kernel semi-from the ground up (crdroid kernel source will be used as base), not a fork of either STRIX or Vantom

2nd option just cause they're specific to AOSP and MIUI does not necessarily mean it would be bug free and shit. Also, development cycles will be dependent on what ROM (AOSP or MIUI) I'm on.
Example: If I remain on a MIUI ROM, development will be only occurring for ReSTRIX whereas vbantom will be stalled until I switch to an AOSP ROM.

I'll remake the poll when the circumstances of the 2 options are throughly understood

Okay, you guys don't want me to do something from the ground up myself and instead want me to base off the work of others. Fine...

Welp, keep an eye over at @vbaromtracker

If it's an MIUI ROM: ReSTRIX will be worked on and vbantom will be stalled
If it's an AOSP ROM: vbantom will be worked on and ReSTRIX will be stalled

Regarding the recent blowup about "ksuinit" being proprietary; it's irrelevant to non-gki (us as in sweet) as we just directly hook into the kernel itself and do not have any dependency on "ksuinit". Also, LKM method for KSU is intended for GKI (not us as in sweet) devices that do not have their kernel source code available.

Still, take what you will with that information...

To address the issue on the proprietary code of ksuinit being closed source, it also exists on ksunext, since we are really against closed source software, it makes sense to drop LKM mode to keep ksunext fully open source, but it makes sense for them to keep it closed source for obvious reason to not be exploited by others and possibly code theft or a reason something entire unknown but it's making a fuss over the community, tbh i could just drop ksuinit LKM mode entirely from ksunext in next release untill we can reverse engineer it or an entirely alternative new code to replace the proprietary code ksuinit.

Till then ksunext may not support LKM.

Weird colours on 90hz workaround: (STRIX-Revived MIUI variant and los-20 perf):-

1. Switch from 60hz first, then 90hz (if you're on 120hz, then switch to 60, then 90)

2. Kernel has KCAL, so via FKM -> burger menu -> Display Control
* Lower Red colour to 246
* Lower Contrast to 245

If via Smartpack kernel manager, then burger menu -> Screen
* Lower Red colour to 246
* Lower Screen Contrast to 117

The colours should now look identical to 60hz

susfs stopped updating for non-gki
while theres susfs 1.5.7 for gki, theres nothing relevant for us yet.

1.5.6 - nothing relevant to backport
1.5.7 - nothing relevant to backport

Update 20250427
Changelog:
Fixed fast charging and ln8000 issues
Other misc changes related to compiling

Kernel Source

Download

THIS KERNEL IS FOR MIUI ONLY, it is not affiliated with other perf kernels.

Channel is public again

My personal recommendation for recoveries depending on what ROM you'll flash:

If it's an EROFS AOSP ROM: Ofox EROFS variant

If anything else that's not EROFS (non-EROFS AOSP ROMs, MIUI ROMs and OOS/COS ports): official TWRP

As promised, re-up to telegram when channel becomes public

This is not affiliated with other perf kernels | @tbyool

Calling for porters (HyperOS and OxygenOS/ColorOS) to test kernel..
DM me to if you wish to test 😊

#ReSTRIX

Very important reminder ^

Please quit harassing other developers for having similar kernel names....

This kernel is not affiliated with other STRIX forks | @tbyool

This kernel is not affiliated with other STRIX forks | @tbyool