📥 ChicKernel permalinks

GitHub Releases | SourceForge mirror | XDA Forums thread

📝 Note:

This kernel is tuned for these SDM685 (sm6225-AD) devices:

• Xiaomi Redmi Note 12 4G (topaz / tapas)
• Xiaomi Redmi Note 13 4G (sapphire / sapphiren)

🏗️ Notes (for developers):

Cloning this source (for beginners):

• There are custom repo manifest files in this branch root directory, Download one, and move it into some directory.
• After that, (expecting the manifest is in the current directory) execute these commands

repo init -u https://android.googlesource.com/kernel/manifest -m $(pwd)/<chickernel variant>.xml
repo sync --fetch-submodules

Building this source:

• You can either use bazel or build.sh to build a GKI kernel. I personally hate bazel.

BUILD_CONFIG=common/<build config>
FAST_BUILD=1 # Not required, forces thinLTO

build/config.sh nconfig # Edit build configuration
build/build.sh # Build the kernel

• After building, the artifacts are at out/dist

This kernel is built with these configurations:

• build.config.gki.aarch64.chickernel
• build.config.gki.aarch64.chickernel.ksu
• build.config.gki.aarch64.chickernel.ksu.susfs (On the SuSFS branch)

Upstreaming kernelSU:

• This is dependent on how you cloned this repository!
• Example: change directory to your source, and run:

# If managed by repo
repo sync --fetch-submodules

# If managed by git
git submodule update --init --remote

Upstreaming SuSFS:

• Upstreaming SuSFS implementation in kernel is kinda tricky, because it involves applying patches, and re-doing everything
• Clone the gki-android13-5.15 branch into your working directory outside the kernel, and after you do the 1st step mentioned below, do everything as according the guide in it's README

I do it someway like this:

1. First, i revert previous implementation commit
2. I merge the directories from kernel_patches/ to my tree
3. I apply the patch: git apply *.patch --whitespace=fix
4. I commit, and push to origin

⛔ Report Issues

Please report issues here, or to my telegram