v1.1 #3
Replies: 1 comment 9 replies
|
Can this kernel be used in HyperOS 3.0.301.0 WOJMIXM on POCO X7 Pro, and will it also be usable in HyperOS 4 in the future? Is it just the Stock Kernel with SUSFS and ReSukiSU, or is it different? If it is different, does it target performance or battery life or balanced? |
|
1. Why is the MiCode source at 6.6.30? Xiaomi's MiCode kernel releases are one-time snapshots published for GPL compliance, roughly matching an early/launch firmware state — and they are not kept in sync with OTA updates. The newer kernels on retail units (6.6.56 on HyperOS 2, 6.6.89 on HyperOS 3, as you said) are internal LTS merges that never got pushed back to the public repo. This is a well-known pattern across MiCode branches, not something specific to rodin. That's actually one of the reasons this project exists: I took the 6.6.30 release as the base and merged the latest AOSP 2. You're right — HyperOS 3 on rodin is Android 16 The "Android 15" in the README actually refers to the kernel source tree, not the OS version — the rodin kernel is based on AOSP's |
|
Thanks a lot, this made all my confusion clear. 😃 Do you know whether in HyperOS 4, they will update the kernel version of the Stock Kernel of rodin? Like how they updated from 6.6.56 in HyperOS 2 to 6.6.89 in HyperOS 3, to which version do you think they will update to in HyperOS 4? 🤔 I really like your kernel, because I prefer stock type kernels, and since your kernel is like stock only but with improvements and root + SUSFS (which is a must) so it's perfect, I will start using it from HyperOS 4. :) and btw one more question, why did you choose ReSukiSU root instead of something more reputable and stable like KernelSU-Next? Are you planning to shift to KernelSU-Next root in HyperOS 4? |
|
About HyperOS 4's kernel version: I can't say for sure — But based on how they handle existing devices, rodin will almost certainly stay on the 6.6 GKI generation with only LTS point-release bumps (like 6.6.56 → 6.6.89 did), not a jump to a new kernel generation. Mid-cycle generation bumps (e.g. to 6.12) almost never happen for an already-shipped device. About ReSukiSU vs KernelSU-Next: First, a correction to the premise — both are community forks of KernelSU, so neither is more "official" than the other. KernelSU-Next forks straight from tiann's KernelSU; ReSukiSU comes down the SukiSU-Ultra line, whose whole purpose is being a more stable SukiSU, with years of real-world testing in the GKI + susfs custom kernel scene. On a 6.6 GKI kernel, both are rock solid. The actual reasons I chose ReSukiSU for this kernel: Multi-manager support — the ReSukiSU kernel works with the official KernelSU, MKSU, RKSU and SukiSU managers, so users aren't locked into a single manager APK. KSU-Next only works with its own manager. |
|
I saw some people saying that Stock Kernel of POCO X7 Pro [rodin] has been updated to 6.6.118 in HyperOS 3.0.302.0 WOJMIXM (Global), so my guess is that they will keep using this in HyperOS 4, But you are already ahead of them and in 6.6.142 haha. 👀 |
What about ReSukiSU-Ultima? It's basically like an upgraded version of ReSukiSU with built-in Zygisk and better hiding for modern kernels like ours, did you take a look at that? |
Uh oh!
There was an error while loading. Please reload this page.
内核版本：6.6.142-by-Omachirimanbu-4k-g630b1fd707d0
构建时间：# 6 SMP PREEMPT Wed Aug 26 13:32:42 CST 2026
构建工具链：(Android (15682573, +pgo, +bolt, +lto, +mlgo, based on r596125) clang version 22.0.2 (https://android.googlesource.com/toolchain/llvm-project de03d430485c884861198b25459851f429cbdbad), LLD 22.0.2 (/mnt/disks/build-disk/src/googleplex-android/llvm-r596125-release/out/llvm-project/llvm de03d430485c884861198b25459851f429cbdbad))
变更：
已经过实机测试，可稳定使用
This discussion was created from the release v1.1.
All reactions