Let's not be toxic anymore for the sake of the open source community 👍

If the authors of the cherry-picked code has any issues on KernelSU-Next please contact me as a civilized professional manner and not yapping and monkeying over things that's not even your code.

"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

manager: added developer options toggle
manager: removed module card onClick open webui
manager: diabled umount modules by default

https://github.com/rifsxd/KernelSU-Next/commit/00cab2209eb547e4d8022b7e3baf69a237c2a740

manager: fix umountModule toggle not showing as enabled after manager restart

https://github.com/rifsxd/KernelSU-Next/commit/682f93667b2266fbf17cf17478b4950ac6acb57d

Revert "manager: fix umountModule toggle not showing as enabled after manager restart"

https://github.com/rifsxd/KernelSU-Next/commit/8696ed8f36b2fa99fffdf02b2b7fb2b19300b67f

kernel: do not umount modules by default

https://github.com/rifsxd/KernelSU-Next/commit/bbb05b292aaebf674105ee7239ac612cedbfb88a

Minor error on the commit to not umount modules by default which was in manager which is a dead code and really doesnt do the job so lets just directly do it from the kernel driver itself

manager: added allowlist backup and restore (#9)
manager: create separate module & restore screen


https://github.com/rifsxd/KernelSU-Next/commit/d85bff2943f512726b5f09d6a0c0aa5774978d84

feature requested from - https://github.com/rifsxd/KernelSU-Next/issues/9

manager: disable restore module button on overlayfs mount mode (since the restore module code for overlayfs mount never got out of internal testing, wull be implemented in the future)

https://github.com/rifsxd/KernelSU-Next/commit/74f55dd807f09e984426d0fdc51df554301329c1

ksud_overlayfs: reduce sparse image size to 6GB

https://github.com/rifsxd/KernelSU-Next/commit/b2a8fb66d380b9dc03175b408fc3e66139f66cc8

About this ive reduced down the sparse image size from 16GB to now 6GB since in future updates KernelSU-Next will allow you to set custom sparse image sizes so small size wont matter for your huge module lists that exceeds 6GB lol

KernelSU Official completely trying to kill NON-GKI support and more over manual hooks for kernel also improving on kprobes Su which might be interesting who knows if its better than manual hooks or not. But rip NON-GKI tho i wont pick this change to keep NON-GKI alive for Next.