librepods-org / librepods-org/librepods
L2CAP Connection Fails on Fairphone 5 with Both Xposed and Magisk Methods
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
quite a similar bug report as #229 but with a different hardware (Fairphone FP5 / AirPods Pro 3) / software (Android 13).
No L2CAP connection available.
Device Information:
- Device: Fairphone FP5 / arm64-v8a
- Android Version: 13 (API 33) (TQ3A.230901.001 / 3.1.4-t-20250915526530-official-FP5)
- Root: Magisk
- Magisk Version 29.0
- Xposed Framework: Zygisk - LSPosed (v1.9.2 7024)
- LibrePods v0.2.0-alpha
Description: The LibrePods app is unable to establish an L2CAP connection to my AirPods Pro 3 on my Fairphone FP5, despite trying both the recommended Xposed and Magisk module methods. The symptoms are slightly different depending on the method used.
Tests :
- Method 1: Xposed Hook (Recommended):
- Zygisk - LSPosed correctly detected the LibrePods 0.2.0-alpha module which was activated.
- Reset Hook:
- correctly reset Xposed Module
- correctly toggled Bluetooth
- troubleshoot connection
- The logcat shows
L2CAP Registered service classic PSM: 0x1001thenFailed to set metadata for key xxxx-java.lang.SecurityException: ... has no android.permission.BLUETOOTH_PRIVILEGED - Logs: airpods_log_20251020_144623.txt
- Method 2:
btl2capfixMagisk Module:
- I disabled the Xposed module and installed the
btl2capfix(from v0.0.3-hotfix) Magisk module instead. - Result: Same issue and same symptoms.
- Logs: airpods_log_20251020_145419.txt
Let me know what kind of further tests I should made to qualify the issue.
At the moment, lacking a working platform, I don't know exactly what are the markers for success and progression but if you share your troubleshooting methodology I'll certainly be able to help pinpointing the issue.
Thanks for your time and investment on this project.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached airpods_log_20251020_144623.txt and airpods_log_20251020_145419.txt, focusing on the L2CAP registration and BLUETOOTH_PRIVILEGED SecurityException. Compare the Xposed and btl2capfix results on the Fairphone FP5, then establish reproducible success criteria for an L2CAP connection before investigating a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100