Issue metadata
Sign in to add a comment
|
Audio mode still using Voice stream even after ending webrtc Call.
Reported by
mr.shyam...@gmail.com,
Oct 3 2016
|
||||||||||||||||||||||||
Issue description
Example URL:
Steps to reproduce the problem:
1. Do getusermedia
2. add local stream to peerconnection
3. start a webrtc call
4. try to change call voice, showing voice stream is updating.
5. end call
While on end call
- remove the stream from peerconnection
- release the track from the local stream.
tracks[0].stop()
6. Now try to change the volume, still its showing voice stream.
What is the expected behavior?
After webrtc Call, when trying to reduce the volume, using volume button, it should show default ringer volume changing.
What went wrong?
Device is still showing Call Volume change instead of changing Ringer volume change.
Did this work before? N/A
Is it a problem with Flash or HTML5? HTML5
Does this work in other browsers? N/A
Chrome version: 53.0.2785.116 Channel: stable
OS Version: 6.0.1
Flash Version:
Tested this in Galaxy s5 active, Samsung J3
Same behavior observed in 54 beta.
,
Oct 3 2016
,
Oct 5 2016
braveyao@ could you take a look at this? IMHO I think the volume buttons should change to system/media volume after the mediaStream has been stopped.
,
Oct 5 2016
This works as intended so far. An ended track is still a track, which means if the user adds it to the peerconnection, he would expect it to be treated the same as any other track added to the peerconnection. It also means the audio input stream won't be stopped and audio mode won't be changed back. https://cs.chromium.org/chromium/src/media/audio/android/audio_manager_android.cc?q=audio_manager_android.cc&sq=package:chromium&dr&l=201. + hta@ & henrika@ for more comments.
,
Oct 6 2016
,
Oct 6 2016
First of all, there is a known issue in https://bugs.chromium.org/p/chromium/issues/detail?id=650533 related to volume changes in Chrome on Android that can be related. Not an identical problem but I am inclined to mark this one as a duplicate. Even with the issue in 650533 resolve, it is very difficult to make a perfect solution in Chrome on Android since it is not clear when an audio session has ended. Also, Android does not allow separate settings per stream, hence if a page uses both WebRTC and HTML5, it is not clear what is the most appropriate mode. IMHO, to get a total control of all parts like device selection, audio focus, volume etc. a standalone WebRTC application is most likely needed. Things can always be improved in Chrome on Android but there will always be corner cases that don't work as expected.
,
Oct 6 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Oct 3 2016