- Decision
- ADR-136
- Date
- 2026-10-05
- Status
- ProposedProposed
- Part
- AirPods
- Mentions
- ADR-124, ADR-129
- Mentioned by
- ADR-137
1Decision
The AirPods app gets the privileged permission android.permission.START_ACTIVITIES_FROM_BACKGROUND, named in its privapp allow-list, for one use: ConnectionSheetTrigger starts the app's own ConnectionSheetActivity when a recognised AirPods connects (once per connection, ConnectionSheetPolicy, never during a call or a ring) and the phone is unlocked and interactive. The notification stays: its tap opens Settings' device details of the AirPods; the full-screen intent still serves a locked or dark screen. Supersedes the sentence of ADR-129 that excluded a background activity start permission.
2Why and evidence
Owner decision 2026-10-05: the popup with the rings must appear when the case is opened, as on an iPhone; on an unlocked phone a full-screen intent only produces a heads-up notification, and a broadcast receiver may not start an activity from the background without this permission. The permission is signature\|privileged (frameworks/base/core/res/AndroidManifest.xml:4923 [verified-in-source]), so only the privapp allow-list can give it to a non-platform-signed priv-app, as for START_FOREGROUND_SERVICES_FROM_BACKGROUND (ADR-124).
3Consequences
The only call site is the trigger. The sheet is not exported, shows the ring values and the listening mode and no personal data, and closes when the link drops. A misuse by a compromised app would be limited to showing its own screen; the app holds no overlay, no accessibility and no input permission. Proven on the device by AIR-172 (opens on a case opening with an unlocked phone, does not open twice per connection, does not open during a call).
4Review when
A second activity started from the background; sheet content with personal data; an exported sheet.
Read from docs/governance/decision-log.md, entry ADR-136.