ObliviOS Developer portal Project site

Home / Decisions / ADR-078

Close the decoy primary-profile visual parity plan.

Accepted, recorded 3 September 2026.

Decision
ADR-078
Date
2026-09-03
Status
AcceptedAccepted, qualified
Part
Duress Unlock
Mentions
ADR-029, ADR-046, ADR-074, ADR-077
Mentioned by
ADR-079, ADR-083

1Decision

Close the decoy primary-profile visual parity plan (Tasks 5-7): consolidated lynx build, alpha/vault-key signing, and physical hardware validation of ADR-074 through ADR-077's four patches.

2Why and evidence

Task 5's first consolidated lynx build silently omitted packages/apps/Settings's changes (patches 0008/0009) from the flashed candidate — m -j6 systemimage reported success but system_ext.img (carrying Settings.apk on this device) kept a stale pre-patch mtime; caught by pulling the installed Settings.apk and grepping its dex files for isMainForUiDisplay, not by trusting the build's own success report.

Root-caused to a Ninja/Soong incremental-analysis staleness specific to the out-lynx output directory (not reproduced in out-preflight); worked around by force-touching the patched source files and invoking the systemextimage Ninja target directly after a plain m systemimage re-run reported "Build Succeeded: 0 steps" while the real target file was missing entirely — a second, distinct instance of a build claiming success while the artifact state disagreed.

The corrected system_ext.img was re-signed with the signing host's vault key (<vault>/keys/lynx/avb.pem — the key that has actually signed this device's trusted vbmeta since ADR-046, corroborating that this is not the original ADR-029/030 alpha key, a naming distinction clarified during this closure), rollback index 1783209600 (confirmed via avbtool info_image against the pre-signing build output), 13/13 AVB checks independently verified on the signing host and the build host.

Two real procedural incidents during signing were caught and corrected, not silently worked around: an initial staging location (<home>/sign-work/, 5GB) ran out of disk mid-copy and corrupted two partition images, contradicting this project's own already-written guidance to use <build-root>/signed/.ad-hoc-work/<name>/ for exactly this; and a first make_vbmeta_image attempt produced a silent zero-byte output (exit 0) because the vault had not yet been opened, caught by verifying the real output file rather than the exit code.

The owner flashed the corrected candidate via fastboot flashall (no -w, confirmed safe via the real fastboot-info.txt's if-wipe conditional). Full record: docs/devices/lynx-duress-decoy-visual-parity-findings.md.

3Consequences

Physical hardware confirms both patch sets present by direct extraction (not by build-number string, which proved to be a stale, harmless out-lynx cache artifact unrelated to code content) and zero crash/ANR/tombstone.

The QS footer "End session" fix — the plan's single highest-severity item, left UNCHECKED by the emulator round because a synthetic tap never opened the dialog — is now positively confirmed working on real hardware (the same tap opened the real "Select user" dialog; the SIGN_OUT action is genuinely absent for the decoy, present as before for the owner).

The Settings ▸ Users "Owner" label fix is confirmed with no false-positive leak onto the decoy's row when viewed by the owner.

Two items remain honestly UNCHECKED, not forced to a pass: the device-admin policy text fix (patch 0009) was confirmed present by dex string search but not dynamically exercised on hardware this round; the ordinary-secondary-user regression check relies on Task 6's emulator evidence (unchanged frameworks/base logic) rather than an independent re-run on this hardware.

A real, unrelated environment quirk was noted but not investigated further: /sdcard is inaccessible via adb shell while a secondary/decoy user is current.

4Review when

Any future session finding the compiled diff missing from a flashed lynx candidate despite a clean build log should check this entry's out-lynx/system_extimage finding before re-diagnosing from scratch. A future dedicated dynamic-validation pass should close the two remaining UNCHECKED items above before this feature's indistinguishability posture is described as fully hardware-verified end to end.

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