react-native-webrtc / react-native-webrtc/react-native-callkeep
Audio routing to bluetooth headset with setAudioRoute doesn't work on OnePlus devices
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 511
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 2
Description
Bug report
-
I've checked the example to reproduce the issue.
-
Reproduced on:
-
Android
-
iOS
Description
Hi,
I've been working on a voice call app for 2 years now. I received a bug report from one of our testers which setAudioRoute doesn't work on OnePlus devices for bluetooth routing. Then I tested and observed that it indeed doesn't work. Routing to speaker and earpiece works perfect though. Only for bluetooth.
I've been struggling this issue for a month now. No visible indication, error or debug log. Nothing. It just doesn't turn on bluetooth headset. I tried different headsets and none of them worked.
This functionality works just fine on other brands as far as I tested. Did anyone face this issue before ?
Steps to Reproduce
- Start a call/answer a call
- Try to route audio to bluetooth headset with setAudioRoute
Versions
- Callkeep: 4.3.3
- React Native: 0.69.5
- iOS: N/A
- Android: 12
- Phone model: OnePlus Nord 2T
Logs
No logs available
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 example linked in the issue and reproduce setAudioRoute on Android 12 using a OnePlus Nord 2T and Bluetooth headset. Compare the Bluetooth path with the working speaker and earpiece routes; done means Bluetooth routing succeeds on the reported device and the behavior is covered by useful diagnostics or a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100