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 😡

vbantom Kernel 20241016
Changelogs:
Changed uname to vbantom now to make it very clear this is not official vantom!
Synced with upstream:
*Upstream kernel to 4.14.353
*Fixed a rare issue where plugging in some wired headphones would cause the phone to soft reboot
Actually enable BORE scheduler this time 😅
Added some kernel optimizations from Zelo and some more from WestCoast
Added c2tcp TCP congestion algorithm
Replaced power supply drivers from vantom to sleepy, this hopefully fixes disconnect and reconnect during charging issues
Other stuff I forgor
———————————————————
[KSU] Fixed broken uname spoofing with susfs (ksu_susfs set_uname)

Kernel Source (and 15-experi-ksu branch for ksu changes)
⚠️ Disclaimer
Credits:

@itsshashanksp for tweaks and power supply drivers from sleepy and A15 bpf changes
@RooGhz720, @fiqri_ardyansyah, @zelodev and @xfirstnamelastname for tweaks from aghsina, strix, zelo and westcoast respectively
@aryannn999 and @Vantom for bes kernel

KernelSU guide for non-gki and this GitHub issue
@simonpunk for SUSFS

Yes, I'm gonna make a hotfix build for ksu variant of strix revived one sec

STRIX Kernel Revived
HOTFIX for KSU variant
Fixed broken uname spoofing with susfs (ksu_susfs set_uname)

I'm gonna end both polls next week-ish
Your feedback will be greatly appreciated

I should make it clear, currently, there is no difference whatsoever between 0.9.5 and 1.0.1 for non-gki

I should reiterate:
STRIX Revived supports both MIUI and OSS
vbantom supports OSS only!!
Please do not try booting vbantom on MIUI, otherwise you'll suffer undesirable effects

Chat closed, I will explain what happened.

Google banned a lot of fingerprints in the last hours, specifically ones from beta roms for Pixel devices.

I will try to find a valid fingerprint and update PIF but I can't promise I will find it.

Expect all leaked keyboxes to be banned in the next hours.

The winter is coming...

Ah would you look at that
Looks like it's much nearer to do this now 🫠