ObliviOS Developer portal Project site

Home / Decisions / ADR-095

Close ADR-092/094 re-open condition 3 (partially).

Method, recorded 20 September 2026.

Decision
ADR-095
Date
2026-09-20
Status
MethodMethod confirmed working; full decoy-vs-owner color match still unconfirmed. The tooling gap itself (no reliable screenshot method existed) is closed; the specific decoy scenario needs the owner's own set-decoy-profile run to finish verifying.
Mentions
ADR-063, ADR-082, ADR-092
Mentioned by
ADR-096

1Decision

Close ADR-092/094 re-open condition 3 (partially): confirm a working live avatar-color pixel-verification method end-to-end on a real, relevant screen.

2Why and evidence

On the same build-server emulator, adb shell pm create-user created an ordinary second user (non-decoy), Settings ▸ Users was opened via am start -a android.settings.USER_SETTINGS, uiautomator dump gave each row's icon bounds, and adb exec-out screencap -p + the same pure-Python PNG decoder sampled real, distinct pixel colors: Owner (228,105,98), the ordinary second user (158,158,158) — genuinely different colors, the expected/correct baseline for a non-decoy secondary user (only a registered decoy should get the owner's own color via isMainForUiDisplay).

This directly demonstrates the screenshot method works on the exact class of screen (Settings ▸ Users) the ADR-082 avatar-color patches target, refuting the prior "screencap unreliable, root cause not identified" framing for this context — docs/architecture/duress-engineering-notes.md's own solid-black finding was reproduced separately this session, but only on a genuine FLAG_SECURE surface (a PIN bouncer), confirming it as intentional Android secure-surface behavior, not a tooling defect.

3Consequences

Full decoy-color-match confirmation (registering an actual org.aegisos.usertype.full.DECOY user via set-decoy-profile --owner-credential <cred> <decoyUserId> and re-sampling both rows) was not done: that command requires typing a credential value, which per this project's own hard rule (and the assistant's own standing prohibition on entering any password/credential into any field or command, regardless of context) must always be run by the owner directly, never the assistant — matching the exact precedent already established for the physical device (ADR-063).

The test user created for this round (pm create-user testsecondary, id 10) was removed after the comparison; the emulator was left in its post-wipe-data clean state otherwise.

4Review when

If the owner wants the full decoy-vs-owner match confirmed on this emulator: adb shell locksettings set-pin <test-pin> (a disposable test value, not a real credential, since this is a throwaway build-server emulator with no prior lock screen), adb shell pm create-user decoytest, then adb shell locksettings set-decoy-profile --owner-credential <test-pin> <decoyUserId>, then re-run the same screencap+sample procedure against both rows.

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