react-native-webrtc / react-native-webrtc/react-native-incall-manager
chooseAudioRoute seems not detecting the bluetooth connected to the phone.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
The audio is not routed to the Bluetooth device even using chooseAudioRoute('BLUETOOTH') seems like it is not being detected.
I tried to change the parameter to 'EARPIECE' to see the result and check for the available device list and yeah no Bluetooth there:
{"availableAudioDeviceList": "[\"SPEAKER_PHONE\",\"EARPIECE\"]", "selectedAudioDevice": "EARPIECE"}
I tried not to call the InCallManager.start() then the phone routed the audio to the Bluetooth, but is used like this the routing back to speaker phone and earpiece will not be working.
I tested this on Samsung S22.
Anyidea why?
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 at the chooseAudioRoute('BLUETOOTH') and InCallManager.start() entry points, then reproduce the reported behavior on a Samsung S22. Compare the availableAudioDeviceList and selectedAudioDevice values with InCallManager.start() enabled and disabled; done means Bluetooth is detected and selected while speakerphone and earpiece routing still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100