There is no native Android app for OpsCommandCenter, and building one wasn't feasible from the machine this project was developed on — no Android SDK, no Java, and no emulator or physical device to test against. Instead, the Android "agent" is a plain shell script that runs inside Termux, a free terminal app — no APK, no Android Studio, no SDK required on either side.
Status: written and syntax-checked (
bash -n), but not run on a real Android device — same honesty bar as every other deployment guide in this project. Treat your first run as the first real test.
The full setup guide (installing Termux/Termux:API, getting the script onto the phone, running it, keeping it alive in the background, and exactly what data it does/doesn't report) lives next to the script itself:
src/OpsCommandCenter.Agent.Android/README.md
Quick version, once Termux + curl are installed and the script is on the phone:
chmod +x opscc-agent.sh
./opscc-agent.sh --server=http://<server-ip>:5252 --interval=30- No disk health, disk temperature, or antivirus status — none of these are reachable from an unprivileged Termux shell, so they're left "n/a" rather than guessed.
- CPU model is best-effort (Android doesn't expose a clean model string to unprivileged apps;
falls back to the CPU ABI, e.g.
arm64-v8a). - Staying alive in the background depends on Android not killing the Termux process — the
README covers
termux-wake-lockand Termux:Boot for auto-start, but aggressive OEM battery optimization (common on some phone brands) may still need a manual battery-optimization exemption for Termux, which isn't something a script can configure for you.