To all the fucking scammers, yes you! Go die in hell for scamming people for 30 to even 100 usd for ksunext installation and setup, you are getting paid for something i maintain for free, i hope you all die in hellfire for scamming innocent people for so much money and blackmail them to brick them, who ever is this mr.root go kill yourself please.

If anyone needs help for anything related to ksunext, just fucking dm me or ping me in the group t.me/ksunext_group i always see your message and help whenever i can don't fall for these scams

Imagine paying scammers instead of donating to open source projects 😭

Apatch next I pay 50usdt

I have seen a total of 10 - 15 people paying for ksunext rooting which would sum upto a thousand usd

I'm gonna go insane in Telegram

A bit of FYI,

If you want to use sound modules i.e Dolby and Viper4Android then you need to disable umount for those sound module apps for the processing to work correctly.

To address the issue on the proprietary code of ksuinit being closed source, it also exists on ksunext, since we are really against closed source software, it makes sense to drop LKM mode to keep ksunext fully open source, but it makes sense for them to keep it closed source for obvious reason to not be exploited by others and possibly code theft or a reason something entire unknown but it's making a fuss over the community, tbh i could just drop ksuinit LKM mode entirely from ksunext in next release untill we can reverse engineer it or an entirely alternative new code to replace the proprietary code ksuinit.

Till then ksunext may not support LKM.

Well tbh this vote wont affect my decision on the issue, if you want lkm mode then you can either fork ksunext rn and cherry pick my newer commits (improvements and bug fixes) while keeping lkm and build your own manager or just stick to v1.0.6 apk manager

FYI,

Onec you have installed LKM mode from v1.0.6 you can then update the manager but cant update the LKM driver

To address possible confusion regarding incompatibility after dropping LKM, you can still flash GKI kernels from my releases on github and also from wildplus kernels which also has susfs and more kernel patch version for various devices so i don't think dropping LKM will hurt anyone, it's the same procedure to have root by flashing the GKI boot.img, plus you can get possibly the best root hiding tool known an susfs.

Dropping LKM will elevate KSUN even more cuz now i can ship susfs GKI images directly instead of third party GKI kernel projects.

This is mainly a GKI device matter, NON GKI can still use ksunext through custom built kernels

next-susfs-dev branch is upstreamed to KernelSU-Next commit (a7a9f86) & SuSFS v1.5.7

https://github.com/KernelSU-Next/KernelSU-Next/commit/a0125579acb55e983fb9fb6fa1ff85f38e42750e

Exiting stuff coming soon...

https://github.com/KernelSU-Next/KernelSU-Next/pull/316

Introducing WebUI-X (Thanks to @Der_Googler)

MMRL WebUI with Advanced Features: Includes Edge-to-Edge support and dynamic app themes for a seamless user experience.


Side note -

Better ksurootservice

Superuser applist loading is now very fast

Here is the CI manager if anyone wants to test it out