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

Issue 716329 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
guidou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

webrtc resolution settings

Reported by nicholas...@gmail.com, Apr 28 2017 
Device name:

From "Settings > About Chrome"
Application version: 58.0.3029.83
Operating system: Android 7.1.1

URLs (if applicable): https://webrtchacks.github.io/WebRTC-Camera-Resolution/

Steps to reproduce:
(1) select a camera with a maximum resolution higher than 1920x1080 (requires knowledge of the device in question).
(2) Select 'Quick scan'.
(3) Allow media capture when prompted for permission.
(4) Observe the results table.

Expected result:
Higher resolution settings (e.g. 3840x2160) should pass or fail:mismatch in the results table.

Actual result:
High resolution settings fail with ConstraintNotSatisfiedError.

I strongly suspect that line 265 in device_info_linux.cc (https://cs.chromium.org/chromium/src/third_party/webrtc/modules/video_capture/linux/device_info_linux.cc?dr=C&l=265) is to blame.

Given the apparent lack of resolution reporting in V4L2 (looking at the source in the above file indicates that one probes the device with candidate resolutions), this looks like it can only be remedied with adding more magic numbers to the array at line 265. Are there any specific objections to adding the entry for 4K?

Comment 1 by msrchandra@chromium.org, Oct 26 2017

Cc: msrchandra@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org sandeepkumars@chromium.org
Components: Blink>WebRTC
Labels: M-64 Needs-triage-Mobile Triaged-Mobile Type-Bug
Status: Untriaged (was: Unconfirmed)
Tested the issue on Chrome Stable# 61.0.3163.98 / 62.0.3202.66 & Chrome Canary# 64.0.3248.0 on Pixel (Android 8.0.0 / OPR1 170623.027) and Pixel XL (Android 7.1.2 / N2G48E) and was able to reproduce the issue. 
This is a Non-Regression Issue seen from M58# 58.0.3029.125.
Please find the logs in the below URL --
go/chrome-androidlogs/716329

Thank You.

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

More than 1920x1080 does not necessarily mean that it supports 3840x2160.
If 3840x2160 is requested and the camera does not support it, the error is correct.
What is the maximum resolution you get in the "Video Capture" tab of chrome://media-internals?

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

Components: -Blink>WebRTC Blink>GetUserMedia
Labels: Needs-Feedback

Comment 4 by nicholas...@gmail.com, Oct 30 2017 

Media internals reports nothing in Video Capture on Chrome for Android (stable through to Canary - 61 - 64), with camera permissions enabled. Various camera apps on the device (in this case a HTC 10) report 4K UHD (3840x2160) as available (and several 1:1, 4:3 and 16:9 configurations in between).

Comment 5 by nicholas...@gmail.com, Oct 30 2017 

Oops, addendum to the previous comment: camera apps tested were the system Camera app, and Open Camera.

Comment 6 by ligim...@chromium.org, Mar 9 2018

Status: WontFix (was: Untriaged)
***Bulk edit***

Since there is no valid updates, closing for now. Feel free to reopen if needed.
►

Sign in to add a comment