-
-
Notifications
You must be signed in to change notification settings - Fork 3k
manager: if manager incompatible with current kernel, don't save ksud #2895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
This will cause lots of bug too. |
hmmm, maybe i need add a ksud update when user update kernel to solve this problem? i will write a new commit |
|
@tiann can you review again? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR refactors when the KernelSU daemon (ksud) installation occurs, moving it from app startup to after successful direct boot installations, with additional guards for outdated kernels.
- Moved
install()call fromMainActivity.onCreate()toinstallBoot()when direct installation succeeds - Added kernel version check to prevent
install()from running when kernel is outdated - Fixed code style issue (removed unnecessary semicolon)
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| manager/app/src/main/java/me/weishu/kernelsu/ui/util/KsuCli.kt | Moved install() call to occur after successful direct boot installation instead of at app startup; removed semicolon from getRootShell() call |
| manager/app/src/main/java/me/weishu/kernelsu/ui/MainActivity.kt | Added kernel version check to prevent install() from running when requireNewKernel() returns true |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…tiann#2895) I think we should'nt install kernelsu's userspace when manager incompatible with current kernel this maybe cause a lot of bug, for example, when user install 2.x kernelsu manager, but not update his kernel to 2.x, ksud will return "kernel version 0", because ksud incompatible with old supercall impl
…tiann#2895) I think we should'nt install kernelsu's userspace when manager incompatible with current kernel this maybe cause a lot of bug, for example, when user install 2.x kernelsu manager, but not update his kernel to 2.x, ksud will return "kernel version 0", because ksud incompatible with old supercall impl
…tiann#2895) I think we should'nt install kernelsu's userspace when manager incompatible with current kernel this maybe cause a lot of bug, for example, when user install 2.x kernelsu manager, but not update his kernel to 2.x, ksud will return "kernel version 0", because ksud incompatible with old supercall impl
…tiann#2895) I think we should'nt install kernelsu's userspace when manager incompatible with current kernel this maybe cause a lot of bug, for example, when user install 2.x kernelsu manager, but not update his kernel to 2.x, ksud will return "kernel version 0", because ksud incompatible with old supercall impl
I think we should'nt install kernelsu's userspace when manager incompatible with current kernel
this maybe cause a lot of bug, for example, when user install 2.x kernelsu manager, but not update
his kernel to 2.x, ksud will return "kernel version 0", because ksud incompatible with old supercall impl