The next-generation Android package manager — all the power, half the friction.
AppManagerNG is a continuation of the App Manager project — a full-featured, root/ADB-aware package manager for Android — with a focus on user experience, polish, and approachability without sacrificing any of the depth that makes the original a power user staple.
Think of it as AppManager with a friendlier front door: the same engine, the same root/ADB capabilities, the same component blocking and tracker scanning — but layered behind a Material 3 interface that doesn't punish casual users for opening it.
Note
This is an early-stage project. v0.1.0 is the rebranded baseline — the code below is the
upstream AppManager source pinned at commit 3d11bcb (2026-04-16). Subsequent releases will
introduce the AppManagerNG UX overhaul incrementally, in working increments, with full
attribution to upstream contributions preserved.
A new main-menu entry that flips the standard "app -> permissions" view on its head. Pick a permission group (Camera, Microphone, Location, Contacts, SMS, Phone, Files & media, Calendar, Body sensors, Physical activity, Nearby devices, Notifications) and see every installed app that holds it, with a one-tap toggle per app and a master Revoke for all apps action in the toolbar. Changes persist through the same rule store the per-app permissions tab uses, so they survive reinstalls.
Reclaim storage without losing anything: archiving removes an app's APK and cache but keeps its data and launcher icon, so unarchiving picks up exactly where you left off. AppManagerNG drives the native Android 15 archiving API — archive or unarchive a single app from its App Info page, or select multiple apps and do it as a batch operation. Archived apps are detected and shown as such in the app list. Works on user apps without root (the system asks you to confirm each request). No other open-source package manager ships this yet.
- Material 3 with dynamic colours
- Rich app information page (activities, services, providers, receivers, app ops, permissions, signatures, shared libraries)
- Activity launcher and activity-shortcut creator
- Activity interceptor
- Tracker and library scanner with class dumps
- Manifest viewer/exporter
- App usage, data usage (mobile + Wi-Fi), storage info
- Install/uninstall APK / APKS / APKM / XAPK (with OBB support)
- APK sharing
- Backup/restore APK files
- Batch and single-click operations
- Logcat viewer, manager, exporter
- Profiles
- Debloater
- Code editor
- File manager
- Simple terminal emulator
- Aurora Store / F-Droid client launch integration
- APK signing with custom signatures
- Backup encryption: OpenPGP (OpenKeychain), RSA, ECC (hybrid + AES), AES
- Foreground UI component tracking
- Revoke runtime + development permissions
- App-op mode editing
- Display/kill/force-stop running apps and processes
- Clear app data/cache
- Net policy view/edit
- Battery optimization control
- Freeze/unfreeze apps
- Block any component (activities/receivers/services/providers); native + Watt + Blocker import/export
- View/edit/delete shared preferences
- Backup/restore apps with data, rules, and extras (permissions, battery opt, SSAID, etc.)
- View/edit system configurations (blacklisted/whitelisted apps, permissions)
- View/change SSAID
See ROADMAP.md for planned work. Completed and stale items are in
COMPLETED.md; consolidated research is in
RESEARCH_REPORT.md. Historical roadmap and research ledgers
are archived under docs/roadmap/archive/ and
docs/archive/. Version targets:
- v0.2.0 ✅ — applicationId rename to
io.github.sysadmindoc.AppManagerNG, fresh keystore, GitHub Actions release pipeline, NG CONTRIBUTING.md - v0.3.0 ✅ — Material 3 dashboard refresh, Pro Mode toggle, edge-to-edge (Android 15/16 compliance), AMOLED/dark/light themes
- v0.4.0 ✅ — Permission Inspector (review/bulk-revoke dangerous permissions across all apps; critical-package guard; recovery action) + Onboarding capability wizard
- v0.5.0 ✅ 2026-05-25 — Discovery & Polish: in-app changelog viewer + auto-display after update, global in-app Settings search, plus the Iter-91 → Iter-142 batch (scheduled auto-backup polish, AES metadata v7 HKDF per-archive keys, ADB tcpip reuse, KernelSU/Magisk drop-cap diagnostics, Dhizuku detection, Restricted Settings unlock walkthrough, installer privilege cascade, OEM debloat-blocker bypass, per-app rollback, snapshot-bundle portability v2, Component rules preview, Tasker am:// intents, QS freeze tile, FM recursive search and ZIP create/extract, AGP 9.2.0). See
CHANGELOG.md. - v0.5.x — post-release consolidation plus the pass-2 feature backlog: background-run rule persistence, multi-volume cache trimming, activity-launch polish, structured log exports, scanner/file/editor reliability work.
- v0.6.0 — Rootless Power: Routine Operations / Scheduler executor and UI, plus Premium Polish Phase 2. Multi-tag and saved-filter data layers already landed.
Every AppManagerNG release ships two build flavors. Both are the same app; the only difference is whether the optional online features are compiled in.
| Flavor | For | Optional online features (VirusTotal, Pithus, debloat-definition auto-updates, Settings → Privacy → "Use the Internet") |
|---|---|---|
floss |
F-Droid, IzzyOnDroid, reproducibility audits, anyone who wants a fully offline build | Removed at compile time — there is no setting to turn them on. Local networking (ADB-over-TCP, wireless pairing, the localhost privileged-server) still works. |
full |
GitHub Releases / Obtainium power users who want online scan reports and the debloat-definition auto-updater | Available, opt-in — every online feature stays gated behind its existing user toggle and the master "Use the Internet" preference. Nothing reaches the network without you turning it on. |
floss is the default flavor in source; full is the optional variant. If you don't need VirusTotal / Pithus / debloat-definition auto-updates, floss is the right choice. See docs/distribution/build-flavors.md for the maintainer contract.
Grab the signed APK from GitHub Releases — pick full or floss per the table above. Use arm64-v8a for modern devices or universal for maximum compatibility (older 32-bit ARM and x86_64 emulators).
Obtainium is the recommended path for users who want automatic update checks straight from GitHub Releases without going through any store.
-
Install Obtainium.
-
Add App → paste the URL:
https://github.com/SysAdminDoc/AppManagerNG -
(Optional but recommended) Use the bundled config file for fully pre-tuned settings (correct ABI auto-detection, version regex, prerelease-skipping):
- Open
Obtainium → Settings → Import/Export → Import Apps From File. - Select
docs/distribution/obtainium-config.json(the file is wrapped in the standard Obtainium{"apps":[…]}backup format so the import flow accepts it directly).
- Open
Obtainium will then auto-track every signed release published to this repo and notify you on update.
Tip
Pair Obtainium with AppVerifier so every Obtainium-fetched APK is checked against the published certificate fingerprint below before install.
ROM builders who pre-seed F-Droid repositories should ship both the F-Droid 2.0 JSON file and the legacy XML file during the migration window. Templates and placement notes live in docs/distribution/rom-fdroid-preseed.md.
Important
Brazil / Indonesia / Singapore / Thailand users: Google's Android Developer Verification program begins enforcement on certified devices in your region on 2026-09-30. After that date, AppManagerNG (like every other on-device installer) is subject to the platform verifier gate. AppManagerNG preserves verifier failure reasons in install results and can offer an ADB-mode retry when ADB is already reachable, because ADB installs remain exempt.
APK signing certificate SHA-256 fingerprint:
21:5F:B4:70:63:2E:A6:CD:59:A4:BA:AB:35:0A:9E:0B:99:AD:11:0F:DD:FA:F5:A9:EA:64:61:E5:D0:C2:38:6C
Verify with AppVerifier or:
apksigner verify --print-certs AppManagerNG-<version>.apk | grep SHA-256Release publishing also runs a two-build reproducibility gate: CI builds the
signed APK twice from a clean checkout, compares the binary SHA-256 hashes, and
uploads a .sha256 sidecar only when the bytes match. Maintainers can run the
same check locally with scripts/verify_reproducible_release.ps1
on Windows or scripts/verify_reproducible_release.sh
on Linux CI; details are in docs/distribution/reproducible-builds.md.
The same fingerprint is published in machine-parseable form at a stable URL so AppVerifier and similar tools can fetch it without scraping the README:
https://raw.githubusercontent.com/SysAdminDoc/AppManagerNG/main/docs/fingerprints.txt
The file is comment-tolerant (# prefix) and uses the same package: /
sha256: record pairs as SD Maid SE's published fingerprints.
See BUILDING.rst. Submodules must be initialized before building:
git submodule update --init --recursiveSee CONTRIBUTING.md. Translation contributions go through Weblate (link TBD).
Released under GPL-3.0-or-later. Per-file SPDX headers and the LICENSES/ directory follow
the REUSE specification — please preserve them.
See COPYING for the full GPL-3.0 text. Vendored third-party components retain their
original licenses (Apache-2.0, BSD-2-Clause, BSD-3-Clause, CC-BY-SA-4.0, GPL-2.0, ISC, MIT, WTFPL)
as documented in LICENSES/.
AppManagerNG would not exist without the years of work that went into the upstream
App Manager project by Muntashir Al-Islam and
the broader contributor community. AppManagerNG was bootstrapped from upstream commit
3d11bcb
on 2026-04-30.
The original project remains the canonical implementation; AppManagerNG is a parallel effort focused on UX polish and approachability. If you want the upstream experience — or want to contribute features broadly applicable to the package-manager domain — please direct your effort upstream first.
A full list of credits and bundled libraries is available in the About section of the app.