Defer WebRTC audio mode setup to prevent resource locking on app start#24
Conversation
This change prevents the app from switching to `MODE_IN_COMMUNICATION` immediately upon startup. The audio mode switch and focus request are now handled in `setupAudioForCall()`, which is called only when a call is started or answered. This resolves issues where the earpiece was active and the camera was blocked on some devices (e.g., Samsung J2) when the app was just open but not in a call. Co-authored-by: DivyanshuChipa <211708943+DivyanshuChipa@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
DivyanshuChipa
deleted the
fix-webrtc-audio-mode-15588707003704709131
branch
1 participant
Moved
audioManager.mode = MODE_IN_COMMUNICATIONfrominitWebRTCto a newsetupAudioForCallmethod, invoked only during active calls. This prevents premature audio routing and resource locking.PR created automatically by Jules for task 15588707003704709131 started by @DivyanshuChipa