The iptables chain machinery (ensure_chain, trusted_dot_ips, fill_chain_v4/v6, expected_rule_count, chain_intact, enforce_iptables) moves into dns_iptables.sh — a sibling, not a lib/ member, because lib/ does not exist on the phone and deploy.sh copies these files flat into $REMOTE_DIR. Both deploy lists grew the entry, matching how tether_iptables.sh is carried; it is correctly absent from the chmod 755 line, since a sourced library needs read, not execute. extract_shell_functions.py refuses to anchor a source line in a #!/system/bin/sh script, as documented — but when it refuses it still writes the library and does NOT remove the functions from the source, so a naive run leaves every function defined twice and the entry script longer than it started. The excision was done separately; the hash tool confirms all 14 functions moved verbatim. test_dns_enforcer.sh is deleted rather than repaired. Its six assertions targeted extract_ping_ip, extract_package_uid and append_unique_line — none of which dns_enforcer.sh has ever defined. It died at its source line and had never run a single assertion since it was added. Its replacement, test_dns_iptables.sh, covers all seven moved functions with 20 assertions, staged the way test_tether_enforcer.sh stages its subject. Three independent mutations were each caught: undercounting the trusted-resolver ACCEPT, miscounting rules per DoH IP, and moving the ACCEPT after the blanket REJECT. Shared staging lives in dns_iptables_harness.sh so both test files stay under the cap. Not verified on the phone — no deploy has run, by instruction. Over-cap count 23 -> 22. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY |
||
|---|---|---|
| .. | ||
| docs | ||
| focus_status_app | ||
| lib | ||
| systemd | ||
| backup_manifest.sh | ||
| batch3_bloatware_uninstall.sh | ||
| config.sh | ||
| curfew_enforcer.sh | ||
| deploy.sh | ||
| distraction_purge.sh | ||
| dns_enforcer.sh | ||
| dns_iptables.sh | ||
| enable_persistent_adb.sh | ||
| focus_ctl.sh | ||
| focus_daemon.sh | ||
| hosts_enforcer.sh | ||
| launcher_enforcer.sh | ||
| magisk_service.sh | ||
| phone_backup.sh | ||
| README.md | ||
| restore_apps.sh | ||
| run_phone.sh | ||
| strip_workout_hosts.py | ||
| tether_enforcer.sh | ||
| tether_iptables.sh | ||
| workout_detector.sh | ||
Phone Focus Mode
Location-based app restriction for a rooted Android phone using wireless ADB.
When within ~500m of home: only whitelisted productive apps remain usable. When outside that radius: all apps work normally.
Requirements
- Rooted phone with Magisk installed
- Wireless ADB enabled (
Settings → Developer options → Wireless debugging) adbinstalled on your PC (sudo apt install adbon Debian/Ubuntu)- GPS/Location enabled on the phone
Setup (first time)
1. Find your home coordinates
Open Google Maps, right-click your apartment → copy the coordinates shown.
2. Edit config_secrets.sh
HOME_LAT="-48.876667" # your latitude
HOME_LON="-123.393333" # your longitude
3. (Optional) Adjust the whitelist in config.sh
To find the exact package name of any app:
./deploy.sh <phone_ip> --find-pkg stronglift
./deploy.sh <phone_ip> --find-pkg anki
./deploy.sh <phone_ip> --find-pkg pomodoro
Then add the correct package name to WHITELIST in config.sh.
4. Deploy
chmod +x deploy.sh
./deploy.sh 192.168.1.42 # replace with your phone's IP
This:
- Pushes all scripts to
/data/local/tmp/focus_mode/on the device - Installs a Magisk
service.dscript so the daemon auto-starts on boot - Starts the daemon immediately
Usage
./deploy.sh <ip> --status # Current mode, location, distance from home
./deploy.sh <ip> --log # View recent daemon log
./deploy.sh <ip> --list # List all apps + whitelist status
./deploy.sh <ip> --enable # Force focus mode ON (for testing)
./deploy.sh <ip> --disable # Force focus mode OFF
./deploy.sh <ip> --stop # Stop daemon entirely (restores all apps)
./deploy.sh <ip> --start # Start daemon
./deploy.sh <ip> --restart # Restart daemon (picks up config changes)
./deploy.sh <ip> --pull-log # Download log file to your PC
How it works
Every 60 seconds:
get_location() ─── dumpsys location ──► lat,lon
│
▼
calc_distance() ─── Haversine formula ──► meters
│
├── within radius? ──► enable_focus_mode()
│ pm disable-user all non-whitelisted apps
│ record which apps were disabled
│
└── outside radius? ──► disable_focus_mode()
pm enable each app in the disabled list
Hysteresis: 50m buffer prevents rapid toggling at the boundary. You must travel
radius - 50m inward to trigger lock, and radius + 50m outward to unlock.
Fail-safe: If location is unavailable for 5 consecutive checks (~5 minutes), focus mode is automatically disabled so you can't be locked out.
State persistence: The daemon records exactly which apps it disabled
(in /data/local/tmp/focus_mode/disabled_by_focus.txt), so it never accidentally
re-enables apps that were already disabled by the user before focus mode ran.
On-device control (without PC)
From a root terminal app (e.g. Termux + tsu):
su --mount-master -c 'sh /data/local/tmp/focus_mode/focus_ctl.sh status'
su --mount-master -c 'sh /data/local/tmp/focus_mode/focus_ctl.sh disable'
Why --mount-master: MagiskSU puts each su -c session in an isolated
mount namespace by default, so bind mounts made by the hosts enforcer would be
invisible (and /data/adb/focus_mode/* checks would fail due to SELinux
interactions). --mount-master joins the global namespace where the daemons
(started from Magisk service.d at boot) actually live. The boot autostart
script doesn't need this flag because post-fs-data already runs there.
File layout
| File | Purpose |
|---|---|
config.sh |
Coordinates, radius, whitelist, constants |
focus_daemon.sh |
Main daemon — runs on device, loops every 60s |
focus_ctl.sh |
Control utility — runs on device |
curfew_enforcer.sh |
Night-curfew enforcer — grayscale + DND + optional net |
hosts_enforcer.sh |
Bind-mounts hosts.canonical over /system/etc/hosts |
magisk_service.sh |
Magisk boot hook → auto-starts both daemons |
deploy.sh |
PC-side ADB deployment and control script |
Hosts hardening
A second daemon, hosts_enforcer.sh, locks the phone's /system/etc/hosts
to the same blocklist installed by linux_configuration/hosts/install.sh
on the PC. Three layers:
- Canonical copy at
/data/adb/focus_mode/hosts.canonicalischattr +i. - It is bind-mounted read-only over
/system/etc/hostsat boot. - A watchdog verifies a sha256 every 15 seconds and restores on mismatch.
This blocks the common echo > /etc/hosts one-liner from a terminal app.
It is NOT a guarantee against a determined root user on the device itself —
a real "impossible without USB" gate would require removing su access,
which would break the rest of this system. The watchdog at least ensures
tampering is logged and reverted within ~15s.
Status and logs:
./deploy.sh <ip> --hosts-status
./deploy.sh <ip> --hosts-log
Periodic rescan / Play Store
The focus daemon now re-scans every tick (not just on first entry). If
you re-enable an app via Play Store or pm enable, it gets re-disabled
within CHECK_INTERVAL_FOCUS seconds. com.android.vending (Play Store),
com.*.packageinstaller, and popular terminal apps are also uninstalled
--user 0 in focus mode to close the usual bypass paths. Google Play
Services (com.google.android.gms) is left alone so banking apps work.
More detail
Split out to stay under the 250-line cap.