2 Commits

Author	SHA1	Message	Date
Krzysztof kuhy Rudnicki	82e206116a	Make the geofence tell the truth, and the phone explain itself ... The enforcer failed in both directions: nothing blocked at home, and everything blocked at the office. The comparison was never inverted -- `metres <= threshold` was always right. Three separate causes: Only ACCESS_COARSE_LOCATION was declared. Android 12+ fuzzes coarse to a ~1-2 km grid against a 150 m fence, so a fix taken at home routinely landed outside it, read as AWAY, and restored every app the geofence exists to hide. FINE is now declared and self-granted by the device owner, along with coarse and background, re-asserted every pass so a reinstall cannot silently drop it. There were three states but two behaviours. LOCATION_UNKNOWN applies the identical sweep to AT_HOME -- correct fail-closed design, indistinguishable from outside. And nothing ever requested a fix: the pass read whatever another app happened to cache, so at the office with no navigation running the cache was empty. Passes now acquire a fix inside a location-typed foreground service, bounded at 20 s, and treat anything older than 30 min as no fix. That window is deliberately longer than the 15-minute cadence; a shorter one marks the newest cache stale on every pass of an idle phone and blocks everything. None of it was diagnosable. `adb logcat -d -s FocusOwner:V` came back empty while dumpsys showed 82 alarms had fired, and `run-as` is refused on the release build device owner requires. So the pass now writes a ring-buffered JSONL record read back in-app: reason, distance vs the fence, fix age/provider/accuracy, curfew state, and every hidden app with the rule that hid it. Coordinates are never recorded -- a distance is enough to debug a geofence, and this is a home address. Also fixed along the way: - Hysteresis keyed off `isEnforcing`, which is true under AWAY too because YouTube stays hidden, so the threshold was permanently radius+hysteresis. It now keys off whether the previous pass was inside the fence. - The scheduler's curfew-boundary alarms were documented but never scheduled; both callers invoked `scheduleNext()` bare, so 05:00 could land 15 min late. - Installing over the app cancelled its pending alarms, so `adb install -r` silently stopped enforcement until someone opened the app. MY_PACKAGE_REPLACED now re-arms it, verified on device without launching the app. - A wrong-typed log record threw instead of being skipped, and the exception escaped far enough to leave the page stuck busy -- which disables the release-device-owner button, the one control that must work when everything else has gone wrong. - `lib/enforcement.dart` was a second decision layer with no always-blocked concept, cited by KDoc as pinned by a `PolicyParityTest` that never existed. It would have made the new screen report YouTube visible while it is hidden. Deleted; the UI renders the Kotlin record rather than re-deciding. - Anchoring home accepted a stale or unknown-precision fix. A wrong home offsets the fence everywhere and forever, which is what produced a 766 m reading while standing at home. Policy: Play Store is allowed by day (not during curfew) so infakt can be installed and updated; the sweep is default-deny for third-party packages, so anything installed from Play is hidden on the next at-home pass. Tachiyomi's per-source extension apks are covered by a new prefix allowlist rather than an exact list that goes stale whenever an extension is installed. `export.py` stopped subtracting the allowlist from `blockable_system_packages`. Sweepable is not hideable: that list decides which system packages are eligible for a decision, and `isAllowed` is what protects them. Removing an allowed system package from the sweep freezes it in its last state -- it would have stranded Play hidden permanently the moment it was allowlisted. Verified on the Pixel 6a: FINE granted POLICY_FIXED, `applied AT_HOME` with a 0 m distance from a +/-11 m GPS fix, YouTube/Chrome/Firefox absent from `pm list packages -e`, Play Store, infakt, RunnerUp and all five Tachiyomi packages present. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HjxL9kdAzZmGqQA5tMNrZ8	2026-08-14 13:43:05 +02:00
Krzysztof kuhy Rudnicki	f636d2b21b	Make focus policy and blocklist usable without root; fix workout CDN unblock ... phone_focus_mode is built for a rooted phone: the hosts layer is a read-only bind mount over /system/etc/hosts, chosen so that even root-in-a-terminal cannot overwrite it. None of that ports to a stock locked device. This splits out the parts that are device-independent so one policy can drive both. python_pkg/focus_policy parses config.sh rather than copying it, so the shell config stays the source of truth and the two cannot drift. It rejects the shipped REDACTED_* coordinate placeholder instead of defaulting to (0,0), which would move "home" to the Atlantic and quietly disable the location gate. blocklist.py converts the hosts file to domains for a DoT resolver or a local VpnService. Three properties of the real 194k-line file make the obvious parser wrong, and all three are handled: generate_hosts_file.sh *comments out* deliberate unblocks rather than deleting them, so stripping '#' re-blocks facebook/messenger/linkedin/4chan; the StevenBlack header carries loopback and IPv6 housekeeping that would blackhole localhost; and ~1060 upstream annotation tokens ('#[adware.zeno]', '"spam') render as address=/"spam/, which makes dnsmasq refuse to start -- taking DNS down rather than blocking anything. Verified with dnsmasq --test over all 185681 generated domains. strip_workout_hosts.py had the same class of bug on the live rooted phone: exact set membership meant the allowlisted googlevideo.com never matched the dynamic r*---sn-*.googlevideo.com hosts YouTube actually streams from, so the workout unblock was only partly working. Now suffix-matched (17 lines stripped, was 14). The three new tests were checked against the original code in a throwaway worktree; two of them fail there, so they pin the fix rather than passing vacuously. focus_owner is a device-owner app that deliberately does nothing yet. It ships clearDeviceOwnerApp() implemented and tested first, because dpm remove-active-admin does not work on a device owner: an app that locks the device down before proving it can let go leaves a soft-brick recoverable only through fastboot on a locked bootloader. Built, installed and launched on the Pixel 6a; dumpsys afterwards confirms Device Owner Type -1 and no user restrictions, i.e. the phone is unchanged. Measured while scoping this, and not yet reflected in any enforcement code: on Android 16 both pm suspend and pm disable-user are cleared by a reboot, so shell-level app blocking is per-session only. setApplicationHidden is assumed to persist under Device Owner but is untested. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AwepyL5Lxs5QKbKkMpxxxL	2026-08-05 09:15:02 +02:00