- Decision
- ADR-233
- Date
- 2026-11-15
- Status
- ProposedProposed (owner, 2026-11-15: \"Ja, D1 t/m D9\" after the review; landing on the build tree without a build). Landed on the build tree 2026-11-15 (frameworks/base
7477bc952ea4to7bc79c21e815, Settings69945953b93), type-checked. The owner asked for an image build instead of a module build (2026-11-15); it isIMG-035(tools/build/build-lynx-2026111501.sh). Not run on a device (DUR-048toDUR-051). - Part
- Duress Unlock
- Mentions
- ADR-231
- Mentioned by
- ADR-234
1Decision
Fixes the findings D1 to D9 of the read of all Duress Unlock code (2026-11-duress-unlock-code-review.md) in credential/duress-unlock-decoy of oblivios-platform, as frameworks-base/0050 to 0054 and packages-apps-settings/0005: the lock-time warm start, mirrors and launcher look read run only while the owner's session is current (D1); the wait for the decoy's unlock does not spin (D4); the finger link zeroizes its derived key and cannot refill its cache after a clear (D7); the stage registers its receiver before it adds its window and decodes one wallpaper at a time (D5, D6); the wipe PIN or password is refused when it unlocks the decoy (D2); the Home key is not held back by a deferred decoy home (D8, third part only); the Settings screens warn when a decoy PIN no longer has the owner's length under Auto confirm and do not keep the owner credential in their saved state (D3, D9).
2Why and evidence
[verified-in-source] for every finding, see the review record; D1, D4, D5, D6, D7 and D8 are in the same classes as 0014 to 0049. D8 is applied only in part: the mint that outlives a failed switch (D8, first part) and the silent switch that is queued behind a running one (second part) need a new method of ActivityManagerInternal or a new coupling between locksettings and am, and ADR-231 rejected new methods of framework.jar for the module build (NoSuchMethodError, system_server ended at the duress PIN, 2026-11-15).
3Consequences
Rejected: editing the patch files by hand (CONTRIBUTING.md of oblivios-platform); a new ActivityManagerInternal method for D8 (see the rationale); refusing the wipe PIN in Settings only (the framework call is Binder-exposed, so the check belongs in DuressPasswordHelper); a rule in the routing that lets the wipe win over the decoy (it would wipe the phone silently for an owner who has both equal today, and adds a scrypt to the unlock path).
The check of D2 costs one hardware attempt on the decoy per wipe credential of the decoy's own type; five changes of the wipe credential without a decoy unlock in between would throttle the decoy (DUR-049). [assumption] A refusal of the wipe PIN ends in the existing error dialog of DuressPasswordSetupActivity (it catches every Exception); the Auto confirm warning is right because the keyguard hides Enter under Auto confirm.
4Review when
A build or a module build shows a changed timing of the duress unlock (DUR-019) or a wrong setting in the decoy after a lock (DUR-048); the wipe PIN dialog shows the raw exception text; D8's first or second part is wanted (needs an own ADR for the method or the coupling).
Read from docs/governance/decision-log.md, entry ADR-233.