RAGEQUIT SERVICES & OUTPUTS

Know what runs.
Know how to stop it.

Your Hit List rules can trigger effects while you use another app. Some effects need an Android service and a visible notification to keep their controls available.

Updated October 23, 2026. Features depend on the access, device hardware and playback information available on your phone.

Automatic effects and notifications

Once setup is complete and an authorized rule is saved, assigned sounds, vibration and supported challenges can start automatically when that app’s timing and eligibility conditions are met. Granting a permission by itself does not select a bait or start microphone capture.

An Android foreground service handles eligible sound and vibration and supports bounded sensor challenges. “Foreground service” means Android keeps a visible notification for an ongoing task; it does not mean the RageQuit app must be on screen. RageQuit’s output notification includes Stop outputs.

The service checks current use, access and output conditions. A lost permission, unavailable output or uncertain app state can stop or pause affected effects. Android can also interrupt a service. RageQuit cannot guarantee uninterrupted tracking on every device or every app.

Without Full Access, only your chosen free Hit List app and its assigned free baits are active. Saved paid baits and extra apps pause until Full Access is restored. See how saved setups and the free app work.

Media Playback access

Android calls this permission Notification access and shows a broad system warning. It is separate from allowing RageQuit to display its own notifications. RageQuit uses this access to observe the media sessions published by apps on your Hit List.

For those selected sessions, RageQuit checks the owning app, reported playing state and whether the player identifies its output as local or remote. It does not read notification messages, track titles, artwork, queues, playback positions or another app’s audio. Temporary session observations are not saved as playback history.

With this access enabled, supported selected playback can keep earning tracked use in the background. Assigned Ticking Deadline and Vibration Gremlin effects may continue while selected media reports playing with the screen off or locked. Visible touch and sensor challenges do not become hidden tasks.

A player’s “playing” report is not proof that sound is audible. Some apps or casting routes do not publish enough information; support varies. RageQuit does not send playback commands to remote receivers.

Humiliation and the microphone

Microphone access is required to finish first-time setup. Humiliation listens only while you explicitly hold its control during an eligible visible attempt. Release, cancellation, completion, permission loss or a safety limit stops capture. Audio is analyzed locally for accepted humming; no recording, voice profile or pitch history is saved or uploaded.

With Media Playback access, a held Hum attempt can request a bounded pause of a qualifying selected local player. After microphone capture has stopped, RageQuit may resume that same player once if its state and safety checks still permit it. It does not unconditionally restart playback, and access by itself never begins listening.

Motion and compass challenges

Configured motion and compass challenges use the available sensors only during the current visible task. Unavailable or stale readings do not earn progress. Touch Grass is retired; it is not an active Rage Bait, and current setup does not request Physical Activity access.

These are local challenge inputs. RageQuit does not use location, camera access or screen recording for them. Turning on access does not assign a challenge.

Volume Drop changes real media volume

An assigned Volume Drop effect also makes bounded reductions to the phone’s local media volume when its timing and safety conditions allow. It does not change ringtone or alarm volume, and does not control a remote receiver’s volume. It does not keep a saved volume level to restore later.

Other sound and haptic previews can produce real sound or vibration. Their availability depends on Android’s current output and quiet-mode settings.

Stopping and reviewing access

• In a preview: demonstrations start automatically when their required access and hardware are available. Use the preview’s Stop control to end its run. Leaving the preview or losing the required visibility or focus also cancels it. A stopped or interrupted preview needs an explicit Play to restart during that visit.
• For active service outputs: open Android’s notification shade and tap Stop outputs. This ends the current output session and suppresses automatic outputs until you reopen RageQuit. It does not delete rules, reset tracked use or restore a volume level already changed. Reopening RageQuit allows saved effects to run again when the selected app is eligible.
• For access: open Rage HQ → Update Rage Access to review the four access types and their Android settings. All four are required for first-time setup. Android lets you revoke access later; affected features become unavailable.

Android navigation remains accessible during challenges. Stop controls are immediate controls for their respective sessions, rather than a change to the saved Hit List. The Rage Code protects configuration changes inside RageQuit. On supported Android Settings pages, the storage-management button opens Manage RageQuit storage, where resetting requires a fresh code check and explicit confirmation. If no code has been set, confirmation is still required.

App info, clearing the cache, uninstalling and the Accessibility toggle remain available without a Rage Code. Clearing the cache keeps your code, rules and tracked-use totals. Clearing stored app data or uninstalling removes those local records. The app’s storage screen works independently of Accessibility and cannot prevent resets through uninstall/reinstall, privileged tools, recovery or other unsupported routes.

For the information behind app recognition, read Accessibility access. For stored data and website connections, read Privacy. If an effect behaves unexpectedly, contact support with the app version and Android version, without sharing your Rage Code.