[webcontent] Camera switching bug when remembering decision for site still
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
People
(Reporter: jib, Assigned: jib)
References
Details
Attachments
(1 file, 1 obsolete file)
+++ This bug was initially created as a clone of Bug #1744807 +++
In bug 1744807 we put in a camera retry attempt 200ms after a certain failure to obtain a camera from Android.
But we have new reports from https://github.com/mozilla-mobile/fenix/issues/22704#issuecomment-1350822362 that this was insufficient, and that at least on Samsung s21 and s22 devices, it may be necessary to wait up to 450 ms sometimes to keep the phones from failing to obtain a camera when switching back and forth between front and back camera.
STRs:
- See bug 1744807 comment 0, or
- use https://jsfiddle.net/jib1/fsexmu8v/show to flip back and forth (check
☑ Remember this decision
)
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:jib, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•2 years ago
|
Hi,
while trying to use some older and/or lower end Android devices, I noticed that even 450ms delay is not sufficient.
You can reproduce this issue even on WebRTC samples page:
- Trying to change sources rapidly in this sample: https://webrtc.github.io/samples/src/content/devices/input-output/ until the camera stream freezes
- Then, trying to initialise camera here: https://webrtc.github.io/samples/src/content/getusermedia/gum/ should invoke an
AbortError
I, personally, have tried it with devices: Redmi Note 7, Huawei P10 Lite - the latter one being so power limited, that 450ms delay was not enough most of the time.
I hope this information might help you somehow with progress of fixing this issue.
Thanks, have a nice day :)
Updated•8 months ago
|
Description
•