If you have ever set a screen time limit at 9 PM and watched it disappear at midnight, you already know the problem. Most Android blockers fail because the person who set the rule is also the person who can undo it, and willpower is lowest late at night. I built Ripple (v0.1.1), a free and local-only Android focus app, to close the three loopholes I kept hitting myself.
The three classic loopholes
1. Changing the system clock. Sleep schedules and cooldown timers usually read wall-clock time. Open Settings, move the date forward a day, and the timer is over. Any blocker that trusts System.currentTimeMillis() can be beaten in seconds.
2. Scrolling feeds inside whitelisted apps. Most people whitelist messaging apps so they stay reachable. Those apps now ship short-video feeds and stories, so a "messaging only" exception becomes a two-hour scroll session.
3. Uninstalling or force-stopping the blocker. If an urge hits at midnight, revoking Accessibility permission or uninstalling the blocker takes about five seconds. Friction that you can remove on demand decays to zero.
How Ripple closes each one
Monotonic clock anchoring
Ripple measures every timer with SystemClock.elapsedRealtime(), which keeps counting regardless of what the user sets in the date and time settings. The app anchors its state to this clock and re-anchors across reboots, so changing the phone's time does nothing to a running cooldown or a sleep lock.
Asymmetric cooldowns
Tightening a rule is instant. Add an app to the block list, lower a daily limit, or extend sleep hours, and it applies immediately. Relaxing a rule is slow. Pausing a schedule, raising a limit, or unlocking uninstall requires waiting out a cooldown of 15 minutes by default, configurable up to 2 hours, and doubled for short-video apps. If a real emergency comes up, a friend or family member can generate a one-time unlock code so you can skip the wait.
Per-session caps on whitelisted apps
Whitelisted messaging apps get a 30-minute per-session limit. You can still reply to people, but a built-in video feed cannot turn into a late-night loophole.
Uninstall and force-stop protection
On Android 11 and newer, Ripple can pair with Wireless Debugging on the phone itself, with no PC and no root. It starts a small local daemon through app_process running as UID 2000 (the shell user). That daemon locks the OS uninstall switch and restarts the blocker within about 2.5 seconds if it is swiped away from Recents. If you already use Shizuku, Ripple supports that route too.
Why the design works
Each fix removes one cheap exit. The monotonic clock removes the time trick, the asymmetric cooldown makes late-night relaxing costly, the session cap shrinks the whitelist loophole, and the shell daemon protects the app itself. Together they keep a rule you set in the morning alive at midnight.
Try it
- Project page: https://ripplefocus.github.io/en/
- Comparison with AppBlock and StayFocused: https://ripplefocus.github.io/en/vs-appblock-stayfocused/
- Latest release (APK): https://github.com/ripplefocus/ripplefocus.github.io/releases/latest
Feedback from developers and digital minimalists is welcome, especially on edge cases for the clock and uninstall protections.
Top comments (0)