Camera
#include <NdkCameraCaptureSession.h>
#include <NdkCameraDevice.h>
#include <NdkCameraError.h>
#include <NdkCameraManager.h>
#include <NdkCameraMetadata.h>
#include <NdkCameraMetadataTags.h>
#include <NdkCameraWindowType.h>
#include <NdkCaptureRequest.h>
Summary
Typedefs |
|
---|---|
ACameraCaptureFailure
|
typedefstruct ACameraCaptureFailure
Struct to describe a capture failure. |
ACameraCaptureSession
|
typedeftypedef__BEGIN_DECLS struct ACameraCaptureSession
ACameraCaptureSession is an opaque type that manages frame captures of a camera device. |
ACameraCaptureSession_captureCallback_bufferLost)(void *context, ACameraCaptureSession *session, ACaptureRequest *request, ANativeWindow *window, int64_t frameNumber)
|
typedefvoid(*
The definition of camera buffer lost callback. |
ACameraCaptureSession_captureCallback_failed)(void *context, ACameraCaptureSession *session, ACaptureRequest *request, ACameraCaptureFailure *failure)
|
typedefvoid(*
The definition of camera capture failure callback. |
ACameraCaptureSession_captureCallback_result)(void *context, ACameraCaptureSession *session, ACaptureRequest *request, const ACameraMetadata *result)
|
typedefvoid(*
The definition of camera capture progress/result callback. |
ACameraCaptureSession_captureCallback_sequenceAbort)(void *context, ACameraCaptureSession *session, int sequenceId)
|
typedefvoid(*
The definition of camera sequence aborted callback. |
ACameraCaptureSession_captureCallback_sequenceEnd)(void *context, ACameraCaptureSession *session, int sequenceId, int64_t frameNumber)
|
typedefvoid(*
The definition of camera sequence end callback. |
ACameraCaptureSession_captureCallback_start)(void *context, ACameraCaptureSession *session, const ACaptureRequest *request, int64_t timestamp)
|
typedefvoid(*
The definition of camera capture start callback. |
ACameraCaptureSession_captureCallback_startV2)(void *context, ACameraCaptureSession *session, const ACaptureRequest *request, int64_t timestamp, int64_t frameNumber)
|
typedefvoid(*
The definition of camera capture start callback. |
ACameraCaptureSession_captureCallbacks
|
typedef ACaptureCaptureSession_captureCallbacks structure used in ACameraCaptureSession_capture and ACameraCaptureSession_setRepeatingRequest. |
ACameraCaptureSession_captureCallbacksV2
|
typedef This has the same functionality as ACameraCaptureSession_captureCallbacks, with the exception that captureCallback_startV2 callback is used, instead of captureCallback_start, to support retrieving the frame number. |
ACameraCaptureSession_logicalCamera_captureCallback_failed)(void *context, ACameraCaptureSession *session, ACaptureRequest *request, ALogicalCameraCaptureFailure *failure)
|
typedefvoid(*
The definition of logical camera capture failure callback. |
ACameraCaptureSession_logicalCamera_captureCallback_result)(void *context, ACameraCaptureSession *session, ACaptureRequest *request, const ACameraMetadata *result, size_t physicalResultCount, const char **physicalCameraIds, const ACameraMetadata **physicalResults)
|
typedefvoid(*
The definition of final capture result callback with logical multi-camera support. |
ACameraCaptureSession_logicalCamera_captureCallbacks
|
typedef This has the same functionality as ACameraCaptureSession_captureCallbacks, with the exception that an onLogicalCameraCaptureCompleted callback is used, instead of onCaptureCompleted, to support logical multi-camera. |
ACameraCaptureSession_logicalCamera_captureCallbacksV2
|
typedef This has the same functionality as ACameraCaptureSession_logicalCamera_captureCallbacks, with the exception that an captureCallback_startV2 callback is used, instead of captureCallback_start, to support retrieving frame number. |
ACameraCaptureSession_prepareCallback)(void *context, ANativeWindow *window, ACameraCaptureSession *session)
|
typedefvoid(*
The definition of camera capture session onWindowPrepared callback. |
ACameraCaptureSession_stateCallback)(void *context, ACameraCaptureSession *session)
|
typedefvoid(*
The definition of camera capture session state callback. |
ACameraCaptureSession_stateCallbacks
|
typedef Capture session state callbacks used in ACameraDevice_createCaptureSession and ACameraDevice_createCaptureSessionWithSessionParameters. |
ACameraDevice
|
typedefstruct ACameraDevice
ACameraDevice is opaque type that provides access to a camera device. |
ACameraDevice
|
typedefstruct ACameraDevice
ACameraDevice is opaque type that provides access to a camera device. |
ACameraDevice_ErrorStateCallback)(void *context, ACameraDevice *device, int error)
|
typedefvoid(*
Camera device error state callbacks to be used in ACameraDevice_StateCallbacks. |
ACameraDevice_StateCallback)(void *context, ACameraDevice *device)
|
typedefvoid(*
Camera device state callbacks to be used in ACameraDevice_StateCallbacks. |
ACameraDevice_StateCallbacks
|
typedefstruct ACameraDevice_StateCallbacks
Applications' callbacks for camera device state changes, register with ACameraManager_openCamera. |
ACameraDevice_stateCallbacks
|
typedef For backward compatiblity. |
ACameraIdList
|
typedefstruct ACameraIdList
Struct to hold list of camera device Ids. |
ACameraManager
|
typedefstruct ACameraManager
ACameraManager is opaque type that provides access to camera service. |
ACameraManager_AccessPrioritiesChangedCallback)(void *context)
|
typedefvoid(*
Definition of camera access permission change callback. |
ACameraManager_AvailabilityCallback)(void *context, const char *cameraId)
|
typedefvoid(*
Definition of camera availability callbacks. |
ACameraManager_AvailabilityCallbacks
|
typedef A listener for camera devices becoming available or unavailable to open. |
ACameraManager_ExtendedAvailabilityCallbacks
|
typedef A listener for camera devices becoming available/unavailable to open or when the camera access permissions change. |
ACameraManager_PhysicalCameraAvailabilityCallback)(void *context, const char *cameraId, const char *physicalCameraId)
|
typedefvoid(*
Definition of physical camera availability callbacks. |
ACameraMetadata
|
typedefstruct ACameraMetadata
ACameraMetadata is opaque type that provides access to read-only camera metadata like camera characteristics (via ACameraManager_getCameraCharacteristics) or capture results (via ACameraCaptureSession_captureCallback_result). |
ACameraMetadata_const_entry
|
typedefstruct ACameraMetadata_const_entry
A single read-only camera metadata entry. |
ACameraMetadata_entry
|
typedefstruct ACameraMetadata_entry
A single camera metadata entry. |
ACameraMetadata_rational
|
typedefstruct ACameraMetadata_rational
Definition of rational data type in ACameraMetadata. |
ACameraOutputTarget
|
typedefstruct ACameraOutputTarget
Container for a single output target. |
ACameraOutputTargets
|
typedefstruct ACameraOutputTargets
Container for output targets. |
ACameraWindowType
|
typedef
Deprecated.
No longer needed. Both NDK and VNDK use ANativeWindow now. Use ANativeWindow directly. This file defines the window type used by NDK and the VNDK variants of the camera2 NDK. |
ACaptureRequest
|
typedefstruct ACaptureRequest
ACaptureRequest is an opaque type that contains settings and output targets needed to capture a single image from camera device. |
ACaptureSessionOutput
|
typedefstruct ACaptureSessionOutput
Opaque object for capture session output, use ACaptureSessionOutput_create or ACaptureSessionSharedOutput_create to create an instance. |
ACaptureSessionOutputContainer
|
typedef Opaque object for CaptureSessionOutput container, use ACaptureSessionOutputContainer_create to create an instance. |
ALogicalCameraCaptureFailure
|
typedefstruct ALogicalCameraCaptureFailure
Struct to describe a logical camera capture failure. |
acamera_metadata_enum_android_automotive_lens_facing_t
|
typedef |
acamera_metadata_enum_android_automotive_location_t
|
typedef |
acamera_metadata_enum_android_black_level_lock_t
|
typedefenum acamera_metadata_enum_acamera_black_level_lock
|
acamera_metadata_enum_android_color_correction_aberration_mode_t
|
typedef |
acamera_metadata_enum_android_color_correction_mode_t
|
typedef Enumeration definitions for the various entries that need them. |
acamera_metadata_enum_android_control_ae_antibanding_mode_t
|
typedef |
acamera_metadata_enum_android_control_ae_lock_available_t
|
typedefenum acamera_metadata_enum_acamera_control_ae_lock_available
|
acamera_metadata_enum_android_control_ae_lock_t
|
typedef |
acamera_metadata_enum_android_control_ae_mode_t
|
typedef |
acamera_metadata_enum_android_control_ae_precapture_trigger_t
|
typedef |
acamera_metadata_enum_android_control_ae_state_t
|
typedef |
acamera_metadata_enum_android_control_af_mode_t
|
typedef |
acamera_metadata_enum_android_control_af_scene_change_t
|
typedef |
acamera_metadata_enum_android_control_af_state_t
|
typedef |
acamera_metadata_enum_android_control_af_trigger_t
|
typedef |
acamera_metadata_enum_android_control_autoframing_available_t
|
typedefenum acamera_metadata_enum_acamera_control_autoframing_available
|
acamera_metadata_enum_android_control_autoframing_state_t
|
typedef |
acamera_metadata_enum_android_control_autoframing_t
|
typedef |
acamera_metadata_enum_android_control_awb_lock_available_t
|
typedefenum acamera_metadata_enum_acamera_control_awb_lock_available
|
acamera_metadata_enum_android_control_awb_lock_t
|
typedef |
acamera_metadata_enum_android_control_awb_mode_t
|
typedef |
acamera_metadata_enum_android_control_awb_state_t
|
typedef |
acamera_metadata_enum_android_control_capture_intent_t
|
typedef |
acamera_metadata_enum_android_control_effect_mode_t
|
typedef |
acamera_metadata_enum_android_control_enable_zsl_t
|
typedef |
acamera_metadata_enum_android_control_extended_scene_mode_t
|
typedef |
acamera_metadata_enum_android_control_low_light_boost_state_t
|
typedef |
acamera_metadata_enum_android_control_mode_t
|
typedef |
acamera_metadata_enum_android_control_scene_mode_t
|
typedef |
acamera_metadata_enum_android_control_settings_override_t
|
typedef |
acamera_metadata_enum_android_control_video_stabilization_mode_t
|
typedef |
acamera_metadata_enum_android_depth_available_depth_stream_configurations_maximum_resolution_t
|
typedefenum acamera_metadata_enum_acamera_depth_available_depth_stream_configurations_maximum_resolution
|
acamera_metadata_enum_android_depth_available_depth_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_depth_available_depth_stream_configurations
|
acamera_metadata_enum_android_depth_available_dynamic_depth_stream_configurations_maximum_resolution_t
|
typedefenum acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations_maximum_resolution
|
acamera_metadata_enum_android_depth_available_dynamic_depth_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations
|
acamera_metadata_enum_android_depth_depth_is_exclusive_t
|
typedefenum acamera_metadata_enum_acamera_depth_depth_is_exclusive
|
acamera_metadata_enum_android_distortion_correction_mode_t
|
typedef |
acamera_metadata_enum_android_edge_mode_t
|
typedef |
acamera_metadata_enum_android_flash_info_available_t
|
typedefenum acamera_metadata_enum_acamera_flash_info_available
|
acamera_metadata_enum_android_flash_mode_t
|
typedef |
acamera_metadata_enum_android_flash_state_t
|
typedef |
acamera_metadata_enum_android_heic_available_heic_stream_configurations_maximum_resolution_t
|
typedefenum acamera_metadata_enum_acamera_heic_available_heic_stream_configurations_maximum_resolution
|
acamera_metadata_enum_android_heic_available_heic_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_heic_available_heic_stream_configurations
|
acamera_metadata_enum_android_hot_pixel_mode_t
|
typedef |
acamera_metadata_enum_android_info_supported_hardware_level_t
|
typedef |
acamera_metadata_enum_android_jpegr_available_jpeg_r_stream_configurations_maximum_resolution_t
|
typedefenum acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations_maximum_resolution
|
acamera_metadata_enum_android_jpegr_available_jpeg_r_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations
|
acamera_metadata_enum_android_lens_facing_t
|
typedef |
acamera_metadata_enum_android_lens_info_focus_distance_calibration_t
|
typedef |
acamera_metadata_enum_android_lens_optical_stabilization_mode_t
|
typedef |
acamera_metadata_enum_android_lens_pose_reference_t
|
typedef |
acamera_metadata_enum_android_lens_state_t
|
typedef |
acamera_metadata_enum_android_logical_multi_camera_sensor_sync_type_t
|
typedef |
acamera_metadata_enum_android_noise_reduction_mode_t
|
typedef |
acamera_metadata_enum_android_request_available_capabilities_t
|
typedef |
acamera_metadata_enum_android_request_available_color_space_profiles_map_t
|
typedef |
acamera_metadata_enum_android_request_available_dynamic_range_profiles_map_t
|
typedef |
acamera_metadata_enum_android_scaler_available_recommended_stream_configurations_t
|
typedef |
acamera_metadata_enum_android_scaler_available_stream_configurations_maximum_resolution_t
|
typedefenum acamera_metadata_enum_acamera_scaler_available_stream_configurations_maximum_resolution
|
acamera_metadata_enum_android_scaler_available_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_scaler_available_stream_configurations
|
acamera_metadata_enum_android_scaler_available_stream_use_cases_t
|
typedef |
acamera_metadata_enum_android_scaler_cropping_type_t
|
typedef |
acamera_metadata_enum_android_scaler_multi_resolution_stream_supported_t
|
typedefenum acamera_metadata_enum_acamera_scaler_multi_resolution_stream_supported
|
acamera_metadata_enum_android_scaler_physical_camera_multi_resolution_stream_configurations_t
|
typedefenum acamera_metadata_enum_acamera_scaler_physical_camera_multi_resolution_stream_configurations
|
acamera_metadata_enum_android_scaler_rotate_and_crop_t
|
typedef |
acamera_metadata_enum_android_sensor_info_color_filter_arrangement_t
|
typedef |
acamera_metadata_enum_android_sensor_info_lens_shading_applied_t
|
typedefenum acamera_metadata_enum_acamera_sensor_info_lens_shading_applied
|
acamera_metadata_enum_android_sensor_info_timestamp_source_t
|
typedef |
acamera_metadata_enum_android_sensor_pixel_mode_t
|
typedef |
acamera_metadata_enum_android_sensor_raw_binning_factor_used_t
|
typedef |
acamera_metadata_enum_android_sensor_reference_illuminant1_t
|
typedef |
acamera_metadata_enum_android_sensor_test_pattern_mode_t
|
typedef |
acamera_metadata_enum_android_shading_mode_t
|
typedef |
acamera_metadata_enum_android_statistics_face_detect_mode_t
|
typedef |
acamera_metadata_enum_android_statistics_hot_pixel_map_mode_t
|
typedef |
acamera_metadata_enum_android_statistics_lens_shading_map_mode_t
|
typedef |
acamera_metadata_enum_android_statistics_ois_data_mode_t
|
typedef |
acamera_metadata_enum_android_statistics_scene_flicker_t
|
typedef |
acamera_metadata_enum_android_sync_frame_number_t
|
typedef |
acamera_metadata_enum_android_sync_max_latency_t
|
typedef |
acamera_metadata_enum_android_tonemap_mode_t
|
typedef |
acamera_metadata_enum_android_tonemap_preset_curve_t
|
typedef |
acamera_metadata_section_start_t
|
typedef Hierarchy positions in enum space. |
acamera_metadata_section_t
|
typedefenum acamera_metadata_section
|
acamera_metadata_tag_t
|
typedefenum acamera_metadata_tag
Main enum for camera metadata tags. |
Functions |
|
---|---|
ACameraCaptureSession_abortCaptures(ACameraCaptureSession *session)
|
Discard all captures currently pending and in-progress as fast as possible.
|
ACameraCaptureSession_capture(ACameraCaptureSession *session, ACameraCaptureSession_captureCallbacks *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
Submit an array of requests to be captured in sequence as a burst in the minimum of time possible.
|
ACameraCaptureSession_captureV2(ACameraCaptureSession *session, ACameraCaptureSession_captureCallbacksV2 *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_capture, with added support for v2 of camera callbacks, where the onCaptureStarted callback adds frame number in its parameter list.
|
ACameraCaptureSession_close(ACameraCaptureSession *session)
|
void
Close this capture session.
|
ACameraCaptureSession_getDevice(ACameraCaptureSession *session, ACameraDevice **device)
|
Get the ACameraDevice pointer associated with this capture session in the device argument if the method succeeds.
|
ACameraCaptureSession_logicalCamera_capture(ACameraCaptureSession *session, ACameraCaptureSession_logicalCamera_captureCallbacks *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_capture, with added support for logical multi-camera where the capture callbacks supports result metadata for physical cameras.
|
ACameraCaptureSession_logicalCamera_captureV2(ACameraCaptureSession *session, ACameraCaptureSession_logicalCamera_captureCallbacksV2 *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_logical_capture, with added support for v2 of logical multi-camera callbacks where the onCaptureStarted callback adds frame number in its parameter list.
|
ACameraCaptureSession_logicalCamera_setRepeatingRequest(ACameraCaptureSession *session, ACameraCaptureSession_logicalCamera_captureCallbacks *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_setRepeatingRequest, with added support for logical multi-camera where the capture callbacks supports result metadata for physical cameras.
|
ACameraCaptureSession_logicalCamera_setRepeatingRequestV2(ACameraCaptureSession *session, ACameraCaptureSession_logicalCamera_captureCallbacksV2 *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_logical_setRepeatingRequest, with added support for v2 of logical multi-camera callbacks where the onCaptureStarted callback adds frame number in its parameter list.
|
ACameraCaptureSession_prepareWindow(ACameraCaptureSession *session, ANativeWindow *window)
|
|
ACameraCaptureSession_setRepeatingRequest(ACameraCaptureSession *session, ACameraCaptureSession_captureCallbacks *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
Request endlessly repeating capture of a sequence of images by this capture session.
|
ACameraCaptureSession_setRepeatingRequestV2(ACameraCaptureSession *session, ACameraCaptureSession_captureCallbacksV2 *callbacks, int numRequests, ACaptureRequest **requests, int *captureSequenceId)
|
This has the same functionality as ACameraCaptureSession_logical_setRepeatingRequest, with added support for v2 of logical multi-camera callbacks where the onCaptureStarted callback adds frame number in its parameter list.
|
ACameraCaptureSession_setWindowPreparedCallback(ACameraCaptureSession *session, void *context, ACameraCaptureSession_prepareCallback callback)
|
Set the callback that is called when the output window for which the client has requested pre-allocation of buffers through the ACameraCaptureSession_prepareWindow call has completed the pre-allocation of buffers.
|
ACameraCaptureSession_stopRepeating(ACameraCaptureSession *session)
|
Cancel any ongoing repeating capture set by ACameraCaptureSession_setRepeatingRequest.
|
ACameraCaptureSession_updateSharedOutput(ACameraCaptureSession *session, ACaptureSessionOutput *output)
|
Update shared ACaptureSessionOutput.
|
ACameraDevice_close(ACameraDevice *device)
|
Close the connection and free this ACameraDevice synchronously.
|
ACameraDevice_createCaptureRequest(const ACameraDevice *device, ACameraDevice_request_template templateId, ACaptureRequest **request)
|
Create a ACaptureRequest for capturing images, initialized with template for a target use case.
|
ACameraDevice_createCaptureRequest_withPhysicalIds(const ACameraDevice *device, ACameraDevice_request_template templateId, const ACameraIdList *physicalIdList, ACaptureRequest **request)
|
Create a logical multi-camera ACaptureRequest for capturing images, initialized with template for a target use case, with the ability to specify physical camera settings.
|
ACameraDevice_createCaptureSession(ACameraDevice *device, const ACaptureSessionOutputContainer *outputs, const ACameraCaptureSession_stateCallbacks *callbacks, ACameraCaptureSession **session)
|
Create a new camera capture session by providing the target output set of ANativeWindow to the camera device.
|
ACameraDevice_createCaptureSessionWithSessionParameters(ACameraDevice *device, const ACaptureSessionOutputContainer *outputs, const ACaptureRequest *sessionParameters, const ACameraCaptureSession_stateCallbacks *callbacks, ACameraCaptureSession **session)
|
Create a new camera capture session similar to ACameraDevice_createCaptureSession.
|
ACameraDevice_getId(const ACameraDevice *device)
|
const char *
Return the camera id associated with this camera device.
|
ACameraDevice_isSessionConfigurationSupported(const ACameraDevice *device, const ACaptureSessionOutputContainer *sessionOutputContainer)
|
Check whether a particular ACaptureSessionOutputContainer is supported by the camera device.
|
ACameraManager_create()
|
Create ACameraManager instance.
|
ACameraManager_delete(ACameraManager *manager)
|
void
|
ACameraManager_deleteCameraIdList(ACameraIdList *cameraIdList)
|
void
Delete a list of camera devices allocated via ACameraManager_getCameraIdList.
|
ACameraManager_getCameraCharacteristics(ACameraManager *manager, const char *cameraId, ACameraMetadata **characteristics)
|
Query the capabilities of a camera device.
|
ACameraManager_getCameraIdList(ACameraManager *manager, ACameraIdList **cameraIdList)
|
Create a list of currently connected camera devices, including cameras that may be in use by other camera API clients.
|
ACameraManager_openCamera(ACameraManager *manager, const char *cameraId, ACameraDevice_StateCallbacks *callback, ACameraDevice **device)
|
Open a connection to a camera with the given ID.
|
ACameraManager_registerAvailabilityCallback(ACameraManager *manager, const ACameraManager_AvailabilityCallbacks *callback)
|
Register camera availability callbacks.
|
ACameraManager_registerExtendedAvailabilityCallback(ACameraManager *manager, const ACameraManager_ExtendedAvailabilityCallbacks *callback)
|
Register camera extended availability callbacks.
|
ACameraManager_unregisterAvailabilityCallback(ACameraManager *manager, const ACameraManager_AvailabilityCallbacks *callback)
|
Unregister camera availability callbacks.
|
ACameraManager_unregisterExtendedAvailabilityCallback(ACameraManager *manager, const ACameraManager_ExtendedAvailabilityCallbacks *callback)
|
Unregister camera extended availability callbacks.
|
ACameraMetadata_copy(const ACameraMetadata *src)
|
Create a copy of input ACameraMetadata.
|
ACameraMetadata_free(ACameraMetadata *metadata)
|
void
Free a ACameraMetadata structure.
|
ACameraMetadata_fromCameraMetadata(JNIEnv *env, jobject cameraMetadata)
|
Return a ACameraMetadata that references the same data as android.hardware.camera2.CameraMetadata from Java API.
|
ACameraMetadata_getAllTags(const ACameraMetadata *metadata, int32_t *numEntries, const uint32_t **tags)
|
List all the entry tags in input ACameraMetadata.
|
ACameraMetadata_getConstEntry(const ACameraMetadata *metadata, uint32_t tag, ACameraMetadata_const_entry *entry)
|
Get a metadata entry from an input ACameraMetadata.
|
ACameraMetadata_isLogicalMultiCamera(const ACameraMetadata *staticMetadata, size_t *numPhysicalCameras, const char *const **physicalCameraIds)
|
bool
Helper function to check if a camera is logical multi-camera.
|
ACameraOutputTarget_create(ANativeWindow *window, ACameraOutputTarget **output)
|
Create a ACameraOutputTarget object.
|
ACameraOutputTarget_free(ACameraOutputTarget *output)
|
void
Free a ACameraOutputTarget object.
|
ACaptureRequest_addTarget(ACaptureRequest *request, const ACameraOutputTarget *output)
|
Add an ACameraOutputTarget object to ACaptureRequest.
|
ACaptureRequest_copy(const ACaptureRequest *src)
|
Create a copy of input ACaptureRequest.
|
ACaptureRequest_free(ACaptureRequest *request)
|
void
Free a ACaptureRequest structure.
|
ACaptureRequest_getAllTags(const ACaptureRequest *request, int32_t *numTags, const uint32_t **tags)
|
|
ACaptureRequest_getConstEntry(const ACaptureRequest *request, uint32_t tag, ACameraMetadata_const_entry *entry)
|
Get a metadata entry from input ACaptureRequest.
|
ACaptureRequest_getConstEntry_physicalCamera(const ACaptureRequest *request, const char *physicalId, uint32_t tag, ACameraMetadata_const_entry *entry)
|
Get a metadata entry from input ACaptureRequest for a physical camera backing a logical multi-camera device.
|
ACaptureRequest_getUserContext(const ACaptureRequest *request, void **context)
|
Get the user context pointer of the ACaptureRequest.
|
ACaptureRequest_removeTarget(ACaptureRequest *request, const ACameraOutputTarget *output)
|
Remove an ACameraOutputTarget object from ACaptureRequest.
|
ACaptureRequest_setEntry_double(ACaptureRequest *request, uint32_t tag, uint32_t count, const double *data)
|
Set/change a camera capture control entry with double data type.
|
ACaptureRequest_setEntry_float(ACaptureRequest *request, uint32_t tag, uint32_t count, const float *data)
|
Set/change a camera capture control entry with float data type.
|
ACaptureRequest_setEntry_i32(ACaptureRequest *request, uint32_t tag, uint32_t count, const int32_t *data)
|
Set/change a camera capture control entry with signed 32 bits data type.
|
ACaptureRequest_setEntry_i64(ACaptureRequest *request, uint32_t tag, uint32_t count, const int64_t *data)
|
Set/change a camera capture control entry with signed 64 bits data type.
|
ACaptureRequest_setEntry_physicalCamera_double(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const double *data)
|
Set/change a camera capture control entry with double data type for a physical camera of a logical multi-camera device.
|
ACaptureRequest_setEntry_physicalCamera_float(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const float *data)
|
Set/change a camera capture control entry with float data type for a physical camera of a logical multi-camera device.
|
ACaptureRequest_setEntry_physicalCamera_i32(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const int32_t *data)
|
Set/change a camera capture control entry with signed 32 bits data type for a physical camera of a logical multi-camera device.
|
ACaptureRequest_setEntry_physicalCamera_i64(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const int64_t *data)
|
Set/change a camera capture control entry with signed 64 bits data type for a physical camera of a logical multi-camera device.
|
ACaptureRequest_setEntry_physicalCamera_rational(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const ACameraMetadata_rational *data)
|
Set/change a camera capture control entry with rational data type for a physical camera of a logical multi-camera device.
|
ACaptureRequest_setEntry_physicalCamera_u8(ACaptureRequest *request, const char *physicalId, uint32_t tag, uint32_t count, const uint8_t *data)
|
Set/change a camera capture control entry with unsigned 8 bits data type for a physical camera backing a logical multi-camera device.
|
ACaptureRequest_setEntry_rational(ACaptureRequest *request, uint32_t tag, uint32_t count, const ACameraMetadata_rational *data)
|
Set/change a camera capture control entry with rational data type.
|
ACaptureRequest_setEntry_u8(ACaptureRequest *request, uint32_t tag, uint32_t count, const uint8_t *data)
|
Set/change a camera capture control entry with unsigned 8 bits data type.
|
ACaptureRequest_setUserContext(ACaptureRequest *request, void *context)
|
Associate an arbitrary user context pointer to the ACaptureRequest.
|
ACaptureSessionOutputContainer_add(ACaptureSessionOutputContainer *container, const ACaptureSessionOutput *output)
|
Add an ACaptureSessionOutput object to ACaptureSessionOutputContainer.
|
ACaptureSessionOutputContainer_create(ACaptureSessionOutputContainer **container)
|
Create a capture session output container.
|
ACaptureSessionOutputContainer_free(ACaptureSessionOutputContainer *container)
|
void
Free a capture session output container.
|
ACaptureSessionOutputContainer_remove(ACaptureSessionOutputContainer *container, const ACaptureSessionOutput *output)
|
Remove an ACaptureSessionOutput object from ACaptureSessionOutputContainer.
|
ACaptureSessionOutput_create(ANativeWindow *anw, ACaptureSessionOutput **output)
|
Create a ACaptureSessionOutput object.
|
ACaptureSessionOutput_free(ACaptureSessionOutput *output)
|
void
Free a ACaptureSessionOutput object.
|
ACaptureSessionPhysicalOutput_create(ANativeWindow *anw, const char *physicalId, ACaptureSessionOutput **output)
|
Create a ACaptureSessionOutput object used for streaming from a physical camera as part of a logical camera device.
|
ACaptureSessionSharedOutput_add(ACaptureSessionOutput *output, ANativeWindow *anw)
|
Add a native window to shared ACaptureSessionOutput.
|
ACaptureSessionSharedOutput_create(ANativeWindow *anw, ACaptureSessionOutput **output)
|
Create a shared ACaptureSessionOutput object.
|
ACaptureSessionSharedOutput_remove(ACaptureSessionOutput *output, ANativeWindow *anw)
|
Remove a native window from shared ACaptureSessionOutput.
|
Structs |
|
---|---|
ACameraCaptureFailure |
Struct to describe a capture failure. |
ACameraCaptureSession_captureCallbacks |
ACaptureCaptureSession_captureCallbacks structure used in ACameraCaptureSession_capture and ACameraCaptureSession_setRepeatingRequest. |
ACameraCaptureSession_captureCallbacksV2 |
This has the same functionality as ACameraCaptureSession_captureCallbacks, with the exception that captureCallback_startV2 callback is used, instead of captureCallback_start, to support retrieving the frame number. |
ACameraCaptureSession_logicalCamera_captureCallbacks |
This has the same functionality as ACameraCaptureSession_captureCallbacks, with the exception that an onLogicalCameraCaptureCompleted callback is used, instead of onCaptureCompleted, to support logical multi-camera. |
ACameraCaptureSession_logicalCamera_captureCallbacksV2 |
This has the same functionality as ACameraCaptureSession_logicalCamera_captureCallbacks, with the exception that an captureCallback_startV2 callback is used, instead of captureCallback_start, to support retrieving frame number. |
ACameraCaptureSession_stateCallbacks |
Capture session state callbacks used in ACameraDevice_createCaptureSession and ACameraDevice_createCaptureSessionWithSessionParameters. |
ACameraDevice_StateCallbacks |
Applications' callbacks for camera device state changes, register with ACameraManager_openCamera. |
ACameraIdList |
Struct to hold list of camera device Ids. |
ACameraManager_AvailabilityListener |
A listener for camera devices becoming available or unavailable to open. |
ACameraManager_ExtendedAvailabilityListener |
A listener for camera devices becoming available/unavailable to open or when the camera access permissions change. |
ACameraMetadata_const_entry |
A single read-only camera metadata entry. |
ACameraMetadata_entry |
A single camera metadata entry. |
ACameraMetadata_rational |
Definition of rational data type in ACameraMetadata. |
ALogicalCameraCaptureFailure |
Struct to describe a logical camera capture failure. |
Enumerations
Anonymous Enum 108
Anonymous Enum 108
Enum for describing error reason in ACameraCaptureFailure.
Properties | |
---|---|
CAPTURE_FAILURE_REASON_ERROR
|
The capture session has dropped this frame due to an error in the framework. |
CAPTURE_FAILURE_REASON_FLUSHED
|
The capture session has dropped this frame due to an ACameraCaptureSession_abortCaptures call. |
Anonymous Enum 110
Anonymous Enum 110
Enum for ACameraDevice_ErrorStateCallback error code.
Anonymous Enum 111
Anonymous Enum 111
Possible data types of a metadata entry.
Keep in sync with system/media/include/system/camera_metadata.h
Properties | |
---|---|
ACAMERA_NUM_TYPES
|
Number of type fields. |
ACAMERA_TYPE_BYTE
|
Unsigned 8-bit integer (uint8_t) |
ACAMERA_TYPE_DOUBLE
|
64-bit float (double) |
ACAMERA_TYPE_FLOAT
|
32-bit float (float) |
ACAMERA_TYPE_INT32
|
Signed 32-bit integer (int32_t) |
ACAMERA_TYPE_INT64
|
Signed 64-bit integer (int64_t) |
ACAMERA_TYPE_RATIONAL
|
A 64-bit fraction (ACameraMetadata_rational) |
ACameraDevice_request_template
ACameraDevice_request_template
Capture request pre-defined template types, used in ACameraDevice_createCaptureRequest and ACameraDevice_createCaptureRequest_withPhysicalIds.
Properties | |
---|---|
TEMPLATE_MANUAL
|
A basic template for direct application control of capture parameters. All automatic control is disabled (auto-exposure, auto-white balance, auto-focus), and post-processing parameters are set to preview quality. The manual capture parameters (exposure, sensitivity, and so on) are set to reasonable defaults, but should be overriden by the application depending on the intended use case. This template is guaranteed to be supported on camera devices that support the ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR capability. See also: ACameraDevice_createCaptureRequest |
TEMPLATE_PREVIEW
|
Create a request suitable for a camera preview window. Specifically, this means that high frame rate is given priority over the highest-quality post-processing. These requests would normally be used with the ACameraCaptureSession_setRepeatingRequest method. This template is guaranteed to be supported on all camera devices. See also: ACameraDevice_createCaptureRequest |
TEMPLATE_RECORD
|
Create a request suitable for video recording. Specifically, this means that a stable frame rate is used, and post-processing is set for recording quality. These requests would commonly be used with the ACameraCaptureSession_setRepeatingRequest method. This template is guaranteed to be supported on all camera devices. See also: ACameraDevice_createCaptureRequest |
TEMPLATE_STILL_CAPTURE
|
Create a request suitable for still image capture. Specifically, this means prioritizing image quality over frame rate. These requests would commonly be used with the ACameraCaptureSession_capture method. This template is guaranteed to be supported on all camera devices. See also: ACameraDevice_createCaptureRequest |
TEMPLATE_VIDEO_SNAPSHOT
|
Create a request suitable for still image capture while recording video. Specifically, this means maximizing image quality without disrupting the ongoing recording. These requests would commonly be used with the ACameraCaptureSession_capture method while a request based on TEMPLATE_RECORD is is in use with ACameraCaptureSession_setRepeatingRequest. This template is guaranteed to be supported on all camera devices. See also: ACameraDevice_createCaptureRequest |
TEMPLATE_ZERO_SHUTTER_LAG
|
Create a request suitable for zero shutter lag still capture. This means means maximizing image quality without compromising preview frame rate. AE/AWB/AF should be on auto mode. See also: ACameraDevice_createCaptureRequest |
acamera_metadata_enum_acamera_automotive_lens_facing
acamera_metadata_enum_acamera_automotive_lens_facing
Properties | |
---|---|
ACAMERA_AUTOMOTIVE_LENS_FACING_EXTERIOR_FRONT
|
The camera device faces the front of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LENS_FACING_EXTERIOR_LEFT
|
The camera device faces the left side of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LENS_FACING_EXTERIOR_OTHER
|
The camera device faces the outside of the vehicle body frame but not exactly one of the exterior sides defined by this enum. Applications should determine the exact facing direction from ACAMERA_LENS_POSE_ROTATION and ACAMERA_LENS_POSE_TRANSLATION. See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_AUTOMOTIVE_LENS_FACING_EXTERIOR_REAR
|
The camera device faces the rear of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LENS_FACING_EXTERIOR_RIGHT
|
The camera device faces the right side of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_OTHER
|
The camera device faces the inside of the vehicle body frame but not exactly one of seats described by this enum. Applications should determine the exact facing direction from ACAMERA_LENS_POSE_ROTATION and ACAMERA_LENS_POSE_TRANSLATION. See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_1_CENTER
|
The camera device faces the center seat of the first row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_1_LEFT
|
The camera device faces the left side seat of the first row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_1_RIGHT
|
The camera device faces the right seat of the first row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_2_CENTER
|
The camera device faces the center seat of the second row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_2_LEFT
|
The camera device faces the left side seat of the second row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_2_RIGHT
|
The camera device faces the right side seat of the second row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_3_CENTER
|
The camera device faces the center seat of the third row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_3_LEFT
|
The camera device faces the left side seat of the third row. |
ACAMERA_AUTOMOTIVE_LENS_FACING_INTERIOR_SEAT_ROW_3_RIGHT
|
The camera device faces the right seat of the third row. |
acamera_metadata_enum_acamera_automotive_location
acamera_metadata_enum_acamera_automotive_location
Properties | |
---|---|
ACAMERA_AUTOMOTIVE_LOCATION_EXTERIOR_FRONT
|
The camera device exists outside of the vehicle body frame and on its front side. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTERIOR_LEFT
|
The camera device exists outside and on left side of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTERIOR_OTHER
|
The camera exists outside of the vehicle body frame but not exactly on one of the exterior locations this enum defines. The applications should determine the exact location from ACAMERA_LENS_POSE_TRANSLATION. See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_AUTOMOTIVE_LOCATION_EXTERIOR_REAR
|
The camera device exists outside of the vehicle body frame and on its rear side. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTERIOR_RIGHT
|
The camera device exists outside and on right side of the vehicle body frame. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTRA_FRONT
|
The camera device exists outside of the extra vehicle's body frame and on its front side. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTRA_LEFT
|
The camera device exists outside and on left side of the extra vehicle body. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTRA_OTHER
|
The camera device exists on an extra vehicle, such as the trailer, but not exactly on one of front, rear, left, or right side. Applications should determine the exact location from ACAMERA_LENS_POSE_TRANSLATION. See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_AUTOMOTIVE_LOCATION_EXTRA_REAR
|
The camera device exists outside of the extra vehicle's body frame and on its rear side. |
ACAMERA_AUTOMOTIVE_LOCATION_EXTRA_RIGHT
|
The camera device exists outside and on right side of the extra vehicle body. |
ACAMERA_AUTOMOTIVE_LOCATION_INTERIOR
|
The camera device exists inside of the vehicle cabin. |
acamera_metadata_enum_acamera_black_level_lock
acamera_metadata_enum_acamera_black_level_lock
acamera_metadata_enum_acamera_color_correction_aberration_mode
acamera_metadata_enum_acamera_color_correction_aberration_mode
acamera_metadata_enum_acamera_color_correction_mode
acamera_metadata_enum_acamera_color_correction_mode
Enumeration definitions for the various entries that need them.
Properties | |
---|---|
ACAMERA_COLOR_CORRECTION_MODE_FAST
|
Color correction processing must not slow down capture rate relative to sensor raw output. Advanced white balance adjustments above and beyond the specified white balance pipeline may be applied. If AWB is enabled with See also: ACAMERA_CONTROL_AWB_MODE |
ACAMERA_COLOR_CORRECTION_MODE_HIGH_QUALITY
|
Color correction processing operates at improved quality but the capture rate might be reduced (relative to sensor raw output rate) Advanced white balance adjustments above and beyond the specified white balance pipeline may be applied. If AWB is enabled with See also: ACAMERA_CONTROL_AWB_MODE |
ACAMERA_COLOR_CORRECTION_MODE_TRANSFORM_MATRIX
|
Use the ACAMERA_COLOR_CORRECTION_TRANSFORM matrix and ACAMERA_COLOR_CORRECTION_GAINS to do color conversion. All advanced white balance adjustments (not specified by our white balance pipeline) must be disabled. If AWB is enabled with See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM See also: ACAMERA_CONTROL_AWB_MODE |
acamera_metadata_enum_acamera_control_ae_antibanding_mode
acamera_metadata_enum_acamera_control_ae_antibanding_mode
acamera_metadata_enum_acamera_control_ae_lock
acamera_metadata_enum_acamera_control_ae_lock
Properties | |
---|---|
ACAMERA_CONTROL_AE_LOCK_OFF
|
Auto-exposure lock is disabled; the AE algorithm is free to update its parameters. |
ACAMERA_CONTROL_AE_LOCK_ON
|
Auto-exposure lock is enabled; the AE algorithm must not update the exposure and sensitivity parameters while the lock is active. ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION setting changes will still take effect while auto-exposure is locked. Some rare LEGACY devices may not support this, in which case the value will always be overridden to OFF. See also: ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION |
acamera_metadata_enum_acamera_control_ae_lock_available
acamera_metadata_enum_acamera_control_ae_lock_available
acamera_metadata_enum_acamera_control_ae_mode
acamera_metadata_enum_acamera_control_ae_mode
Properties | |
---|---|
ACAMERA_CONTROL_AE_MODE_OFF
|
The camera device's autoexposure routine is disabled. The application-selected ACAMERA_SENSOR_EXPOSURE_TIME, ACAMERA_SENSOR_SENSITIVITY and ACAMERA_SENSOR_FRAME_DURATION are used by the camera device, along with ACAMERA_FLASH_* fields, if there's a flash unit for this camera device. Note that auto-white balance (AWB) and auto-focus (AF) behavior is device dependent when AE is in OFF mode. To have consistent behavior across different devices, it is recommended to either set AWB and AF to OFF mode or lock AWB and AF before setting AE to OFF. See ACAMERA_CONTROL_AWB_MODE, ACAMERA_CONTROL_AF_MODE, ACAMERA_CONTROL_AWB_LOCK, and ACAMERA_CONTROL_AF_TRIGGER for more details. LEGACY devices do not support the OFF mode and will override attempts to use this value to ON. See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AF_TRIGGER See also: ACAMERA_CONTROL_AWB_LOCK See also: ACAMERA_CONTROL_AWB_MODE See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_FRAME_DURATION See also: ACAMERA_SENSOR_SENSITIVITY |
ACAMERA_CONTROL_AE_MODE_ON
|
The camera device's autoexposure routine is active, with no flash control. The application's values for ACAMERA_SENSOR_EXPOSURE_TIME, ACAMERA_SENSOR_SENSITIVITY, and ACAMERA_SENSOR_FRAME_DURATION are ignored. The application has control over the various ACAMERA_FLASH_* fields. See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_FRAME_DURATION See also: ACAMERA_SENSOR_SENSITIVITY |
ACAMERA_CONTROL_AE_MODE_ON_ALWAYS_FLASH
|
Like ON, except that the camera device also controls the camera's flash unit, always firing it for still captures. The flash may be fired during a precapture sequence (triggered by ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER) and will always be fired for captures for which the ACAMERA_CONTROL_CAPTURE_INTENT field is set to STILL_CAPTURE See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_CONTROL_AE_MODE_ON_AUTO_FLASH
|
Like ON, except that the camera device also controls the camera's flash unit, firing it in low-light conditions. The flash may be fired during a precapture sequence (triggered by ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER) and may be fired for captures for which the ACAMERA_CONTROL_CAPTURE_INTENT field is set to STILL_CAPTURE See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_CONTROL_AE_MODE_ON_AUTO_FLASH_REDEYE
|
Like ON_AUTO_FLASH, but with automatic red eye reduction. If deemed necessary by the camera device, a red eye reduction flash will fire during the precapture sequence. |
ACAMERA_CONTROL_AE_MODE_ON_EXTERNAL_FLASH
|
An external flash has been turned on. It informs the camera device that an external flash has been turned on, and that metering (and continuous focus if active) should be quickly recalculated to account for the external flash. Otherwise, this mode acts like ON. When the external flash is turned off, AE mode should be changed to one of the other available AE modes. If the camera device supports AE external flash mode, ACAMERA_CONTROL_AE_STATE must be FLASH_REQUIRED after the camera device finishes AE scan and it's too dark without flash. See also: ACAMERA_CONTROL_AE_STATE |
ACAMERA_CONTROL_AE_MODE_ON_LOW_LIGHT_BOOST_BRIGHTNESS_PRIORITY
|
Like 'ON' but applies additional brightness boost in low light scenes. When the scene lighting conditions are within the range defined by ACAMERA_CONTROL_LOW_LIGHT_BOOST_INFO_LUMINANCE_RANGE this mode will apply additional brightness boost. This mode will automatically adjust the intensity of low light boost applied according to the scene lighting conditions. A darker scene will receive more boost while a brighter scene will receive less boost. This mode can ignore the set target frame rate to allow more light to be captured which can result in choppier motion. The frame rate can extend to lower than the ACAMERA_CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES but will not go below 10 FPS. This mode can also increase the sensor sensitivity gain which can result in increased luma and chroma noise. The sensor sensitivity gain can extend to higher values beyond ACAMERA_SENSOR_INFO_SENSITIVITY_RANGE. This mode may also apply additional processing to recover details in dark and bright areas of the image,and noise reduction at high sensitivity gain settings to manage the trade-off between light sensitivity and capture noise. This mode is restricted to two output surfaces. One output surface type can either be SurfaceView or TextureView. Another output surface type can either be MediaCodec or MediaRecorder. This mode cannot be used with a target FPS range higher than 30 FPS. If the session configuration is not supported, the AE mode reported in the CaptureResult will be 'ON' instead of 'ON_LOW_LIGHT_BOOST_BRIGHTNESS_PRIORITY'. The application can observe the CapturerResult field ACAMERA_CONTROL_LOW_LIGHT_BOOST_STATE to determine when low light boost is 'ACTIVE' or 'INACTIVE'. The low light boost is 'ACTIVE' once the scene lighting condition is less than the upper bound lux value defined by ACAMERA_CONTROL_LOW_LIGHT_BOOST_INFO_LUMINANCE_RANGE. This mode will be 'INACTIVE' once the scene lighting condition is greater than the upper bound lux value defined by ACAMERA_CONTROL_LOW_LIGHT_BOOST_INFO_LUMINANCE_RANGE. See also: ACAMERA_CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES See also: ACAMERA_CONTROL_LOW_LIGHT_BOOST_INFO_LUMINANCE_RANGE See also: ACAMERA_CONTROL_LOW_LIGHT_BOOST_STATE See also: ACAMERA_SENSOR_INFO_SENSITIVITY_RANGE |
acamera_metadata_enum_acamera_control_ae_precapture_trigger
acamera_metadata_enum_acamera_control_ae_precapture_trigger
acamera_metadata_enum_acamera_control_ae_state
acamera_metadata_enum_acamera_control_ae_state
Properties | |
---|---|
ACAMERA_CONTROL_AE_STATE_CONVERGED
|
AE has a good set of control values for the current scene. |
ACAMERA_CONTROL_AE_STATE_FLASH_REQUIRED
|
AE has a good set of control values, but flash needs to be fired for good quality still capture. |
ACAMERA_CONTROL_AE_STATE_INACTIVE
|
AE is off or recently reset. When a camera device is opened, it starts in this state. This is a transient state, the camera device may skip reporting this state in capture result. |
ACAMERA_CONTROL_AE_STATE_LOCKED
|
AE has been locked. |
ACAMERA_CONTROL_AE_STATE_PRECAPTURE
|
AE has been asked to do a precapture sequence and is currently executing it. Precapture can be triggered through setting ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER to START. Currently active and completed (if it causes camera device internal AE lock) precapture metering sequence can be canceled through setting ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER to CANCEL. Once PRECAPTURE completes, AE will transition to CONVERGED or FLASH_REQUIRED as appropriate. This is a transient state, the camera device may skip reporting this state in capture result. See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER |
ACAMERA_CONTROL_AE_STATE_SEARCHING
|
AE doesn't yet have a good set of control values for the current scene. This is a transient state, the camera device may skip reporting this state in capture result. |
acamera_metadata_enum_acamera_control_af_mode
acamera_metadata_enum_acamera_control_af_mode
Properties | |
---|---|
ACAMERA_CONTROL_AF_MODE_AUTO
|
Basic automatic focus mode. In this mode, the lens does not move unless the autofocus trigger action is called. When that trigger is activated, AF will transition to ACTIVE_SCAN, then to the outcome of the scan (FOCUSED or NOT_FOCUSED). Always supported if lens is not fixed focus. Use ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE to determine if lens is fixed-focus. Triggering AF_CANCEL resets the lens position to default, and sets the AF state to INACTIVE. See also: ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE |
ACAMERA_CONTROL_AF_MODE_CONTINUOUS_PICTURE
|
In this mode, the AF algorithm modifies the lens position continually to attempt to provide a constantly-in-focus image stream. The focusing behavior should be suitable for still image capture; typically this means focusing as fast as possible. When the AF trigger is not involved, the AF algorithm should start in INACTIVE state, and then transition into PASSIVE_SCAN and PASSIVE_FOCUSED states as appropriate as it attempts to maintain focus. When the AF trigger is activated, the algorithm should finish its PASSIVE_SCAN if active, and then transition into AF_FOCUSED or AF_NOT_FOCUSED as appropriate, and lock the lens position until a cancel AF trigger is received. When the AF cancel trigger is activated, the algorithm should transition back to INACTIVE and then act as if it has just been started. |
ACAMERA_CONTROL_AF_MODE_CONTINUOUS_VIDEO
|
In this mode, the AF algorithm modifies the lens position continually to attempt to provide a constantly-in-focus image stream. The focusing behavior should be suitable for good quality video recording; typically this means slower focus movement and no overshoots. When the AF trigger is not involved, the AF algorithm should start in INACTIVE state, and then transition into PASSIVE_SCAN and PASSIVE_FOCUSED states as appropriate. When the AF trigger is activated, the algorithm should immediately transition into AF_FOCUSED or AF_NOT_FOCUSED as appropriate, and lock the lens position until a cancel AF trigger is received. Once cancel is received, the algorithm should transition back to INACTIVE and resume passive scan. Note that this behavior is not identical to CONTINUOUS_PICTURE, since an ongoing PASSIVE_SCAN must immediately be canceled. |
ACAMERA_CONTROL_AF_MODE_EDOF
|
Extended depth of field (digital focus) mode. The camera device will produce images with an extended depth of field automatically; no special focusing operations need to be done before taking a picture. AF triggers are ignored, and the AF state will always be INACTIVE. |
ACAMERA_CONTROL_AF_MODE_MACRO
|
Close-up focusing mode. In this mode, the lens does not move unless the autofocus trigger action is called. When that trigger is activated, AF will transition to ACTIVE_SCAN, then to the outcome of the scan (FOCUSED or NOT_FOCUSED). This mode is optimized for focusing on objects very close to the camera. When that trigger is activated, AF will transition to ACTIVE_SCAN, then to the outcome of the scan (FOCUSED or NOT_FOCUSED). Triggering cancel AF resets the lens position to default, and sets the AF state to INACTIVE. |
ACAMERA_CONTROL_AF_MODE_OFF
|
The auto-focus routine does not control the lens; ACAMERA_LENS_FOCUS_DISTANCE is controlled by the application. See also: ACAMERA_LENS_FOCUS_DISTANCE |
acamera_metadata_enum_acamera_control_af_scene_change
acamera_metadata_enum_acamera_control_af_scene_change
acamera_metadata_enum_acamera_control_af_state
acamera_metadata_enum_acamera_control_af_state
Properties | |
---|---|
ACAMERA_CONTROL_AF_STATE_ACTIVE_SCAN
|
AF is performing an AF scan because it was triggered by AF trigger. Only used by AUTO or MACRO AF modes. This is a transient state, the camera device may skip reporting this state in capture result. |
ACAMERA_CONTROL_AF_STATE_FOCUSED_LOCKED
|
AF believes it is focused correctly and has locked focus. This state is reached only after an explicit START AF trigger has been sent (ACAMERA_CONTROL_AF_TRIGGER), when good focus has been obtained. The lens will remain stationary until the AF mode (ACAMERA_CONTROL_AF_MODE) is changed or a new AF trigger is sent to the camera device (ACAMERA_CONTROL_AF_TRIGGER). See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AF_TRIGGER |
ACAMERA_CONTROL_AF_STATE_INACTIVE
|
AF is off or has not yet tried to scan/been asked to scan. When a camera device is opened, it starts in this state. This is a transient state, the camera device may skip reporting this state in capture result. |
ACAMERA_CONTROL_AF_STATE_NOT_FOCUSED_LOCKED
|
AF has failed to focus successfully and has locked focus. This state is reached only after an explicit START AF trigger has been sent (ACAMERA_CONTROL_AF_TRIGGER), when good focus cannot be obtained. The lens will remain stationary until the AF mode (ACAMERA_CONTROL_AF_MODE) is changed or a new AF trigger is sent to the camera device (ACAMERA_CONTROL_AF_TRIGGER). See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AF_TRIGGER |
ACAMERA_CONTROL_AF_STATE_PASSIVE_FOCUSED
|
AF currently believes it is in focus, but may restart scanning at any time. Only used by CONTINUOUS_* AF modes. This is a transient state, the camera device may skip reporting this state in capture result. |
ACAMERA_CONTROL_AF_STATE_PASSIVE_SCAN
|
AF is currently performing an AF scan initiated the camera device in a continuous autofocus mode. Only used by CONTINUOUS_* AF modes. This is a transient state, the camera device may skip reporting this state in capture result. |
ACAMERA_CONTROL_AF_STATE_PASSIVE_UNFOCUSED
|
AF finished a passive scan without finding focus, and may restart scanning at any time. Only used by CONTINUOUS_* AF modes. This is a transient state, the camera device may skip reporting this state in capture result. LEGACY camera devices do not support this state. When a passive scan has finished, it will always go to PASSIVE_FOCUSED. |
acamera_metadata_enum_acamera_control_af_trigger
acamera_metadata_enum_acamera_control_af_trigger
acamera_metadata_enum_acamera_control_autoframing
acamera_metadata_enum_acamera_control_autoframing
acamera_metadata_enum_acamera_control_autoframing_available
acamera_metadata_enum_acamera_control_autoframing_available
acamera_metadata_enum_acamera_control_autoframing_state
acamera_metadata_enum_acamera_control_autoframing_state
acamera_metadata_enum_acamera_control_awb_lock
acamera_metadata_enum_acamera_control_awb_lock
acamera_metadata_enum_acamera_control_awb_lock_available
acamera_metadata_enum_acamera_control_awb_lock_available
acamera_metadata_enum_acamera_control_awb_mode
acamera_metadata_enum_acamera_control_awb_mode
Properties | |
---|---|
ACAMERA_CONTROL_AWB_MODE_AUTO
|
The camera device's auto-white balance routine is active. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_CLOUDY_DAYLIGHT
|
The camera device's auto-white balance routine is disabled; the camera device uses cloudy daylight light as the assumed scene illumination for white balance. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_DAYLIGHT
|
The camera device's auto-white balance routine is disabled; the camera device uses daylight light as the assumed scene illumination for white balance. While the exact white balance transforms are up to the camera device, they will approximately match the CIE standard illuminant D65. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_FLUORESCENT
|
The camera device's auto-white balance routine is disabled; the camera device uses fluorescent light as the assumed scene illumination for white balance. While the exact white balance transforms are up to the camera device, they will approximately match the CIE standard illuminant F2. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_INCANDESCENT
|
The camera device's auto-white balance routine is disabled; the camera device uses incandescent light as the assumed scene illumination for white balance. While the exact white balance transforms are up to the camera device, they will approximately match the CIE standard illuminant A. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_OFF
|
The camera device's auto-white balance routine is disabled. The application-selected color transform matrix (ACAMERA_COLOR_CORRECTION_TRANSFORM) and gains (ACAMERA_COLOR_CORRECTION_GAINS) are used by the camera device for manual white balance control. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_SHADE
|
The camera device's auto-white balance routine is disabled; the camera device uses shade light as the assumed scene illumination for white balance. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_TWILIGHT
|
The camera device's auto-white balance routine is disabled; the camera device uses twilight light as the assumed scene illumination for white balance. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
ACAMERA_CONTROL_AWB_MODE_WARM_FLUORESCENT
|
The camera device's auto-white balance routine is disabled; the camera device uses warm fluorescent light as the assumed scene illumination for white balance. While the exact white balance transforms are up to the camera device, they will approximately match the CIE standard illuminant F4. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS are ignored. For devices that support the MANUAL_POST_PROCESSING capability, the values used by the camera device for the transform and gains will be available in the capture result for this request. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM |
acamera_metadata_enum_acamera_control_awb_state
acamera_metadata_enum_acamera_control_awb_state
acamera_metadata_enum_acamera_control_capture_intent
acamera_metadata_enum_acamera_control_capture_intent
Properties | |
---|---|
ACAMERA_CONTROL_CAPTURE_INTENT_CUSTOM
|
The goal of this request doesn't fall into the other categories. The camera device will default to preview-like behavior. |
ACAMERA_CONTROL_CAPTURE_INTENT_MANUAL
|
This request is for manual capture use case where the applications want to directly control the capture parameters. For example, the application may wish to manually control ACAMERA_SENSOR_EXPOSURE_TIME, ACAMERA_SENSOR_SENSITIVITY, etc. See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_SENSITIVITY |
ACAMERA_CONTROL_CAPTURE_INTENT_MOTION_TRACKING
|
This request is for a motion tracking use case, where the application will use camera and inertial sensor data to locate and track objects in the world. The camera device auto-exposure routine will limit the exposure time of the camera to no more than 20 milliseconds, to minimize motion blur. |
ACAMERA_CONTROL_CAPTURE_INTENT_PREVIEW
|
This request is for a preview-like use case. The precapture trigger may be used to start off a metering w/flash sequence. |
ACAMERA_CONTROL_CAPTURE_INTENT_STILL_CAPTURE
|
This request is for a still capture-type use case. If the flash unit is under automatic control, it may fire as needed. |
ACAMERA_CONTROL_CAPTURE_INTENT_VIDEO_RECORD
|
This request is for a video recording use case. |
ACAMERA_CONTROL_CAPTURE_INTENT_VIDEO_SNAPSHOT
|
This request is for a video snapshot (still image while recording video) use case. The camera device should take the highest-quality image possible (given the other settings) without disrupting the frame rate of video recording. |
ACAMERA_CONTROL_CAPTURE_INTENT_ZERO_SHUTTER_LAG
|
This request is for a ZSL usecase; the application will stream full-resolution images and reprocess one or several later for a final capture. |
acamera_metadata_enum_acamera_control_effect_mode
acamera_metadata_enum_acamera_control_effect_mode
acamera_metadata_enum_acamera_control_enable_zsl
acamera_metadata_enum_acamera_control_enable_zsl
Properties | |
---|---|
ACAMERA_CONTROL_ENABLE_ZSL_FALSE
|
Requests with ACAMERA_CONTROL_CAPTURE_INTENT == STILL_CAPTURE must be captured after previous requests. See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_CONTROL_ENABLE_ZSL_TRUE
|
Requests with ACAMERA_CONTROL_CAPTURE_INTENT == STILL_CAPTURE may or may not be captured before previous requests. See also: ACAMERA_CONTROL_CAPTURE_INTENT |
acamera_metadata_enum_acamera_control_extended_scene_mode
acamera_metadata_enum_acamera_control_extended_scene_mode
acamera_metadata_enum_acamera_control_low_light_boost_state
acamera_metadata_enum_acamera_control_low_light_boost_state
acamera_metadata_enum_acamera_control_mode
acamera_metadata_enum_acamera_control_mode
Properties | |
---|---|
ACAMERA_CONTROL_MODE_AUTO
|
Use settings for each individual 3A routine. Manual control of capture parameters is disabled. All controls in ACAMERA_CONTROL_* besides sceneMode take effect. |
ACAMERA_CONTROL_MODE_OFF
|
Full application control of pipeline. All control by the device's metering and focusing (3A) routines is disabled, and no other settings in ACAMERA_CONTROL_* have any effect, except that ACAMERA_CONTROL_CAPTURE_INTENT may be used by the camera device to select post-processing values for processing blocks that do not allow for manual control, or are not exposed by the camera API. However, the camera device's 3A routines may continue to collect statistics and update their internal state so that when control is switched to AUTO mode, good control values can be immediately applied. See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_CONTROL_MODE_OFF_KEEP_STATE
|
Same as OFF mode, except that this capture will not be used by camera device background auto-exposure, auto-white balance and auto-focus algorithms (3A) to update their statistics. Specifically, the 3A routines are locked to the last values set from a request with AUTO, OFF, or USE_SCENE_MODE, and any statistics or state updates collected from manual captures with OFF_KEEP_STATE will be discarded by the camera device. |
ACAMERA_CONTROL_MODE_USE_EXTENDED_SCENE_MODE
|
Use a specific extended scene mode. When extended scene mode is on, the camera device may override certain control parameters, such as targetFpsRange, AE, AWB, and AF modes, to achieve best power and quality tradeoffs. Only the mandatory stream combinations of LIMITED hardware level are guaranteed. This setting can only be used if extended scene mode is supported (i.e. android.control.availableExtendedSceneModes contains some modes other than DISABLED). |
ACAMERA_CONTROL_MODE_USE_SCENE_MODE
|
Use a specific scene mode. Enabling this disables control.aeMode, control.awbMode and control.afMode controls; the camera device will ignore those settings while USE_SCENE_MODE is active (except for FACE_PRIORITY scene mode). Other control entries are still active. This setting can only be used if scene mode is supported (i.e. ACAMERA_CONTROL_AVAILABLE_SCENE_MODES contain some modes other than DISABLED). For extended scene modes such as BOKEH, please use USE_EXTENDED_SCENE_MODE instead. See also: ACAMERA_CONTROL_AVAILABLE_SCENE_MODES |
acamera_metadata_enum_acamera_control_scene_mode
acamera_metadata_enum_acamera_control_scene_mode
Properties | |
---|---|
ACAMERA_CONTROL_SCENE_MODE_ACTION
|
Optimized for photos of quickly moving objects. Similar to SPORTS. |
ACAMERA_CONTROL_SCENE_MODE_BARCODE
|
Optimized for accurately capturing a photo of barcode for use by camera applications that wish to read the barcode value. |
ACAMERA_CONTROL_SCENE_MODE_BEACH
|
Optimized for bright, outdoor beach settings. |
ACAMERA_CONTROL_SCENE_MODE_CANDLELIGHT
|
Optimized for dim settings where the main light source is a candle. |
ACAMERA_CONTROL_SCENE_MODE_DISABLED
|
Indicates that no scene modes are set for a given capture request. |
ACAMERA_CONTROL_SCENE_MODE_FACE_PRIORITY
|
If face detection support exists, use face detection data for auto-focus, auto-white balance, and auto-exposure routines. If face detection statistics are disabled (i.e. ACAMERA_STATISTICS_FACE_DETECT_MODE is set to OFF), this should still operate correctly (but will not return face detection statistics to the framework). Unlike the other scene modes, ACAMERA_CONTROL_AE_MODE, ACAMERA_CONTROL_AWB_MODE, and ACAMERA_CONTROL_AF_MODE remain active when FACE_PRIORITY is set. See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AWB_MODE See also: ACAMERA_STATISTICS_FACE_DETECT_MODE |
ACAMERA_CONTROL_SCENE_MODE_FIREWORKS
|
Optimized for nighttime photos of fireworks. |
ACAMERA_CONTROL_SCENE_MODE_HDR
|
Turn on a device-specific high dynamic range (HDR) mode. In this scene mode, the camera device captures images that keep a larger range of scene illumination levels visible in the final image. For example, when taking a picture of a object in front of a bright window, both the object and the scene through the window may be visible when using HDR mode, while in normal AUTO mode, one or the other may be poorly exposed. As a tradeoff, HDR mode generally takes much longer to capture a single image, has no user control, and may have other artifacts depending on the HDR method used. Therefore, HDR captures operate at a much slower rate than regular captures. In this mode, on LIMITED or FULL devices, when a request is made with a ACAMERA_CONTROL_CAPTURE_INTENT of STILL_CAPTURE, the camera device will capture an image using a high dynamic range capture technique. On LEGACY devices, captures that target a JPEG-format output will be captured with HDR, and the capture intent is not relevant. The HDR capture may involve the device capturing a burst of images internally and combining them into one, or it may involve the device using specialized high dynamic range capture hardware. In all cases, a single image is produced in response to a capture request submitted while in HDR mode. Since substantial post-processing is generally needed to produce an HDR image, only YUV, PRIVATE, and JPEG outputs are supported for LIMITED/FULL device HDR captures, and only JPEG outputs are supported for LEGACY HDR captures. Using a RAW output for HDR capture is not supported. Some devices may also support always-on HDR, which applies HDR processing at full frame rate. For these devices, intents other than STILL_CAPTURE will also produce an HDR output with no frame rate impact compared to normal operation, though the quality may be lower than for STILL_CAPTURE intents. If SCENE_MODE_HDR is used with unsupported output types or capture intents, the images captured will be as if the SCENE_MODE was not enabled at all. See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_CONTROL_SCENE_MODE_LANDSCAPE
|
Optimized for photos of distant macroscopic objects. |
ACAMERA_CONTROL_SCENE_MODE_NIGHT
|
Optimized for low-light settings. |
ACAMERA_CONTROL_SCENE_MODE_NIGHT_PORTRAIT
|
Optimized for still photos of people in low-light settings. |
ACAMERA_CONTROL_SCENE_MODE_PARTY
|
Optimized for dim, indoor settings with multiple moving people. |
ACAMERA_CONTROL_SCENE_MODE_PORTRAIT
|
Optimized for still photos of people. |
ACAMERA_CONTROL_SCENE_MODE_SNOW
|
Optimized for bright, outdoor settings containing snow. |
ACAMERA_CONTROL_SCENE_MODE_SPORTS
|
Optimized for photos of quickly moving people. Similar to ACTION. |
ACAMERA_CONTROL_SCENE_MODE_STEADYPHOTO
|
Optimized to avoid blurry photos due to small amounts of device motion (for example: due to hand shake). |
ACAMERA_CONTROL_SCENE_MODE_SUNSET
|
Optimized for scenes of the setting sun. |
ACAMERA_CONTROL_SCENE_MODE_THEATRE
|
Optimized for dim, indoor settings where flash must remain off. |
acamera_metadata_enum_acamera_control_settings_override
acamera_metadata_enum_acamera_control_settings_override
Properties | |
---|---|
ACAMERA_CONTROL_SETTINGS_OVERRIDE_OFF
|
No keys are applied sooner than the other keys when applying CaptureRequest settings to the camera device. This is the default value. |
ACAMERA_CONTROL_SETTINGS_OVERRIDE_ZOOM
|
Zoom related keys are applied sooner than the other keys in the CaptureRequest. The zoom related keys are:
Even though ACAMERA_CONTROL_AE_REGIONS, ACAMERA_CONTROL_AWB_REGIONS, and ACAMERA_CONTROL_AF_REGIONS are not directly zoom related, applications typically scale these regions together with ACAMERA_SCALER_CROP_REGION to have a consistent mapping within the current field of view. In this aspect, they are related to ACAMERA_SCALER_CROP_REGION and ACAMERA_CONTROL_ZOOM_RATIO. See also: ACAMERA_CONTROL_AE_REGIONS See also: ACAMERA_CONTROL_AF_REGIONS See also: ACAMERA_CONTROL_AWB_REGIONS See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_SCALER_CROP_REGION |
acamera_metadata_enum_acamera_control_video_stabilization_mode
acamera_metadata_enum_acamera_control_video_stabilization_mode
acamera_metadata_enum_acamera_depth_available_depth_stream_configurations
acamera_metadata_enum_acamera_depth_available_depth_stream_configurations
acamera_metadata_enum_acamera_depth_available_depth_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_depth_available_depth_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations
acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations
acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_depth_available_dynamic_depth_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_depth_depth_is_exclusive
acamera_metadata_enum_acamera_depth_depth_is_exclusive
acamera_metadata_enum_acamera_distortion_correction_mode
acamera_metadata_enum_acamera_distortion_correction_mode
acamera_metadata_enum_acamera_edge_mode
acamera_metadata_enum_acamera_edge_mode
Properties | |
---|---|
ACAMERA_EDGE_MODE_FAST
|
Apply edge enhancement at a quality level that does not slow down frame rate relative to sensor output. It may be the same as OFF if edge enhancement will slow down frame rate relative to sensor. |
ACAMERA_EDGE_MODE_HIGH_QUALITY
|
Apply high-quality edge enhancement, at a cost of possibly reduced output frame rate. |
ACAMERA_EDGE_MODE_OFF
|
No edge enhancement is applied. |
ACAMERA_EDGE_MODE_ZERO_SHUTTER_LAG
|
Edge enhancement is applied at different levels for different output streams, based on resolution. Streams at maximum recording resolution (see ACameraDevice_createCaptureSession) or below have edge enhancement applied, while higher-resolution streams have no edge enhancement applied. The level of edge enhancement for low-resolution streams is tuned so that frame rate is not impacted, and the quality is equal to or better than FAST (since it is only applied to lower-resolution outputs, quality may improve from FAST). This mode is intended to be used by applications operating in a zero-shutter-lag mode with YUV or PRIVATE reprocessing, where the application continuously captures high-resolution intermediate buffers into a circular buffer, from which a final image is produced via reprocessing when a user takes a picture. For such a use case, the high-resolution buffers must not have edge enhancement applied to maximize efficiency of preview and to avoid double-applying enhancement when reprocessed, while low-resolution buffers (used for recording or preview, generally) need edge enhancement applied for reasonable preview quality. This mode is guaranteed to be supported by devices that support either the YUV_REPROCESSING or PRIVATE_REPROCESSING capabilities (ACAMERA_REQUEST_AVAILABLE_CAPABILITIES lists either of those capabilities) and it will be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template. See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
acamera_metadata_enum_acamera_flash_info_available
acamera_metadata_enum_acamera_flash_info_available
acamera_metadata_enum_acamera_flash_mode
acamera_metadata_enum_acamera_flash_mode
acamera_metadata_enum_acamera_flash_state
acamera_metadata_enum_acamera_flash_state
acamera_metadata_enum_acamera_heic_available_heic_stream_configurations
acamera_metadata_enum_acamera_heic_available_heic_stream_configurations
acamera_metadata_enum_acamera_heic_available_heic_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_heic_available_heic_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_hot_pixel_mode
acamera_metadata_enum_acamera_hot_pixel_mode
Properties | |
---|---|
ACAMERA_HOT_PIXEL_MODE_FAST
|
Hot pixel correction is applied, without reducing frame rate relative to sensor raw output. The hotpixel map may be returned in ACAMERA_STATISTICS_HOT_PIXEL_MAP. See also: ACAMERA_STATISTICS_HOT_PIXEL_MAP |
ACAMERA_HOT_PIXEL_MODE_HIGH_QUALITY
|
High-quality hot pixel correction is applied, at a cost of possibly reduced frame rate relative to sensor raw output. The hotpixel map may be returned in ACAMERA_STATISTICS_HOT_PIXEL_MAP. See also: ACAMERA_STATISTICS_HOT_PIXEL_MAP |
ACAMERA_HOT_PIXEL_MODE_OFF
|
No hot pixel correction is applied. The frame rate must not be reduced relative to sensor raw output for this option. The hotpixel map may be returned in ACAMERA_STATISTICS_HOT_PIXEL_MAP. See also: ACAMERA_STATISTICS_HOT_PIXEL_MAP |
acamera_metadata_enum_acamera_info_supported_hardware_level
acamera_metadata_enum_acamera_info_supported_hardware_level
Properties | |
---|---|
ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL_3
|
This camera device is capable of YUV reprocessing and RAW data capture, in addition to FULL-level capabilities. The stream configurations listed in the The following additional capabilities are guaranteed to be supported:
See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL_EXTERNAL
|
This camera device is backed by an external camera connected to this Android device. The device has capability identical to a LIMITED level device, with the following exceptions:
See also: ACAMERA_LENS_FOCAL_LENGTH See also: ACAMERA_LENS_INFO_HYPERFOCAL_DISTANCE See also: ACAMERA_SENSOR_BLACK_LEVEL_PATTERN See also: ACAMERA_SENSOR_INFO_COLOR_FILTER_ARRANGEMENT See also: ACAMERA_SENSOR_INFO_PHYSICAL_SIZE See also: ACAMERA_SENSOR_INFO_WHITE_LEVEL See also: ACAMERA_SENSOR_ORIENTATION See also: ACAMERA_SENSOR_ROLLING_SHUTTER_SKEW |
ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL_FULL
|
This camera device is capable of supporting advanced imaging applications. The stream configurations listed in the A
Note: Pre-API level 23, FULL devices also supported arbitrary cropping region (ACAMERA_SCALER_CROPPING_TYPE See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES See also: ACAMERA_SCALER_CROPPING_TYPE See also: ACAMERA_SENSOR_INFO_EXPOSURE_TIME_RANGE See also: ACAMERA_SENSOR_INFO_MAX_FRAME_DURATION See also: ACAMERA_SYNC_MAX_LATENCY |
ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL_LEGACY
|
This camera device is running in backward compatibility mode. Only the stream configurations listed in the A In addition, the ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER is not functional on Devices that initially shipped with Android version Q or newer will not include any LEGACY-level devices. See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
|
This camera device does not have enough capabilities to qualify as a Only the stream configurations listed in the All
A Additional capabilities may optionally be supported by a See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AWB_MODE See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations
acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations
acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_jpegr_available_jpeg_r_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_lens_facing
acamera_metadata_enum_acamera_lens_facing
acamera_metadata_enum_acamera_lens_info_focus_distance_calibration
acamera_metadata_enum_acamera_lens_info_focus_distance_calibration
Properties | |
---|---|
ACAMERA_LENS_INFO_FOCUS_DISTANCE_CALIBRATION_APPROXIMATE
|
The lens focus distance is measured in diopters. However, setting the lens to the same focus distance on separate occasions may result in a different real focus distance, depending on factors such as the orientation of the device, the age of the focusing mechanism, and the device temperature. |
ACAMERA_LENS_INFO_FOCUS_DISTANCE_CALIBRATION_CALIBRATED
|
The lens focus distance is measured in diopters, and is calibrated. The lens mechanism is calibrated so that setting the same focus distance is repeatable on multiple occasions with good accuracy, and the focus distance corresponds to the real physical distance to the plane of best focus. |
ACAMERA_LENS_INFO_FOCUS_DISTANCE_CALIBRATION_UNCALIBRATED
|
The lens focus distance is not accurate, and the units used for ACAMERA_LENS_FOCUS_DISTANCE do not correspond to any physical units. Setting the lens to the same focus distance on separate occasions may result in a different real focus distance, depending on factors such as the orientation of the device, the age of the focusing mechanism, and the device temperature. The focus distance value will still be in the range of See also: ACAMERA_LENS_FOCUS_DISTANCE See also: ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE |
acamera_metadata_enum_acamera_lens_optical_stabilization_mode
acamera_metadata_enum_acamera_lens_optical_stabilization_mode
acamera_metadata_enum_acamera_lens_pose_reference
acamera_metadata_enum_acamera_lens_pose_reference
Properties | |
---|---|
ACAMERA_LENS_POSE_REFERENCE_AUTOMOTIVE
|
The value of ACAMERA_LENS_POSE_TRANSLATION is relative to the origin of the automotive sensor coordinate system, which is at the center of the rear axle. See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_LENS_POSE_REFERENCE_GYROSCOPE
|
The value of ACAMERA_LENS_POSE_TRANSLATION is relative to the position of the primary gyroscope of this Android device. See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_LENS_POSE_REFERENCE_PRIMARY_CAMERA
|
The value of ACAMERA_LENS_POSE_TRANSLATION is relative to the optical center of the largest camera device facing the same direction as this camera. This is the default value for API levels before Android P. See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_LENS_POSE_REFERENCE_UNDEFINED
|
The camera device cannot represent the values of ACAMERA_LENS_POSE_TRANSLATION and ACAMERA_LENS_POSE_ROTATION accurately enough. One such example is a camera device on the cover of a foldable phone: in order to measure the pose translation and rotation, some kind of hinge position sensor would be needed. The value of ACAMERA_LENS_POSE_TRANSLATION must be all zeros, and ACAMERA_LENS_POSE_ROTATION must be values matching its default facing. See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
acamera_metadata_enum_acamera_lens_state
acamera_metadata_enum_acamera_lens_state
Properties | |
---|---|
ACAMERA_LENS_STATE_MOVING
|
One or several of the lens parameters (ACAMERA_LENS_FOCAL_LENGTH, ACAMERA_LENS_FOCUS_DISTANCE, ACAMERA_LENS_FILTER_DENSITY or ACAMERA_LENS_APERTURE) is currently changing. See also: ACAMERA_LENS_APERTURE See also: ACAMERA_LENS_FILTER_DENSITY See also: ACAMERA_LENS_FOCAL_LENGTH See also: ACAMERA_LENS_FOCUS_DISTANCE |
ACAMERA_LENS_STATE_STATIONARY
|
The lens parameters (ACAMERA_LENS_FOCAL_LENGTH, ACAMERA_LENS_FOCUS_DISTANCE, ACAMERA_LENS_FILTER_DENSITY and ACAMERA_LENS_APERTURE) are not changing. See also: ACAMERA_LENS_APERTURE See also: ACAMERA_LENS_FILTER_DENSITY See also: ACAMERA_LENS_FOCAL_LENGTH See also: ACAMERA_LENS_FOCUS_DISTANCE |
acamera_metadata_enum_acamera_logical_multi_camera_sensor_sync_type
acamera_metadata_enum_acamera_logical_multi_camera_sensor_sync_type
acamera_metadata_enum_acamera_noise_reduction_mode
acamera_metadata_enum_acamera_noise_reduction_mode
Properties | |
---|---|
ACAMERA_NOISE_REDUCTION_MODE_FAST
|
Noise reduction is applied without reducing frame rate relative to sensor output. It may be the same as OFF if noise reduction will reduce frame rate relative to sensor. |
ACAMERA_NOISE_REDUCTION_MODE_HIGH_QUALITY
|
High-quality noise reduction is applied, at the cost of possibly reduced frame rate relative to sensor output. |
ACAMERA_NOISE_REDUCTION_MODE_MINIMAL
|
MINIMAL noise reduction is applied without reducing frame rate relative to sensor output. |
ACAMERA_NOISE_REDUCTION_MODE_OFF
|
No noise reduction is applied. |
ACAMERA_NOISE_REDUCTION_MODE_ZERO_SHUTTER_LAG
|
Noise reduction is applied at different levels for different output streams, based on resolution. Streams at maximum recording resolution (see ACameraDevice_createCaptureSession) or below have noise reduction applied, while higher-resolution streams have MINIMAL (if supported) or no noise reduction applied (if MINIMAL is not supported.) The degree of noise reduction for low-resolution streams is tuned so that frame rate is not impacted, and the quality is equal to or better than FAST (since it is only applied to lower-resolution outputs, quality may improve from FAST). This mode is intended to be used by applications operating in a zero-shutter-lag mode with YUV or PRIVATE reprocessing, where the application continuously captures high-resolution intermediate buffers into a circular buffer, from which a final image is produced via reprocessing when a user takes a picture. For such a use case, the high-resolution buffers must not have noise reduction applied to maximize efficiency of preview and to avoid over-applying noise filtering when reprocessing, while low-resolution buffers (used for recording or preview, generally) need noise reduction applied for reasonable preview quality. This mode is guaranteed to be supported by devices that support either the YUV_REPROCESSING or PRIVATE_REPROCESSING capabilities (ACAMERA_REQUEST_AVAILABLE_CAPABILITIES lists either of those capabilities) and it will be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template. See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
acamera_metadata_enum_acamera_request_available_capabilities
acamera_metadata_enum_acamera_request_available_capabilities
Properties | |
---|---|
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE
|
The minimal set of capabilities that every camera device (regardless of ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL) supports. This capability is listed by all normal devices, and indicates that the camera device has a feature set that's comparable to the baseline requirements for the older android.hardware.Camera API. Devices with the DEPTH_OUTPUT capability might not list this capability, indicating that they support only depth measurement, not standard color output. See also: ACAMERA_INFO_SUPPORTED_HARDWARE_LEVEL |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_BURST_CAPTURE
|
The camera device supports capturing high-resolution images at >= 20 frames per second, in at least the uncompressed YUV format, when post-processing settings are set to FAST. Additionally, all image resolutions less than 24 megapixels can be captured at >= 10 frames per second. Here, 'high resolution' means at least 8 megapixels, or the maximum resolution of the device, whichever is smaller. More specifically, this means that at least one output AIMAGE_FORMAT_YUV_420_888 size listed in ACAMERA_SCALER_AVAILABLE_STREAM_CONFIGURATIONS is larger or equal to the 'high resolution' defined above, and can be captured at at least 20 fps. For the largest AIMAGE_FORMAT_YUV_420_888 size listed in ACAMERA_SCALER_AVAILABLE_STREAM_CONFIGURATIONS, camera device can capture this size for at least 10 frames per second if the size is less than 24 megapixels. Also the ACAMERA_CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES entry lists at least one FPS range where the minimum FPS is >= 1 / minimumFrameDuration for the largest YUV_420_888 size. If the device supports the AIMAGE_FORMAT_RAW10, AIMAGE_FORMAT_RAW12, AIMAGE_FORMAT_Y8, then those can also be captured at the same rate as the maximum-size YUV_420_888 resolution is. In addition, the ACAMERA_SYNC_MAX_LATENCY field is guaranteed to have a value between 0 and 4, inclusive. ACAMERA_CONTROL_AE_LOCK_AVAILABLE and ACAMERA_CONTROL_AWB_LOCK_AVAILABLE are also guaranteed to be See also: ACAMERA_CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES See also: ACAMERA_CONTROL_AE_LOCK_AVAILABLE See also: ACAMERA_CONTROL_AWB_LOCK_AVAILABLE See also: ACAMERA_SYNC_MAX_LATENCY |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_DEPTH_OUTPUT
|
The camera device can produce depth measurements from its field of view. This capability requires the camera device to support the following:
Generally, depth output operates at a slower frame rate than standard color capture, so the DEPTH16 and DEPTH_POINT_CLOUD formats will commonly have a stall duration that should be accounted for (see ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS). On a device that supports both depth and color-based output, to enable smooth preview, using a repeating burst is recommended, where a depth-output target is only included once every N frames, where N is the ratio between preview output rate and depth output rate, including depth stall time. See also: ACAMERA_DEPTH_DEPTH_IS_EXCLUSIVE See also: ACAMERA_LENS_DISTORTION See also: ACAMERA_LENS_FACING See also: ACAMERA_LENS_INTRINSIC_CALIBRATION See also: ACAMERA_LENS_POSE_REFERENCE See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA
|
The camera device is a logical camera backed by two or more physical cameras. In API level 28, the physical cameras must also be exposed to the application via CameraManager::getCameraIdList. Starting from API level 29:
Combinations of logical and physical streams, or physical streams from different physical cameras are not guaranteed. However, if the camera device supports ACameraDevice_isSessionConfigurationSupported, application must be able to query whether a stream combination involving physical streams is supported by calling ACameraDevice_isSessionConfigurationSupported. Camera application shouldn't assume that there are at most 1 rear camera and 1 front camera in the system. For an application that switches between front and back cameras, the recommendation is to switch between the first rear camera and the first front camera in the list of supported camera devices. This capability requires the camera device to support the following:
A logical camera device's dynamic metadata may contain ACAMERA_LOGICAL_MULTI_CAMERA_ACTIVE_PHYSICAL_ID to notify the application of the current active physical camera Id. An active physical camera is the physical camera from which the logical camera's main image data outputs (YUV or RAW) and metadata come from. In addition, this serves as an indication which physical camera is used to output to a RAW stream, or in case only physical cameras support RAW, which physical RAW stream the application should request. Logical camera's static metadata tags below describe the default active physical camera. An active physical camera is default if it's used when application directly uses requests built from a template. All templates will default to the same active physical camera.
The field of view of non-RAW physical streams must not be smaller than that of the non-RAW logical streams, or the maximum field-of-view of the physical camera, whichever is smaller. The application should check the physical capture result metadata for how the physical streams are cropped or zoomed. More specifically, given the physical camera result metadata, the effective horizontal field-of-view of the physical camera is:
where the equation parameters are the physical camera's crop region width, physical sensor width, zoom ratio, active array width, and focal length respectively. Typically the physical stream of active physical camera has the same field-of-view as the logical streams. However, the same may not be true for physical streams from non-active physical cameras. For example, if the logical camera has a wide-ultrawide configuration where the wide lens is the default, when the crop region is set to the logical camera's active array size, (and the zoom ratio set to 1.0 starting from Android 11), a physical stream for the ultrawide camera may prefer outputting images with larger field-of-view than that of the wide camera for better stereo matching margin or more robust motion tracking. At the same time, the physical non-RAW streams' field of view must not be smaller than the requested crop region and zoom ratio, as long as it's within the physical lens' capability. For example, for a logical camera with wide-tele lens configuration where the wide lens is the default, if the logical camera's crop region is set to maximum size, and zoom ratio set to 1.0, the physical stream for the tele lens will be configured to its maximum size crop region (no zoom). Deprecated: Prior to Android 11, the field of view of all non-RAW physical streams cannot be larger than that of non-RAW logical streams. If the logical camera has a wide-ultrawide lens configuration where the wide lens is the default, when the logical camera's crop region is set to maximum size, the FOV of the physical streams for the ultrawide lens will be the same as the logical stream, by making the crop region smaller than its active array size to compensate for the smaller focal length. For a logical camera, typically the underlying physical cameras have different RAW capabilities (such as resolution or CFA pattern). There are two ways for the application to capture RAW images from the logical camera:
The capture request and result metadata tags required for backward compatible camera functionalities will be solely based on the logical camera capability. On the other hand, the use of manual capture controls (sensor or post-processing) with a logical camera may result in unexpected behavior when the HAL decides to switch between physical cameras with different characteristics under the hood. For example, when the application manually sets exposure time and sensitivity while zooming in, the brightness of the camera images may suddenly change because HAL switches from one physical camera to the other. See also: ACAMERA_LENS_DISTORTION See also: ACAMERA_LENS_INFO_FOCUS_DISTANCE_CALIBRATION See also: ACAMERA_LENS_INFO_HYPERFOCAL_DISTANCE See also: ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE See also: ACAMERA_LENS_INTRINSIC_CALIBRATION See also: ACAMERA_LENS_POSE_REFERENCE See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION See also: ACAMERA_LOGICAL_MULTI_CAMERA_ACTIVE_PHYSICAL_ID See also: ACAMERA_LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE See also: ACAMERA_SENSOR_AVAILABLE_TEST_PATTERN_MODES See also: ACAMERA_SENSOR_BLACK_LEVEL_PATTERN See also: ACAMERA_SENSOR_CALIBRATION_TRANSFORM1 See also: ACAMERA_SENSOR_CALIBRATION_TRANSFORM2 See also: ACAMERA_SENSOR_COLOR_TRANSFORM1 See also: ACAMERA_SENSOR_COLOR_TRANSFORM2 See also: ACAMERA_SENSOR_FORWARD_MATRIX1 See also: ACAMERA_SENSOR_FORWARD_MATRIX2 See also: ACAMERA_SENSOR_INFO_COLOR_FILTER_ARRANGEMENT See also: ACAMERA_SENSOR_INFO_EXPOSURE_TIME_RANGE See also: ACAMERA_SENSOR_INFO_LENS_SHADING_APPLIED See also: ACAMERA_SENSOR_INFO_MAX_FRAME_DURATION See also: ACAMERA_SENSOR_INFO_PHYSICAL_SIZE See also: ACAMERA_SENSOR_INFO_SENSITIVITY_RANGE See also: ACAMERA_SENSOR_INFO_WHITE_LEVEL See also: ACAMERA_SENSOR_MAX_ANALOG_SENSITIVITY See also: ACAMERA_SENSOR_OPTICAL_BLACK_REGIONS See also: ACAMERA_SENSOR_REFERENCE_ILLUMINANT1 See also: ACAMERA_SENSOR_REFERENCE_ILLUMINANT2 |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_MANUAL_POST_PROCESSING
|
The camera device post-processing stages can be manually controlled. The camera device supports basic manual control of the image post-processing stages. This means the following controls are guaranteed to be supported:
If auto white balance is enabled, then the camera device will accurately report the values applied by AWB in the result. A given camera device may also support additional post-processing controls, but this capability only covers the above list of controls. For camera devices with LOGICAL_MULTI_CAMERA capability, when underlying active physical camera switches, tonemap, white balance, and shading map may change even if awb is locked. However, the overall post-processing experience for users will be consistent. Refer to LOGICAL_MULTI_CAMERA capability for details. See also: ACAMERA_COLOR_CORRECTION_ABERRATION_MODE See also: ACAMERA_COLOR_CORRECTION_AVAILABLE_ABERRATION_MODES See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM See also: ACAMERA_CONTROL_AWB_LOCK See also: ACAMERA_LENS_INFO_SHADING_MAP_SIZE See also: ACAMERA_SHADING_MODE See also: ACAMERA_STATISTICS_LENS_SHADING_MAP See also: ACAMERA_STATISTICS_LENS_SHADING_MAP_MODE See also: ACAMERA_TONEMAP_GAMMA See also: ACAMERA_TONEMAP_MAX_CURVE_POINTS See also: ACAMERA_TONEMAP_MODE See also: ACAMERA_TONEMAP_PRESET_CURVE |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR
|
The camera device can be manually controlled (3A algorithms such as auto-exposure, and auto-focus can be bypassed). The camera device supports basic manual control of the sensor image acquisition related stages. This means the following controls are guaranteed to be supported:
If any of the above 3A algorithms are enabled, then the camera device will accurately report the values applied by 3A in the result. A given camera device may also support additional manual sensor controls, but this capability only covers the above list of controls. If this is supported, android.scaler.streamConfigurationMap will additionally return a min frame duration that is greater than zero for each supported size-format combination. For camera devices with LOGICAL_MULTI_CAMERA capability, when the underlying active physical camera switches, exposureTime, sensitivity, and lens properties may change even if AE/AF is locked. However, the overall auto exposure and auto focus experience for users will be consistent. Refer to LOGICAL_MULTI_CAMERA capability for details. See also: ACAMERA_BLACK_LEVEL_LOCK See also: ACAMERA_CONTROL_AE_LOCK See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_FRAME_DURATION See also: ACAMERA_SENSOR_INFO_EXPOSURE_TIME_RANGE See also: ACAMERA_SENSOR_INFO_MAX_FRAME_DURATION See also: ACAMERA_SENSOR_INFO_SENSITIVITY_RANGE See also: ACAMERA_SENSOR_SENSITIVITY |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_MONOCHROME
|
The camera device is a monochrome camera that doesn't contain a color filter array, and for YUV_420_888 stream, the pixel values on U and V planes are all 128. A MONOCHROME camera must support the guaranteed stream combinations required for its device level and capabilities. Additionally, if the monochrome camera device supports Y8 format, all mandatory stream combination requirements related to YUV_420_888 apply to Y8 as well. There are no mandatory stream combination requirements with regard to Y8 for Bayer camera devices. Starting from Android Q, the SENSOR_INFO_COLOR_FILTER_ARRANGEMENT of a MONOCHROME camera will be either MONO or NIR. |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING
|
The camera device supports the MOTION_TRACKING value for ACAMERA_CONTROL_CAPTURE_INTENT, which limits maximum exposure time to 20 ms. This limits the motion blur of capture images, resulting in better image tracking results for use cases such as image stabilization or augmented reality. See also: ACAMERA_CONTROL_CAPTURE_INTENT |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_RAW
|
The camera device supports outputting RAW buffers and metadata for interpreting them. Devices supporting the RAW capability allow both for saving DNG files, and for direct application processing of raw sensor images.
See also: ACAMERA_SENSOR_INFO_PIXEL_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_READ_SENSOR_SETTINGS
|
The camera device supports accurately reporting the sensor settings for many of the sensor controls while the built-in 3A algorithm is running. This allows reporting of sensor settings even when these settings cannot be manually changed. The values reported for the following controls are guaranteed to be available in the CaptureResult, including when 3A is enabled:
This capability is a subset of the MANUAL_SENSOR control capability, and will always be included if the MANUAL_SENSOR capability is available. See also: ACAMERA_LENS_APERTURE See also: ACAMERA_LENS_FOCUS_DISTANCE See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_SENSITIVITY |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_SECURE_IMAGE_DATA
|
The camera device is capable of writing image data into a region of memory inaccessible to Android userspace or the Android kernel, and only accessible to trusted execution environments (TEE). |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_STREAM_USE_CASE
|
The camera device supports selecting a per-stream use case via OutputConfiguration::setStreamUseCase so that the device can optimize camera pipeline parameters such as tuning, sensor mode, or ISP settings for a specific user scenario. Some sample usages of this capability are:
This capability requires the camera device to support the following stream use cases:
CameraCharacteristics::SCALER_AVAILABLE_STREAM_USE_CASES lists all of the supported stream use cases. Refer to the guideline for the mandatory stream combinations involving stream use cases, which can also be queried via MandatoryStreamCombination. |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_SYSTEM_CAMERA
|
The camera device is only accessible by Android's system components and privileged applications. Processes need to have the android.permission.SYSTEM_CAMERA in addition to android.permission.CAMERA in order to connect to this camera device. |
ACAMERA_REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR
|
This camera device is capable of producing ultra high resolution images in addition to the image sizes described in the android.scaler.streamConfigurationMap. It can operate in 'default' mode and 'max resolution' mode. It generally does this by binning pixels in 'default' mode and not binning them in 'max resolution' mode. See also: ACAMERA_SENSOR_INFO_PIXEL_ARRAY_SIZE |
acamera_metadata_enum_acamera_request_available_color_space_profiles_map
acamera_metadata_enum_acamera_request_available_color_space_profiles_map
acamera_metadata_enum_acamera_request_available_dynamic_range_profiles_map
acamera_metadata_enum_acamera_request_available_dynamic_range_profiles_map
acamera_metadata_enum_acamera_scaler_available_recommended_stream_configurations
acamera_metadata_enum_acamera_scaler_available_recommended_stream_configurations
Properties | |
---|---|
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_10BIT_OUTPUT
|
If supported, the recommended 10-bit output stream configurations must include a subset of the advertised ImageFormat::YCBCR_P010 and ImageFormat::PRIVATE outputs that are optimized for power and performance when registered along with a supported 10-bit dynamic range profile. see android.hardware.camera2.params.OutputConfiguration::setDynamicRangeProfile for details. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_LOW_LATENCY_SNAPSHOT
|
If supported, the recommended low latency stream configurations must have end-to-end latency that does not exceed 200 ms. under standard operating conditions (reasonable light levels, not loaded system) and using template TEMPLATE_STILL_CAPTURE. This is primarily for listing configurations for the JPEG output format however other supported output formats can be added as well. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_PREVIEW
|
Preview must only include non-stalling processed stream configurations with output formats like AIMAGE_FORMAT_YUV_420_888, AIMAGE_FORMAT_PRIVATE, etc. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_PUBLIC_END
|
|
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_PUBLIC_END_3_8
|
|
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_RAW
|
If supported, recommended raw stream configurations must only include RAW based output formats. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_RECORD
|
Video record must include stream configurations that match the advertised supported media profiles CamcorderProfile with IMPLEMENTATION_DEFINED format. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_SNAPSHOT
|
Recommended snapshot stream configurations must include at least one with size close to ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE and JPEG output format. Taking into account restrictions on aspect ratio, alignment etc. the area of the maximum suggested size shouldn’t be less than 97% of the sensor array size area. See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_VENDOR_START
|
Vendor defined use cases. These depend on the vendor implementation. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_VIDEO_SNAPSHOT
|
Video snapshot must include stream configurations at least as big as the maximum RECORD resolutions and only with JPEG output format. Additionally the configurations shouldn't cause preview glitches and also be able to run at 30 fps. |
ACAMERA_SCALER_AVAILABLE_RECOMMENDED_STREAM_CONFIGURATIONS_ZSL
|
If supported, recommended input stream configurations must only be advertised with ZSL along with other processed and/or stalling output formats. |
acamera_metadata_enum_acamera_scaler_available_stream_configurations
acamera_metadata_enum_acamera_scaler_available_stream_configurations
acamera_metadata_enum_acamera_scaler_available_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_scaler_available_stream_configurations_maximum_resolution
acamera_metadata_enum_acamera_scaler_available_stream_use_cases
acamera_metadata_enum_acamera_scaler_available_stream_use_cases
Properties | |
---|---|
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_CROPPED_RAW
|
Cropped RAW stream when the client chooses to crop the field of view. Certain types of image sensors can run in binned modes in order to improve signal to noise ratio while capturing frames. However, at certain zoom levels and / or when other scene conditions are deemed fit, the camera sub-system may choose to un-bin and remosaic the sensor's output. This results in a RAW frame which is cropped in field of view and yet has the same number of pixels as full field of view RAW, thereby improving image detail. The resultant field of view of the RAW stream will be greater than or equal to croppable non-RAW streams. The effective crop region for this RAW stream will be reflected in the CaptureResult key ACAMERA_SCALER_RAW_CROP_REGION. If this stream use case is set on a non-RAW stream, i.e. not one of :
session configuration is not guaranteed to succeed. This stream use case may not be supported on some devices. See also: ACAMERA_SCALER_RAW_CROP_REGION |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_DEFAULT
|
Default stream use case. This use case is the same as when the application doesn't set any use case for the stream. The camera device uses the properties of the output target, such as format, dataSpace, or surface class type, to optimize the image processing pipeline. |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_PREVIEW
|
Live stream shown to the user. Optimized for performance and usability as a viewfinder, but not necessarily for image quality. The output is not meant to be persisted as saved images or video. No stall if ACAMERA_CONTROL_* are set to FAST. There may be stall if they are set to HIGH_QUALITY. This use case has the same behavior as the default SurfaceView and SurfaceTexture targets. Additionally, this use case can be used for in-app image analysis. |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_PREVIEW_VIDEO_STILL
|
One single stream used for combined purposes of preview, video, and still capture. For such multi-purpose streams, the camera device aims to make the best tradeoff between the individual use cases. For example, the STILL_CAPTURE use case by itself may have stalls for achieving best image quality. But if combined with PREVIEW and VIDEO_RECORD, the camera device needs to trade off the additional image processing for speed so that preview and video recording aren't slowed down. Similarly, VIDEO_RECORD may produce frames with a substantial lag, but PREVIEW_VIDEO_STILL must have minimal output delay. This means that to enable video stabilization with this use case, the device must support and the app must select the PREVIEW_STABILIZATION mode for video stabilization. |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_STILL_CAPTURE
|
Still photo capture. Optimized for high-quality high-resolution capture, and not expected to maintain preview-like frame rates. The stream may have stalls regardless of whether ACAMERA_CONTROL_* is HIGH_QUALITY. This use case has the same behavior as the default JPEG and RAW related formats. |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_VIDEO_CALL
|
Long-running video call optimized for both power efficiency and video quality. The camera sensor may run in a lower-resolution mode to reduce power consumption at the cost of some image and digital zoom quality. Unlike VIDEO_RECORD, VIDEO_CALL outputs are expected to work in dark conditions, so are usually accompanied with variable frame rate settings to allow sufficient exposure time in low light. |
ACAMERA_SCALER_AVAILABLE_STREAM_USE_CASES_VIDEO_RECORD
|
Recording video clips. Optimized for high-quality video capture, including high-quality image stabilization if supported by the device and enabled by the application. As a result, may produce output frames with a substantial lag from real time, to allow for highest-quality stabilization or other processing. As such, such an output is not suitable for drawing to screen directly, and is expected to be persisted to disk or similar for later playback or processing. Only streams that set the VIDEO_RECORD use case are guaranteed to have video stabilization applied when the video stabilization control is set to ON, as opposed to PREVIEW_STABILIZATION. This use case has the same behavior as the default MediaRecorder and MediaCodec targets. |
acamera_metadata_enum_acamera_scaler_cropping_type
acamera_metadata_enum_acamera_scaler_cropping_type
acamera_metadata_enum_acamera_scaler_multi_resolution_stream_supported
acamera_metadata_enum_acamera_scaler_multi_resolution_stream_supported
acamera_metadata_enum_acamera_scaler_physical_camera_multi_resolution_stream_configurations
acamera_metadata_enum_acamera_scaler_physical_camera_multi_resolution_stream_configurations
acamera_metadata_enum_acamera_scaler_rotate_and_crop
acamera_metadata_enum_acamera_scaler_rotate_and_crop
acamera_metadata_enum_acamera_sensor_info_color_filter_arrangement
acamera_metadata_enum_acamera_sensor_info_color_filter_arrangement
acamera_metadata_enum_acamera_sensor_info_lens_shading_applied
acamera_metadata_enum_acamera_sensor_info_lens_shading_applied
acamera_metadata_enum_acamera_sensor_info_timestamp_source
acamera_metadata_enum_acamera_sensor_info_timestamp_source
Properties | |
---|---|
ACAMERA_SENSOR_INFO_TIMESTAMP_SOURCE_REALTIME
|
Timestamps from ACAMERA_SENSOR_TIMESTAMP are in the same timebase as SystemClock::elapsedRealtimeNanos, and they can be compared to other timestamps using that base. When buffers from a REALTIME device are passed directly to a video encoder from the camera, automatic compensation is done to account for differing timebases of the audio and camera subsystems. If the application is receiving buffers and then later sending them to a video encoder or other application where they are compared with audio subsystem timestamps or similar, this compensation is not present. In those cases, applications need to adjust the timestamps themselves. Since SystemClock::elapsedRealtimeNanos and SystemClock::uptimeMillis only diverge while the device is asleep, an offset between the two sources can be measured once per active session and applied to timestamps for sufficient accuracy for A/V sync. See also: ACAMERA_SENSOR_TIMESTAMP |
ACAMERA_SENSOR_INFO_TIMESTAMP_SOURCE_UNKNOWN
|
Timestamps from ACAMERA_SENSOR_TIMESTAMP are in nanoseconds and monotonic, but can not be compared to timestamps from other subsystems (e.g. accelerometer, gyro etc.), or other instances of the same or different camera devices in the same system with accuracy. However, the timestamps are roughly in the same timebase as SystemClock::uptimeMillis. The accuracy is sufficient for tasks like A/V synchronization for video recording, at least, and the timestamps can be directly used together with timestamps from the audio subsystem for that task. Timestamps between streams and results for a single camera instance are comparable, and the timestamps for all buffers and the result metadata generated by a single capture are identical. See also: ACAMERA_SENSOR_TIMESTAMP |
acamera_metadata_enum_acamera_sensor_pixel_mode
acamera_metadata_enum_acamera_sensor_pixel_mode
acamera_metadata_enum_acamera_sensor_raw_binning_factor_used
acamera_metadata_enum_acamera_sensor_raw_binning_factor_used
Properties | |
---|---|
ACAMERA_SENSOR_RAW_BINNING_FACTOR_USED_FALSE
|
The |
ACAMERA_SENSOR_RAW_BINNING_FACTOR_USED_TRUE
|
The See also: ACAMERA_SENSOR_INFO_BINNING_FACTOR |
acamera_metadata_enum_acamera_sensor_reference_illuminant1
acamera_metadata_enum_acamera_sensor_reference_illuminant1
acamera_metadata_enum_acamera_sensor_test_pattern_mode
acamera_metadata_enum_acamera_sensor_test_pattern_mode
Properties | |
---|---|
ACAMERA_SENSOR_TEST_PATTERN_MODE_COLOR_BARS
|
All pixel data is replaced with an 8-bar color pattern. The vertical bars (left-to-right) are as follows:
In general the image would look like the following:
Each bar should take up 1/8 of the sensor pixel array width. When this is not possible, the bar size should be rounded down to the nearest integer and the pattern can repeat on the right side. Each bar's height must always take up the full sensor pixel array height. Each pixel in this test pattern must be set to either 0% intensity or 100% intensity. |
ACAMERA_SENSOR_TEST_PATTERN_MODE_COLOR_BARS_FADE_TO_GRAY
|
The test pattern is similar to COLOR_BARS, except that each bar should start at its specified color at the top, and fade to gray at the bottom. Furthermore each bar is further subdivided into a left and right half. The left half should have a smooth gradient, and the right half should have a quantized gradient. In particular, the right half's should consist of blocks of the same color for 1/16th active sensor pixel array width. The least significant bits in the quantized gradient should be copied from the most significant bits of the smooth gradient. The height of each bar should always be a multiple of 128. When this is not the case, the pattern should repeat at the bottom of the image. |
ACAMERA_SENSOR_TEST_PATTERN_MODE_CUSTOM1
|
The first custom test pattern. All custom patterns that are available only on this camera device are at least this numeric value. All of the custom test patterns will be static (that is the raw image must not vary from frame to frame). |
ACAMERA_SENSOR_TEST_PATTERN_MODE_OFF
|
No test pattern mode is used, and the camera device returns captures from the image sensor. This is the default if the key is not set. |
ACAMERA_SENSOR_TEST_PATTERN_MODE_PN9
|
All pixel data is replaced by a pseudo-random sequence generated from a PN9 512-bit sequence (typically implemented in hardware with a linear feedback shift register). The generator should be reset at the beginning of each frame, and thus each subsequent raw frame with this test pattern should be exactly the same as the last. |
ACAMERA_SENSOR_TEST_PATTERN_MODE_SOLID_COLOR
|
Each pixel in For example:
All green pixels are 100% green. All red/blue pixels are black.
All red pixels are 100% red. Only the odd green pixels are 100% green. All blue pixels are 100% black. See also: ACAMERA_SENSOR_TEST_PATTERN_DATA |
acamera_metadata_enum_acamera_shading_mode
acamera_metadata_enum_acamera_shading_mode
acamera_metadata_enum_acamera_statistics_face_detect_mode
acamera_metadata_enum_acamera_statistics_face_detect_mode
acamera_metadata_enum_acamera_statistics_hot_pixel_map_mode
acamera_metadata_enum_acamera_statistics_hot_pixel_map_mode
acamera_metadata_enum_acamera_statistics_lens_shading_map_mode
acamera_metadata_enum_acamera_statistics_lens_shading_map_mode
acamera_metadata_enum_acamera_statistics_ois_data_mode
acamera_metadata_enum_acamera_statistics_ois_data_mode
Properties | |
---|---|
ACAMERA_STATISTICS_OIS_DATA_MODE_OFF
|
Do not include OIS data in the capture result. |
ACAMERA_STATISTICS_OIS_DATA_MODE_ON
|
Include OIS data in the capture result. ACAMERA_STATISTICS_OIS_TIMESTAMPS, ACAMERA_STATISTICS_OIS_X_SHIFTS, and ACAMERA_STATISTICS_OIS_Y_SHIFTS provide OIS data in the output result metadata. See also: ACAMERA_STATISTICS_OIS_TIMESTAMPS See also: ACAMERA_STATISTICS_OIS_X_SHIFTS See also: ACAMERA_STATISTICS_OIS_Y_SHIFTS |
acamera_metadata_enum_acamera_statistics_scene_flicker
acamera_metadata_enum_acamera_statistics_scene_flicker
acamera_metadata_enum_acamera_sync_frame_number
acamera_metadata_enum_acamera_sync_frame_number
Properties | |
---|---|
ACAMERA_SYNC_FRAME_NUMBER_CONVERGING
|
The current result is not yet fully synchronized to any request. Synchronization is in progress, and reading metadata from this result may include a mix of data that have taken effect since the last synchronization time. In some future result, within ACAMERA_SYNC_MAX_LATENCY frames, this value will update to the actual frame number frame number the result is guaranteed to be synchronized to (as long as the request settings remain constant). See also: ACAMERA_SYNC_MAX_LATENCY |
ACAMERA_SYNC_FRAME_NUMBER_UNKNOWN
|
The current result's synchronization status is unknown. The result may have already converged, or it may be in progress. Reading from this result may include some mix of settings from past requests. After a settings change, the new settings will eventually all take effect for the output buffers and results. However, this value will not change when that happens. Altering settings rapidly may provide outcomes using mixes of settings from recent requests. This value is intended primarily for backwards compatibility with the older camera implementations (for android.hardware.Camera). |
acamera_metadata_enum_acamera_sync_max_latency
acamera_metadata_enum_acamera_sync_max_latency
acamera_metadata_enum_acamera_tonemap_mode
acamera_metadata_enum_acamera_tonemap_mode
Properties | |
---|---|
ACAMERA_TONEMAP_MODE_CONTRAST_CURVE
|
Use the tone mapping curve specified in the ACAMERA_TONEMAPCURVE_* entries. All color enhancement and tonemapping must be disabled, except for applying the tonemapping curve specified by android.tonemap.curve. Must not slow down frame rate relative to raw sensor output. |
ACAMERA_TONEMAP_MODE_FAST
|
Advanced gamma mapping and color enhancement may be applied, without reducing frame rate compared to raw sensor output. |
ACAMERA_TONEMAP_MODE_GAMMA_VALUE
|
Use the gamma value specified in ACAMERA_TONEMAP_GAMMA to perform tonemapping. All color enhancement and tonemapping must be disabled, except for applying the tonemapping curve specified by ACAMERA_TONEMAP_GAMMA. Must not slow down frame rate relative to raw sensor output. See also: ACAMERA_TONEMAP_GAMMA |
ACAMERA_TONEMAP_MODE_HIGH_QUALITY
|
High-quality gamma mapping and color enhancement will be applied, at the cost of possibly reduced frame rate compared to raw sensor output. |
ACAMERA_TONEMAP_MODE_PRESET_CURVE
|
Use the preset tonemapping curve specified in ACAMERA_TONEMAP_PRESET_CURVE to perform tonemapping. All color enhancement and tonemapping must be disabled, except for applying the tonemapping curve specified by ACAMERA_TONEMAP_PRESET_CURVE. Must not slow down frame rate relative to raw sensor output. See also: ACAMERA_TONEMAP_PRESET_CURVE |
acamera_metadata_enum_acamera_tonemap_preset_curve
acamera_metadata_enum_acamera_tonemap_preset_curve
acamera_metadata_section
acamera_metadata_section
acamera_metadata_section_start
acamera_metadata_section_start
Hierarchy positions in enum space.
acamera_metadata_tag
acamera_metadata_tag
Main enum for camera metadata tags.
Properties | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ACAMERA_AUTOMOTIVE_END
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_AUTOMOTIVE_LENS_END
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_AUTOMOTIVE_LENS_FACING
|
The direction of the camera faces relative to the vehicle body frame and the passenger seats. Type: byte[n] (acamera_metadata_enum_android_automotive_lens_facing_t) This tag may appear in:
This enum defines the lens facing characteristic of the cameras on the automotive devices with locations ACAMERA_AUTOMOTIVE_LOCATION defines. If the system has FEATURE_AUTOMOTIVE, the camera will have this entry in its static metadata. When ACAMERA_AUTOMOTIVE_LOCATION is INTERIOR, this has one or more INTERIOR_* values or a single EXTERIOR_* value. When this has more than one INTERIOR_*, the first value must be the one for the seat closest to the optical axis. If this contains INTERIOR_OTHER, all other values will be ineffective. When ACAMERA_AUTOMOTIVE_LOCATION is EXTERIOR_* or EXTRA, this has a single EXTERIOR_* value. If a camera has INTERIOR_OTHER or EXTERIOR_OTHER, or more than one camera is at the same location and facing the same direction, their static metadata will list the following entries, so that applications can determine their lenses' exact facing directions:
See also: ACAMERA_AUTOMOTIVE_LOCATION See also: ACAMERA_LENS_POSE_REFERENCE See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_AUTOMOTIVE_LOCATION
|
Location of the cameras on the automotive devices. Type: byte (acamera_metadata_enum_android_automotive_location_t) This tag may appear in:
This enum defines the locations of the cameras relative to the vehicle body frame on the automotive sensor coordinate system. If the system has FEATURE_AUTOMOTIVE, the camera will have this entry in its static metadata.
Each side of the vehicle body frame on this coordinate system is defined as below:
If the camera has either EXTERIOR_OTHER or EXTRA_OTHER, its static metadata will list the following entries, so that applications can determine the camera's exact location:
See also: ACAMERA_LENS_POSE_REFERENCE See also: ACAMERA_LENS_POSE_ROTATION See also: ACAMERA_LENS_POSE_TRANSLATION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_BLACK_LEVEL_END
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_BLACK_LEVEL_LOCK
|
Whether black-level compensation is locked to its current values, or is free to vary. Type: byte (acamera_metadata_enum_android_black_level_lock_t) This tag may appear in:
Whether the black level offset was locked for this frame. Should be ON if ACAMERA_BLACK_LEVEL_LOCK was ON in the capture request, unless a change in other capture settings forced the camera device to perform a black level reset. See also: ACAMERA_BLACK_LEVEL_LOCK |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_ABERRATION_MODE
|
Mode of operation for the chromatic aberration correction algorithm. Type: byte (acamera_metadata_enum_android_color_correction_aberration_mode_t) This tag may appear in:
Chromatic (color) aberration is caused by the fact that different wavelengths of light can not focus on the same point after exiting from the lens. This metadata defines the high level control of chromatic aberration correction algorithm, which aims to minimize the chromatic artifacts that may occur along the object boundaries in an image. FAST/HIGH_QUALITY both mean that camera device determined aberration correction will be applied. HIGH_QUALITY mode indicates that the camera device will use the highest-quality aberration correction algorithms, even if it slows down capture rate. FAST means the camera device will not slow down capture rate when applying aberration correction. LEGACY devices will always be in FAST mode. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_AVAILABLE_ABERRATION_MODES
|
List of aberration correction modes for ACAMERA_COLOR_CORRECTION_ABERRATION_MODE that are supported by this camera device. See also: ACAMERA_COLOR_CORRECTION_ABERRATION_MODE Type: byte[n] This tag may appear in:
This key lists the valid modes for ACAMERA_COLOR_CORRECTION_ABERRATION_MODE. If no aberration correction modes are available for a device, this list will solely include OFF mode. All camera devices will support either OFF or FAST mode. Camera devices that support the MANUAL_POST_PROCESSING capability will always list OFF mode. This includes all FULL level devices. LEGACY devices will always only support FAST mode. See also: ACAMERA_COLOR_CORRECTION_ABERRATION_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_END
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_GAINS
|
Gains applying to Bayer raw color channels for white-balance. Type: float[4] This tag may appear in:
These per-channel gains are either set by the camera device when the request ACAMERA_COLOR_CORRECTION_MODE is not TRANSFORM_MATRIX, or directly by the application in the request when the ACAMERA_COLOR_CORRECTION_MODE is TRANSFORM_MATRIX. The gains in the result metadata are the gains actually applied by the camera device to the current frame. The valid range of gains varies on different devices, but gains between [1.0, 3.0] are guaranteed not to be clipped. Even if a given device allows gains below 1.0, this is usually not recommended because this can create color artifacts. See also: ACAMERA_COLOR_CORRECTION_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_MODE
|
The mode control selects how the image data is converted from the sensor's native color into linear sRGB color. Type: byte (acamera_metadata_enum_android_color_correction_mode_t) This tag may appear in:
When auto-white balance (AWB) is enabled with ACAMERA_CONTROL_AWB_MODE, this control is overridden by the AWB routine. When AWB is disabled, the application controls how the color mapping is performed. We define the expected processing pipeline below. For consistency across devices, this is always the case with TRANSFORM_MATRIX. When either FAST or HIGH_QUALITY is used, the camera device may do additional processing but ACAMERA_COLOR_CORRECTION_GAINS and ACAMERA_COLOR_CORRECTION_TRANSFORM will still be provided by the camera device (in the results) and be roughly correct. Switching to TRANSFORM_MATRIX and using the data provided from FAST or HIGH_QUALITY will yield a picture with the same white point as what was produced by the camera device in the earlier frame. The expected processing pipeline is as follows:
The white balance is encoded by two values, a 4-channel white-balance gain vector (applied in the Bayer domain), and a 3x3 color transform matrix (applied after demosaic). The 4-channel white-balance gains are defined as:
where The matrices for color transforms are defined as a 9-entry vector:
which define a transform from input sensor colors, with colors as follows:
Both the input and output value ranges must match. Overflow/underflow values are clipped to fit within the range. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_TRANSFORM See also: ACAMERA_CONTROL_AWB_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_COLOR_CORRECTION_TRANSFORM
|
A color transform matrix to use to transform from sensor RGB color space to output linear sRGB color space. Type: rational[3*3] This tag may appear in:
This matrix is either set by the camera device when the request ACAMERA_COLOR_CORRECTION_MODE is not TRANSFORM_MATRIX, or directly by the application in the request when the ACAMERA_COLOR_CORRECTION_MODE is TRANSFORM_MATRIX. In the latter case, the camera device may round the matrix to account for precision issues; the final rounded matrix should be reported back in this matrix result metadata. The transform should keep the magnitude of the output color values within The valid range of each matrix element varies on different devices, but values within [-1.5, 3.0] are guaranteed not to be clipped. See also: ACAMERA_COLOR_CORRECTION_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_ANTIBANDING_MODE
|
The desired setting for the camera device's auto-exposure algorithm's antibanding compensation. Type: byte (acamera_metadata_enum_android_control_ae_antibanding_mode_t) This tag may appear in:
Some kinds of lighting fixtures, such as some fluorescent lights, flicker at the rate of the power supply frequency (60Hz or 50Hz, depending on country). While this is typically not noticeable to a person, it can be visible to a camera device. If a camera sets its exposure time to the wrong value, the flicker may become visible in the viewfinder as flicker or in a final captured image, as a set of variable-brightness bands across the image. Therefore, the auto-exposure routines of camera devices include antibanding routines that ensure that the chosen exposure value will not cause such banding. The choice of exposure time depends on the rate of flicker, which the camera device can detect automatically, or the expected rate can be selected by the application using this control. A given camera device may not support all of the possible options for the antibanding mode. The ACAMERA_CONTROL_AE_AVAILABLE_ANTIBANDING_MODES key contains the available modes for a given camera device. AUTO mode is the default if it is available on given camera device. When AUTO mode is not available, the default will be either 50HZ or 60HZ, and both 50HZ and 60HZ will be available. If manual exposure control is enabled (by setting ACAMERA_CONTROL_AE_MODE or ACAMERA_CONTROL_MODE to OFF), then this setting has no effect, and the application must ensure it selects exposure times that do not cause banding issues. The ACAMERA_STATISTICS_SCENE_FLICKER key can assist the application in this. See also: ACAMERA_CONTROL_AE_AVAILABLE_ANTIBANDING_MODES See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_MODE See also: ACAMERA_STATISTICS_SCENE_FLICKER |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_AVAILABLE_ANTIBANDING_MODES
|
List of auto-exposure antibanding modes for ACAMERA_CONTROL_AE_ANTIBANDING_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_AE_ANTIBANDING_MODE Type: byte[n] This tag may appear in:
Not all of the auto-exposure anti-banding modes may be supported by a given camera device. This field lists the valid anti-banding modes that the application may request for this camera device with the ACAMERA_CONTROL_AE_ANTIBANDING_MODE control. See also: ACAMERA_CONTROL_AE_ANTIBANDING_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_AVAILABLE_MODES
|
List of auto-exposure modes for ACAMERA_CONTROL_AE_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_AE_MODE Type: byte[n] This tag may appear in:
Not all the auto-exposure modes may be supported by a given camera device, especially if no flash unit is available. This entry lists the valid modes for ACAMERA_CONTROL_AE_MODE for this camera device. All camera devices support ON, and all camera devices with flash units support ON_AUTO_FLASH and ON_ALWAYS_FLASH. FULL mode camera devices always support OFF mode, which enables application control of camera exposure time, sensitivity, and frame duration. LEGACY mode camera devices never support OFF mode. LIMITED mode devices support OFF if they support the MANUAL_SENSOR capability. See also: ACAMERA_CONTROL_AE_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES
|
List of frame rate ranges for ACAMERA_CONTROL_AE_TARGET_FPS_RANGE supported by this camera device. See also: ACAMERA_CONTROL_AE_TARGET_FPS_RANGE Type: int32[2*n] This tag may appear in:
For devices at the LEGACY level or above:
For devices at the LIMITED level or above:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_COMPENSATION_RANGE
|
Maximum and minimum exposure compensation values for ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION, in counts of ACAMERA_CONTROL_AE_COMPENSATION_STEP, that are supported by this camera device. See also: ACAMERA_CONTROL_AE_COMPENSATION_STEP See also: ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION Type: int32[2] This tag may appear in:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_COMPENSATION_STEP
|
Smallest step by which the exposure compensation can be changed. Type: rational This tag may appear in:
This is the unit for ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION. For example, if this key has a value of One unit of EV compensation changes the brightness of the captured image by a factor of two. +1 EV doubles the image brightness, while -1 EV halves the image brightness. See also: ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION
|
Adjustment to auto-exposure (AE) target image brightness. Type: int32 This tag may appear in:
The adjustment is measured as a count of steps, with the step size defined by ACAMERA_CONTROL_AE_COMPENSATION_STEP and the allowed range by ACAMERA_CONTROL_AE_COMPENSATION_RANGE. For example, if the exposure value (EV) step is 0.333, '6' will mean an exposure compensation of +2 EV; -3 will mean an exposure compensation of -1 EV. One EV represents a doubling of image brightness. Note that this control will only be effective if ACAMERA_CONTROL_AE_MODE In the event of exposure compensation value being changed, camera device may take several frames to reach the newly requested exposure target. During that time, ACAMERA_CONTROL_AE_STATE field will be in the SEARCHING state. Once the new exposure target is reached, ACAMERA_CONTROL_AE_STATE will change from SEARCHING to either CONVERGED, LOCKED (if AE lock is enabled), or FLASH_REQUIRED (if the scene is too dark for still capture). See also: ACAMERA_CONTROL_AE_COMPENSATION_RANGE See also: ACAMERA_CONTROL_AE_COMPENSATION_STEP See also: ACAMERA_CONTROL_AE_LOCK See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AE_STATE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_LOCK
|
Whether auto-exposure (AE) is currently locked to its latest calculated values. Type: byte (acamera_metadata_enum_android_control_ae_lock_t) This tag may appear in:
When set to Note that even when AE is locked, the flash may be fired if the ACAMERA_CONTROL_AE_MODE is ON_AUTO_FLASH / ON_ALWAYS_FLASH / ON_AUTO_FLASH_REDEYE. When ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION is changed, even if the AE lock is ON, the camera device will still adjust its exposure value. If AE precapture is triggered (see ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER) when AE is already locked, the camera device will not change the exposure time (ACAMERA_SENSOR_EXPOSURE_TIME) and sensitivity (ACAMERA_SENSOR_SENSITIVITY) parameters. The flash may be fired if the ACAMERA_CONTROL_AE_MODE is ON_AUTO_FLASH/ON_AUTO_FLASH_REDEYE and the scene is too dark. If the ACAMERA_CONTROL_AE_MODE is ON_ALWAYS_FLASH, the scene may become overexposed. Similarly, AE precapture trigger CANCEL has no effect when AE is already locked. When an AE precapture sequence is triggered, AE unlock will not be able to unlock the AE if AE is locked by the camera device internally during precapture metering sequence In other words, submitting requests with AE unlock has no effect for an ongoing precapture metering sequence. Otherwise, the precapture metering sequence will never succeed in a sequence of preview requests where AE lock is always set to Since the camera device has a pipeline of in-flight requests, the settings that get locked do not necessarily correspond to the settings that were present in the latest capture result received from the camera device, since additional captures and AE updates may have occurred even before the result was sent out. If an application is switching between automatic and manual control and wishes to eliminate any flicker during the switch, the following procedure is recommended:
See ACAMERA_CONTROL_AE_STATE for AE lock related state transition details. See also: ACAMERA_CONTROL_AE_EXPOSURE_COMPENSATION See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_CONTROL_AE_STATE See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_SENSITIVITY |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_LOCK_AVAILABLE
|
Whether the camera device supports ACAMERA_CONTROL_AE_LOCK See also: ACAMERA_CONTROL_AE_LOCK Type: byte (acamera_metadata_enum_android_control_ae_lock_available_t) This tag may appear in:
Devices with MANUAL_SENSOR capability or BURST_CAPTURE capability will always list |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_MODE
|
The desired mode for the camera device's auto-exposure routine. Type: byte (acamera_metadata_enum_android_control_ae_mode_t) This tag may appear in:
This control is only effective if ACAMERA_CONTROL_MODE is AUTO. When set to any of the ON modes, the camera device's auto-exposure routine is enabled, overriding the application's selected exposure time, sensor sensitivity, and frame duration (ACAMERA_SENSOR_EXPOSURE_TIME, ACAMERA_SENSOR_SENSITIVITY, and ACAMERA_SENSOR_FRAME_DURATION). If one of the FLASH modes is selected, the camera device's flash unit controls are also overridden. The FLASH modes are only available if the camera device has a flash unit (ACAMERA_FLASH_INFO_AVAILABLE is If flash TORCH mode is desired, this field must be set to ON or OFF, and ACAMERA_FLASH_MODE set to TORCH. When set to any of the ON modes, the values chosen by the camera device auto-exposure routine for the overridden fields for a given capture will be available in its CaptureResult. See also: ACAMERA_CONTROL_MODE See also: ACAMERA_FLASH_INFO_AVAILABLE See also: ACAMERA_FLASH_MODE See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_FRAME_DURATION See also: ACAMERA_SENSOR_SENSITIVITY |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER
|
Whether the camera device will trigger a precapture metering sequence when it processes this request. Type: byte (acamera_metadata_enum_android_control_ae_precapture_trigger_t) This tag may appear in:
This entry is normally set to IDLE, or is not included at all in the request settings. When included and set to START, the camera device will trigger the auto-exposure (AE) precapture metering sequence. When set to CANCEL, the camera device will cancel any active precapture metering trigger, and return to its initial AE state. If a precapture metering sequence is already completed, and the camera device has implicitly locked the AE for subsequent still capture, the CANCEL trigger will unlock the AE and return to its initial AE state. The precapture sequence should be triggered before starting a high-quality still capture for final metering decisions to be made, and for firing pre-capture flash pulses to estimate scene brightness and required final capture flash power, when the flash is enabled. Normally, this entry should be set to START for only a single request, and the application should wait until the sequence completes before starting a new one. When a precapture metering sequence is finished, the camera device may lock the auto-exposure routine internally to be able to accurately expose the subsequent still capture image ( The exact effect of auto-exposure (AE) precapture trigger depends on the current AE mode and state; see ACAMERA_CONTROL_AE_STATE for AE precapture state transition details. On LEGACY-level devices, the precapture trigger is not supported; capturing a high-resolution JPEG image will automatically trigger a precapture sequence before the high-resolution capture, including potentially firing a pre-capture flash. Using the precapture trigger and the auto-focus trigger ACAMERA_CONTROL_AF_TRIGGER simultaneously is allowed. However, since these triggers often require cooperation between the auto-focus and auto-exposure routines (for example, the may need to be enabled for a focus sweep), the camera device may delay acting on a later trigger until the previous trigger has been fully handled. This may lead to longer intervals between the trigger and changes to ACAMERA_CONTROL_AE_STATE indicating the start of the precapture sequence, for example. If both the precapture and the auto-focus trigger are activated on the same request, then the camera device will complete them in the optimal order for that device. See also: ACAMERA_CONTROL_AE_LOCK See also: ACAMERA_CONTROL_AE_STATE See also: ACAMERA_CONTROL_AF_TRIGGER See also: ACAMERA_CONTROL_CAPTURE_INTENT |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_REGIONS
|
List of metering areas to use for auto-exposure adjustment. Type: int32[5*area_count] This tag may appear in:
Not available if android.control.maxRegionsAe is 0. Otherwise will always be present. The maximum number of regions supported by the device is determined by the value of android.control.maxRegionsAe. For devices not supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system always follows that of ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE, with (0,0) being the top-left pixel in the active pixel array, and (ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.width - 1, ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.height - 1) being the bottom-right pixel in the active pixel array. For devices supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system depends on the mode being set. When the distortion correction mode is OFF, the coordinate system follows ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE, with The weight must be within The weights are relative to weights of other exposure metering regions, so if only one region is used, all non-zero weights will have the same effect. A region with 0 weight is ignored. If all regions have 0 weight, then no specific metering area needs to be used by the camera device. If the metering region is outside the used ACAMERA_SCALER_CROP_REGION returned in capture result metadata, the camera device will ignore the sections outside the crop region and output only the intersection rectangle as the metering region in the result metadata. If the region is entirely outside the crop region, it will be ignored and not reported in the result metadata. When setting the AE metering regions, the application must consider the additional crop resulted from the aspect ratio differences between the preview stream and ACAMERA_SCALER_CROP_REGION. For example, if the ACAMERA_SCALER_CROP_REGION is the full active array size with 4:3 aspect ratio, and the preview stream is 16:9, the boundary of AE regions will be [0, y_crop] and [active_width, active_height - 2 * y_crop] rather than [0, 0] and [active_width, active_height], where y_crop is the additional crop due to aspect ratio mismatch. Starting from API level 30, the coordinate system of activeArraySize or preCorrectionActiveArraySize is used to represent post-zoomRatio field of view, not pre-zoom field of view. This means that the same aeRegions values at different ACAMERA_CONTROL_ZOOM_RATIO represent different parts of the scene. The aeRegions coordinates are relative to the activeArray/preCorrectionActiveArray representing the zoomed field of view. If ACAMERA_CONTROL_ZOOM_RATIO is set to 1.0 (default), the same aeRegions at different ACAMERA_SCALER_CROP_REGION still represent the same parts of the scene as they do before. See ACAMERA_CONTROL_ZOOM_RATIO for details. Whether to use activeArraySize or preCorrectionActiveArraySize still depends on distortion correction mode. For camera devices with the CameraMetadata::REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR capability or devices where CameraCharacteristics::getAvailableCaptureRequestKeys lists ACAMERA_SENSOR_PIXEL_MODE ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION / ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION must be used as the coordinate system for requests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. The data representation is See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_DISTORTION_CORRECTION_MODE See also: ACAMERA_SCALER_CROP_REGION See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_STATE
|
Current state of the auto-exposure (AE) algorithm. Type: byte (acamera_metadata_enum_android_control_ae_state_t) This tag may appear in:
Switching between or enabling AE modes (ACAMERA_CONTROL_AE_MODE) always resets the AE state to INACTIVE. Similarly, switching between ACAMERA_CONTROL_MODE, or ACAMERA_CONTROL_SCENE_MODE if The camera device can do several state transitions between two results, if it is allowed by the state transition table. For example: INACTIVE may never actually be seen in a result. The state in the result is the state for this image (in sync with this image): if AE state becomes CONVERGED, then the image data associated with this result should be good to use. Below are state transition tables for different AE modes.
When ACAMERA_CONTROL_AE_MODE is AE_MODE_ON*:
If the camera device supports AE external flash mode (ON_EXTERNAL_FLASH is included in ACAMERA_CONTROL_AE_AVAILABLE_MODES), ACAMERA_CONTROL_AE_STATE must be FLASH_REQUIRED after the camera device finishes AE scan and it's too dark without flash. For the above table, the camera device may skip reporting any state changes that happen without application intervention (i.e. mode switch, trigger, locking). Any state that can be skipped in that manner is called a transient state. For example, for above AE modes (AE_MODE_ON*), in addition to the state transitions listed in above table, it is also legal for the camera device to skip one or more transient states between two results. See below table for examples:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AE_TARGET_FPS_RANGE
|
Range over which the auto-exposure routine can adjust the capture frame rate to maintain good exposure. Type: int32[2] This tag may appear in:
Only constrains auto-exposure (AE) algorithm, not manual control of ACAMERA_SENSOR_EXPOSURE_TIME and ACAMERA_SENSOR_FRAME_DURATION. Note that the actual achievable max framerate also depends on the minimum frame duration of the output streams. The max frame rate will be To start a CaptureSession with a target FPS range different from the capture request template's default value, the application is strongly recommended to call ACameraDevice_createCaptureSessionWithSessionParameters with the target fps range before creating the capture session. The aeTargetFpsRange is typically a session parameter. Specifying it at session creation time helps avoid session reconfiguration delays in cases like 60fps or high speed recording. See also: ACAMERA_SENSOR_EXPOSURE_TIME See also: ACAMERA_SENSOR_FRAME_DURATION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_AVAILABLE_MODES
|
List of auto-focus (AF) modes for ACAMERA_CONTROL_AF_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_AF_MODE Type: byte[n] This tag may appear in:
Not all the auto-focus modes may be supported by a given camera device. This entry lists the valid modes for ACAMERA_CONTROL_AF_MODE for this camera device. All LIMITED and FULL mode camera devices will support OFF mode, and all camera devices with adjustable focuser units ( LEGACY devices will support OFF mode only if they support focusing to infinity (by also setting ACAMERA_LENS_FOCUS_DISTANCE to See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_LENS_FOCUS_DISTANCE See also: ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_MODE
|
Whether auto-focus (AF) is currently enabled, and what mode it is set to. Type: byte (acamera_metadata_enum_android_control_af_mode_t) This tag may appear in:
Only effective if ACAMERA_CONTROL_MODE = AUTO and the lens is not fixed focus (i.e. If the lens is controlled by the camera device auto-focus algorithm, the camera device will report the current AF status in ACAMERA_CONTROL_AF_STATE in result metadata. See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AF_STATE See also: ACAMERA_CONTROL_AF_TRIGGER See also: ACAMERA_CONTROL_MODE See also: ACAMERA_LENS_INFO_MINIMUM_FOCUS_DISTANCE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_REGIONS
|
List of metering areas to use for auto-focus. Type: int32[5*area_count] This tag may appear in:
Not available if android.control.maxRegionsAf is 0. Otherwise will always be present. The maximum number of focus areas supported by the device is determined by the value of android.control.maxRegionsAf. For devices not supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system always follows that of ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE, with (0,0) being the top-left pixel in the active pixel array, and (ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.width - 1, ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.height - 1) being the bottom-right pixel in the active pixel array. For devices supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system depends on the mode being set. When the distortion correction mode is OFF, the coordinate system follows ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE, with The weight must be within The weights are relative to weights of other metering regions, so if only one region is used, all non-zero weights will have the same effect. A region with 0 weight is ignored. If all regions have 0 weight, then no specific metering area needs to be used by the camera device. The capture result will either be a zero weight region as well, or the region selected by the camera device as the focus area of interest. If the metering region is outside the used ACAMERA_SCALER_CROP_REGION returned in capture result metadata, the camera device will ignore the sections outside the crop region and output only the intersection rectangle as the metering region in the result metadata. If the region is entirely outside the crop region, it will be ignored and not reported in the result metadata. When setting the AF metering regions, the application must consider the additional crop resulted from the aspect ratio differences between the preview stream and ACAMERA_SCALER_CROP_REGION. For example, if the ACAMERA_SCALER_CROP_REGION is the full active array size with 4:3 aspect ratio, and the preview stream is 16:9, the boundary of AF regions will be [0, y_crop] and [active_width, active_height - 2 * y_crop] rather than [0, 0] and [active_width, active_height], where y_crop is the additional crop due to aspect ratio mismatch. Starting from API level 30, the coordinate system of activeArraySize or preCorrectionActiveArraySize is used to represent post-zoomRatio field of view, not pre-zoom field of view. This means that the same afRegions values at different ACAMERA_CONTROL_ZOOM_RATIO represent different parts of the scene. The afRegions coordinates are relative to the activeArray/preCorrectionActiveArray representing the zoomed field of view. If ACAMERA_CONTROL_ZOOM_RATIO is set to 1.0 (default), the same afRegions at different ACAMERA_SCALER_CROP_REGION still represent the same parts of the scene as they do before. See ACAMERA_CONTROL_ZOOM_RATIO for details. Whether to use activeArraySize or preCorrectionActiveArraySize still depends on distortion correction mode. For camera devices with the CameraMetadata::REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR capability or devices where CameraCharacteristics::getAvailableCaptureRequestKeys lists ACAMERA_SENSOR_PIXEL_MODE, ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION / ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION must be used as the coordinate system for requests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. The data representation is See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_DISTORTION_CORRECTION_MODE See also: ACAMERA_SCALER_CROP_REGION See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_SCENE_CHANGE
|
Whether a significant scene change is detected within the currently-set AF region(s). Type: byte (acamera_metadata_enum_android_control_af_scene_change_t) This tag may appear in:
When the camera focus routine detects a change in the scene it is looking at, such as a large shift in camera viewpoint, significant motion in the scene, or a significant illumination change, this value will be set to DETECTED for a single capture result. Otherwise the value will be NOT_DETECTED. The threshold for detection is similar to what would trigger a new passive focus scan to begin in CONTINUOUS autofocus modes. This key will be available if the camera device advertises this key via ACAMERA_REQUEST_AVAILABLE_RESULT_KEYS. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_STATE
|
Current state of auto-focus (AF) algorithm. Type: byte (acamera_metadata_enum_android_control_af_state_t) This tag may appear in:
Switching between or enabling AF modes (ACAMERA_CONTROL_AF_MODE) always resets the AF state to INACTIVE. Similarly, switching between ACAMERA_CONTROL_MODE, or ACAMERA_CONTROL_SCENE_MODE if The camera device can do several state transitions between two results, if it is allowed by the state transition table. For example: INACTIVE may never actually be seen in a result. The state in the result is the state for this image (in sync with this image): if AF state becomes FOCUSED, then the image data associated with this result should be sharp. Below are state transition tables for different AF modes. When ACAMERA_CONTROL_AF_MODE is AF_MODE_OFF or AF_MODE_EDOF:
When ACAMERA_CONTROL_AF_MODE is AF_MODE_AUTO or AF_MODE_MACRO:
For the above table, the camera device may skip reporting any state changes that happen without application intervention (i.e. mode switch, trigger, locking). Any state that can be skipped in that manner is called a transient state. For example, for these AF modes (AF_MODE_AUTO and AF_MODE_MACRO), in addition to the state transitions listed in above table, it is also legal for the camera device to skip one or more transient states between two results. See below table for examples:
When ACAMERA_CONTROL_AF_MODE is AF_MODE_CONTINUOUS_VIDEO:
When ACAMERA_CONTROL_AF_MODE is AF_MODE_CONTINUOUS_PICTURE:
When switch between AF_MODE_CONTINUOUS_* (CAF modes) and AF_MODE_AUTO/AF_MODE_MACRO (AUTO modes), the initial INACTIVE or PASSIVE_SCAN states may be skipped by the camera device. When a trigger is included in a mode switch request, the trigger will be evaluated in the context of the new mode in the request. See below table for examples:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AF_TRIGGER
|
Whether the camera device will trigger autofocus for this request. Type: byte (acamera_metadata_enum_android_control_af_trigger_t) This tag may appear in:
This entry is normally set to IDLE, or is not included at all in the request settings. When included and set to START, the camera device will trigger the autofocus algorithm. If autofocus is disabled, this trigger has no effect. When set to CANCEL, the camera device will cancel any active trigger, and return to its initial AF state. Generally, applications should set this entry to START or CANCEL for only a single capture, and then return it to IDLE (or not set at all). Specifying START for multiple captures in a row means restarting the AF operation over and over again. See ACAMERA_CONTROL_AF_STATE for what the trigger means for each AF mode. Using the autofocus trigger and the precapture trigger ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER simultaneously is allowed. However, since these triggers often require cooperation between the auto-focus and auto-exposure routines (for example, the may need to be enabled for a focus sweep), the camera device may delay acting on a later trigger until the previous trigger has been fully handled. This may lead to longer intervals between the trigger and changes to ACAMERA_CONTROL_AF_STATE, for example. See also: ACAMERA_CONTROL_AE_PRECAPTURE_TRIGGER See also: ACAMERA_CONTROL_AF_STATE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AUTOFRAMING
|
Automatic crop, pan and zoom to keep objects in the center of the frame. Type: byte (acamera_metadata_enum_android_control_autoframing_t) This tag may appear in:
Auto-framing is a special mode provided by the camera device to dynamically crop, zoom or pan the camera feed to try to ensure that the people in a scene occupy a reasonable portion of the viewport. It is primarily designed to support video calling in situations where the user isn't directly in front of the device, especially for wide-angle cameras. ACAMERA_SCALER_CROP_REGION and ACAMERA_CONTROL_ZOOM_RATIO in CaptureResult will be used to denote the coordinates of the auto-framed region. Zoom and video stabilization controls are disabled when auto-framing is enabled. The 3A regions must map the screen coordinates into the scaler crop returned from the capture result instead of using the active array sensor. See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_SCALER_CROP_REGION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AUTOFRAMING_AVAILABLE
|
Whether the camera device supports ACAMERA_CONTROL_AUTOFRAMING. See also: ACAMERA_CONTROL_AUTOFRAMING Type: byte (acamera_metadata_enum_android_control_autoframing_available_t) This tag may appear in:
Will be |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AUTOFRAMING_STATE
|
Current state of auto-framing. Type: byte (acamera_metadata_enum_android_control_autoframing_state_t) This tag may appear in:
When the camera doesn't have auto-framing available (i.e
See also: ACAMERA_CONTROL_AUTOFRAMING See also: ACAMERA_CONTROL_AUTOFRAMING_AVAILABLE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_EFFECTS
|
List of color effects for ACAMERA_CONTROL_EFFECT_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_EFFECT_MODE Type: byte[n] This tag may appear in:
This list contains the color effect modes that can be applied to images produced by the camera device. Implementations are not expected to be consistent across all devices. If no color effect modes are available for a device, this will only list OFF. A color effect will only be applied if ACAMERA_CONTROL_MODE != OFF. OFF is always included in this list. This control has no effect on the operation of other control routines such as auto-exposure, white balance, or focus. See also: ACAMERA_CONTROL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_EXTENDED_SCENE_MODE_MAX_SIZES
|
The list of extended scene modes for ACAMERA_CONTROL_EXTENDED_SCENE_MODE that are supported by this camera device, and each extended scene mode's maximum streaming (non-stall) size with effect. See also: ACAMERA_CONTROL_EXTENDED_SCENE_MODE Type: int32[3*n] This tag may appear in:
For DISABLED mode, the camera behaves normally with no extended scene mode enabled. For BOKEH_STILL_CAPTURE mode, the maximum streaming dimension specifies the limit under which bokeh is effective when capture intent is PREVIEW. Note that when capture intent is PREVIEW, the bokeh effect may not be as high in quality compared to STILL_CAPTURE intent in order to maintain reasonable frame rate. The maximum streaming dimension must be one of the YUV_420_888 or PRIVATE resolutions in availableStreamConfigurations, or (0, 0) if preview bokeh is not supported. If the application configures a stream larger than the maximum streaming dimension, bokeh effect may not be applied for this stream for PREVIEW intent. For BOKEH_CONTINUOUS mode, the maximum streaming dimension specifies the limit under which bokeh is effective. This dimension must be one of the YUV_420_888 or PRIVATE resolutions in availableStreamConfigurations, and if the sensor maximum resolution is larger than or equal to 1080p, the maximum streaming dimension must be at least 1080p. If the application configures a stream with larger dimension, the stream may not have bokeh effect applied. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_EXTENDED_SCENE_MODE_ZOOM_RATIO_RANGES
|
The ranges of supported zoom ratio for non-DISABLED ACAMERA_CONTROL_EXTENDED_SCENE_MODE. See also: ACAMERA_CONTROL_EXTENDED_SCENE_MODE Type: float[2*n] This tag may appear in:
When extended scene mode is set, the camera device may have limited range of zoom ratios compared to when extended scene mode is DISABLED. This tag lists the zoom ratio ranges for all supported non-DISABLED extended scene modes, in the same order as in android.control.availableExtended. Range [1.0, 1.0] means that no zoom (optical or digital) is supported. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_MODES
|
List of control modes for ACAMERA_CONTROL_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_MODE Type: byte[n] This tag may appear in:
This list contains control modes that can be set for the camera device. LEGACY mode devices will always support AUTO mode. LIMITED and FULL devices will always support OFF, AUTO modes. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_SCENE_MODES
|
List of scene modes for ACAMERA_CONTROL_SCENE_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_SCENE_MODE Type: byte[n] This tag may appear in:
This list contains scene modes that can be set for the camera device. Only scene modes that have been fully implemented for the camera device may be included here. Implementations are not expected to be consistent across all devices. If no scene modes are supported by the camera device, this will be set to DISABLED. Otherwise DISABLED will not be listed. FACE_PRIORITY is always listed if face detection is supported (i.e. See also: ACAMERA_STATISTICS_INFO_MAX_FACE_COUNT |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_SETTINGS_OVERRIDES
|
List of available settings overrides supported by the camera device that can be used to speed up certain controls. Type: int32[n] This tag may appear in:
When not all controls within a CaptureRequest are required to take effect at the same time on the outputs, the camera device may apply certain request keys sooner to improve latency. This list contains such supported settings overrides. Each settings override corresponds to a set of CaptureRequest keys that can be sped up when applying. A supported settings override can be passed in via CaptureRequest::CONTROL_SETTINGS_OVERRIDE, and the CaptureRequest keys corresponding to the override are applied as soon as possible, not bound by per-frame synchronization. See ACAMERA_CONTROL_SETTINGS_OVERRIDE for the CaptureRequest keys for each override. OFF is always included in this list. See also: ACAMERA_CONTROL_SETTINGS_OVERRIDE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AVAILABLE_VIDEO_STABILIZATION_MODES
|
List of video stabilization modes for ACAMERA_CONTROL_VIDEO_STABILIZATION_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_VIDEO_STABILIZATION_MODE Type: byte[n] This tag may appear in:
OFF will always be listed. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_AVAILABLE_MODES
|
List of auto-white-balance modes for ACAMERA_CONTROL_AWB_MODE that are supported by this camera device. See also: ACAMERA_CONTROL_AWB_MODE Type: byte[n] This tag may appear in:
Not all the auto-white-balance modes may be supported by a given camera device. This entry lists the valid modes for ACAMERA_CONTROL_AWB_MODE for this camera device. All camera devices will support ON mode. Camera devices that support the MANUAL_POST_PROCESSING capability will always support OFF mode, which enables application control of white balance, by using ACAMERA_COLOR_CORRECTION_TRANSFORM and ACAMERA_COLOR_CORRECTION_GAINS(ACAMERA_COLOR_CORRECTION_MODE must be set to TRANSFORM_MATRIX). This includes all FULL mode camera devices. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_MODE See also: ACAMERA_COLOR_CORRECTION_TRANSFORM See also: ACAMERA_CONTROL_AWB_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_LOCK
|
Whether auto-white balance (AWB) is currently locked to its latest calculated values. Type: byte (acamera_metadata_enum_android_control_awb_lock_t) This tag may appear in:
When set to Since the camera device has a pipeline of in-flight requests, the settings that get locked do not necessarily correspond to the settings that were present in the latest capture result received from the camera device, since additional captures and AWB updates may have occurred even before the result was sent out. If an application is switching between automatic and manual control and wishes to eliminate any flicker during the switch, the following procedure is recommended:
Note that AWB lock is only meaningful when ACAMERA_CONTROL_AWB_MODE is in the AUTO mode; in other modes, AWB is already fixed to a specific setting. Some LEGACY devices may not support ON; the value is then overridden to OFF. See also: ACAMERA_CONTROL_AWB_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_LOCK_AVAILABLE
|
Whether the camera device supports ACAMERA_CONTROL_AWB_LOCK See also: ACAMERA_CONTROL_AWB_LOCK Type: byte (acamera_metadata_enum_android_control_awb_lock_available_t) This tag may appear in:
Devices with MANUAL_POST_PROCESSING capability or BURST_CAPTURE capability will always list |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_MODE
|
Whether auto-white balance (AWB) is currently setting the color transform fields, and what its illumination target is. Type: byte (acamera_metadata_enum_android_control_awb_mode_t) This tag may appear in:
This control is only effective if ACAMERA_CONTROL_MODE is AUTO. When set to the AUTO mode, the camera device's auto-white balance routine is enabled, overriding the application's selected ACAMERA_COLOR_CORRECTION_TRANSFORM, ACAMERA_COLOR_CORRECTION_GAINS and ACAMERA_COLOR_CORRECTION_MODE. Note that when ACAMERA_CONTROL_AE_MODE is OFF, the behavior of AWB is device dependent. It is recommended to also set AWB mode to OFF or lock AWB by using ACAMERA_CONTROL_AWB_LOCK before setting AE mode to OFF. When set to the OFF mode, the camera device's auto-white balance routine is disabled. The application manually controls the white balance by ACAMERA_COLOR_CORRECTION_TRANSFORM, ACAMERA_COLOR_CORRECTION_GAINS and ACAMERA_COLOR_CORRECTION_MODE. When set to any other modes, the camera device's auto-white balance routine is disabled. The camera device uses each particular illumination target for white balance adjustment. The application's values for ACAMERA_COLOR_CORRECTION_TRANSFORM, ACAMERA_COLOR_CORRECTION_GAINS and ACAMERA_COLOR_CORRECTION_MODE are ignored. See also: ACAMERA_COLOR_CORRECTION_GAINS See also: ACAMERA_COLOR_CORRECTION_MODE See also: ACAMERA_COLOR_CORRECTION_TRANSFORM See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AWB_LOCK See also: ACAMERA_CONTROL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_REGIONS
|
List of metering areas to use for auto-white-balance illuminant estimation. Type: int32[5*area_count] This tag may appear in:
Not available if android.control.maxRegionsAwb is 0. Otherwise will always be present. The maximum number of regions supported by the device is determined by the value of android.control.maxRegionsAwb. For devices not supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system always follows that of ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE, with (0,0) being the top-left pixel in the active pixel array, and (ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.width - 1, ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE.height - 1) being the bottom-right pixel in the active pixel array. For devices supporting ACAMERA_DISTORTION_CORRECTION_MODE control, the coordinate system depends on the mode being set. When the distortion correction mode is OFF, the coordinate system follows ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE, with The weight must range from 0 to 1000, and represents a weight for every pixel in the area. This means that a large metering area with the same weight as a smaller area will have more effect in the metering result. Metering areas can partially overlap and the camera device will add the weights in the overlap region. The weights are relative to weights of other white balance metering regions, so if only one region is used, all non-zero weights will have the same effect. A region with 0 weight is ignored. If all regions have 0 weight, then no specific metering area needs to be used by the camera device. If the metering region is outside the used ACAMERA_SCALER_CROP_REGION returned in capture result metadata, the camera device will ignore the sections outside the crop region and output only the intersection rectangle as the metering region in the result metadata. If the region is entirely outside the crop region, it will be ignored and not reported in the result metadata. When setting the AWB metering regions, the application must consider the additional crop resulted from the aspect ratio differences between the preview stream and ACAMERA_SCALER_CROP_REGION. For example, if the ACAMERA_SCALER_CROP_REGION is the full active array size with 4:3 aspect ratio, and the preview stream is 16:9, the boundary of AWB regions will be [0, y_crop] and [active_width, active_height - 2 * y_crop] rather than [0, 0] and [active_width, active_height], where y_crop is the additional crop due to aspect ratio mismatch. Starting from API level 30, the coordinate system of activeArraySize or preCorrectionActiveArraySize is used to represent post-zoomRatio field of view, not pre-zoom field of view. This means that the same awbRegions values at different ACAMERA_CONTROL_ZOOM_RATIO represent different parts of the scene. The awbRegions coordinates are relative to the activeArray/preCorrectionActiveArray representing the zoomed field of view. If ACAMERA_CONTROL_ZOOM_RATIO is set to 1.0 (default), the same awbRegions at different ACAMERA_SCALER_CROP_REGION still represent the same parts of the scene as they do before. See ACAMERA_CONTROL_ZOOM_RATIO for details. Whether to use activeArraySize or preCorrectionActiveArraySize still depends on distortion correction mode. For camera devices with the CameraMetadata::REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR capability or devices where CameraCharacteristics::getAvailableCaptureRequestKeys lists ACAMERA_SENSOR_PIXEL_MODE, ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION / ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION must be used as the coordinate system for requests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. The data representation is See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_DISTORTION_CORRECTION_MODE See also: ACAMERA_SCALER_CROP_REGION See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE See also: ACAMERA_SENSOR_INFO_PRE_CORRECTION_ACTIVE_ARRAY_SIZE_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_AWB_STATE
|
Current state of auto-white balance (AWB) algorithm. Type: byte (acamera_metadata_enum_android_control_awb_state_t) This tag may appear in:
Switching between or enabling AWB modes (ACAMERA_CONTROL_AWB_MODE) always resets the AWB state to INACTIVE. Similarly, switching between ACAMERA_CONTROL_MODE, or ACAMERA_CONTROL_SCENE_MODE if The camera device can do several state transitions between two results, if it is allowed by the state transition table. So INACTIVE may never actually be seen in a result. The state in the result is the state for this image (in sync with this image): if AWB state becomes CONVERGED, then the image data associated with this result should be good to use. Below are state transition tables for different AWB modes. When
When ACAMERA_CONTROL_AWB_MODE is AWB_MODE_AUTO:
For the above table, the camera device may skip reporting any state changes that happen without application intervention (i.e. mode switch, trigger, locking). Any state that can be skipped in that manner is called a transient state. For example, for this AWB mode (AWB_MODE_AUTO), in addition to the state transitions listed in above table, it is also legal for the camera device to skip one or more transient states between two results. See below table for examples:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_CAPTURE_INTENT
|
Information to the camera device 3A (auto-exposure, auto-focus, auto-white balance) routines about the purpose of this capture, to help the camera device to decide optimal 3A strategy. Type: byte (acamera_metadata_enum_android_control_capture_intent_t) This tag may appear in:
This control (except for MANUAL) is only effective if All intents are supported by all devices, except that:
See also: ACAMERA_CONTROL_MODE See also: ACAMERA_REQUEST_AVAILABLE_CAPABILITIES |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_EFFECT_MODE
|
A special color effect to apply. Type: byte (acamera_metadata_enum_android_control_effect_mode_t) This tag may appear in:
When this mode is set, a color effect will be applied to images produced by the camera device. The interpretation and implementation of these color effects is left to the implementor of the camera device, and should not be depended on to be consistent (or present) across all devices. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_ENABLE_ZSL
|
Allow camera device to enable zero-shutter-lag mode for requests with ACAMERA_CONTROL_CAPTURE_INTENT == STILL_CAPTURE. See also: ACAMERA_CONTROL_CAPTURE_INTENT Type: byte (acamera_metadata_enum_android_control_enable_zsl_t) This tag may appear in:
If enableZsl is For example, when requests are submitted in the following order: Request A: enableZsl is ON, ACAMERA_CONTROL_CAPTURE_INTENT is PREVIEW Request B: enableZsl is ON, ACAMERA_CONTROL_CAPTURE_INTENT is STILL_CAPTURE The output images for request B may have contents captured before the output images for request A, and the result metadata for request B may be older than the result metadata for request A. Note that when enableZsl is For applications targeting SDK versions O and newer, the value of enableZsl in TEMPLATE_STILL_CAPTURE template may be For applications targeting SDK versions older than O, the value of enableZsl in all capture templates is always For application-operated ZSL, use CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template. See also: ACAMERA_CONTROL_CAPTURE_INTENT See also: ACAMERA_SENSOR_TIMESTAMP |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_END
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_EXTENDED_SCENE_MODE
|
Whether extended scene mode is enabled for a particular capture request. Type: byte (acamera_metadata_enum_android_control_extended_scene_mode_t) This tag may appear in:
With bokeh mode, the camera device may blur out the parts of scene that are not in focus, creating a bokeh (or shallow depth of field) effect for people or objects. When set to BOKEH_STILL_CAPTURE mode with STILL_CAPTURE capture intent, due to the extra processing needed for high quality bokeh effect, the stall may be longer than when capture intent is not STILL_CAPTURE. When set to BOKEH_STILL_CAPTURE mode with PREVIEW capture intent,
When set to BOKEH_CONTINUOUS mode, configured streams dimension should not exceed this mode's maximum streaming dimension in order to have bokeh effect applied. Bokeh effect may not be available for streams larger than the maximum streaming dimension. Switching between different extended scene modes may involve reconfiguration of the camera pipeline, resulting in long latency. The application should check this key against the available session keys queried via ACameraManager_getCameraCharacteristics. For a logical multi-camera, bokeh may be implemented by stereo vision from sub-cameras with different field of view. As a result, when bokeh mode is enabled, the camera device may override ACAMERA_SCALER_CROP_REGION or ACAMERA_CONTROL_ZOOM_RATIO, and the field of view may be smaller than when bokeh mode is off. See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_SCALER_CROP_REGION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_LOW_LIGHT_BOOST_INFO_LUMINANCE_RANGE
|
The operating luminance range of low light boost measured in lux (lx). Type: float[2] This tag may appear in:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_LOW_LIGHT_BOOST_STATE
|
Current state of the low light boost AE mode. Type: byte (acamera_metadata_enum_android_control_low_light_boost_state_t) This tag may appear in:
When low light boost is enabled by setting the AE mode to 'ON_LOW_LIGHT_BOOST_BRIGHTNESS_PRIORITY', it can dynamically apply a low light boost when the light level threshold is exceeded. This state indicates when low light boost is 'ACTIVE' and applied. Similarly, it can indicate when it is not being applied by returning 'INACTIVE'. This key will be absent from the CaptureResult if AE mode is not set to 'ON_LOW_LIGHT_BOOST_BRIGHTNESS_PRIORITY. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_MAX_REGIONS
|
List of the maximum number of regions that can be used for metering in auto-exposure (AE), auto-white balance (AWB), and auto-focus (AF); this corresponds to the maximum number of elements in ACAMERA_CONTROL_AE_REGIONS, ACAMERA_CONTROL_AWB_REGIONS, and ACAMERA_CONTROL_AF_REGIONS. See also: ACAMERA_CONTROL_AE_REGIONS See also: ACAMERA_CONTROL_AF_REGIONS See also: ACAMERA_CONTROL_AWB_REGIONS Type: int32[3] This tag may appear in:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_MODE
|
Overall mode of 3A (auto-exposure, auto-white-balance, auto-focus) control routines. Type: byte (acamera_metadata_enum_android_control_mode_t) This tag may appear in:
This is a top-level 3A control switch. When set to OFF, all 3A control by the camera device is disabled. The application must set the fields for capture parameters itself. When set to AUTO, the individual algorithm controls in ACAMERA_CONTROL_* are in effect, such as ACAMERA_CONTROL_AF_MODE. When set to USE_SCENE_MODE or USE_EXTENDED_SCENE_MODE, the individual controls in ACAMERA_CONTROL_* are mostly disabled, and the camera device implements one of the scene mode or extended scene mode settings (such as ACTION, SUNSET, PARTY, or BOKEH) as it wishes. The camera device scene mode 3A settings are provided by capture results. When set to OFF_KEEP_STATE, it is similar to OFF mode, the only difference is that this frame will not be used by camera device background 3A statistics update, as if this frame is never captured. This mode can be used in the scenario where the application doesn't want a 3A manual control capture to affect the subsequent auto 3A capture results. See also: ACAMERA_CONTROL_AF_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST
|
The amount of additional sensitivity boost applied to output images after RAW sensor data is captured. Type: int32 This tag may appear in:
Some camera devices support additional digital sensitivity boosting in the camera processing pipeline after sensor RAW image is captured. Such a boost will be applied to YUV/JPEG format output images but will not have effect on RAW output formats like RAW_SENSOR, RAW10, RAW12 or RAW_OPAQUE. This key will be If the camera device cannot apply the exact boost requested, it will reduce the boost to the nearest supported value. The final boost value used will be available in the output capture result. For devices that support post RAW sensitivity boost, the YUV/JPEG output images of such device will have the total sensitivity of This control is only effective if ACAMERA_CONTROL_AE_MODE or ACAMERA_CONTROL_MODE is set to OFF; otherwise the auto-exposure algorithm will override this value. See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_MODE See also: ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST See also: ACAMERA_SENSOR_SENSITIVITY |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST_RANGE
|
Range of boosts for ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST supported by this camera device. See also: ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST Type: int32[2] This tag may appear in:
Devices support post RAW sensitivity boost will advertise ACAMERA_CONTROL_POST_RAW_SENSITIVITY_BOOST key for controlling post RAW sensitivity boost. This key will be |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_SCENE_MODE
|
Control for which scene mode is currently active. Type: byte (acamera_metadata_enum_android_control_scene_mode_t) This tag may appear in:
Scene modes are custom camera modes optimized for a certain set of conditions and capture settings. This is the mode that that is active when The interpretation and implementation of these scene modes is left to the implementor of the camera device. Their behavior will not be consistent across all devices, and any given device may only implement a subset of these modes. See also: ACAMERA_CONTROL_AE_MODE See also: ACAMERA_CONTROL_AF_MODE See also: ACAMERA_CONTROL_AWB_MODE See also: ACAMERA_CONTROL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_SETTINGS_OVERRIDE
|
The desired CaptureRequest settings override with which certain keys are applied earlier so that they can take effect sooner. Type: int32 (acamera_metadata_enum_android_control_settings_override_t) This tag may appear in:
There are some CaptureRequest keys which can be applied earlier than others when controls within a CaptureRequest aren't required to take effect at the same time. One such example is zoom. Zoom can be applied at a later stage of the camera pipeline. As soon as the camera device receives the CaptureRequest, it can apply the requested zoom value onto an earlier request that's already in the pipeline, thus improves zoom latency. This key's value in the capture result reflects whether the controls for this capture are overridden "by" a newer request. This means that if a capture request turns on settings override, the capture result of an earlier request will contain the key value of ZOOM. On the other hand, if a capture request has settings override turned on, but all newer requests have it turned off, the key's value in the capture result will be OFF because this capture isn't overridden by a newer capture. In the two examples below, the capture results columns illustrate the settingsOverride values in different scenarios. Assuming the zoom settings override can speed up by 1 frame, below example illustrates the speed-up at the start of capture session:
The application can turn on settings override and use zoom as normal. The example shows that the later zoom values (1.2x, 1.4x, 1.6x, and 1.8x) overwrite the zoom values (1.0x, 1.2x, 1.4x, and 1.8x) of earlier requests (#1, #2, #3, and #4). The application must make sure the settings override doesn't interfere with user journeys requiring simultaneous application of all controls in CaptureRequest on the requested output targets. For example, if the application takes a still capture using CameraCaptureSession::capture, and the repeating request immediately sets a different zoom value using override, the inflight still capture could have its zoom value overwritten unexpectedly. So the application is strongly recommended to turn off settingsOverride when taking still/burst captures, and turn it back on when there is only repeating viewfinder request and no inflight still/burst captures. Below is the example demonstrating the transitions in and out of the settings override:
This example shows that:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_VIDEO_STABILIZATION_MODE
|
Whether video stabilization is active. Type: byte (acamera_metadata_enum_android_control_video_stabilization_mode_t) This tag may appear in:
Video stabilization automatically warps images from the camera in order to stabilize motion between consecutive frames. If enabled, video stabilization can modify the ACAMERA_SCALER_CROP_REGION to keep the video stream stabilized. Switching between different video stabilization modes may take several frames to initialize, the camera device will report the current mode in capture result metadata. For example, When "ON" mode is requested, the video stabilization modes in the first several capture results may still be "OFF", and it will become "ON" when the initialization is done. In addition, not all recording sizes or frame rates may be supported for stabilization by a device that reports stabilization support. It is guaranteed that an output targeting a MediaRecorder or MediaCodec will be stabilized if the recording resolution is less than or equal to 1920 x 1080 (width less than or equal to 1920, height less than or equal to 1080), and the recording frame rate is less than or equal to 30fps. At other sizes, the CaptureResult ACAMERA_CONTROL_VIDEO_STABILIZATION_MODE field will return OFF if the recording output is not stabilized, or if there are no output Surface types that can be stabilized. The application is strongly recommended to call ACameraDevice_createCaptureSessionWithSessionParameters with the desired video stabilization mode before creating the capture session. Video stabilization mode is a session parameter on many devices. Specifying it at session creation time helps avoid reconfiguration delay caused by difference between the default value and the first CaptureRequest. If a camera device supports both this mode and OIS (ACAMERA_LENS_OPTICAL_STABILIZATION_MODE), turning both modes on may produce undesirable interaction, so it is recommended not to enable both at the same time. If video stabilization is set to "PREVIEW_STABILIZATION", ACAMERA_LENS_OPTICAL_STABILIZATION_MODE is overridden. The camera sub-system may choose to turn on hardware based image stabilization in addition to software based stabilization if it deems that appropriate. This key may be a part of the available session keys, which camera clients may query via ACameraManager_getCameraCharacteristics. If this is the case, changing this key over the life-time of a capture session may cause delays / glitches. See also: ACAMERA_CONTROL_VIDEO_STABILIZATION_MODE See also: ACAMERA_LENS_OPTICAL_STABILIZATION_MODE See also: ACAMERA_SCALER_CROP_REGION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_ZOOM_RATIO
|
The desired zoom ratio Type: float This tag may appear in:
Instead of using ACAMERA_SCALER_CROP_REGION for zoom, the application can now choose to use this tag to specify the desired zoom level. By using this control, the application gains a simpler way to control zoom, which can be a combination of optical and digital zoom. For example, a multi-camera system may contain more than one lens with different focal lengths, and the user can use optical zoom by switching between lenses. Using zoomRatio has benefits in the scenarios below:
To illustrate, here are several scenarios of different zoom ratios, crop regions, and output streams, for a hypothetical camera device with an active array of size
As seen from the graphs above, the coordinate system of cropRegion now changes to the effective after-zoom field-of-view, and is represented by the rectangle of (0, 0, activeArrayWith, activeArrayHeight). The same applies to AE/AWB/AF regions, and faces. This coordinate system change isn't applicable to RAW capture and its related metadata such as intrinsicCalibration and lensShadingMap. Using the same hypothetical example above, and assuming output stream #1 (640x480) is the viewfinder stream, the application can achieve 2.0x zoom in one of two ways:
If the application intends to set aeRegions to be top-left quarter of the viewfinder field-of-view, the ACAMERA_CONTROL_AE_REGIONS should be set to (0, 0, 1000, 750) with zoomRatio set to 2.0. Alternatively, the application can set aeRegions to the equivalent region of (500, 375, 1000, 750) for zoomRatio of 1.0. If the application doesn't explicitly set ACAMERA_CONTROL_ZOOM_RATIO, its value defaults to 1.0. One limitation of controlling zoom using zoomRatio is that the ACAMERA_SCALER_CROP_REGION must only be used for letterboxing or pillarboxing of the sensor active array, and no FREEFORM cropping can be used with ACAMERA_CONTROL_ZOOM_RATIO other than 1.0. If ACAMERA_CONTROL_ZOOM_RATIO is not 1.0, and ACAMERA_SCALER_CROP_REGION is set to be windowboxing, the camera framework will override the ACAMERA_SCALER_CROP_REGION to be the active array. In the capture request, if the application sets ACAMERA_CONTROL_ZOOM_RATIO to a value != 1.0, the ACAMERA_CONTROL_ZOOM_RATIO tag in the capture result reflects the effective zoom ratio achieved by the camera device, and the ACAMERA_SCALER_CROP_REGION adjusts for additional crops that are not zoom related. Otherwise, if the application sets ACAMERA_CONTROL_ZOOM_RATIO to 1.0, or does not set it at all, the ACAMERA_CONTROL_ZOOM_RATIO tag in the result metadata will also be 1.0. When the application requests a physical stream for a logical multi-camera, the ACAMERA_CONTROL_ZOOM_RATIO in the physical camera result metadata will be 1.0, and the ACAMERA_SCALER_CROP_REGION tag reflects the amount of zoom and crop done by the physical camera device. See also: ACAMERA_CONTROL_AE_REGIONS See also: ACAMERA_CONTROL_ZOOM_RATIO See also: ACAMERA_SCALER_CROP_REGION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_CONTROL_ZOOM_RATIO_RANGE
|
Minimum and maximum zoom ratios supported by this camera device. Type: float[2] This tag may appear in:
If the camera device supports zoom-out from 1x zoom, minZoom will be less than 1.0, and setting ACAMERA_CONTROL_ZOOM_RATIO to values less than 1.0 increases the camera's field of view. See also: ACAMERA_CONTROL_ZOOM_RATIO |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_MIN_FRAME_DURATIONS
|
This lists the minimum frame duration for each format/size combination for depth output formats. Type: int64[4*n] This tag may appear in:
This should correspond to the frame duration when only that stream is active, with all processing (typically in android.*.mode) set to either OFF or FAST. When multiple streams are used in a request, the minimum frame duration will be max(individual stream min durations). The minimum frame duration of a stream (of a particular format, size) is the same regardless of whether the stream is input or output. See ACAMERA_SENSOR_FRAME_DURATION and ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS for more details about calculating the max frame rate. See also: ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS See also: ACAMERA_SENSOR_FRAME_DURATION |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_MIN_FRAME_DURATIONS_MAXIMUM_RESOLUTION
|
This lists the minimum frame duration for each format/size combination for depth output formats when a CaptureRequest is submitted with ACAMERA_SENSOR_PIXEL_MODE set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_SENSOR_PIXEL_MODE Type: int64[4*n] This tag may appear in:
Analogous to ACAMERA_DEPTH_AVAILABLE_DEPTH_MIN_FRAME_DURATIONS, for configurations which are applicable when ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See ACAMERA_SENSOR_FRAME_DURATION and ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS_MAXIMUM_RESOLUTION for more details about calculating the max frame rate. See also: ACAMERA_DEPTH_AVAILABLE_DEPTH_MIN_FRAME_DURATIONS See also: ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS_MAXIMUM_RESOLUTION See also: ACAMERA_SENSOR_FRAME_DURATION See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS
|
This lists the maximum stall duration for each output format/size combination for depth streams. Type: int64[4*n] This tag may appear in:
A stall duration is how much extra time would get added to the normal minimum frame duration for a repeating request that has streams with non-zero stall. This functions similarly to ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS for depth streams. All depth output stream formats may have a nonzero stall duration. See also: ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS_MAXIMUM_RESOLUTION
|
This lists the maximum stall duration for each output format/size combination for depth streams for CaptureRequests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_SENSOR_PIXEL_MODE Type: int64[4*n] This tag may appear in:
Analogous to ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS, for configurations which are applicable when ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_STREAM_CONFIGURATIONS
|
The available depth dataspace stream configurations that this camera device supports (i.e. format, width, height, output/input stream). Type: int32[n*4] (acamera_metadata_enum_android_depth_available_depth_stream_configurations_t) This tag may appear in:
These are output stream configurations for use with dataSpace HAL_DATASPACE_DEPTH. The configurations are listed as Only devices that support depth output for at least the HAL_PIXEL_FORMAT_Y16 dense depth map may include this entry. A device that also supports the HAL_PIXEL_FORMAT_BLOB sparse depth point cloud must report a single entry for the format in this list as |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DEPTH_STREAM_CONFIGURATIONS_MAXIMUM_RESOLUTION
|
The available depth dataspace stream configurations that this camera device supports (i.e. format, width, height, output/input stream) when a CaptureRequest is submitted with ACAMERA_SENSOR_PIXEL_MODE set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_SENSOR_PIXEL_MODE Type: int32[n*4] (acamera_metadata_enum_android_depth_available_depth_stream_configurations_maximum_resolution_t) This tag may appear in:
Analogous to ACAMERA_DEPTH_AVAILABLE_DEPTH_STREAM_CONFIGURATIONS, for configurations which are applicable when ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_DEPTH_AVAILABLE_DEPTH_STREAM_CONFIGURATIONS See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_MIN_FRAME_DURATIONS
|
This lists the minimum frame duration for each format/size combination for dynamic depth output streams. Type: int64[4*n] This tag may appear in:
This should correspond to the frame duration when only that stream is active, with all processing (typically in android.*.mode) set to either OFF or FAST. When multiple streams are used in a request, the minimum frame duration will be max(individual stream min durations). The minimum frame duration of a stream (of a particular format, size) is the same regardless of whether the stream is input or output. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_MIN_FRAME_DURATIONS_MAXIMUM_RESOLUTION
|
This lists the minimum frame duration for each format/size combination for dynamic depth output streams for CaptureRequests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_SENSOR_PIXEL_MODE Type: int64[4*n] This tag may appear in:
Analogous to ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_MIN_FRAME_DURATIONS, for configurations which are applicable when ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_MIN_FRAME_DURATIONS See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_STALL_DURATIONS
|
This lists the maximum stall duration for each output format/size combination for dynamic depth streams. Type: int64[4*n] This tag may appear in:
A stall duration is how much extra time would get added to the normal minimum frame duration for a repeating request that has streams with non-zero stall. All dynamic depth output streams may have a nonzero stall duration. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_STALL_DURATIONS_MAXIMUM_RESOLUTION
|
This lists the maximum stall duration for each output format/size combination for dynamic depth streams for CaptureRequests where ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_SENSOR_PIXEL_MODE Type: int64[4*n] This tag may appear in:
Analogous to ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_STALL_DURATIONS, for configurations which are applicable when ACAMERA_SENSOR_PIXEL_MODE is set to CameraMetadata::SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION. See also: ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_STALL_DURATIONS See also: ACAMERA_SENSOR_PIXEL_MODE |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACAMERA_DEPTH_AVAILABLE_DYNAMIC_DEPTH_STREAM_CONFIGURATIONS
|
The available dynamic depth dataspace stream configurations that this camera device supports (i.e. format, width, height, output/input stream). Type: int32[n*4] (acamera_metadata_enum_android_depth_available_dynamic_depth_stream_configura |