Skip to content

About

Automated kernel builder for OnePlus 13 with KernelSU and SUSFS support

Resources

Stars

2 stars

Watchers

1 watching

Forks

Latest commit

 

History

368 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OnePlus13-KernelBuilder

Custom GKI kernel for the OnePlus 13 (sun / SM8750) — KernelSU-Next + SUSFS + NetHunter, with working internal-radio monitor-mode injection.

Build KernelSU-Next SUSFS Injection

A GitHub Actions CI/CD pipeline that builds a custom, feature-packed kernel for the OnePlus 13 (Qualcomm SM8750, codename sun). Each variant produces:

  • A flashable AnyKernel3 ZIP (AK3_*.zip)
  • A raw ARM64 Image
  • A wireless/CAN modules pack (kernel_modules_*.zip) plus a firmware passthrough ZIP

This repository intentionally produces no boot.img, vendor_boot.img, vendor_dlkm.img, or system_dlkm.img.


Caution

Your warranty is no longer valid!

I am not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about features included in this kernel before flashing it! YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you.


Tip

Installation

  1. Flash the AK3 ZIP with KernelFlasher or TWRP.
  2. Reboot. That is the whole kernel install — the AnyKernel3 package carries Image and patches the boot image in place.
  3. (Optional, NetHunter) Unzip kernel_modules_*.zip to internal storage and load a driver with nethunter-wifi.sh. See Wireless modules.

Verify the flash with /proc/version, not uname -r — SUSFS rewrites the uname release string, so uname -r reports a plausible stock value that matches no partition on the device. It is not a sign the flash failed.


Note

Features

  • 🔐 Root — KernelSU-Next (default) or KernelSU, resolved to a concrete commit SHA before building.
  • 🥷 SUSFS — root hiding (path/mount/kstat spoofing), optional, default on.
  • 🛡️ BBG (Baseband Guard) — LSM-based protection for critical device partitions.
  • 🐉 NetHunter — inline configs (Bluetooth, SDR/AirSpy/HackRF, CAN, USB-serial) plus external Wi-Fi drivers (ath9k_htc/AR9271, ath10k_usb, carl9170, rtl8187, rtl8xxxu, rtw88, rt2x00, zd1211rw, p54, mt76) as loadable modules.
  • 📡 Monitor-mode injection — the internal Qualcomm radio can transmit arbitrary 802.11 management frames. See below.
  • ⚡ feat/perf-stack — MGLRU rework, af_unix GC rewrite, BPF opts, f2fs fixes, THP reclaim fix, cpufreq/sched NEED_UPDATE_LIMITS, zsmalloc + zram, UKSM, HMBIRD.
  • 🧩 Extras — ADIOS I/O scheduler, zram lz4/zstd backports, Re-Kernel freeze-notification LKM.
  • 🧠 BORE scheduler — opt-in burst-time scoring on top of EEVDF, so interactive work wins under load. A scheduler change, so it stays off by default. See BORE scheduler.
  • 🎲 LRNG v60 — opt-in replacement for the kernel RNG: independent IRQ/CPU/Jitter entropy sources feeding a ChaCha20 DRBG instead of one BLAKE2s pool. An entropy-subsystem change, so it stays off by default. See LRNG v60.
  • 🔋 Battery — an always-on patch series plus opt-in battery_save / audit_off knobs. See Battery.
  • 🌐 Networking — BBR / BBRv3, TTL target, IP_SET & IPv6 NAT, FQ/CAKE/PIE, NTSync, TMPFS xattr/ACL.
  • 🖥️ Droidspaces — SYSVIPC / PID_NS / POSIX_MQUEUE for portable Linux containers.
  • 🚀 Oryon tuning — -mcpu=oryon-1, ThinLTO with a persistent cache.

Important

Monitor-mode injection

The DDK build patches the vendor Wi-Fi driver (qcacld-3.0 → qca_cld3_<chipset>.ko) so the internal radio can inject management frames — deauth, probe requests, and the rest — while in monitor mode. Toggle with ddk_injection.

Verified on-device (6.6.142 A16, OnePlus 13):

  • Injected deauths measurably disconnect a station — 24–26 of 40 samples on an independent receiver, where the same test before the TX-power fix produced 0.
  • Stock wifite runs end-to-end: 390 deauths on air, 62 EAPOL captured, and 2 complete crackable WPA 4-way handshakes (aircrack-ng: WPA (1 handshake)).

How it works

Firmware drops management TX on a plain monitor vdev, so the patch creates a hidden ghost STA vdev via direct WMI (VDEV_CREATE/VDEV_START/PEER_CREATE) and routes injected frames out on that vdev, bypassing wlan_mgmt_txrx entirely via wmi_mgmt_unified_cmd_send(). Each buffer is tracked in a 32-slot table keyed by a 16-bit token — the only lane firmware echoes back, since desc_id is uint16_t.

The traps (each cost real debugging time)

Trap Symptom Fix
Ghost vdev started with maxregpower = 0 Firmware reports status 0, frames appear on the phone's own monitor iface, nothing is radiated Set maxregpower/maxpower
Deauth sent with our own SA Stations ignore it Spoof addr2 = the AP's BSSID
PEER_CREATE under load Firmware hangs ~135 ms later Skip peer create while inflight is high
Drop-and-continue at the TX cap A fast injector still hangs firmware netif_tx_stop_all_queues() + wake on drain
Monitor netdev gets no cfg80211 channel airodump blocks on CH 0, captures ~2% Synthesise cfg80211_ch_switch_notify()

[!WARNING] Monitor-mode sessions can wedge the firmware and leave Wi-Fi dead. Reboot to recover — an in-place mode switch has a documented panic class.


Tip

Quick Start

Builds run only through GitHub Actions (workflow_dispatch); there is no local build script.

# Default (6.6.89 A16, KSUN + SUSFS + NetHunter + wireless modules)
gh workflow run "Build OnePlus 13 Kernel" -R Hipuu/OnePlus13-KernelBuilder

# A single variant
gh workflow run "Build OnePlus 13 Kernel" -R Hipuu/OnePlus13-KernelBuilder \
  -f kernel_version="6.6.118 A16"

# All seven in parallel
gh workflow run "Build OnePlus 13 Kernel" -R Hipuu/OnePlus13-KernelBuilder \
  -f kernel_version=all

Or use Actions → Build OnePlus 13 Kernel → Run workflow.

Dispatch inputs

Input Default Notes
kernel_version 6.6.89 A16 One of the seven variants, or all.
ksu_variant KSUN KSUN or KSU.
ksu_branch (empty) Empty uses main for KSU, dev for KSUN, falling back to a pinned compatible commit.
use_susfs / susfs_branch true / (empty) SUSFS feature set; empty branch auto-selects the GKI branch.
nethunter / wireless_modules true Inline configs / external driver modules.
ddk / ddk_injection true Bazel-Kleaf build + qcacld injection (6.6.118/6.6.142 A16 only).
optimize_level / lto O2 / thin Compiler optimization; thin enables the persistent ThinLTO cache.
compiler zycromerz-19 Or manifest for the pinned Clang.
battery_save / audit_off false Opt-in power knobs.
bore false Opt-in BORE scheduler patch — 6.6.118/6.6.142 only (not "A16": 6.6.89 A16 also fails), see BORE scheduler.
lrng false Opt-in LRNG v60 RNG replacement — all seven variants, see LRNG v60.
kernel_uname OP-WILD Release-string suffix.
clean_build / debug false Force a full rebuild / emit debug artifacts.
release_type none none, prerelease, or release.
runner github-hosted Or self-hosted.

Supported variants

All seven share the SoC (SM8750), Android generation (android15), and manifest branch (wild/sm8750); they differ in kernel version and OxygenOS generation.

Config Kernel OS Manifest
configs/OP13-6.6.89.json 6.6.89 A16 manifests/a16/oneplus_13_6.6.89_w.xml
configs/OP13-6.6.118.json 6.6.118 A16 manifests/a16/oneplus_13_6.6.118_w.xml
configs/OP13-6.6.142.json 6.6.142 A16 manifests/a16/oneplus_13_6.6.142_w.xml
configs/OP13-6.6.66.json 6.6.66 A15 manifests/a15/oneplus_13_6.6.66_v.xml
configs/OP13-6.6.30.json 6.6.30 A15 manifests/a15/oneplus_13_6.6.30_v.xml
configs/OP13-CPH-6.6.89.json 6.6.89 A15 global manifests/a15/oneplus_13_global_6.6.89_v.xml
configs/OP13-CPH-6.6.56.json 6.6.56 A15 global manifests/a15/oneplus_13_global_6.6.56_v.xml

Wireless modules

# from the extracted module pack, as root
./nethunter-wifi.sh                     # interactive menu
./nethunter-wifi.sh load                # ath9k_htc by default
./nethunter-wifi.sh status
./nethunter-wifi.sh restore             # bring internal Wi-Fi back
./nethunter-wifi.sh conmode monitor 1   # internal Wi-Fi -> monitor mode
./nethunter-wifi.sh conmode sta         # back to normal

The loader displaces the platform Wi-Fi stack only when a loaded driver actually needs mac80211; a reboot (or restore) brings the internal Wi-Fi back.


Battery & power tweaks

An always-on, idempotent, --forward-safe patch series (.github/actions/build-kernel/files/battery/):

  • Wakelock entropy — a global 500 ms timeout on new wakelocks, so stray locks cannot pin the CPU awake.
  • s2idle / freeze — wake once from s2idle; freeze timeout reduced to 1 s.
  • ext4/f2fs — larger default commit age / min_fsync_blocks so writes batch.
  • alarmtimer / hrtimer / PCI PME — minimised wake timeout, no pointless reprogramming, fewer PME wakeups.
  • Log spam — devkmsg and IRQ-affinity spam silenced.
  • Vendor tasktracker — gate the oplus_bsp_schedinfo periodic hrtimer on tasktrack_enable.

Opt-in knobs (both default false)

Knob What it does Trade-off
battery_save CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y; appends rcupdate.rcu_normal_after_boot=1 to CONFIG_CMDLINE; blacklists qcom_cpuss_sleep_stats{,_v4} Small latency overhead on workqueue-heavy paths; the sleep-stats drivers cost ~0 battery — blocking them only removes a debugfs node
audit_off Appends audit=0 to CONFIG_CMDLINE On this permissive-SELinux device audit churn is constant; the gain is log hygiene, not battery

A service.d script (files/battery/99-battery-tweaks.sh) adds vm.page-cluster=0 and oplus_log_level=1 at boot.


Important

BORE scheduler

BORE (Burst-Oriented Response Enhancer, v7.0.0, by Masahito Suzuki) scores each task by its burst time — the runtime since it last slept or yielded — and boosts the shorter, burstier ones. That is the profile of a compositor, a launcher, a game loop or a scroll gesture, so interactive work keeps its latency while a background compile or download runs. It costs some scheduling fairness, which is why it is a knob and not a default.

Enable it with bore=true. The step applies .github/actions/build-kernel/files/bore/bore-7.0.0.patch with --fuzz=0 and appends CONFIG_SCHED_BORE=y to the common gki_defconfig. It runs before every other patch that touches kernel/sched/, so its hunks always see the freshly synced tree.

Provenance. A backport of firelzrd's canonical patches/stable/0001-linux6.12.37-bore-7.0.0.patch to this tree's 6.6 EEVDF. firelzrd ships 7.0.0 only for 6.12/6.18/7.1/7.2/7.3; 34 of its hunks reject against 6.6 because they depend on the 6.12 EEVDF (do_preempt_short, do_preempt_weight, protect_slice, cancel_protect_slice, requeue_delayed_entity, rel_deadline, custom_slice, sched_delayed). Each rejected site was re-derived here against the 6.6 forms — protect_slice() is inlined as vlag == deadline, and place_entity()'s deferred vslice replaces the rel_deadline dance — and the ctl_table handler signatures were changed from const struct ctl_table * (6.12) to struct ctl_table * (6.6). Everything else is firelzrd's text.

Why 7.0.0 and not the older 5.9.7. The previously vendored 5.9.7 patch (palazik/brokestar233) bootlooped on device. The embedded-config delta between a booting kernel and that one was exactly CONFIG_SCHED_BORE=y plus CONFIG_MIN_BASE_SLICE_NS=2000000 — nothing else — so the fault was in 5.9.7 itself against this tree's newer fair.c. 7.0.0 is the maintained line and restructures the burst accounting onto static keys and a per-task bore_ctx.

The one deliberate deviation from firelzrd's text: ABI-neutral storage. Upstream 7.0.0 embeds struct bore_ctx bore; inline in task_struct, which grows the struct. genksyms CRCs propagate transitively through the type graph, so that shifts the CRC of every exported symbol whose signature reaches task_struct (e.g. hci_dev → sk_buff → sock → mem_cgroup → task_struct), and ~430 symbols disagree between the GKI and vendor Module.symvers. The vendor tree has its own include/linux/sched.h and is not patched, so with ddk=true modpost then dies with <sym> exported twice. Previous export was in <same .ko> in //vendor/qcom/opensource/wlan/platform (proved 2026-10-13: bore=true ddk=true fails, bore=false ddk=true passes, all 36 OP_* variables otherwise identical). So the ctx is a pointer in sched_entity's free KABI reserve slot 1: android_kabi.h expands _ANDROID_KABI_REPLACE to bare _orig under __GENKSYMS__, so the slot stays an 8-byte u64 for CRC purposes and the layout never moves — confirmed by running the real scripts/genksyms/genksyms, which yields an identical CRC for a task_struct-taking symbol (and for a sched_entity-taking one) with BORE on and off. This is how palazik's 5.9.7 did it, and why 5.9.7 never hit the failure. The ctx is kzalloc'd in dup_task_struct and freed in free_task; the step asserts the slot is claimed and that no inline field reappeared, because losing it silently reintroduces the ABI break.

Why sched_entity and not a task_struct slot. Both are ABI-neutral, but task_struct's free KABI slots are all inside the context of the Droidspaces SYSVIPC patch, which the pipeline applies later and which first probes with patch -R --dry-run to see whether it is already applied. Claiming a task_struct slot makes that probe fail, so the step falls through to a forward apply that hard-fails under set -e (this is what killed run 38541385542, ~3.5 minutes in — long before any compile). Around 30 patches in WildKernels/kernel_patches touch task_struct's KABI region; none touches sched_entity's, so slot 1 is collision-free. sched_entity precedes struct bore_ctx in the header, so the patch adds a struct bore_ctx; forward declaration above it.

Scope. 6.6.118 and 6.6.142 only — not "A16". The label is misleading: 6.6.89 is also an A16 variant, but its fair.c still carries the older EEVDF shape (sysctl_sched_base_slice = 750000ULL, 0.75 msec), which BORE's rewrite hunks replace, and no fuzz factor bridges that gap. So both the five A15 trees and 6.6.89 A16 fail the strict dry-run, and asking for bore=true there fails the build with the offending hunks printed, rather than half-patching the tree. Note that 6.6.89 A16 is the default dispatch variant, so this is the first thing a bore=true user hits if they do not name a version.

At runtime the tunables are sysctls under /proc/sys/kernel/ (sched_bore, sched_burst_inherit_type, sched_burst_protect_slice_lv, sched_credit_cap_us and the other sched_burst_* knobs, mode 0644). echo 0 > /proc/sys/kernel/sched_bore puts the fair class back to plain EEVDF without reflashing.

Status. Verified to apply with --fuzz=0 and to compile against both 6.6.118 and 6.6.142 (locally, kernel/sched/*.o plus fork.o/exit.o/futex/waitwake.o, with BORE both on and off), and validate_workflow.sh re-checks its hunk counts. It has not been booted — a green compile proves it links, not that the scheduler is sound at runtime.


Important

LRNG v60

LRNG (Linux Random Number Generator, v60, by Stephan Mueller) replaces drivers/char/random.c with a different architecture: independent entropy sources — interrupt timing, per-CPU timing, and optionally Jitter and the scheduler — each credited separately, feeding a ChaCha20 DRBG. The stock kernel funnels everything into a single BLAKE2s pool. The practical difference is faster, better-credited boot entropy: the LRNG reports a fully seeded DRNG early instead of waiting for the pool to reach its threshold, which matters on a phone that has to have a usable /dev/random before user space is far along.

Enable it with lrng=true. The step applies .github/actions/build-kernel/files/lrng/lrng_v60_android15-6.6.patch with --fuzz=0 and appends # CONFIG_RANDOM_DEFAULT_IMPL is not set plus CONFIG_LRNG=y to the common gki_defconfig.

Provenance. Ported from palazik/kernel_patches blob 7567dc0c, which consolidates upstream smuellerDD/lrng kernel_patches/v6.18 with backports/v60-6.6.119 for the android15-6.6 GKI. The vendored copy is sha256 17a872f6f160004c26ab025409656f8b6df394f4e1dedbda3766b182f8c47c3a. It modifies five files (crypto/drbg.c, drivers/char/Kconfig, drivers/char/Makefile, include/crypto/drbg.h, kernel/sched/core.c) and creates 56 under drivers/char/lrng/, 71 hunks in all.

Variants. All seven — A15 and A16. Unlike BORE, the LRNG patch does not rewrite version-specific scheduler code: its only kernel/sched/core.c hunks are an include line and a two-line call in ttwu_stat, both of which sit on anchors every pinned tree shares. Applicability is checked by strict dry-run against all seven trees, by fetching the five modified files at each pin.

Config shape. The patch gates random.o behind a new CONFIG_RANDOM_DEFAULT_IMPL (default y) and adds CONFIG_LRNG (default n). Turning the former off makes LRNG_RANDOM_IF — which defaults on exactly when it is off — provide /dev/random, /dev/urandom and getrandom(2) from the LRNG, and pulls in the ChaCha20 DRBG and the sysctl interface. If the Kconfig source line or the Makefile gate were ever lost, olddefconfig would drop both symbols as unknown and the tree would build with no RNG at all (the link dies on get_random_bytes), so the step greps the plumbing that proves the patch landed where it had to, and both build paths assert CONFIG_LRNG=y in the resolved .config.

What stays off. LRNG_SCHED (the scheduler entropy source) is left at its n default: it adds a call on every context switch, and the IRQ and CPU sources are on by default and sufficient. The optional /dev/lrng device and the kernel-crypto-API/hwrng registrations are likewise off.

At runtime /proc/sys/kernel/random/ is the LRNG's own table (entropy_avail, poolsize, write_wakeup_threshold, boot_id, uuid, urandom_min_reseed_secs), and /proc/lrng_type prints the DRNG name, security strength and per-source state. dmesg | grep -i lrng shows LRNG minimally seeded with N bits of entropy and LRNG fully seeded with N bits of entropy.

Status. Verified at the patch level only: it applies cleanly with --fuzz=0 on all seven pinned trees, composes with BORE in either order, and validate_workflow.sh re-checks its hunk counts. It has not been compiled or booted yet — the first lrng=true run is the compile check.


Artifacts

Artifact Contents
AK3_<MODEL>_<OS>_<KERNEL>_<KSU>_<VER>[_SuSFS_<ver>].zip Flashable AnyKernel3 package
Image Raw ARM64 kernel image
kernel_modules_<MODEL>_<OS>_<KERNEL>.zip External Wi-Fi/CAN modules, flattened modules.dep, nethunter-wifi.sh
Nethunter-Wireless-Firmware-<VER>.zip Re-published unmodified from nullptr-t-oss/Nethunter-Wireless-Firmware
qca_cld3_peach_v2.ko (DDK) The vendor Wi-Fi module, standalone
(with debug=true) Build/install logs, vmlinux, Module.symvers, modules tree

Modules are built with CONFIG_MODVERSIONS=y, so a modules ZIP loads only on the exact kernel build it shipped with.


Build caches

Caches live in GitHub Releases via the custom cache/restore and cache/save actions, not actions/cache.

Cache Bucket Gating
ccache ccache-cache make-based, non-clean builds
Bazel disk cache bazel-disk-cache DDK builds
ThinLTO cache lto-cache make-based + lto=thin, non-clean

Version keys include the KernelSU variant, model, OS version, full kernel version, and Clang fingerprint, so caches never cross-link across toolchains or variants.


Self-hosted runners

Optional. The DDK build completes on GitHub-hosted ubuntu-latest (16 GB RAM + the 16 GB swap this action configures). Register a runner with labels self-hosted, linux, X64.

  • RAM — no ≥32 GB floor. The Bazel JVM heap is clamped to 24 GB (host RAM − 6 GB, floored at 8 GB).
  • Disk — 150 GiB floor for Bazel DDK variants, 50 GiB otherwise. GitHub-hosted VMs are only warned, since builds have historically fit.
  • Concurrency — matrix jobs serialise via a top-level concurrency: group, since they share the host.

Repository layout

.github/
  workflows/build-oneplus13-kernel.yml   # Top-level workflow (workflow_dispatch)
  compatible-commits.json                # Pinned, verified SUSFS/KSUN commits
  actions/
    build-kernel/action.yml              # The actual build (patches, make/Kleaf, packaging)
    build-kernel/files/                  # battery/*.patch, ddk/*, nethunter-wifi.sh
    kernel-source-sync/action.yml        # Downloads pinned sources/toolchains
    cache/restore|save/action.yml        # Release-backed ccache / Bazel / ThinLTO caches
configs/                                 # JSON device configs (one per variant)
manifests/                               # XML repo manifests (one per variant)

The published repository is deliberately just the pipeline: .github/**, configs/, manifests/, and .gitattributes. Local tooling (validate_workflow.sh, debug_workflow.sh), TESTING.md, and AGENTS.md are kept in the working checkout but untracked — see .gitignore. (.gitattributes stays tracked because it pins *.sh to eol=lf; the on-device loader does not execute from a CRLF checkout.)


Development

SKIP_NETWORK=1 bash validate_workflow.sh     # local static validation
./debug_workflow.sh [status|logs|failed|watch|rerun|artifacts|download] [run_id]

The validator checks YAML/JSON/XML parseability, DDK and battery patch hunk counts, workflow/action structure, config↔manifest alignment, full-SHA pins, absence of boot-image construction, and POSIX/LF conformance of the on-device loader.

To read compiler warnings, use the live job log — the post-completion summary omits them, and a real failure can hide there:

gh api repos/<owner>/<repo>/actions/jobs/<job_id>/logs --allow-escape-sequences

Note

validate_workflow.sh and debug_workflow.sh are untracked, so a fresh clone has neither the scripts nor any ignore rules. Take care with git add -A after a build.


Important

Credits

Project Author
KernelSU tiann
KernelSU-Next rifsxd
Magic-KSU 5ec1cff
SUSFS simonpunk
SUSFS Module sidex15
Baseband Guard vc-teahouse
Droidspaces ravindu644
Kernel Flasher fatalcoder524
HMBIRD / Fengchi Numbersf
Re-Kernel Sakion-Team
Nethunter Wireless Firmware nullptr-t-oss
Sultan Kernels kerneltoast

Special thanks to the open-source community for their contributions!


Warning

Disclaimer

Flashing this kernel will void your warranty, and there is always a risk of bricking your device. Back up your data and understand the risks before proceeding.

Proceed at your own risk!

About

Automated kernel builder for OnePlus 13 with KernelSU and SUSFS support

Resources

Stars

2 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors