This application was developed locally to research background execution limits on heavily modified Android ROMs (MIUI). It was migrated to this public GitHub repository on March 29, 2026, for academic review.
GhostProtocol is an experimental Android utility designed to test the boundaries of OS-level background execution and asynchronous event handling.
Modern Android OEMs (specifically Xiaomi/Redmi MIUI) utilize highly aggressive task-killers to terminate background services, making continuous background event listening nearly impossible. This project successfully bypasses these OEM restrictions using a combination of NotificationListenerService APIs and a deliberate WindowManager persistence exploit.
![]() Home |
![]() Away Messages |
![]() Settings |
- WindowManager Exploit: To prevent the OS from killing the background service, the app utilizes the
SYSTEM_ALERT_WINDOWpermission to continuously draw a transparent 1x1 pixel overlay (TYPE_APPLICATION_OVERLAY) on the screen. - Process Elevation: Because the OS compositor believes the application is actively rendering UI to the user, the Android scheduler elevates the process priority, bypassing OEM battery optimization algorithms and strict sandboxing environments.
- Extends
NotificationListenerServiceto intercept incoming OS-level notification payloads asynchronously. - Capable of reading incoming messaging events and programmatically executing automated actions (like auto-replying) without requiring the user to open the application or interact with the GUI.
- Replies are dispatched by extracting the notification's
RemoteInputaction and firing itsPendingIntent— including a fallback that recovers the reply action from the wearable (WearableExtender) channel when the inline one is absent.
- A per-sender finite state machine governs what is sent and how often, keyed on the notification title:
- First message in a window → a random reply from the pool, or a keyword-matched reply if one fits.
- Repeat within the window → a single spam warning, then silence (rate-limited by a cooldown).
- Unknown senders → a distinct one-time "stranger" reply, after which they follow the normal track.
- Anti-loop shields prevent the bot from talking to itself or spamming duplicates:
- Mirror Shield drops our own replies echoed back (scoped to a short window after each send).
- Photocopier Shield drops Android's duplicate re-deliveries of the same text.
- Echo Shield drops rapid bursts within a few seconds.
- The protocol stands down while the user is actively in WhatsApp. This uses
UsageStatsManager.queryEvents()to reconstruct the current foreground app from the OS event stream (MOVE_TO_FOREGROUND/MOVE_TO_BACKGROUND), which is accurate even for long-open sessions — unlike the aggregatedqueryUsageStatssnapshot. - Requires Usage Access (
PACKAGE_USAGE_STATS); the app detects the missing grant viaAppOpsManagerand guides the user to enable it. Results are cached briefly to keep the listener thread responsive.
- Distinguishes saved contacts from strangers by matching the notification title against the device contact list (
READ_CONTACTS) — exact name match plus last-9-digit phone-number matching to normalize formats like+94771234567vs0771234567. Falls back to a number-only heuristic when permission is denied.
- User-editable behavior (no rebuild required): the random reply pool, per-situation message lists (spam / call / stranger, one picked at random each time with no back-to-back repeats); any message in a list of two or more can be switched off to leave the random pick without deleting it (at least one always stays on), keyword→reply rules, the contact whitelist, the reply window, and the spam cooldown are all editable from the in-app UI.
- Reply To (whitelist / focus mode): with Reply To: Everyone, the people list is "Never Reply To" — those contacts are ignored. With Reply To: Only Selected People it inverts into an allow-list ("Only Reply To") — the protocol replies only to those contacts.
- Pause: pausing only saves a flag that the listener checks. The listener component is never disabled — on HyperOS, disabling it (even briefly, as the old pause/restart/watchdog did) revokes notification access. Restart and the watchdog now unbind/rebind instead.
- Storage: all settings persist in
SharedPreferences, mirrored into an in-memory cache that is rebuilt lazily via anOnSharedPreferenceChangeListenerso edits take effect immediately without per-notification disk reads. - Auto Backup:
allowBackupwith scoped backup/data-extraction rules preserves all settings across app updates, reinstalls, and device transfers. - Export / Import Backup: Settings › Backup saves every reply and setting (everything except reply history) to a JSON file through the system file picker, and restores it later after showing what the file contains. This is the reliable path for sideloaded installs, where Auto Backup often doesn't restore.
- Language: Java · Min SDK: 24 · Target SDK: 36
- Core APIs:
NotificationListenerService,RemoteInput/PendingIntent,UsageStatsManager,AppOpsManager,ContactsContract,WindowManageroverlays, foregroundService. - UI: fully programmatic (no XML layouts) — a minimal dark, end-user-facing design built from shared view helpers (
Ui.java) and a single centralized palette (Theme.java).
This project was built for educational and research purposes to understand the Android component lifecycle, memory management, and OEM process throttling. The 1x1 pixel overlay technique consumes additional battery by keeping the screen rendering pipeline active and should be used cautiously.


