[Chrome][M56][Android7.0] It fails to play video content during call
Reported by
seiyon.p...@gmail.com,
Mar 21 2017
|
|||||||
Issue descriptionExample URL: Steps to reproduce the problem: 1. Precondition - it's only reproducible under Sprint VoLTE network 2. VoLTE call received 3. Call accepted 4. Go to home screen > Launch Chrome during call 5. Open YouTube.com > Play any contents during call What is the expected behavior? User can play contents during call What went wrong? User can't play content during call. Did this work before? N/A Is it a problem with Flash or HTML5? N/A Does this work in other browsers? Yes Chrome version: 56.0.2924.87 Channel: stable OS Version: 7.0 Flash Version: Contents of chrome://gpu: User can play content on Firefox, Dolphin. And could you see the following log in main.log.1? 03-14 13:02:15.165 9622 9747 I LGIMS : TEXT_SIP_START 03-14 13:02:15.165 9622 9747 I LGIMS : 03-14 13:02:15.165 9622 9747 I LGIMS : TIME: Tue Mar 14 13:02:15 2017 03-14 13:02:15.165 9622 9747 I LGIMS : <<<==SEND:1752:TCP:2600:0:c082:600f:10:200:48:173:5060== 03-14 13:02:15.165 9622 9747 I LGIMS : 03-14 13:02:15.165 9622 9747 I LGIMS : INVITE sip:6265008551@ims.spcsdns.net;user=phone SIP/2.0
,
Mar 21 2017
Does adb mentions a rejected audio focus request?
,
Mar 21 2017
I see the following adb logs multiple times (I guess the reporter is trying to play the video multiple times but failed) 03-14 13:03:26.431 31246 31246 V AudioManager: requestAudioFocus() durationHint = 1 Request Package = com.android.chrome 03-14 13:03:26.431 31246 31246 V AudioManager: requestAudioFocus() flags = 0 durationHint = 1 Request Package = com.android.chrome 03-14 13:03:26.431 31246 31246 V AudioManager: requestAudioFocus() flags = 0 durationHint = 1 AudioPolicy = null Request Package = com.android.chrome 03-14 13:03:26.433 1572 17252 I MediaFocusControl: AudioFocus requestAudioFocus() from uid/pid 10127/31246 clientId=android.media.AudioManagerEx@de81c42org.chromium.content.browser.AudioFocusDelegate@17c5453 req=1 flags=0x0 Haven't seen anything unusual yet. However we don't log whether the request is successful or not. So it's probably either an AudioFocus issue or audio routing issue.
,
Mar 23 2017
Appreciated your prompt feedback. But sorry that I can't confirm that it is an audio focus isseu. So I'll take a look and get back to you.
,
Mar 23 2017
,
Apr 10 2017
no response from bug opener for > 2 weeks. resolve as won't fix. seiyon.park@gmail.com,, please reactivate if you have more feedback. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dalecur...@chromium.org
, Mar 21 2017