- Decision
- ADR-230
- Date
- 2026-11-14
- Status
- ProposedProposed (owner, 2026-11-14: every criterion must be met, the time equal to the ordinary unlock, "work thoroughly").
0035and0036landed on the build tree (f83ebf636926,de89c21728ad) with the owner's yes and pushed to the phone as a module build afteradb disable-verity(owner's yes); the stage window and the Launcher prefs copy are designed, not written. - Part
- Duress Unlock
- Mentions
- ADR-088, ADR-229, ADR-231
- Mentioned by
- ADR-229, ADR-231
1Decision
The Duress unlock and the return from the decoy are shown over a SystemUI stage window that carries the owner's wallpaper and keeps the notification stack hidden until the decoy's (or the owner's) home has drawn, so the keyguard's own exit animation (pad flight, wallpaper dim and recovery) plays over a real background as for an ordinary unlock; the decoy's Launcher3 look preferences (themed icons, shape, labels) are copied into the decoy's prefs when its storage is open.
Replaces ADR-229's rejection of a placeholder window (owner, 2026-11-14: "if this is the best solution, do it", after a better one was looked for). The decoy wallpaper is copied as files (frameworks-base/0035) and the decoy is not killed at the start of the switch back (0036). The mechanisms of the stage and of the look copy are corrected by ADR-231 (2026-11-15).
2Why and evidence
[measured 2026-11-14, lynx 2026111401 plus 0035 and 0036] Ordinary 0.77 to 0.83 s; duress 0.83 and 0.85 s, return 0.96 and 0.97 s, stock exit 1.27 to 1.37 s. Black for about 0.8 s between the pad and the decoy home (fast path); a wallpaper card sliding up, 0.15 s of black and a notification card on one frame (stock exit); on the return a flat fill, a wallpaper card over 75% with a band over 25%, a dark fill.
The decoy launcher draws +711 ms after its start. The owner's Launcher prefs hold icon_theme_id mono-icons:with-theme, icon_shape_model square, labels hidden; the decoy's hold none. Full record: duress-engineering-notes.md.
3Consequences
Rejected, each with its reason: holding the exit until the decoy home has drawn (the stock exit, 1.27 s, with the snapshot and the sliding card); starting the decoy home earlier inside the switch (the transition waits for its first draw); keeping the owner's wallpaper engine bound across the switch (the wallpaper layer needs a window as target); a warm decoy launcher (the decoy is opened only when needed); the owner's home as the stage (ADR-088).
[assumption] A SystemUI window above the transition's snapshot layer can hold the stage; the keyguard's exit animation plays over it unchanged; the Launcher reads its prefs after the copy (needs 0021 out); the palette of the decoy equals the owner's once the wallpaper colours are extracted.
4Review when
The stage window cannot be placed above the transition snapshot; the stage and the exit do not look like the ordinary unlock on a frame read; the time of the duress unlock rises above the ordinary one; the owner sees a tell the stage did not remove.
Read from docs/governance/decision-log.md, entry ADR-230.