- Decision
- ADR-069
- Date
- 2026-08-30
- Status
- AcceptedAccepted
- Mentions
- ADR-066
1Decision
Fix the audit's High item 8 (the dormant status-bar multi-user icon) and Medium item 12 (the Multiuser widget's own data layer).
2Why and evidence
UserManagerService#areThereMultipleUiSwitchableUsers() gates isUserSwitcherEnabled(), which controls the status bar's mMultiUserAvatar icon — directly observed on the physical device's lock screen during this session's own earlier hardware testing. It called the raw getUsers(excludeDying=true).
Confirmed via source this is currently masked only as a side effect of the decoy user type's own default restriction set not setting DISALLOW_ADD_USER (the sibling check in isUserSwitcherEnabled() short-circuits first) — a coincidence, not a fix, since a future restriction-default change could silently reactivate it with no code change of its own.
Fixed with a one-line substitution to this same class's own already-fixed getUsersForUiDisplay(true) (patch frameworks-base 0029).
Separately, the Multiuser widget's own UsersRepository.getUsers() called the raw getAliveUsers(), three lines from its own sibling checkUserSwitchRestrictions() in the same file, which was already migrated — every real user's name/avatar loaded into memory on every widget refresh, currently withheld from rendering only by an incidental filter elsewhere in the widget (CurrentUserStateUseCase.kt), not by design.
Fixed to match the sibling method (patch packages-apps-multiuser 0002).
Both authored under the established local-first worktree discipline (fetched files confirmed byte-identical via sha256sum before editing, landed via git am only after confirming no build was in flight, patches regenerated fresh from real post-git am branch history) and independently build-verified (m services: Build Succeeded: 18 steps; m Multiuser: Build Succeeded: 30 steps, both MultiuserWidgetLib and the outer app module compiling cleanly), no diagnostics on either edited file.
3Consequences
Patches exported to aegisos-platform/credential/duress-unlock-decoy/patches/{frameworks-base,packages-apps-multiuser}/, SOURCE.md/README.md updated. Both fixes are compile-time verified only, deferred to the same consolidated hardware-validation round as ADR-066/068.
4Review when
Nine of the 21 audit items are now fixed (Critical 1-3, High 4-8, Medium 12). Remaining: Guardian's cross-user AppOps ingestion (item 13, needs aegisos-services source review or a hardware test before a fix can be scoped), and three low-confidence items (14, 16, 17) needing further tracing before a responsible fix/no-fix call.
Read from docs/governance/decision-log.md, entry ADR-069.