react-native-webrtc / react-native-webrtc/react-native-incall-manager
Galaxy buds bluetooth does not connect in middle of VOIP (Android)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
HI I have a question regarding trying to connect galaxy buds in middle of a voip call.
I did some logging and it seems to disconnect the Bluetooth audio SCO if the bluetooth is paired in middle of a voip call.
However for an apple air pod, it seems to work just fine.
I found the code where it seems to disconnect the SCO Audio, and I was wondering what the purpose of the code below is and if what possible errors can occur when removing bluetoothManager.stopScoAudio()?
*Update: bluetoothManager.stopScoAudio()? does not seem to disconnect bluetooth audio SCO,
Is there any way to keep the bluetooth audio SCO connected?
Any help would be greatly appreciated!
// --- stop bluetooth if needed
if (selectedAudioDevice == AudioDevice.BLUETOOTH
&& newAudioDevice != AudioDevice.BLUETOOTH
&& (bluetoothManager.getState() == AppRTCBluetoothManager.State.SCO_CONNECTED
|| bluetoothManager.getState() == AppRTCBluetoothManager.State.SCO_CONNECTING)
) {
bluetoothManager.stopScoAudio(); // SEEMS TO DISCONNECT SCO AUDIO HERE
bluetoothManager.updateDevice();
}
Galaxy Buds pairing log

Airpod pairing log

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 by locating the Android code containing stopScoAudio() and updateDevice(), then compare the Galaxy Buds and AirPods pairing behavior described in the issue. Reproduce pairing during an active VOIP call and determine whether the SCO route should remain connected; the issue is done only when the intended behavior and a verified change are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- audio-video-rtc, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100