fix: Fix "Unknown AF/AE/AWB State" error #2592
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
isaaccolson
pushed a commit
to isaaccolson/deliveries-mobile
that referenced
this pull request
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
In Camera2, there's
CaptureResult.CONTROL_AF_STATE(or the respective value for AE and AWB).These are the supported values: https://developer.android.com/reference/android/hardware/camera2/CaptureResult#CONTROL_AF_STATE
For some reason, on a Samsung SM-S901B there is a situation where this value is
101which is none of those enums. WTF?So maybe Samsung has a proprietrary intermediate state which is not exposed to Android. In that case, we just use "UNKNOWN" instead to avoid this error being thrown.,
Changes
Tested on
Related issues