MiCode / MiCode/Xiaomi_Kernel_OpenSource
Title: Redmi 15 5G (spring) stock kernel build blocked by incomplete Kleaf workspace
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9.9k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Device:
- Redmi 15 5G
- codename: spring
- stock HyperOS 2
- Android 15
- bootloader unlocked
- Magisk 29
Current kernel:
- 6.1.118-android14-11-ga3b9c44908dd-ab13320413
Goal:
Build a stock-compatible kernel with external Atheros USB Wi-Fi support for Kali NetHunter, specifically ATH9K_HTC / AR9271.
What I did:
- extracted Xiaomi_Kernel_OpenSource-spring-v-oss.zip
- extracted spring kernel devicetree zip
- confirmed spring uses Qualcomm GKI fragment-based config flow
- patched config fragments to enable:
- CONFIG_WLAN_VENDOR_ATH=y
- CONFIG_ATH9K_HTC=m
- switched from Termux to Kali rootfs so Bazel can run properly
Current blocker:
The released source package does not appear to be a complete standalone Kleaf workspace.
Build fails because required files are missing, especially:
- build/kernel/kleaf/workspace.bzl
So the problem appears to be missing workspace/build infrastructure rather than config syntax or environment.
Request:
- Is there a full manifest/repo checkout for spring?
- Is there an additional package needed for Kleaf workspace files?
- Has anyone successfully built spring stock kernel from Xiaomi’s released source?
I can provide logs, partition backups, and test results.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the released source around build/kernel/kleaf/workspace.bzl and reproduce the reported Bazel failure. Compare the package with the required Kleaf workspace or manifest, using the missing-file error and any supplied logs. Done means identifying the needed checkout or package and confirming that the spring stock-compatible build can proceed with the requested config fragments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100