# Print output for @column tags ?>
public
abstract
class
CameraMetadata
extends Object
java.lang.Object | |
↳ | android.hardware.camera2.CameraMetadata<TKey> |
The base class for camera controls and information.
This class defines the basic key/value map used for querying for camera characteristics or capture results, and for setting camera request parameters.
All instances of CameraMetadata are immutable. The list of keys with getKeys()
never changes, nor do the values returned by any key with #get
throughout
the lifetime of the object.
Constants | |
---|---|
int |
COLOR_CORRECTION_ABERRATION_MODE_FAST
Aberration correction will not slow down capture rate relative to sensor raw output. |
int |
COLOR_CORRECTION_ABERRATION_MODE_HIGH_QUALITY
Aberration correction operates at improved quality but the capture rate might be reduced (relative to sensor raw output rate) |
int |
COLOR_CORRECTION_ABERRATION_MODE_OFF
No aberration correction is applied. |
int |
COLOR_CORRECTION_MODE_FAST
Color correction processing must not slow down capture rate relative to sensor raw output. |
int |
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. |
int |
COLOR_CORRECTION_MODE_TRANSFORM_MATRIX
Use the |
int |
CONTROL_AE_ANTIBANDING_MODE_50HZ
The camera device will adjust exposure duration to avoid banding problems with 50Hz illumination sources. |
int |
CONTROL_AE_ANTIBANDING_MODE_60HZ
The camera device will adjust exposure duration to avoid banding problems with 60Hz illumination sources. |
int |
CONTROL_AE_ANTIBANDING_MODE_AUTO
The camera device will automatically adapt its antibanding routine to the current illumination condition. |
int |
CONTROL_AE_ANTIBANDING_MODE_OFF
The camera device will not adjust exposure duration to avoid banding problems. |
int |
CONTROL_AE_MODE_OFF
The camera device's autoexposure routine is disabled. |
int |
CONTROL_AE_MODE_ON
The camera device's autoexposure routine is active, with no flash control. |
int |
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. |
int |
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. |
int |
CONTROL_AE_MODE_ON_AUTO_FLASH_REDEYE
Like ON_AUTO_FLASH, but with automatic red eye reduction. |
int |
CONTROL_AE_MODE_ON_EXTERNAL_FLASH
An external flash has been turned on. |
int |
CONTROL_AE_PRECAPTURE_TRIGGER_CANCEL
The camera device will cancel any currently active or completed precapture metering sequence, the auto-exposure routine will return to its initial state. |
int |
CONTROL_AE_PRECAPTURE_TRIGGER_IDLE
The trigger is idle. |
int |
CONTROL_AE_PRECAPTURE_TRIGGER_START
The precapture metering sequence will be started by the camera device. |
int |
CONTROL_AE_STATE_CONVERGED
AE has a good set of control values for the current scene. |
int |
CONTROL_AE_STATE_FLASH_REQUIRED
AE has a good set of control values, but flash needs to be fired for good quality still capture. |
int |
CONTROL_AE_STATE_INACTIVE
AE is off or recently reset. |
int |
CONTROL_AE_STATE_LOCKED
AE has been locked. |
int |
CONTROL_AE_STATE_PRECAPTURE
AE has been asked to do a precapture sequence and is currently executing it. |
int |
CONTROL_AE_STATE_SEARCHING
AE doesn't yet have a good set of control values for the current scene. |
int |
CONTROL_AF_MODE_AUTO
Basic automatic focus mode. |
int |
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. |
int |
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. |
int |
CONTROL_AF_MODE_EDOF
Extended depth of field (digital focus) mode. |
int |
CONTROL_AF_MODE_MACRO
Close-up focusing mode. |
int |
CONTROL_AF_MODE_OFF
The auto-focus routine does not control the lens;
|
int |
CONTROL_AF_SCENE_CHANGE_DETECTED
Scene change is detected within the AF region(s). |
int |
CONTROL_AF_SCENE_CHANGE_NOT_DETECTED
Scene change is not detected within the AF region(s). |
int |
CONTROL_AF_STATE_ACTIVE_SCAN
AF is performing an AF scan because it was triggered by AF trigger. |
int |
CONTROL_AF_STATE_FOCUSED_LOCKED
AF believes it is focused correctly and has locked focus. |
int |
CONTROL_AF_STATE_INACTIVE
AF is off or has not yet tried to scan/been asked to scan. |
int |
CONTROL_AF_STATE_NOT_FOCUSED_LOCKED
AF has failed to focus successfully and has locked focus. |
int |
CONTROL_AF_STATE_PASSIVE_FOCUSED
AF currently believes it is in focus, but may restart scanning at any time. |
int |
CONTROL_AF_STATE_PASSIVE_SCAN
AF is currently performing an AF scan initiated the camera device in a continuous autofocus mode. |
int |
CONTROL_AF_STATE_PASSIVE_UNFOCUSED
AF finished a passive scan without finding focus, and may restart scanning at any time. |
int |
CONTROL_AF_TRIGGER_CANCEL
Autofocus will return to its initial state, and cancel any currently active trigger. |
int |
CONTROL_AF_TRIGGER_IDLE
The trigger is idle. |
int |
CONTROL_AF_TRIGGER_START
Autofocus will trigger now. |
int |
CONTROL_AWB_MODE_AUTO
The camera device's auto-white balance routine is active. |
int |
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. |
int |
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. |
int |
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. |
int |
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. |
int |
CONTROL_AWB_MODE_OFF
The camera device's auto-white balance routine is disabled. |
int |
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. |
int |
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. |
int |
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. |
int |
CONTROL_AWB_STATE_CONVERGED
AWB has a good set of control values for the current scene. |
int |
CONTROL_AWB_STATE_INACTIVE
AWB is not in auto mode, or has not yet started metering. |
int |
CONTROL_AWB_STATE_LOCKED
AWB has been locked. |
int |
CONTROL_AWB_STATE_SEARCHING
AWB doesn't yet have a good set of control values for the current scene. |
int |
CONTROL_CAPTURE_INTENT_CUSTOM
The goal of this request doesn't fall into the other categories. |
int |
CONTROL_CAPTURE_INTENT_MANUAL
This request is for manual capture use case where the applications want to directly control the capture parameters. |
int |
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. |
int |
CONTROL_CAPTURE_INTENT_PREVIEW
This request is for a preview-like use case. |
int |
CONTROL_CAPTURE_INTENT_STILL_CAPTURE
This request is for a still capture-type use case. |
int |
CONTROL_CAPTURE_INTENT_VIDEO_RECORD
This request is for a video recording use case. |
int |
CONTROL_CAPTURE_INTENT_VIDEO_SNAPSHOT
This request is for a video snapshot (still image while recording video) use case. |
int |
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. |
int |
CONTROL_EFFECT_MODE_AQUA
An "aqua" effect where a blue hue is added to the image. |
int |
CONTROL_EFFECT_MODE_BLACKBOARD
A "blackboard" effect where the image is typically displayed as regions of black, with white or grey details. |
int |
CONTROL_EFFECT_MODE_MONO
A "monocolor" effect where the image is mapped into a single color. |
int |
CONTROL_EFFECT_MODE_NEGATIVE
A "photo-negative" effect where the image's colors are inverted. |
int |
CONTROL_EFFECT_MODE_OFF
No color effect will be applied. |
int |
CONTROL_EFFECT_MODE_POSTERIZE
A "posterization" effect where the image uses discrete regions of tone rather than a continuous gradient of tones. |
int |
CONTROL_EFFECT_MODE_SEPIA
A "sepia" effect where the image is mapped into warm gray, red, and brown tones. |
int |
CONTROL_EFFECT_MODE_SOLARIZE
A "solarisation" effect (Sabattier effect) where the image is wholly or partially reversed in tone. |
int |
CONTROL_EFFECT_MODE_WHITEBOARD
A "whiteboard" effect where the image is typically displayed as regions of white, with black or grey details. |
int |
CONTROL_EXTENDED_SCENE_MODE_BOKEH_CONTINUOUS
Bokeh effect must not slow down capture rate relative to sensor raw output, and the effect is applied to all processed streams no larger than the maximum streaming dimension. |
int |
CONTROL_EXTENDED_SCENE_MODE_BOKEH_STILL_CAPTURE
High quality bokeh mode is enabled for all non-raw streams (including YUV, JPEG, and IMPLEMENTATION_DEFINED) when capture intent is STILL_CAPTURE. |
int |
CONTROL_EXTENDED_SCENE_MODE_DISABLED
Extended scene mode is disabled. |
int |
CONTROL_MODE_AUTO
Use settings for each individual 3A routine. |
int |
CONTROL_MODE_OFF
Full application control of pipeline. |
int |
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. |
int |
CONTROL_MODE_USE_EXTENDED_SCENE_MODE
Use a specific extended scene mode. |
int |
CONTROL_MODE_USE_SCENE_MODE
Use a specific scene mode. |
int |
CONTROL_SCENE_MODE_ACTION
Optimized for photos of quickly moving objects. |
int |
CONTROL_SCENE_MODE_BARCODE
Optimized for accurately capturing a photo of barcode for use by camera applications that wish to read the barcode value. |
int |
CONTROL_SCENE_MODE_BEACH
Optimized for bright, outdoor beach settings. |
int |
CONTROL_SCENE_MODE_CANDLELIGHT
Optimized for dim settings where the main light source is a candle. |
int |
CONTROL_SCENE_MODE_DISABLED
Indicates that no scene modes are set for a given capture request. |
int |
CONTROL_SCENE_MODE_FACE_PRIORITY
If face detection support exists, use face detection data for auto-focus, auto-white balance, and auto-exposure routines. |
int |
CONTROL_SCENE_MODE_FIREWORKS
Optimized for nighttime photos of fireworks. |
int |
CONTROL_SCENE_MODE_HDR
Turn on a device-specific high dynamic range (HDR) mode. |
int |
CONTROL_SCENE_MODE_HIGH_SPEED_VIDEO
This constant is deprecated. Please refer to this API documentation to find the alternatives |
int |
CONTROL_SCENE_MODE_LANDSCAPE
Optimized for photos of distant macroscopic objects. |
int |
CONTROL_SCENE_MODE_NIGHT
Optimized for low-light settings. |
int |
CONTROL_SCENE_MODE_NIGHT_PORTRAIT
Optimized for still photos of people in low-light settings. |
int |
CONTROL_SCENE_MODE_PARTY
Optimized for dim, indoor settings with multiple moving people. |
int |
CONTROL_SCENE_MODE_PORTRAIT
Optimized for still photos of people. |
int |
CONTROL_SCENE_MODE_SNOW
Optimized for bright, outdoor settings containing snow. |
int |
CONTROL_SCENE_MODE_SPORTS
Optimized for photos of quickly moving people. |
int |
CONTROL_SCENE_MODE_STEADYPHOTO
Optimized to avoid blurry photos due to small amounts of device motion (for example: due to hand shake). |
int |
CONTROL_SCENE_MODE_SUNSET
Optimized for scenes of the setting sun. |
int |
CONTROL_SCENE_MODE_THEATRE
Optimized for dim, indoor settings where flash must remain off. |
int |
CONTROL_VIDEO_STABILIZATION_MODE_OFF
Video stabilization is disabled. |
int |
CONTROL_VIDEO_STABILIZATION_MODE_ON
Video stabilization is enabled. |
int |
DISTORTION_CORRECTION_MODE_FAST
Lens distortion correction is applied without reducing frame rate relative to sensor output. |
int |
DISTORTION_CORRECTION_MODE_HIGH_QUALITY
High-quality distortion correction is applied, at the cost of possibly reduced frame rate relative to sensor output. |
int |
DISTORTION_CORRECTION_MODE_OFF
No distortion correction is applied. |
int |
EDGE_MODE_FAST
Apply edge enhancement at a quality level that does not slow down frame rate relative to sensor output. |
int |
EDGE_MODE_HIGH_QUALITY
Apply high-quality edge enhancement, at a cost of possibly reduced output frame rate. |
int |
EDGE_MODE_OFF
No edge enhancement is applied. |
int |
EDGE_MODE_ZERO_SHUTTER_LAG
Edge enhancement is applied at different levels for different output streams, based on resolution. |
int |
FLASH_MODE_OFF
Do not fire the flash for this capture. |
int |
FLASH_MODE_SINGLE
If the flash is available and charged, fire flash for this capture. |
int |
FLASH_MODE_TORCH
Transition flash to continuously on. |
int |
FLASH_STATE_CHARGING
Flash is charging and cannot be fired. |
int |
FLASH_STATE_FIRED
Flash fired for this capture. |
int |
FLASH_STATE_PARTIAL
Flash partially illuminated this frame. |
int |
FLASH_STATE_READY
Flash is ready to fire. |
int |
FLASH_STATE_UNAVAILABLE
No flash on camera. |
int |
HOT_PIXEL_MODE_FAST
Hot pixel correction is applied, without reducing frame rate relative to sensor raw output. |
int |
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. |
int |
HOT_PIXEL_MODE_OFF
No hot pixel correction is applied. |
int |
INFO_SUPPORTED_HARDWARE_LEVEL_3
This camera device is capable of YUV reprocessing and RAW data capture, in addition to FULL-level capabilities. |
int |
INFO_SUPPORTED_HARDWARE_LEVEL_EXTERNAL
This camera device is backed by an external camera connected to this Android device. |
int |
INFO_SUPPORTED_HARDWARE_LEVEL_FULL
This camera device is capable of supporting advanced imaging applications. |
int |
INFO_SUPPORTED_HARDWARE_LEVEL_LEGACY
This camera device is running in backward compatibility mode. |
int |
INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
This camera device does not have enough capabilities to qualify as a |
int |
LENS_FACING_BACK
The camera device faces the opposite direction as the device's screen. |
int |
LENS_FACING_EXTERNAL
The camera device is an external camera, and has no fixed facing relative to the device's screen. |
int |
LENS_FACING_FRONT
The camera device faces the same direction as the device's screen. |
int |
LENS_INFO_FOCUS_DISTANCE_CALIBRATION_APPROXIMATE
The lens focus distance is measured in diopters. |
int |
LENS_INFO_FOCUS_DISTANCE_CALIBRATION_CALIBRATED
The lens focus distance is measured in diopters, and is calibrated. |
int |
LENS_INFO_FOCUS_DISTANCE_CALIBRATION_UNCALIBRATED
The lens focus distance is not accurate, and the units used for
|
int |
LENS_OPTICAL_STABILIZATION_MODE_OFF
Optical stabilization is unavailable. |
int |
LENS_OPTICAL_STABILIZATION_MODE_ON
Optical stabilization is enabled. |
int |
LENS_POSE_REFERENCE_GYROSCOPE
The value of |
int |
LENS_POSE_REFERENCE_PRIMARY_CAMERA
The value of |
int |
LENS_POSE_REFERENCE_UNDEFINED
The camera device cannot represent the values of |
int |
LENS_STATE_MOVING
One or several of the lens parameters
( |
int |
LENS_STATE_STATIONARY
The lens parameters ( |
int |
LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_APPROXIMATE
A software mechanism is used to synchronize between the physical cameras. |
int |
LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_CALIBRATED
The camera device supports frame timestamp synchronization at the hardware level, and the timestamp of a physical stream image accurately reflects its start-of-exposure time. |
int |
NOISE_REDUCTION_MODE_FAST
Noise reduction is applied without reducing frame rate relative to sensor output. |
int |
NOISE_REDUCTION_MODE_HIGH_QUALITY
High-quality noise reduction is applied, at the cost of possibly reduced frame rate relative to sensor output. |
int |
NOISE_REDUCTION_MODE_MINIMAL
MINIMAL noise reduction is applied without reducing frame rate relative to sensor output. |
int |
NOISE_REDUCTION_MODE_OFF
No noise reduction is applied. |
int |
NOISE_REDUCTION_MODE_ZERO_SHUTTER_LAG
Noise reduction is applied at different levels for different output streams, based on resolution. |
int |
REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE
The minimal set of capabilities that every camera
device (regardless of |
int |
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. |
int |
REQUEST_AVAILABLE_CAPABILITIES_CONSTRAINED_HIGH_SPEED_VIDEO
The device supports constrained high speed video recording (frame rate >=120fps) use case. |
int |
REQUEST_AVAILABLE_CAPABILITIES_DEPTH_OUTPUT
The camera device can produce depth measurements from its field of view. |
int |
REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA
The camera device is a logical camera backed by two or more physical cameras. |
int |
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_POST_PROCESSING
The camera device post-processing stages can be manually controlled. |
int |
REQUEST_AVAILABLE_CAPABILITIES_MANUAL_SENSOR
The camera device can be manually controlled (3A algorithms such as auto-exposure, and auto-focus can be bypassed). |
int |
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. |
int |
REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING
The camera device supports the MOTION_TRACKING value for
|
int |
REQUEST_AVAILABLE_CAPABILITIES_OFFLINE_PROCESSING
The camera device supports the OFFLINE_PROCESSING use case. |
int |
REQUEST_AVAILABLE_CAPABILITIES_PRIVATE_REPROCESSING
The camera device supports the Zero Shutter Lag reprocessing use case. |
int |
REQUEST_AVAILABLE_CAPABILITIES_RAW
The camera device supports outputting RAW buffers and metadata for interpreting them. |
int |
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. |
int |
REQUEST_AVAILABLE_CAPABILITIES_REMOSAIC_REPROCESSING
The device supports reprocessing from the |
int |
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). |
int |
REQUEST_AVAILABLE_CAPABILITIES_SYSTEM_CAMERA
The camera device is only accessible by Android's system components and privileged applications. |
int |
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
|
int |
REQUEST_AVAILABLE_CAPABILITIES_YUV_REPROCESSING
The camera device supports the YUV_420_888 reprocessing use case, similar as PRIVATE_REPROCESSING, This capability requires the camera device to support the following:
|
int |
SCALER_CROPPING_TYPE_CENTER_ONLY
The camera device only supports centered crop regions. |
int |
SCALER_CROPPING_TYPE_FREEFORM
The camera device supports arbitrarily chosen crop regions. |
int |
SCALER_ROTATE_AND_CROP_180
Processed images are rotated by 180 degrees. |
int |
SCALER_ROTATE_AND_CROP_270
Processed images are rotated by 270 degrees clockwise, and then cropped to the original aspect ratio. |
int |
SCALER_ROTATE_AND_CROP_90
Processed images are rotated by 90 degrees clockwise, and then cropped to the original aspect ratio. |
int |
SCALER_ROTATE_AND_CROP_AUTO
The camera API automatically selects the best concrete value for rotate-and-crop based on the application's support for resizability and the current multi-window mode. |
int |
SCALER_ROTATE_AND_CROP_NONE
No rotate and crop is applied. |
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_BGGR
|
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_GBRG
|
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_GRBG
|
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_MONO
Sensor doesn't have any Bayer color filter. |
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_NIR
Sensor has a near infrared filter capturing light with wavelength between roughly 750nm and 1400nm, and the same filter covers the whole sensor array. |
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_RGB
Sensor is not Bayer; output has 3 16-bit values for each pixel, instead of just 1 16-bit value per pixel. |
int |
SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_RGGB
|
int |
SENSOR_INFO_TIMESTAMP_SOURCE_REALTIME
Timestamps from |
int |
SENSOR_INFO_TIMESTAMP_SOURCE_UNKNOWN
Timestamps from |
int |
SENSOR_PIXEL_MODE_DEFAULT
This is the default sensor pixel mode. |
int |
SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION
This sensor pixel mode is offered by devices with capability
|
int |
SENSOR_REFERENCE_ILLUMINANT1_CLOUDY_WEATHER
|
int |
SENSOR_REFERENCE_ILLUMINANT1_COOL_WHITE_FLUORESCENT
W 3900 - 4500K |
int |
SENSOR_REFERENCE_ILLUMINANT1_D50
|
int |
SENSOR_REFERENCE_ILLUMINANT1_D55
|
int |
SENSOR_REFERENCE_ILLUMINANT1_D65
|
int |
SENSOR_REFERENCE_ILLUMINANT1_D75
|
int |
SENSOR_REFERENCE_ILLUMINANT1_DAYLIGHT
|
int |
SENSOR_REFERENCE_ILLUMINANT1_DAYLIGHT_FLUORESCENT
D 5700 - 7100K |
int |
SENSOR_REFERENCE_ILLUMINANT1_DAY_WHITE_FLUORESCENT
N 4600 - 5400K |
int |
SENSOR_REFERENCE_ILLUMINANT1_FINE_WEATHER
|
int |
SENSOR_REFERENCE_ILLUMINANT1_FLASH
|
int |
SENSOR_REFERENCE_ILLUMINANT1_FLUORESCENT
|
int |
SENSOR_REFERENCE_ILLUMINANT1_ISO_STUDIO_TUNGSTEN
|
int |
SENSOR_REFERENCE_ILLUMINANT1_SHADE
|
int |
SENSOR_REFERENCE_ILLUMINANT1_STANDARD_A
|
int |
SENSOR_REFERENCE_ILLUMINANT1_STANDARD_B
|
int |
SENSOR_REFERENCE_ILLUMINANT1_STANDARD_C
|
int |
SENSOR_REFERENCE_ILLUMINANT1_TUNGSTEN
Incandescent light |
int |
SENSOR_REFERENCE_ILLUMINANT1_WHITE_FLUORESCENT
WW 3200 - 3700K |
int |
SENSOR_TEST_PATTERN_MODE_COLOR_BARS
All pixel data is replaced with an 8-bar color pattern. |
int |
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. |
int |
SENSOR_TEST_PATTERN_MODE_CUSTOM1
The first custom test pattern. |
int |
SENSOR_TEST_PATTERN_MODE_OFF
No test pattern mode is used, and the camera device returns captures from the image sensor. |
int |
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). |
int |
SENSOR_TEST_PATTERN_MODE_SOLID_COLOR
Each pixel in |
int |
SHADING_MODE_FAST
Apply lens shading corrections, without slowing frame rate relative to sensor raw output |
int |
SHADING_MODE_HIGH_QUALITY
Apply high-quality lens shading correction, at the cost of possibly reduced frame rate. |
int |
SHADING_MODE_OFF
No lens shading correction is applied. |
int |
STATISTICS_FACE_DETECT_MODE_FULL
Return all face metadata. |
int |
STATISTICS_FACE_DETECT_MODE_OFF
Do not include face detection statistics in capture results. |
int |
STATISTICS_FACE_DETECT_MODE_SIMPLE
Return face rectangle and confidence values only. |
int |
STATISTICS_LENS_SHADING_MAP_MODE_OFF
Do not include a lens shading map in the capture result. |
int |
STATISTICS_LENS_SHADING_MAP_MODE_ON
Include a lens shading map in the capture result. |
int |
STATISTICS_OIS_DATA_MODE_OFF
Do not include OIS data in the capture result. |
int |
STATISTICS_OIS_DATA_MODE_ON
Include OIS data in the capture result. |
int |
STATISTICS_SCENE_FLICKER_50HZ
The camera device detects illumination flickering at 50Hz in the current scene. |
int |
STATISTICS_SCENE_FLICKER_60HZ
The camera device detects illumination flickering at 60Hz in the current scene. |
int |
STATISTICS_SCENE_FLICKER_NONE
The camera device does not detect any flickering illumination in the current scene. |
int |
SYNC_MAX_LATENCY_PER_FRAME_CONTROL
Every frame has the requests immediately applied. |
int |
SYNC_MAX_LATENCY_UNKNOWN
Each new frame has some subset (potentially the entire set) of the past requests applied to the camera settings. |
int |
TONEMAP_MODE_CONTRAST_CURVE
Use the tone mapping curve specified in
the |
int |
TONEMAP_MODE_FAST
Advanced gamma mapping and color enhancement may be applied, without reducing frame rate compared to raw sensor output. |
int |
TONEMAP_MODE_GAMMA_VALUE
Use the gamma value specified in |
int |
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. |
int |
TONEMAP_MODE_PRESET_CURVE
Use the preset tonemapping curve specified in
|
int |
TONEMAP_PRESET_CURVE_REC709
Tonemapping curve is defined by ITU-R BT.709 |
int |
TONEMAP_PRESET_CURVE_SRGB
Tonemapping curve is defined by sRGB |
Public methods | |
---|---|
List<TKey>
|
getKeys()
Returns a list of the keys contained in this map. |
Inherited methods | |
---|---|
public static final int COLOR_CORRECTION_ABERRATION_MODE_FAST
Aberration correction will not slow down capture rate relative to sensor raw output.
Constant Value: 1 (0x00000001)
public static final int COLOR_CORRECTION_ABERRATION_MODE_HIGH_QUALITY
Aberration correction operates at improved quality but the capture rate might be reduced (relative to sensor raw output rate)
Constant Value: 2 (0x00000002)
public static final int COLOR_CORRECTION_ABERRATION_MODE_OFF
No aberration correction is applied.
Constant Value: 0 (0x00000000)
public static final int 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
, then
the camera device uses the last frame's AWB values
(or defaults if AWB has never been run).android.control.awbMode
!= OFF
Constant Value: 1 (0x00000001)
public static final int 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
, then
the camera device uses the last frame's AWB values
(or defaults if AWB has never been run).android.control.awbMode
!= OFF
Constant Value: 2 (0x00000002)
public static final int COLOR_CORRECTION_MODE_TRANSFORM_MATRIX
Use the android.colorCorrection.transform
matrix
and android.colorCorrection.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
, then
TRANSFORM_MATRIX is ignored. The camera device will override
this value to either FAST or HIGH_QUALITY.android.control.awbMode
!= OFF
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_AE_ANTIBANDING_MODE_50HZ
The camera device will adjust exposure duration to avoid banding problems with 50Hz illumination sources.
Constant Value: 1 (0x00000001)
public static final int CONTROL_AE_ANTIBANDING_MODE_60HZ
The camera device will adjust exposure duration to avoid banding problems with 60Hz illumination sources.
Constant Value: 2 (0x00000002)
public static final int CONTROL_AE_ANTIBANDING_MODE_AUTO
The camera device will automatically adapt its antibanding routine to the current illumination condition. This is the default mode if AUTO is available on given camera device.
Constant Value: 3 (0x00000003)
public static final int CONTROL_AE_ANTIBANDING_MODE_OFF
The camera device will not adjust exposure duration to avoid banding problems.
Constant Value: 0 (0x00000000)
public static final int CONTROL_AE_MODE_OFF
The camera device's autoexposure routine is disabled.
The application-selected android.sensor.exposureTime
,
android.sensor.sensitivity
and
android.sensor.frameDuration
are used by the camera
device, along with android.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 android.control.awbMode
, android.control.afMode
,
android.control.awbLock
, and android.control.afTrigger
for more details.
LEGACY devices do not support the OFF mode and will override attempts to use this value to ON.
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_AE_MODE_ON
The camera device's autoexposure routine is active, with no flash control.
The application's values for
android.sensor.exposureTime
,
android.sensor.sensitivity
, and
android.sensor.frameDuration
are ignored. The
application has control over the various
android.flash.* fields.
See also:
Constant Value: 1 (0x00000001)
public static final int 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 android.control.aePrecaptureTrigger
) and
will always be fired for captures for which the
android.control.captureIntent
field is set to
STILL_CAPTURE
See also:
Constant Value: 3 (0x00000003)
public static final int 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 android.control.aePrecaptureTrigger
) and
may be fired for captures for which the
android.control.captureIntent
field is set to
STILL_CAPTURE
See also:
Constant Value: 2 (0x00000002)
public static final int 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.
See also:
Constant Value: 4 (0x00000004)
public static final int 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 recaculated 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, android.control.aeState
must
be FLASH_REQUIRED after the camera device finishes AE scan and it's too dark without
flash.
Constant Value: 5 (0x00000005)
public static final int CONTROL_AE_PRECAPTURE_TRIGGER_CANCEL
The camera device will cancel any currently active or completed precapture metering sequence, the auto-exposure routine will return to its initial state.
Constant Value: 2 (0x00000002)
public static final int CONTROL_AE_PRECAPTURE_TRIGGER_IDLE
The trigger is idle.
Constant Value: 0 (0x00000000)
public static final int CONTROL_AE_PRECAPTURE_TRIGGER_START
The precapture metering sequence will be started by the camera device.
The exact effect of the precapture trigger depends on the current AE mode and state.
Constant Value: 1 (0x00000001)
public static final int CONTROL_AE_STATE_CONVERGED
AE has a good set of control values for the current scene.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_AE_STATE_FLASH_REQUIRED
AE has a good set of control values, but flash needs to be fired for good quality still capture.
See also:
Constant Value: 4 (0x00000004)
public static final int 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.
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_AE_STATE_LOCKED
AE has been locked.
See also:
Constant Value: 3 (0x00000003)
public static final int CONTROL_AE_STATE_PRECAPTURE
AE has been asked to do a precapture sequence and is currently executing it.
Precapture can be triggered through setting
android.control.aePrecaptureTrigger
to START. Currently
active and completed (if it causes camera device internal AE lock) precapture
metering sequence can be canceled through setting
android.control.aePrecaptureTrigger
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.
Constant Value: 5 (0x00000005)
public static final int 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.
See also:
Constant Value: 1 (0x00000001)
public static final int 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 android.lens.info.minimumFocusDistance
to determine if lens
is fixed-focus.
Triggering AF_CANCEL resets the lens position to default, and sets the AF state to INACTIVE.
Constant Value: 1 (0x00000001)
public static final int 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.
See also:
Constant Value: 4 (0x00000004)
public static final int 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.
See also:
Constant Value: 3 (0x00000003)
public static final int 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.
See also:
Constant Value: 5 (0x00000005)
public static final int 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.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_AF_MODE_OFF
The auto-focus routine does not control the lens;
android.lens.focusDistance
is controlled by the
application.
Constant Value: 0 (0x00000000)
public static final int CONTROL_AF_SCENE_CHANGE_DETECTED
Scene change is detected within the AF region(s).
See also:
Constant Value: 1 (0x00000001)
public static final int CONTROL_AF_SCENE_CHANGE_NOT_DETECTED
Scene change is not detected within the AF region(s).
See also:
Constant Value: 0 (0x00000000)
public static final int 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.
See also:
Constant Value: 3 (0x00000003)
public static final int 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 (android.control.afTrigger
), when good focus has been obtained.
The lens will remain stationary until the AF mode (android.control.afMode
) is changed or
a new AF trigger is sent to the camera device (android.control.afTrigger
).
See also:
Constant Value: 4 (0x00000004)
public static final int 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.
See also:
Constant Value: 0 (0x00000000)
public static final int 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 (android.control.afTrigger
), when good focus cannot be obtained.
The lens will remain stationary until the AF mode (android.control.afMode
) is changed or
a new AF trigger is sent to the camera device (android.control.afTrigger
).
See also:
Constant Value: 5 (0x00000005)
public static final int 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.
See also:
Constant Value: 2 (0x00000002)
public static final int 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.
See also:
Constant Value: 1 (0x00000001)
public static final int 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.
See also:
Constant Value: 6 (0x00000006)
public static final int CONTROL_AF_TRIGGER_CANCEL
Autofocus will return to its initial state, and cancel any currently active trigger.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_AF_TRIGGER_IDLE
The trigger is idle.
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_AF_TRIGGER_START
Autofocus will trigger now.
See also:
Constant Value: 1 (0x00000001)
public static final int CONTROL_AWB_MODE_AUTO
The camera device's auto-white balance routine is active.
The application's values for android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 1 (0x00000001)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 6 (0x00000006)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 5 (0x00000005)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 3 (0x00000003)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 2 (0x00000002)
public static final int CONTROL_AWB_MODE_OFF
The camera device's auto-white balance routine is disabled.
The application-selected color transform matrix
(android.colorCorrection.transform
) and gains
(android.colorCorrection.gains
) are used by the camera
device for manual white balance control.
See also:
Constant Value: 0 (0x00000000)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 8 (0x00000008)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 7 (0x00000007)
public static final int 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 android.colorCorrection.transform
and android.colorCorrection.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:
Constant Value: 4 (0x00000004)
public static final int CONTROL_AWB_STATE_CONVERGED
AWB has a good set of control values for the current scene.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_AWB_STATE_INACTIVE
AWB is not in auto mode, or has not yet started metering.
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.
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_AWB_STATE_LOCKED
AWB has been locked.
See also:
Constant Value: 3 (0x00000003)
public static final int CONTROL_AWB_STATE_SEARCHING
AWB 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.
See also:
Constant Value: 1 (0x00000001)
public static final int 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.
See also:
Constant Value: 0 (0x00000000)
public static final int 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
android.sensor.exposureTime
, android.sensor.sensitivity
, etc.
See also:
Constant Value: 6 (0x00000006)
public static final int 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.
See also:
Constant Value: 7 (0x00000007)
public static final int 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.
See also:
Constant Value: 1 (0x00000001)
public static final int 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.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_CAPTURE_INTENT_VIDEO_RECORD
This request is for a video recording use case.
See also:
Constant Value: 3 (0x00000003)
public static final int 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.
See also:
Constant Value: 4 (0x00000004)
public static final int 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.
See also:
Constant Value: 5 (0x00000005)
public static final int CONTROL_EFFECT_MODE_AQUA
An "aqua" effect where a blue hue is added to the image.
See also:
Constant Value: 8 (0x00000008)
public static final int CONTROL_EFFECT_MODE_BLACKBOARD
A "blackboard" effect where the image is typically displayed as regions of black, with white or grey details.
See also:
Constant Value: 7 (0x00000007)
public static final int CONTROL_EFFECT_MODE_MONO
A "monocolor" effect where the image is mapped into a single color.
This will typically be grayscale.
See also:
Constant Value: 1 (0x00000001)
public static final int CONTROL_EFFECT_MODE_NEGATIVE
A "photo-negative" effect where the image's colors are inverted.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_EFFECT_MODE_OFF
No color effect will be applied.
See also:
Constant Value: 0 (0x00000000)
public static final int CONTROL_EFFECT_MODE_POSTERIZE
A "posterization" effect where the image uses discrete regions of tone rather than a continuous gradient of tones.
See also:
Constant Value: 5 (0x00000005)
public static final int CONTROL_EFFECT_MODE_SEPIA
A "sepia" effect where the image is mapped into warm gray, red, and brown tones.
See also:
Constant Value: 4 (0x00000004)
public static final int CONTROL_EFFECT_MODE_SOLARIZE
A "solarisation" effect (Sabattier effect) where the image is wholly or partially reversed in tone.
See also:
Constant Value: 3 (0x00000003)
public static final int CONTROL_EFFECT_MODE_WHITEBOARD
A "whiteboard" effect where the image is typically displayed as regions of white, with black or grey details.
See also:
Constant Value: 6 (0x00000006)
public static final int CONTROL_EXTENDED_SCENE_MODE_BOKEH_CONTINUOUS
Bokeh effect must not slow down capture rate relative to sensor raw output, and the effect is applied to all processed streams no larger than the maximum streaming dimension. This mode should be used if performance and power are a priority, such as video recording.
Constant Value: 2 (0x00000002)
public static final int CONTROL_EXTENDED_SCENE_MODE_BOKEH_STILL_CAPTURE
High quality bokeh mode is enabled for all non-raw streams (including YUV, JPEG, and IMPLEMENTATION_DEFINED) when capture intent is STILL_CAPTURE. Due to the extra image processing, this mode may introduce additional stall to non-raw streams. This mode should be used in high quality still capture use case.
Constant Value: 1 (0x00000001)
public static final int CONTROL_EXTENDED_SCENE_MODE_DISABLED
Extended scene mode is disabled.
Constant Value: 0 (0x00000000)
public static final int CONTROL_MODE_AUTO
Use settings for each individual 3A routine.
Manual control of capture parameters is disabled. All controls in android.control.* besides sceneMode take effect.
See also:
Constant Value: 1 (0x00000001)
public static final int 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
android.control.* have any effect, except that
android.control.captureIntent
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.
Constant Value: 0 (0x00000000)
public static final int 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.
See also:
Constant Value: 3 (0x00000003)
public static final int 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).
See also:
Constant Value: 4 (0x00000004)
public static final int 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.
android.control.availableSceneModes
contain some modes other than DISABLED).
For extended scene modes such as BOKEH, please use USE_EXTENDED_SCENE_MODE instead.
Constant Value: 2 (0x00000002)
public static final int CONTROL_SCENE_MODE_ACTION
Optimized for photos of quickly moving objects.
Similar to SPORTS.
See also:
Constant Value: 2 (0x00000002)
public static final int CONTROL_SCENE_MODE_BARCODE
Optimized for accurately capturing a photo of barcode for use by camera applications that wish to read the barcode value.
See also:
Constant Value: 16 (0x00000010)
public static final int CONTROL_SCENE_MODE_BEACH
Optimized for bright, outdoor beach settings.
See also:
Constant Value: 8 (0x00000008)
public static final int CONTROL_SCENE_MODE_CANDLELIGHT
Optimized for dim settings where the main light source is a candle.
See also:
Constant Value: 15 (0x0000000f)
public static final int CONTROL_SCENE_MODE_DISABLED
Indicates that no scene modes are set for a given capture request.
See also:
Constant Value: 0 (0x00000000)
public static final int 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. android.statistics.faceDetectMode
is set to OFF),
this should still operate correctly (but will not return
face detection statistics to the framework).
Unlike the other scene modes, android.control.aeMode
,
android.control.awbMode
, and android.control.afMode
remain active when FACE_PRIORITY is set.
See also:
Constant Value: 1 (0x00000001)
public static final int CONTROL_SCENE_MODE_FIREWORKS
Optimized for nighttime photos of fireworks.
See also:
Constant Value: 12 (0x0000000c)
public static final int 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 android.control.captureIntent
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.
Constant Value: 18 (0x00000012)
public static final int CONTROL_SCENE_MODE_HIGH_SPEED_VIDEO
This constant is deprecated.
Please refer to this API documentation to find the alternatives
This is deprecated, please use CameraDevice.createConstrainedHighSpeedCaptureSession(List
and CameraConstrainedHighSpeedCaptureSession.createHighSpeedRequestList(CaptureRequest)
for high speed video recording.
Optimized for high speed video recording (frame rate >=60fps) use case.
The supported high speed video sizes and fps ranges are specified in
android.control.availableHighSpeedVideoConfigurations. To get desired
output frame rates, the application is only allowed to select video size
and fps range combinations listed in this static metadata. The fps range
can be control via android.control.aeTargetFpsRange
.
In this mode, the camera device will override aeMode, awbMode, and afMode to
ON, ON, and CONTINUOUS_VIDEO, respectively. All post-processing block mode
controls will be overridden to be FAST. Therefore, no manual control of capture
and post-processing parameters is possible. All other controls operate the
same as when android.control.mode
== AUTO. This means that all other
android.control.* fields continue to work, such as
android.control.aeTargetFpsRange
android.control.aeExposureCompensation
android.control.aeLock
android.control.awbLock
android.control.effectMode
android.control.aeRegions
android.control.afRegions
android.control.awbRegions
android.control.afTrigger
android.control.aePrecaptureTrigger
android.control.zoomRatio
Outside of android.control.*, the following controls will work:
android.flash.mode
(automatic flash for still capture will not work since aeMode is ON)android.lens.opticalStabilizationMode
(if it is supported)android.scaler.cropRegion
android.statistics.faceDetectMode
For high speed recording use case, the actual maximum supported frame rate may be lower than what camera can output, depending on the destination Surfaces for the image data. For example, if the destination surface is from video encoder, the application need check if the video encoder is capable of supporting the high frame rate for a given video size, or it will end up with lower recording frame rate. If the destination surface is from preview window, the preview frame rate will be bounded by the screen refresh rate.
The camera device will only support up to 2 output high speed streams (processed non-stalling format defined in android.request.maxNumOutputStreams) in this mode. This control will be effective only if all of below conditions are true:
When above conditions are NOT satistied, the controls of this mode and
android.control.aeTargetFpsRange
will be ignored by the camera device,
the camera device will fall back to android.control.mode
==
AUTO,
and the returned capture result metadata will give the fps range choosen
by the camera device.
Switching into or out of this mode may trigger some camera ISP/sensor reconfigurations, which may introduce extra latency. It is recommended that the application avoids unnecessary scene mode switch as much as possible.
See also:
CaptureRequest.CONTROL_AE_EXPOSURE_COMPENSATION
CaptureRequest.CONTROL_AE_LOCK
CaptureRequest.CONTROL_AE_PRECAPTURE_TRIGGER
CaptureRequest.CONTROL_AE_REGIONS
CaptureRequest.CONTROL_AE_TARGET_FPS_RANGE
CaptureRequest.CONTROL_AF_REGIONS
CaptureRequest.CONTROL_AF_TRIGGER
CaptureRequest.CONTROL_AWB_LOCK
CaptureRequest.CONTROL_AWB_REGIONS
CaptureRequest.CONTROL_EFFECT_MODE
CaptureRequest.CONTROL_MODE
CaptureRequest.CONTROL_ZOOM_RATIO
CaptureRequest.FLASH_MODE
CaptureRequest.LENS_OPTICAL_STABILIZATION_MODE
CaptureRequest.SCALER_CROP_REGION
CaptureRequest.STATISTICS_FACE_DETECT_MODE
CaptureRequest.CONTROL_SCENE_MODE
Constant Value: 17 (0x00000011)
public static final int CONTROL_SCENE_MODE_LANDSCAPE
Optimized for photos of distant macroscopic objects.
See also:
Constant Value: 4 (0x00000004)
public static final int CONTROL_SCENE_MODE_NIGHT
Optimized for low-light settings.
See also:
Constant Value: 5 (0x00000005)
public static final int CONTROL_SCENE_MODE_NIGHT_PORTRAIT
Optimized for still photos of people in low-light settings.
See also:
Constant Value: 6 (0x00000006)
public static final int CONTROL_SCENE_MODE_PARTY
Optimized for dim, indoor settings with multiple moving people.
See also:
Constant Value: 14 (0x0000000e)
public static final int CONTROL_SCENE_MODE_PORTRAIT
Optimized for still photos of people.
See also:
Constant Value: 3 (0x00000003)
public static final int CONTROL_SCENE_MODE_SNOW
Optimized for bright, outdoor settings containing snow.
See also:
Constant Value: 9 (0x00000009)
public static final int CONTROL_SCENE_MODE_SPORTS
Optimized for photos of quickly moving people.
Similar to ACTION.
See also:
Constant Value: 13 (0x0000000d)
public static final int CONTROL_SCENE_MODE_STEADYPHOTO
Optimized to avoid blurry photos due to small amounts of device motion (for example: due to hand shake).
See also:
Constant Value: 11 (0x0000000b)
public static final int CONTROL_SCENE_MODE_SUNSET
Optimized for scenes of the setting sun.
See also:
Constant Value: 10 (0x0000000a)
public static final int CONTROL_SCENE_MODE_THEATRE
Optimized for dim, indoor settings where flash must remain off.
See also:
Constant Value: 7 (0x00000007)
public static final int CONTROL_VIDEO_STABILIZATION_MODE_OFF
Video stabilization is disabled.
Constant Value: 0 (0x00000000)
public static final int CONTROL_VIDEO_STABILIZATION_MODE_ON
Video stabilization is enabled.
Constant Value: 1 (0x00000001)
public static final int DISTORTION_CORRECTION_MODE_FAST
Lens distortion correction is applied without reducing frame rate relative to sensor output. It may be the same as OFF if distortion correction would reduce frame rate relative to sensor.
Constant Value: 1 (0x00000001)
public static final int DISTORTION_CORRECTION_MODE_HIGH_QUALITY
High-quality distortion correction is applied, at the cost of possibly reduced frame rate relative to sensor output.
Constant Value: 2 (0x00000002)
public static final int DISTORTION_CORRECTION_MODE_OFF
No distortion correction is applied.
Constant Value: 0 (0x00000000)
public static final int 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.
See also:
Constant Value: 1 (0x00000001)
public static final int EDGE_MODE_HIGH_QUALITY
Apply high-quality edge enhancement, at a cost of possibly reduced output frame rate.
See also:
Constant Value: 2 (0x00000002)
public static final int EDGE_MODE_OFF
No edge enhancement is applied.
See also:
Constant Value: 0 (0x00000000)
public static final int 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 CameraDevice.createCaptureSession(SessionConfiguration)
)
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
(android.request.availableCapabilities
lists either of those capabilities) and it will
be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template.
Constant Value: 3 (0x00000003)
public static final int FLASH_MODE_OFF
Do not fire the flash for this capture.
See also:
Constant Value: 0 (0x00000000)
public static final int FLASH_MODE_SINGLE
If the flash is available and charged, fire flash for this capture.
See also:
Constant Value: 1 (0x00000001)
public static final int FLASH_MODE_TORCH
Transition flash to continuously on.
See also:
Constant Value: 2 (0x00000002)
public static final int FLASH_STATE_CHARGING
Flash is charging and cannot be fired.
See also:
Constant Value: 1 (0x00000001)
public static final int FLASH_STATE_FIRED
Flash fired for this capture.
See also:
Constant Value: 3 (0x00000003)
public static final int FLASH_STATE_PARTIAL
Flash partially illuminated this frame.
This is usually due to the next or previous frame having the flash fire, and the flash spilling into this capture due to hardware limitations.
See also:
Constant Value: 4 (0x00000004)
public static final int FLASH_STATE_READY
Flash is ready to fire.
See also:
Constant Value: 2 (0x00000002)
public static final int FLASH_STATE_UNAVAILABLE
No flash on camera.
See also:
Constant Value: 0 (0x00000000)
public static final int 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 android.statistics.hotPixelMap
.
Constant Value: 1 (0x00000001)
public static final int 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 android.statistics.hotPixelMap
.
Constant Value: 2 (0x00000002)
public static final int 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 android.statistics.hotPixelMap
.
Constant Value: 0 (0x00000000)
public static final int 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 LEVEL_3
, RAW
, FULL
, LEGACY
and
LIMITED
tables in the createCaptureSession
documentation are guaranteed to be supported.
The following additional capabilities are guaranteed to be supported:
YUV_REPROCESSING
capability (android.request.availableCapabilities
contains
YUV_REPROCESSING
)RAW
capability (android.request.availableCapabilities
contains
RAW
)See also:
Constant Value: 3 (0x00000003)
public static final int 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:
android.sensor.orientation
See also:
CaptureRequest.LENS_FOCAL_LENGTH
CameraCharacteristics.LENS_INFO_HYPERFOCAL_DISTANCE
CameraCharacteristics.SENSOR_BLACK_LEVEL_PATTERN
CameraCharacteristics.SENSOR_INFO_COLOR_FILTER_ARRANGEMENT
CameraCharacteristics.SENSOR_INFO_PHYSICAL_SIZE
CameraCharacteristics.SENSOR_INFO_WHITE_LEVEL
CameraCharacteristics.SENSOR_ORIENTATION
CaptureResult.SENSOR_ROLLING_SHUTTER_SKEW
CameraCharacteristics.INFO_SUPPORTED_HARDWARE_LEVEL
Constant Value: 4 (0x00000004)
public static final int INFO_SUPPORTED_HARDWARE_LEVEL_FULL
This camera device is capable of supporting advanced imaging applications.
The stream configurations listed in the FULL
, LEGACY
and LIMITED
tables in the
createCaptureSession
documentation are guaranteed to be supported.
A FULL
device will support below capabilities:
BURST_CAPTURE
capability (android.request.availableCapabilities
contains
BURST_CAPTURE
)android.sync.maxLatency
==
PER_FRAME_CONTROL)android.request.availableCapabilities
contains MANUAL_SENSOR
)android.request.availableCapabilities
contains
MANUAL_POST_PROCESSING
)android.sensor.info.exposureTimeRange
android.sensor.info.maxFrameDuration
Note:
Pre-API level 23, FULL devices also supported arbitrary cropping region
(android.scaler.croppingType
== FREEFORM
); this requirement was relaxed in API level
23, and FULL
devices may only support CENTERED
cropping.
See also:
Constant Value: 1 (0x00000001)
public static final int INFO_SUPPORTED_HARDWARE_LEVEL_LEGACY
This camera device is running in backward compatibility mode.
Only the stream configurations listed in the LEGACY
table in the createCaptureSession
documentation are supported.
A LEGACY
device does not support per-frame control, manual sensor control, manual
post-processing, arbitrary cropping regions, and has relaxed performance constraints.
No additional capabilities beyond BACKWARD_COMPATIBLE
will ever be listed by a
LEGACY
device in android.request.availableCapabilities
.
In addition, the android.control.aePrecaptureTrigger
is not functional on LEGACY
devices. Instead, every request that includes a JPEG-format output target is treated
as triggering a still capture, internally executing a precapture trigger. This may
fire the flash for flash power metering during precapture, and then fire the flash
for the final capture, if a flash is available on the device and the AE mode is set to
enable the flash.
Devices that initially shipped with Android version Q
or newer will not include any LEGACY-level devices.
See also:
Constant Value: 2 (0x00000002)
public static final int INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
This camera device does not have enough capabilities to qualify as a FULL
device or
better.
Only the stream configurations listed in the LEGACY
and LIMITED
tables in the
createCaptureSession
documentation are guaranteed to be supported.
All LIMITED
devices support the BACKWARDS_COMPATIBLE
capability, indicating basic
support for color image capture. The only exception is that the device may
alternatively support only the DEPTH_OUTPUT
capability, if it can only output depth
measurements and not color images.
LIMITED
devices and above require the use of android.control.aePrecaptureTrigger
to lock exposure metering (and calculate flash power, for cameras with flash) before
capturing a high-quality still image.
A LIMITED
device that only lists the BACKWARDS_COMPATIBLE
capability is only
required to support full-automatic operation and post-processing (OFF
is not
supported for android.control.aeMode
, android.control.afMode
, or
android.control.awbMode
)
Additional capabilities may optionally be supported by a LIMITED
-level device, and
can be checked for in android.request.availableCapabilities
.
See also:
Constant Value: 0 (0x00000000)
public static final int LENS_FACING_BACK
The camera device faces the opposite direction as the device's screen.
See also:
Constant Value: 1 (0x00000001)
public static final int LENS_FACING_EXTERNAL
The camera device is an external camera, and has no fixed facing relative to the device's screen.
See also:
Constant Value: 2 (0x00000002)
public static final int LENS_FACING_FRONT
The camera device faces the same direction as the device's screen.
See also:
Constant Value: 0 (0x00000000)
public static final int 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.
Constant Value: 1 (0x00000001)
public static final int 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.
Constant Value: 2 (0x00000002)
public static final int LENS_INFO_FOCUS_DISTANCE_CALIBRATION_UNCALIBRATED
The lens focus distance is not accurate, and the units used for
android.lens.focusDistance
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 [0,
, where 0
represents the farthest focus.android.lens.info.minimumFocusDistance
]
See also:
Constant Value: 0 (0x00000000)
public static final int LENS_OPTICAL_STABILIZATION_MODE_OFF
Optical stabilization is unavailable.
Constant Value: 0 (0x00000000)
public static final int LENS_OPTICAL_STABILIZATION_MODE_ON
Optical stabilization is enabled.
Constant Value: 1 (0x00000001)
public static final int LENS_POSE_REFERENCE_GYROSCOPE
The value of android.lens.poseTranslation
is relative to the position of the
primary gyroscope of this Android device.
Constant Value: 1 (0x00000001)
public static final int LENS_POSE_REFERENCE_PRIMARY_CAMERA
The value of android.lens.poseTranslation
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.
Constant Value: 0 (0x00000000)
public static final int LENS_POSE_REFERENCE_UNDEFINED
The camera device cannot represent the values of android.lens.poseTranslation
and android.lens.poseRotation
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 android.lens.poseTranslation
must be all zeros, and
android.lens.poseRotation
must be values matching its default facing.
See also:
Constant Value: 2 (0x00000002)
public static final int LENS_STATE_MOVING
One or several of the lens parameters
(android.lens.focalLength
, android.lens.focusDistance
,
android.lens.filterDensity
or android.lens.aperture
) is
currently changing.
See also:
Constant Value: 1 (0x00000001)
public static final int LENS_STATE_STATIONARY
The lens parameters (android.lens.focalLength
, android.lens.focusDistance
,
android.lens.filterDensity
and android.lens.aperture
) are not changing.
See also:
Constant Value: 0 (0x00000000)
public static final int LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_APPROXIMATE
A software mechanism is used to synchronize between the physical cameras. As a result, the timestamp of an image from a physical stream is only an approximation of the image sensor start-of-exposure time.
Constant Value: 0 (0x00000000)
public static final int LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE_CALIBRATED
The camera device supports frame timestamp synchronization at the hardware level, and the timestamp of a physical stream image accurately reflects its start-of-exposure time.
Constant Value: 1 (0x00000001)
public static final int 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.
See also:
Constant Value: 1 (0x00000001)
public static final int NOISE_REDUCTION_MODE_HIGH_QUALITY
High-quality noise reduction is applied, at the cost of possibly reduced frame rate relative to sensor output.
See also:
Constant Value: 2 (0x00000002)
public static final int NOISE_REDUCTION_MODE_MINIMAL
MINIMAL noise reduction is applied without reducing frame rate relative to sensor output.
See also:
Constant Value: 3 (0x00000003)
public static final int NOISE_REDUCTION_MODE_OFF
No noise reduction is applied.
See also:
Constant Value: 0 (0x00000000)
public static final int 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 CameraDevice.createCaptureSession(SessionConfiguration)
)
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
(android.request.availableCapabilities
lists either of those capabilities) and it will
be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template.
Constant Value: 4 (0x00000004)
public static final int REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE
The minimal set of capabilities that every camera
device (regardless of android.info.supportedHardwareLevel
)
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:
Constant Value: 0 (0x00000000)
public static final int 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 a size matching the camera device's active array
size is listed as a supported size for the ImageFormat.YUV_420_888
format in either StreamConfigurationMap.getOutputSizes(int)
or StreamConfigurationMap.getHighResolutionOutputSizes(int)
,
with a minimum frame duration for that format and size of either <= 1/20 s, or
<= 1/10 s if the image size is less than 24 megapixels, respectively; and
the android.control.aeAvailableTargetFpsRanges
entry lists at least one FPS range
where the minimum FPS is >= 1 / minimumFrameDuration for the maximum-size
YUV_420_888 format. If that maximum size is listed in StreamConfigurationMap.getHighResolutionOutputSizes(int)
,
then the list of resolutions for YUV_420_888 from StreamConfigurationMap.getOutputSizes(int)
contains at
least one resolution >= 8 megapixels, with a minimum frame duration of <= 1/20
s.
If the device supports the ImageFormat.RAW10
, ImageFormat.RAW12
, ImageFormat.Y8
, then those can also be
captured at the same rate as the maximum-size YUV_420_888 resolution is.
If the device supports the PRIVATE_REPROCESSING capability, then the same guarantees
as for the YUV_420_888 format also apply to the ImageFormat.PRIVATE
format.
In addition, the android.sync.maxLatency
field is guaranted to have a value between 0
and 4, inclusive. android.control.aeLockAvailable
and android.control.awbLockAvailable
are also guaranteed to be true
so burst capture with these two locks ON yields
consistent image output.
See also:
Constant Value: 6 (0x00000006)
public static final int REQUEST_AVAILABLE_CAPABILITIES_CONSTRAINED_HIGH_SPEED_VIDEO
The device supports constrained high speed video recording (frame rate >=120fps) use
case. The camera device will support high speed capture session created by CameraDevice.createConstrainedHighSpeedCaptureSession(List
, which
only accepts high speed request lists created by CameraConstrainedHighSpeedCaptureSession.createHighSpeedRequestList(CaptureRequest)
.
A camera device can still support high speed video streaming by advertising the high
speed FPS ranges in android.control.aeAvailableTargetFpsRanges
. For this case, all
normal capture request per frame control and synchronization requirements will apply
to the high speed fps ranges, the same as all other fps ranges. This capability
describes the capability of a specialized operating mode with many limitations (see
below), which is only targeted at high speed video recording.
The supported high speed video sizes and fps ranges are specified in StreamConfigurationMap.getHighSpeedVideoFpsRanges()
.
To get desired output frame rates, the application is only allowed to select video
size and FPS range combinations provided by StreamConfigurationMap.getHighSpeedVideoSizes()
. The
fps range can be controlled via android.control.aeTargetFpsRange
.
In this capability, the camera device will override aeMode, awbMode, and afMode to
ON, AUTO, and CONTINUOUS_VIDEO, respectively. All post-processing block mode
controls will be overridden to be FAST. Therefore, no manual control of capture
and post-processing parameters is possible. All other controls operate the
same as when android.control.mode
== AUTO. This means that all other
android.control.* fields continue to work, such as
android.control.aeTargetFpsRange
android.control.aeExposureCompensation
android.control.aeLock
android.control.awbLock
android.control.effectMode
android.control.aeRegions
android.control.afRegions
android.control.awbRegions
android.control.afTrigger
android.control.aePrecaptureTrigger
android.control.zoomRatio
Outside of android.control.*, the following controls will work:
android.flash.mode
(TORCH mode only, automatic flash for still capture will not
work since aeMode is ON)android.lens.opticalStabilizationMode
(if it is supported)android.scaler.cropRegion
android.statistics.faceDetectMode
(if it is supported)For high speed recording use case, the actual maximum supported frame rate may be lower than what camera can output, depending on the destination Surfaces for the image data. For example, if the destination surface is from video encoder, the application need check if the video encoder is capable of supporting the high frame rate for a given video size, or it will end up with lower recording frame rate. If the destination surface is from preview window, the actual preview frame rate will be bounded by the screen refresh rate.
The camera device will only support up to 2 high speed simultaneous output surfaces (preview and recording surfaces) in this mode. Above controls will be effective only if all of below conditions are true:
CameraDevice.createConstrainedHighSpeedCaptureSession(List, CameraCaptureSession.StateCallback, Handler)
. The
targeted surfaces must be preview surface (either from SurfaceView
or SurfaceTexture
) or recording
surface(either from MediaRecorder.getSurface()
or MediaCodec.createInputSurface()
).StreamConfigurationMap.getHighSpeedVideoSizes()
.StreamConfigurationMap.getHighSpeedVideoFpsRanges()
.When above conditions are NOT satistied,
CameraDevice.createConstrainedHighSpeedCaptureSession(List
will fail.
Switching to a FPS range that has different maximum FPS may trigger some camera device reconfigurations, which may introduce extra latency. It is recommended that the application avoids unnecessary maximum target FPS changes as much as possible during high speed streaming.
See also:
CameraCharacteristics.CONTROL_AE_AVAILABLE_TARGET_FPS_RANGES
CaptureRequest.CONTROL_AE_EXPOSURE_COMPENSATION
CaptureRequest.CONTROL_AE_LOCK
CaptureRequest.CONTROL_AE_PRECAPTURE_TRIGGER
CaptureRequest.CONTROL_AE_REGIONS
CaptureRequest.CONTROL_AE_TARGET_FPS_RANGE
CaptureRequest.CONTROL_AF_REGIONS
CaptureRequest.CONTROL_AF_TRIGGER
CaptureRequest.CONTROL_AWB_LOCK
CaptureRequest.CONTROL_AWB_REGIONS
CaptureRequest.CONTROL_EFFECT_MODE
CaptureRequest.CONTROL_MODE
CaptureRequest.CONTROL_ZOOM_RATIO
CaptureRequest.FLASH_MODE
CaptureRequest.LENS_OPTICAL_STABILIZATION_MODE
CaptureRequest.SCALER_CROP_REGION
CaptureRequest.STATISTICS_FACE_DETECT_MODE
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 9 (0x00000009)
public static final int 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:
ImageFormat.DEPTH16
is supported as
an output format.ImageFormat.DEPTH_POINT_CLOUD
is
optionally supported as an output format.android.lens.facing
, will
list the following calibration metadata entries in both CameraCharacteristics
and CaptureResult
:
android.depth.depthIsExclusive
entry is listed by this device.android.lens.poseReference
entry is listed by this device.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 StreamConfigurationMap.getOutputStallDuration(int, Size)
).
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:
CameraCharacteristics.DEPTH_DEPTH_IS_EXCLUSIVE
CameraCharacteristics.LENS_DISTORTION
CameraCharacteristics.LENS_FACING
CameraCharacteristics.LENS_INTRINSIC_CALIBRATION
CameraCharacteristics.LENS_POSE_REFERENCE
CameraCharacteristics.LENS_POSE_ROTATION
CameraCharacteristics.LENS_POSE_TRANSLATION
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 8 (0x00000008)
public static final int 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:
CameraManager.getCameraIdList()
. But the
application can still query the physical cameras' characteristics by calling
CameraManager.getCameraCharacteristics(String)
.CameraManager.AvailabilityCallback#onPhysicalCameraUnavailable
callback.Combinations of logical and physical streams, or physical streams from different
physical cameras are not guaranteed. However, if the camera device supports
CameraDevice#isSessionConfigurationSupported
,
application must be able to query whether a stream combination involving physical
streams is supported by calling
CameraDevice#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:
CameraCharacteristics.getPhysicalCameraIds()
.android.logicalMultiCamera.sensorSyncType
in
CameraCharacteristics
.A logical camera device's dynamic metadata may contain
android.logicalMultiCamera.activePhysicalId
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.
android.sensor.info.sensitivityRange
android.sensor.info.colorFilterArrangement
android.sensor.info.exposureTimeRange
android.sensor.info.maxFrameDuration
android.sensor.info.physicalSize
android.sensor.info.whiteLevel
android.sensor.info.lensShadingApplied
android.sensor.referenceIlluminant1
android.sensor.referenceIlluminant2
android.sensor.calibrationTransform1
android.sensor.calibrationTransform2
android.sensor.colorTransform1
android.sensor.colorTransform2
android.sensor.forwardMatrix1
android.sensor.forwardMatrix2
android.sensor.blackLevelPattern
android.sensor.maxAnalogSensitivity
android.sensor.opticalBlackRegions
android.sensor.availableTestPatternModes
android.lens.info.hyperfocalDistance
android.lens.info.minimumFocusDistance
android.lens.info.focusDistanceCalibration
android.lens.poseRotation
android.lens.poseTranslation
android.lens.intrinsicCalibration
android.lens.poseReference
android.lens.distortion
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:
fov = 2 * atan2(cropW * sensorW / (2 * zoomRatio * activeArrayW), focalLength)
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 outputing 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.
There are two ways for the application to capture RAW images from a logical camera with RAW capability:
MultiResolutionImageReader
to capture RAW images from the currently active physical camera. Because different
physical camera may have different RAW characteristics, the application needs to use
the characteristics and result metadata of the active physical camera for the
relevant RAW metadata.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:
CameraCharacteristics.LENS_DISTORTION
CameraCharacteristics.LENS_INFO_FOCUS_DISTANCE_CALIBRATION
CameraCharacteristics.LENS_INFO_HYPERFOCAL_DISTANCE
CameraCharacteristics.LENS_INFO_MINIMUM_FOCUS_DISTANCE
CameraCharacteristics.LENS_INTRINSIC_CALIBRATION
CameraCharacteristics.LENS_POSE_REFERENCE
CameraCharacteristics.LENS_POSE_ROTATION
CameraCharacteristics.LENS_POSE_TRANSLATION
CaptureResult.LOGICAL_MULTI_CAMERA_ACTIVE_PHYSICAL_ID
CameraCharacteristics.LOGICAL_MULTI_CAMERA_SENSOR_SYNC_TYPE
CameraCharacteristics.SENSOR_AVAILABLE_TEST_PATTERN_MODES
CameraCharacteristics.SENSOR_BLACK_LEVEL_PATTERN
CameraCharacteristics.SENSOR_CALIBRATION_TRANSFORM1
CameraCharacteristics.SENSOR_CALIBRATION_TRANSFORM2
CameraCharacteristics.SENSOR_COLOR_TRANSFORM1
CameraCharacteristics.SENSOR_COLOR_TRANSFORM2
CameraCharacteristics.SENSOR_FORWARD_MATRIX1
CameraCharacteristics.SENSOR_FORWARD_MATRIX2
CameraCharacteristics.SENSOR_INFO_COLOR_FILTER_ARRANGEMENT
CameraCharacteristics.SENSOR_INFO_EXPOSURE_TIME_RANGE
CameraCharacteristics.SENSOR_INFO_LENS_SHADING_APPLIED
CameraCharacteristics.SENSOR_INFO_MAX_FRAME_DURATION
CameraCharacteristics.SENSOR_INFO_PHYSICAL_SIZE
CameraCharacteristics.SENSOR_INFO_SENSITIVITY_RANGE
CameraCharacteristics.SENSOR_INFO_WHITE_LEVEL
CameraCharacteristics.SENSOR_MAX_ANALOG_SENSITIVITY
CameraCharacteristics.SENSOR_OPTICAL_BLACK_REGIONS
CameraCharacteristics.SENSOR_REFERENCE_ILLUMINANT1
CameraCharacteristics.SENSOR_REFERENCE_ILLUMINANT2
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 11 (0x0000000b)
public static final int 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:
Manual tonemap control
Manual white balance control
android.shading.mode
android.statistics.lensShadingMapMode
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:
CaptureRequest.COLOR_CORRECTION_ABERRATION_MODE
CameraCharacteristics.COLOR_CORRECTION_AVAILABLE_ABERRATION_MODES
CaptureRequest.COLOR_CORRECTION_GAINS
CaptureRequest.COLOR_CORRECTION_TRANSFORM
CaptureRequest.CONTROL_AWB_LOCK
CaptureRequest.SHADING_MODE
CaptureRequest.STATISTICS_LENS_SHADING_MAP_MODE
CaptureRequest.TONEMAP_CURVE
CaptureRequest.TONEMAP_GAMMA
CameraCharacteristics.TONEMAP_MAX_CURVE_POINTS
CaptureRequest.TONEMAP_MODE
CaptureRequest.TONEMAP_PRESET_CURVE
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 2 (0x00000002)
public static final int 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:
CaptureRequest.BLACK_LEVEL_LOCK
CaptureRequest.CONTROL_AE_LOCK
CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP
CaptureRequest.SENSOR_EXPOSURE_TIME
CaptureRequest.SENSOR_FRAME_DURATION
CameraCharacteristics.SENSOR_INFO_EXPOSURE_TIME_RANGE
CameraCharacteristics.SENSOR_INFO_MAX_FRAME_DURATION
CameraCharacteristics.SENSOR_INFO_SENSITIVITY_RANGE
CaptureRequest.SENSOR_SENSITIVITY
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 1 (0x00000001)
public static final int 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.
Constant Value: 12 (0x0000000c)
public static final int REQUEST_AVAILABLE_CAPABILITIES_MOTION_TRACKING
The camera device supports the MOTION_TRACKING value for
android.control.captureIntent
, 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.
Constant Value: 10 (0x0000000a)
public static final int REQUEST_AVAILABLE_CAPABILITIES_OFFLINE_PROCESSING
The camera device supports the OFFLINE_PROCESSING use case.
With OFFLINE_PROCESSING capability, the application can switch an ongoing capture session to offline mode by calling the CameraCaptureSession#switchToOffline method and specify streams to be kept in offline mode. The camera will then stop currently active repeating requests, prepare for some requests to go into offline mode, and return an offline session object. After the switchToOffline call returns, the original capture session is in closed state as if the CameraCaptureSession#close method has been called. In the offline mode, all inflight requests will continue to be processed in the background, and the application can immediately close the camera or create a new capture session without losing those requests' output images and capture results.
While the camera device is processing offline requests, it might not be able to support all stream configurations it can support without offline requests. When that happens, the createCaptureSession method call will fail. The following stream configurations are guaranteed to work without hitting the resource busy exception:
Camera
with the following parameter settings:Constant Value: 15 (0x0000000f)
public static final int REQUEST_AVAILABLE_CAPABILITIES_PRIVATE_REPROCESSING
The camera device supports the Zero Shutter Lag reprocessing use case.
android.request.maxNumInputStreams
== 1
.ImageFormat.PRIVATE
is supported as an output/input format,
that is, ImageFormat.PRIVATE
is included in the lists of
formats returned by StreamConfigurationMap.getInputFormats()
and StreamConfigurationMap.getOutputFormats()
.StreamConfigurationMap.getValidOutputFormatsForInput(int)
returns non-empty int[] for each supported input format returned by StreamConfigurationMap.getInputFormats()
.getInputSizes(ImageFormat.PRIVATE)
is also included in getOutputSizes(ImageFormat.PRIVATE)
ImageFormat.PRIVATE
does not cause a frame rate drop
relative to the sensor's maximum capture rate (at that resolution).ImageFormat.PRIVATE
will be reprocessable into both
ImageFormat.YUV_420_888
and
ImageFormat.JPEG
formats.ImageFormat.PRIVATE
will be reprocessable into
ImageFormat.Y8
.android.reprocess.maxCaptureStall
.android.noiseReduction.mode
android.edge.mode
android.noiseReduction.availableNoiseReductionModes
and
android.edge.availableEdgeModes
will both list ZERO_SHUTTER_LAG as a supported mode.See also:
CameraCharacteristics.EDGE_AVAILABLE_EDGE_MODES
CaptureRequest.EDGE_MODE
CameraCharacteristics.NOISE_REDUCTION_AVAILABLE_NOISE_REDUCTION_MODES
CaptureRequest.NOISE_REDUCTION_MODE
CameraCharacteristics.REPROCESS_MAX_CAPTURE_STALL
CameraCharacteristics.REQUEST_MAX_NUM_INPUT_STREAMS
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 4 (0x00000004)
public static final int 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.
android.sensor.info.pixelArraySize
or
android.sensor.info.preCorrectionActiveArraySize
.See also:
Constant Value: 3 (0x00000003)
public static final int 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:
Constant Value: 5 (0x00000005)
public static final int REQUEST_AVAILABLE_CAPABILITIES_REMOSAIC_REPROCESSING
The device supports reprocessing from the RAW_SENSOR
format with a bayer pattern
given by android.sensor.info.binningFactor
(m x n group of pixels with the same
color filter) to a remosaiced regular bayer pattern.
This capability will only be present for devices with
REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR
capability. When
REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR
devices do not advertise this capability,
ImageFormat.RAW_SENSOR
images will already have a
regular bayer pattern.
If a RAW_SENSOR
stream is requested along with another non-RAW stream in a
CaptureRequest
(if multiple streams are supported
when android.sensor.pixelMode
is set to
SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION
),
the RAW_SENSOR
stream will have a regular bayer pattern.
This capability requires the camera device to support the following :
* The StreamConfigurationMap
mentioned below
refers to the one, described by
.
* One input stream is supported, that is, android.scaler.streamConfigurationMapMaximumResolution
.
* android.request.maxNumInputStreams
== 1ImageFormat.RAW_SENSOR
is supported as an output/input
format, that is, ImageFormat.RAW_SENSOR
is included in the
lists of formats returned by StreamConfigurationMap.getInputFormats()
and StreamConfigurationMap.getOutputFormats()
.
* StreamConfigurationMap.getValidOutputFormatsForInput(int)
returns non-empty int[] for each supported input format returned by StreamConfigurationMap.getInputFormats()
.
* Each size returned by getInputSizes(ImageFormat.RAW_SENSOR)
is also included in getOutputSizes(ImageFormat.RAW_SENSOR)
* Using ImageFormat.RAW_SENSOR
does not cause a frame rate
drop relative to the sensor's maximum capture rate (at that resolution).
* No CaptureRequest controls will be applicable when a request has an input target
with ImageFormat.RAW_SENSOR
format.
See also:
Constant Value: 17 (0x00000011)
public static final int 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).
Constant Value: 13 (0x0000000d)
public static final int 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.
Constant Value: 14 (0x0000000e)
public static final int 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.
describes the streams supported in 'default'
mode.
The stream configurations supported in 'max resolution' mode are described by
android.scaler.streamConfigurationMap
.
The maximum resolution mode pixel array size of a camera device
(android.scaler.streamConfigurationMapMaximumResolution
) with this capability,
will be at least 24 megapixels.android.sensor.info.pixelArraySize
See also:
Constant Value: 16 (0x00000010)
public static final int REQUEST_AVAILABLE_CAPABILITIES_YUV_REPROCESSING
The camera device supports the YUV_420_888 reprocessing use case, similar as PRIVATE_REPROCESSING, This capability requires the camera device to support the following:
android.request.maxNumInputStreams
== 1
.ImageFormat.YUV_420_888
is supported as an output/input
format, that is, YUV_420_888 is included in the lists of formats returned by StreamConfigurationMap.getInputFormats()
and StreamConfigurationMap.getOutputFormats()
.StreamConfigurationMap.getValidOutputFormatsForInput(int)
returns non-empty int[] for each supported input format returned by StreamConfigurationMap.getInputFormats()
.getInputSizes(YUV_420_888)
is also included in getOutputSizes(YUV_420_888)
ImageFormat.YUV_420_888
does not cause a frame rate
drop relative to the sensor's maximum capture rate (at that resolution).ImageFormat.YUV_420_888
will be reprocessable into both
ImageFormat.YUV_420_888
and ImageFormat.JPEG
formats.ImageFormat.YUV_420_888
streams (both input/output) will match the
maximum available resolution of ImageFormat.JPEG
streams.android.reprocess.maxCaptureStall
.ImageFormat.YUV_420_888
output buffers. All other controls in the
reprocess requests will be ignored by the camera device.
android.noiseReduction.availableNoiseReductionModes
and
android.edge.availableEdgeModes
will both list ZERO_SHUTTER_LAG as a supported mode.See also:
CameraCharacteristics.EDGE_AVAILABLE_EDGE_MODES
CaptureRequest.EDGE_MODE
CameraCharacteristics.NOISE_REDUCTION_AVAILABLE_NOISE_REDUCTION_MODES
CaptureRequest.NOISE_REDUCTION_MODE
CaptureRequest.REPROCESS_EFFECTIVE_EXPOSURE_FACTOR
CameraCharacteristics.REPROCESS_MAX_CAPTURE_STALL
CameraCharacteristics.REQUEST_MAX_NUM_INPUT_STREAMS
CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITIES
Constant Value: 7 (0x00000007)
public static final int SCALER_CROPPING_TYPE_CENTER_ONLY
The camera device only supports centered crop regions.
Constant Value: 0 (0x00000000)
public static final int SCALER_CROPPING_TYPE_FREEFORM
The camera device supports arbitrarily chosen crop regions.
Constant Value: 1 (0x00000001)
public static final int SCALER_ROTATE_AND_CROP_180
Processed images are rotated by 180 degrees. Since the aspect ratio does not change, no cropping is performed.
See also:
Constant Value: 2 (0x00000002)
public static final int SCALER_ROTATE_AND_CROP_270
Processed images are rotated by 270 degrees clockwise, and then cropped to the original aspect ratio.
See also:
Constant Value: 3 (0x00000003)
public static final int SCALER_ROTATE_AND_CROP_90
Processed images are rotated by 90 degrees clockwise, and then cropped to the original aspect ratio.
See also:
Constant Value: 1 (0x00000001)
public static final int SCALER_ROTATE_AND_CROP_AUTO
The camera API automatically selects the best concrete value for rotate-and-crop based on the application's support for resizability and the current multi-window mode.
If the application does not support resizing but the display mode for its main
Activity is not in a typical orientation, the camera API will set ROTATE_AND_CROP_90
or some other supported rotation value, depending on device configuration,
to ensure preview and captured images are correctly shown to the user. Otherwise,
ROTATE_AND_CROP_NONE
will be selected.
When a value other than NONE is selected, several metadata fields will also be parsed differently to ensure that coordinates are correctly handled for features like drawing face detection boxes or passing in tap-to-focus coordinates. The camera API will convert positions in the active array coordinate system to/from the cropped-and-rotated coordinate system to make the operation transparent for applications.
No coordinate mapping will be done when the application selects a non-AUTO mode.
See also:
Constant Value: 4 (0x00000004)
public static final int SCALER_ROTATE_AND_CROP_NONE
No rotate and crop is applied. Processed outputs are in the sensor orientation.
See also:
Constant Value: 0 (0x00000000)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_BGGR
Constant Value: 3 (0x00000003)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_GBRG
Constant Value: 2 (0x00000002)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_GRBG
Constant Value: 1 (0x00000001)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_MONO
Sensor doesn't have any Bayer color filter. Such sensor captures visible light in monochrome. The exact weighting and wavelengths captured is not specified, but generally only includes the visible frequencies. This value implies a MONOCHROME camera.
Constant Value: 5 (0x00000005)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_NIR
Sensor has a near infrared filter capturing light with wavelength between roughly 750nm and 1400nm, and the same filter covers the whole sensor array. This value implies a MONOCHROME camera.
Constant Value: 6 (0x00000006)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_RGB
Sensor is not Bayer; output has 3 16-bit values for each pixel, instead of just 1 16-bit value per pixel.
Constant Value: 4 (0x00000004)
public static final int SENSOR_INFO_COLOR_FILTER_ARRANGEMENT_RGGB
Constant Value: 0 (0x00000000)
public static final int SENSOR_INFO_TIMESTAMP_SOURCE_REALTIME
Timestamps from android.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.
Constant Value: 1 (0x00000001)
public static final int SENSOR_INFO_TIMESTAMP_SOURCE_UNKNOWN
Timestamps from android.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.
Constant Value: 0 (0x00000000)
public static final int SENSOR_PIXEL_MODE_DEFAULT
This is the default sensor pixel mode. This is the only sensor pixel mode
supported unless a camera device advertises
REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR
.
See also:
Constant Value: 0 (0x00000000)
public static final int SENSOR_PIXEL_MODE_MAXIMUM_RESOLUTION
This sensor pixel mode is offered by devices with capability
REQUEST_AVAILABLE_CAPABILITIES_ULTRA_HIGH_RESOLUTION_SENSOR
.
In this mode, sensors typically do not bin pixels, as a result can offer larger
image sizes.
See also:
Constant Value: 1 (0x00000001)
public static final int SENSOR_REFERENCE_ILLUMINANT1_CLOUDY_WEATHER
Constant Value: 10 (0x0000000a)
public static final int SENSOR_REFERENCE_ILLUMINANT1_COOL_WHITE_FLUORESCENT
W 3900 - 4500K
Constant Value: 14 (0x0000000e)
public static final int SENSOR_REFERENCE_ILLUMINANT1_D50
Constant Value: 23 (0x00000017)
public static final int SENSOR_REFERENCE_ILLUMINANT1_D55
Constant Value: 20 (0x00000014)
public static final int SENSOR_REFERENCE_ILLUMINANT1_D65
Constant Value: 21 (0x00000015)
public static final int SENSOR_REFERENCE_ILLUMINANT1_D75
Constant Value: 22 (0x00000016)
public static final int SENSOR_REFERENCE_ILLUMINANT1_DAYLIGHT
Constant Value: 1 (0x00000001)
public static final int SENSOR_REFERENCE_ILLUMINANT1_DAYLIGHT_FLUORESCENT
D 5700 - 7100K
Constant Value: 12 (0x0000000c)
public static final int SENSOR_REFERENCE_ILLUMINANT1_DAY_WHITE_FLUORESCENT
N 4600 - 5400K
Constant Value: 13 (0x0000000d)
public static final int SENSOR_REFERENCE_ILLUMINANT1_FINE_WEATHER
Constant Value: 9 (0x00000009)
public static final int SENSOR_REFERENCE_ILLUMINANT1_FLASH
Constant Value: 4 (0x00000004)
public static final int SENSOR_REFERENCE_ILLUMINANT1_FLUORESCENT
Constant Value: 2 (0x00000002)
public static final int SENSOR_REFERENCE_ILLUMINANT1_ISO_STUDIO_TUNGSTEN
Constant Value: 24 (0x00000018)
public static final int SENSOR_REFERENCE_ILLUMINANT1_SHADE
Constant Value: 11 (0x0000000b)
public static final int SENSOR_REFERENCE_ILLUMINANT1_STANDARD_A
Constant Value: 17 (0x00000011)
public static final int SENSOR_REFERENCE_ILLUMINANT1_STANDARD_B
Constant Value: 18 (0x00000012)
public static final int SENSOR_REFERENCE_ILLUMINANT1_STANDARD_C
Constant Value: 19 (0x00000013)
public static final int SENSOR_REFERENCE_ILLUMINANT1_TUNGSTEN
Incandescent light
Constant Value: 3 (0x00000003)
public static final int SENSOR_REFERENCE_ILLUMINANT1_WHITE_FLUORESCENT
WW 3200 - 3700K
Constant Value: 15 (0x0000000f)
public static final int 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:
W Y C G M R B K
W Y C G M R B K
W Y C G M R B K
W Y C G M R B K
W Y C G M R B K
. . . . . . . .
. . . . . . . .
. . . . . . . .
(B = Blue, K = Black)
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.
See also:
Constant Value: 2 (0x00000002)
public static final int 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.
See also:
Constant Value: 3 (0x00000003)
public static final int 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).
See also:
Constant Value: 256 (0x00000100)
public static final int 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.
See also:
Constant Value: 0 (0x00000000)
public static final int 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.
See also:
Constant Value: 4 (0x00000004)
public static final int SENSOR_TEST_PATTERN_MODE_SOLID_COLOR
Each pixel in [R, G_even, G_odd, B]
is replaced by its
respective color channel provided in
android.sensor.testPatternData
.
For example:
android.sensor.testPatternData
= [0, 0xFFFFFFFF, 0xFFFFFFFF, 0]
All green pixels are 100% green. All red/blue pixels are black.
android.sensor.testPatternData
= [0xFFFFFFFF, 0, 0xFFFFFFFF, 0]
All red pixels are 100% red. Only the odd green pixels are 100% green. All blue pixels are 100% black.
Constant Value: 1 (0x00000001)
public static final int SHADING_MODE_FAST
Apply lens shading corrections, without slowing frame rate relative to sensor raw output
See also:
Constant Value: 1 (0x00000001)
public static final int SHADING_MODE_HIGH_QUALITY
Apply high-quality lens shading correction, at the cost of possibly reduced frame rate.
See also:
Constant Value: 2 (0x00000002)
public static final int SHADING_MODE_OFF
No lens shading correction is applied.
See also:
Constant Value: 0 (0x00000000)
public static final int STATISTICS_FACE_DETECT_MODE_FULL
Return all face metadata.
In this mode, face rectangles, scores, landmarks, and face IDs are all valid.
Constant Value: 2 (0x00000002)
public static final int STATISTICS_FACE_DETECT_MODE_OFF
Do not include face detection statistics in capture results.
Constant Value: 0 (0x00000000)
public static final int STATISTICS_FACE_DETECT_MODE_SIMPLE
Return face rectangle and confidence values only.
Constant Value: 1 (0x00000001)
public static final int STATISTICS_LENS_SHADING_MAP_MODE_OFF
Do not include a lens shading map in the capture result.
Constant Value: 0 (0x00000000)
public static final int STATISTICS_LENS_SHADING_MAP_MODE_ON
Include a lens shading map in the capture result.
Constant Value: 1 (0x00000001)
public static final int STATISTICS_OIS_DATA_MODE_OFF
Do not include OIS data in the capture result.
See also:
Constant Value: 0 (0x00000000)
public static final int STATISTICS_OIS_DATA_MODE_ON
Include OIS data in the capture result.
android.statistics.oisSamples
provides OIS sample data in the
output result metadata.
Constant Value: 1 (0x00000001)
public static final int STATISTICS_SCENE_FLICKER_50HZ
The camera device detects illumination flickering at 50Hz in the current scene.
See also:
Constant Value: 1 (0x00000001)
public static final int STATISTICS_SCENE_FLICKER_60HZ
The camera device detects illumination flickering at 60Hz in the current scene.
See also:
Constant Value: 2 (0x00000002)
public static final int STATISTICS_SCENE_FLICKER_NONE
The camera device does not detect any flickering illumination in the current scene.
See also:
Constant Value: 0 (0x00000000)
public static final int SYNC_MAX_LATENCY_PER_FRAME_CONTROL
Every frame has the requests immediately applied.
Changing controls over multiple requests one after another will produce results that have those controls applied atomically each frame.
All FULL capability devices will have this as their maxLatency.
See also:
Constant Value: 0 (0x00000000)
public static final int SYNC_MAX_LATENCY_UNKNOWN
Each new frame has some subset (potentially the entire set) of the past requests applied to the camera settings.
By submitting a series of identical requests, the camera device will eventually have the camera settings applied, but it is unknown when that exact point will be.
All LEGACY capability devices will have this as their maxLatency.
See also:
Constant Value: -1 (0xffffffff)
public static final int TONEMAP_MODE_CONTRAST_CURVE
Use the tone mapping curve specified in
the android.tonemap.curve
* 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.
Constant Value: 0 (0x00000000)
public static final int TONEMAP_MODE_FAST
Advanced gamma mapping and color enhancement may be applied, without reducing frame rate compared to raw sensor output.
See also:
Constant Value: 1 (0x00000001)
public static final int TONEMAP_MODE_GAMMA_VALUE
Use the gamma value specified in android.tonemap.gamma
to peform
tonemapping.
All color enhancement and tonemapping must be disabled, except
for applying the tonemapping curve specified by android.tonemap.gamma
.
Must not slow down frame rate relative to raw sensor output.
Constant Value: 3 (0x00000003)
public static final int 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.
See also:
Constant Value: 2 (0x00000002)
public static final int TONEMAP_MODE_PRESET_CURVE
Use the preset tonemapping curve specified in
android.tonemap.presetCurve
to peform tonemapping.
All color enhancement and tonemapping must be disabled, except
for applying the tonemapping curve specified by
android.tonemap.presetCurve
.
Must not slow down frame rate relative to raw sensor output.
Constant Value: 4 (0x00000004)
public static final int TONEMAP_PRESET_CURVE_REC709
Tonemapping curve is defined by ITU-R BT.709
See also:
Constant Value: 1 (0x00000001)
public static final int TONEMAP_PRESET_CURVE_SRGB
Tonemapping curve is defined by sRGB
See also:
Constant Value: 0 (0x00000000)
public List<TKey> getKeys ()
Returns a list of the keys contained in this map.
The list returned is not modifiable, so any attempts to modify it will throw
a UnsupportedOperationException
.
All values retrieved by a key from this list with #get
are guaranteed to be
non-null
. Each key is only listed once in the list. The order of the keys
is undefined.
Returns | |
---|---|
List<TKey> |
List of the keys contained in this map. |