1.4.1 SUSFS

Again, this is just base module, you'll still need to configure service.sh and post-fs-data.sh inside to actually do anything
You can look inside said files for examples

I will boot it 2: Android 15 edition

STRIX Kernel Revived

"Your duty is NOT over" -Sage

Changelog:
Upstreamed kernel to 4.14.352-openela!
Merged CLO tag LA.UM.9.1.r1-16300-SMxxx0.QSSI14.0
Added A14 QPR2, A14 QPR3 and A15 support!
Compiled with ZyC Clang v20
Zip supports both OSS and MIUI
—————————————————————
KSU 0.9.5 (non-gki EOL) and SUSFS 1.4.1 (module)
Kernel Source
⚠️ Disclaimer
Credits:

@itsshashanksp for the BPF and A15 changes
@aryannn999 for scripts from vantom that are very useful
@fiqri_ardyansyah for the kernel everyone loves ❤

KernelSU guide for non-gki
@simonpunk for SUSFS

Now, do NOT expect me to introduce any new stuff into strix kernel, strix will be maintained only so that it works with any new android updates in the future

If you want new experimental features and stuff, that's gonna be exclusive to me vbantom kernel, which I'm hoping to release a new update for soonish™

About time I give a review to this ROM 😍

Gad damm, the first ever A15 ROM to grace sweet, what an understatement
Despite being an alpha build, it was very much solid rock stable, for me, it's definitely yet another of these ROMs that I enjoyed so much I keep using them for a month and maybe more

Battery life's good (at least with my vbantom kernel, results may vary with you). The new animations are good, snappy, and responsive. And there are little nice customisations
Definitely, a ROM that has placed a very good first impression of A15 for me

Pros:
- Fast, smooth, and responsive
- A very solid stable experience for an alpha build
- Very good Android 15 experience for being the first ever A15 ROM to release
- Very little to no custom ROM detections

Cons:
- There's this Dolby Atmos bug, where if you get a notification when watching YT, listening to Music, etc.. The audio effects suddenly stop and are just gone, doesn't matter how many times you enable and disable Dolby Atmos, the audio effect is gone, the only way to workaround it is to reboot the device
This has become very annoying lately, that every time I get a singular notification that interrupts playback the audio effects just *poof* and you're left with a degraded audio experience until you reboot
- For whatever reason, you cannot pass strong intergrity on it, only device intergrity with PIF module

If it weren't for the Dolby Atmos bug, it would have been a solid 10 from me, but I'm obligated to give it a light 9

Next ROM in queue:
https://t.me/RedmiNote10ProChannel/2243

Okay, I just flashed this ROM, only to be met now with a brand new trend that has been now starting to grind my gears
And that is, why are ROMs nowadays cockblocking GMS attestation in framework.jar WHEN THEY DONT EVEN PASS INTERGRITY OOTB??

Like come fucking on, not only you don't pass play intergrity checks for the user OOTB, but you also block the user from passing strong?? WTF!
What a very shitty trend that I hope to not see spreading around, this is much far worse than hardcoding leaked keyboxes into ROM source

"bu-but there's a prop to disable it!!"

Yeah, but on ROMs like cAOSP, THERE IS NO SUCH PROP!
Thus, the dogshit droidguard cockblocker is always enabled and cannot be disabled with a prop

Now, what I meant of "ROMs should stop bothering themselves with play intergrity and let the user pass it on their own", I meant for ROMs to to completely drop anything related to play intergrity and droidguard attestation.
This also includes dropping DG clockblock. This fuckery of not passing intergrity checks but blocking DG attestation is literally the worse, it's like telling the user "fuck you, how dare you attempt to pass play intergrity?"

"oh why are you picking on cAOSP when in YAAP you also couldn't pass strong integrity on it either?!?!"

YAAP I wasn't able to pass strong integrity on because it NEEDED PIF options set that conflict with TrickyStore to even pass device integrity!
https://t.me/vbaloboto/681

Whereas cAOSP doesn't need them, yet deliberately blocks Droidguard attestation that is needed for strong integrity 😡