- Decision
- ADR-108
- Date
- 2026-09-28
- Status
- AcceptedAccepted
- Part
- AirPods
- Mentions
- ADR-106, ADR-107
- Mentioned by
- ADR-109, ADR-115
1Decision
Amend ADR-106: add a new, narrowly-scoped privileged AIDL method (setAirPodsIdentity-style) on IBluetooth.aidl, gated by a new dedicated signature permission held only by AirPodsApp, as the confirmed real bridge letting AirPodsApp register a validated bonded AirPods BD_ADDR with com.android.bluetooth's native interop database for design §6.2's scoped identity patch to consult.
2Why and evidence
Continuing Task 1's investigation to unblock Task 3, BluetoothDevice.setMetadata() was checked as a candidate bridge and found unusable: tracing its real implementation (AdapterService.setMetadata -> BluetoothStorageManager -> MetadataDatabase/MetadataDao/CustomizedMetadataEntity, confirmed Room/SQLite class names) shows its storage lives in a Java-side database inside com.android.bluetooth's own process, not reachable synchronously from the native SDP/L2CAP hook points sdp_server.cc/l2c_fcr.cc run in.
The existing native-reachable per-device store is btif_config, and the existing native path that writes into it for an arbitrary BD_ADDR is interop_database_add/interopDatabaseAddRemoveAddrNative — but confirmed private to com.android.bluetooth's own internal Java code (zero matches searching IBluetooth.aidl for either name).
interop_feature_t (system/device/include/interop.h) is a plain, extensible native enum with a matching CASE_RETURN_STR name table in interop.cc, confirming a new INTEROP_AIRPODS_IDENTITY entry follows an existing, real pattern rather than inventing new native plumbing. The only genuinely new surface needed is the single AIDL call from AirPodsApp into AdapterService, forwarding to that existing native mechanism.
3Consequences
Design doc §6.2 is amended in place with a second dated amendment note citing this ADR; original approved text and the ADR-107 amendment are both kept, not overwritten. This is a new IPC endpoint between two system apps and is held to this project's explicit higher bar for IPC-touching changes (AGENTS.md) — the new permission must be individually justified in docs/research/airpods-platform-api-verification.md per the platform-integration plan's own Global Constraints, before or alongside the task that first requests it. Task 3's patch may now proceed with a confirmed, real architecture for the identity-registration bridge instead of an unresolved gap.
4Review when
If a future Bluetooth-module rebase changes interop_feature_t's shape, removes the interop database mechanism, or AdapterService's AIDL surface is restructured, this bridge design needs re-verification against the new pinned revision before reuse. Revisit if code review finds a narrower-still bridge (e.g. reusing an existing permission instead of a new one) once the exact AirPodsApp permission set is finalized in Task 5.
Read from docs/governance/decision-log.md, entry ADR-108.