Will be commiting in a few mins

Can be enabled in Developer settings with Webui debugging toggle

New strings added

Is it just me or this feels like an AI coded PR to me and which got merged is diabolical

https://github.com/tiann/KernelSU/pull/2675

Was gonna cherry-pick but now after reviewing the code it oddly gives me AI vibes

keep the request reasonable and sensible or else i wont accept and close the request

KernelSU-Next v1.0.9 is Released!

https://github.com/KernelSU-Next/KernelSU-Next/releases/tag/v1.0.9

KernelSU-Next compatible Zygisk-Next

https://github.com/Dr-TSNG/ZygiskNext/issues/233#issuecomment-3069761446

Lucky kernel a13-5.15 with susfs pre patched branch (only a13-5.15 cuz it's for my own device)

https://github.com/KernelSU-Next/KernelSU-Next/tree/next-susfs-a13-5.15-dev

Might be useful for people who wants to test their own managers

i have set the minimal kernel driver version for new manager to be at least version 12797

to eliminate the confusion of zygisk detection for older kernels in newer managers which i shouldve done in the 1.0.9 release

well anyways ive update the manager apk in v1.0.9 release in github

older kernel driver version before 12797 cant use newer manager entirely

https://github.com/KernelSU-Next/KernelSU-Next/commit/892a62afdf0b3524221f4aefc39c0f840fb240d5

Either update the kernel driver or stick to older manager version

kernel: guard syscall hook types
- for kernel syscall hooks we need to pass additional guards for ksun (#ifdef CONFIG_KSU -> #if defined(CONFIG_KSU) && !defined(CONFIG_KSU_KPROBES_HOOK)) or else it will fail to build because of undefined symbol

- reference https://github.com/KernelSU-Next/kernel_patches/blob/main/syscall_hook/min_scope_syscall_hooks_v1.4.patch

https://github.com/KernelSU-Next/KernelSU-Next/commit/45ad73e9dd86a0ff04a02e73a8fc2dbc3160ee6c

ksud: auto create our own new ramdisk when no compatible ramdisk found for LKM installation

Now supported ramdisk partitions in sequence [ vendor_boot/ramdisk , vendor_boot/init_boot , init_boot/ramdisk and lastly boot/ramdisk ]

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

those who ever installed LKM through these two commit ci managers Main/Spoofed i would suggest installing stock partition of the LKM and install the last ci manager and patch with that untill the hot fixed comes which i just committed and force pushed

KernelSU-Next GKI kernels will now have Minimal Syscall 1.4 Hooks

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