Android/Linux systems · Kernel & root · Device trust · AI clients & agents · Build engineering
I build practical systems software around Android and Linux, with current work spanning kernel engineering, root infrastructure, trusted execution, mobile AI clients, agent runtimes, audio stacks, networking and reproducible build systems.
- Kernel & root — OnePlus 13 / OnePlus 6 kernels, KernelPatch/KPM, ReSukiSU/SUSFS, congestion control and reproducible build pipelines.
- TEE / device trust — TEE simulation, Android RKP/StrongBox experiments and device-side trust infrastructure.
- AI clients & agents — mobile-first AI clients, rootless agent runtimes, provider integration, tool execution and persistent environments.
- System extensions — download acceleration, audio processing, lyrics/translation experiments and Android framework tooling.
- Engineering systems — CI/CD, upstream tracking, source-base maintenance, deployment infrastructure and validation-first releases.
| Project | Direction |
|---|---|
| PatchNest Module | KernelPatch/KPM-oriented Android system module and WebUI work |
| TEESimulator | TEE simulation and Android trust-stack experiments |
| Android RKP Bridge | RKP / device attestation integration experiments |
| OnePlus 13 Kernel | OnePlus 13 kernel integration, validation and release workflows |
| OnePlus 6 Kernel | OnePlus 6 kernel work with ReSukiSU/SUSFS-oriented build variants |
| TCP Optimiser | Dynamic TCP tuning, congestion-control work and Android system integration |
| System Download Accelerator | Android download-path acceleration and configurable system rules |
| Kelivo | Mobile AI client with chat, story and agent-oriented workflows |
| Nova Agent | Agent runtime and mobile execution experiments |
| Rootless JamesDSP | Rootless Android audio processing and DSP integration |
| Space | Role |
|---|---|
| Zhanfg | Maintained products, representative research and user-facing projects |
| ZhanfgBuild | Build/release infrastructure, source bases, upstream/reference forks and supporting engineering |
| axymorrsen.cc | Project and writing hub |
This repository boundary is now the maintained layout. A small number of engineering-adjacent repositories intentionally remain under the personal namespace where that better fits their operational or project role.
- Evidence before claims: distinguish verified behavior from planned or device-pending work.
- Prefer small, reviewable changes with clear rollback paths.
- Track upstream aggressively, but validate compatibility before integration.
- Treat documentation, CI and reproducible builds as part of the implementation.
- Keep credentials, tokens, private device data and unreleased material out of public repositories.
中文交流 / English documentation welcome.