ObliviOS Developer portal Project site

Home / Decisions / ADR-238

Amend ADR-194 (the decoy user stops after a visit).

Proposed, recorded 16 November 2026.

Decision
ADR-238
Date
2026-11-16
Status
ProposedProposed 2026-11-16 (owner's choice for review A3; type-checked on the build server, not landed, not built, not on a device)
Part
Duress Unlock
Mentions
ADR-194

1Decision

Amend ADR-194 (the decoy user stops after a visit): only the Duress decoy user is stopped when the device switches away from it. UserController.stopUserOnSwitchIfEnforced stops an old user of type USER_TYPE_FULL_OBLIVIOS_DECOY besides the stock rules, and the product property fw.stop_bg_users_on_switch=1 of memory/decoy-stop-on-switch vendor-adevtool/0001 is removed (vendor-adevtool/0002). Patches memory/decoy-stop-on-switch frameworks-base/0001 and vendor-adevtool/0002.

2Why and evidence

Review A3 of 2026-11-unreviewed-code-review.md. [verified-in-source] the stock property stops every secondary user on a switch (UserController.isStopUserOnSwitchEnabled, stopUserOnSwitchIfEnforced); ADR-194 only knew of no app that relies on a running second user. The other reader of the property, the package kill at the start of a switch, returns false for the decoy already and the stock default for every other user once the property is gone.

3Consequences

A secondary user other than the decoy (a work profile as full user, a guest is stopped by stock code anyway) is no longer stopped on a switch and stays resident as on stock. The decoy keeps stopping, as before. A change of device-common.mk needs the adevtool pin of each built device updated (memory/zram-size/SOURCE.md, \"Apply\").

4Review when

Accepted when the decoy reads User is not started after a visit on an image that carries it (MEM-021 is the row for the old mechanism); reopen if a second user must be stopped as well.

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