banner test

Finally, a porter whom bothered to credit me for kernel 🥹

STRIX-Revived Staging 20241210
* Attempt to fix the issue of soft reboots once and for all (specifically reported with bq charger driver users)
Please let me know over in DMs if everything works fine..
I.e no more soft reboots, no disconnect and reconnect during charging, etc..

If all goes well, new STRIX-Revived update with KSU and SUSFS update, as well as a special performance-focused MIUI-only variant that is focused for 💣 ports such A15 HyperOS 2.0, OxygenOS/ColorOS, etc..

Same for vbantom, even though again no changelog for the third time in a row, meaning again NoSU will be skipped as it is not affected

I will not repeat the same confusion as last time as release both vbantom and STRIX-Revived updates at the same time
One will be released first, the other will be delayed by 24+ hours

vbantom Kernel 20241212

"Ah hell nah they done patched the 1TB storage glitch"

Changelog:
None, same as 20241129. Thus, NO-SU build has been skipped for the second time in a row (I'll work and make more changes on it when I'm back in a AOSP ROM)
20241129 NoSU build
———————————————————————
rsuntk's KSU fork 12022 (required manager apk!, Github Mirror) + SUSFS 1.5.2 (direct dl link to module)
Introducing Magic Mount! the very same bind mount module system that is used on Magisk has been brought to KSU, and it's all thanks to @real5ec1cff ❤️
Benefits of Magic Mount explained by xx
!!WARNING!! with this update you'll lose all your installed modules, so please back them up somewhere safe!, and then when restoring them, restore them to /data/adb/modules_update after you flashed kernel and installed manager update and then reboot

The difference between [KSU] and [KSU-NEXT] is that the NEXT build has lineage map hiding which should help hide custom ROM detections, however, not all ROMs like it and can cause bootloops on certian ROMs, in that case, please switch to the [KSU] build
To benefit from [KSU-NEXT], go to the SUSFS module webui > custom susfs settings > toggle on "Hide custom ROM paths"

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
@real5ec1cff for bringing magic mount to KSU
@xfirstnamelastname for the lineage maphide and ksu hooks commits
@sidex15 for their SUSFS module
@simonpunk for SUSFS ❤️

MIUI peeps you just wait for new STRIX-Revived (and a new performance focused fork 👀), okay?

STRIX Kernel Revived 20241214

"I'll have 2 numba batter with a large smoothie"

Changelog:
(from 20241210-STAGING) Fix soft reboots occurring on bq charger driver
Fixed disconnect and reconnect while charging issue again (I don't like this wack-a-mole game 💢)
Some slight changes to increase smoothness and responsiveness
—————————————————————
rsuntk's KSU fork 12022 (required manager apk!, Github Mirror) + SUSFS 1.5.2 (direct dl link to module)
Introducing Magic Mount! the very same bind mount module system that is used on Magisk has been brought to KSU, and it's all thanks to @real5ec1cff ❤️
Benefits of Magic Mount explained by xx
!!WARNING!! with this update you'll lose all your installed modules, so please back them up somewhere safe!, and then when restoring them, restore them to /data/adb/modules_update after you flashed kernel and installed manager update and then reboot

The difference between [KSU] and [KSU-NEXT] is that the NEXT build has lineage map hiding which should help hide custom ROM detections, however, not all ROMs like it and can cause bootloops on those ROMs, in that case, please switch to the [KSU] build
To benefit from [KSU-NEXT], go to the SUSFS module webui > custom susfs settings > toggle on "Hide custom ROM paths"
[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, @aryannn999, @unmoved21, @xfirstnamelastname, @sidex15 and @RooGhz720 for the fixes, tweaks and features from their kernels
@fiqri_ardyansyah for the kernel everyone loves ❤️

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

Soon.. 👀

                                    
              _/      _/            
   _/    _/  _/      _/  _/    _/   
  _/    _/  _/      _/  _/    _/    
 _/    _/    _/  _/    _/    _/     
  _/_/_/      _/        _/_/_/      
     _/                    _/       
_/_/                  _/_/          

Introducing yVy: a very performance-focused kernel, intended for UI-heavy ports like HyperOS 2.0, OxygenOS/ColorOS in mind
yVy (acronym for youVsyou) is a fork of the STRIX-Revived with several performance focused and responsiveness optimizations picked from aghisna, zelo and westcoast. Testing shows it handles all of HyperOS 2.0 animations very smoothly*

*Atleast with 60 and 90hz, 120hz animation slow down issue seems to be a ximi fuckup or something, there's nothing further to be done kernel-wise unfortunately

Obviously, such a performance-focus changes come at the cost of battery-life unfortunately, like slightly more battery drain than STRIX, but that all depends on the port really
Another thing worth noting is that OSS support in this fork has been dropped, but I have instead reverted the IR Blaster fix for OSS that breaks it for MIUI (see https://t.me/tbyool/800) so that at least IR Blaster should work now

For disappointed OSS peeps, fret not, I'll pick changes from yVy to vbantom when I switch to an AOSP ROM

Moreover, porters are encouraged to feel free to try yVy with their HOS, OOS, COS, etc ports, you won't be disappointed 🔥