ObliviOS Developer portal Project site

Home / Decisions / ADR-106

Approve docs/superpowers/specs/2026-09-28-airpods-compatibility-and-finding-design.md as the accepted AirPods compatibility and finding design, replacing (not…

Accepted, recorded 28 September 2026.

Decision
ADR-106
Date
2026-09-28
Status
AcceptedAccepted
Part
AirPods
Mentions
ADR-097
Mentioned by
ADR-107, ADR-108, ADR-109, ADR-110

1Decision

Approve docs/superpowers/specs/2026-09-28-airpods-compatibility-and-finding-design.md as the accepted AirPods compatibility and finding design, replacing (not archiving; recoverable via git history) the 2026-07-30 design of the same scope.

2Why and evidence

The prior design was stale on branding (30 occurrences of AegisOS, pre-dating ADR-097) and had never resolved how proprietary AirPods control would be reached without root — it left "changing the inherited Bluetooth stack requires a separate security case" as an unfilled placeholder.

This revision reads LibrePods' own Android source directly (not its docs) and finds its root/Xposed dependency is two native hooks in com.android.bluetooth (fake_BTA_DmSetLocalDiRecord, presenting a device-wide Apple vendor ID; fake_l2c_fcr_chk_chan_modes) plus a hidden-API reflection call blocked by ART for ordinary apps.

Because SovereignOS controls its own Bluetooth stack source and its own non-SDK API allowlist, the same functionality is reachable as a bonded-device-scoped source patch plus a service-scoped non-SDK API exemption — never a device-wide identity change, never root, never a general hooking framework.

The revision also closes two open questions the owner raised directly: real out-of-Bluetooth-range Find My location was investigated and found to require storing a real Apple ID session plus emulating Apple device attestation (anisette) against Apple's servers — refused outright as identity fraud, not gated behind future validation, since AGENTS.md and this design's own non-goals already forbid both; head-tracked spatial audio was investigated and found to be an open reverse-engineering gap (LibrePods itself marks it "Unknown" and out of its own scope), not a policy block, so it is kept in scope as an explicitly gated research track with no capability promise until real hardware evidence exists.

3Consequences

Implementation must follow the design's §15 delivery sequence, starting with the accepted decision, capability-boundary, and threat-model updates before any code. docs/security/capability-boundaries.md and docs/security/threat-model.md must be extended with §8/§10 of the design before implementation begins. LibrePods stays a reverse-engineering reference only; its GPL-3.0 code is not approved for direct reuse (design §13).

The scoped Bluetooth-stack patch and non-SDK API exemption (design §6.2) each require their own platform-patch security case, upstream-diff review, rollback plan, and validation record, per this project's existing IPC/HAL change bar — this ADR approves the design's architecture, not a waiver of that review. No implementation plan exists yet.

4Review when

The owner asks to reopen the no-root/no-Xposed invariant itself for this feature (a materially larger, separate decision per the design's own §3.2); the scoped Bluetooth-stack patch's security case is rejected in review and no compliant alternative is found; LibrePods, Apple's documentation, or AOSP's Spatializer/head-tracking APIs change in a way that invalidates §4 of the design; the spatial-audio research track produces or fails to produce real hardware evidence.

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