Operator

com.byarchitect.operator
by Zapstore _@zapstore.dev

Republished from GitHub / F-Droid by the Zapstore main account.

First release: Nov 30, 2025, 3 total releases.

Most recent release: Sep 25, 2026.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Sep 25, 2026 2.0
    ## Operator no longer requires root Where there is no root, Operator can now run through **[Shizuku](https://shizuku.rikka.app/)**, which executes commands as the ADB shell user. That is enough to read the full process table and to force-stop apps. Root is still preferred and is used automatically whenever it is available. **Installs as a normal update over v1.0.x.** Same signing key. ### How the two compare
    More…
    | | Root | Shizuku | |---|---|---| | Read the process table | yes | yes | | Stop an app | yes | yes, via `am force-stop` | | Stop a system process | yes | no | | Survives a reboot | yes | no — Shizuku must be started again | Operator picks root first and falls back to Shizuku. If neither is available, the start screen offers to request Shizuku access, but only when Shizuku is actually running. **About** shows which method is in use. ### Also in this release - Native system processes cannot be stopped over Shizuku, and Operator now tells you that instead of quietly doing nothing. - Fixed: stopping a process never reported success, so a working kill was indistinguishable from a failed one. Closes #2. This also supersedes #3 — see that issue for why Shizuku was chosen over an accessibility service. ### Verifying this APK ``` apksigner verify --print-certs Operator-v2.0.apk ``` Signing certificate SHA-256, unchanged since v1.0.1: ``` 8c74ae8fd94d7122d50d6d2db3f50b79be06e57b82aee1d07e6a89c45e14895e ``` ### Install Preferably from [IzzyOnDroid](https://apt.izzysoft.de/packages/com.byarchitect.operator), which updates automatically.
  • Sep 24, 2026 1.0.1
    Version metadata fix for the v1.0.0 release. The v1.0.0 APK was accidentally built from the commit *before* the release tag, so it identified itself as version `0.0.7`. This build comes from a clean clone of the `v1.0.1` tag and reports the correct version. - `versionName`: `1.0.1` - `versionCode`: `2` **No functional changes to the app.** ### ⚠️ You must uninstall v1.0.0 first
    More…
    This release is signed with a **new key**, so Android will refuse to install it as an update. Uninstall v1.0.0, then install v1.0.1. **Your app settings will be lost.** The previous release keystore had been accidentally committed to this repository and must be treated as compromised. Normally the fix would be APK Signature Scheme v3 certificate rotation, which keeps updates working — but that requires the old private key, and the old keystore's password is no longer recoverable. A clean break was the only option. Sorry for the disruption. The new key is stored properly, so this will not happen again. ### Verifying this APK ``` apksigner verify --print-certs Operator-v1.0.1.apk ``` Signing certificate SHA-256: ``` 8c74ae8fd94d7122d50d6d2db3f50b79be06e57b82aee1d07e6a89c45e14895e ``` ### Install Preferably from [IzzyOnDroid](https://apt.izzysoft.de/packages/com.byarchitect.operator), which keeps you updated automatically. See `RELEASING.md` in the repository for how releases are built and verified.
  • Nov 30, 2025 0.0.7 Release page →
    ### Features - Sort processes by Cpu usage - Sort processes by Memory usage - Kill selected process ### Requirements - Rooted Device