ObliviOS Developer portal Project site

Home / Decisions / ADR-117

Close the open decisions O1-O5 of ADR-116 from a read-only investigation of the pinned tree, and recommend not granting BLUETOOTH_PRIVILEGED to AirPodsApp.

Accepted, recorded 29 September 2026.

Decision
ADR-117
Date
2026-09-29
Status
AcceptedAccepted (findings and O1, O3-O5); O2 route pending owner confirmation
Mentions
ADR-116
Mentioned by
ADR-119, ADR-125, ADR-135, ADR-140

1Decision

Close the open decisions O1-O5 of ADR-116 from a read-only investigation of the pinned tree, and recommend not granting BLUETOOTH_PRIVILEGED to AirPodsApp. O1: a transparent bitmap per mode button on the native page only. O2: a narrow platform setter setAirPodsMetadata behind MANAGE_AIRPODS_IDENTITY (proposed patch 0006). O3-O5 closed with recorded values and tooling. O6 stays out of scope.

2Why and evidence

Evidence is docs/research/airpods-settings-ui-investigation.md, every finding with a path and line. The live native toggle is the view-based SegmentedButtonPreference (the Compose variant has no caller), whose button has no text, so a transparent icon leaves no gap. Settings can find the provider only through device metadata; there is no resource route.

IBluetooth#setMetadata is key- and device-agnostic and enforces BLUETOOTH_PRIVILEGED, so granting it would let the app rewrite any paired device's metadata; the ring needs about 15 metadata keys, not three. Settings takes a persistable URI grant before it loads a ring icon (UriGrantsManagerService.java:438-441 throws without one), so the icon provider must grant Settings access; a permission-only provider would leave blank icons.

The platform already deletes a device's metadata on unbond. Title size and category colour in the design were right; the level greens in the reference were wrong and are corrected.

3Consequences

Adds patch 0006 (a new IPC endpoint in the Bluetooth module: higher review bar, worktree route, own plan) and validation case AIR-036; amends ADR-116's provider and icon-provider security wording; the icon provider becomes non-exported with a per-URI grant. Plan 6 (UI implementation) is defined by the record's "Conclusions for Plan 6" and depends on Plan 3 Tasks 4-6 and on 0006. Not proven: how the transparent-button row looks on a device (AIR-033), whether a platform_apis app links the system_current SettingsLib modules (single build), the byte format of the battery and charging metadata (read in Plan 6).

4Review when

Owner confirmation of O2; if AIR-033 shows a gap or clipping with the transparent icons (fall back to a row that opens our page); any rebase that changes SegmentedButtonPreference, the DeviceSettings framework, AdvancedBluetoothDetailsHeaderController#loadIcon or UriGrantsManagerService.

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