Auto Target manages the package list used by TrickyStore. It can add user-installed apps at boot, monitor package changes, preserve custom and blocked entries, and expose the resulting target.txt through an on-device WebUI.
Automated TrickyStore Target Management
A background monitor and cached app index keep the target list synchronized without making the WebUI wait on package scans.
Smart Monitor
Detects package installations and removals on a configurable 10–3600 second interval, then rebuilds the target list.
WebUI Controls
Provides app toggles, a direct target editor, counts, monitor controls, theme settings, logs, and persistent custom or blocked packages.
Backup and Diagnostics
Creates timestamped target-list backups, manages keybox input, and can save a diagnostic snapshot during every boot.
How It Builds the List
At boot, service.sh waits 30 seconds, builds a display-name cache with the bundled aapt, starts the package monitor, and optionally records boot diagnostics. When packages change, update_target.sh rebuilds /data/adb/tricky_store/target.txt.
The generated file always includes the core Google packages documented by the project, omits packages in the persistent block list, and merges entries from the custom package list. Manual WebUI edits and backups provide a recovery path before larger changes.
Requirements and Optional Tools
- Android 10 or newer.
- TrickyStore already installed.
- Magisk 25.2+, KernelSU, or APatch.
- A root manager capable of opening module WebUIs.
Security-patch spoofing, trace clearing, TEE repair, property reset, and keybox replacement are separate optional tools in the interface. They are not required for basic target-list maintenance and should be used only when their effect is understood.
target.txt before using bulk actions, and do not load keybox material from an untrusted URL.