react-native-webrtc / react-native-webrtc/react-native-incall-manager
setSpeakerPhoneOn not working for incoming call Android
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
When il make incoming call and accept . il try setSpeakerPhoneOn but its not working.
But for outgoing call its working. I use sip js react-native webrtc and react native incall manager.
const onAccepted = (data: any) => {
if (data && data.route === 'incoming') {
setCallActive(true);
setIsCalling(false);
InCallManager.start({media: 'audio'});
RNCallKeep.setCurrentCallActive(currentCallUUID);
} else if (data && data.route === 'outgoing') {
RNCallKeep.setCurrentCallActive(currentCallUUID);
setIsCalling(false);
InCallManager.stopRingback();
}
}
const handleSpeaker = (isSpeaker: boolean) => {
InCallManager.setSpeakerphoneOn(isSpeaker);
}
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 handling behind InCallManager.setSpeakerphoneOn and compare its behavior after the onAccepted incoming and outgoing branches shown in the report. Reproduce an accepted incoming call with the provided handleSpeaker flow; done means speakerphone routing works for incoming calls as it does for outgoing calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native, typescript
- 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
- 25/100