We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
in my project, and also when trying the live-demo, the "environment" cameras will just give a black screen on Samsung Note 10+ and S20 Ultra.
The front facing cameras works, but when switching to the environment cameras the screen goes black. None of the environment cameras work.
Under messages in the live demo, it only says: { "messages": "Could not start video source", "mediaStreamError": {} }
I have tested both with Samsung Note 10+ and S20 Ultra. It works fine on "normal" s20 model.
Android version 11.
I have tested with both Edge (v 46.03.4.5155) and Chrome (v 83.0.4103.106) browser.
Does anyone know what causes this or has any workarounds?
The text was updated successfully, but these errors were encountered:
Hi @angroPowel, does this issue still happen with the latest version of this library (0.4.1)?
Sorry, something went wrong.
Hi, I'm also experiencing this behavior on a Samsung Galaxy Tab A with the lib lastest version (0.4.1) Does anyone have a fix for it?
I'm also facing camera issue in samsung mobile and motorola device
No branches or pull requests
Hi,
in my project, and also when trying the live-demo, the "environment" cameras will just give a black screen on Samsung Note 10+ and S20 Ultra.
The front facing cameras works, but when switching to the environment cameras the screen goes black. None of the environment cameras work.
Under messages in the live demo, it only says:
{ "messages": "Could not start video source", "mediaStreamError": {} }
I have tested both with Samsung Note 10+ and S20 Ultra. It works fine on "normal" s20 model.
Android version 11.
I have tested with both Edge (v 46.03.4.5155) and Chrome (v 83.0.4103.106) browser.
Does anyone know what causes this or has any workarounds?
The text was updated successfully, but these errors were encountered: