MaxManager ships five native binaries. Each one exists because a different kind of knowledge does not belong inside an Android app.
| Binary | Language | What it knows |
|---|---|---|
sys.maxmanager-service |
C (14 components) | The device-facing service: app loading, game preload, PID tracking, bypass charging, system profile, inotify, config, logging, startup sequencing |
sys.maxmanager-profilesettings |
Rust (binprofiles/) |
Chipset strategies |
sys.maxmanager-utilityconf |
Rust (binutils/) |
Utility configuration |
sys.maxmanager-rianixiathermalcore |
Rust (thermalcore/) |
Thermal policy — see thermal.md |
sys.maxmanager-preloadbin |
C (preloadbin/) |
Game library preloading |
binprofiles| File | What it is |
|---|---|
chipsets/ |
Five families, each with its own strategy: Snapdragon · MediaTek · Exynos · Tensor · Unisoc |
plan.rs |
The pure table of the binary’s CLI contract: parsing, the ownership gate, and what each verb does — separated from I/O so the contract can be tested without a device |
props.rs |
The single source of truth for every persist.sys.maxmanager* property key this binary reads or writes |
profiles/ |
The profile definitions themselves |
Two design points worth naming, because they are the difference between a profile system and a pile of
if statements:
plan.rs holds the table; the main loop only executes it. That makes
“what does this verb do” answerable by reading one file, and testable off-device.The module exposes the daemons as ordinary binaries on system/bin, and symlinks the shorter names
so a terminal user can reach them quickly (including zx for the service binary). One name, one path —
see the path table in rom-integration.md.
preloadbinpreloadbin/jni/main.c embeds vmtouch 1.4.1 (BSD-3-Clause, © Doug Hoyte and contributors; measured
at 99.7 % identical, three lines different) and keeps that notice in the file header. It is what puts a
game’s libraries into page cache before the game needs them.
That is a copied-and-adapted component, and it is credited as one rather than presented as original work. The full accounting is in THIRD_PARTY_NOTICES.md.
archdaemonFourteen components, each one a single concern: StartupInit, ConfigHandler, AppLoader,
AppMonitoring (the Java companion), GamePreload, PidTracker, BypassCharge, SystemProfile,
InotifyHandler, BinaryCLI, MaxManagerUtility, ShellUtility, FileUtility, SystemLogger.
It descends from Encore Tweaks (Apache-2.0, © Rem01Gaming), whose notices are preserved in the files
that carry its header. The daemon builds with -std=c23 -Werror -pedantic-errors in the AOSP kit — it
is not a script with a C extension, it is C that has to survive a strict compiler.