-
Notifications
You must be signed in to change notification settings - Fork 74.1k
New issue
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
Why using Camera2 API for Android Tensorflow Lite Demo? #22620
Comments
Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks. |
@shashishekhar so you have any insight on this? I suspect we just used the new API arbitrarily. |
The main issue with Camera2 API that I can't set Full HD resolution for preview (1920x1080), though it can be done with Legacy Camera API (TextureView can be set maximum to 1440x1080) Proofs: googlearchive/android-Camera2Basic#123 I tried some Xiaomi devices and some users reported this problem on Samsung devices (see stackoverflow links) and some others Seems many phone manufactures (Samsung, Xiaomi, Sony and so on) didn't care about Camera2 that much |
@anonym24 : Thank you for the links. This seems like a bad implementation on some particular manufacturers. I hope in future the manufacturers will fix these bugs. Most of our samples are forward looking so we want to support Camera 2 API, rather than Camera 1. This is certainly not a problem with AOSP. I agree for production use cases, you may have to do workarounds against bugs and may need to use Camera 1 API for your use case. |
Many manufactures didn't implemented Camera2 that well googlearchive/android-Camera2Basic#123
So it's better to use legacy Camera API even for Android API >= 25
The text was updated successfully, but these errors were encountered: