- Decision
- ADR-118
- Date
- 2026-09-29
- Status
- AcceptedAccepted (scaffold uncompiled)
- Part
- AirPods
- Mentions
- ADR-115
- Mentioned by
- ADR-124, ADR-158
1Decision
AirPodsApp is a privileged app on /system that is NOT platform-signed and NOT platform_apis: sdk_version: "system_current", default development certificate (release key at signing), one privileged permission (MANAGE_AIRPODS_IDENTITY) and a single-package hidden-api-whitelisted-app sysconfig entry. This decides the open certificate question of ADR-115 and folds Plan 3 Task 4 (the exemption) into the Task 5 scaffold.
2Why and evidence
The platform-signed route (Guardian's posture) would give the app the platform key's identity and every signature permission, far beyond the two things it needs.
The privileged calls it needs are @SystemApi (BluetoothDevice#setAirPodsIdentity, patch 0005), so system_current suffices; its only hidden-API use (the BluetoothSocket L2CAP constructor) is covered by the sysconfig entry the exemption investigation already verified (SystemConfig.java:918, :1049), which exempts one package and is read from /system/etc/sysconfig, not the /product path upstream marks for removal.
system_current also removes the risk that a platform_apis app cannot link the system_current SettingsLib modules. Evidence and per-permission justification: docs/research/airpods-platform-api-verification.md.
3Consequences
Scaffold landed in sovereignos-platform airpods/app/ and airpods/core/ (vendored airpods-core.jar, SHA-256 324091f9..., 22 tests green, rebuilt from clean to the same hash); no BLUETOOTH_PRIVILEGED, no network permission. Not compiled: the single rebuild follows all planned work.
The PRODUCT_PACKAGES patch is landed as commit 4438b3d305f7 on vendor/adevtool branch sovereignos-airpods-identity (package patch vendor-adevtool/0001), and the package is deployed to the build server as vendor/sovereignos/airpods (owner-run, commit c61330f; 9 of 9 files sha256-identical to sovereignos-platform airpods/, jar 324091f9...).
Open: the runtime grant of BLUETOOTH_CONNECT, and AIR-022 (the exemption works for the constructor, and an unexempted app is still blocked).
4Review when
If AIR-022 shows the exemption is not enough, or a needed API turns out not to be @SystemApi; a rebase that moves the sysconfig hidden-API path; any proposal to add a permission beyond BLUETOOTH_CONNECT and MANAGE_AIRPODS_IDENTITY.
Read from docs/governance/decision-log.md, entry ADR-118.