You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably AE state can be used for this, but that's not available in all devices (legacy devices don't report 3A states at all), so need to consider the UI for those cases as well.
Maybe it's better to handle all these in CameraX, we can probably provide an API which mentions if something like AUTO_SCREEN_FLASH is supported, but not sure how big of a priority this should be. We can start a feature request to CameraX first and discuss further.
The text was updated successfully, but these errors were encountered:
I'll file a FR bug and discuss further at CameraX side.
But I haven't seen any other apps actually doing this, and I suppose this is not too important for JCA too, right?
Meanwhile, JCA probably needs to decide on how to handle different camera requiring/supporting different flash modes (and perhaps the same for other settings as well), i.e. there needs to be a way in JCA to not provide users the option to set auto flash in case of front camera (since it's never guaranteed to be supported). But this comes with problems like what to do if user sets flash auto in rear camera and then changes to front camera.
Switch to flash always on if auto is not supported. But then comes the question of what should happen if user switches back to rear camera.
JCA remembers settings differently for each camera and user needs to explicitly set the setting for each camera. This is what most apps do and seem most reasonable.
Some sort of hybrid of no. 1 and 2.
Do you already have some plans/issues regarding this?
Ah gotcha. Yes we have some in-progress work to add camera "constraints" per-lens (see #168) . We can make sure the front lens only suppors ON and OFF for now.
The simple UX for this would be to change to ON when AUTO was used for the back lens. When switching back, we would just stay using ON. More complicated UX would be to keep track of whatever setting the user last prescribed and switch back to that. So if they switch lenses to the front but never actually explicitly change the flash mode, it would return to whatever they had previously set.
JCA Version: 1.0.0-rc01
Device: Pixel 7 pro
Probably AE state can be used for this, but that's not available in all devices (legacy devices don't report 3A states at all), so need to consider the UI for those cases as well.
Maybe it's better to handle all these in CameraX, we can probably provide an API which mentions if something like AUTO_SCREEN_FLASH is supported, but not sure how big of a priority this should be. We can start a feature request to CameraX first and discuss further.
The text was updated successfully, but these errors were encountered: