ObliviOS Developer portal Project site

Home / Decisions / ADR-109

Land Task 3 of docs/superpowers/plans/2026-09-28-airpods-platform-integration.md.

Accepted, recorded 28 September 2026.

Decision
ADR-109
Date
2026-09-28
Status
AcceptedAccepted
Mentions
ADR-106, ADR-107, ADR-108

1Decision

Land Task 3 of docs/superpowers/plans/2026-09-28-airpods-platform-integration.md: the scoped Bluetooth-stack identity patch (design §6.2, corrected per ADR-107/ADR-108) is authored, git am'd onto a real build-server branch, and compile-verified.

2Why and evidence

Authored in a disposable local worktree (sovereignos-platform/.worktrees/airpods-identity-patch/, seeded read-only from packages/modules/Bluetooth at pinned rev 469799157dcd901470465b243f0ccc762de40d36), per sovereignos-platform/AGENTS.md's hard rule. Real branch sovereignos-airpods-identity on the build server, real commit 1102e506bdb774bf2a4ccb24d8057e3e370d6290 (git am applied cleanly, exit 0).

Touches 12 files, all within packages/modules/Bluetooth, zero frameworks/base changes: the new org.sovereignos.permission.MANAGE_AIRPODS_IDENTITY signature\|privileged permission and its AIDL method (ADR-108), a bonded-device guard in AdapterService#setAirPodsIdentity (refuses to register a non-bonded device), the new INTEROP_AIRPODS_IDENTITY native interop feature, and the two scoped hook patches (sdp_dynamic_change_airpods_vendor in sdp_server.cc, called from both process_service_attr_req and process_service_search_attr_req; the l2c_fcr_chk_chan_modes extension in l2c_fcr.cc).

One real defect found and fixed before landing: the first patch attempt failed a real preflight build with a genuine AIDL compiler error (Found invalid character '\' at index 92) — this codebase has no precedent anywhere for embedding a literal, non-android.Manifest.permission string inside a RequiresPermission/JavaPassthrough AIDL annotation, so the annotation was corrected to reference only the real BLUETOOTH_CONNECT constant, with a comment noting the custom permission is enforced at runtime in AdapterServiceBinder (unaffected by this annotation, which is lint/doc-only with no runtime effect).

Compile verification, real evidence: a fully-detached preflight build on the build server (m com.android.bt, sdk_phone64_x86_64-cp2a-userdebug, OUT_DIR=out-preflight, USE_CCACHE=1) — first attempt failed on the AIDL error above (AIRPODS_PREFLIGHT_BUILD_EXIT_CODE:1); after the fix, the branch was reset to the pinned baseline and the corrected patch re-applied (git am exit 0, new commit 1102e506bd), and the rebuilt preflight succeeded: ninja: 1h13m18.17s Build Succeeded: 15425 steps, AIRPODS_PREFLIGHT_BUILD_EXIT_CODE:0.

All warnings in the log are pre-existing telephony/frameworks warnings unrelated to this patch.

3Consequences

Patch committed here as airpods/patches/packages-modules-bluetooth/0001-airpods-scope-Device-ID-vendor-and-L2CAP-mode-to-registered-peers.patch, airpods/SOURCE.md written mirroring guardian/SOURCE.md's format, citing this ADR. Compile verification only — this ADR does not claim AIR-021 (real-hardware, two-peer validation) is satisfied; that requires the owner's physical AirPods and a flashed device, per design §12, and remains open. Tasks 4-6 of the platform-integration plan are unblocked to proceed (Task 4's non-SDK exemption reuses the confirmed-achievable mechanism from ADR-106/Task 2's findings; Task 5/6 depend on this patch's effect, not a compiled interface).

4Review when

Revisit if AIR-021 hardware validation finds the scoped presentation behaves differently from what compile-time review predicted (e.g. the L2CAP basic-mode fallback's real on-wire effect turns out wrong — Finding 3's addendum in the investigation doc already flags this as inherited-but-unconfirmed behavior). If a future Bluetooth-module rebase changes any of the four real hook points this patch touches, the patch needs re-verification against the new pinned revision, not a blind re-apply.

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