react-native-webrtc / react-native-webrtc/react-native-callkeep
Audio routing on Android is not routing to Speaker
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
When using RNCallKeep.setAudioRoute(systemId, routeName), if routeName is Speaker (or whatever the name of the speaker is from the list from RNCallKeep.getAudioRoutes()) the audio is routed to the Earpiece instead of Speaker.
Logs
selected audio route: Speaker
RNCallKeep didChangeAudioRoute {"callUUID": "47ce4dbb-4dc1-4f27-9165-5afa9eae0a2d", "handle": "909c6991-96c6-4844-a925-accd3a0fdd94", "output": "SPEAKER"}
AudioDeviceManager: _onDeviceChanged
AudioDeviceManager: emit event DeviceChanged
onAudioDeviceChanged currentDevice Earpiece
Versions
- Callkeep: "4.3.12"
- React Native: "0.72.4"
- Android: 11
- Phone model: Google Pixel 2XL
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 Android entry points for RNCallKeep.setAudioRoute and RNCallKeep.getAudioRoutes, then reproduce the issue in the example using the reported Pixel 2XL and Android 11 setup. Compare the selected Speaker route with the didChangeAudioRoute and AudioDeviceManager logs. Done means selecting Speaker produces Speaker output rather than Earpiece.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, react-native
- Domain
- audio-video-rtc, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100