Last poll before finally an update for STRIX-Revived

Note: Higher version number does not always mean better 🤭

Anyhow, for the next release, I have *definitely* fixed the following issues below:

* LN8K disconnect and reconnect + BQ soft reboots
* IR Blaster only working for (aryan's tree) AOSP (unsure for pulkit because no testers)
* Sluggishness and less smoothness

Bad news, no I've not fixed it 😔

Sorry, I'll add that to "Known Issues" list when the update is out.

STRIX Kernel Revived 20250202

"Whoops, my bad, I slept the remaining half of the month"

Changelog:
(From 20250121-Staging)
- * ->> [UNIVER]
- Merged KSU and NSU into one zip file, now it'll ask during flashing which one to install (expect if you're using Magisk, it'll enforce NSU.)
- Fixed IR Blaster only working for (aryan's tree) AOSP ROMs (thank you @dereference for the fix)

Finally.. Fixed all LN8K disconnect and reconnect issues and well as soft reboots for BQ (make sure to thank @aryannn999 for saving LN8K)
Dropped CASS (turns out it was hogging things down and offered worse bb, my bad 😔)
Reverted kernel timer ticker back to the EOL STRIX value of 100Hz
Now using 8/4 Pelt
Allow swappiness to be set up to 200 and default to 100 (Hint: use this module and edit service.sh file inside module dir after installation to set swappiness beyond 100)
Other misc changes and upstreams.
Now compiled with ZyC clang v21
[UNIVER] DOES NOT SUPPORT A15 QPR1, USE [enAOSP]!

[enAOSP]
Initial AOSP only build offering support up to A16/Baklava (merged 5.4 ebpf backports). To be used for A15 QPR1 ROMs. Same changelogs as [UNIVER]

[leMIUI]
Initial MIUI only build with all ebpf changes reverted and supports up to A14 (does not support A15 HyperOS, use [UNIVER] for that). To be used when [UNIVER] does not boot on your MIUI ROM due to ebpf related reasons. Same changelogs as [UNIVER]

For more info about the variants, see https://t.me/tbyool/987
————————————————————
@ksunext - Next v1.0.4 (12348) (manager apk) + SUSFS 1.5.4 (module direct dl)

Kernel Source
❗️Known Issues
⚠️ Disclaimer
Credits:

@aryannn999, @itsshashanksp, @unmoved21, @xfirstnamelastname, @RooGhz720, Jan and @dereference for the fixes, tweaks and features from their kernels
@fiqri_ardyansyah for the kernel everyone loves ❤️

@rifsxd for KernelSU-Next
@real5ec1cff for bringing magic mount to KSU
@xfirstnamelastname for the lineage maphide and ksu hooks commits
@sidex15 for the SUSFS module
@simonpunk for SUSFS ❤️

@hdrd13, @konfigurare and Jan for testing

2 Things regarding that issue:

1. It has been solved by implementing Sbalance which will be available in the next update, but it won't be as smooth as 60hz
2. A proper fix should be ROM-sided not kernel-sided. For example, @Yar_Zloy's latest EU 2.0.104.0 port does not have this issue on current stable 20250202 release

Another example would be @llxcd_EGy's MegaOS EU port, that too doesn't have that issue

Tipbit from me (my personal experience, yours may differ)

If MIUI 14 or HyperOS 1.0: feel free to nuke Joyose, and maybe you'll get a slight performance improvement

However, do not nuke Joyose on HyperOS 2.0! It'll make things much more laggy

I really didn't want this, but since it has reached the point of no return....

Starting from the next STRIX-Revived/moddedVantom update, KSU bases will be switched back to @rsukrnlsu

If you have any issues with any modules that is caused by magic mount, please use this module

I will just stop development since the repo is getting too much issue spam to post hate, so go on use ksu official like I even forced you to not use it lol I always said use whatever you want but coming in ksu next group to slander without using it is actually brainrot, I will unarchive it when I feel like it till then I will develop it locally

❗️THIS IS NOT VBANTOM!! THIS IS NOT OFFICIAL VANTOM BUILD EITHER!
This is upstream vantom (source) + @xfirstnamelastname's brickports linux upstream (4.14.355+4) + slow charging fix from vbantom (🤔) + @rsukrnlsu (NOT KSU-NEXT!!!) (manager apk) + SUSFS 1.5.5 (direct dl link for susfs module)

Kernel Source
⚠️ Disclaimer

Credits:

@xfirstnamelastname for the brickports
@aryannn999 and @Vantom for bes kernel

@RissuDesu for their KSU fork
@real5ec1cff for bringing magic mount to KSU
@xfirstnamelastname for the ksu hooks commits
@sidex15 for their SUSFS module
@simonpunk for SUSFS ❤️

AOSP only, do not flash on MIUI

Hi 👋

"If your device has an open kernel source and still use magisk or apatch instead of KernelSU-Next + SuSFS then it's a serious goddamn crime and you need to lock your bootloader for real you don't deserve root 🥴"


The emoji 🥴 should've obviously gave out the joke but it was taken as a serious and bad mouthing like bro I use magisk on my other devices and I absolutely love the concept of apatch from the very beginning and have said it in public groups multiple times as it has some much potential even more than KernelSU or Next, to the point I wanna work on apatch as well cuz I love everything about kpm, so idk why people are talking my words as a bad intent still and keeping the drama alive which shouldn't ever be a drama about this, I simply joked that why you not using ksu next + susfs if you really want root hidden and shit talking next while never used it and using magisk and apatch which has issues with root hiding at the moment and with the joke part I also said if you don't use something you don't know anything about and not use ksu next while you are in the ksu next group then you should lock your bootloader and you don't deserve root an obvious joke also I said it's a crime because you are here in the group and not using ksu next before shit talking is brainrot,

I would never diss other root solution/alternatives while I use them myself and am a fan since magisk was very new to the community.

If you are so butt hurt about a joke then it's a you problem and idk how it is an issue for me .

But anyways I apologize for a joke

🥴 Now we have to apologize for a joke is what says this generation is fucked up