react-native-webrtc / react-native-webrtc/react-native-incall-manager
Proximity sensor also stopping after calling stop() method in Samsung S20FE and iPhone
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 597
- Forks
- 201
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 1
Description
Before receiving an incoming call the proximity sensor works fine, e.g., WhatsApp or Signal voice message is loudspeaker in normal mode, and the volume is low when it is in proximity mode. When receiving an incoming WebRTC the start({media: "audio"}) method is called and when the call is over the stop() method is invoked, But after that, the voice message does not play through the loudspeaker in normal mode.
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
Reproduce the flow described in the issue on a Samsung S20FE and iPhone: start({media: "audio"}) for an incoming WebRTC call, then call stop() and play a voice message. Trace the proximity-sensor and loudspeaker/media-route handling around these entry points; done means the voice message returns to loudspeaker mode after the call ends.
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
- 30/100