- Decision
- ADR-210
- Date
- 2026-11-02
- Status
- ProposedProposed
- Part
- Duress Unlock
- Mentions
- ADR-145
1Decision
Amend ADR-145: the Duress Unlock second credential has the type of the screen lock, a PIN under a PIN lock and a password under a password lock; a pattern or no lock still offers no set-up. Patch packages-apps-settings/0003 of credential/duress-unlock-decoy; frameworks/base does not change.
2Why and evidence
Owner request 2026-11-02 (chat): the second credential may be a password; ADR-145 had made it PIN-only until a password was built. SyntheticPasswordManager rejects a typed credential whose type differs from the stored one and the keyguard types the lock's own type, so the decoy type must equal the lock type [verified-in-source: SyntheticPasswordManager.java, Credential type mismatch]; the routing (DecoyProfileHelper.maybeRouteToDecoy) and the wipe check (DuressPasswordHelper.isDuressCredential) already handle both types [verified-in-source].
3Consequences
A lock type changed after the set-up leaves a decoy that never matches, which is the worst failure for this feature; the main screen says so and Change repairs it, but nothing stops the lock change itself. The Auto confirm unlock length rule applies to a PIN only. The patch is landed as dcb63695a6f on the build-server Settings branch, not compiled and not run.
4Review when
Accepted when rows DUR-014 to DUR-018 of the validation matrix have evidence or the owner waives them; a row that fails on lynx reopens the design.
Read from docs/governance/decision-log.md, entry ADR-210.