KernelSU has been around for nearly two years and has stabilized, and we plan to move to 1.0 in the future; here are some adjustments:

1. In principle, we only accept Bug Reports and do not accept external Feature Requests; if you want new features, you are welcome to submit a Pull Request. We will still develop new features that we think are interesting/cool, such as sulog, ksufs, webui, etc.
2. Since non-GKI kernels are full of weird things, it is very time-consuming to deal with this kind of problem; from now on, we will only deal with issues related to GKI kernels. For problems with old kernels, please search for issues by yourself; we will give up supporting non-GKI kernels in version 1.0. Since non-GKI kernels are no longer updated, you can continue to use KernelSU version 0.9.x; in fact, starting from 0.7.0, we have not added any new features to non-GKI kernels.

Our energy is limited, but the rewards are even more limited, so please understand our choice, thank you!

If you wish to contribute code to KernelSU, here are some good first issues:

- https://github.com/tiann/KernelSU/issues/1664
- https://github.com/tiann/KernelSU/issues/1571
- https://github.com/tiann/KernelSU/issues/1542

GitHub

[Feature] Add logs export to local storage · Issue #1664 · tiann/KernelSU

Is your feature request related to a problem? Please describe. I'm always frustrated when I need to get KernelSU logs because when I click the Logs button in Settings it opens the Share menu, t...

The installation guide has been updated, with added instructions for LKM mode: https://kernelsu.org/guide/installation.html#introduction

https://github.com/tiann/KernelSU/releases/tag/v0.9.2

- [manager]: Support offline patching of the kernel.
- [kernel]: Fix issue with ColorOS.
- [kernel]: Hide traces of LKM in user space.
- [manager]: Fix possible errors during OTA upgrades.

KernelSU now supports installation through kernel modules (LKM) (GKI Only), you can use it with official kernels or third-party kernels; at the same time, the manager has also added installation functionality, you can choose to patch files, install directly, or install after OTA. Regarding the new LKM installation method, there are some tips:

1. LKM does not support non-GKI kernels, and will not support them in the future;
2. When patching files, if the init_boot partition exists, you should choose to patch init_boot; otherwise, patch boot;
3. If you have already installed the GKI kernel provided by KernelSU and want to switch to the LKM method, you need to flash back to the stock kernel; if your device has an init_boot partition, you can directly flash back to the stock boot;
4. The installation method of GKI kernel and LKM will always exist, use whichever you like; in the future, it will also support flashing GKI kernel in the manager.

https://github.com/tiann/KernelSU/releases/tag/v0.9.0

https://github.com/tiann/KernelSU/releases/tag/v0.8.1

And the webui docs

KernelSU version 0.8.0 use sparse image to storage module files. If you do not wait patiently for the module installation process to end after upgrading (it takes time to migrate the old version to the new version), but forcefully stop the process and then switch to the old version of the manager, then serious problems will occur at this time.

Because the old version of the manager cannot handle sparse image, it treats sparse files as ordinary files, and one copy is enough to use up all the storage space on your phone.

If you switch to an old manager version, be sure to delete /data/adb/ksu/modues.img and /data/adb/ksu/modules_update.img!

For a long time, the module functionality of Magisk / KernelSU was limited to executing boot scripts and modifying system files. Now, we are exploring the possibility of endowing modules with the capability to display UI interfaces!

Previously, after installing some modules, users needed to configure them either through the command line or by directly modifying configuration files in specific locations. Clearly, this process was quite inconvenient for users. At times, in order to configure settings, it was even necessary to write a separate app. With the ability for modules to display interfaces, these issues could become a thing of the past.

Moreover, the display interface can be used for more than just configurations. You have the freedom to present anything you'd like to showcase and interact with the user.

The current interface is implemented through WebUI. You can create HTML pages using any web technology and place them in the module's webroot directory. After the module is installed, users can access this page through the KernelSU manager's list of modules. KernelSU also provides a JavaScript library to facilitate interaction with the system.

However, these trials are still in their infancy, and the jsapi is not yet stable. We welcome your feedback!

Although I am not sure what has transpired, as someone who has also been the target of malicious slander, I understand and support the decision of the LSPosed developers.