ObliviOS Developer portal Project site

Home / Decisions / ADR-153

The system does not tell apps that the user took a screenshot.

Accepted, recorded 11 October 2026.

Decision
ADR-153
Date
2026-10-11
Status
AcceptedAccepted

1Decision

The system does not tell apps that the user took a screenshot. WindowManagerService.notifyScreenshotListeners returns an empty list at once, so no Activity.ScreenCaptureCallback is called and SystemUI shows no notice of notified apps. One patch for frameworks/base, package privacy/screenshot-detection of sovereignos-platform; the upstream body stays behind one constant. FLAG_SECURE is untouched.

2Why and evidence

Owner request 2026-10-11 (chat): apps can see that a screenshot is taken and people ask for it to be undetectable.

Verified in source (build server, frameworks/base, branch sovereignos-2026091900-r2): the only caller of notifyScreenshotListeners is SystemUI ScreenshotDetectionController.maybeNotifyOfScreenshot (through MessageContainerController.onScreenshotTaken, every source except the overview), and the notice that names the notified apps is shown only for a non-empty list.

The change removes a signal to apps and adds no capability, permission, endpoint or IPC; it lowers no upstream hardening: a screenshot is still blocked by FLAG_SECURE, so banking, identity and DRM apps are unaffected.

Measured on lynx image 2026101101 (PRIV-001): the built notifyScreenshotListeners has only the permission check and the empty list (dexdump); a test app that registered the callback logged REGISTERED, a system screenshot was taken and the app logged no FIRED.

3Consequences

An app that holds the media permission still sees the saved screenshot file. Screen-recording callbacks (WindowManager.addScreenRecordingCallback) are untouched. A page in a browser has no detection API of its own, so the change acts only on apps. An app that uses the callback as a protection of its own (it hides its content when a screenshot is taken) no longer gets that signal. There is no unpatched image to show that the callback fires there; that is upstream behaviour read in source, not a run.

4Review when

An app or a compatibility report that needs the callback; upstream adds another way to detect a capture; the patch stops applying after an upstream rebase.

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