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

Issue metadata

Status: Duplicate
Merged: issue 769148
Closed: Oct 2017
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression

Sign in to add a comment

Issue 770560: webrtc video no longer showing

Reported by, Oct 1 2017

Issue description

Example URL:

Steps to reproduce the problem:
1. visit
2. press '+'
3. accept the default family name
4. Send the invitation link to an Android device with Chrome 61 installed.
5. Accept the link on the Android device (open & press accept)
6. On the first device - press 'Baby' and then 'START' - make sure camera is enabled.
7. On the Android phone press 'Parent' and then 'Connect'.

What is the expected behavior?
You should see the transmitted video and a volume bar showing the actual volume on the Android phone.

What went wrong?
From Chrome 61 on (only on Android) all you get is a black screen where the video should be, the volume bar is there but does not show anything. Sound works.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? Yes Chrome 60

Does this work in other browsers? N/A

Chrome version: 61.0.3163.9  Channel: stable
OS Version: 7.0.0
Flash Version:
34.5 KB View Download

Comment 1 by, Oct 1 2017

This somehow got lost: It does work in other browsers. Firefox mobile works just fine!

Comment 2 by, Oct 1 2017

I forgot: The bug also does not get triggered when you have a USB debugging session open. In this case it also works just fine.

Comment 3 by, Oct 3 2017

Components: Blink>WebRTC>Video
Labels: -Pri-2 -Type-Compat hasbisect-per-revision M-63 Needs-triage-Mobile Triaged-Mobile Pri-1 Type-Bug-Regression
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue in Android. observed the black screen.

Chrome versions tested
61.0.3163.98, 63.0.3226.0

Android 7.1.2, 6.0.1

Android Devices
7.1.2 Pixel XL Build/N2G48E, 6.0.1: SM-J710F Build/MMB29K,

Below is the bisect info

Chrome Good Build -- 61.0.3142.0
Chrome Bad Build  -- 61.0.3143.0

Results from pre revision bisect --
You are looking for a change made after 482822(GOOD), but before 482823(BAD).

From the above revision range suspecting the following --

@liberato -- Could you please look into the issue, kindly re-assign if this is not related to your changes.

1. Issue is seen in M63 as well.
2. Issue is not seen using #61.0.3163.100, #63.0.3226.0 on Linux Ubuntu 14.04, Mac 10.12.6, Win 10.


Comment 4 by, Oct 3 2017

Labels: -M-63 ReleaseBlock-Stable M-62
Regressed in 61, but its good to have a fix for M62. Tagging accordingly, update if needed.

Comment 5 by, Oct 6 2017

liberato@, any update here?  Please note that M62 Stable release is VERY SOON.

If you don't feel this is blocking, please remove the label.

Comment 6 by, Oct 6 2017

Please don't just remove the label - this is really bad for us and our users, so a fast fix would be highly appreciated. Thank you!

Comment 7 by, Oct 6 2017

Status: Started (was: Assigned)
i think this is fixed.  didn't notice that this one was separate from the other bugs, which were all dup'd together.

fix is here: with a a merge request to 62 already.

i'll verify this use-case then dup this into that.

Comment 8 by, Oct 6 2017

i'm unable to get ToT working for unrelated reasons (gpu channel hang at startup).  if anybody could try to repro this @ToT, i'd appreciate it.  i suspect that it works now, but it'd be nice to confirm.

in the interim, i'll try to find something earlier than ToT that works.

Comment 9 by, Oct 6 2017

Mergedinto: 769148
Status: Duplicate (was: Started)
okay, got it.  it does work @ToT on my 5X.

Comment 10 by, Oct 6 2017

Awesome! Many, many thanks!

Sign in to add a comment