ObliviOS Developer portal Project site

Home / Decisions / ADR-169

Add grab detection as designed in 2026-10-15-grab-detection-design.md.

Accepted, recorded 15 October 2026.

Decision
ADR-169
Date
2026-10-15
Status
AcceptedAccepted (owner, 2026-10-15, after review of the written design).
Part
Grab detection
Mentioned by
ADR-176, ADR-195, ADR-260

1Decision

Add grab detection as designed in 2026-10-15-grab-detection-design.md. While the phone is unlocked and interactive, a new system_server service detects a pull out of the hand from an acceleration peak, the end of touch contact and continued movement. Phase 1 locks the phone with STRONG_AUTH_REQUIRED_AFTER_USER_LOCKDOWN, shows one line above the PIN entry and vibrates.

Phase 2 is the existing GrapheneOS auto-reboot timer, armed through sys.auto_reboot_ctl for a fixed 60 seconds before the lock; a PIN unlock cancels it. The first build ships a shadow mode (log only) with thresholds tunable by Settings.Global keys; one on/off switch in Settings; identical behaviour in the decoy session; no exception during a call. BFU without a restart is parked (docs/research/bfu-without-reboot-feasibility.md).

2Why and evidence

An additional layer that reuses the lock and the restart path of upstream. init is not changed (the timer, its 20-second floor and its "ignore while running" rule are used as they are), no Binder interface, permission or network access is added, and the touch monitor keeps only a contact flag and a release time. SecureLockDeviceService was rejected: it is flag-gated, persists across reboot and needs two-factor to disable. The false-positive rate outdoors cannot be shown by room tests; daily use on stallion is the evidence and the owner accepted fixing what it shows.

3Consequences

A new service in system_server with a spy-window input monitor, one Settings switch and one lock screen line; the lock path is touched. The thresholds are unknown until measured. A pull without touch contact is not detected.

4Review when

The shadow phase shows false triggers that thresholds cannot remove; a request for a detection route without touch or with a trusted Bluetooth device; a working BFU without a restart (it replaces the restart in phase 2).

Read from docs/governance/decision-log.md, entry ADR-169.