react-native-webrtc / react-native-webrtc/react-native-incall-manager
When a user connects to our application if they are on headphones it doesn't connect to their headphones
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
Is there a method that is exposed that allows us to perhaps add a button to choose which device they want to connect to or, is there a way to check and see if the user is connected to bluetooth. Currently working on a fix, but just seeing if this is a known issue, or if there is a simpler fix.
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 reviewing the existing media-route, sensor, and event handling exposed by react-native-incall-manager. Compare the current connection behavior for headphone and Bluetooth routes, then define completion as reliably connecting to the intended headphone device or clearly exposing the available route for selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100