ObliviOS Developer portal Project site

Home / Decisions / ADR-138

After the device round on image 2026100215: (1) the AirPods app holds no POST_NOTIFICATIONS and shows no notification, not even the one its foreground service carries…

Proposed, recorded 5 October 2026.

Decision
ADR-138
Date
2026-10-05
Status
ProposedProposed
Part
AirPods
Mentions
ADR-137

1Decision

After the device round on image 2026100215: (1) the AirPods app holds no POST_NOTIFICATIONS and shows no notification, not even the one its foreground service carries; (2) Settings' device page has no lowered-volume ("Volume while speaking") choice, the own page keeps the slider; (3) the connection sheet has the Settings button only, a tap outside closes it.

2Why and evidence

Owner decisions 2026-10-05 (chat): no notification when the AirPods connect, only the sheet; the lowered-volume choice on the device page is ugly and goes; Done goes. Measured on lynx with the permission revoked: the service stays foreground (isForeground=true, foregroundId=1), a session runs (first frame after 2704 ms) and the package has 0 notification records [measured].

3Consequences

Supersedes the sentence of ADR-137 that POST_NOTIFICATIONS stays for the foreground service, the readable Done of ADR-137 (2), and the four-button lowered-volume group on Settings' device page (design update of 2026-10-04, AIR-149). The permission is removed from the manifest, so it cannot be granted or requested; this narrows the app, and the privapp allow-list never listed it.

The foreground service is unchanged (FOREGROUND_SERVICE_CONNECTED_DEVICE), so the session still runs while the process would otherwise be frozen. Proven by AIR-172 and AIR-149 after the next image: dumpsys package lists no POST_NOTIFICATIONS, and the device page and the sheet look as decided.

4Review when

A feature that needs a notification (then a new ADR), or a platform change that shows the foreground-service notification regardless of the grant.

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