Neutrino Kernel (Pixel 9 Series) pinned «6.1.155-NeutrinoKernel https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.155-NeutrinoKernel I've re-uploaded the latest release with some hotfixes to improve the performance and stability of SuSFS v1.5.11 as well as to address a…»
6.1.156-NeutrinoKernel
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.156-NeutrinoKernel
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.156-NeutrinoKernel
GitHub
Release 6.1.156-NeutrinoKernel · 0ctobot/neutrino_kernel_google_caimito
October 15th
Sync with android14-6.1-lts common kernel
Update to Linux 6.1.156
Sync with latest SuSFS-v1.5.12 codebase
Decouple BPF_EVENTS from FTRACE
Fix gpuservice crash on init
Full Changel...
Sync with android14-6.1-lts common kernel
Update to Linux 6.1.156
Sync with latest SuSFS-v1.5.12 codebase
Decouple BPF_EVENTS from FTRACE
Fix gpuservice crash on init
Full Changel...
Neutrino Kernel (Pixel 9 Series) pinned «6.1.156-NeutrinoKernel https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.156-NeutrinoKernel»
6.1.157-NeutrinoKernel
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.157-NeutrinoKernel
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.157-NeutrinoKernel
GitHub
Release 6.1.157-NeutrinoKernel · 0ctobot/neutrino_kernel_google_caimito
October 19th
Sync with android14-6.1 common kernel
Update to Linux 6.1.157
Sync with latest SuSFS-v1.5.12 codebase
Fix KSU thread info flag corruption
ATTENTION:
As you will no doubt notice, ther...
Sync with android14-6.1 common kernel
Update to Linux 6.1.157
Sync with latest SuSFS-v1.5.12 codebase
Fix KSU thread info flag corruption
ATTENTION:
As you will no doubt notice, ther...
ATTENTION:
As you will no doubt notice, there are two zips attached to this release - it's very important that you comprehend the following in order to ensure that you flash the correct one. I've taken a bit of an experimental turn here and have compiled the standard kernel, as it always has been, with KernelSU and SuSFS, and well as a variant without KernelSU for those who might be interested in using this kernel with Magisk.
- If you are a regular user and wish to continue using this kernel with KernelSU, please flash the first zip labeled with KSU
- If you are a Magisk user who would like to try the kernel, please flash the second build that does NOT have the KSU label
Please do not interpret this as a guarantee or commitment that I will always release variant builds for both root solutions, I may or may not choose to continue doing this going forward. Thanks!
As you will no doubt notice, there are two zips attached to this release - it's very important that you comprehend the following in order to ensure that you flash the correct one. I've taken a bit of an experimental turn here and have compiled the standard kernel, as it always has been, with KernelSU and SuSFS, and well as a variant without KernelSU for those who might be interested in using this kernel with Magisk.
- If you are a regular user and wish to continue using this kernel with KernelSU, please flash the first zip labeled with KSU
- If you are a Magisk user who would like to try the kernel, please flash the second build that does NOT have the KSU label
Please do not interpret this as a guarantee or commitment that I will always release variant builds for both root solutions, I may or may not choose to continue doing this going forward. Thanks!
Neutrino Kernel (Pixel 9 Series) pinned «6.1.157-NeutrinoKernel https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.157-NeutrinoKernel»
It is imperative that you read and understand the following:
As many of you know KernelSU has been rapidly evolving over the last month or so, and getting caught up has been quite the process. Neutrino is now current with KSU v2.1.2 (22164), which means I recommend using the equivalent official KSU Manager CI or newer:
https://github.com/tiann/KernelSU/actions/runs/19726628479
The latest CI of 5ec1cff's KSU Manager fork (formerly MKSU) is also supported:
https://github.com/5ec1cff/KernelSU/actions
These are the only two supported KSU Manager variants, there's really no good reason not to use the official CI's right now, but the choice is yours.
If you haven't been keeping up, I highly suggest that you educate yourself on the ways in which KernelSU has changed. The main point to be aware of is that KernelSU no longer handles module mounts natively, but rather uses a metamodule to handle mount operations:
https://github.com/tiann/KernelSU/blob/d00b4cc03717259815abf8b497ac73ca772e9bb8/website/docs/guide/metamodule.md
This change is only relevant to those of you using modules that mount /system. Otherwise, the way you interact with KSU Manager on a surface-level will not change.
SuSFS has been updated to v2.0.0, and has also seen significant functional changes in line with KernelSU updates. As you know I was already implementing a stripped down version of SuSFS in the past, and it is now more minimal than ever.
This was not my decision, although I'm thrilled to have SuSFS as small as possible, a good chunk of its previous functionality has been deprecated upstream and is no longer relevant to KSU in its current form.
What this means in practice is that there is no longer any automated functionality, TRY_UMOUNT operations are now handled exclusively by KSU, the only core feature that persists is SUS_MOUNT and even then it is only relevant when using a metamodule to perform /system mounts.
TL;DR - SuSFS no longer does anything unless you assign sus_mounts via userspace daemon.
I think for the time being I'll go back to shipping KSU-only releases unless there is a particular demand for Magisk-compatible variants, which it didn't seem like there was when I was running them.
As many of you know KernelSU has been rapidly evolving over the last month or so, and getting caught up has been quite the process. Neutrino is now current with KSU v2.1.2 (22164), which means I recommend using the equivalent official KSU Manager CI or newer:
https://github.com/tiann/KernelSU/actions/runs/19726628479
The latest CI of 5ec1cff's KSU Manager fork (formerly MKSU) is also supported:
https://github.com/5ec1cff/KernelSU/actions
These are the only two supported KSU Manager variants, there's really no good reason not to use the official CI's right now, but the choice is yours.
If you haven't been keeping up, I highly suggest that you educate yourself on the ways in which KernelSU has changed. The main point to be aware of is that KernelSU no longer handles module mounts natively, but rather uses a metamodule to handle mount operations:
https://github.com/tiann/KernelSU/blob/d00b4cc03717259815abf8b497ac73ca772e9bb8/website/docs/guide/metamodule.md
This change is only relevant to those of you using modules that mount /system. Otherwise, the way you interact with KSU Manager on a surface-level will not change.
SuSFS has been updated to v2.0.0, and has also seen significant functional changes in line with KernelSU updates. As you know I was already implementing a stripped down version of SuSFS in the past, and it is now more minimal than ever.
This was not my decision, although I'm thrilled to have SuSFS as small as possible, a good chunk of its previous functionality has been deprecated upstream and is no longer relevant to KSU in its current form.
What this means in practice is that there is no longer any automated functionality, TRY_UMOUNT operations are now handled exclusively by KSU, the only core feature that persists is SUS_MOUNT and even then it is only relevant when using a metamodule to perform /system mounts.
TL;DR - SuSFS no longer does anything unless you assign sus_mounts via userspace daemon.
I think for the time being I'll go back to shipping KSU-only releases unless there is a particular demand for Magisk-compatible variants, which it didn't seem like there was when I was running them.
GitHub
manager: redo fetchAppList onCreate · tiann/KernelSU@4355ff4
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
Neutrino Kernel (Pixel 9 Series) pinned «It is imperative that you read and understand the following: As many of you know KernelSU has been rapidly evolving over the last month or so, and getting caught up has been quite the process. Neutrino is now current with KSU v2.1.2 (22164), which means I…»
6.1.158-NeutrinoKernel-KSU (reupload)
- Upstream KSU to v3.0.0 (32179-neutrino)
- Spoof LKM flag to suppress manager warning
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.158-NeutrinoKernel-KSU
- Upstream KSU to v3.0.0 (32179-neutrino)
- Spoof LKM flag to suppress manager warning
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.158-NeutrinoKernel-KSU
GitHub
Release 6.1.158-NeutrinoKernel-KSU · 0ctobot/neutrino_kernel_google_caimito
November 29th
Sync with android14-6.1-lts common kernel
Upstream KSU to v3.0.0 (32179-neutrino)
Spoof LKM flag to suppress manager warning
Forward-port various key functionalities:
Restore LSM...
Sync with android14-6.1-lts common kernel
Upstream KSU to v3.0.0 (32179-neutrino)
Spoof LKM flag to suppress manager warning
Forward-port various key functionalities:
Restore LSM...
Neutrino Kernel (Pixel 9 Series) pinned «6.1.158-NeutrinoKernel-KSU (reupload) - Upstream KSU to v3.0.0 (32179-neutrino) - Spoof LKM flag to suppress manager warning https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.158-NeutrinoKernel-KSU»
Just to get ahead of the inevitable confusion, because we're kind of in this weird in-between stage where QPR2 has gone stable and QPR3 is yet to be released I've updated the latest build to be in line with BP4A.251205.006, meaning - if you're on December stable, you can use it and if your still on QPR2 beta awaiting QPR3, you can also use it.
Please don't get used to this, once QPR3 goes live I will be back to supporting beta exclusively.
Please don't get used to this, once QPR3 goes live I will be back to supporting beta exclusively.
Neutrino Kernel (Pixel 9 Series) pinned «Just to get ahead of the inevitable confusion, because we're kind of in this weird in-between stage where QPR2 has gone stable and QPR3 is yet to be released I've updated the latest build to be in line with BP4A.251205.006, meaning - if you're on December…»
6.1.159-NeutrinoKernel (Reupload)
HOTFIX:
- Add preliminary support for KSU-Next v3.0.0 (32857)
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.159-NeutrinoKernel
Please update to NeutrinoKernel-caimito-A16-20251214.zip if this is relevant to you.
HOTFIX:
- Add preliminary support for KSU-Next v3.0.0 (32857)
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.159-NeutrinoKernel
Please update to NeutrinoKernel-caimito-A16-20251214.zip if this is relevant to you.
6.1.159-NeutrinoKernel-QPR3 (Reupload)
- Sync with CP11.251114.006
- Restore BBRv3 TCP algorithm
- Support various KSU alt-managers
- Support KSU Toolkit
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.159-NeutrinoKernel-QPR3
(Here is your obligatory reminder to not flash this kernel on December Stable, as you'll likely end up with broken WiFi.)
- Sync with CP11.251114.006
- Restore BBRv3 TCP algorithm
- Support various KSU alt-managers
- Support KSU Toolkit
https://github.com/0ctobot/neutrino_kernel_google_caimito/releases/tag/6.1.159-NeutrinoKernel-QPR3
(Here is your obligatory reminder to not flash this kernel on December Stable, as you'll likely end up with broken WiFi.)