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

Issue 777896 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
braveyao@chromium.org
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
ligim...@chromium.org
█ msrchandra@chromium.org
chfremer@chromium.org
guidou@chromium.org
niklase@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

WebRTC doesn't access camera

Reported by anthony....@gmail.com, Oct 24 2017 
Steps to reproduce the problem:
1. Open Chrome 
2. Goto Appr.tc
3. Join Room

What is the expected behavior?
You should be able to see your self

What went wrong?
Failed to Get access to local media error, Err name was NotReadableError

Can't see your self 

Did this work before? Yes 50 something

Does this work in other browsers? N/A

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 6.0.1
Flash Version: 

The Betas, dev, can seem to work but when they get pushed to stable they stop working. (Gmail also doesnt work)

I've been working on this for a while now, see bug  Issue 716070  for some more details

Comment 1 by sandeepkumars@chromium.org, Oct 25 2017

Cc: msrchandra@chromium.org nyerramilli@chromium.org ligim...@chromium.org sandeepkumars@chromium.org
Labels: -Pri-2 hasbisect-per-revision M-61 Needs-triage-Mobile Triaged-Mobile Pri-1
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue in Android. Observed the Video is not working, getting local media error.

Steps Followed:
1. Launched Browser
2. Navigated to appr.tc
3. Observed the Video is not working.

Chrome versions tested:
61.0.3163.98

OS
Android 6.0.1

Android Devices 
6.0.1: SM-J710F Build/MMB29K

Below is the bisect info
=======================

Chrome Good Build -- 62.0.3164.0
Chrome Bad Build  -- 61.0.3163.0

https://chromium.googlesource.com/chromium/src/+log/61.0.3163.0..62.0.3164.0?pretty=fuller&n=10000

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

Unable to find the suspect from above Log. Could someone from Blink>WebRTC team look into this issue.

Please navigate to below link for log's and video--
go/chrome-androidlogs/777896

Note:
1. Issue is not seen in latest Stable, Beta, Dev and Canary as well.
2. Issue is not seen using #61.0.3163.98 on Samsung S6 with 6.0.1 
3. Issue is not seen in 7.1.2 Pixel XL Build/N2G48E, 8.0.0 Pixel Build/OPR1 170623.027, 5.0.0:; Micromax A106 Build?LRX21M, 

Thanks!!

Comment 2 by guidou@chromium.org, Oct 26 2017

Cc: chfremer@chromium.org
Components: -Blink>WebRTC Blink>GetUserMedia>Webcam
So, it seems the issue is fixed in 62?
chfremer@: could this be related to the new utility process for video capture?

Comment 3 by chfremer@chromium.org, Oct 26 2017

Cc: braveyao@chromium.org
The video capture service is currently only active for Windows, Mac, and Linux. Android  is still using the same old video capture path, so should not be related.

braveyao@: Do we have or can we get this device for repro?

Comment 4 by guidou@chromium.org, Oct 26 2017 

This bug sounds similar to  bug 777548 , which is apparently fixed in 62.

Comment 5 by braveyao@chromium.org, Oct 26 2017 

The interesting comments in original report:
"The Betas, dev, can seem to work but when they get pushed to stable they stop working".   Issue 716070  has more details.

sandeepkumars@, could you please verify it again when M62 is in stable?

anthony.selby@, what's your device? any replication on device other than HUAWEI? like Samsung, Nexus.

Comment 6 by ligim...@chromium.org, Oct 27 2017 

Sandeep, please verify.

Comment 7 by sandeepkumars@chromium.org, Oct 30 2017 

Re-tested the issue using 62.0.3202.73 on Android 6.0.1: SM-J710F Build/MMB29K and could not reproduce the issue. (Observed WebRTC accessing the video without any issues).

Thanks!!

Comment 8 by niklase@chromium.org, Nov 2 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment