Oblivion

net.oblivion.wipe
by Zapstore Catalog

Remote lock and wipe triggers for compromised or unattended devices.

Oblivion is a security-focused Android application that allows a user to lock and wipe a device when a trigger is fired. The application is intended for high-risk situations such as device loss, forced unlock, or temporary loss of physical control. Trigger methods: * Panic button (Quick Settings tile) * Remote message containing a secret code * Trigger when the device has not been unlocked for a configurable period of time Actions: * Perform a factory reset (wipe) Device control is implemented using the Android Device Administration API. The has full support for GrapheneOS. Security notes: * Only encrypted (password protected) devices can guarantee that data cannot be recovered * The application does not function in Safe Mode License Free and Open Source Software GPL-3.0

First release: Nov 17, 2026, 1 total release.

Most recent release: Nov 17, 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

  • Nov 17, 2026 1.0.8
    Much thanks to @bearincrypto. [Replace lock-trigger foreground service with alarm polling](https://gitlab.com/swampc4-group/oblivionwipe/-/commit/a66b718ba8226401670b6478924fce4cb860a5e8 "Replace lock-trigger foreground service with alarm polling The LOCK trigger required a permanent foreground service only because ACTION_SCREEN_OFF / ACTION_USER_PRESENT cannot be manifest-registered since API 26. That forced an always-visible notification (with a placeholder title) and a permanent entry in the system task manager. Replace it with a self-perpetuating setExactAndAllowWhileIdle alarm that
    More…
    wakes the process once per minute and reads the lock state directly from KeyguardManager. Wipe semantics are unchanged: the deadline starts when the device locks, is reset by an unlock, and triggerLockCount is read live on each tick. Between ticks the process is cached and invisible, so the notification and the task-manager entry are gone entirely. Details: - BootReceiver re-arms the chain after boot/app-update (RTC alarms do not survive reboots); direct-boot ticks keep the chain alive without evaluating prefs, since encrypted prefs are not readable before first unlock. - Exact alarms degrade to ine...") [app-release.apk](/uploads/52dab9d124aa5f5546aebcf6a4f9d766/app-release.apk)