Issue metadata
Sign in to add a comment
|
WebRTC - Can't access back (rear/environment) camera
Reported by
pymous.s...@gmail.com,
Sep 28 2017
|
||||||||||||||||||||||
Issue descriptionExample URL: https://webrtc.github.io/samples/src/content/devices/input-output/ Steps to reproduce the problem: 1. Go to the provided URL ( https://webrtc.github.io/samples/src/content/devices/input-output/ ) 2. In the select "Video Source" choose "camera2 0, facing back" 3. If you see a black screen, you reproduced the issue. What is the expected behavior? The expected behavior is being able to get the Back camera video stream What went wrong? The back camera seems to be unaccessible from Chrome since the latest update (2 days ago, 09/26). You can't access it either by deviceID or using the following constraint : facingMode: "environment". Both were working before. Did this work before? Yes Before the upgrade 2 days ago (09/26) Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 61.0.3163.98 Channel: stable OS Version: 6.0 Flash Version: Contents of chrome://gpu:
,
Sep 29 2017
Tested the issue on Chrome Stable# 61.0.3163.98 and Chrome Canary# 63.0.3226.0 using Pixel (Android 8.0.0 / OPR1.170623.027) and Pixel XL (Android 7.1.2 / N2G48E) and was able to reproduce the issue. Noticing Black screen when the Camera is toggled between front and rear. This is a Non-Regression issue seen from M58# 55.0.2883.91. Please find the logs and screen cast in the below URL -- go/chrome-androidlogs/769721 Thank You.
,
Sep 29 2017
Thanks. I know this isn't a support platform, but this bug is critical to our application, do you know a way to downgrade the actual version of Chrome ? To get our application working again, at least on our test devices ?
,
Oct 2 2017
,
Oct 3 2017
pymous.studio@: I haven't checked, but maybe the sample is not stopping the original video track after switching the camera. It is known that many devices (including the Pixel XL) cannot have both cameras open at the same time, so you have to stop the track with the first camera before opening a new track with the second camera. See the discussion in bug 746534 and bug 750701 .
,
Oct 3 2017
Hi Guidou. The usecase you're describing would be consistant if you switch from one camera to another, yes, but sadly, using only constraints (facingMode) for the read camera doesn't work either. With facingMode : "environment", the first stream should be the rear video (and was before the update), but it's the user camera.
,
Oct 4 2017
Can you provide a simple snippet (jsfiddle or similar) that reproduces the problem and indicate which combinations of chrome version and device models reproduce it?
,
Oct 4 2017
,
Oct 5 2017
It seems that the issue is actually related to WebRTC Adapter.JS. My minimal snippet works without it on Chrome, sorry for the false alert.
,
Oct 31 2017
Closing as per comment #9 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Sep 28 2017