New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 773345 link

Starred by 5 users
Status: Duplicate
Merged: issue 761336
Owner: ----
Closed: Nov 2017
Cc:
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
█ mflodman@webrtc.org
ligim...@chromium.org
█ msrchandra@chromium.org
mflodman@chromium.org
sprang@chromium.org
brandtr@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Android WebView fails to decode h264 encoded WebRTC video/audio stream from iOS 11

Reported by ruebsame...@gmail.com, Oct 10 2017 
Steps to reproduce the problem:
1. Initiate a WebRTC video connection between Android WebView and iOS 11.0.2 Safari 11

What is the expected behavior?
Video and Audio streams on both ends (ie. Android & iOS 11 device)

What went wrong?
The iOS 11 device is able to decode incoming video and Audio from Android; however, the opposite is not true:  The Android device is unable to decode audio/video from the iOS source (encoded h264).

Relevant error from attached log: 

E/chromium: [ERROR:internaldecoderfactory.cc(71)] Unable to create an H.264 decoder fallback. Decoding of this stream will be broken.

I've verified the Webview is able to stream and auto play h264 embedded videos.  

Furthermore, the output from createOffer() for the webView shows support for h264:

a=rtpmap:96 VP8/90000
a=rtpmap:98 VP9/90000
a=rtpmap:127 H264/90000

Did this work before? No 

Chrome version: 61.0.3163.98  Channel: stable
OS Version: 61.0.3163.98
Flash Version:
logcat.txt
40.8 KB View Download

Comment 1 by ruebsame...@gmail.com, Oct 10 2017 

Able to reproduce this bug using h264 loopback on Android WebView:
https://appr.tc/r/7476647479?vrc=H264&debug=loopback&vsc=H264

On Android Webview, received video and audio are not decoded.


Trying the same URL on Android Chrome results in different behavior:
* First frame of video is decoded and then freezes
* Audio seems to be decoded properly.

Comment 2 by ligim...@chromium.org, Oct 10 2017

Components: -Blink Mobile>WebView Blink>WebRTC

Comment 3 by guidou@chromium.org, Oct 11 2017

Components: -Blink>WebRTC Blink>WebRTC>Video

Comment 4 by sandeepkumars@chromium.org, Oct 11 2017

Cc: msrchandra@chromium.org sandeepk...@techmahindra.com nyerramilli@chromium.org ligim...@chromium.org
Labels: Needs-triage-Mobile WV-Triaged M-63
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue. Observed the video is getting stuck and the audio is fine

Steps Followed:
1. Launched Chrome in Android
2. initiated a webrtc call from appr.tc
3. connected to same room using safari in iPhone  
4. Observed the video is getting stuck and the audio is fine
5. Observed that safari didn't trigger either video or audio.

Chrome versions tested:
61.0.3163.98, 63.0.3236.6

OS
Android 8.0.0, iPhone 7+ 11.0.2

Android Devices
8.0.0 Pixel Build/OPR1 170623.027

Somehow observed same behavior in older builds as well. Untriaged for further input's on this issue. 

Thanks!!

Comment 5 by sandeepkumars@chromium.org, Oct 12 2017

Cc: -sandeepk...@techmahindra.com sandeepkumars@chromium.org

Comment 6 by tobiasjs@chromium.org, Oct 12 2017 

webrtc.gni contains

rtc_use_h264 = proprietary_codecs && !is_android && !is_ios

So I guess h264 is disabled for webrtc on android regardless of whether webview/chrome has support for it?

Comment 7 by tobiasjs@chromium.org, Oct 12 2017

Cc: mflodman@webrtc.org

Comment 8 by brandtr@chromium.org, Oct 16 2017 

tobiasjs: H.264 is enabled if there is HW encode/decode support. I believe that the |rtc_use_h264| build flag only applies to the SW encode/decode support, which is not available on mobile devices.

Comment 9 by brandtr@chromium.org, Oct 16 2017 

This may be a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=761336. Do you have the SDPs for local and remote?

Comment 10 by ctzsm@chromium.org, Oct 19 2017

Labels: Needs-Feedback
ruebsamen.gene@, please see the question in #9

Comment 11 by holmer@chromium.org, Nov 15 2017

Mergedinto: 761336
Status: Duplicate (was: Untriaged)
I'll assume this is a dupe of 761336 which has been fixed. Feel free to reopen if that's not the case.
►

Sign in to add a comment