-
-
Notifications
You must be signed in to change notification settings - Fork 153
Request for official connection method #589
Copy link
Copy link
Open
Labels
coms/AAPUses Apples AirPod Protocol. Requires Android ROM with fixed L2CAP support on the Bluetooth sockets.Uses Apples AirPod Protocol. Requires Android ROM with fixed L2CAP support on the Bluetooth sockets.enhancementAdd a new feature of improve an existing featureAdd a new feature of improve an existing feature
Metadata
Metadata
Assignees
Labels
coms/AAPUses Apples AirPod Protocol. Requires Android ROM with fixed L2CAP support on the Bluetooth sockets.Uses Apples AirPod Protocol. Requires Android ROM with fixed L2CAP support on the Bluetooth sockets.enhancementAdd a new feature of improve an existing featureAdd a new feature of improve an existing feature
Type
Fields
Give feedbackNo fields configured for issues without a type.
TL;DR
CAPod uses an unofficial workaround to talk to AirPods. It could break with any future Android update, and there's nothing we can do about it on our side.
We've filed a request asking Google to add an official Android API: https://issuetracker.google.com/issues/510252114
You can help us push Google to fix this.
How to help (30 seconds)
That's it. The more +1s the ticket gets, the more likely Google will prioritize the work.
Only the +1 button counts as a vote. Extra comments add noise and can get the ticket muted.
What's actually broken (optional reading)
AirPods talk to your phone over a specific Bluetooth feature called BR/EDR L2CAP. Android supports this feature internally, but doesn't give apps an official API to use it.
CAPod accesses the hidden internal method through reflection plus a runtime workaround. It works today, but it's fragile by design — Google can change the internals at any time.
Google already fixed the underlying transport bug. We're now asking them to add the missing public API so apps like CAPod can stop relying on the hack.