Tracker: ROM compatibility for advanced AirPods features (L2CAP)

CAPod can now talk to AirPods on a deeper level than regular Bluetooth scanning — that's what powers things like changing the noise control mode, customising press controls, and reading extra device info directly from the earbuds.

Under the hood this needs a specific kind of Bluetooth connection called L2CAP. The long technical story is in #215.

**The short version: the fix that makes this connection work reliably with AirPods isn't present on every Android build. Whether it works on your phone depends on your manufacturer, ROM and Android version — some devices work out of the box, others never manage to connect.**

This issue is a place to collect reports from the community so we can build a public picture of which phones / ROMs / Android versions are known to work, and which aren't.

> Google confirmed on issuetracker #371713238 that the fix landed in AOSP's Bluetooth stack in the March 2026 release. Pixels were the first to ship it (in the April 2026 security update on stable A16, and the A17 beta). Other OEMs pick it up whenever they rebase.

Known ROMs that include the L2CAP Bluetooth socket fix:

* **Google Pixel**
* Android 16, since April 2026 update (`QPR3`)
* Android 17, since beta 3+ (`CP21.260306.017`) — mixed reports on the A17 beta track, CAPod confirmation welcome
* **OnePlus — OxygenOS 16** — reportedly includes the fix; community reports are mixed, CAPod confirmation welcome
* **Oppo / Realme — ColorOS 16** — reportedly includes the fix; community reports are mixed, CAPod confirmation welcome

No files, tests, or entry points are identified. Start by reading the linked technical background in #215 and checking the device, ROM, and Android-version reports described here; done means adding a reproducible compatibility report that clearly confirms whether CAPod's AirPods L2CAP connection works.

Written by the indexing model from the issue text.