librepods-org / librepods-org/librepods
Oppo Find X9 initial handshake not happening
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
App version
v0.2.9
App source
Play
Device
Oppo Find X9
Android / OS version
ColorOS 16.0.9
Root / hook method
No root (native L2CAP support)
AirPods model
AirPods Pro 2 (USB-C)
AirPods firmware
No response
What happened
Initial handshake not happening. The app says AirPods not connected. Airpods shows up in Bluetooth section and works normally.
Logs
No response
Additional context
Tried many things as suggested in the readme and the issues sections. Tried to play music and then connect. Granted Nearby Devices and Bluetooth access, enabled Notifications in the system settings, allowed Battery Background Activity, toggled on High Background Power Consumption, allowed the app to Display Over Other Apps, unpaired and forgot the AirPods in Bluetooth settings, cleared cache and data for the LibrePods app, used the Quick Settings Bluetooth toggle trick, tried the reversed launch order with music playing, reset all network and Bluetooth settings on the phone and rebooted your Oppo Find X9 multiple times.
Nothing has worked. Kindly suggest any help.
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
The issue names no source file, test, or entry point. Begin by reproducing the initial-handshake failure on an Oppo Find X9 with ColorOS 16.0.9 and collect the missing logs; done means the cause is identified and the AirPods connect through the initial handshake on this device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100