- Decision
- ADR-096
- Date
- 2026-09-20
- Status
- BothBoth UX gaps confirmed resolved on this candidate; avatar-color match confirmed correct. All of ADR-092's four re-open conditions are now closed.
- Part
- Duress Unlock
- Mentions
- ADR-064, ADR-083, ADR-092, ADR-094, ADR-095
- Mentioned by
- ADR-097, ADR-098, ADR-099, ADR-166
1Decision
Close ADR-092 re-open condition 4 (the two UX gaps: owner→decoy swipe residual, decoy→owner double-password) with real evidence on the current branch tip, and close condition 3 in full (the decoy-vs-owner avatar-color match).
2Why and evidence
The owner ran every credential-touching step themselves, per this project's own standing rule (locksettings set-pin 1234 for the owner, pm create-user --user-type org.aegisos.usertype.full.DECOY decoytest — id 12 after a first attempt without --user-type correctly failed DecoyProfileHelper's own type check from ADR-064 — locksettings set-decoy-profile --owner-credential 1234 12, then locksettings set-pin --user 12 5678 for the decoy's own separate credential); the assistant then drove the rest via adb/uiautomator.
Avatar-color match: Settings ▸ Users, opened fresh (a first attempt reused a stale cached Settings activity from ADR-095's own round and had to be force-stopped and restarted), shows the real registered decoy with a different color from Owner when viewed from the owner's own session ((158,158,158) vs Owner's (228,105,98)) — confirmed correct by reading UserManagerService.isMainForUiDisplay(): it only returns true for a decoy when that decoy is the device's actual current user, by design, so a decoy row viewed from a different session is expected to differ, not match.
UX gap 1 (owner→decoy swipe): entering the decoy's own PIN (5678) at the real bouncer (synthetic uiautomator taps, not a shell bypass) produced am get-current-user → 12 and, once the transition settled, isKeyguardShowing=false with topResumedActivity/mCurrentFocus on the decoy's own real QuickstepLauncher — no lingering swipe/lock surface.
UX gap 2 (decoy→owner double password): entering the owner's own PIN (1234) at the bouncer while the decoy session was active produced am get-current-user → 0 in one credential entry, and after the same settle delay, isKeyguardShowing=false on the owner's own real launcher — also no second prompt and no lingering swipe screen.
dumpsys activity users confirms both User #0 and User #12 reached RUNNING_UNLOCKED (not stranded, matching the ADR-083/084 storage-unmount fix holding), and dumpsys dropbox shows zero crash/ANR/watchdog entries across the whole round.
3Consequences
This is one emulator round on the build-server sdk_phone64_x86_64-cp2a-userdebug configuration, not a physical lynx re-validation — ADR-092's own four conditions never required physical hardware specifically, but a physical re-check would still be the stronger form of this same evidence if ever prioritized.
The decoy (id 12) and its test credential were removed after the round; the owner's own PIN (1234) was left in place on this disposable build-server emulator, not reverted — harmless since this device holds no real data and no other session depends on it staying unlocked-by-default, but worth knowing before reusing this exact emulator instance for an unrelated future task expecting no lockscreen.
4Review when
Re-open only if: (1) physical lynx hardware re-confirmation of either UX-gap result is ever wanted; (2) a future patch touches the decoy switch/return path or isMainForUiDisplay and needs re-verification; (3) the 4 unrelated UserRepositoryImplTest failures from ADR-094 turn out to be connected to any of this after all (not indicated by anything found this round).
Read from docs/governance/decision-log.md, entry ADR-096.