1 <?xml version="1.0" encoding="utf-8"?>
2 <!-- Copyright (C) 2012 The Android Open Source Project
4 Licensed under the Apache License, Version 2.0 (the "License");
5 you may not use this file except in compliance with the License.
6 You may obtain a copy of the License at
8 http://www.apache.org/licenses/LICENSE-2.0
10 Unless required by applicable law or agreed to in writing, software
11 distributed under the License is distributed on an "AS IS" BASIS,
12 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 See the License for the specific language governing permissions and
14 limitations under the License.
16 <metadata xmlns="http://schemas.android.com/service/camera/metadata/"
17 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
18 xsi:schemaLocation="http://schemas.android.com/service/camera/metadata/ metadata_properties.xsd">
22 Needed for backwards compatibility with old Java API
25 New features for first camera 2 release (API1)
28 Needed for useful RAW image processing and DNG file support
31 Entry is only used by camera device legacy HAL 2.x
34 Entry is required for full hardware level devices, and optional for other hardware levels
37 Entry is required for the depth capability.
40 Entry is required for the YUV or PRIVATE reprocessing capability.
42 <tag id="LOGICALCAMERA">
43 Entry is required for logical multi-camera capability.
46 Entry is under-specified and is not required for now. This is for book-keeping purpose,
47 do not implement or use it, it may be revised for future.
52 <typedef name="pairFloatFloat">
53 <language name="java">android.util.Pair<Float,Float></language>
55 <typedef name="pairDoubleDouble">
56 <language name="java">android.util.Pair<Double,Double></language>
58 <typedef name="rectangle">
59 <language name="java">android.graphics.Rect</language>
62 <language name="java">android.util.Size</language>
64 <typedef name="string">
65 <language name="java">String</language>
67 <typedef name="boolean">
68 <language name="java">boolean</language>
70 <typedef name="imageFormat">
71 <language name="java">int</language>
73 <typedef name="streamConfigurationMap">
74 <language name="java">android.hardware.camera2.params.StreamConfigurationMap</language>
76 <typedef name="streamConfiguration">
77 <language name="java">android.hardware.camera2.params.StreamConfiguration</language>
79 <typedef name="streamConfigurationDuration">
80 <language name="java">android.hardware.camera2.params.StreamConfigurationDuration</language>
83 <language name="java">android.hardware.camera2.params.Face</language>
85 <typedef name="meteringRectangle">
86 <language name="java">android.hardware.camera2.params.MeteringRectangle</language>
88 <typedef name="rangeFloat">
89 <language name="java">android.util.Range<Float></language>
91 <typedef name="rangeInt">
92 <language name="java">android.util.Range<Integer></language>
94 <typedef name="rangeLong">
95 <language name="java">android.util.Range<Long></language>
97 <typedef name="colorSpaceTransform">
98 <language name="java">android.hardware.camera2.params.ColorSpaceTransform</language>
100 <typedef name="rggbChannelVector">
101 <language name="java">android.hardware.camera2.params.RggbChannelVector</language>
103 <typedef name="blackLevelPattern">
104 <language name="java">android.hardware.camera2.params.BlackLevelPattern</language>
106 <typedef name="enumList">
107 <language name="java">int</language>
109 <typedef name="sizeF">
110 <language name="java">android.util.SizeF</language>
112 <typedef name="point">
113 <language name="java">android.graphics.Point</language>
115 <typedef name="tonemapCurve">
116 <language name="java">android.hardware.camera2.params.TonemapCurve</language>
118 <typedef name="lensShadingMap">
119 <language name="java">android.hardware.camera2.params.LensShadingMap</language>
121 <typedef name="location">
122 <language name="java">android.location.Location</language>
124 <typedef name="highSpeedVideoConfiguration">
125 <language name="java">android.hardware.camera2.params.HighSpeedVideoConfiguration</language>
127 <typedef name="reprocessFormatsMap">
128 <language name="java">android.hardware.camera2.params.ReprocessFormatsMap</language>
130 <typedef name="oisSample">
131 <language name="java">android.hardware.camera2.params.OisSample</language>
135 <namespace name="android">
136 <section name="colorCorrection">
138 <entry name="mode" type="byte" visibility="public" enum="true" hwlevel="full">
140 <value>TRANSFORM_MATRIX
141 <notes>Use the android.colorCorrection.transform matrix
142 and android.colorCorrection.gains to do color conversion.
144 All advanced white balance adjustments (not specified
145 by our white balance pipeline) must be disabled.
147 If AWB is enabled with `android.control.awbMode != OFF`, then
148 TRANSFORM_MATRIX is ignored. The camera device will override
149 this value to either FAST or HIGH_QUALITY.
153 <notes>Color correction processing must not slow down
154 capture rate relative to sensor raw output.
156 Advanced white balance adjustments above and beyond
157 the specified white balance pipeline may be applied.
159 If AWB is enabled with `android.control.awbMode != OFF`, then
160 the camera device uses the last frame's AWB values
161 (or defaults if AWB has never been run).
165 <notes>Color correction processing operates at improved
166 quality but the capture rate might be reduced (relative to sensor
169 Advanced white balance adjustments above and beyond
170 the specified white balance pipeline may be applied.
172 If AWB is enabled with `android.control.awbMode != OFF`, then
173 the camera device uses the last frame's AWB values
174 (or defaults if AWB has never been run).
180 The mode control selects how the image data is converted from the
181 sensor's native color into linear sRGB color.
184 When auto-white balance (AWB) is enabled with android.control.awbMode, this
185 control is overridden by the AWB routine. When AWB is disabled, the
186 application controls how the color mapping is performed.
188 We define the expected processing pipeline below. For consistency
189 across devices, this is always the case with TRANSFORM_MATRIX.
191 When either FULL or HIGH_QUALITY is used, the camera device may
192 do additional processing but android.colorCorrection.gains and
193 android.colorCorrection.transform will still be provided by the
194 camera device (in the results) and be roughly correct.
196 Switching to TRANSFORM_MATRIX and using the data provided from
197 FAST or HIGH_QUALITY will yield a picture with the same white point
198 as what was produced by the camera device in the earlier frame.
200 The expected processing pipeline is as follows:
202 ![White balance processing pipeline](android.colorCorrection.mode/processing_pipeline.png)
204 The white balance is encoded by two values, a 4-channel white-balance
205 gain vector (applied in the Bayer domain), and a 3x3 color transform
206 matrix (applied after demosaic).
208 The 4-channel white-balance gains are defined as:
210 android.colorCorrection.gains = [ R G_even G_odd B ]
212 where `G_even` is the gain for green pixels on even rows of the
213 output, and `G_odd` is the gain for green pixels on the odd rows.
214 These may be identical for a given camera device implementation; if
215 the camera device does not support a separate gain for even/odd green
216 channels, it will use the `G_even` value, and write `G_odd` equal to
217 `G_even` in the output result metadata.
219 The matrices for color transforms are defined as a 9-entry vector:
221 android.colorCorrection.transform = [ I0 I1 I2 I3 I4 I5 I6 I7 I8 ]
223 which define a transform from input sensor colors, `P_in = [ r g b ]`,
224 to output linear sRGB, `P_out = [ r' g' b' ]`,
226 with colors as follows:
232 Both the input and output value ranges must match. Overflow/underflow
233 values are clipped to fit within the range.
236 HAL must support both FAST and HIGH_QUALITY if color correction control is available
237 on the camera device, but the underlying implementation can be the same for both modes.
238 That is, if the highest quality implementation on the camera device does not slow down
239 capture rate, then FAST and HIGH_QUALITY should generate the same output.
242 <entry name="transform" type="rational" visibility="public"
243 type_notes="3x3 rational matrix in row-major order"
244 container="array" typedef="colorSpaceTransform" hwlevel="full">
249 <description>A color transform matrix to use to transform
250 from sensor RGB color space to output linear sRGB color space.
252 <units>Unitless scale factors</units>
253 <details>This matrix is either set by the camera device when the request
254 android.colorCorrection.mode is not TRANSFORM_MATRIX, or
255 directly by the application in the request when the
256 android.colorCorrection.mode is TRANSFORM_MATRIX.
258 In the latter case, the camera device may round the matrix to account
259 for precision issues; the final rounded matrix should be reported back
260 in this matrix result metadata. The transform should keep the magnitude
261 of the output color values within `[0, 1.0]` (assuming input color
262 values is within the normalized range `[0, 1.0]`), or clipping may occur.
264 The valid range of each matrix element varies on different devices, but
265 values within [-1.5, 3.0] are guaranteed not to be clipped.
268 <entry name="gains" type="float" visibility="public"
269 type_notes="A 1D array of floats for 4 color channel gains"
270 container="array" typedef="rggbChannelVector" hwlevel="full">
274 <description>Gains applying to Bayer raw color channels for
275 white-balance.</description>
276 <units>Unitless gain factors</units>
278 These per-channel gains are either set by the camera device
279 when the request android.colorCorrection.mode is not
280 TRANSFORM_MATRIX, or directly by the application in the
281 request when the android.colorCorrection.mode is
284 The gains in the result metadata are the gains actually
285 applied by the camera device to the current frame.
287 The valid range of gains varies on different devices, but gains
288 between [1.0, 3.0] are guaranteed not to be clipped. Even if a given
289 device allows gains below 1.0, this is usually not recommended because
290 this can create color artifacts.
293 The 4-channel white-balance gains are defined in
294 the order of `[R G_even G_odd B]`, where `G_even` is the gain
295 for green pixels on even rows of the output, and `G_odd`
296 is the gain for green pixels on the odd rows.
298 If a HAL does not support a separate gain for even/odd green
299 channels, it must use the `G_even` value, and write
300 `G_odd` equal to `G_even` in the output result metadata.
303 <entry name="aberrationMode" type="byte" visibility="public" enum="true" hwlevel="legacy">
307 No aberration correction is applied.
312 Aberration correction will not slow down capture rate
313 relative to sensor raw output.
318 Aberration correction operates at improved quality but the capture rate might be
319 reduced (relative to sensor raw output rate)
324 Mode of operation for the chromatic aberration correction algorithm.
326 <range>android.colorCorrection.availableAberrationModes</range>
328 Chromatic (color) aberration is caused by the fact that different wavelengths of light
329 can not focus on the same point after exiting from the lens. This metadata defines
330 the high level control of chromatic aberration correction algorithm, which aims to
331 minimize the chromatic artifacts that may occur along the object boundaries in an
334 FAST/HIGH_QUALITY both mean that camera device determined aberration
335 correction will be applied. HIGH_QUALITY mode indicates that the camera device will
336 use the highest-quality aberration correction algorithms, even if it slows down
337 capture rate. FAST means the camera device will not slow down capture rate when
338 applying aberration correction.
340 LEGACY devices will always be in FAST mode.
345 <clone entry="android.colorCorrection.mode" kind="controls">
347 <clone entry="android.colorCorrection.transform" kind="controls">
349 <clone entry="android.colorCorrection.gains" kind="controls">
351 <clone entry="android.colorCorrection.aberrationMode" kind="controls">
355 <entry name="availableAberrationModes" type="byte" visibility="public"
356 type_notes="list of enums" container="array" typedef="enumList" hwlevel="legacy">
361 List of aberration correction modes for android.colorCorrection.aberrationMode that are
362 supported by this camera device.
364 <range>Any value listed in android.colorCorrection.aberrationMode</range>
366 This key lists the valid modes for android.colorCorrection.aberrationMode. If no
367 aberration correction modes are available for a device, this list will solely include
368 OFF mode. All camera devices will support either OFF or FAST mode.
370 Camera devices that support the MANUAL_POST_PROCESSING capability will always list
371 OFF mode. This includes all FULL level devices.
373 LEGACY devices will always only support FAST mode.
376 HAL must support both FAST and HIGH_QUALITY if chromatic aberration control is available
377 on the camera device, but the underlying implementation can be the same for both modes.
378 That is, if the highest quality implementation on the camera device does not slow down
379 capture rate, then FAST and HIGH_QUALITY will generate the same output.
385 <section name="control">
387 <entry name="aeAntibandingMode" type="byte" visibility="public"
388 enum="true" hwlevel="legacy">
392 The camera device will not adjust exposure duration to
393 avoid banding problems.
398 The camera device will adjust exposure duration to
399 avoid banding problems with 50Hz illumination sources.
404 The camera device will adjust exposure duration to
405 avoid banding problems with 60Hz illumination
411 The camera device will automatically adapt its
412 antibanding routine to the current illumination
413 condition. This is the default mode if AUTO is
414 available on given camera device.
419 The desired setting for the camera device's auto-exposure
420 algorithm's antibanding compensation.
423 android.control.aeAvailableAntibandingModes
426 Some kinds of lighting fixtures, such as some fluorescent
427 lights, flicker at the rate of the power supply frequency
428 (60Hz or 50Hz, depending on country). While this is
429 typically not noticeable to a person, it can be visible to
430 a camera device. If a camera sets its exposure time to the
431 wrong value, the flicker may become visible in the
432 viewfinder as flicker or in a final captured image, as a
433 set of variable-brightness bands across the image.
435 Therefore, the auto-exposure routines of camera devices
436 include antibanding routines that ensure that the chosen
437 exposure value will not cause such banding. The choice of
438 exposure time depends on the rate of flicker, which the
439 camera device can detect automatically, or the expected
440 rate can be selected by the application using this
443 A given camera device may not support all of the possible
444 options for the antibanding mode. The
445 android.control.aeAvailableAntibandingModes key contains
446 the available modes for a given camera device.
448 AUTO mode is the default if it is available on given
449 camera device. When AUTO mode is not available, the
450 default will be either 50HZ or 60HZ, and both 50HZ
451 and 60HZ will be available.
453 If manual exposure control is enabled (by setting
454 android.control.aeMode or android.control.mode to OFF),
455 then this setting has no effect, and the application must
456 ensure it selects exposure times that do not cause banding
457 issues. The android.statistics.sceneFlicker key can assist
458 the application in this.
461 For all capture request templates, this field must be set
462 to AUTO if AUTO mode is available. If AUTO is not available,
463 the default must be either 50HZ or 60HZ, and both 50HZ and
464 60HZ must be available.
466 If manual exposure control is enabled (by setting
467 android.control.aeMode or android.control.mode to OFF),
468 then the exposure values provided by the application must not be
469 adjusted for antibanding.
473 <entry name="aeExposureCompensation" type="int32" visibility="public" hwlevel="legacy">
474 <description>Adjustment to auto-exposure (AE) target image
475 brightness.</description>
476 <units>Compensation steps</units>
477 <range>android.control.aeCompensationRange</range>
479 The adjustment is measured as a count of steps, with the
480 step size defined by android.control.aeCompensationStep and the
481 allowed range by android.control.aeCompensationRange.
483 For example, if the exposure value (EV) step is 0.333, '6'
484 will mean an exposure compensation of +2 EV; -3 will mean an
485 exposure compensation of -1 EV. One EV represents a doubling
486 of image brightness. Note that this control will only be
487 effective if android.control.aeMode `!=` OFF. This control
488 will take effect even when android.control.aeLock `== true`.
490 In the event of exposure compensation value being changed, camera device
491 may take several frames to reach the newly requested exposure target.
492 During that time, android.control.aeState field will be in the SEARCHING
493 state. Once the new exposure target is reached, android.control.aeState will
494 change from SEARCHING to either CONVERGED, LOCKED (if AE lock is enabled), or
495 FLASH_REQUIRED (if the scene is too dark for still capture).
499 <entry name="aeLock" type="byte" visibility="public" enum="true"
500 typedef="boolean" hwlevel="legacy">
503 <notes>Auto-exposure lock is disabled; the AE algorithm
504 is free to update its parameters.</notes></value>
506 <notes>Auto-exposure lock is enabled; the AE algorithm
507 must not update the exposure and sensitivity parameters
508 while the lock is active.
510 android.control.aeExposureCompensation setting changes
511 will still take effect while auto-exposure is locked.
513 Some rare LEGACY devices may not support
514 this, in which case the value will always be overridden to OFF.
517 <description>Whether auto-exposure (AE) is currently locked to its latest
518 calculated values.</description>
520 When set to `true` (ON), the AE algorithm is locked to its latest parameters,
521 and will not change exposure settings until the lock is set to `false` (OFF).
523 Note that even when AE is locked, the flash may be fired if
524 the android.control.aeMode is ON_AUTO_FLASH /
525 ON_ALWAYS_FLASH / ON_AUTO_FLASH_REDEYE.
527 When android.control.aeExposureCompensation is changed, even if the AE lock
528 is ON, the camera device will still adjust its exposure value.
530 If AE precapture is triggered (see android.control.aePrecaptureTrigger)
531 when AE is already locked, the camera device will not change the exposure time
532 (android.sensor.exposureTime) and sensitivity (android.sensor.sensitivity)
533 parameters. The flash may be fired if the android.control.aeMode
534 is ON_AUTO_FLASH/ON_AUTO_FLASH_REDEYE and the scene is too dark. If the
535 android.control.aeMode is ON_ALWAYS_FLASH, the scene may become overexposed.
536 Similarly, AE precapture trigger CANCEL has no effect when AE is already locked.
538 When an AE precapture sequence is triggered, AE unlock will not be able to unlock
539 the AE if AE is locked by the camera device internally during precapture metering
540 sequence In other words, submitting requests with AE unlock has no effect for an
541 ongoing precapture metering sequence. Otherwise, the precapture metering sequence
542 will never succeed in a sequence of preview requests where AE lock is always set
545 Since the camera device has a pipeline of in-flight requests, the settings that
546 get locked do not necessarily correspond to the settings that were present in the
547 latest capture result received from the camera device, since additional captures
548 and AE updates may have occurred even before the result was sent out. If an
549 application is switching between automatic and manual control and wishes to eliminate
550 any flicker during the switch, the following procedure is recommended:
552 1. Starting in auto-AE mode:
554 3. Wait for the first result to be output that has the AE locked
555 4. Copy exposure settings from that result into a request, set the request to manual AE
556 5. Submit the capture request, proceed to run manual AE as desired.
558 See android.control.aeState for AE lock related state transition details.
562 <entry name="aeMode" type="byte" visibility="public" enum="true" hwlevel="legacy">
566 The camera device's autoexposure routine is disabled.
568 The application-selected android.sensor.exposureTime,
569 android.sensor.sensitivity and
570 android.sensor.frameDuration are used by the camera
571 device, along with android.flash.* fields, if there's
572 a flash unit for this camera device.
574 Note that auto-white balance (AWB) and auto-focus (AF)
575 behavior is device dependent when AE is in OFF mode.
576 To have consistent behavior across different devices,
577 it is recommended to either set AWB and AF to OFF mode
578 or lock AWB and AF before setting AE to OFF.
579 See android.control.awbMode, android.control.afMode,
580 android.control.awbLock, and android.control.afTrigger
583 LEGACY devices do not support the OFF mode and will
584 override attempts to use this value to ON.
589 The camera device's autoexposure routine is active,
590 with no flash control.
592 The application's values for
593 android.sensor.exposureTime,
594 android.sensor.sensitivity, and
595 android.sensor.frameDuration are ignored. The
596 application has control over the various
597 android.flash.* fields.
602 Like ON, except that the camera device also controls
603 the camera's flash unit, firing it in low-light
606 The flash may be fired during a precapture sequence
607 (triggered by android.control.aePrecaptureTrigger) and
608 may be fired for captures for which the
609 android.control.captureIntent field is set to
613 <value>ON_ALWAYS_FLASH
615 Like ON, except that the camera device also controls
616 the camera's flash unit, always firing it for still
619 The flash may be fired during a precapture sequence
620 (triggered by android.control.aePrecaptureTrigger) and
621 will always be fired for captures for which the
622 android.control.captureIntent field is set to
626 <value>ON_AUTO_FLASH_REDEYE
628 Like ON_AUTO_FLASH, but with automatic red eye
631 If deemed necessary by the camera device, a red eye
632 reduction flash will fire during the precapture
636 <value hal_version="3.3">ON_EXTERNAL_FLASH
638 An external flash has been turned on.
640 It informs the camera device that an external flash has been turned on, and that
641 metering (and continuous focus if active) should be quickly recaculated to account
642 for the external flash. Otherwise, this mode acts like ON.
644 When the external flash is turned off, AE mode should be changed to one of the
645 other available AE modes.
647 If the camera device supports AE external flash mode, android.control.aeState must
648 be FLASH_REQUIRED after the camera device finishes AE scan and it's too dark without
653 <description>The desired mode for the camera device's
654 auto-exposure routine.</description>
655 <range>android.control.aeAvailableModes</range>
657 This control is only effective if android.control.mode is
660 When set to any of the ON modes, the camera device's
661 auto-exposure routine is enabled, overriding the
662 application's selected exposure time, sensor sensitivity,
663 and frame duration (android.sensor.exposureTime,
664 android.sensor.sensitivity, and
665 android.sensor.frameDuration). If one of the FLASH modes
666 is selected, the camera device's flash unit controls are
669 The FLASH modes are only available if the camera device
670 has a flash unit (android.flash.info.available is `true`).
672 If flash TORCH mode is desired, this field must be set to
673 ON or OFF, and android.flash.mode set to TORCH.
675 When set to any of the ON modes, the values chosen by the
676 camera device auto-exposure routine for the overridden
677 fields for a given capture will be available in its
682 <entry name="aeRegions" type="int32" visibility="public"
683 optional="true" container="array" typedef="meteringRectangle">
686 <size>area_count</size>
688 <description>List of metering areas to use for auto-exposure adjustment.</description>
689 <units>Pixel coordinates within android.sensor.info.activeArraySize</units>
690 <range>Coordinates must be between `[(0,0), (width, height))` of
691 android.sensor.info.activeArraySize</range>
693 Not available if android.control.maxRegionsAe is 0.
694 Otherwise will always be present.
696 The maximum number of regions supported by the device is determined by the value
697 of android.control.maxRegionsAe.
699 The coordinate system is based on the active pixel array,
700 with (0,0) being the top-left pixel in the active pixel array, and
701 (android.sensor.info.activeArraySize.width - 1,
702 android.sensor.info.activeArraySize.height - 1) being the
703 bottom-right pixel in the active pixel array.
705 The weight must be within `[0, 1000]`, and represents a weight
706 for every pixel in the area. This means that a large metering area
707 with the same weight as a smaller area will have more effect in
708 the metering result. Metering areas can partially overlap and the
709 camera device will add the weights in the overlap region.
711 The weights are relative to weights of other exposure metering regions, so if only one
712 region is used, all non-zero weights will have the same effect. A region with 0
715 If all regions have 0 weight, then no specific metering area needs to be used by the
718 If the metering region is outside the used android.scaler.cropRegion returned in
719 capture result metadata, the camera device will ignore the sections outside the crop
720 region and output only the intersection rectangle as the metering region in the result
721 metadata. If the region is entirely outside the crop region, it will be ignored and
722 not reported in the result metadata.
725 The data representation is `int[5 * area_count]`.
726 Every five elements represent a metering region of `(xmin, ymin, xmax, ymax, weight)`.
727 The rectangle is defined to be inclusive on xmin and ymin, but exclusive on xmax and
731 The HAL level representation of MeteringRectangle[] is a
733 Every five elements represent a metering region of
734 (xmin, ymin, xmax, ymax, weight).
735 The rectangle is defined to be inclusive on xmin and ymin, but
736 exclusive on xmax and ymax.
740 <entry name="aeTargetFpsRange" type="int32" visibility="public"
741 container="array" typedef="rangeInt" hwlevel="legacy">
745 <description>Range over which the auto-exposure routine can
746 adjust the capture frame rate to maintain good
747 exposure.</description>
748 <units>Frames per second (FPS)</units>
749 <range>Any of the entries in android.control.aeAvailableTargetFpsRanges</range>
750 <details>Only constrains auto-exposure (AE) algorithm, not
751 manual control of android.sensor.exposureTime and
752 android.sensor.frameDuration.</details>
755 <entry name="aePrecaptureTrigger" type="byte" visibility="public"
756 enum="true" hwlevel="limited">
759 <notes>The trigger is idle.</notes>
762 <notes>The precapture metering sequence will be started
763 by the camera device.
765 The exact effect of the precapture trigger depends on
766 the current AE mode and state.</notes>
769 <notes>The camera device will cancel any currently active or completed
770 precapture metering sequence, the auto-exposure routine will return to its
771 initial state.</notes>
774 <description>Whether the camera device will trigger a precapture
775 metering sequence when it processes this request.</description>
776 <details>This entry is normally set to IDLE, or is not
777 included at all in the request settings. When included and
778 set to START, the camera device will trigger the auto-exposure (AE)
779 precapture metering sequence.
781 When set to CANCEL, the camera device will cancel any active
782 precapture metering trigger, and return to its initial AE state.
783 If a precapture metering sequence is already completed, and the camera
784 device has implicitly locked the AE for subsequent still capture, the
785 CANCEL trigger will unlock the AE and return to its initial AE state.
787 The precapture sequence should be triggered before starting a
788 high-quality still capture for final metering decisions to
789 be made, and for firing pre-capture flash pulses to estimate
790 scene brightness and required final capture flash power, when
791 the flash is enabled.
793 Normally, this entry should be set to START for only a
794 single request, and the application should wait until the
795 sequence completes before starting a new one.
797 When a precapture metering sequence is finished, the camera device
798 may lock the auto-exposure routine internally to be able to accurately expose the
799 subsequent still capture image (`android.control.captureIntent == STILL_CAPTURE`).
800 For this case, the AE may not resume normal scan if no subsequent still capture is
801 submitted. To ensure that the AE routine restarts normal scan, the application should
802 submit a request with `android.control.aeLock == true`, followed by a request
803 with `android.control.aeLock == false`, if the application decides not to submit a
804 still capture request after the precapture sequence completes. Alternatively, for
805 API level 23 or newer devices, the CANCEL can be used to unlock the camera device
806 internally locked AE if the application doesn't submit a still capture request after
807 the AE precapture trigger. Note that, the CANCEL was added in API level 23, and must not
808 be used in devices that have earlier API levels.
810 The exact effect of auto-exposure (AE) precapture trigger
811 depends on the current AE mode and state; see
812 android.control.aeState for AE precapture state transition
815 On LEGACY-level devices, the precapture trigger is not supported;
816 capturing a high-resolution JPEG image will automatically trigger a
817 precapture sequence before the high-resolution capture, including
818 potentially firing a pre-capture flash.
820 Using the precapture trigger and the auto-focus trigger android.control.afTrigger
821 simultaneously is allowed. However, since these triggers often require cooperation between
822 the auto-focus and auto-exposure routines (for example, the may need to be enabled for a
823 focus sweep), the camera device may delay acting on a later trigger until the previous
824 trigger has been fully handled. This may lead to longer intervals between the trigger and
825 changes to android.control.aeState indicating the start of the precapture sequence, for
828 If both the precapture and the auto-focus trigger are activated on the same request, then
829 the camera device will complete them in the optimal order for that device.
832 The HAL must support triggering the AE precapture trigger while an AF trigger is active
833 (and vice versa), or at the same time as the AF trigger. It is acceptable for the HAL to
834 treat these as two consecutive triggers, for example handling the AF trigger and then the
835 AE trigger. Or the HAL may choose to optimize the case with both triggers fired at once,
836 to minimize the latency for converging both focus and exposure/flash usage.
840 <entry name="afMode" type="byte" visibility="public" enum="true"
844 <notes>The auto-focus routine does not control the lens;
845 android.lens.focusDistance is controlled by the
846 application.</notes></value>
848 <notes>Basic automatic focus mode.
850 In this mode, the lens does not move unless
851 the autofocus trigger action is called. When that trigger
852 is activated, AF will transition to ACTIVE_SCAN, then to
853 the outcome of the scan (FOCUSED or NOT_FOCUSED).
855 Always supported if lens is not fixed focus.
857 Use android.lens.info.minimumFocusDistance to determine if lens
860 Triggering AF_CANCEL resets the lens position to default,
861 and sets the AF state to INACTIVE.</notes></value>
863 <notes>Close-up focusing mode.
865 In this mode, the lens does not move unless the
866 autofocus trigger action is called. When that trigger is
867 activated, AF will transition to ACTIVE_SCAN, then to
868 the outcome of the scan (FOCUSED or NOT_FOCUSED). This
869 mode is optimized for focusing on objects very close to
872 When that trigger is activated, AF will transition to
873 ACTIVE_SCAN, then to the outcome of the scan (FOCUSED or
874 NOT_FOCUSED). Triggering cancel AF resets the lens
875 position to default, and sets the AF state to
876 INACTIVE.</notes></value>
877 <value>CONTINUOUS_VIDEO
878 <notes>In this mode, the AF algorithm modifies the lens
879 position continually to attempt to provide a
880 constantly-in-focus image stream.
882 The focusing behavior should be suitable for good quality
883 video recording; typically this means slower focus
884 movement and no overshoots. When the AF trigger is not
885 involved, the AF algorithm should start in INACTIVE state,
886 and then transition into PASSIVE_SCAN and PASSIVE_FOCUSED
887 states as appropriate. When the AF trigger is activated,
888 the algorithm should immediately transition into
889 AF_FOCUSED or AF_NOT_FOCUSED as appropriate, and lock the
890 lens position until a cancel AF trigger is received.
892 Once cancel is received, the algorithm should transition
893 back to INACTIVE and resume passive scan. Note that this
894 behavior is not identical to CONTINUOUS_PICTURE, since an
895 ongoing PASSIVE_SCAN must immediately be
896 canceled.</notes></value>
897 <value>CONTINUOUS_PICTURE
898 <notes>In this mode, the AF algorithm modifies the lens
899 position continually to attempt to provide a
900 constantly-in-focus image stream.
902 The focusing behavior should be suitable for still image
903 capture; typically this means focusing as fast as
904 possible. When the AF trigger is not involved, the AF
905 algorithm should start in INACTIVE state, and then
906 transition into PASSIVE_SCAN and PASSIVE_FOCUSED states as
907 appropriate as it attempts to maintain focus. When the AF
908 trigger is activated, the algorithm should finish its
909 PASSIVE_SCAN if active, and then transition into
910 AF_FOCUSED or AF_NOT_FOCUSED as appropriate, and lock the
911 lens position until a cancel AF trigger is received.
913 When the AF cancel trigger is activated, the algorithm
914 should transition back to INACTIVE and then act as if it
915 has just been started.</notes></value>
917 <notes>Extended depth of field (digital focus) mode.
919 The camera device will produce images with an extended
920 depth of field automatically; no special focusing
921 operations need to be done before taking a picture.
923 AF triggers are ignored, and the AF state will always be
924 INACTIVE.</notes></value>
926 <description>Whether auto-focus (AF) is currently enabled, and what
927 mode it is set to.</description>
928 <range>android.control.afAvailableModes</range>
929 <details>Only effective if android.control.mode = AUTO and the lens is not fixed focus
930 (i.e. `android.lens.info.minimumFocusDistance > 0`). Also note that
931 when android.control.aeMode is OFF, the behavior of AF is device
932 dependent. It is recommended to lock AF by using android.control.afTrigger before
933 setting android.control.aeMode to OFF, or set AF mode to OFF when AE is OFF.
935 If the lens is controlled by the camera device auto-focus algorithm,
936 the camera device will report the current AF status in android.control.afState
937 in result metadata.</details>
939 When afMode is AUTO or MACRO, the lens must not move until an AF trigger is sent in a
940 request (android.control.afTrigger `==` START). After an AF trigger, the afState will end
941 up with either FOCUSED_LOCKED or NOT_FOCUSED_LOCKED state (see
942 android.control.afState for detailed state transitions), which indicates that the lens is
943 locked and will not move. If camera movement (e.g. tilting camera) causes the lens to move
944 after the lens is locked, the HAL must compensate this movement appropriately such that
945 the same focal plane remains in focus.
947 When afMode is one of the continuous auto focus modes, the HAL is free to start a AF
948 scan whenever it's not locked. When the lens is locked after an AF trigger
949 (see android.control.afState for detailed state transitions), the HAL should maintain the
950 same lock behavior as above.
952 When afMode is OFF, the application controls focus manually. The accuracy of the
953 focus distance control depends on the android.lens.info.focusDistanceCalibration.
954 However, the lens must not move regardless of the camera movement for any focus distance
957 To put this in concrete terms, if the camera has lens elements which may move based on
958 camera orientation or motion (e.g. due to gravity), then the HAL must drive the lens to
959 remain in a fixed position invariant to the camera's orientation or motion, for example,
960 by using accelerometer measurements in the lens control logic. This is a typical issue
961 that will arise on camera modules with open-loop VCMs.
965 <entry name="afRegions" type="int32" visibility="public"
966 optional="true" container="array" typedef="meteringRectangle">
969 <size>area_count</size>
971 <description>List of metering areas to use for auto-focus.</description>
972 <units>Pixel coordinates within android.sensor.info.activeArraySize</units>
973 <range>Coordinates must be between `[(0,0), (width, height))` of
974 android.sensor.info.activeArraySize</range>
976 Not available if android.control.maxRegionsAf is 0.
977 Otherwise will always be present.
979 The maximum number of focus areas supported by the device is determined by the value
980 of android.control.maxRegionsAf.
982 The coordinate system is based on the active pixel array,
983 with (0,0) being the top-left pixel in the active pixel array, and
984 (android.sensor.info.activeArraySize.width - 1,
985 android.sensor.info.activeArraySize.height - 1) being the
986 bottom-right pixel in the active pixel array.
988 The weight must be within `[0, 1000]`, and represents a weight
989 for every pixel in the area. This means that a large metering area
990 with the same weight as a smaller area will have more effect in
991 the metering result. Metering areas can partially overlap and the
992 camera device will add the weights in the overlap region.
994 The weights are relative to weights of other metering regions, so if only one region
995 is used, all non-zero weights will have the same effect. A region with 0 weight is
998 If all regions have 0 weight, then no specific metering area needs to be used by the
999 camera device. The capture result will either be a zero weight region as well, or
1000 the region selected by the camera device as the focus area of interest.
1002 If the metering region is outside the used android.scaler.cropRegion returned in
1003 capture result metadata, the camera device will ignore the sections outside the crop
1004 region and output only the intersection rectangle as the metering region in the result
1005 metadata. If the region is entirely outside the crop region, it will be ignored and
1006 not reported in the result metadata.
1009 The data representation is `int[5 * area_count]`.
1010 Every five elements represent a metering region of `(xmin, ymin, xmax, ymax, weight)`.
1011 The rectangle is defined to be inclusive on xmin and ymin, but exclusive on xmax and
1015 The HAL level representation of MeteringRectangle[] is a
1016 int[5 * area_count].
1017 Every five elements represent a metering region of
1018 (xmin, ymin, xmax, ymax, weight).
1019 The rectangle is defined to be inclusive on xmin and ymin, but
1020 exclusive on xmax and ymax.
1024 <entry name="afTrigger" type="byte" visibility="public" enum="true"
1028 <notes>The trigger is idle.</notes>
1031 <notes>Autofocus will trigger now.</notes>
1034 <notes>Autofocus will return to its initial
1035 state, and cancel any currently active trigger.</notes>
1039 Whether the camera device will trigger autofocus for this request.
1041 <details>This entry is normally set to IDLE, or is not
1042 included at all in the request settings.
1044 When included and set to START, the camera device will trigger the
1045 autofocus algorithm. If autofocus is disabled, this trigger has no effect.
1047 When set to CANCEL, the camera device will cancel any active trigger,
1048 and return to its initial AF state.
1050 Generally, applications should set this entry to START or CANCEL for only a
1051 single capture, and then return it to IDLE (or not set at all). Specifying
1052 START for multiple captures in a row means restarting the AF operation over
1055 See android.control.afState for what the trigger means for each AF mode.
1057 Using the autofocus trigger and the precapture trigger android.control.aePrecaptureTrigger
1058 simultaneously is allowed. However, since these triggers often require cooperation between
1059 the auto-focus and auto-exposure routines (for example, the may need to be enabled for a
1060 focus sweep), the camera device may delay acting on a later trigger until the previous
1061 trigger has been fully handled. This may lead to longer intervals between the trigger and
1062 changes to android.control.afState, for example.
1065 The HAL must support triggering the AF trigger while an AE precapture trigger is active
1066 (and vice versa), or at the same time as the AE trigger. It is acceptable for the HAL to
1067 treat these as two consecutive triggers, for example handling the AF trigger and then the
1068 AE trigger. Or the HAL may choose to optimize the case with both triggers fired at once,
1069 to minimize the latency for converging both focus and exposure/flash usage.
1073 <entry name="awbLock" type="byte" visibility="public" enum="true"
1074 typedef="boolean" hwlevel="legacy">
1077 <notes>Auto-white balance lock is disabled; the AWB
1078 algorithm is free to update its parameters if in AUTO
1079 mode.</notes></value>
1081 <notes>Auto-white balance lock is enabled; the AWB
1082 algorithm will not update its parameters while the lock
1083 is active.</notes></value>
1085 <description>Whether auto-white balance (AWB) is currently locked to its
1086 latest calculated values.</description>
1088 When set to `true` (ON), the AWB algorithm is locked to its latest parameters,
1089 and will not change color balance settings until the lock is set to `false` (OFF).
1091 Since the camera device has a pipeline of in-flight requests, the settings that
1092 get locked do not necessarily correspond to the settings that were present in the
1093 latest capture result received from the camera device, since additional captures
1094 and AWB updates may have occurred even before the result was sent out. If an
1095 application is switching between automatic and manual control and wishes to eliminate
1096 any flicker during the switch, the following procedure is recommended:
1098 1. Starting in auto-AWB mode:
1100 3. Wait for the first result to be output that has the AWB locked
1101 4. Copy AWB settings from that result into a request, set the request to manual AWB
1102 5. Submit the capture request, proceed to run manual AWB as desired.
1104 Note that AWB lock is only meaningful when
1105 android.control.awbMode is in the AUTO mode; in other modes,
1106 AWB is already fixed to a specific setting.
1108 Some LEGACY devices may not support ON; the value is then overridden to OFF.
1112 <entry name="awbMode" type="byte" visibility="public" enum="true"
1117 The camera device's auto-white balance routine is disabled.
1119 The application-selected color transform matrix
1120 (android.colorCorrection.transform) and gains
1121 (android.colorCorrection.gains) are used by the camera
1122 device for manual white balance control.
1127 The camera device's auto-white balance routine is active.
1129 The application's values for android.colorCorrection.transform
1130 and android.colorCorrection.gains are ignored.
1131 For devices that support the MANUAL_POST_PROCESSING capability, the
1132 values used by the camera device for the transform and gains
1133 will be available in the capture result for this request.
1138 The camera device's auto-white balance routine is disabled;
1139 the camera device uses incandescent light as the assumed scene
1140 illumination for white balance.
1142 While the exact white balance transforms are up to the
1143 camera device, they will approximately match the CIE
1144 standard illuminant A.
1146 The application's values for android.colorCorrection.transform
1147 and android.colorCorrection.gains are ignored.
1148 For devices that support the MANUAL_POST_PROCESSING capability, the
1149 values used by the camera device for the transform and gains
1150 will be available in the capture result for this request.
1155 The camera device's auto-white balance routine is disabled;
1156 the camera device uses fluorescent light as the assumed scene
1157 illumination for white balance.
1159 While the exact white balance transforms are up to the
1160 camera device, they will approximately match the CIE
1161 standard illuminant F2.
1163 The application's values for android.colorCorrection.transform
1164 and android.colorCorrection.gains are ignored.
1165 For devices that support the MANUAL_POST_PROCESSING capability, the
1166 values used by the camera device for the transform and gains
1167 will be available in the capture result for this request.
1170 <value>WARM_FLUORESCENT
1172 The camera device's auto-white balance routine is disabled;
1173 the camera device uses warm fluorescent light as the assumed scene
1174 illumination for white balance.
1176 While the exact white balance transforms are up to the
1177 camera device, they will approximately match the CIE
1178 standard illuminant F4.
1180 The application's values for android.colorCorrection.transform
1181 and android.colorCorrection.gains are ignored.
1182 For devices that support the MANUAL_POST_PROCESSING capability, the
1183 values used by the camera device for the transform and gains
1184 will be available in the capture result for this request.
1189 The camera device's auto-white balance routine is disabled;
1190 the camera device uses daylight light as the assumed scene
1191 illumination for white balance.
1193 While the exact white balance transforms are up to the
1194 camera device, they will approximately match the CIE
1195 standard illuminant D65.
1197 The application's values for android.colorCorrection.transform
1198 and android.colorCorrection.gains are ignored.
1199 For devices that support the MANUAL_POST_PROCESSING capability, the
1200 values used by the camera device for the transform and gains
1201 will be available in the capture result for this request.
1204 <value>CLOUDY_DAYLIGHT
1206 The camera device's auto-white balance routine is disabled;
1207 the camera device uses cloudy daylight light as the assumed scene
1208 illumination for white balance.
1210 The application's values for android.colorCorrection.transform
1211 and android.colorCorrection.gains are ignored.
1212 For devices that support the MANUAL_POST_PROCESSING capability, the
1213 values used by the camera device for the transform and gains
1214 will be available in the capture result for this request.
1219 The camera device's auto-white balance routine is disabled;
1220 the camera device uses twilight light as the assumed scene
1221 illumination for white balance.
1223 The application's values for android.colorCorrection.transform
1224 and android.colorCorrection.gains are ignored.
1225 For devices that support the MANUAL_POST_PROCESSING capability, the
1226 values used by the camera device for the transform and gains
1227 will be available in the capture result for this request.
1232 The camera device's auto-white balance routine is disabled;
1233 the camera device uses shade light as the assumed scene
1234 illumination for white balance.
1236 The application's values for android.colorCorrection.transform
1237 and android.colorCorrection.gains are ignored.
1238 For devices that support the MANUAL_POST_PROCESSING capability, the
1239 values used by the camera device for the transform and gains
1240 will be available in the capture result for this request.
1244 <description>Whether auto-white balance (AWB) is currently setting the color
1245 transform fields, and what its illumination target
1247 <range>android.control.awbAvailableModes</range>
1249 This control is only effective if android.control.mode is AUTO.
1251 When set to the ON mode, the camera device's auto-white balance
1252 routine is enabled, overriding the application's selected
1253 android.colorCorrection.transform, android.colorCorrection.gains and
1254 android.colorCorrection.mode. Note that when android.control.aeMode
1255 is OFF, the behavior of AWB is device dependent. It is recommened to
1256 also set AWB mode to OFF or lock AWB by using android.control.awbLock before
1257 setting AE mode to OFF.
1259 When set to the OFF mode, the camera device's auto-white balance
1260 routine is disabled. The application manually controls the white
1261 balance by android.colorCorrection.transform, android.colorCorrection.gains
1262 and android.colorCorrection.mode.
1264 When set to any other modes, the camera device's auto-white
1265 balance routine is disabled. The camera device uses each
1266 particular illumination target for white balance
1267 adjustment. The application's values for
1268 android.colorCorrection.transform,
1269 android.colorCorrection.gains and
1270 android.colorCorrection.mode are ignored.
1274 <entry name="awbRegions" type="int32" visibility="public"
1275 optional="true" container="array" typedef="meteringRectangle">
1278 <size>area_count</size>
1280 <description>List of metering areas to use for auto-white-balance illuminant
1281 estimation.</description>
1282 <units>Pixel coordinates within android.sensor.info.activeArraySize</units>
1283 <range>Coordinates must be between `[(0,0), (width, height))` of
1284 android.sensor.info.activeArraySize</range>
1286 Not available if android.control.maxRegionsAwb is 0.
1287 Otherwise will always be present.
1289 The maximum number of regions supported by the device is determined by the value
1290 of android.control.maxRegionsAwb.
1292 The coordinate system is based on the active pixel array,
1293 with (0,0) being the top-left pixel in the active pixel array, and
1294 (android.sensor.info.activeArraySize.width - 1,
1295 android.sensor.info.activeArraySize.height - 1) being the
1296 bottom-right pixel in the active pixel array.
1298 The weight must range from 0 to 1000, and represents a weight
1299 for every pixel in the area. This means that a large metering area
1300 with the same weight as a smaller area will have more effect in
1301 the metering result. Metering areas can partially overlap and the
1302 camera device will add the weights in the overlap region.
1304 The weights are relative to weights of other white balance metering regions, so if
1305 only one region is used, all non-zero weights will have the same effect. A region with
1306 0 weight is ignored.
1308 If all regions have 0 weight, then no specific metering area needs to be used by the
1311 If the metering region is outside the used android.scaler.cropRegion returned in
1312 capture result metadata, the camera device will ignore the sections outside the crop
1313 region and output only the intersection rectangle as the metering region in the result
1314 metadata. If the region is entirely outside the crop region, it will be ignored and
1315 not reported in the result metadata.
1318 The data representation is `int[5 * area_count]`.
1319 Every five elements represent a metering region of `(xmin, ymin, xmax, ymax, weight)`.
1320 The rectangle is defined to be inclusive on xmin and ymin, but exclusive on xmax and
1324 The HAL level representation of MeteringRectangle[] is a
1325 int[5 * area_count].
1326 Every five elements represent a metering region of
1327 (xmin, ymin, xmax, ymax, weight).
1328 The rectangle is defined to be inclusive on xmin and ymin, but
1329 exclusive on xmax and ymax.
1333 <entry name="captureIntent" type="byte" visibility="public" enum="true"
1337 <notes>The goal of this request doesn't fall into the other
1338 categories. The camera device will default to preview-like
1339 behavior.</notes></value>
1341 <notes>This request is for a preview-like use case.
1343 The precapture trigger may be used to start off a metering
1346 <value>STILL_CAPTURE
1347 <notes>This request is for a still capture-type
1350 If the flash unit is under automatic control, it may fire as needed.
1353 <notes>This request is for a video recording
1354 use case.</notes></value>
1355 <value>VIDEO_SNAPSHOT
1356 <notes>This request is for a video snapshot (still
1357 image while recording video) use case.
1359 The camera device should take the highest-quality image
1360 possible (given the other settings) without disrupting the
1361 frame rate of video recording. </notes></value>
1362 <value>ZERO_SHUTTER_LAG
1363 <notes>This request is for a ZSL usecase; the
1364 application will stream full-resolution images and
1365 reprocess one or several later for a final
1369 <notes>This request is for manual capture use case where
1370 the applications want to directly control the capture parameters.
1372 For example, the application may wish to manually control
1373 android.sensor.exposureTime, android.sensor.sensitivity, etc.
1375 <value hal_version="3.3">MOTION_TRACKING
1376 <notes>This request is for a motion tracking use case, where
1377 the application will use camera and inertial sensor data to
1378 locate and track objects in the world.
1380 The camera device auto-exposure routine will limit the exposure time
1381 of the camera to no more than 20 milliseconds, to minimize motion blur.
1384 <description>Information to the camera device 3A (auto-exposure,
1385 auto-focus, auto-white balance) routines about the purpose
1386 of this capture, to help the camera device to decide optimal 3A
1387 strategy.</description>
1388 <details>This control (except for MANUAL) is only effective if
1389 `android.control.mode != OFF` and any 3A routine is active.
1391 All intents are supported by all devices, except that:
1392 * ZERO_SHUTTER_LAG will be supported if android.request.availableCapabilities contains
1393 PRIVATE_REPROCESSING or YUV_REPROCESSING.
1394 * MANUAL will be supported if android.request.availableCapabilities contains
1396 * MOTION_TRACKING will be supported if android.request.availableCapabilities contains
1401 <entry name="effectMode" type="byte" visibility="public" enum="true"
1406 No color effect will be applied.
1409 <value optional="true">MONO
1411 A "monocolor" effect where the image is mapped into
1414 This will typically be grayscale.
1417 <value optional="true">NEGATIVE
1419 A "photo-negative" effect where the image's colors
1423 <value optional="true">SOLARIZE
1425 A "solarisation" effect (Sabattier effect) where the
1426 image is wholly or partially reversed in
1430 <value optional="true">SEPIA
1432 A "sepia" effect where the image is mapped into warm
1433 gray, red, and brown tones.
1436 <value optional="true">POSTERIZE
1438 A "posterization" effect where the image uses
1439 discrete regions of tone rather than a continuous
1443 <value optional="true">WHITEBOARD
1445 A "whiteboard" effect where the image is typically displayed
1446 as regions of white, with black or grey details.
1449 <value optional="true">BLACKBOARD
1451 A "blackboard" effect where the image is typically displayed
1452 as regions of black, with white or grey details.
1455 <value optional="true">AQUA
1457 An "aqua" effect where a blue hue is added to the image.
1461 <description>A special color effect to apply.</description>
1462 <range>android.control.availableEffects</range>
1464 When this mode is set, a color effect will be applied
1465 to images produced by the camera device. The interpretation
1466 and implementation of these color effects is left to the
1467 implementor of the camera device, and should not be
1468 depended on to be consistent (or present) across all
1473 <entry name="mode" type="byte" visibility="public" enum="true"
1477 <notes>Full application control of pipeline.
1479 All control by the device's metering and focusing (3A)
1480 routines is disabled, and no other settings in
1481 android.control.* have any effect, except that
1482 android.control.captureIntent may be used by the camera
1483 device to select post-processing values for processing
1484 blocks that do not allow for manual control, or are not
1485 exposed by the camera API.
1487 However, the camera device's 3A routines may continue to
1488 collect statistics and update their internal state so that
1489 when control is switched to AUTO mode, good control values
1490 can be immediately applied.
1493 <notes>Use settings for each individual 3A routine.
1495 Manual control of capture parameters is disabled. All
1496 controls in android.control.* besides sceneMode take
1497 effect.</notes></value>
1498 <value optional="true">USE_SCENE_MODE
1499 <notes>Use a specific scene mode.
1501 Enabling this disables control.aeMode, control.awbMode and
1502 control.afMode controls; the camera device will ignore
1503 those settings while USE_SCENE_MODE is active (except for
1504 FACE_PRIORITY scene mode). Other control entries are still active.
1505 This setting can only be used if scene mode is supported (i.e.
1506 android.control.availableSceneModes
1507 contain some modes other than DISABLED).</notes></value>
1508 <value optional="true">OFF_KEEP_STATE
1509 <notes>Same as OFF mode, except that this capture will not be
1510 used by camera device background auto-exposure, auto-white balance and
1511 auto-focus algorithms (3A) to update their statistics.
1513 Specifically, the 3A routines are locked to the last
1514 values set from a request with AUTO, OFF, or
1515 USE_SCENE_MODE, and any statistics or state updates
1516 collected from manual captures with OFF_KEEP_STATE will be
1517 discarded by the camera device.
1520 <description>Overall mode of 3A (auto-exposure, auto-white-balance, auto-focus) control
1521 routines.</description>
1522 <range>android.control.availableModes</range>
1524 This is a top-level 3A control switch. When set to OFF, all 3A control
1525 by the camera device is disabled. The application must set the fields for
1526 capture parameters itself.
1528 When set to AUTO, the individual algorithm controls in
1529 android.control.* are in effect, such as android.control.afMode.
1531 When set to USE_SCENE_MODE, the individual controls in
1532 android.control.* are mostly disabled, and the camera device
1533 implements one of the scene mode settings (such as ACTION,
1534 SUNSET, or PARTY) as it wishes. The camera device scene mode
1535 3A settings are provided by {@link
1536 android.hardware.camera2.CaptureResult|ACameraCaptureSession_captureCallback_result
1539 When set to OFF_KEEP_STATE, it is similar to OFF mode, the only difference
1540 is that this frame will not be used by camera device background 3A statistics
1541 update, as if this frame is never captured. This mode can be used in the scenario
1542 where the application doesn't want a 3A manual control capture to affect
1543 the subsequent auto 3A capture results.
1547 <entry name="sceneMode" type="byte" visibility="public" enum="true"
1550 <value id="0">DISABLED
1552 Indicates that no scene modes are set for a given capture request.
1555 <value>FACE_PRIORITY
1556 <notes>If face detection support exists, use face
1557 detection data for auto-focus, auto-white balance, and
1558 auto-exposure routines.
1560 If face detection statistics are disabled
1561 (i.e. android.statistics.faceDetectMode is set to OFF),
1562 this should still operate correctly (but will not return
1563 face detection statistics to the framework).
1565 Unlike the other scene modes, android.control.aeMode,
1566 android.control.awbMode, and android.control.afMode
1567 remain active when FACE_PRIORITY is set.
1570 <value optional="true">ACTION
1572 Optimized for photos of quickly moving objects.
1577 <value optional="true">PORTRAIT
1579 Optimized for still photos of people.
1582 <value optional="true">LANDSCAPE
1584 Optimized for photos of distant macroscopic objects.
1587 <value optional="true">NIGHT
1589 Optimized for low-light settings.
1592 <value optional="true">NIGHT_PORTRAIT
1594 Optimized for still photos of people in low-light
1598 <value optional="true">THEATRE
1600 Optimized for dim, indoor settings where flash must
1604 <value optional="true">BEACH
1606 Optimized for bright, outdoor beach settings.
1609 <value optional="true">SNOW
1611 Optimized for bright, outdoor settings containing snow.
1614 <value optional="true">SUNSET
1616 Optimized for scenes of the setting sun.
1619 <value optional="true">STEADYPHOTO
1621 Optimized to avoid blurry photos due to small amounts of
1622 device motion (for example: due to hand shake).
1625 <value optional="true">FIREWORKS
1627 Optimized for nighttime photos of fireworks.
1630 <value optional="true">SPORTS
1632 Optimized for photos of quickly moving people.
1637 <value optional="true">PARTY
1639 Optimized for dim, indoor settings with multiple moving
1643 <value optional="true">CANDLELIGHT
1645 Optimized for dim settings where the main light source
1649 <value optional="true">BARCODE
1651 Optimized for accurately capturing a photo of barcode
1652 for use by camera applications that wish to read the
1656 <value deprecated="true" optional="true" ndk_hidden="true">HIGH_SPEED_VIDEO
1658 This is deprecated, please use {@link
1659 android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}
1661 android.hardware.camera2.CameraConstrainedHighSpeedCaptureSession#createHighSpeedRequestList}
1662 for high speed video recording.
1664 Optimized for high speed video recording (frame rate >=60fps) use case.
1666 The supported high speed video sizes and fps ranges are specified in
1667 android.control.availableHighSpeedVideoConfigurations. To get desired
1668 output frame rates, the application is only allowed to select video size
1669 and fps range combinations listed in this static metadata. The fps range
1670 can be control via android.control.aeTargetFpsRange.
1672 In this mode, the camera device will override aeMode, awbMode, and afMode to
1673 ON, ON, and CONTINUOUS_VIDEO, respectively. All post-processing block mode
1674 controls will be overridden to be FAST. Therefore, no manual control of capture
1675 and post-processing parameters is possible. All other controls operate the
1676 same as when android.control.mode == AUTO. This means that all other
1677 android.control.* fields continue to work, such as
1679 * android.control.aeTargetFpsRange
1680 * android.control.aeExposureCompensation
1681 * android.control.aeLock
1682 * android.control.awbLock
1683 * android.control.effectMode
1684 * android.control.aeRegions
1685 * android.control.afRegions
1686 * android.control.awbRegions
1687 * android.control.afTrigger
1688 * android.control.aePrecaptureTrigger
1690 Outside of android.control.*, the following controls will work:
1692 * android.flash.mode (automatic flash for still capture will not work since aeMode is ON)
1693 * android.lens.opticalStabilizationMode (if it is supported)
1694 * android.scaler.cropRegion
1695 * android.statistics.faceDetectMode
1697 For high speed recording use case, the actual maximum supported frame rate may
1698 be lower than what camera can output, depending on the destination Surfaces for
1699 the image data. For example, if the destination surface is from video encoder,
1700 the application need check if the video encoder is capable of supporting the
1701 high frame rate for a given video size, or it will end up with lower recording
1702 frame rate. If the destination surface is from preview window, the preview frame
1703 rate will be bounded by the screen refresh rate.
1705 The camera device will only support up to 2 output high speed streams
1706 (processed non-stalling format defined in android.request.maxNumOutputStreams)
1707 in this mode. This control will be effective only if all of below conditions are true:
1709 * The application created no more than maxNumHighSpeedStreams processed non-stalling
1710 format output streams, where maxNumHighSpeedStreams is calculated as
1711 min(2, android.request.maxNumOutputStreams[Processed (but not-stalling)]).
1712 * The stream sizes are selected from the sizes reported by
1713 android.control.availableHighSpeedVideoConfigurations.
1714 * No processed non-stalling or raw streams are configured.
1716 When above conditions are NOT satistied, the controls of this mode and
1717 android.control.aeTargetFpsRange will be ignored by the camera device,
1718 the camera device will fall back to android.control.mode `==` AUTO,
1719 and the returned capture result metadata will give the fps range choosen
1720 by the camera device.
1722 Switching into or out of this mode may trigger some camera ISP/sensor
1723 reconfigurations, which may introduce extra latency. It is recommended that
1724 the application avoids unnecessary scene mode switch as much as possible.
1727 <value optional="true">HDR
1729 Turn on a device-specific high dynamic range (HDR) mode.
1731 In this scene mode, the camera device captures images
1732 that keep a larger range of scene illumination levels
1733 visible in the final image. For example, when taking a
1734 picture of a object in front of a bright window, both
1735 the object and the scene through the window may be
1736 visible when using HDR mode, while in normal AUTO mode,
1737 one or the other may be poorly exposed. As a tradeoff,
1738 HDR mode generally takes much longer to capture a single
1739 image, has no user control, and may have other artifacts
1740 depending on the HDR method used.
1742 Therefore, HDR captures operate at a much slower rate
1743 than regular captures.
1745 In this mode, on LIMITED or FULL devices, when a request
1746 is made with a android.control.captureIntent of
1747 STILL_CAPTURE, the camera device will capture an image
1748 using a high dynamic range capture technique. On LEGACY
1749 devices, captures that target a JPEG-format output will
1750 be captured with HDR, and the capture intent is not
1753 The HDR capture may involve the device capturing a burst
1754 of images internally and combining them into one, or it
1755 may involve the device using specialized high dynamic
1756 range capture hardware. In all cases, a single image is
1757 produced in response to a capture request submitted
1760 Since substantial post-processing is generally needed to
1761 produce an HDR image, only YUV, PRIVATE, and JPEG
1762 outputs are supported for LIMITED/FULL device HDR
1763 captures, and only JPEG outputs are supported for LEGACY
1764 HDR captures. Using a RAW output for HDR capture is not
1767 Some devices may also support always-on HDR, which
1768 applies HDR processing at full frame rate. For these
1769 devices, intents other than STILL_CAPTURE will also
1770 produce an HDR output with no frame rate impact compared
1771 to normal operation, though the quality may be lower
1772 than for STILL_CAPTURE intents.
1774 If SCENE_MODE_HDR is used with unsupported output types
1775 or capture intents, the images captured will be as if
1776 the SCENE_MODE was not enabled at all.
1779 <value optional="true" hidden="true">FACE_PRIORITY_LOW_LIGHT
1780 <notes>Same as FACE_PRIORITY scene mode, except that the camera
1781 device will choose higher sensitivity values (android.sensor.sensitivity)
1782 under low light conditions.
1784 The camera device may be tuned to expose the images in a reduced
1785 sensitivity range to produce the best quality images. For example,
1786 if the android.sensor.info.sensitivityRange gives range of [100, 1600],
1787 the camera device auto-exposure routine tuning process may limit the actual
1788 exposure sensitivity range to [100, 1200] to ensure that the noise level isn't
1789 exessive in order to preserve the image quality. Under this situation, the image under
1790 low light may be under-exposed when the sensor max exposure time (bounded by the
1791 android.control.aeTargetFpsRange when android.control.aeMode is one of the
1792 ON_* modes) and effective max sensitivity are reached. This scene mode allows the
1793 camera device auto-exposure routine to increase the sensitivity up to the max
1794 sensitivity specified by android.sensor.info.sensitivityRange when the scene is too
1795 dark and the max exposure time is reached. The captured images may be noisier
1796 compared with the images captured in normal FACE_PRIORITY mode; therefore, it is
1797 recommended that the application only use this scene mode when it is capable of
1798 reducing the noise level of the captured images.
1800 Unlike the other scene modes, android.control.aeMode,
1801 android.control.awbMode, and android.control.afMode
1802 remain active when FACE_PRIORITY_LOW_LIGHT is set.
1805 <value optional="true" hidden="true" id="100">DEVICE_CUSTOM_START
1807 Scene mode values within the range of
1808 `[DEVICE_CUSTOM_START, DEVICE_CUSTOM_END]` are reserved for device specific
1809 customized scene modes.
1812 <value optional="true" hidden="true" id="127">DEVICE_CUSTOM_END
1814 Scene mode values within the range of
1815 `[DEVICE_CUSTOM_START, DEVICE_CUSTOM_END]` are reserved for device specific
1816 customized scene modes.
1821 Control for which scene mode is currently active.
1823 <range>android.control.availableSceneModes</range>
1825 Scene modes are custom camera modes optimized for a certain set of conditions and
1828 This is the mode that that is active when
1829 `android.control.mode == USE_SCENE_MODE`. Aside from FACE_PRIORITY, these modes will
1830 disable android.control.aeMode, android.control.awbMode, and android.control.afMode
1833 The interpretation and implementation of these scene modes is left
1834 to the implementor of the camera device. Their behavior will not be
1835 consistent across all devices, and any given device may only implement
1836 a subset of these modes.
1839 HAL implementations that include scene modes are expected to provide
1840 the per-scene settings to use for android.control.aeMode,
1841 android.control.awbMode, and android.control.afMode in
1842 android.control.sceneModeOverrides.
1844 For HIGH_SPEED_VIDEO mode, if it is included in android.control.availableSceneModes, the
1845 HAL must list supported video size and fps range in
1846 android.control.availableHighSpeedVideoConfigurations. For a given size, e.g. 1280x720,
1847 if the HAL has two different sensor configurations for normal streaming mode and high
1848 speed streaming, when this scene mode is set/reset in a sequence of capture requests, the
1849 HAL may have to switch between different sensor modes. This mode is deprecated in legacy
1850 HAL3.3, to support high speed video recording, please implement
1851 android.control.availableHighSpeedVideoConfigurations and CONSTRAINED_HIGH_SPEED_VIDEO
1852 capbility defined in android.request.availableCapabilities.
1856 <entry name="videoStabilizationMode" type="byte" visibility="public"
1857 enum="true" hwlevel="legacy">
1861 Video stabilization is disabled.
1865 Video stabilization is enabled.
1868 <description>Whether video stabilization is
1869 active.</description>
1871 Video stabilization automatically warps images from
1872 the camera in order to stabilize motion between consecutive frames.
1874 If enabled, video stabilization can modify the
1875 android.scaler.cropRegion to keep the video stream stabilized.
1877 Switching between different video stabilization modes may take several
1878 frames to initialize, the camera device will report the current mode
1879 in capture result metadata. For example, When "ON" mode is requested,
1880 the video stabilization modes in the first several capture results may
1881 still be "OFF", and it will become "ON" when the initialization is
1884 In addition, not all recording sizes or frame rates may be supported for
1885 stabilization by a device that reports stabilization support. It is guaranteed
1886 that an output targeting a MediaRecorder or MediaCodec will be stabilized if
1887 the recording resolution is less than or equal to 1920 x 1080 (width less than
1888 or equal to 1920, height less than or equal to 1080), and the recording
1889 frame rate is less than or equal to 30fps. At other sizes, the CaptureResult
1890 android.control.videoStabilizationMode field will return
1891 OFF if the recording output is not stabilized, or if there are no output
1892 Surface types that can be stabilized.
1894 If a camera device supports both this mode and OIS
1895 (android.lens.opticalStabilizationMode), turning both modes on may
1896 produce undesirable interaction, so it is recommended not to enable
1897 both at the same time.
1903 <entry name="aeAvailableAntibandingModes" type="byte" visibility="public"
1904 type_notes="list of enums" container="array" typedef="enumList"
1910 List of auto-exposure antibanding modes for android.control.aeAntibandingMode that are
1911 supported by this camera device.
1913 <range>Any value listed in android.control.aeAntibandingMode</range>
1915 Not all of the auto-exposure anti-banding modes may be
1916 supported by a given camera device. This field lists the
1917 valid anti-banding modes that the application may request
1918 for this camera device with the
1919 android.control.aeAntibandingMode control.
1923 <entry name="aeAvailableModes" type="byte" visibility="public"
1924 type_notes="list of enums" container="array" typedef="enumList"
1930 List of auto-exposure modes for android.control.aeMode that are supported by this camera
1933 <range>Any value listed in android.control.aeMode</range>
1935 Not all the auto-exposure modes may be supported by a
1936 given camera device, especially if no flash unit is
1937 available. This entry lists the valid modes for
1938 android.control.aeMode for this camera device.
1940 All camera devices support ON, and all camera devices with flash
1941 units support ON_AUTO_FLASH and ON_ALWAYS_FLASH.
1943 FULL mode camera devices always support OFF mode,
1944 which enables application control of camera exposure time,
1945 sensitivity, and frame duration.
1947 LEGACY mode camera devices never support OFF mode.
1948 LIMITED mode devices support OFF if they support the MANUAL_SENSOR
1953 <entry name="aeAvailableTargetFpsRanges" type="int32" visibility="public"
1954 type_notes="list of pairs of frame rates"
1955 container="array" typedef="rangeInt"
1961 <description>List of frame rate ranges for android.control.aeTargetFpsRange supported by
1962 this camera device.</description>
1963 <units>Frames per second (FPS)</units>
1965 For devices at the LEGACY level or above:
1967 * For constant-framerate recording, for each normal
1968 {@link android.media.CamcorderProfile CamcorderProfile}, that is, a
1969 {@link android.media.CamcorderProfile CamcorderProfile} that has
1970 {@link android.media.CamcorderProfile#quality quality} in
1971 the range [{@link android.media.CamcorderProfile#QUALITY_LOW QUALITY_LOW},
1972 {@link android.media.CamcorderProfile#QUALITY_2160P QUALITY_2160P}], if the profile is
1973 supported by the device and has
1974 {@link android.media.CamcorderProfile#videoFrameRate videoFrameRate} `x`, this list will
1975 always include (`x`,`x`).
1977 * Also, a camera device must either not support any
1978 {@link android.media.CamcorderProfile CamcorderProfile},
1979 or support at least one
1980 normal {@link android.media.CamcorderProfile CamcorderProfile} that has
1981 {@link android.media.CamcorderProfile#videoFrameRate videoFrameRate} `x` >= 24.
1983 For devices at the LIMITED level or above:
1985 * For YUV_420_888 burst capture use case, this list will always include (`min`, `max`)
1986 and (`max`, `max`) where `min` <= 15 and `max` = the maximum output frame rate of the
1987 maximum YUV_420_888 output size.
1991 <entry name="aeCompensationRange" type="int32" visibility="public"
1992 container="array" typedef="rangeInt"
1997 <description>Maximum and minimum exposure compensation values for
1998 android.control.aeExposureCompensation, in counts of android.control.aeCompensationStep,
1999 that are supported by this camera device.</description>
2001 Range [0,0] indicates that exposure compensation is not supported.
2003 For LIMITED and FULL devices, range must follow below requirements if exposure
2004 compensation is supported (`range != [0, 0]`):
2006 `Min.exposure compensation * android.control.aeCompensationStep <= -2 EV`
2008 `Max.exposure compensation * android.control.aeCompensationStep >= 2 EV`
2010 LEGACY devices may support a smaller range than this.
2014 <entry name="aeCompensationStep" type="rational" visibility="public"
2016 <description>Smallest step by which the exposure compensation
2017 can be changed.</description>
2018 <units>Exposure Value (EV)</units>
2020 This is the unit for android.control.aeExposureCompensation. For example, if this key has
2021 a value of `1/2`, then a setting of `-2` for android.control.aeExposureCompensation means
2022 that the target EV offset for the auto-exposure routine is -1 EV.
2024 One unit of EV compensation changes the brightness of the captured image by a factor
2025 of two. +1 EV doubles the image brightness, while -1 EV halves the image brightness.
2028 This must be less than or equal to 1/2.
2032 <entry name="afAvailableModes" type="byte" visibility="public"
2033 type_notes="List of enums" container="array" typedef="enumList"
2039 List of auto-focus (AF) modes for android.control.afMode that are
2040 supported by this camera device.
2042 <range>Any value listed in android.control.afMode</range>
2044 Not all the auto-focus modes may be supported by a
2045 given camera device. This entry lists the valid modes for
2046 android.control.afMode for this camera device.
2048 All LIMITED and FULL mode camera devices will support OFF mode, and all
2049 camera devices with adjustable focuser units
2050 (`android.lens.info.minimumFocusDistance > 0`) will support AUTO mode.
2052 LEGACY devices will support OFF mode only if they support
2053 focusing to infinity (by also setting android.lens.focusDistance to
2058 <entry name="availableEffects" type="byte" visibility="public"
2059 type_notes="List of enums (android.control.effectMode)." container="array"
2060 typedef="enumList" hwlevel="legacy">
2065 List of color effects for android.control.effectMode that are supported by this camera
2068 <range>Any value listed in android.control.effectMode</range>
2070 This list contains the color effect modes that can be applied to
2071 images produced by the camera device.
2072 Implementations are not expected to be consistent across all devices.
2073 If no color effect modes are available for a device, this will only list
2076 A color effect will only be applied if
2077 android.control.mode != OFF. OFF is always included in this list.
2079 This control has no effect on the operation of other control routines such
2080 as auto-exposure, white balance, or focus.
2084 <entry name="availableSceneModes" type="byte" visibility="public"
2085 type_notes="List of enums (android.control.sceneMode)."
2086 container="array" typedef="enumList" hwlevel="legacy">
2091 List of scene modes for android.control.sceneMode that are supported by this camera
2094 <range>Any value listed in android.control.sceneMode</range>
2096 This list contains scene modes that can be set for the camera device.
2097 Only scene modes that have been fully implemented for the
2098 camera device may be included here. Implementations are not expected
2099 to be consistent across all devices.
2101 If no scene modes are supported by the camera device, this
2102 will be set to DISABLED. Otherwise DISABLED will not be listed.
2104 FACE_PRIORITY is always listed if face detection is
2105 supported (i.e.`android.statistics.info.maxFaceCount >
2110 <entry name="availableVideoStabilizationModes" type="byte"
2111 visibility="public" type_notes="List of enums." container="array"
2112 typedef="enumList" hwlevel="legacy">
2117 List of video stabilization modes for android.control.videoStabilizationMode
2118 that are supported by this camera device.
2120 <range>Any value listed in android.control.videoStabilizationMode</range>
2122 OFF will always be listed.
2126 <entry name="awbAvailableModes" type="byte" visibility="public"
2127 type_notes="List of enums"
2128 container="array" typedef="enumList" hwlevel="legacy">
2133 List of auto-white-balance modes for android.control.awbMode that are supported by this
2136 <range>Any value listed in android.control.awbMode</range>
2138 Not all the auto-white-balance modes may be supported by a
2139 given camera device. This entry lists the valid modes for
2140 android.control.awbMode for this camera device.
2142 All camera devices will support ON mode.
2144 Camera devices that support the MANUAL_POST_PROCESSING capability will always support OFF
2145 mode, which enables application control of white balance, by using
2146 android.colorCorrection.transform and android.colorCorrection.gains
2147 (android.colorCorrection.mode must be set to TRANSFORM_MATRIX). This includes all FULL
2148 mode camera devices.
2152 <entry name="maxRegions" type="int32" visibility="ndk_public"
2153 container="array" hwlevel="legacy">
2158 List of the maximum number of regions that can be used for metering in
2159 auto-exposure (AE), auto-white balance (AWB), and auto-focus (AF);
2160 this corresponds to the the maximum number of elements in
2161 android.control.aeRegions, android.control.awbRegions,
2162 and android.control.afRegions.
2165 Value must be &gt;= 0 for each element. For full-capability devices
2166 this value must be &gt;= 1 for AE and AF. The order of the elements is:
2167 `(AE, AWB, AF)`.</range>
2170 <entry name="maxRegionsAe" type="int32" visibility="java_public"
2171 synthetic="true" hwlevel="legacy">
2173 The maximum number of metering regions that can be used by the auto-exposure (AE)
2176 <range>Value will be &gt;= 0. For FULL-capability devices, this
2177 value will be &gt;= 1.
2180 This corresponds to the the maximum allowed number of elements in
2181 android.control.aeRegions.
2183 <hal_details>This entry is private to the framework. Fill in
2184 maxRegions to have this entry be automatically populated.
2187 <entry name="maxRegionsAwb" type="int32" visibility="java_public"
2188 synthetic="true" hwlevel="legacy">
2190 The maximum number of metering regions that can be used by the auto-white balance (AWB)
2193 <range>Value will be &gt;= 0.
2196 This corresponds to the the maximum allowed number of elements in
2197 android.control.awbRegions.
2199 <hal_details>This entry is private to the framework. Fill in
2200 maxRegions to have this entry be automatically populated.
2203 <entry name="maxRegionsAf" type="int32" visibility="java_public"
2204 synthetic="true" hwlevel="legacy">
2206 The maximum number of metering regions that can be used by the auto-focus (AF) routine.
2208 <range>Value will be &gt;= 0. For FULL-capability devices, this
2209 value will be &gt;= 1.
2212 This corresponds to the the maximum allowed number of elements in
2213 android.control.afRegions.
2215 <hal_details>This entry is private to the framework. Fill in
2216 maxRegions to have this entry be automatically populated.
2219 <entry name="sceneModeOverrides" type="byte" visibility="system"
2220 container="array" hwlevel="limited">
2223 <size>length(availableSceneModes)</size>
2226 Ordered list of auto-exposure, auto-white balance, and auto-focus
2227 settings to use with each available scene mode.
2230 For each available scene mode, the list must contain three
2231 entries containing the android.control.aeMode,
2232 android.control.awbMode, and android.control.afMode values used
2233 by the camera device. The entry order is `(aeMode, awbMode, afMode)`
2234 where aeMode has the lowest index position.
2237 When a scene mode is enabled, the camera device is expected
2238 to override android.control.aeMode, android.control.awbMode,
2239 and android.control.afMode with its preferred settings for
2242 The order of this list matches that of availableSceneModes,
2243 with 3 entries for each mode. The overrides listed
2244 for FACE_PRIORITY and FACE_PRIORITY_LOW_LIGHT (if supported) are ignored,
2245 since for that mode the application-set android.control.aeMode,
2246 android.control.awbMode, and android.control.afMode values are
2247 used instead, matching the behavior when android.control.mode
2248 is set to AUTO. It is recommended that the FACE_PRIORITY and
2249 FACE_PRIORITY_LOW_LIGHT (if supported) overrides should be set to 0.
2251 For example, if availableSceneModes contains
2252 `(FACE_PRIORITY, ACTION, NIGHT)`, then the camera framework
2253 expects sceneModeOverrides to have 9 entries formatted like:
2254 `(0, 0, 0, ON_AUTO_FLASH, AUTO, CONTINUOUS_PICTURE,
2255 ON_AUTO_FLASH, INCANDESCENT, AUTO)`.
2258 To maintain backward compatibility, this list will be made available
2259 in the static metadata of the camera service. The camera service will
2260 use these values to set android.control.aeMode,
2261 android.control.awbMode, and android.control.afMode when using a scene
2262 mode other than FACE_PRIORITY and FACE_PRIORITY_LOW_LIGHT (if supported).
2268 <entry name="aePrecaptureId" type="int32" visibility="system" deprecated="true">
2269 <description>The ID sent with the latest
2270 CAMERA2_TRIGGER_PRECAPTURE_METERING call</description>
2271 <deprecation_description>
2272 Removed in camera HAL v3
2273 </deprecation_description>
2274 <details>Must be 0 if no
2275 CAMERA2_TRIGGER_PRECAPTURE_METERING trigger received yet
2276 by HAL. Always updated even if AE algorithm ignores the
2279 <clone entry="android.control.aeAntibandingMode" kind="controls">
2281 <clone entry="android.control.aeExposureCompensation" kind="controls">
2283 <clone entry="android.control.aeLock" kind="controls">
2285 <clone entry="android.control.aeMode" kind="controls">
2287 <clone entry="android.control.aeRegions" kind="controls">
2289 <clone entry="android.control.aeTargetFpsRange" kind="controls">
2291 <clone entry="android.control.aePrecaptureTrigger" kind="controls">
2293 <entry name="aeState" type="byte" visibility="public" enum="true"
2297 <notes>AE is off or recently reset.
2299 When a camera device is opened, it starts in
2300 this state. This is a transient state, the camera device may skip reporting
2301 this state in capture result.</notes></value>
2303 <notes>AE doesn't yet have a good set of control values
2304 for the current scene.
2306 This is a transient state, the camera device may skip
2307 reporting this state in capture result.</notes></value>
2309 <notes>AE has a good set of control values for the
2310 current scene.</notes></value>
2312 <notes>AE has been locked.</notes></value>
2313 <value>FLASH_REQUIRED
2314 <notes>AE has a good set of control values, but flash
2315 needs to be fired for good quality still
2316 capture.</notes></value>
2318 <notes>AE has been asked to do a precapture sequence
2319 and is currently executing it.
2321 Precapture can be triggered through setting
2322 android.control.aePrecaptureTrigger to START. Currently
2323 active and completed (if it causes camera device internal AE lock) precapture
2324 metering sequence can be canceled through setting
2325 android.control.aePrecaptureTrigger to CANCEL.
2327 Once PRECAPTURE completes, AE will transition to CONVERGED
2328 or FLASH_REQUIRED as appropriate. This is a transient
2329 state, the camera device may skip reporting this state in
2330 capture result.</notes></value>
2332 <description>Current state of the auto-exposure (AE) algorithm.</description>
2333 <details>Switching between or enabling AE modes (android.control.aeMode) always
2334 resets the AE state to INACTIVE. Similarly, switching between android.control.mode,
2335 or android.control.sceneMode if `android.control.mode == USE_SCENE_MODE` resets all
2336 the algorithm states to INACTIVE.
2338 The camera device can do several state transitions between two results, if it is
2339 allowed by the state transition table. For example: INACTIVE may never actually be
2342 The state in the result is the state for this image (in sync with this image): if
2343 AE state becomes CONVERGED, then the image data associated with this result should
2346 Below are state transition tables for different AE modes.
2348 State | Transition Cause | New State | Notes
2349 :------------:|:----------------:|:---------:|:-----------------------:
2350 INACTIVE | | INACTIVE | Camera device auto exposure algorithm is disabled
2352 When android.control.aeMode is AE_MODE_ON*:
2354 State | Transition Cause | New State | Notes
2355 :-------------:|:--------------------------------------------:|:--------------:|:-----------------:
2356 INACTIVE | Camera device initiates AE scan | SEARCHING | Values changing
2357 INACTIVE | android.control.aeLock is ON | LOCKED | Values locked
2358 SEARCHING | Camera device finishes AE scan | CONVERGED | Good values, not changing
2359 SEARCHING | Camera device finishes AE scan | FLASH_REQUIRED | Converged but too dark w/o flash
2360 SEARCHING | android.control.aeLock is ON | LOCKED | Values locked
2361 CONVERGED | Camera device initiates AE scan | SEARCHING | Values changing
2362 CONVERGED | android.control.aeLock is ON | LOCKED | Values locked
2363 FLASH_REQUIRED | Camera device initiates AE scan | SEARCHING | Values changing
2364 FLASH_REQUIRED | android.control.aeLock is ON | LOCKED | Values locked
2365 LOCKED | android.control.aeLock is OFF | SEARCHING | Values not good after unlock
2366 LOCKED | android.control.aeLock is OFF | CONVERGED | Values good after unlock
2367 LOCKED | android.control.aeLock is OFF | FLASH_REQUIRED | Exposure good, but too dark
2368 PRECAPTURE | Sequence done. android.control.aeLock is OFF | CONVERGED | Ready for high-quality capture
2369 PRECAPTURE | Sequence done. android.control.aeLock is ON | LOCKED | Ready for high-quality capture
2370 LOCKED | aeLock is ON and aePrecaptureTrigger is START | LOCKED | Precapture trigger is ignored when AE is already locked
2371 LOCKED | aeLock is ON and aePrecaptureTrigger is CANCEL| LOCKED | Precapture trigger is ignored when AE is already locked
2372 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is START | PRECAPTURE | Start AE precapture metering sequence
2373 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is CANCEL| INACTIVE | Currently active precapture metering sequence is canceled
2375 If the camera device supports AE external flash mode (ON_EXTERNAL_FLASH is included in
2376 android.control.aeAvailableModes), android.control.aeState must be FLASH_REQUIRED after
2377 the camera device finishes AE scan and it's too dark without flash.
2379 For the above table, the camera device may skip reporting any state changes that happen
2380 without application intervention (i.e. mode switch, trigger, locking). Any state that
2381 can be skipped in that manner is called a transient state.
2383 For example, for above AE modes (AE_MODE_ON*), in addition to the state transitions
2384 listed in above table, it is also legal for the camera device to skip one or more
2385 transient states between two results. See below table for examples:
2387 State | Transition Cause | New State | Notes
2388 :-------------:|:-----------------------------------------------------------:|:--------------:|:-----------------:
2389 INACTIVE | Camera device finished AE scan | CONVERGED | Values are already good, transient states are skipped by camera device.
2390 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is START, sequence done | FLASH_REQUIRED | Converged but too dark w/o flash after a precapture sequence, transient states are skipped by camera device.
2391 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is START, sequence done | CONVERGED | Converged after a precapture sequence, transient states are skipped by camera device.
2392 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is CANCEL, converged | FLASH_REQUIRED | Converged but too dark w/o flash after a precapture sequence is canceled, transient states are skipped by camera device.
2393 Any state (excluding LOCKED) | android.control.aePrecaptureTrigger is CANCEL, converged | CONVERGED | Converged after a precapture sequenceis canceled, transient states are skipped by camera device.
2394 CONVERGED | Camera device finished AE scan | FLASH_REQUIRED | Converged but too dark w/o flash after a new scan, transient states are skipped by camera device.
2395 FLASH_REQUIRED | Camera device finished AE scan | CONVERGED | Converged after a new scan, transient states are skipped by camera device.
2398 <clone entry="android.control.afMode" kind="controls">
2400 <clone entry="android.control.afRegions" kind="controls">
2402 <clone entry="android.control.afTrigger" kind="controls">
2404 <entry name="afState" type="byte" visibility="public" enum="true"
2408 <notes>AF is off or has not yet tried to scan/been asked
2411 When a camera device is opened, it starts in this
2412 state. This is a transient state, the camera device may
2413 skip reporting this state in capture
2414 result.</notes></value>
2416 <notes>AF is currently performing an AF scan initiated the
2417 camera device in a continuous autofocus mode.
2419 Only used by CONTINUOUS_* AF modes. This is a transient
2420 state, the camera device may skip reporting this state in
2421 capture result.</notes></value>
2422 <value>PASSIVE_FOCUSED
2423 <notes>AF currently believes it is in focus, but may
2424 restart scanning at any time.
2426 Only used by CONTINUOUS_* AF modes. This is a transient
2427 state, the camera device may skip reporting this state in
2428 capture result.</notes></value>
2430 <notes>AF is performing an AF scan because it was
2431 triggered by AF trigger.
2433 Only used by AUTO or MACRO AF modes. This is a transient
2434 state, the camera device may skip reporting this state in
2435 capture result.</notes></value>
2436 <value>FOCUSED_LOCKED
2437 <notes>AF believes it is focused correctly and has locked
2440 This state is reached only after an explicit START AF trigger has been
2441 sent (android.control.afTrigger), when good focus has been obtained.
2443 The lens will remain stationary until the AF mode (android.control.afMode) is changed or
2444 a new AF trigger is sent to the camera device (android.control.afTrigger).
2446 <value>NOT_FOCUSED_LOCKED
2447 <notes>AF has failed to focus successfully and has locked
2450 This state is reached only after an explicit START AF trigger has been
2451 sent (android.control.afTrigger), when good focus cannot be obtained.
2453 The lens will remain stationary until the AF mode (android.control.afMode) is changed or
2454 a new AF trigger is sent to the camera device (android.control.afTrigger).
2456 <value>PASSIVE_UNFOCUSED
2457 <notes>AF finished a passive scan without finding focus,
2458 and may restart scanning at any time.
2460 Only used by CONTINUOUS_* AF modes. This is a transient state, the camera
2461 device may skip reporting this state in capture result.
2463 LEGACY camera devices do not support this state. When a passive
2464 scan has finished, it will always go to PASSIVE_FOCUSED.
2467 <description>Current state of auto-focus (AF) algorithm.</description>
2469 Switching between or enabling AF modes (android.control.afMode) always
2470 resets the AF state to INACTIVE. Similarly, switching between android.control.mode,
2471 or android.control.sceneMode if `android.control.mode == USE_SCENE_MODE` resets all
2472 the algorithm states to INACTIVE.
2474 The camera device can do several state transitions between two results, if it is
2475 allowed by the state transition table. For example: INACTIVE may never actually be
2478 The state in the result is the state for this image (in sync with this image): if
2479 AF state becomes FOCUSED, then the image data associated with this result should
2482 Below are state transition tables for different AF modes.
2484 When android.control.afMode is AF_MODE_OFF or AF_MODE_EDOF:
2486 State | Transition Cause | New State | Notes
2487 :------------:|:----------------:|:---------:|:-----------:
2488 INACTIVE | | INACTIVE | Never changes
2490 When android.control.afMode is AF_MODE_AUTO or AF_MODE_MACRO:
2492 State | Transition Cause | New State | Notes
2493 :-----------------:|:----------------:|:------------------:|:--------------:
2494 INACTIVE | AF_TRIGGER | ACTIVE_SCAN | Start AF sweep, Lens now moving
2495 ACTIVE_SCAN | AF sweep done | FOCUSED_LOCKED | Focused, Lens now locked
2496 ACTIVE_SCAN | AF sweep done | NOT_FOCUSED_LOCKED | Not focused, Lens now locked
2497 ACTIVE_SCAN | AF_CANCEL | INACTIVE | Cancel/reset AF, Lens now locked
2498 FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Cancel/reset AF
2499 FOCUSED_LOCKED | AF_TRIGGER | ACTIVE_SCAN | Start new sweep, Lens now moving
2500 NOT_FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Cancel/reset AF
2501 NOT_FOCUSED_LOCKED | AF_TRIGGER | ACTIVE_SCAN | Start new sweep, Lens now moving
2502 Any state | Mode change | INACTIVE |
2504 For the above table, the camera device may skip reporting any state changes that happen
2505 without application intervention (i.e. mode switch, trigger, locking). Any state that
2506 can be skipped in that manner is called a transient state.
2508 For example, for these AF modes (AF_MODE_AUTO and AF_MODE_MACRO), in addition to the
2509 state transitions listed in above table, it is also legal for the camera device to skip
2510 one or more transient states between two results. See below table for examples:
2512 State | Transition Cause | New State | Notes
2513 :-----------------:|:----------------:|:------------------:|:--------------:
2514 INACTIVE | AF_TRIGGER | FOCUSED_LOCKED | Focus is already good or good after a scan, lens is now locked.
2515 INACTIVE | AF_TRIGGER | NOT_FOCUSED_LOCKED | Focus failed after a scan, lens is now locked.
2516 FOCUSED_LOCKED | AF_TRIGGER | FOCUSED_LOCKED | Focus is already good or good after a scan, lens is now locked.
2517 NOT_FOCUSED_LOCKED | AF_TRIGGER | FOCUSED_LOCKED | Focus is good after a scan, lens is not locked.
2520 When android.control.afMode is AF_MODE_CONTINUOUS_VIDEO:
2522 State | Transition Cause | New State | Notes
2523 :-----------------:|:-----------------------------------:|:------------------:|:--------------:
2524 INACTIVE | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2525 INACTIVE | AF_TRIGGER | NOT_FOCUSED_LOCKED | AF state query, Lens now locked
2526 PASSIVE_SCAN | Camera device completes current scan| PASSIVE_FOCUSED | End AF scan, Lens now locked
2527 PASSIVE_SCAN | Camera device fails current scan | PASSIVE_UNFOCUSED | End AF scan, Lens now locked
2528 PASSIVE_SCAN | AF_TRIGGER | FOCUSED_LOCKED | Immediate transition, if focus is good. Lens now locked
2529 PASSIVE_SCAN | AF_TRIGGER | NOT_FOCUSED_LOCKED | Immediate transition, if focus is bad. Lens now locked
2530 PASSIVE_SCAN | AF_CANCEL | INACTIVE | Reset lens position, Lens now locked
2531 PASSIVE_FOCUSED | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2532 PASSIVE_UNFOCUSED | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2533 PASSIVE_FOCUSED | AF_TRIGGER | FOCUSED_LOCKED | Immediate transition, lens now locked
2534 PASSIVE_UNFOCUSED | AF_TRIGGER | NOT_FOCUSED_LOCKED | Immediate transition, lens now locked
2535 FOCUSED_LOCKED | AF_TRIGGER | FOCUSED_LOCKED | No effect
2536 FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Restart AF scan
2537 NOT_FOCUSED_LOCKED | AF_TRIGGER | NOT_FOCUSED_LOCKED | No effect
2538 NOT_FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Restart AF scan
2540 When android.control.afMode is AF_MODE_CONTINUOUS_PICTURE:
2542 State | Transition Cause | New State | Notes
2543 :-----------------:|:------------------------------------:|:------------------:|:--------------:
2544 INACTIVE | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2545 INACTIVE | AF_TRIGGER | NOT_FOCUSED_LOCKED | AF state query, Lens now locked
2546 PASSIVE_SCAN | Camera device completes current scan | PASSIVE_FOCUSED | End AF scan, Lens now locked
2547 PASSIVE_SCAN | Camera device fails current scan | PASSIVE_UNFOCUSED | End AF scan, Lens now locked
2548 PASSIVE_SCAN | AF_TRIGGER | FOCUSED_LOCKED | Eventual transition once the focus is good. Lens now locked
2549 PASSIVE_SCAN | AF_TRIGGER | NOT_FOCUSED_LOCKED | Eventual transition if cannot find focus. Lens now locked
2550 PASSIVE_SCAN | AF_CANCEL | INACTIVE | Reset lens position, Lens now locked
2551 PASSIVE_FOCUSED | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2552 PASSIVE_UNFOCUSED | Camera device initiates new scan | PASSIVE_SCAN | Start AF scan, Lens now moving
2553 PASSIVE_FOCUSED | AF_TRIGGER | FOCUSED_LOCKED | Immediate trans. Lens now locked
2554 PASSIVE_UNFOCUSED | AF_TRIGGER | NOT_FOCUSED_LOCKED | Immediate trans. Lens now locked
2555 FOCUSED_LOCKED | AF_TRIGGER | FOCUSED_LOCKED | No effect
2556 FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Restart AF scan
2557 NOT_FOCUSED_LOCKED | AF_TRIGGER | NOT_FOCUSED_LOCKED | No effect
2558 NOT_FOCUSED_LOCKED | AF_CANCEL | INACTIVE | Restart AF scan
2560 When switch between AF_MODE_CONTINUOUS_* (CAF modes) and AF_MODE_AUTO/AF_MODE_MACRO
2561 (AUTO modes), the initial INACTIVE or PASSIVE_SCAN states may be skipped by the
2562 camera device. When a trigger is included in a mode switch request, the trigger
2563 will be evaluated in the context of the new mode in the request.
2564 See below table for examples:
2566 State | Transition Cause | New State | Notes
2567 :-----------:|:--------------------------------------:|:----------------------------------------:|:--------------:
2568 any state | CAF-->AUTO mode switch | INACTIVE | Mode switch without trigger, initial state must be INACTIVE
2569 any state | CAF-->AUTO mode switch with AF_TRIGGER | trigger-reachable states from INACTIVE | Mode switch with trigger, INACTIVE is skipped
2570 any state | AUTO-->CAF mode switch | passively reachable states from INACTIVE | Mode switch without trigger, passive transient state is skipped
2573 <entry name="afTriggerId" type="int32" visibility="system" deprecated="true">
2574 <description>The ID sent with the latest
2575 CAMERA2_TRIGGER_AUTOFOCUS call</description>
2576 <deprecation_description>
2577 Removed in camera HAL v3
2578 </deprecation_description>
2579 <details>Must be 0 if no CAMERA2_TRIGGER_AUTOFOCUS trigger
2580 received yet by HAL. Always updated even if AF algorithm
2581 ignores the trigger</details>
2583 <clone entry="android.control.awbLock" kind="controls">
2585 <clone entry="android.control.awbMode" kind="controls">
2587 <clone entry="android.control.awbRegions" kind="controls">
2589 <clone entry="android.control.captureIntent" kind="controls">
2591 <entry name="awbState" type="byte" visibility="public" enum="true"
2595 <notes>AWB is not in auto mode, or has not yet started metering.
2597 When a camera device is opened, it starts in this
2598 state. This is a transient state, the camera device may
2599 skip reporting this state in capture
2600 result.</notes></value>
2602 <notes>AWB doesn't yet have a good set of control
2603 values for the current scene.
2605 This is a transient state, the camera device
2606 may skip reporting this state in capture result.</notes></value>
2608 <notes>AWB has a good set of control values for the
2609 current scene.</notes></value>
2611 <notes>AWB has been locked.
2614 <description>Current state of auto-white balance (AWB) algorithm.</description>
2615 <details>Switching between or enabling AWB modes (android.control.awbMode) always
2616 resets the AWB state to INACTIVE. Similarly, switching between android.control.mode,
2617 or android.control.sceneMode if `android.control.mode == USE_SCENE_MODE` resets all
2618 the algorithm states to INACTIVE.
2620 The camera device can do several state transitions between two results, if it is
2621 allowed by the state transition table. So INACTIVE may never actually be seen in
2624 The state in the result is the state for this image (in sync with this image): if
2625 AWB state becomes CONVERGED, then the image data associated with this result should
2628 Below are state transition tables for different AWB modes.
2630 When `android.control.awbMode != AWB_MODE_AUTO`:
2632 State | Transition Cause | New State | Notes
2633 :------------:|:----------------:|:---------:|:-----------------------:
2634 INACTIVE | |INACTIVE |Camera device auto white balance algorithm is disabled
2636 When android.control.awbMode is AWB_MODE_AUTO:
2638 State | Transition Cause | New State | Notes
2639 :-------------:|:--------------------------------:|:-------------:|:-----------------:
2640 INACTIVE | Camera device initiates AWB scan | SEARCHING | Values changing
2641 INACTIVE | android.control.awbLock is ON | LOCKED | Values locked
2642 SEARCHING | Camera device finishes AWB scan | CONVERGED | Good values, not changing
2643 SEARCHING | android.control.awbLock is ON | LOCKED | Values locked
2644 CONVERGED | Camera device initiates AWB scan | SEARCHING | Values changing
2645 CONVERGED | android.control.awbLock is ON | LOCKED | Values locked
2646 LOCKED | android.control.awbLock is OFF | SEARCHING | Values not good after unlock
2648 For the above table, the camera device may skip reporting any state changes that happen
2649 without application intervention (i.e. mode switch, trigger, locking). Any state that
2650 can be skipped in that manner is called a transient state.
2652 For example, for this AWB mode (AWB_MODE_AUTO), in addition to the state transitions
2653 listed in above table, it is also legal for the camera device to skip one or more
2654 transient states between two results. See below table for examples:
2656 State | Transition Cause | New State | Notes
2657 :-------------:|:--------------------------------:|:-------------:|:-----------------:
2658 INACTIVE | Camera device finished AWB scan | CONVERGED | Values are already good, transient states are skipped by camera device.
2659 LOCKED | android.control.awbLock is OFF | CONVERGED | Values good after unlock, transient states are skipped by camera device.
2662 <clone entry="android.control.effectMode" kind="controls">
2664 <clone entry="android.control.mode" kind="controls">
2666 <clone entry="android.control.sceneMode" kind="controls">
2668 <clone entry="android.control.videoStabilizationMode" kind="controls">
2672 <entry name="availableHighSpeedVideoConfigurations" type="int32" visibility="hidden"
2673 container="array" typedef="highSpeedVideoConfiguration" hwlevel="limited">
2679 List of available high speed video size, fps range and max batch size configurations
2680 supported by the camera device, in the format of (width, height, fps_min, fps_max, batch_size_max).
2683 For each configuration, the fps_max &gt;= 120fps.
2686 When CONSTRAINED_HIGH_SPEED_VIDEO is supported in android.request.availableCapabilities,
2687 this metadata will list the supported high speed video size, fps range and max batch size
2688 configurations. All the sizes listed in this configuration will be a subset of the sizes
2689 reported by {@link android.hardware.camera2.params.StreamConfigurationMap#getOutputSizes}
2690 for processed non-stalling formats.
2692 For the high speed video use case, the application must
2693 select the video size and fps range from this metadata to configure the recording and
2694 preview streams and setup the recording requests. For example, if the application intends
2695 to do high speed recording, it can select the maximum size reported by this metadata to
2696 configure output streams. Once the size is selected, application can filter this metadata
2697 by selected size and get the supported fps ranges, and use these fps ranges to setup the
2698 recording requests. Note that for the use case of multiple output streams, application
2699 must select one unique size from this metadata to use (e.g., preview and recording streams
2700 must have the same size). Otherwise, the high speed capture session creation will fail.
2702 The min and max fps will be multiple times of 30fps.
2704 High speed video streaming extends significant performance pressue to camera hardware,
2705 to achieve efficient high speed streaming, the camera device may have to aggregate
2706 multiple frames together and send to camera device for processing where the request
2707 controls are same for all the frames in this batch. Max batch size indicates
2708 the max possible number of frames the camera device will group together for this high
2709 speed stream configuration. This max batch size will be used to generate a high speed
2710 recording request list by
2711 {@link android.hardware.camera2.CameraConstrainedHighSpeedCaptureSession#createHighSpeedRequestList}.
2712 The max batch size for each configuration will satisfy below conditions:
2714 * Each max batch size will be a divisor of its corresponding fps_max / 30. For example,
2715 if max_fps is 300, max batch size will only be 1, 2, 5, or 10.
2716 * The camera device may choose smaller internal batch size for each configuration, but
2717 the actual batch size will be a divisor of max batch size. For example, if the max batch
2718 size is 8, the actual batch size used by camera device will only be 1, 2, 4, or 8.
2719 * The max batch size in each configuration entry must be no larger than 32.
2721 The camera device doesn't have to support batch mode to achieve high speed video recording,
2722 in such case, batch_size_max will be reported as 1 in each configuration entry.
2724 This fps ranges in this configuration list can only be used to create requests
2725 that are submitted to a high speed camera capture session created by
2726 {@link android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}.
2727 The fps ranges reported in this metadata must not be used to setup capture requests for
2728 normal capture session, or it will cause request error.
2731 All the sizes listed in this configuration will be a subset of the sizes reported by
2732 android.scaler.availableStreamConfigurations for processed non-stalling output formats.
2733 Note that for all high speed video configurations, HAL must be able to support a minimum
2734 of two streams, though the application might choose to configure just one stream.
2736 The HAL may support multiple sensor modes for high speed outputs, for example, 120fps
2737 sensor mode and 120fps recording, 240fps sensor mode for 240fps recording. The application
2738 usually starts preview first, then starts recording. To avoid sensor mode switch caused
2739 stutter when starting recording as much as possible, the application may want to ensure
2740 the same sensor mode is used for preview and recording. Therefore, The HAL must advertise
2741 the variable fps range [30, fps_max] for each fixed fps range in this configuration list.
2742 For example, if the HAL advertises [120, 120] and [240, 240], the HAL must also advertise
2743 [30, 120] and [30, 240] for each configuration. In doing so, if the application intends to
2744 do 120fps recording, it can select [30, 120] to start preview, and [120, 120] to start
2745 recording. For these variable fps ranges, it's up to the HAL to decide the actual fps
2746 values that are suitable for smooth preview streaming. If the HAL sees different max_fps
2747 values that fall into different sensor modes in a sequence of requests, the HAL must
2748 switch the sensor mode as quick as possible to minimize the mode switch caused stutter.
2752 <entry name="aeLockAvailable" type="byte" visibility="public" enum="true"
2753 typedef="boolean" hwlevel="legacy">
2755 <value>FALSE</value>
2758 <description>Whether the camera device supports android.control.aeLock</description>
2760 Devices with MANUAL_SENSOR capability or BURST_CAPTURE capability will always
2761 list `true`. This includes FULL devices.
2765 <entry name="awbLockAvailable" type="byte" visibility="public" enum="true"
2766 typedef="boolean" hwlevel="legacy">
2768 <value>FALSE</value>
2771 <description>Whether the camera device supports android.control.awbLock</description>
2773 Devices with MANUAL_POST_PROCESSING capability or BURST_CAPTURE capability will
2774 always list `true`. This includes FULL devices.
2778 <entry name="availableModes" type="byte" visibility="public"
2779 type_notes="List of enums (android.control.mode)." container="array"
2780 typedef="enumList" hwlevel="legacy">
2785 List of control modes for android.control.mode that are supported by this camera
2788 <range>Any value listed in android.control.mode</range>
2790 This list contains control modes that can be set for the camera device.
2791 LEGACY mode devices will always support AUTO mode. LIMITED and FULL
2792 devices will always support OFF, AUTO modes.
2795 <entry name="postRawSensitivityBoostRange" type="int32" visibility="public"
2796 type_notes="Range of supported post RAW sensitivitiy boosts"
2797 container="array" typedef="rangeInt">
2801 <description>Range of boosts for android.control.postRawSensitivityBoost supported
2802 by this camera device.
2804 <units>ISO arithmetic units, the same as android.sensor.sensitivity</units>
2806 Devices support post RAW sensitivity boost will advertise
2807 android.control.postRawSensitivityBoost key for controling
2808 post RAW sensitivity boost.
2810 This key will be `null` for devices that do not support any RAW format
2811 outputs. For devices that do support RAW format outputs, this key will always
2812 present, and if a device does not support post RAW sensitivity boost, it will
2813 list `(100, 100)` in this key.
2816 This key is added in legacy HAL3.4. For legacy HAL3.3 or earlier devices, camera
2817 framework will generate this key as `(100, 100)` if device supports any of RAW output
2818 formats. All legacy HAL3.4 and above devices should list this key if device supports
2819 any of RAW output formats.
2824 <entry name="postRawSensitivityBoost" type="int32" visibility="public">
2825 <description>The amount of additional sensitivity boost applied to output images
2826 after RAW sensor data is captured.
2828 <units>ISO arithmetic units, the same as android.sensor.sensitivity</units>
2829 <range>android.control.postRawSensitivityBoostRange</range>
2831 Some camera devices support additional digital sensitivity boosting in the
2832 camera processing pipeline after sensor RAW image is captured.
2833 Such a boost will be applied to YUV/JPEG format output images but will not
2834 have effect on RAW output formats like RAW_SENSOR, RAW10, RAW12 or RAW_OPAQUE.
2836 This key will be `null` for devices that do not support any RAW format
2837 outputs. For devices that do support RAW format outputs, this key will always
2838 present, and if a device does not support post RAW sensitivity boost, it will
2839 list `100` in this key.
2841 If the camera device cannot apply the exact boost requested, it will reduce the
2842 boost to the nearest supported value.
2843 The final boost value used will be available in the output capture result.
2845 For devices that support post RAW sensitivity boost, the YUV/JPEG output images
2846 of such device will have the total sensitivity of
2847 `android.sensor.sensitivity * android.control.postRawSensitivityBoost / 100`
2848 The sensitivity of RAW format images will always be `android.sensor.sensitivity`
2850 This control is only effective if android.control.aeMode or android.control.mode is set to
2851 OFF; otherwise the auto-exposure algorithm will override this value.
2856 <clone entry="android.control.postRawSensitivityBoost" kind="controls">
2860 <entry name="enableZsl" type="byte" visibility="public" enum="true" typedef="boolean">
2863 <notes>Requests with android.control.captureIntent == STILL_CAPTURE must be captured
2864 after previous requests.</notes></value>
2866 <notes>Requests with android.control.captureIntent == STILL_CAPTURE may or may not be
2867 captured before previous requests.</notes></value>
2869 <description>Allow camera device to enable zero-shutter-lag mode for requests with
2870 android.control.captureIntent == STILL_CAPTURE.
2873 If enableZsl is `true`, the camera device may enable zero-shutter-lag mode for requests with
2874 STILL_CAPTURE capture intent. The camera device may use images captured in the past to
2875 produce output images for a zero-shutter-lag request. The result metadata including the
2876 android.sensor.timestamp reflects the source frames used to produce output images.
2877 Therefore, the contents of the output images and the result metadata may be out of order
2878 compared to previous regular requests. enableZsl does not affect requests with other
2881 For example, when requests are submitted in the following order:
2882 Request A: enableZsl is ON, android.control.captureIntent is PREVIEW
2883 Request B: enableZsl is ON, android.control.captureIntent is STILL_CAPTURE
2885 The output images for request B may have contents captured before the output images for
2886 request A, and the result metadata for request B may be older than the result metadata for
2889 Note that when enableZsl is `true`, it is not guaranteed to get output images captured in
2890 the past for requests with STILL_CAPTURE capture intent.
2892 For applications targeting SDK versions O and newer, the value of enableZsl in
2893 TEMPLATE_STILL_CAPTURE template may be `true`. The value in other templates is always
2896 For applications targeting SDK versions older than O, the value of enableZsl in all
2897 capture templates is always `false` if present.
2899 For application-operated ZSL, use CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template.
2902 It is valid for HAL to produce regular output images for requests with STILL_CAPTURE
2908 <clone entry="android.control.enableZsl" kind="controls">
2910 <entry name="afSceneChange" type="byte" visibility="public" enum="true" hal_version="3.3">
2913 <notes>Scene change is not detected within the AF region(s).</notes></value>
2915 <notes>Scene change is detected within the AF region(s).</notes></value>
2917 <description>Whether a significant scene change is detected within the currently-set AF
2918 region(s).</description>
2919 <details>When the camera focus routine detects a change in the scene it is looking at,
2920 such as a large shift in camera viewpoint, significant motion in the scene, or a
2921 significant illumination change, this value will be set to DETECTED for a single capture
2922 result. Otherwise the value will be NOT_DETECTED. The threshold for detection is similar
2923 to what would trigger a new passive focus scan to begin in CONTINUOUS autofocus modes.
2925 This key will be available if the camera device advertises this key via {@link
2926 android.hardware.camera2.CameraCharacteristics#getAvailableCaptureResultKeys|ACAMERA_REQUEST_AVAILABLE_RESULT_KEYS}.
2931 <section name="demosaic">
2933 <entry name="mode" type="byte" enum="true">
2936 <notes>Minimal or no slowdown of frame rate compared to
2937 Bayer RAW output.</notes></value>
2939 <notes>Improved processing quality but the frame rate might be slowed down
2940 relative to raw output.</notes></value>
2942 <description>Controls the quality of the demosaicing
2943 processing.</description>
2948 <section name="edge">
2950 <entry name="mode" type="byte" visibility="public" enum="true" hwlevel="full">
2953 <notes>No edge enhancement is applied.</notes></value>
2955 <notes>Apply edge enhancement at a quality level that does not slow down frame rate
2956 relative to sensor output. It may be the same as OFF if edge enhancement will
2957 slow down frame rate relative to sensor.</notes></value>
2959 <notes>Apply high-quality edge enhancement, at a cost of possibly reduced output frame rate.
2961 <value optional="true">ZERO_SHUTTER_LAG <notes>Edge enhancement is applied at different
2962 levels for different output streams, based on resolution. Streams at maximum recording
2963 resolution (see {@link
2964 android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession})
2965 or below have edge enhancement applied, while higher-resolution streams have no edge
2966 enhancement applied. The level of edge enhancement for low-resolution streams is tuned
2967 so that frame rate is not impacted, and the quality is equal to or better than FAST
2968 (since it is only applied to lower-resolution outputs, quality may improve from FAST).
2970 This mode is intended to be used by applications operating in a zero-shutter-lag mode
2971 with YUV or PRIVATE reprocessing, where the application continuously captures
2972 high-resolution intermediate buffers into a circular buffer, from which a final image is
2973 produced via reprocessing when a user takes a picture. For such a use case, the
2974 high-resolution buffers must not have edge enhancement applied to maximize efficiency of
2975 preview and to avoid double-applying enhancement when reprocessed, while low-resolution
2976 buffers (used for recording or preview, generally) need edge enhancement applied for
2977 reasonable preview quality.
2979 This mode is guaranteed to be supported by devices that support either the
2980 YUV_REPROCESSING or PRIVATE_REPROCESSING capabilities
2981 (android.request.availableCapabilities lists either of those capabilities) and it will
2982 be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template.
2985 <description>Operation mode for edge
2986 enhancement.</description>
2987 <range>android.edge.availableEdgeModes</range>
2988 <details>Edge enhancement improves sharpness and details in the captured image. OFF means
2989 no enhancement will be applied by the camera device.
2991 FAST/HIGH_QUALITY both mean camera device determined enhancement
2992 will be applied. HIGH_QUALITY mode indicates that the
2993 camera device will use the highest-quality enhancement algorithms,
2994 even if it slows down capture rate. FAST means the camera device will
2995 not slow down capture rate when applying edge enhancement. FAST may be the same as OFF if
2996 edge enhancement will slow down capture rate. Every output stream will have a similar
2997 amount of enhancement applied.
2999 ZERO_SHUTTER_LAG is meant to be used by applications that maintain a continuous circular
3000 buffer of high-resolution images during preview and reprocess image(s) from that buffer
3001 into a final capture when triggered by the user. In this mode, the camera device applies
3002 edge enhancement to low-resolution streams (below maximum recording resolution) to
3003 maximize preview quality, but does not apply edge enhancement to high-resolution streams,
3004 since those will be reprocessed later if necessary.
3006 For YUV_REPROCESSING, these FAST/HIGH_QUALITY modes both mean that the camera
3007 device will apply FAST/HIGH_QUALITY YUV-domain edge enhancement, respectively.
3008 The camera device may adjust its internal edge enhancement parameters for best
3009 image quality based on the android.reprocess.effectiveExposureFactor, if it is set.
3012 For YUV_REPROCESSING The HAL can use android.reprocess.effectiveExposureFactor to
3013 adjust the internal edge enhancement reduction parameters appropriately to get the best
3019 <entry name="strength" type="byte">
3020 <description>Control the amount of edge enhancement
3021 applied to the images</description>
3022 <units>1-10; 10 is maximum sharpening</units>
3027 <entry name="availableEdgeModes" type="byte" visibility="public"
3028 type_notes="list of enums" container="array" typedef="enumList"
3034 List of edge enhancement modes for android.edge.mode that are supported by this camera
3037 <range>Any value listed in android.edge.mode</range>
3039 Full-capability camera devices must always support OFF; camera devices that support
3040 YUV_REPROCESSING or PRIVATE_REPROCESSING will list ZERO_SHUTTER_LAG; all devices will
3044 HAL must support both FAST and HIGH_QUALITY if edge enhancement control is available
3045 on the camera device, but the underlying implementation can be the same for both modes.
3046 That is, if the highest quality implementation on the camera device does not slow down
3047 capture rate, then FAST and HIGH_QUALITY will generate the same output.
3054 <clone entry="android.edge.mode" kind="controls">
3060 <section name="flash">
3062 <entry name="firingPower" type="byte">
3063 <description>Power for flash firing/torch</description>
3064 <units>10 is max power; 0 is no flash. Linear</units>
3065 <range>0 - 10</range>
3066 <details>Power for snapshot may use a different scale than
3067 for torch mode. Only one entry for torch mode will be
3071 <entry name="firingTime" type="int64">
3072 <description>Firing time of flash relative to start of
3073 exposure</description>
3074 <units>nanoseconds</units>
3075 <range>0-(exposure time-flash duration)</range>
3076 <details>Clamped to (0, exposure time - flash
3077 duration).</details>
3080 <entry name="mode" type="byte" visibility="public" enum="true" hwlevel="legacy">
3084 Do not fire the flash for this capture.
3089 If the flash is available and charged, fire flash
3095 Transition flash to continuously on.
3099 <description>The desired mode for for the camera device's flash control.</description>
3101 This control is only effective when flash unit is available
3102 (`android.flash.info.available == true`).
3104 When this control is used, the android.control.aeMode must be set to ON or OFF.
3105 Otherwise, the camera device auto-exposure related flash control (ON_AUTO_FLASH,
3106 ON_ALWAYS_FLASH, or ON_AUTO_FLASH_REDEYE) will override this control.
3108 When set to OFF, the camera device will not fire flash for this capture.
3110 When set to SINGLE, the camera device will fire flash regardless of the camera
3111 device's auto-exposure routine's result. When used in still capture case, this
3112 control should be used along with auto-exposure (AE) precapture metering sequence
3113 (android.control.aePrecaptureTrigger), otherwise, the image may be incorrectly exposed.
3115 When set to TORCH, the flash will be on continuously. This mode can be used
3116 for use cases such as preview, auto-focus assist, still capture, or video recording.
3118 The flash status will be reported by android.flash.state in the capture result metadata.
3124 <namespace name="info">
3125 <entry name="available" type="byte" visibility="public" enum="true"
3126 typedef="boolean" hwlevel="legacy">
3128 <value>FALSE</value>
3131 <description>Whether this camera device has a
3132 flash unit.</description>
3134 Will be `false` if no flash is available.
3136 If there is no flash unit, none of the flash controls do
3140 <entry name="chargeDuration" type="int64">
3141 <description>Time taken before flash can fire
3143 <units>nanoseconds</units>
3144 <range>0-1e9</range>
3145 <details>1 second too long/too short for recharge? Should
3146 this be power-dependent?</details>
3150 <entry name="colorTemperature" type="byte">
3151 <description>The x,y whitepoint of the
3153 <units>pair of floats</units>
3154 <range>0-1 for both</range>
3157 <entry name="maxEnergy" type="byte">
3158 <description>Max energy output of the flash for a full
3159 power single flash</description>
3160 <units>lumen-seconds</units>
3161 <range>&gt;= 0</range>
3166 <clone entry="android.flash.firingPower" kind="controls">
3168 <clone entry="android.flash.firingTime" kind="controls">
3170 <clone entry="android.flash.mode" kind="controls"></clone>
3171 <entry name="state" type="byte" visibility="public" enum="true"
3175 <notes>No flash on camera.</notes></value>
3177 <notes>Flash is charging and cannot be fired.</notes></value>
3179 <notes>Flash is ready to fire.</notes></value>
3181 <notes>Flash fired for this capture.</notes></value>
3183 <notes>Flash partially illuminated this frame.
3185 This is usually due to the next or previous frame having
3186 the flash fire, and the flash spilling into this capture
3187 due to hardware limitations.</notes></value>
3189 <description>Current state of the flash
3192 When the camera device doesn't have flash unit
3193 (i.e. `android.flash.info.available == false`), this state will always be UNAVAILABLE.
3194 Other states indicate the current flash status.
3196 In certain conditions, this will be available on LEGACY devices:
3198 * Flash-less cameras always return UNAVAILABLE.
3199 * Using android.control.aeMode `==` ON_ALWAYS_FLASH
3200 will always return FIRED.
3201 * Using android.flash.mode `==` TORCH
3202 will always return FIRED.
3204 In all other conditions the state will not be available on
3205 LEGACY devices (i.e. it will be `null`).
3210 <section name="hotPixel">
3212 <entry name="mode" type="byte" visibility="public" enum="true">
3216 No hot pixel correction is applied.
3218 The frame rate must not be reduced relative to sensor raw output
3221 The hotpixel map may be returned in android.statistics.hotPixelMap.
3226 Hot pixel correction is applied, without reducing frame
3227 rate relative to sensor raw output.
3229 The hotpixel map may be returned in android.statistics.hotPixelMap.
3234 High-quality hot pixel correction is applied, at a cost
3235 of possibly reduced frame rate relative to sensor raw output.
3237 The hotpixel map may be returned in android.statistics.hotPixelMap.
3242 Operational mode for hot pixel correction.
3244 <range>android.hotPixel.availableHotPixelModes</range>
3246 Hotpixel correction interpolates out, or otherwise removes, pixels
3247 that do not accurately measure the incoming light (i.e. pixels that
3248 are stuck at an arbitrary value or are oversensitive).
3255 <entry name="availableHotPixelModes" type="byte" visibility="public"
3256 type_notes="list of enums" container="array" typedef="enumList">
3261 List of hot pixel correction modes for android.hotPixel.mode that are supported by this
3264 <range>Any value listed in android.hotPixel.mode</range>
3266 FULL mode camera devices will always support FAST.
3269 To avoid performance issues, there will be significantly fewer hot
3270 pixels than actual pixels on the camera sensor.
3271 HAL must support both FAST and HIGH_QUALITY if hot pixel correction control is available
3272 on the camera device, but the underlying implementation can be the same for both modes.
3273 That is, if the highest quality implementation on the camera device does not slow down
3274 capture rate, then FAST and HIGH_QUALITY will generate the same output.
3281 <clone entry="android.hotPixel.mode" kind="controls">
3287 <section name="jpeg">
3289 <entry name="gpsLocation" type="byte" visibility="java_public" synthetic="true"
3290 typedef="location" hwlevel="legacy">
3292 A location object to use when generating image GPS metadata.
3295 Setting a location object in a request will include the GPS coordinates of the location
3296 into any JPEG images captured based on the request. These coordinates can then be
3297 viewed by anyone who receives the JPEG image.
3300 <entry name="gpsCoordinates" type="double" visibility="ndk_public"
3301 type_notes="latitude, longitude, altitude. First two in degrees, the third in meters"
3302 container="array" hwlevel="legacy">
3306 <description>GPS coordinates to include in output JPEG
3308 <range>(-180 - 180], [-90,90], [-inf, inf]</range>
3311 <entry name="gpsProcessingMethod" type="byte" visibility="ndk_public"
3312 typedef="string" hwlevel="legacy">
3313 <description>32 characters describing GPS algorithm to
3314 include in EXIF.</description>
3315 <units>UTF-8 null-terminated string</units>
3318 <entry name="gpsTimestamp" type="int64" visibility="ndk_public" hwlevel="legacy">
3319 <description>Time GPS fix was made to include in
3321 <units>UTC in seconds since January 1, 1970</units>
3324 <entry name="orientation" type="int32" visibility="public" hwlevel="legacy">
3325 <description>The orientation for a JPEG image.</description>
3326 <units>Degrees in multiples of 90</units>
3327 <range>0, 90, 180, 270</range>
3329 The clockwise rotation angle in degrees, relative to the orientation
3330 to the camera, that the JPEG picture needs to be rotated by, to be viewed
3333 Camera devices may either encode this value into the JPEG EXIF header, or
3334 rotate the image data to match this orientation. When the image data is rotated,
3335 the thumbnail data will also be rotated.
3337 Note that this orientation is relative to the orientation of the camera sensor, given
3338 by android.sensor.orientation.
3340 To translate from the device orientation given by the Android sensor APIs, the following
3341 sample code may be used:
3343 private int getJpegOrientation(CameraCharacteristics c, int deviceOrientation) {
3344 if (deviceOrientation == android.view.OrientationEventListener.ORIENTATION_UNKNOWN) return 0;
3345 int sensorOrientation = c.get(CameraCharacteristics.SENSOR_ORIENTATION);
3347 // Round device orientation to a multiple of 90
3348 deviceOrientation = (deviceOrientation + 45) / 90 * 90;
3350 // Reverse device orientation for front-facing cameras
3351 boolean facingFront = c.get(CameraCharacteristics.LENS_FACING) == CameraCharacteristics.LENS_FACING_FRONT;
3352 if (facingFront) deviceOrientation = -deviceOrientation;
3354 // Calculate desired JPEG orientation relative to camera orientation to make
3355 // the image upright relative to the device orientation
3356 int jpegOrientation = (sensorOrientation + deviceOrientation + 360) % 360;
3358 return jpegOrientation;
3363 <entry name="quality" type="byte" visibility="public" hwlevel="legacy">
3364 <description>Compression quality of the final JPEG
3365 image.</description>
3366 <range>1-100; larger is higher quality</range>
3367 <details>85-95 is typical usage range.</details>
3370 <entry name="thumbnailQuality" type="byte" visibility="public" hwlevel="legacy">
3371 <description>Compression quality of JPEG
3372 thumbnail.</description>
3373 <range>1-100; larger is higher quality</range>
3376 <entry name="thumbnailSize" type="int32" visibility="public"
3377 container="array" typedef="size" hwlevel="legacy">
3381 <description>Resolution of embedded JPEG thumbnail.</description>
3382 <range>android.jpeg.availableThumbnailSizes</range>
3383 <details>When set to (0, 0) value, the JPEG EXIF will not contain thumbnail,
3384 but the captured JPEG will still be a valid image.
3386 For best results, when issuing a request for a JPEG image, the thumbnail size selected
3387 should have the same aspect ratio as the main JPEG output.
3389 If the thumbnail image aspect ratio differs from the JPEG primary image aspect
3390 ratio, the camera device creates the thumbnail by cropping it from the primary image.
3391 For example, if the primary image has 4:3 aspect ratio, the thumbnail image has
3392 16:9 aspect ratio, the primary image will be cropped vertically (letterbox) to
3393 generate the thumbnail image. The thumbnail image will always have a smaller Field
3394 Of View (FOV) than the primary image when aspect ratios differ.
3396 When an android.jpeg.orientation of non-zero degree is requested,
3397 the camera device will handle thumbnail rotation in one of the following ways:
3399 * Set the {@link android.media.ExifInterface#TAG_ORIENTATION EXIF orientation flag}
3400 and keep jpeg and thumbnail image data unrotated.
3401 * Rotate the jpeg and thumbnail image data and not set
3402 {@link android.media.ExifInterface#TAG_ORIENTATION EXIF orientation flag}. In this
3403 case, LIMITED or FULL hardware level devices will report rotated thumnail size in
3404 capture result, so the width and height will be interchanged if 90 or 270 degree
3405 orientation is requested. LEGACY device will always report unrotated thumbnail
3409 The HAL must not squeeze or stretch the downscaled primary image to generate thumbnail.
3410 The cropping must be done on the primary jpeg image rather than the sensor active array.
3411 The stream cropping rule specified by "S5. Cropping" in camera3.h doesn't apply to the
3412 thumbnail image cropping.
3418 <entry name="availableThumbnailSizes" type="int32" visibility="public"
3419 container="array" typedef="size" hwlevel="legacy">
3424 <description>List of JPEG thumbnail sizes for android.jpeg.thumbnailSize supported by this
3425 camera device.</description>
3427 This list will include at least one non-zero resolution, plus `(0,0)` for indicating no
3428 thumbnail should be generated.
3430 Below condiditions will be satisfied for this size list:
3432 * The sizes will be sorted by increasing pixel area (width x height).
3433 If several resolutions have the same area, they will be sorted by increasing width.
3434 * The aspect ratio of the largest thumbnail size will be same as the
3435 aspect ratio of largest JPEG output size in android.scaler.availableStreamConfigurations.
3436 The largest size is defined as the size that has the largest pixel area
3437 in a given size list.
3438 * Each output JPEG size in android.scaler.availableStreamConfigurations will have at least
3439 one corresponding size that has the same aspect ratio in availableThumbnailSizes,
3441 * All non-`(0, 0)` sizes will have non-zero widths and heights.</details>
3444 <entry name="maxSize" type="int32" visibility="system">
3445 <description>Maximum size in bytes for the compressed
3446 JPEG buffer</description>
3447 <range>Must be large enough to fit any JPEG produced by
3449 <details>This is used for sizing the gralloc buffers for
3454 <clone entry="android.jpeg.gpsLocation" kind="controls">
3456 <clone entry="android.jpeg.gpsCoordinates" kind="controls">
3458 <clone entry="android.jpeg.gpsProcessingMethod"
3459 kind="controls"></clone>
3460 <clone entry="android.jpeg.gpsTimestamp" kind="controls">
3462 <clone entry="android.jpeg.orientation" kind="controls">
3464 <clone entry="android.jpeg.quality" kind="controls">
3466 <entry name="size" type="int32">
3467 <description>The size of the compressed JPEG image, in
3469 <range>&gt;= 0</range>
3470 <details>If no JPEG output is produced for the request,
3473 Otherwise, this describes the real size of the compressed
3474 JPEG image placed in the output stream. More specifically,
3475 if android.jpeg.maxSize = 1000000, and a specific capture
3476 has android.jpeg.size = 500000, then the output buffer from
3477 the JPEG stream will be 1000000 bytes, of which the first
3478 500000 make up the real data.</details>
3481 <clone entry="android.jpeg.thumbnailQuality"
3482 kind="controls"></clone>
3483 <clone entry="android.jpeg.thumbnailSize" kind="controls">
3487 <section name="lens">
3489 <entry name="aperture" type="float" visibility="public" hwlevel="full">
3490 <description>The desired lens aperture size, as a ratio of lens focal length to the
3491 effective aperture diameter.</description>
3492 <units>The f-number (f/N)</units>
3493 <range>android.lens.info.availableApertures</range>
3494 <details>Setting this value is only supported on the camera devices that have a variable
3497 When this is supported and android.control.aeMode is OFF,
3498 this can be set along with android.sensor.exposureTime,
3499 android.sensor.sensitivity, and android.sensor.frameDuration
3500 to achieve manual exposure control.
3502 The requested aperture value may take several frames to reach the
3503 requested value; the camera device will report the current (intermediate)
3504 aperture size in capture result metadata while the aperture is changing.
3505 While the aperture is still changing, android.lens.state will be set to MOVING.
3507 When this is supported and android.control.aeMode is one of
3508 the ON modes, this will be overridden by the camera device
3509 auto-exposure algorithm, the overridden values are then provided
3510 back to the user in the corresponding result.</details>
3513 <entry name="filterDensity" type="float" visibility="public" hwlevel="full">
3515 The desired setting for the lens neutral density filter(s).
3517 <units>Exposure Value (EV)</units>
3518 <range>android.lens.info.availableFilterDensities</range>
3520 This control will not be supported on most camera devices.
3522 Lens filters are typically used to lower the amount of light the
3523 sensor is exposed to (measured in steps of EV). As used here, an EV
3524 step is the standard logarithmic representation, which are
3525 non-negative, and inversely proportional to the amount of light
3526 hitting the sensor. For example, setting this to 0 would result
3527 in no reduction of the incoming light, and setting this to 2 would
3528 mean that the filter is set to reduce incoming light by two stops
3529 (allowing 1/4 of the prior amount of light to the sensor).
3531 It may take several frames before the lens filter density changes
3532 to the requested value. While the filter density is still changing,
3533 android.lens.state will be set to MOVING.
3537 <entry name="focalLength" type="float" visibility="public" hwlevel="legacy">
3539 The desired lens focal length; used for optical zoom.
3541 <units>Millimeters</units>
3542 <range>android.lens.info.availableFocalLengths</range>
3544 This setting controls the physical focal length of the camera
3545 device's lens. Changing the focal length changes the field of
3546 view of the camera device, and is usually used for optical zoom.
3548 Like android.lens.focusDistance and android.lens.aperture, this
3549 setting won't be applied instantaneously, and it may take several
3550 frames before the lens can change to the requested focal length.
3551 While the focal length is still changing, android.lens.state will
3554 Optical zoom will not be supported on most devices.
3558 <entry name="focusDistance" type="float" visibility="public" hwlevel="full">
3559 <description>Desired distance to plane of sharpest focus,
3560 measured from frontmost surface of the lens.</description>
3561 <units>See android.lens.info.focusDistanceCalibration for details</units>
3562 <range>&gt;= 0</range>
3564 This control can be used for setting manual focus, on devices that support
3565 the MANUAL_SENSOR capability and have a variable-focus lens (see
3566 android.lens.info.minimumFocusDistance).
3568 A value of `0.0f` means infinity focus. The value set will be clamped to
3569 `[0.0f, android.lens.info.minimumFocusDistance]`.
3571 Like android.lens.focalLength, this setting won't be applied
3572 instantaneously, and it may take several frames before the lens
3573 can move to the requested focus distance. While the lens is still moving,
3574 android.lens.state will be set to MOVING.
3576 LEGACY devices support at most setting this to `0.0f`
3582 <entry name="opticalStabilizationMode" type="byte" visibility="public"
3583 enum="true" hwlevel="limited">
3586 <notes>Optical stabilization is unavailable.</notes>
3588 <value optional="true">ON
3589 <notes>Optical stabilization is enabled.</notes>
3593 Sets whether the camera device uses optical image stabilization (OIS)
3594 when capturing images.
3596 <range>android.lens.info.availableOpticalStabilization</range>
3598 OIS is used to compensate for motion blur due to small
3599 movements of the camera during capture. Unlike digital image
3600 stabilization (android.control.videoStabilizationMode), OIS
3601 makes use of mechanical elements to stabilize the camera
3602 sensor, and thus allows for longer exposure times before
3603 camera shake becomes apparent.
3605 Switching between different optical stabilization modes may take several
3606 frames to initialize, the camera device will report the current mode in
3607 capture result metadata. For example, When "ON" mode is requested, the
3608 optical stabilization modes in the first several capture results may still
3609 be "OFF", and it will become "ON" when the initialization is done.
3611 If a camera device supports both OIS and digital image stabilization
3612 (android.control.videoStabilizationMode), turning both modes on may produce undesirable
3613 interaction, so it is recommended not to enable both at the same time.
3615 Not all devices will support OIS; see
3616 android.lens.info.availableOpticalStabilization for
3623 <namespace name="info">
3624 <entry name="availableApertures" type="float" visibility="public"
3625 container="array" hwlevel="full">
3629 <description>List of aperture size values for android.lens.aperture that are
3630 supported by this camera device.</description>
3631 <units>The aperture f-number</units>
3632 <details>If the camera device doesn't support a variable lens aperture,
3633 this list will contain only one value, which is the fixed aperture size.
3635 If the camera device supports a variable aperture, the aperture values
3636 in this list will be sorted in ascending order.</details>
3639 <entry name="availableFilterDensities" type="float" visibility="public"
3640 container="array" hwlevel="full">
3645 List of neutral density filter values for
3646 android.lens.filterDensity that are supported by this camera device.
3648 <units>Exposure value (EV)</units>
3650 Values are &gt;= 0
3653 If a neutral density filter is not supported by this camera device,
3654 this list will contain only 0. Otherwise, this list will include every
3655 filter density supported by the camera device, in ascending order.
3659 <entry name="availableFocalLengths" type="float" visibility="public"
3660 type_notes="The list of available focal lengths"
3661 container="array" hwlevel="legacy">
3666 List of focal lengths for android.lens.focalLength that are supported by this camera
3669 <units>Millimeters</units>
3671 Values are &gt; 0
3674 If optical zoom is not supported, this list will only contain
3675 a single value corresponding to the fixed focal length of the
3676 device. Otherwise, this list will include every focal length supported
3677 by the camera device, in ascending order.
3682 <entry name="availableOpticalStabilization" type="byte"
3683 visibility="public" type_notes="list of enums" container="array"
3684 typedef="enumList" hwlevel="limited">
3689 List of optical image stabilization (OIS) modes for
3690 android.lens.opticalStabilizationMode that are supported by this camera device.
3692 <range>Any value listed in android.lens.opticalStabilizationMode</range>
3694 If OIS is not supported by a given camera device, this list will
3699 <entry name="hyperfocalDistance" type="float" visibility="public" optional="true"
3701 <description>Hyperfocal distance for this lens.</description>
3702 <units>See android.lens.info.focusDistanceCalibration for details</units>
3703 <range>If lens is fixed focus, &gt;= 0. If lens has focuser unit, the value is
3704 within `(0.0f, android.lens.info.minimumFocusDistance]`</range>
3706 If the lens is not fixed focus, the camera device will report this
3707 field when android.lens.info.focusDistanceCalibration is APPROXIMATE or CALIBRATED.
3710 <entry name="minimumFocusDistance" type="float" visibility="public" optional="true"
3712 <description>Shortest distance from frontmost surface
3713 of the lens that can be brought into sharp focus.</description>
3714 <units>See android.lens.info.focusDistanceCalibration for details</units>
3715 <range>&gt;= 0</range>
3716 <details>If the lens is fixed-focus, this will be
3718 <hal_details>Mandatory for FULL devices; LIMITED devices
3719 must always set this value to 0 for fixed-focus; and may omit
3720 the minimum focus distance otherwise.
3722 This field is also mandatory for all devices advertising
3723 the MANUAL_SENSOR capability.</hal_details>
3726 <entry name="shadingMapSize" type="int32" visibility="ndk_public"
3727 type_notes="width and height (N, M) of lens shading map provided by the camera device."
3728 container="array" typedef="size" hwlevel="full">
3732 <description>Dimensions of lens shading map.</description>
3733 <range>Both values &gt;= 1</range>
3735 The map should be on the order of 30-40 rows and columns, and
3736 must be smaller than 64x64.
3740 <entry name="focusDistanceCalibration" type="byte" visibility="public"
3741 enum="true" hwlevel="limited">
3745 The lens focus distance is not accurate, and the units used for
3746 android.lens.focusDistance do not correspond to any physical units.
3748 Setting the lens to the same focus distance on separate occasions may
3749 result in a different real focus distance, depending on factors such
3750 as the orientation of the device, the age of the focusing mechanism,
3751 and the device temperature. The focus distance value will still be
3752 in the range of `[0, android.lens.info.minimumFocusDistance]`, where 0
3753 represents the farthest focus.
3758 The lens focus distance is measured in diopters.
3760 However, setting the lens to the same focus distance
3761 on separate occasions may result in a different real
3762 focus distance, depending on factors such as the
3763 orientation of the device, the age of the focusing
3764 mechanism, and the device temperature.
3769 The lens focus distance is measured in diopters, and
3772 The lens mechanism is calibrated so that setting the
3773 same focus distance is repeatable on multiple
3774 occasions with good accuracy, and the focus distance
3775 corresponds to the real physical distance to the plane
3780 <description>The lens focus distance calibration quality.</description>
3782 The lens focus distance calibration quality determines the reliability of
3783 focus related metadata entries, i.e. android.lens.focusDistance,
3784 android.lens.focusRange, android.lens.info.hyperfocalDistance, and
3785 android.lens.info.minimumFocusDistance.
3787 APPROXIMATE and CALIBRATED devices report the focus metadata in
3788 units of diopters (1/meter), so `0.0f` represents focusing at infinity,
3789 and increasing positive numbers represent focusing closer and closer
3790 to the camera device. The focus distance control also uses diopters
3793 UNCALIBRATED devices do not use units that are directly comparable
3794 to any real physical measurement, but `0.0f` still represents farthest
3795 focus, and android.lens.info.minimumFocusDistance represents the
3796 nearest focus the device can achieve.
3799 For devices advertise APPROXIMATE quality or higher, diopters 0 (infinity
3800 focus) must work. When autofocus is disabled (android.control.afMode == OFF)
3801 and the lens focus distance is set to 0 diopters
3802 (android.lens.focusDistance == 0), the lens will move to focus at infinity
3803 and is stably focused at infinity even if the device tilts. It may take the
3804 lens some time to move; during the move the lens state should be MOVING and
3805 the output diopter value should be changing toward 0.
3810 <entry name="facing" type="byte" visibility="public" enum="true" hwlevel="legacy">
3814 The camera device faces the same direction as the device's screen.
3818 The camera device faces the opposite direction as the device's screen.
3822 The camera device is an external camera, and has no fixed facing relative to the
3826 <description>Direction the camera faces relative to
3827 device screen.</description>
3829 <entry name="poseRotation" type="float" visibility="public"
3835 The orientation of the camera relative to the sensor
3839 Quaternion coefficients
3842 The four coefficients that describe the quaternion
3843 rotation from the Android sensor coordinate system to a
3844 camera-aligned coordinate system where the X-axis is
3845 aligned with the long side of the image sensor, the Y-axis
3846 is aligned with the short side of the image sensor, and
3847 the Z-axis is aligned with the optical axis of the sensor.
3849 To convert from the quaternion coefficients `(x,y,z,w)`
3850 to the axis of rotation `(a_x, a_y, a_z)` and rotation
3851 amount `theta`, the following formulas can be used:
3854 a_x = x / sin(theta/2)
3855 a_y = y / sin(theta/2)
3856 a_z = z / sin(theta/2)
3858 To create a 3x3 rotation matrix that applies the rotation
3859 defined by this quaternion, the following matrix can be
3862 R = [ 1 - 2y^2 - 2z^2, 2xy - 2zw, 2xz + 2yw,
3863 2xy + 2zw, 1 - 2x^2 - 2z^2, 2yz - 2xw,
3864 2xz - 2yw, 2yz + 2xw, 1 - 2x^2 - 2y^2 ]
3866 This matrix can then be used to apply the rotation to a
3867 column vector point with
3871 where `p` is in the device sensor coordinate system, and
3872 `p'` is in the camera-oriented coordinate system.
3876 <entry name="poseTranslation" type="float" visibility="public"
3881 <description>Position of the camera optical center.</description>
3882 <units>Meters</units>
3884 The position of the camera device's lens optical center,
3885 as a three-dimensional vector `(x,y,z)`.
3887 Prior to Android P, or when android.lens.poseReference is PRIMARY_CAMERA, this position
3888 is relative to the optical center of the largest camera device facing in the same
3889 direction as this camera, in the {@link android.hardware.SensorEvent Android sensor
3890 coordinate axes}. Note that only the axis definitions are shared with the sensor
3891 coordinate system, but not the origin.
3893 If this device is the largest or only camera device with a given facing, then this
3894 position will be `(0, 0, 0)`; a camera device with a lens optical center located 3 cm
3895 from the main sensor along the +X axis (to the right from the user's perspective) will
3896 report `(0.03, 0, 0)`.
3898 To transform a pixel coordinates between two cameras facing the same direction, first
3899 the source camera android.lens.distortion must be corrected for. Then the source
3900 camera android.lens.intrinsicCalibration needs to be applied, followed by the
3901 android.lens.poseRotation of the source camera, the translation of the source camera
3902 relative to the destination camera, the android.lens.poseRotation of the destination
3903 camera, and finally the inverse of android.lens.intrinsicCalibration of the destination
3904 camera. This obtains a radial-distortion-free coordinate in the destination camera pixel
3907 To compare this against a real image from the destination camera, the destination camera
3908 image then needs to be corrected for radial distortion before comparison or sampling.
3910 When android.lens.poseReference is GYROSCOPE, then this position is relative to
3911 the center of the primary gyroscope on the device.
3917 <clone entry="android.lens.aperture" kind="controls">
3920 <clone entry="android.lens.filterDensity" kind="controls">
3923 <clone entry="android.lens.focalLength" kind="controls">
3926 <clone entry="android.lens.focusDistance" kind="controls">
3927 <details>Should be zero for fixed-focus cameras</details>
3930 <entry name="focusRange" type="float" visibility="public"
3931 type_notes="Range of scene distances that are in focus"
3932 container="array" typedef="pairFloatFloat" hwlevel="limited">
3936 <description>The range of scene distances that are in
3937 sharp focus (depth of field).</description>
3938 <units>A pair of focus distances in diopters: (near,
3939 far); see android.lens.info.focusDistanceCalibration for details.</units>
3940 <range>&gt;=0</range>
3941 <details>If variable focus not supported, can still report
3942 fixed depth of field range</details>
3945 <clone entry="android.lens.opticalStabilizationMode"
3949 <entry name="state" type="byte" visibility="public" enum="true" hwlevel="limited">
3953 The lens parameters (android.lens.focalLength, android.lens.focusDistance,
3954 android.lens.filterDensity and android.lens.aperture) are not changing.
3959 One or several of the lens parameters
3960 (android.lens.focalLength, android.lens.focusDistance,
3961 android.lens.filterDensity or android.lens.aperture) is
3966 <description>Current lens status.</description>
3968 For lens parameters android.lens.focalLength, android.lens.focusDistance,
3969 android.lens.filterDensity and android.lens.aperture, when changes are requested,
3970 they may take several frames to reach the requested values. This state indicates
3971 the current status of the lens parameters.
3973 When the state is STATIONARY, the lens parameters are not changing. This could be
3974 either because the parameters are all fixed, or because the lens has had enough
3975 time to reach the most recently-requested values.
3976 If all these lens parameters are not changable for a camera device, as listed below:
3978 * Fixed focus (`android.lens.info.minimumFocusDistance == 0`), which means
3979 android.lens.focusDistance parameter will always be 0.
3980 * Fixed focal length (android.lens.info.availableFocalLengths contains single value),
3981 which means the optical zoom is not supported.
3982 * No ND filter (android.lens.info.availableFilterDensities contains only 0).
3983 * Fixed aperture (android.lens.info.availableApertures contains single value).
3985 Then this state will always be STATIONARY.
3987 When the state is MOVING, it indicates that at least one of the lens parameters
3992 <clone entry="android.lens.poseRotation" kind="static">
3994 <clone entry="android.lens.poseTranslation" kind="static">
3998 <entry name="intrinsicCalibration" type="float" visibility="public"
4004 The parameters for this camera device's intrinsic
4009 android.sensor.info.preCorrectionActiveArraySize
4013 The five calibration parameters that describe the
4014 transform from camera-centric 3D coordinates to sensor
4017 [f_x, f_y, c_x, c_y, s]
4019 Where `f_x` and `f_y` are the horizontal and vertical
4020 focal lengths, `[c_x, c_y]` is the position of the optical
4021 axis, and `s` is a skew parameter for the sensor plane not
4022 being aligned with the lens plane.
4024 These are typically used within a transformation matrix K:
4030 which can then be combined with the camera pose rotation
4031 `R` and translation `t` (android.lens.poseRotation and
4032 android.lens.poseTranslation, respective) to calculate the
4033 complete transform from world coordinates to pixel
4039 and with `p_w` being a point in the world coordinate system
4040 and `p_s` being a point in the camera active pixel array
4041 coordinate system, and with the mapping including the
4042 homogeneous division by z:
4044 p_h = (x_h, y_h, z_h) = P p_w
4047 so `[x_s, y_s]` is the pixel coordinates of the world
4048 point, `z_s = 1`, and `w_s` is a measurement of disparity
4049 (depth) in pixel coordinates.
4051 Note that the coordinate system for this transform is the
4052 android.sensor.info.preCorrectionActiveArraySize system,
4053 where `(0,0)` is the top-left of the
4054 preCorrectionActiveArraySize rectangle. Once the pose and
4055 intrinsic calibration transforms have been applied to a
4056 world point, then the android.lens.distortion
4057 transform needs to be applied, and the result adjusted to
4058 be in the android.sensor.info.activeArraySize coordinate
4059 system (where `(0, 0)` is the top-left of the
4060 activeArraySize rectangle), to determine the final pixel
4061 coordinate of the world point for processed (non-RAW)
4066 <entry name="radialDistortion" type="float" visibility="public"
4067 deprecated="true" container="array">
4072 The correction coefficients to correct for this camera device's
4073 radial and tangential lens distortion.
4075 <deprecation_description>
4076 This field was inconsistently defined in terms of its
4077 normalization. Use android.lens.distortion instead.
4078 </deprecation_description>
4080 Unitless coefficients.
4083 Four radial distortion coefficients `[kappa_0, kappa_1, kappa_2,
4084 kappa_3]` and two tangential distortion coefficients
4085 `[kappa_4, kappa_5]` that can be used to correct the
4086 lens's geometric distortion with the mapping equations:
4088 x_c = x_i * ( kappa_0 + kappa_1 * r^2 + kappa_2 * r^4 + kappa_3 * r^6 ) +
4089 kappa_4 * (2 * x_i * y_i) + kappa_5 * ( r^2 + 2 * x_i^2 )
4090 y_c = y_i * ( kappa_0 + kappa_1 * r^2 + kappa_2 * r^4 + kappa_3 * r^6 ) +
4091 kappa_5 * (2 * x_i * y_i) + kappa_4 * ( r^2 + 2 * y_i^2 )
4093 Here, `[x_c, y_c]` are the coordinates to sample in the
4094 input image that correspond to the pixel values in the
4095 corrected image at the coordinate `[x_i, y_i]`:
4097 correctedImage(x_i, y_i) = sample_at(x_c, y_c, inputImage)
4099 The pixel coordinates are defined in a normalized
4100 coordinate system related to the
4101 android.lens.intrinsicCalibration calibration fields.
4102 Both `[x_i, y_i]` and `[x_c, y_c]` have `(0,0)` at the
4103 lens optical center `[c_x, c_y]`. The maximum magnitudes
4104 of both x and y coordinates are normalized to be 1 at the
4105 edge further from the optical center, so the range
4106 for both dimensions is `-1 <= x <= 1`.
4108 Finally, `r` represents the radial distance from the
4109 optical center, `r^2 = x_i^2 + y_i^2`, and its magnitude
4110 is therefore no larger than `|r| <= sqrt(2)`.
4112 The distortion model used is the Brown-Conrady model.
4118 <clone entry="android.lens.intrinsicCalibration" kind="static">
4120 <clone entry="android.lens.radialDistortion" kind="static">
4124 <entry name="poseReference" type="byte" visibility="public" enum="true" hal_version="3.3">
4126 <value>PRIMARY_CAMERA
4127 <notes>The value of android.lens.poseTranslation is relative to the optical center of
4128 the largest camera device facing the same direction as this camera.
4130 This is the default value for API levels before Android P.
4134 <notes>The value of android.lens.poseTranslation is relative to the position of the
4135 primary gyroscope of this Android device.
4140 The origin for android.lens.poseTranslation.
4143 Different calibration methods and use cases can produce better or worse results
4144 depending on the selected coordinate origin.
4147 <entry name="distortion" type="float" visibility="public" container="array"
4153 The correction coefficients to correct for this camera device's
4154 radial and tangential lens distortion.
4156 Replaces the deprecated android.lens.radialDistortion field, which was
4157 inconsistently defined.
4160 Unitless coefficients.
4163 Three radial distortion coefficients `[kappa_1, kappa_2,
4164 kappa_3]` and two tangential distortion coefficients
4165 `[kappa_4, kappa_5]` that can be used to correct the
4166 lens's geometric distortion with the mapping equations:
4168 x_c = x_i * ( 1 + kappa_1 * r^2 + kappa_2 * r^4 + kappa_3 * r^6 ) +
4169 kappa_4 * (2 * x_i * y_i) + kappa_5 * ( r^2 + 2 * x_i^2 )
4170 y_c = y_i * ( 1 + kappa_1 * r^2 + kappa_2 * r^4 + kappa_3 * r^6 ) +
4171 kappa_5 * (2 * x_i * y_i) + kappa_4 * ( r^2 + 2 * y_i^2 )
4173 Here, `[x_c, y_c]` are the coordinates to sample in the
4174 input image that correspond to the pixel values in the
4175 corrected image at the coordinate `[x_i, y_i]`:
4177 correctedImage(x_i, y_i) = sample_at(x_c, y_c, inputImage)
4179 The pixel coordinates are defined in a coordinate system
4180 related to the android.lens.intrinsicCalibration
4181 calibration fields; see that entry for details of the mapping stages.
4182 Both `[x_i, y_i]` and `[x_c, y_c]`
4183 have `(0,0)` at the lens optical center `[c_x, c_y]`, and
4184 the range of the coordinates depends on the focal length
4185 terms of the intrinsic calibration.
4187 Finally, `r` represents the radial distance from the
4188 optical center, `r^2 = x_i^2 + y_i^2`.
4190 The distortion model used is the Brown-Conrady model.
4196 <clone entry="android.lens.distortion" kind="static">
4200 <section name="noiseReduction">
4202 <entry name="mode" type="byte" visibility="public" enum="true" hwlevel="full">
4205 <notes>No noise reduction is applied.</notes></value>
4207 <notes>Noise reduction is applied without reducing frame rate relative to sensor
4208 output. It may be the same as OFF if noise reduction will reduce frame rate
4209 relative to sensor.</notes></value>
4211 <notes>High-quality noise reduction is applied, at the cost of possibly reduced frame
4212 rate relative to sensor output.</notes></value>
4213 <value optional="true">MINIMAL
4214 <notes>MINIMAL noise reduction is applied without reducing frame rate relative to
4215 sensor output. </notes></value>
4216 <value optional="true">ZERO_SHUTTER_LAG
4218 <notes>Noise reduction is applied at different levels for different output streams,
4219 based on resolution. Streams at maximum recording resolution (see {@link
4220 android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession})
4221 or below have noise reduction applied, while higher-resolution streams have MINIMAL (if
4222 supported) or no noise reduction applied (if MINIMAL is not supported.) The degree of
4223 noise reduction for low-resolution streams is tuned so that frame rate is not impacted,
4224 and the quality is equal to or better than FAST (since it is only applied to
4225 lower-resolution outputs, quality may improve from FAST).
4227 This mode is intended to be used by applications operating in a zero-shutter-lag mode
4228 with YUV or PRIVATE reprocessing, where the application continuously captures
4229 high-resolution intermediate buffers into a circular buffer, from which a final image is
4230 produced via reprocessing when a user takes a picture. For such a use case, the
4231 high-resolution buffers must not have noise reduction applied to maximize efficiency of
4232 preview and to avoid over-applying noise filtering when reprocessing, while
4233 low-resolution buffers (used for recording or preview, generally) need noise reduction
4234 applied for reasonable preview quality.
4236 This mode is guaranteed to be supported by devices that support either the
4237 YUV_REPROCESSING or PRIVATE_REPROCESSING capabilities
4238 (android.request.availableCapabilities lists either of those capabilities) and it will
4239 be the default mode for CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template.
4242 <description>Mode of operation for the noise reduction algorithm.</description>
4243 <range>android.noiseReduction.availableNoiseReductionModes</range>
4244 <details>The noise reduction algorithm attempts to improve image quality by removing
4245 excessive noise added by the capture process, especially in dark conditions.
4247 OFF means no noise reduction will be applied by the camera device, for both raw and
4250 MINIMAL means that only sensor raw domain basic noise reduction is enabled ,to remove
4251 demosaicing or other processing artifacts. For YUV_REPROCESSING, MINIMAL is same as OFF.
4252 This mode is optional, may not be support by all devices. The application should check
4253 android.noiseReduction.availableNoiseReductionModes before using it.
4255 FAST/HIGH_QUALITY both mean camera device determined noise filtering
4256 will be applied. HIGH_QUALITY mode indicates that the camera device
4257 will use the highest-quality noise filtering algorithms,
4258 even if it slows down capture rate. FAST means the camera device will not
4259 slow down capture rate when applying noise filtering. FAST may be the same as MINIMAL if
4260 MINIMAL is listed, or the same as OFF if any noise filtering will slow down capture rate.
4261 Every output stream will have a similar amount of enhancement applied.
4263 ZERO_SHUTTER_LAG is meant to be used by applications that maintain a continuous circular
4264 buffer of high-resolution images during preview and reprocess image(s) from that buffer
4265 into a final capture when triggered by the user. In this mode, the camera device applies
4266 noise reduction to low-resolution streams (below maximum recording resolution) to maximize
4267 preview quality, but does not apply noise reduction to high-resolution streams, since
4268 those will be reprocessed later if necessary.
4270 For YUV_REPROCESSING, these FAST/HIGH_QUALITY modes both mean that the camera device
4271 will apply FAST/HIGH_QUALITY YUV domain noise reduction, respectively. The camera device
4272 may adjust the noise reduction parameters for best image quality based on the
4273 android.reprocess.effectiveExposureFactor if it is set.
4276 For YUV_REPROCESSING The HAL can use android.reprocess.effectiveExposureFactor to
4277 adjust the internal noise reduction parameters appropriately to get the best quality
4283 <entry name="strength" type="byte">
4284 <description>Control the amount of noise reduction
4285 applied to the images</description>
4286 <units>1-10; 10 is max noise reduction</units>
4287 <range>1 - 10</range>
4292 <entry name="availableNoiseReductionModes" type="byte" visibility="public"
4293 type_notes="list of enums" container="array" typedef="enumList" hwlevel="limited">
4298 List of noise reduction modes for android.noiseReduction.mode that are supported
4299 by this camera device.
4301 <range>Any value listed in android.noiseReduction.mode</range>
4303 Full-capability camera devices will always support OFF and FAST.
4305 Camera devices that support YUV_REPROCESSING or PRIVATE_REPROCESSING will support
4308 Legacy-capability camera devices will only support FAST mode.
4311 HAL must support both FAST and HIGH_QUALITY if noise reduction control is available
4312 on the camera device, but the underlying implementation can be the same for both modes.
4313 That is, if the highest quality implementation on the camera device does not slow down
4314 capture rate, then FAST and HIGH_QUALITY will generate the same output.
4321 <clone entry="android.noiseReduction.mode" kind="controls">
4327 <section name="quirks">
4329 <entry name="meteringCropRegion" type="byte" visibility="system" deprecated="true" optional="true">
4330 <description>If set to 1, the camera service does not
4331 scale 'normalized' coordinates with respect to the crop
4332 region. This applies to metering input (a{e,f,wb}Region
4333 and output (face rectangles).</description>
4334 <deprecation_description>
4335 Not used in HALv3 or newer
4336 </deprecation_description>
4337 <details>Normalized coordinates refer to those in the
4338 (-1000,1000) range mentioned in the
4339 android.hardware.Camera API.
4341 HAL implementations should instead always use and emit
4342 sensor array-relative coordinates for all region data. Does
4343 not need to be listed in static metadata. Support will be
4344 removed in future versions of camera service.</details>
4346 <entry name="triggerAfWithAuto" type="byte" visibility="system" deprecated="true" optional="true">
4347 <description>If set to 1, then the camera service always
4348 switches to FOCUS_MODE_AUTO before issuing a AF
4349 trigger.</description>
4350 <deprecation_description>
4351 Not used in HALv3 or newer
4352 </deprecation_description>
4353 <details>HAL implementations should implement AF trigger
4354 modes for AUTO, MACRO, CONTINUOUS_FOCUS, and
4355 CONTINUOUS_PICTURE modes instead of using this flag. Does
4356 not need to be listed in static metadata. Support will be
4357 removed in future versions of camera service</details>
4359 <entry name="useZslFormat" type="byte" visibility="system" deprecated="true" optional="true">
4360 <description>If set to 1, the camera service uses
4361 CAMERA2_PIXEL_FORMAT_ZSL instead of
4362 HAL_PIXEL_FORMAT_IMPLEMENTATION_DEFINED for the zero
4363 shutter lag stream</description>
4364 <deprecation_description>
4365 Not used in HALv3 or newer
4366 </deprecation_description>
4367 <details>HAL implementations should use gralloc usage flags
4368 to determine that a stream will be used for
4369 zero-shutter-lag, instead of relying on an explicit
4370 format setting. Does not need to be listed in static
4371 metadata. Support will be removed in future versions of
4372 camera service.</details>
4374 <entry name="usePartialResult" type="byte" visibility="hidden" deprecated="true" optional="true">
4376 If set to 1, the HAL will always split result
4377 metadata for a single capture into multiple buffers,
4378 returned using multiple process_capture_result calls.
4380 <deprecation_description>
4381 Not used in HALv3 or newer; replaced by better partials mechanism
4382 </deprecation_description>
4384 Does not need to be listed in static
4385 metadata. Support for partial results will be reworked in
4386 future versions of camera service. This quirk will stop
4387 working at that point; DO NOT USE without careful
4388 consideration of future support.
4391 Refer to `camera3_capture_result::partial_result`
4392 for information on how to implement partial results.
4397 <entry name="partialResult" type="byte" visibility="hidden" deprecated="true" optional="true" enum="true" typedef="boolean">
4400 <notes>The last or only metadata result buffer
4401 for this capture.</notes>
4404 <notes>A partial buffer of result metadata for this
4405 capture. More result buffers for this capture will be sent
4406 by the camera device, the last of which will be marked
4411 Whether a result given to the framework is the
4412 final one for the capture, or only a partial that contains a
4413 subset of the full set of dynamic metadata
4414 values.</description>
4415 <deprecation_description>
4416 Not used in HALv3 or newer
4417 </deprecation_description>
4418 <range>Optional. Default value is FINAL.</range>
4420 The entries in the result metadata buffers for a
4421 single capture may not overlap, except for this entry. The
4422 FINAL buffers must retain FIFO ordering relative to the
4423 requests that generate them, so the FINAL buffer for frame 3 must
4424 always be sent to the framework after the FINAL buffer for frame 2, and
4425 before the FINAL buffer for frame 4. PARTIAL buffers may be returned
4426 in any order relative to other frames, but all PARTIAL buffers for a given
4427 capture must arrive before the FINAL buffer for that capture. This entry may
4428 only be used by the camera device if quirks.usePartialResult is set to 1.
4431 Refer to `camera3_capture_result::partial_result`
4432 for information on how to implement partial results.
4437 <section name="request">
4439 <entry name="frameCount" type="int32" visibility="system" deprecated="true">
4440 <description>A frame counter set by the framework. Must
4441 be maintained unchanged in output frame. This value monotonically
4442 increases with every new result (that is, each new result has a unique
4445 <deprecation_description>
4446 Not used in HALv3 or newer
4447 </deprecation_description>
4448 <units>incrementing integer</units>
4449 <range>Any int.</range>
4451 <entry name="id" type="int32" visibility="hidden">
4452 <description>An application-specified ID for the current
4453 request. Must be maintained unchanged in output
4455 <units>arbitrary integer assigned by application</units>
4456 <range>Any int</range>
4459 <entry name="inputStreams" type="int32" visibility="system" deprecated="true"
4464 <description>List which camera reprocess stream is used
4465 for the source of reprocessing data.</description>
4466 <deprecation_description>
4467 Not used in HALv3 or newer
4468 </deprecation_description>
4469 <units>List of camera reprocess stream IDs</units>
4471 Typically, only one entry allowed, must be a valid reprocess stream ID.
4473 <details>Only meaningful when android.request.type ==
4474 REPROCESS. Ignored otherwise</details>
4477 <entry name="metadataMode" type="byte" visibility="system"
4481 <notes>No metadata should be produced on output, except
4482 for application-bound buffer data. If no
4483 application-bound streams exist, no frame should be
4484 placed in the output frame queue. If such streams
4485 exist, a frame should be placed on the output queue
4486 with null metadata but with the necessary output buffer
4487 information. Timestamp information should still be
4488 included with any output stream buffers</notes></value>
4490 <notes>All metadata should be produced. Statistics will
4491 only be produced if they are separately
4492 enabled</notes></value>
4494 <description>How much metadata to produce on
4495 output</description>
4498 <entry name="outputStreams" type="int32" visibility="system" deprecated="true"
4503 <description>Lists which camera output streams image data
4504 from this capture must be sent to</description>
4505 <deprecation_description>
4506 Not used in HALv3 or newer
4507 </deprecation_description>
4508 <units>List of camera stream IDs</units>
4509 <range>List must only include streams that have been
4511 <details>If no output streams are listed, then the image
4512 data should simply be discarded. The image data must
4513 still be captured for metadata and statistics production,
4514 and the lens and flash must operate as requested.</details>
4517 <entry name="type" type="byte" visibility="system" deprecated="true" enum="true">
4520 <notes>Capture a new image from the imaging hardware,
4521 and process it according to the
4522 settings</notes></value>
4524 <notes>Process previously captured data; the
4525 android.request.inputStreams parameter determines the
4526 source reprocessing stream. TODO: Mark dynamic metadata
4527 needed for reprocessing with [RP]</notes></value>
4529 <description>The type of the request; either CAPTURE or
4530 REPROCESS. For legacy HAL3, this tag is redundant.
4532 <deprecation_description>
4533 Not used in HALv3 or newer
4534 </deprecation_description>
4539 <entry name="maxNumOutputStreams" type="int32" visibility="ndk_public"
4540 container="array" hwlevel="legacy">
4544 <description>The maximum numbers of different types of output streams
4545 that can be configured and used simultaneously by a camera device.
4548 For processed (and stalling) format streams, &gt;= 1.
4550 For Raw format (either stalling or non-stalling) streams, &gt;= 0.
4552 For processed (but not stalling) format streams, &gt;= 3
4553 for FULL mode devices (`android.info.supportedHardwareLevel == FULL`);
4554 &gt;= 2 for LIMITED mode devices (`android.info.supportedHardwareLevel == LIMITED`).
4557 This is a 3 element tuple that contains the max number of output simultaneous
4558 streams for raw sensor, processed (but not stalling), and processed (and stalling)
4559 formats respectively. For example, assuming that JPEG is typically a processed and
4560 stalling stream, if max raw sensor format output stream number is 1, max YUV streams
4561 number is 3, and max JPEG stream number is 2, then this tuple should be `(1, 3, 2)`.
4563 This lists the upper bound of the number of output streams supported by
4564 the camera device. Using more streams simultaneously may require more hardware and
4565 CPU resources that will consume more power. The image format for an output stream can
4566 be any supported format provided by android.scaler.availableStreamConfigurations.
4567 The formats defined in android.scaler.availableStreamConfigurations can be catergorized
4568 into the 3 stream types as below:
4570 * Processed (but stalling): any non-RAW format with a stallDurations &gt; 0.
4571 Typically {@link android.graphics.ImageFormat#JPEG|AIMAGE_FORMAT_JPEG JPEG format}.
4572 * Raw formats: {@link android.graphics.ImageFormat#RAW_SENSOR|AIMAGE_FORMAT_RAW16
4573 RAW_SENSOR}, {@link android.graphics.ImageFormat#RAW10|AIMAGE_FORMAT_RAW10 RAW10}, or
4574 {@link android.graphics.ImageFormat#RAW12|AIMAGE_FORMAT_RAW12 RAW12}.
4575 * Processed (but not-stalling): any non-RAW format without a stall duration. Typically
4576 {@link android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888 YUV_420_888},
4577 {@link android.graphics.ImageFormat#NV21 NV21}, or {@link
4578 android.graphics.ImageFormat#YV12 YV12}.
4582 <entry name="maxNumOutputRaw" type="int32" visibility="java_public" synthetic="true"
4584 <description>The maximum numbers of different types of output streams
4585 that can be configured and used simultaneously by a camera device
4586 for any `RAW` formats.
4592 This value contains the max number of output simultaneous
4593 streams from the raw sensor.
4595 This lists the upper bound of the number of output streams supported by
4596 the camera device. Using more streams simultaneously may require more hardware and
4597 CPU resources that will consume more power. The image format for this kind of an output stream can
4598 be any `RAW` and supported format provided by android.scaler.streamConfigurationMap.
4600 In particular, a `RAW` format is typically one of:
4602 * {@link android.graphics.ImageFormat#RAW_SENSOR|AIMAGE_FORMAT_RAW16 RAW_SENSOR}
4603 * {@link android.graphics.ImageFormat#RAW10|AIMAGE_FORMAT_RAW10 RAW10}
4604 * {@link android.graphics.ImageFormat#RAW12|AIMAGE_FORMAT_RAW12 RAW12}
4606 LEGACY mode devices (android.info.supportedHardwareLevel `==` LEGACY)
4607 never support raw streams.
4610 <entry name="maxNumOutputProc" type="int32" visibility="java_public" synthetic="true"
4612 <description>The maximum numbers of different types of output streams
4613 that can be configured and used simultaneously by a camera device
4614 for any processed (but not-stalling) formats.
4618 for FULL mode devices (`android.info.supportedHardwareLevel == FULL`);
4619 &gt;= 2 for LIMITED mode devices (`android.info.supportedHardwareLevel == LIMITED`).
4622 This value contains the max number of output simultaneous
4623 streams for any processed (but not-stalling) formats.
4625 This lists the upper bound of the number of output streams supported by
4626 the camera device. Using more streams simultaneously may require more hardware and
4627 CPU resources that will consume more power. The image format for this kind of an output stream can
4628 be any non-`RAW` and supported format provided by android.scaler.streamConfigurationMap.
4630 Processed (but not-stalling) is defined as any non-RAW format without a stall duration.
4633 * {@link android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888 YUV_420_888}
4634 * {@link android.graphics.ImageFormat#NV21 NV21}
4635 * {@link android.graphics.ImageFormat#YV12 YV12}
4636 * Implementation-defined formats, i.e. {@link
4637 android.hardware.camera2.params.StreamConfigurationMap#isOutputSupportedFor(Class)}
4639 For full guarantees, query {@link
4640 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration} with a
4641 processed format -- it will return 0 for a non-stalling stream.
4643 LEGACY devices will support at least 2 processing/non-stalling streams.
4646 <entry name="maxNumOutputProcStalling" type="int32" visibility="java_public" synthetic="true"
4648 <description>The maximum numbers of different types of output streams
4649 that can be configured and used simultaneously by a camera device
4650 for any processed (and stalling) formats.
4656 This value contains the max number of output simultaneous
4657 streams for any processed (but not-stalling) formats.
4659 This lists the upper bound of the number of output streams supported by
4660 the camera device. Using more streams simultaneously may require more hardware and
4661 CPU resources that will consume more power. The image format for this kind of an output stream can
4662 be any non-`RAW` and supported format provided by android.scaler.streamConfigurationMap.
4664 A processed and stalling format is defined as any non-RAW format with a stallDurations
4665 &gt; 0. Typically only the {@link
4666 android.graphics.ImageFormat#JPEG|AIMAGE_FORMAT_JPEG JPEG format} is a stalling format.
4668 For full guarantees, query {@link
4669 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration} with a
4670 processed format -- it will return a non-0 value for a stalling stream.
4672 LEGACY devices will support up to 1 processing/stalling stream.
4675 <entry name="maxNumReprocessStreams" type="int32" visibility="system"
4676 deprecated="true" container="array">
4680 <description>How many reprocessing streams of any type
4681 can be allocated at the same time.</description>
4682 <deprecation_description>
4683 Not used in HALv3 or newer
4684 </deprecation_description>
4685 <range>&gt;= 0</range>
4687 Only used by HAL2.x.
4689 When set to 0, it means no reprocess stream is supported.
4693 <entry name="maxNumInputStreams" type="int32" visibility="java_public" hwlevel="full">
4695 The maximum numbers of any type of input streams
4696 that can be configured and used simultaneously by a camera device.
4701 <details>When set to 0, it means no input stream is supported.
4703 The image format for a input stream can be any supported format returned by {@link
4704 android.hardware.camera2.params.StreamConfigurationMap#getInputFormats}. When using an
4705 input stream, there must be at least one output stream configured to to receive the
4708 When an input stream and some output streams are used in a reprocessing request,
4709 only the input buffer will be used to produce these output stream buffers, and a
4710 new sensor image will not be captured.
4712 For example, for Zero Shutter Lag (ZSL) still capture use case, the input
4713 stream image format will be PRIVATE, the associated output stream image format
4717 For the reprocessing flow and controls, see
4718 hardware/libhardware/include/hardware/camera3.h Section 10 for more details.
4724 <entry name="frameCount" type="int32" visibility="hidden" deprecated="true">
4725 <description>A frame counter set by the framework. This value monotonically
4726 increases with every new result (that is, each new result has a unique
4727 frameCount value).</description>
4728 <deprecation_description>
4729 Not used in HALv3 or newer
4730 </deprecation_description>
4731 <units>count of frames</units>
4732 <range>&gt; 0</range>
4733 <details>Reset on release()</details>
4735 <clone entry="android.request.id" kind="controls"></clone>
4736 <clone entry="android.request.metadataMode"
4737 kind="controls"></clone>
4738 <clone entry="android.request.outputStreams"
4739 kind="controls"></clone>
4740 <entry name="pipelineDepth" type="byte" visibility="public" hwlevel="legacy">
4741 <description>Specifies the number of pipeline stages the frame went
4742 through from when it was exposed to when the final completed result
4743 was available to the framework.</description>
4744 <range>&lt;= android.request.pipelineMaxDepth</range>
4745 <details>Depending on what settings are used in the request, and
4746 what streams are configured, the data may undergo less processing,
4747 and some pipeline stages skipped.
4749 See android.request.pipelineMaxDepth for more details.
4752 This value must always represent the accurate count of how many
4753 pipeline stages were actually used.
4758 <entry name="pipelineMaxDepth" type="byte" visibility="public" hwlevel="legacy">
4759 <description>Specifies the number of maximum pipeline stages a frame
4760 has to go through from when it's exposed to when it's available
4761 to the framework.</description>
4762 <details>A typical minimum value for this is 2 (one stage to expose,
4763 one stage to readout) from the sensor. The ISP then usually adds
4764 its own stages to do custom HW processing. Further stages may be
4765 added by SW processing.
4767 Depending on what settings are used (e.g. YUV, JPEG) and what
4768 processing is enabled (e.g. face detection), the actual pipeline
4769 depth (specified by android.request.pipelineDepth) may be less than
4770 the max pipeline depth.
4772 A pipeline depth of X stages is equivalent to a pipeline latency of
4775 This value will normally be 8 or less, however, for high speed capture session,
4776 the max pipeline depth will be up to 8 x size of high speed capture request list.
4779 This value should be 4 or less, expect for the high speed recording session, where the
4780 max batch sizes may be larger than 1.
4783 <entry name="partialResultCount" type="int32" visibility="public" optional="true">
4784 <description>Defines how many sub-components
4785 a result will be composed of.
4787 <range>&gt;= 1</range>
4788 <details>In order to combat the pipeline latency, partial results
4789 may be delivered to the application layer from the camera device as
4790 soon as they are available.
4792 Optional; defaults to 1. A value of 1 means that partial
4793 results are not supported, and only the final TotalCaptureResult will
4794 be produced by the camera device.
4796 A typical use case for this might be: after requesting an
4797 auto-focus (AF) lock the new AF state might be available 50%
4798 of the way through the pipeline. The camera device could
4799 then immediately dispatch this state via a partial result to
4800 the application, and the rest of the metadata via later
4804 <entry name="availableCapabilities" type="byte" visibility="public"
4805 enum="true" container="array" hwlevel="legacy">
4810 <value>BACKWARD_COMPATIBLE
4811 <notes>The minimal set of capabilities that every camera
4812 device (regardless of android.info.supportedHardwareLevel)
4815 This capability is listed by all normal devices, and
4816 indicates that the camera device has a feature set
4817 that's comparable to the baseline requirements for the
4818 older android.hardware.Camera API.
4820 Devices with the DEPTH_OUTPUT capability might not list this
4821 capability, indicating that they support only depth measurement,
4822 not standard color output.
4825 <value optional="true">MANUAL_SENSOR
4827 The camera device can be manually controlled (3A algorithms such
4828 as auto-exposure, and auto-focus can be bypassed).
4829 The camera device supports basic manual control of the sensor image
4830 acquisition related stages. This means the following controls are
4831 guaranteed to be supported:
4833 * Manual frame duration control
4834 * android.sensor.frameDuration
4835 * android.sensor.info.maxFrameDuration
4836 * Manual exposure control
4837 * android.sensor.exposureTime
4838 * android.sensor.info.exposureTimeRange
4839 * Manual sensitivity control
4840 * android.sensor.sensitivity
4841 * android.sensor.info.sensitivityRange
4842 * Manual lens control (if the lens is adjustable)
4844 * Manual flash control (if a flash unit is present)
4846 * Manual black level locking
4847 * android.blackLevel.lock
4848 * Auto exposure lock
4849 * android.control.aeLock
4851 If any of the above 3A algorithms are enabled, then the camera
4852 device will accurately report the values applied by 3A in the
4855 A given camera device may also support additional manual sensor controls,
4856 but this capability only covers the above list of controls.
4858 If this is supported, android.scaler.streamConfigurationMap will
4859 additionally return a min frame duration that is greater than
4860 zero for each supported size-format combination.
4863 <value optional="true">MANUAL_POST_PROCESSING
4865 The camera device post-processing stages can be manually controlled.
4866 The camera device supports basic manual control of the image post-processing
4867 stages. This means the following controls are guaranteed to be supported:
4869 * Manual tonemap control
4870 * android.tonemap.curve
4871 * android.tonemap.mode
4872 * android.tonemap.maxCurvePoints
4873 * android.tonemap.gamma
4874 * android.tonemap.presetCurve
4876 * Manual white balance control
4877 * android.colorCorrection.transform
4878 * android.colorCorrection.gains
4879 * Manual lens shading map control
4880 * android.shading.mode
4881 * android.statistics.lensShadingMapMode
4882 * android.statistics.lensShadingMap
4883 * android.lens.info.shadingMapSize
4884 * Manual aberration correction control (if aberration correction is supported)
4885 * android.colorCorrection.aberrationMode
4886 * android.colorCorrection.availableAberrationModes
4887 * Auto white balance lock
4888 * android.control.awbLock
4890 If auto white balance is enabled, then the camera device
4891 will accurately report the values applied by AWB in the result.
4893 A given camera device may also support additional post-processing
4894 controls, but this capability only covers the above list of controls.
4897 <value optional="true">RAW
4899 The camera device supports outputting RAW buffers and
4900 metadata for interpreting them.
4902 Devices supporting the RAW capability allow both for
4903 saving DNG files, and for direct application processing of
4906 * RAW_SENSOR is supported as an output format.
4907 * The maximum available resolution for RAW_SENSOR streams
4908 will match either the value in
4909 android.sensor.info.pixelArraySize or
4910 android.sensor.info.preCorrectionActiveArraySize.
4911 * All DNG-related optional metadata entries are provided
4912 by the camera device.
4915 <value optional="true" ndk_hidden="true">PRIVATE_REPROCESSING
4917 The camera device supports the Zero Shutter Lag reprocessing use case.
4919 * One input stream is supported, that is, `android.request.maxNumInputStreams == 1`.
4920 * {@link android.graphics.ImageFormat#PRIVATE} is supported as an output/input format,
4921 that is, {@link android.graphics.ImageFormat#PRIVATE} is included in the lists of
4922 formats returned by {@link
4923 android.hardware.camera2.params.StreamConfigurationMap#getInputFormats} and {@link
4924 android.hardware.camera2.params.StreamConfigurationMap#getOutputFormats}.
4925 * {@link android.hardware.camera2.params.StreamConfigurationMap#getValidOutputFormatsForInput}
4926 returns non empty int[] for each supported input format returned by {@link
4927 android.hardware.camera2.params.StreamConfigurationMap#getInputFormats}.
4928 * Each size returned by {@link
4929 android.hardware.camera2.params.StreamConfigurationMap#getInputSizes
4930 getInputSizes(ImageFormat.PRIVATE)} is also included in {@link
4931 android.hardware.camera2.params.StreamConfigurationMap#getOutputSizes
4932 getOutputSizes(ImageFormat.PRIVATE)}
4933 * Using {@link android.graphics.ImageFormat#PRIVATE} does not cause a frame rate drop
4934 relative to the sensor's maximum capture rate (at that resolution).
4935 * {@link android.graphics.ImageFormat#PRIVATE} will be reprocessable into both
4936 {@link android.graphics.ImageFormat#YUV_420_888} and
4937 {@link android.graphics.ImageFormat#JPEG} formats.
4938 * The maximum available resolution for PRIVATE streams
4939 (both input/output) will match the maximum available
4940 resolution of JPEG streams.
4941 * Static metadata android.reprocess.maxCaptureStall.
4942 * Only below controls are effective for reprocessing requests and
4943 will be present in capture results, other controls in reprocess
4944 requests will be ignored by the camera device.
4946 * android.noiseReduction.mode
4948 * android.noiseReduction.availableNoiseReductionModes and
4949 android.edge.availableEdgeModes will both list ZERO_SHUTTER_LAG as a supported mode.
4952 <value optional="true">READ_SENSOR_SETTINGS
4954 The camera device supports accurately reporting the sensor settings for many of
4955 the sensor controls while the built-in 3A algorithm is running. This allows
4956 reporting of sensor settings even when these settings cannot be manually changed.
4958 The values reported for the following controls are guaranteed to be available
4959 in the CaptureResult, including when 3A is enabled:
4962 * android.sensor.exposureTime
4963 * Sensitivity control
4964 * android.sensor.sensitivity
4965 * Lens controls (if the lens is adjustable)
4966 * android.lens.focusDistance
4967 * android.lens.aperture
4969 This capability is a subset of the MANUAL_SENSOR control capability, and will
4970 always be included if the MANUAL_SENSOR capability is available.
4973 <value optional="true">BURST_CAPTURE
4975 The camera device supports capturing high-resolution images at >= 20 frames per
4976 second, in at least the uncompressed YUV format, when post-processing settings are set
4977 to FAST. Additionally, maximum-resolution images can be captured at >= 10 frames
4978 per second. Here, 'high resolution' means at least 8 megapixels, or the maximum
4979 resolution of the device, whichever is smaller.
4982 More specifically, this means that a size matching the camera device's active array
4983 size is listed as a supported size for the {@link
4984 android.graphics.ImageFormat#YUV_420_888} format in either {@link
4985 android.hardware.camera2.params.StreamConfigurationMap#getOutputSizes} or {@link
4986 android.hardware.camera2.params.StreamConfigurationMap#getHighResolutionOutputSizes},
4987 with a minimum frame duration for that format and size of either <= 1/20 s, or
4988 <= 1/10 s, respectively; and the android.control.aeAvailableTargetFpsRanges entry
4989 lists at least one FPS range where the minimum FPS is >= 1 / minimumFrameDuration
4990 for the maximum-size YUV_420_888 format. If that maximum size is listed in {@link
4991 android.hardware.camera2.params.StreamConfigurationMap#getHighResolutionOutputSizes},
4992 then the list of resolutions for YUV_420_888 from {@link
4993 android.hardware.camera2.params.StreamConfigurationMap#getOutputSizes} contains at
4994 least one resolution >= 8 megapixels, with a minimum frame duration of <= 1/20
4997 If the device supports the {@link
4998 android.graphics.ImageFormat#RAW10|AIMAGE_FORMAT_RAW10}, {@link
4999 android.graphics.ImageFormat#RAW12|AIMAGE_FORMAT_RAW12}, then those can also be
5000 captured at the same rate as the maximum-size YUV_420_888 resolution is.
5002 If the device supports the PRIVATE_REPROCESSING capability, then the same guarantees
5003 as for the YUV_420_888 format also apply to the {@link
5004 android.graphics.ImageFormat#PRIVATE} format.
5006 In addition, the android.sync.maxLatency field is guaranted to have a value between 0
5007 and 4, inclusive. android.control.aeLockAvailable and android.control.awbLockAvailable
5008 are also guaranteed to be `true` so burst capture with these two locks ON yields
5009 consistent image output.
5012 More specifically, this means that at least one output {@link
5013 android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888} size listed in
5015 android.hardware.camera2.params.StreamConfigurationMap|ACAMERA_SCALER_AVAILABLE_STREAM_CONFIGURATIONS}
5016 is larger or equal to the 'high resolution' defined above, and can be captured at at
5017 least 20 fps. For the largest {@link
5018 android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888} size listed in
5020 android.hardware.camera2.params.StreamConfigurationMap|ACAMERA_SCALER_AVAILABLE_STREAM_CONFIGURATIONS},
5021 camera device can capture this size for at least 10 frames per second. Also the
5022 android.control.aeAvailableTargetFpsRanges entry lists at least one FPS range where
5023 the minimum FPS is >= 1 / minimumFrameDuration for the largest YUV_420_888 size.
5025 If the device supports the {@link
5026 android.graphics.ImageFormat#RAW10|AIMAGE_FORMAT_RAW10}, {@link
5027 android.graphics.ImageFormat#RAW12|AIMAGE_FORMAT_RAW12}, then those can also be
5028 captured at the same rate as the maximum-size YUV_420_888 resolution is.
5030 In addition, the android.sync.maxLatency field is guaranted to have a value between 0
5031 and 4, inclusive. android.control.aeLockAvailable and android.control.awbLockAvailable
5032 are also guaranteed to be `true` so burst capture with these two locks ON yields
5033 consistent image output.
5036 <value optional="true" ndk_hidden="true">YUV_REPROCESSING
5038 The camera device supports the YUV_420_888 reprocessing use case, similar as
5039 PRIVATE_REPROCESSING, This capability requires the camera device to support the
5042 * One input stream is supported, that is, `android.request.maxNumInputStreams == 1`.
5043 * {@link android.graphics.ImageFormat#YUV_420_888} is supported as an output/input
5044 format, that is, YUV_420_888 is included in the lists of formats returned by {@link
5045 android.hardware.camera2.params.StreamConfigurationMap#getInputFormats} and {@link
5046 android.hardware.camera2.params.StreamConfigurationMap#getOutputFormats}.
5048 android.hardware.camera2.params.StreamConfigurationMap#getValidOutputFormatsForInput}
5049 returns non-empty int[] for each supported input format returned by {@link
5050 android.hardware.camera2.params.StreamConfigurationMap#getInputFormats}.
5051 * Each size returned by {@link
5052 android.hardware.camera2.params.StreamConfigurationMap#getInputSizes
5053 getInputSizes(YUV_420_888)} is also included in {@link
5054 android.hardware.camera2.params.StreamConfigurationMap#getOutputSizes
5055 getOutputSizes(YUV_420_888)}
5056 * Using {@link android.graphics.ImageFormat#YUV_420_888} does not cause a frame rate
5057 drop relative to the sensor's maximum capture rate (at that resolution).
5058 * {@link android.graphics.ImageFormat#YUV_420_888} will be reprocessable into both
5059 {@link android.graphics.ImageFormat#YUV_420_888} and {@link
5060 android.graphics.ImageFormat#JPEG} formats.
5061 * The maximum available resolution for {@link
5062 android.graphics.ImageFormat#YUV_420_888} streams (both input/output) will match the
5063 maximum available resolution of {@link android.graphics.ImageFormat#JPEG} streams.
5064 * Static metadata android.reprocess.maxCaptureStall.
5065 * Only the below controls are effective for reprocessing requests and will be present
5066 in capture results. The reprocess requests are from the original capture results
5067 that are associated with the intermediate {@link
5068 android.graphics.ImageFormat#YUV_420_888} output buffers. All other controls in the
5069 reprocess requests will be ignored by the camera device.
5071 * android.noiseReduction.mode
5073 * android.reprocess.effectiveExposureFactor
5074 * android.noiseReduction.availableNoiseReductionModes and
5075 android.edge.availableEdgeModes will both list ZERO_SHUTTER_LAG as a supported mode.
5078 <value optional="true">DEPTH_OUTPUT
5080 The camera device can produce depth measurements from its field of view.
5082 This capability requires the camera device to support the following:
5084 * {@link android.graphics.ImageFormat#DEPTH16|AIMAGE_FORMAT_DEPTH16} is supported as
5087 android.graphics.ImageFormat#DEPTH_POINT_CLOUD|AIMAGE_FORMAT_DEPTH_POINT_CLOUD} is
5088 optionally supported as an output format.
5089 * This camera device, and all camera devices with the same android.lens.facing, will
5090 list the following calibration metadata entries in both {@link
5091 android.hardware.camera2.CameraCharacteristics|ACameraManager_getCameraCharacteristics}
5093 android.hardware.camera2.CaptureResult|ACameraCaptureSession_captureCallback_result}:
5094 - android.lens.poseTranslation
5095 - android.lens.poseRotation
5096 - android.lens.intrinsicCalibration
5097 - android.lens.distortion
5098 * The android.depth.depthIsExclusive entry is listed by this device.
5099 * As of Android P, the android.lens.poseReference entry is listed by this device.
5100 * A LIMITED camera with only the DEPTH_OUTPUT capability does not have to support
5101 normal YUV_420_888, JPEG, and PRIV-format outputs. It only has to support the DEPTH16
5104 Generally, depth output operates at a slower frame rate than standard color capture,
5105 so the DEPTH16 and DEPTH_POINT_CLOUD formats will commonly have a stall duration that
5106 should be accounted for (see {@link
5107 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration|ACAMERA_DEPTH_AVAILABLE_DEPTH_STALL_DURATIONS}).
5108 On a device that supports both depth and color-based output, to enable smooth preview,
5109 using a repeating burst is recommended, where a depth-output target is only included
5110 once every N frames, where N is the ratio between preview output rate and depth output
5111 rate, including depth stall time.
5114 <value optional="true" ndk_hidden="true">CONSTRAINED_HIGH_SPEED_VIDEO
5116 The device supports constrained high speed video recording (frame rate >=120fps) use
5117 case. The camera device will support high speed capture session created by {@link
5118 android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}, which
5119 only accepts high speed request lists created by {@link
5120 android.hardware.camera2.CameraConstrainedHighSpeedCaptureSession#createHighSpeedRequestList}.
5122 A camera device can still support high speed video streaming by advertising the high
5123 speed FPS ranges in android.control.aeAvailableTargetFpsRanges. For this case, all
5124 normal capture request per frame control and synchronization requirements will apply
5125 to the high speed fps ranges, the same as all other fps ranges. This capability
5126 describes the capability of a specialized operating mode with many limitations (see
5127 below), which is only targeted at high speed video recording.
5129 The supported high speed video sizes and fps ranges are specified in {@link
5130 android.hardware.camera2.params.StreamConfigurationMap#getHighSpeedVideoFpsRanges}.
5131 To get desired output frame rates, the application is only allowed to select video
5132 size and FPS range combinations provided by {@link
5133 android.hardware.camera2.params.StreamConfigurationMap#getHighSpeedVideoSizes}. The
5134 fps range can be controlled via android.control.aeTargetFpsRange.
5136 In this capability, the camera device will override aeMode, awbMode, and afMode to
5137 ON, AUTO, and CONTINUOUS_VIDEO, respectively. All post-processing block mode
5138 controls will be overridden to be FAST. Therefore, no manual control of capture
5139 and post-processing parameters is possible. All other controls operate the
5140 same as when android.control.mode == AUTO. This means that all other
5141 android.control.* fields continue to work, such as
5143 * android.control.aeTargetFpsRange
5144 * android.control.aeExposureCompensation
5145 * android.control.aeLock
5146 * android.control.awbLock
5147 * android.control.effectMode
5148 * android.control.aeRegions
5149 * android.control.afRegions
5150 * android.control.awbRegions
5151 * android.control.afTrigger
5152 * android.control.aePrecaptureTrigger
5154 Outside of android.control.*, the following controls will work:
5156 * android.flash.mode (TORCH mode only, automatic flash for still capture will not
5157 work since aeMode is ON)
5158 * android.lens.opticalStabilizationMode (if it is supported)
5159 * android.scaler.cropRegion
5160 * android.statistics.faceDetectMode (if it is supported)
5162 For high speed recording use case, the actual maximum supported frame rate may
5163 be lower than what camera can output, depending on the destination Surfaces for
5164 the image data. For example, if the destination surface is from video encoder,
5165 the application need check if the video encoder is capable of supporting the
5166 high frame rate for a given video size, or it will end up with lower recording
5167 frame rate. If the destination surface is from preview window, the actual preview frame
5168 rate will be bounded by the screen refresh rate.
5170 The camera device will only support up to 2 high speed simultaneous output surfaces
5171 (preview and recording surfaces) in this mode. Above controls will be effective only
5172 if all of below conditions are true:
5174 * The application creates a camera capture session with no more than 2 surfaces via
5176 android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}. The
5177 targeted surfaces must be preview surface (either from {@link
5178 android.view.SurfaceView} or {@link android.graphics.SurfaceTexture}) or recording
5179 surface(either from {@link android.media.MediaRecorder#getSurface} or {@link
5180 android.media.MediaCodec#createInputSurface}).
5181 * The stream sizes are selected from the sizes reported by
5182 {@link android.hardware.camera2.params.StreamConfigurationMap#getHighSpeedVideoSizes}.
5183 * The FPS ranges are selected from {@link
5184 android.hardware.camera2.params.StreamConfigurationMap#getHighSpeedVideoFpsRanges}.
5186 When above conditions are NOT satistied,
5187 {@link android.hardware.camera2.CameraDevice#createConstrainedHighSpeedCaptureSession}
5190 Switching to a FPS range that has different maximum FPS may trigger some camera device
5191 reconfigurations, which may introduce extra latency. It is recommended that
5192 the application avoids unnecessary maximum target FPS changes as much as possible
5193 during high speed streaming.
5196 <value optional="true" hal_version="3.3" >MOTION_TRACKING
5198 The camera device supports the MOTION_TRACKING value for
5199 android.control.captureIntent, which limits maximum exposure time to 20 ms.
5201 This limits the motion blur of capture images, resulting in better image tracking
5202 results for use cases such as image stabilization or augmented reality.
5205 <value optional="true" hal_version="3.3">LOGICAL_MULTI_CAMERA
5207 The camera device is a logical camera backed by two or more physical cameras that are
5208 also exposed to the application.
5210 This capability requires the camera device to support the following:
5212 * This camera device must list the following static metadata entries in {@link
5213 android.hardware.camera2.CameraCharacteristics}:
5214 - android.logicalMultiCamera.physicalIds
5215 - android.logicalMultiCamera.sensorSyncType
5216 * The underlying physical cameras' static metadata must list the following entries,
5217 so that the application can correlate pixels from the physical streams:
5218 - android.lens.poseReference
5219 - android.lens.poseRotation
5220 - android.lens.poseTranslation
5221 - android.lens.intrinsicCalibration
5222 - android.lens.distortion
5223 * The SENSOR_INFO_TIMESTAMP_SOURCE of the logical device and physical devices must be
5225 * The logical camera device must be LIMITED or higher device.
5227 Both the logical camera device and its underlying physical devices support the
5228 mandatory stream combinations required for their device levels.
5230 Additionally, for each guaranteed stream combination, the logical camera supports:
5232 * For each guaranteed stream combination, the logical camera supports replacing one
5233 logical {@link android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888 YUV_420_888}
5234 or raw stream with two physical streams of the same size and format, each from a
5235 separate physical camera, given that the size and format are supported by both
5237 * If the logical camera doesn't advertise RAW capability, but the underlying physical
5238 cameras do, the logical camera will support guaranteed stream combinations for RAW
5239 capability, except that the RAW streams will be physical streams, each from a separate
5240 physical camera. This is usually the case when the physical cameras have different
5243 Using physical streams in place of a logical stream of the same size and format will
5244 not slow down the frame rate of the capture, as long as the minimum frame duration
5245 of the physical and logical streams are the same.
5250 <description>List of capabilities that this camera device
5251 advertises as fully supporting.</description>
5253 A capability is a contract that the camera device makes in order
5254 to be able to satisfy one or more use cases.
5256 Listing a capability guarantees that the whole set of features
5257 required to support a common use will all be available.
5259 Using a subset of the functionality provided by an unsupported
5260 capability may be possible on a specific camera device implementation;
5261 to do this query each of android.request.availableRequestKeys,
5262 android.request.availableResultKeys,
5263 android.request.availableCharacteristicsKeys.
5265 The following capabilities are guaranteed to be available on
5266 android.info.supportedHardwareLevel `==` FULL devices:
5269 * MANUAL_POST_PROCESSING
5271 Other capabilities may be available on either FULL or LIMITED
5272 devices, but the application should query this key to be sure.
5275 Additional constraint details per-capability will be available
5276 in the Compatibility Test Suite.
5278 Minimum baseline requirements required for the
5279 BACKWARD_COMPATIBLE capability are not explicitly listed.
5280 Instead refer to "BC" tags and the camera CTS tests in the
5281 android.hardware.camera2.cts package.
5283 Listed controls that can be either request or result (e.g.
5284 android.sensor.exposureTime) must be available both in the
5285 request and the result in order to be considered to be
5286 capability-compliant.
5288 For example, if the HAL claims to support MANUAL control,
5289 then exposure time must be configurable via the request _and_
5290 the actual exposure applied must be available via
5293 If MANUAL_SENSOR is omitted, the HAL may choose to omit the
5294 android.scaler.availableMinFrameDurations static property entirely.
5296 For PRIVATE_REPROCESSING and YUV_REPROCESSING capabilities, see
5297 hardware/libhardware/include/hardware/camera3.h Section 10 for more information.
5299 Devices that support the MANUAL_SENSOR capability must support the
5300 CAMERA3_TEMPLATE_MANUAL template defined in camera3.h.
5302 Devices that support the PRIVATE_REPROCESSING capability or the
5303 YUV_REPROCESSING capability must support the
5304 CAMERA3_TEMPLATE_ZERO_SHUTTER_LAG template defined in camera3.h.
5306 For DEPTH_OUTPUT, the depth-format keys
5307 android.depth.availableDepthStreamConfigurations,
5308 android.depth.availableDepthMinFrameDurations,
5309 android.depth.availableDepthStallDurations must be available, in
5310 addition to the other keys explicitly mentioned in the DEPTH_OUTPUT
5311 enum notes. The entry android.depth.maxDepthSamples must be available
5312 if the DEPTH_POINT_CLOUD format is supported (HAL pixel format BLOB, dataspace
5315 For a camera device with LOGICAL_MULTI_CAMERA capability, it should operate in the
5316 same way as a physical camera device based on its hardware level and capabilities.
5317 It's recommended that its feature set is superset of that of individual physical cameras.
5320 <entry name="availableRequestKeys" type="int32" visibility="ndk_public"
5321 container="array" hwlevel="legacy">
5325 <description>A list of all keys that the camera device has available
5326 to use with {@link android.hardware.camera2.CaptureRequest|ACaptureRequest}.</description>
5328 <details>Attempting to set a key into a CaptureRequest that is not
5329 listed here will result in an invalid request and will be rejected
5330 by the camera device.
5332 This field can be used to query the feature set of a camera device
5333 at a more granular level than capabilities. This is especially
5334 important for optional keys that are not listed under any capability
5335 in android.request.availableCapabilities.
5338 Vendor tags can be listed here. Vendor tag metadata should also
5339 use the extensions C api (refer to camera3.h for more details).
5341 Setting/getting vendor tags will be checked against the metadata
5342 vendor extensions API and not against this field.
5344 The HAL must not consume any request tags that are not listed either
5345 here or in the vendor tag list.
5347 The public camera2 API will always make the vendor tags visible
5349 {@link android.hardware.camera2.CameraCharacteristics#getAvailableCaptureRequestKeys}.
5352 <entry name="availableResultKeys" type="int32" visibility="ndk_public"
5353 container="array" hwlevel="legacy">
5357 <description>A list of all keys that the camera device has available to use with {@link
5358 android.hardware.camera2.CaptureResult|ACameraCaptureSession_captureCallback_result}.
5361 <details>Attempting to get a key from a CaptureResult that is not
5362 listed here will always return a `null` value. Getting a key from
5363 a CaptureResult that is listed here will generally never return a `null`
5366 The following keys may return `null` unless they are enabled:
5368 * android.statistics.lensShadingMap (non-null iff android.statistics.lensShadingMapMode == ON)
5370 (Those sometimes-null keys will nevertheless be listed here
5371 if they are available.)
5373 This field can be used to query the feature set of a camera device
5374 at a more granular level than capabilities. This is especially
5375 important for optional keys that are not listed under any capability
5376 in android.request.availableCapabilities.
5379 Tags listed here must always have an entry in the result metadata,
5380 even if that size is 0 elements. Only array-type tags (e.g. lists,
5381 matrices, strings) are allowed to have 0 elements.
5383 Vendor tags can be listed here. Vendor tag metadata should also
5384 use the extensions C api (refer to camera3.h for more details).
5386 Setting/getting vendor tags will be checked against the metadata
5387 vendor extensions API and not against this field.
5389 The HAL must not produce any result tags that are not listed either
5390 here or in the vendor tag list.
5392 The public camera2 API will always make the vendor tags visible via {@link
5393 android.hardware.camera2.CameraCharacteristics#getAvailableCaptureResultKeys}.
5396 <entry name="availableCharacteristicsKeys" type="int32" visibility="ndk_public"
5397 container="array" hwlevel="legacy">
5401 <description>A list of all keys that the camera device has available to use with {@link
5402 android.hardware.camera2.CameraCharacteristics|ACameraManager_getCameraCharacteristics}.
5404 <details>This entry follows the same rules as
5405 android.request.availableResultKeys (except that it applies for
5406 CameraCharacteristics instead of CaptureResult). See above for more
5410 Keys listed here must always have an entry in the static info metadata,
5411 even if that size is 0 elements. Only array-type tags (e.g. lists,
5412 matrices, strings) are allowed to have 0 elements.
5414 Vendor tags can listed here. Vendor tag metadata should also use
5415 the extensions C api (refer to camera3.h for more details).
5417 Setting/getting vendor tags will be checked against the metadata
5418 vendor extensions API and not against this field.
5420 The HAL must not have any tags in its static info that are not listed
5421 either here or in the vendor tag list.
5423 The public camera2 API will always make the vendor tags visible
5424 via {@link android.hardware.camera2.CameraCharacteristics#getKeys}.
5427 <entry name="availableSessionKeys" type="int32" visibility="ndk_public"
5428 container="array" hwlevel="legacy" hal_version="3.3">
5432 <description>A subset of the available request keys that the camera device
5433 can pass as part of the capture session initialization.</description>
5435 <details> This is a subset of android.request.availableRequestKeys which
5436 contains a list of keys that are difficult to apply per-frame and
5437 can result in unexpected delays when modified during the capture session
5438 lifetime. Typical examples include parameters that require a
5439 time-consuming hardware re-configuration or internal camera pipeline
5440 change. For performance reasons we advise clients to pass their initial
5442 {@link SessionConfiguration#setSessionParameters|ACameraDevice_createCaptureSessionWithSessionParameters}.
5443 Once the camera capture session is enabled it is also recommended to avoid
5444 changing them from their initial values set in
5445 {@link SessionConfiguration#setSessionParameters|ACameraDevice_createCaptureSessionWithSessionParameters}.
5446 Control over session parameters can still be exerted in capture requests
5447 but clients should be aware and expect delays during their application.
5448 An example usage scenario could look like this:
5450 * The camera client starts by quering the session parameter key list via
5451 {@link android.hardware.camera2.CameraCharacteristics#getAvailableSessionKeys|ACameraManager_getCameraCharacteristics}.
5452 * Before triggering the capture session create sequence, a capture request
5454 {@link CameraDevice#createCaptureRequest|ACameraDevice_createCaptureRequest}
5455 using an appropriate template matching the particular use case.
5456 * The client should go over the list of session parameters and check
5457 whether some of the keys listed matches with the parameters that
5458 they intend to modify as part of the first capture request.
5459 * If there is no such match, the capture request can be passed
5461 {@link SessionConfiguration#setSessionParameters|ACameraDevice_createCaptureSessionWithSessionParameters}.
5462 * If matches do exist, the client should update the respective values
5463 and pass the request to
5464 {@link SessionConfiguration#setSessionParameters|ACameraDevice_createCaptureSessionWithSessionParameters}.
5465 * After the capture session initialization completes the session parameter
5466 key list can continue to serve as reference when posting or updating
5467 further requests. As mentioned above further changes to session
5468 parameters should ideally be avoided, if updates are necessary
5469 however clients could expect a delay/glitch during the
5474 Vendor tags can be listed here. Vendor tag metadata should also
5475 use the extensions C api (refer to
5476 android.hardware.camera.device.V3_4.StreamConfiguration.sessionParams for more details).
5478 Setting/getting vendor tags will be checked against the metadata
5479 vendor extensions API and not against this field.
5481 The HAL must not consume any request tags in the session parameters that
5482 are not listed either here or in the vendor tag list.
5484 The public camera2 API will always make the vendor tags visible
5486 {@link android.hardware.camera2.CameraCharacteristics#getAvailableSessionKeys}.
5489 <entry name="availablePhysicalCameraRequestKeys" type="int32" visibility="hidden"
5490 container="array" hwlevel="limited" hal_version="3.3">
5494 <description>A subset of the available request keys that can be overriden for
5495 physical devices backing a logical multi-camera.</description>
5497 This is a subset of android.request.availableRequestKeys which contains a list
5498 of keys that can be overriden using {@link CaptureRequest.Builder#setPhysicalCameraKey}.
5499 The respective value of such request key can be obtained by calling
5500 {@link CaptureRequest.Builder#getPhysicalCameraKey}. Capture requests that contain
5501 individual physical device requests must be built via
5502 {@link android.hardware.camera2.CameraDevice#createCaptureRequest(int, Set)}.
5505 Vendor tags can be listed here. Vendor tag metadata should also
5506 use the extensions C api (refer to
5507 android.hardware.camera.device.V3_4.CaptureRequest.physicalCameraSettings for more
5510 Setting/getting vendor tags will be checked against the metadata
5511 vendor extensions API and not against this field.
5513 The HAL must not consume any request tags in the session parameters that
5514 are not listed either here or in the vendor tag list.
5516 There should be no overlap between this set of keys and the available session keys
5517 {@link android.hardware.camera2.CameraCharacteristics#getAvailableSessionKeys} along
5518 with any other controls that can have impact on the dual-camera sync.
5520 The public camera2 API will always make the vendor tags visible
5522 {@link android.hardware.camera2.CameraCharacteristics#getAvailablePhysicalCameraRequestKeys}.
5527 <section name="scaler">
5529 <entry name="cropRegion" type="int32" visibility="public"
5530 container="array" typedef="rectangle" hwlevel="legacy">
5534 <description>The desired region of the sensor to read out for this capture.</description>
5535 <units>Pixel coordinates relative to
5536 android.sensor.info.activeArraySize</units>
5538 This control can be used to implement digital zoom.
5540 The crop region coordinate system is based off
5541 android.sensor.info.activeArraySize, with `(0, 0)` being the
5542 top-left corner of the sensor active array.
5544 Output streams use this rectangle to produce their output,
5545 cropping to a smaller region if necessary to maintain the
5546 stream's aspect ratio, then scaling the sensor input to
5547 match the output's configured resolution.
5549 The crop region is applied after the RAW to other color
5550 space (e.g. YUV) conversion. Since raw streams
5551 (e.g. RAW16) don't have the conversion stage, they are not
5552 croppable. The crop region will be ignored by raw streams.
5554 For non-raw streams, any additional per-stream cropping will
5555 be done to maximize the final pixel area of the stream.
5557 For example, if the crop region is set to a 4:3 aspect
5558 ratio, then 4:3 streams will use the exact crop
5559 region. 16:9 streams will further crop vertically
5562 Conversely, if the crop region is set to a 16:9, then 4:3
5563 outputs will crop horizontally (pillarbox), and 16:9
5564 streams will match exactly. These additional crops will
5565 be centered within the crop region.
5567 The width and height of the crop region cannot
5568 be set to be smaller than
5569 `floor( activeArraySize.width / android.scaler.availableMaxDigitalZoom )` and
5570 `floor( activeArraySize.height / android.scaler.availableMaxDigitalZoom )`, respectively.
5572 The camera device may adjust the crop region to account
5573 for rounding and other hardware requirements; the final
5574 crop region used will be included in the output capture
5578 The data representation is int[4], which maps to (left, top, width, height).
5581 The output streams must maintain square pixels at all
5582 times, no matter what the relative aspect ratios of the
5583 crop region and the stream are. Negative values for
5584 corner are allowed for raw output if full pixel array is
5585 larger than active pixel array. Width and height may be
5586 rounded to nearest larger supportable width, especially
5587 for raw output, where only a few fixed scales may be
5590 For a set of output streams configured, if the sensor output is cropped to a smaller
5591 size than active array size, the HAL need follow below cropping rules:
5593 * The HAL need handle the cropRegion as if the sensor crop size is the effective active
5594 array size.More specifically, the HAL must transform the request cropRegion from
5595 android.sensor.info.activeArraySize to the sensor cropped pixel area size in this way:
5596 1. Translate the requested cropRegion w.r.t., the left top corner of the sensor
5597 cropped pixel area by (tx, ty),
5598 where `tx = sensorCrop.top * (sensorCrop.height / activeArraySize.height)`
5599 and `tx = sensorCrop.left * (sensorCrop.width / activeArraySize.width)`. The
5600 (sensorCrop.top, sensorCrop.left) is the coordinate based off the
5601 android.sensor.info.activeArraySize.
5602 2. Scale the width and height of requested cropRegion with scaling factor of
5603 sensorCrop.width/activeArraySize.width and sensorCrop.height/activeArraySize.height
5605 Once this new cropRegion is calculated, the HAL must use this region to crop the image
5606 with regard to the sensor crop size (effective active array size). The HAL still need
5607 follow the general cropping rule for this new cropRegion and effective active
5610 * The HAL must report the cropRegion with regard to android.sensor.info.activeArraySize.
5611 The HAL need convert the new cropRegion generated above w.r.t., full active array size.
5612 The reported cropRegion may be slightly different with the requested cropRegion since
5613 the HAL may adjust the crop region to account for rounding, conversion error, or other
5614 hardware limitations.
5616 HAL2.x uses only (x, y, width)
5622 <entry name="availableFormats" type="int32"
5623 visibility="hidden" deprecated="true" enum="true"
5624 container="array" typedef="imageFormat">
5629 <value optional="true" id="0x20">RAW16
5631 RAW16 is a standard, cross-platform format for raw image
5632 buffers with 16-bit pixels.
5634 Buffers of this format are typically expected to have a
5635 Bayer Color Filter Array (CFA) layout, which is given in
5636 android.sensor.info.colorFilterArrangement. Sensors with
5637 CFAs that are not representable by a format in
5638 android.sensor.info.colorFilterArrangement should not
5641 Buffers of this format will also follow the constraints given for
5642 RAW_OPAQUE buffers, but with relaxed performance constraints.
5644 This format is intended to give users access to the full contents
5645 of the buffers coming directly from the image sensor prior to any
5646 cropping or scaling operations, and all coordinate systems for
5647 metadata used for this format are relative to the size of the
5648 active region of the image sensor before any geometric distortion
5649 correction has been applied (i.e.
5650 android.sensor.info.preCorrectionActiveArraySize). Supported
5651 dimensions for this format are limited to the full dimensions of
5652 the sensor (e.g. either android.sensor.info.pixelArraySize or
5653 android.sensor.info.preCorrectionActiveArraySize will be the
5654 only supported output size).
5656 See android.scaler.availableInputOutputFormatsMap for
5657 the full set of performance guarantees.
5660 <value optional="true" id="0x24">RAW_OPAQUE
5663 {@link android.graphics.ImageFormat#RAW_PRIVATE RAW_PRIVATE}
5664 as referred in public API) is a format for raw image buffers
5665 coming from an image sensor.
5667 The actual structure of buffers of this format is
5668 platform-specific, but must follow several constraints:
5670 1. No image post-processing operations may have been applied to
5671 buffers of this type. These buffers contain raw image data coming
5672 directly from the image sensor.
5673 1. If a buffer of this format is passed to the camera device for
5674 reprocessing, the resulting images will be identical to the images
5675 produced if the buffer had come directly from the sensor and was
5676 processed with the same settings.
5678 The intended use for this format is to allow access to the native
5679 raw format buffers coming directly from the camera sensor without
5680 any additional conversions or decrease in framerate.
5682 See android.scaler.availableInputOutputFormatsMap for the full set of
5683 performance guarantees.
5686 <value optional="true" id="0x32315659">YV12
5687 <notes>YCrCb 4:2:0 Planar</notes>
5689 <value optional="true" id="0x11">YCrCb_420_SP
5692 <value id="0x22">IMPLEMENTATION_DEFINED
5693 <notes>System internal format, not application-accessible</notes>
5695 <value id="0x23">YCbCr_420_888
5696 <notes>Flexible YUV420 Format</notes>
5698 <value id="0x21">BLOB
5699 <notes>JPEG format</notes>
5702 <description>The list of image formats that are supported by this
5703 camera device for output streams.</description>
5704 <deprecation_description>
5705 Not used in HALv3 or newer
5706 </deprecation_description>
5708 All camera devices will support JPEG and YUV_420_888 formats.
5710 When set to YUV_420_888, application can access the YUV420 data directly.
5713 These format values are from HAL_PIXEL_FORMAT_* in
5714 system/core/include/system/graphics.h.
5716 When IMPLEMENTATION_DEFINED is used, the platform
5717 gralloc module will select a format based on the usage flags provided
5718 by the camera HAL device and the other endpoint of the stream. It is
5719 usually used by preview and recording streams, where the application doesn't
5720 need access the image data.
5722 YCbCr_420_888 format must be supported by the HAL. When an image stream
5723 needs CPU/application direct access, this format will be used.
5725 The BLOB format must be supported by the HAL. This is used for the JPEG stream.
5727 A RAW_OPAQUE buffer should contain only pixel data. It is strongly
5728 recommended that any information used by the camera device when
5729 processing images is fully expressed by the result metadata
5730 for that image buffer.
5734 <entry name="availableJpegMinDurations" type="int64" visibility="hidden" deprecated="true"
5739 <description>The minimum frame duration that is supported
5740 for each resolution in android.scaler.availableJpegSizes.
5742 <deprecation_description>
5743 Not used in HALv3 or newer
5744 </deprecation_description>
5745 <units>Nanoseconds</units>
5746 <range>TODO: Remove property.</range>
5748 This corresponds to the minimum steady-state frame duration when only
5749 that JPEG stream is active and captured in a burst, with all
5750 processing (typically in android.*.mode) set to FAST.
5752 When multiple streams are configured, the minimum
5753 frame duration will be &gt;= max(individual stream min
5754 durations)</details>
5757 <entry name="availableJpegSizes" type="int32" visibility="hidden"
5758 deprecated="true" container="array" typedef="size">
5763 <description>The JPEG resolutions that are supported by this camera device.</description>
5764 <deprecation_description>
5765 Not used in HALv3 or newer
5766 </deprecation_description>
5767 <range>TODO: Remove property.</range>
5769 The resolutions are listed as `(width, height)` pairs. All camera devices will support
5770 sensor maximum resolution (defined by android.sensor.info.activeArraySize).
5773 The HAL must include sensor maximum resolution
5774 (defined by android.sensor.info.activeArraySize),
5775 and should include half/quarter of sensor maximum resolution.
5779 <entry name="availableMaxDigitalZoom" type="float" visibility="public"
5781 <description>The maximum ratio between both active area width
5782 and crop region width, and active area height and
5783 crop region height, for android.scaler.cropRegion.
5785 <units>Zoom scale factor</units>
5786 <range>&gt;=1</range>
5788 This represents the maximum amount of zooming possible by
5789 the camera device, or equivalently, the minimum cropping
5792 Crop regions that have a width or height that is smaller
5793 than this ratio allows will be rounded up to the minimum
5794 allowed size by the camera device.
5798 <entry name="availableProcessedMinDurations" type="int64" visibility="hidden" deprecated="true"
5803 <description>For each available processed output size (defined in
5804 android.scaler.availableProcessedSizes), this property lists the
5805 minimum supportable frame duration for that size.
5807 <deprecation_description>
5808 Not used in HALv3 or newer
5809 </deprecation_description>
5810 <units>Nanoseconds</units>
5812 This should correspond to the frame duration when only that processed
5813 stream is active, with all processing (typically in android.*.mode)
5816 When multiple streams are configured, the minimum frame duration will
5817 be &gt;= max(individual stream min durations).
5821 <entry name="availableProcessedSizes" type="int32" visibility="hidden"
5822 deprecated="true" container="array" typedef="size">
5827 <description>The resolutions available for use with
5828 processed output streams, such as YV12, NV12, and
5829 platform opaque YUV/RGB streams to the GPU or video
5830 encoders.</description>
5831 <deprecation_description>
5832 Not used in HALv3 or newer
5833 </deprecation_description>
5835 The resolutions are listed as `(width, height)` pairs.
5837 For a given use case, the actual maximum supported resolution
5838 may be lower than what is listed here, depending on the destination
5839 Surface for the image data. For example, for recording video,
5840 the video encoder chosen may have a maximum size limit (e.g. 1080p)
5841 smaller than what the camera (e.g. maximum resolution is 3264x2448)
5844 Please reference the documentation for the image data destination to
5845 check if it limits the maximum size for image data.
5848 For FULL capability devices (`android.info.supportedHardwareLevel == FULL`),
5849 the HAL must include all JPEG sizes listed in android.scaler.availableJpegSizes
5850 and each below resolution if it is smaller than or equal to the sensor
5851 maximum resolution (if they are not listed in JPEG sizes already):
5856 * 1080p (1920 x 1080)
5858 For LIMITED capability devices (`android.info.supportedHardwareLevel == LIMITED`),
5859 the HAL only has to list up to the maximum video size supported by the devices.
5863 <entry name="availableRawMinDurations" type="int64" deprecated="true"
5869 For each available raw output size (defined in
5870 android.scaler.availableRawSizes), this property lists the minimum
5871 supportable frame duration for that size.
5873 <deprecation_description>
5874 Not used in HALv3 or newer
5875 </deprecation_description>
5876 <units>Nanoseconds</units>
5878 Should correspond to the frame duration when only the raw stream is
5881 When multiple streams are configured, the minimum
5882 frame duration will be &gt;= max(individual stream min
5883 durations)</details>
5886 <entry name="availableRawSizes" type="int32" deprecated="true"
5887 container="array" typedef="size">
5892 <description>The resolutions available for use with raw
5893 sensor output streams, listed as width,
5894 height</description>
5895 <deprecation_description>
5896 Not used in HALv3 or newer
5897 </deprecation_description>
5901 <clone entry="android.scaler.cropRegion" kind="controls">
5905 <entry name="availableInputOutputFormatsMap" type="int32" visibility="hidden"
5906 typedef="reprocessFormatsMap">
5907 <description>The mapping of image formats that are supported by this
5908 camera device for input streams, to their corresponding output formats.
5911 All camera devices with at least 1
5912 android.request.maxNumInputStreams will have at least one
5913 available input format.
5915 The camera device will support the following map of formats,
5916 if its dependent capability (android.request.availableCapabilities) is supported:
5918 Input Format | Output Format | Capability
5919 :-------------------------------------------------|:--------------------------------------------------|:----------
5920 {@link android.graphics.ImageFormat#PRIVATE} | {@link android.graphics.ImageFormat#JPEG} | PRIVATE_REPROCESSING
5921 {@link android.graphics.ImageFormat#PRIVATE} | {@link android.graphics.ImageFormat#YUV_420_888} | PRIVATE_REPROCESSING
5922 {@link android.graphics.ImageFormat#YUV_420_888} | {@link android.graphics.ImageFormat#JPEG} | YUV_REPROCESSING
5923 {@link android.graphics.ImageFormat#YUV_420_888} | {@link android.graphics.ImageFormat#YUV_420_888} | YUV_REPROCESSING
5925 PRIVATE refers to a device-internal format that is not directly application-visible. A
5926 PRIVATE input surface can be acquired by {@link android.media.ImageReader#newInstance}
5927 with {@link android.graphics.ImageFormat#PRIVATE} as the format.
5929 For a PRIVATE_REPROCESSING-capable camera device, using the PRIVATE format as either input
5930 or output will never hurt maximum frame rate (i.e. {@link
5931 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration
5932 getOutputStallDuration(ImageFormat.PRIVATE, size)} is always 0),
5934 Attempting to configure an input stream with output streams not
5935 listed as available in this map is not valid.
5938 For the formats, see `system/core/include/system/graphics.h` for a definition
5939 of the image format enumerations. The PRIVATE format refers to the
5940 HAL_PIXEL_FORMAT_IMPLEMENTATION_DEFINED format. The HAL could determine
5941 the actual format by using the gralloc usage flags.
5942 For ZSL use case in particular, the HAL could choose appropriate format (partially
5943 processed YUV or RAW based format) by checking the format and GRALLOC_USAGE_HW_CAMERA_ZSL.
5944 See camera3.h for more details.
5946 This value is encoded as a variable-size array-of-arrays.
5947 The inner array always contains `[format, length, ...]` where
5948 `...` has `length` elements. An inner array is followed by another
5949 inner array if the total metadata entry size hasn't yet been exceeded.
5951 A code sample to read/write this encoding (with a device that
5952 supports reprocessing IMPLEMENTATION_DEFINED to YUV_420_888, and JPEG,
5953 and reprocessing YUV_420_888 to YUV_420_888 and JPEG):
5956 int32_t* contents = &entry.i32[0];
5957 for (size_t i = 0; i < entry.count; ) {
5958 int32_t format = contents[i++];
5959 int32_t length = contents[i++];
5960 int32_t output_formats[length];
5961 memcpy(&output_formats[0], &contents[i],
5962 length * sizeof(int32_t));
5966 // writing (static example, PRIVATE_REPROCESSING + YUV_REPROCESSING)
5967 int32_t[] contents = {
5968 IMPLEMENTATION_DEFINED, 2, YUV_420_888, BLOB,
5969 YUV_420_888, 2, YUV_420_888, BLOB,
5971 update_camera_metadata_entry(metadata, index, &contents[0],
5972 sizeof(contents)/sizeof(contents[0]), &updated_entry);
5974 If the HAL claims to support any of the capabilities listed in the
5975 above details, then it must also support all the input-output
5976 combinations listed for that capability. It can optionally support
5977 additional formats if it so chooses.
5981 <entry name="availableStreamConfigurations" type="int32" visibility="ndk_public"
5982 enum="true" container="array" typedef="streamConfiguration" hwlevel="legacy">
5988 <value>OUTPUT</value>
5989 <value>INPUT</value>
5991 <description>The available stream configurations that this
5992 camera device supports
5993 (i.e. format, width, height, output/input stream).
5996 The configurations are listed as `(format, width, height, input?)`
5999 For a given use case, the actual maximum supported resolution
6000 may be lower than what is listed here, depending on the destination
6001 Surface for the image data. For example, for recording video,
6002 the video encoder chosen may have a maximum size limit (e.g. 1080p)
6003 smaller than what the camera (e.g. maximum resolution is 3264x2448)
6006 Please reference the documentation for the image data destination to
6007 check if it limits the maximum size for image data.
6009 Not all output formats may be supported in a configuration with
6010 an input stream of a particular format. For more details, see
6011 android.scaler.availableInputOutputFormatsMap.
6013 The following table describes the minimum required output stream
6014 configurations based on the hardware level
6015 (android.info.supportedHardwareLevel):
6017 Format | Size | Hardware Level | Notes
6018 :-------------:|:--------------------------------------------:|:--------------:|:--------------:
6019 JPEG | android.sensor.info.activeArraySize | Any |
6020 JPEG | 1920x1080 (1080p) | Any | if 1080p <= activeArraySize
6021 JPEG | 1280x720 (720) | Any | if 720p <= activeArraySize
6022 JPEG | 640x480 (480p) | Any | if 480p <= activeArraySize
6023 JPEG | 320x240 (240p) | Any | if 240p <= activeArraySize
6024 YUV_420_888 | all output sizes available for JPEG | FULL |
6025 YUV_420_888 | all output sizes available for JPEG, up to the maximum video size | LIMITED |
6026 IMPLEMENTATION_DEFINED | same as YUV_420_888 | Any |
6028 Refer to android.request.availableCapabilities for additional
6029 mandatory stream configurations on a per-capability basis.
6032 It is recommended (but not mandatory) to also include half/quarter
6033 of sensor maximum resolution for JPEG formats (regardless of hardware
6036 (The following is a rewording of the above required table):
6038 For JPEG format, the sizes may be restricted by below conditions:
6040 * The HAL may choose the aspect ratio of each Jpeg size to be one of well known ones
6041 (e.g. 4:3, 16:9, 3:2 etc.). If the sensor maximum resolution
6042 (defined by android.sensor.info.activeArraySize) has an aspect ratio other than these,
6043 it does not have to be included in the supported JPEG sizes.
6044 * Some hardware JPEG encoders may have pixel boundary alignment requirements, such as
6045 the dimensions being a multiple of 16.
6047 Therefore, the maximum JPEG size may be smaller than sensor maximum resolution.
6048 However, the largest JPEG size must be as close as possible to the sensor maximum
6049 resolution given above constraints. It is required that after aspect ratio adjustments,
6050 additional size reduction due to other issues must be less than 3% in area. For example,
6051 if the sensor maximum resolution is 3280x2464, if the maximum JPEG size has aspect
6052 ratio 4:3, the JPEG encoder alignment requirement is 16, the maximum JPEG size will be
6055 For FULL capability devices (`android.info.supportedHardwareLevel == FULL`),
6056 the HAL must include all YUV_420_888 sizes that have JPEG sizes listed
6057 here as output streams.
6059 It must also include each below resolution if it is smaller than or
6060 equal to the sensor maximum resolution (for both YUV_420_888 and JPEG
6061 formats), as output streams:
6066 * 1080p (1920 x 1080)
6068 For LIMITED capability devices
6069 (`android.info.supportedHardwareLevel == LIMITED`),
6070 the HAL only has to list up to the maximum video size
6071 supported by the device.
6073 Regardless of hardware level, every output resolution available for
6074 YUV_420_888 must also be available for IMPLEMENTATION_DEFINED.
6076 This supercedes the following fields, which are now deprecated:
6079 * available[Processed,Raw,Jpeg]Sizes
6082 <entry name="availableMinFrameDurations" type="int64" visibility="ndk_public"
6083 container="array" typedef="streamConfigurationDuration" hwlevel="legacy">
6088 <description>This lists the minimum frame duration for each
6089 format/size combination.
6091 <units>(format, width, height, ns) x n</units>
6093 This should correspond to the frame duration when only that
6094 stream is active, with all processing (typically in android.*.mode)
6095 set to either OFF or FAST.
6097 When multiple streams are used in a request, the minimum frame
6098 duration will be max(individual stream min durations).
6100 The minimum frame duration of a stream (of a particular format, size)
6101 is the same regardless of whether the stream is input or output.
6103 See android.sensor.frameDuration and
6104 android.scaler.availableStallDurations for more details about
6105 calculating the max frame rate.
6109 <entry name="availableStallDurations" type="int64" visibility="ndk_public"
6110 container="array" typedef="streamConfigurationDuration" hwlevel="legacy">
6115 <description>This lists the maximum stall duration for each
6116 output format/size combination.
6118 <units>(format, width, height, ns) x n</units>
6120 A stall duration is how much extra time would get added
6121 to the normal minimum frame duration for a repeating request
6122 that has streams with non-zero stall.
6124 For example, consider JPEG captures which have the following
6127 * JPEG streams act like processed YUV streams in requests for which
6128 they are not included; in requests in which they are directly
6129 referenced, they act as JPEG streams. This is because supporting a
6130 JPEG stream requires the underlying YUV data to always be ready for
6131 use by a JPEG encoder, but the encoder will only be used (and impact
6132 frame duration) on requests that actually reference a JPEG stream.
6133 * The JPEG processor can run concurrently to the rest of the camera
6134 pipeline, but cannot process more than 1 capture at a time.
6136 In other words, using a repeating YUV request would result
6137 in a steady frame rate (let's say it's 30 FPS). If a single
6138 JPEG request is submitted periodically, the frame rate will stay
6139 at 30 FPS (as long as we wait for the previous JPEG to return each
6140 time). If we try to submit a repeating YUV + JPEG request, then
6141 the frame rate will drop from 30 FPS.
6143 In general, submitting a new request with a non-0 stall time
6144 stream will _not_ cause a frame rate drop unless there are still
6145 outstanding buffers for that stream from previous requests.
6147 Submitting a repeating request with streams (call this `S`)
6148 is the same as setting the minimum frame duration from
6149 the normal minimum frame duration corresponding to `S`, added with
6150 the maximum stall duration for `S`.
6152 If interleaving requests with and without a stall duration,
6153 a request will stall by the maximum of the remaining times
6154 for each can-stall stream with outstanding buffers.
6156 This means that a stalling request will not have an exposure start
6157 until the stall has completed.
6159 This should correspond to the stall duration when only that stream is
6160 active, with all processing (typically in android.*.mode) set to FAST
6161 or OFF. Setting any of the processing modes to HIGH_QUALITY
6162 effectively results in an indeterminate stall duration for all
6163 streams in a request (the regular stall calculation rules are
6166 The following formats may always have a stall duration:
6168 * {@link android.graphics.ImageFormat#JPEG|AIMAGE_FORMAT_JPEG}
6169 * {@link android.graphics.ImageFormat#RAW_SENSOR|AIMAGE_FORMAT_RAW16}
6171 The following formats will never have a stall duration:
6173 * {@link android.graphics.ImageFormat#YUV_420_888|AIMAGE_FORMAT_YUV_420_888}
6174 * {@link android.graphics.ImageFormat#RAW10|AIMAGE_FORMAT_RAW10}
6175 * {@link android.graphics.ImageFormat#RAW12|AIMAGE_FORMAT_RAW12}
6177 All other formats may or may not have an allowed stall duration on
6178 a per-capability basis; refer to android.request.availableCapabilities
6181 See android.sensor.frameDuration for more information about
6182 calculating the max frame rate (absent stalls).
6185 If possible, it is recommended that all non-JPEG formats
6186 (such as RAW16) should not have a stall duration. RAW10, RAW12, RAW_OPAQUE
6187 and IMPLEMENTATION_DEFINED must not have stall durations.
6191 <entry name="streamConfigurationMap" type="int32" visibility="java_public"
6192 synthetic="true" typedef="streamConfigurationMap"
6194 <description>The available stream configurations that this
6195 camera device supports; also includes the minimum frame durations
6196 and the stall durations for each format/size combination.
6199 All camera devices will support sensor maximum resolution (defined by
6200 android.sensor.info.activeArraySize) for the JPEG format.
6202 For a given use case, the actual maximum supported resolution
6203 may be lower than what is listed here, depending on the destination
6204 Surface for the image data. For example, for recording video,
6205 the video encoder chosen may have a maximum size limit (e.g. 1080p)
6206 smaller than what the camera (e.g. maximum resolution is 3264x2448)
6209 Please reference the documentation for the image data destination to
6210 check if it limits the maximum size for image data.
6212 The following table describes the minimum required output stream
6213 configurations based on the hardware level
6214 (android.info.supportedHardwareLevel):
6216 Format | Size | Hardware Level | Notes
6217 :-------------------------------------------------:|:--------------------------------------------:|:--------------:|:--------------:
6218 {@link android.graphics.ImageFormat#JPEG} | android.sensor.info.activeArraySize (*1) | Any |
6219 {@link android.graphics.ImageFormat#JPEG} | 1920x1080 (1080p) | Any | if 1080p <= activeArraySize
6220 {@link android.graphics.ImageFormat#JPEG} | 1280x720 (720p) | Any | if 720p <= activeArraySize
6221 {@link android.graphics.ImageFormat#JPEG} | 640x480 (480p) | Any | if 480p <= activeArraySize
6222 {@link android.graphics.ImageFormat#JPEG} | 320x240 (240p) | Any | if 240p <= activeArraySize
6223 {@link android.graphics.ImageFormat#YUV_420_888} | all output sizes available for JPEG | FULL |
6224 {@link android.graphics.ImageFormat#YUV_420_888} | all output sizes available for JPEG, up to the maximum video size | LIMITED |
6225 {@link android.graphics.ImageFormat#PRIVATE} | same as YUV_420_888 | Any |
6227 Refer to android.request.availableCapabilities and {@link
6228 android.hardware.camera2.CameraDevice#createCaptureSession} for additional mandatory
6229 stream configurations on a per-capability basis.
6231 *1: For JPEG format, the sizes may be restricted by below conditions:
6233 * The HAL may choose the aspect ratio of each Jpeg size to be one of well known ones
6234 (e.g. 4:3, 16:9, 3:2 etc.). If the sensor maximum resolution
6235 (defined by android.sensor.info.activeArraySize) has an aspect ratio other than these,
6236 it does not have to be included in the supported JPEG sizes.
6237 * Some hardware JPEG encoders may have pixel boundary alignment requirements, such as
6238 the dimensions being a multiple of 16.
6239 Therefore, the maximum JPEG size may be smaller than sensor maximum resolution.
6240 However, the largest JPEG size will be as close as possible to the sensor maximum
6241 resolution given above constraints. It is required that after aspect ratio adjustments,
6242 additional size reduction due to other issues must be less than 3% in area. For example,
6243 if the sensor maximum resolution is 3280x2464, if the maximum JPEG size has aspect
6244 ratio 4:3, and the JPEG encoder alignment requirement is 16, the maximum JPEG size will be
6248 Do not set this property directly
6249 (it is synthetic and will not be available at the HAL layer);
6250 set the android.scaler.availableStreamConfigurations instead.
6252 Not all output formats may be supported in a configuration with
6253 an input stream of a particular format. For more details, see
6254 android.scaler.availableInputOutputFormatsMap.
6256 It is recommended (but not mandatory) to also include half/quarter
6257 of sensor maximum resolution for JPEG formats (regardless of hardware
6260 (The following is a rewording of the above required table):
6262 The HAL must include sensor maximum resolution (defined by
6263 android.sensor.info.activeArraySize).
6265 For FULL capability devices (`android.info.supportedHardwareLevel == FULL`),
6266 the HAL must include all YUV_420_888 sizes that have JPEG sizes listed
6267 here as output streams.
6269 It must also include each below resolution if it is smaller than or
6270 equal to the sensor maximum resolution (for both YUV_420_888 and JPEG
6271 formats), as output streams:
6276 * 1080p (1920 x 1080)
6278 For LIMITED capability devices
6279 (`android.info.supportedHardwareLevel == LIMITED`),
6280 the HAL only has to list up to the maximum video size
6281 supported by the device.
6283 Regardless of hardware level, every output resolution available for
6284 YUV_420_888 must also be available for IMPLEMENTATION_DEFINED.
6286 This supercedes the following fields, which are now deprecated:
6289 * available[Processed,Raw,Jpeg]Sizes
6292 <entry name="croppingType" type="byte" visibility="public" enum="true"
6297 The camera device only supports centered crop regions.
6302 The camera device supports arbitrarily chosen crop regions.
6306 <description>The crop type that this camera device supports.</description>
6308 When passing a non-centered crop region (android.scaler.cropRegion) to a camera
6309 device that only supports CENTER_ONLY cropping, the camera device will move the
6310 crop region to the center of the sensor active array (android.sensor.info.activeArraySize)
6311 and keep the crop region width and height unchanged. The camera device will return the
6312 final used crop region in metadata result android.scaler.cropRegion.
6314 Camera devices that support FREEFORM cropping will support any crop region that
6315 is inside of the active array. The camera device will apply the same crop region and
6316 return the final used crop region in capture result metadata android.scaler.cropRegion.
6318 LEGACY capability devices will only support CENTER_ONLY cropping.
6323 <section name="sensor">
6325 <entry name="exposureTime" type="int64" visibility="public" hwlevel="full">
6326 <description>Duration each pixel is exposed to
6327 light.</description>
6328 <units>Nanoseconds</units>
6329 <range>android.sensor.info.exposureTimeRange</range>
6330 <details>If the sensor can't expose this exact duration, it will shorten the
6331 duration exposed to the nearest possible value (rather than expose longer).
6332 The final exposure time used will be available in the output capture result.
6334 This control is only effective if android.control.aeMode or android.control.mode is set to
6335 OFF; otherwise the auto-exposure algorithm will override this value.
6339 <entry name="frameDuration" type="int64" visibility="public" hwlevel="full">
6340 <description>Duration from start of frame exposure to
6341 start of next frame exposure.</description>
6342 <units>Nanoseconds</units>
6343 <range>See android.sensor.info.maxFrameDuration, {@link
6344 android.hardware.camera2.params.StreamConfigurationMap|ACAMERA_SCALER_AVAILABLE_MIN_FRAME_DURATIONS}.
6345 The duration is capped to `max(duration, exposureTime + overhead)`.</range>
6347 The maximum frame rate that can be supported by a camera subsystem is
6348 a function of many factors:
6350 * Requested resolutions of output image streams
6351 * Availability of binning / skipping modes on the imager
6352 * The bandwidth of the imager interface
6353 * The bandwidth of the various ISP processing blocks
6355 Since these factors can vary greatly between different ISPs and
6356 sensors, the camera abstraction tries to represent the bandwidth
6357 restrictions with as simple a model as possible.
6359 The model presented has the following characteristics:
6361 * The image sensor is always configured to output the smallest
6362 resolution possible given the application's requested output stream
6363 sizes. The smallest resolution is defined as being at least as large
6364 as the largest requested output stream size; the camera pipeline must
6365 never digitally upsample sensor data when the crop region covers the
6366 whole sensor. In general, this means that if only small output stream
6367 resolutions are configured, the sensor can provide a higher frame
6369 * Since any request may use any or all the currently configured
6370 output streams, the sensor and ISP must be configured to support
6371 scaling a single capture to all the streams at the same time. This
6372 means the camera pipeline must be ready to produce the largest
6373 requested output size without any delay. Therefore, the overall
6374 frame rate of a given configured stream set is governed only by the
6375 largest requested stream resolution.
6376 * Using more than one output stream in a request does not affect the
6378 * Certain format-streams may need to do additional background processing
6379 before data is consumed/produced by that stream. These processors
6380 can run concurrently to the rest of the camera pipeline, but
6381 cannot process more than 1 capture at a time.
6383 The necessary information for the application, given the model above, is provided via
6385 android.hardware.camera2.params.StreamConfigurationMap#getOutputMinFrameDuration|ACAMERA_SCALER_AVAILABLE_MIN_FRAME_DURATIONS}.
6386 These are used to determine the maximum frame rate / minimum frame duration that is
6387 possible for a given stream configuration.
6389 Specifically, the application can use the following rules to
6390 determine the minimum frame duration it can request from the camera
6393 1. Let the set of currently configured input/output streams be called `S`.
6394 1. Find the minimum frame durations for each stream in `S`, by looking it up in {@link
6395 android.hardware.camera2.params.StreamConfigurationMap#getOutputMinFrameDuration|ACAMERA_SCALER_AVAILABLE_MIN_FRAME_DURATIONS}
6396 (with its respective size/format). Let this set of frame durations be called `F`.
6397 1. For any given request `R`, the minimum frame duration allowed for `R` is the maximum
6398 out of all values in `F`. Let the streams used in `R` be called `S_r`.
6400 If none of the streams in `S_r` have a stall time (listed in {@link
6401 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration|ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS}
6402 using its respective size/format), then the frame duration in `F` determines the steady
6403 state frame rate that the application will get if it uses `R` as a repeating request. Let
6404 this special kind of request be called `Rsimple`.
6406 A repeating request `Rsimple` can be _occasionally_ interleaved by a single capture of a
6407 new request `Rstall` (which has at least one in-use stream with a non-0 stall time) and if
6408 `Rstall` has the same minimum frame duration this will not cause a frame rate loss if all
6409 buffers from the previous `Rstall` have already been delivered.
6411 For more details about stalling, see {@link
6412 android.hardware.camera2.params.StreamConfigurationMap#getOutputStallDuration|ACAMERA_SCALER_AVAILABLE_STALL_DURATIONS}.
6414 This control is only effective if android.control.aeMode or android.control.mode is set to
6415 OFF; otherwise the auto-exposure algorithm will override this value.
6418 For more details about stalling, see
6419 android.scaler.availableStallDurations.
6423 <entry name="sensitivity" type="int32" visibility="public" hwlevel="full">
6424 <description>The amount of gain applied to sensor data
6425 before processing.</description>
6426 <units>ISO arithmetic units</units>
6427 <range>android.sensor.info.sensitivityRange</range>
6429 The sensitivity is the standard ISO sensitivity value,
6430 as defined in ISO 12232:2006.
6432 The sensitivity must be within android.sensor.info.sensitivityRange, and
6433 if if it less than android.sensor.maxAnalogSensitivity, the camera device
6434 is guaranteed to use only analog amplification for applying the gain.
6436 If the camera device cannot apply the exact sensitivity
6437 requested, it will reduce the gain to the nearest supported
6438 value. The final sensitivity used will be available in the
6439 output capture result.
6441 This control is only effective if android.control.aeMode or android.control.mode is set to
6442 OFF; otherwise the auto-exposure algorithm will override this value.
6444 <hal_details>ISO 12232:2006 REI method is acceptable.</hal_details>
6449 <namespace name="info">
6450 <entry name="activeArraySize" type="int32" visibility="public"
6451 type_notes="Four ints defining the active pixel rectangle"
6452 container="array" typedef="rectangle" hwlevel="legacy">
6457 The area of the image sensor which corresponds to active pixels after any geometric
6458 distortion correction has been applied.
6460 <units>Pixel coordinates on the image sensor</units>
6462 This is the rectangle representing the size of the active region of the sensor (i.e.
6463 the region that actually receives light from the scene) after any geometric correction
6464 has been applied, and should be treated as the maximum size in pixels of any of the
6465 image output formats aside from the raw formats.
6467 This rectangle is defined relative to the full pixel array; (0,0) is the top-left of
6468 the full pixel array, and the size of the full pixel array is given by
6469 android.sensor.info.pixelArraySize.
6471 The coordinate system for most other keys that list pixel coordinates, including
6472 android.scaler.cropRegion, is defined relative to the active array rectangle given in
6473 this field, with `(0, 0)` being the top-left of this rectangle.
6475 The active array may be smaller than the full pixel array, since the full array may
6476 include black calibration pixels or other inactive regions, and geometric correction
6477 resulting in scaling or cropping may have been applied.
6480 The data representation is `int[4]`, which maps to `(left, top, width, height)`.
6483 This array contains `(xmin, ymin, width, height)`. The `(xmin, ymin)` must be
6485 The `(width, height)` must be &lt;= `android.sensor.info.pixelArraySize`.
6489 <entry name="sensitivityRange" type="int32" visibility="public"
6490 type_notes="Range of supported sensitivities"
6491 container="array" typedef="rangeInt"
6496 <description>Range of sensitivities for android.sensor.sensitivity supported by this
6497 camera device.</description>
6498 <range>Min <= 100, Max &gt;= 800</range>
6500 The values are the standard ISO sensitivity values,
6501 as defined in ISO 12232:2006.
6507 <entry name="colorFilterArrangement" type="byte" visibility="public" enum="true"
6515 <notes>Sensor is not Bayer; output has 3 16-bit
6516 values for each pixel, instead of just 1 16-bit value
6517 per pixel.</notes></value>
6519 <description>The arrangement of color filters on sensor;
6520 represents the colors in the top-left 2x2 section of
6521 the sensor, in reading order.</description>
6524 <entry name="exposureTimeRange" type="int64" visibility="public"
6525 type_notes="nanoseconds" container="array" typedef="rangeLong"
6530 <description>The range of image exposure times for android.sensor.exposureTime supported
6531 by this camera device.
6533 <units>Nanoseconds</units>
6534 <range>The minimum exposure time will be less than 100 us. For FULL
6535 capability devices (android.info.supportedHardwareLevel == FULL),
6536 the maximum exposure time will be greater than 100ms.</range>
6537 <hal_details>For FULL capability devices (android.info.supportedHardwareLevel == FULL),
6538 The maximum of the range SHOULD be at least 1 second (1e9), MUST be at least
6543 <entry name="maxFrameDuration" type="int64" visibility="public"
6545 <description>The maximum possible frame duration (minimum frame rate) for
6546 android.sensor.frameDuration that is supported this camera device.</description>
6547 <units>Nanoseconds</units>
6548 <range>For FULL capability devices
6549 (android.info.supportedHardwareLevel == FULL), at least 100ms.
6551 <details>Attempting to use frame durations beyond the maximum will result in the frame
6552 duration being clipped to the maximum. See that control for a full definition of frame
6556 android.hardware.camera2.params.StreamConfigurationMap#getOutputMinFrameDuration|ACAMERA_SCALER_AVAILABLE_MIN_FRAME_DURATIONS}
6557 for the minimum frame duration values.
6560 For FULL capability devices (android.info.supportedHardwareLevel == FULL),
6561 The maximum of the range SHOULD be at least
6562 1 second (1e9), MUST be at least 100ms (100e6).
6564 android.sensor.info.maxFrameDuration must be greater or
6565 equal to the android.sensor.info.exposureTimeRange max
6566 value (since exposure time overrides frame duration).
6568 Available minimum frame durations for JPEG must be no greater
6569 than that of the YUV_420_888/IMPLEMENTATION_DEFINED
6570 minimum frame durations (for that respective size).
6572 Since JPEG processing is considered offline and can take longer than
6573 a single uncompressed capture, refer to
6574 android.scaler.availableStallDurations
6575 for details about encoding this scenario.
6579 <entry name="physicalSize" type="float" visibility="public"
6580 type_notes="width x height"
6581 container="array" typedef="sizeF" hwlevel="legacy">
6585 <description>The physical dimensions of the full pixel
6586 array.</description>
6587 <units>Millimeters</units>
6588 <details>This is the physical size of the sensor pixel
6589 array defined by android.sensor.info.pixelArraySize.
6591 <hal_details>Needed for FOV calculation for old API</hal_details>
6595 <entry name="pixelArraySize" type="int32" visibility="public"
6596 container="array" typedef="size" hwlevel="legacy">
6600 <description>Dimensions of the full pixel array, possibly
6601 including black calibration pixels.</description>
6602 <units>Pixels</units>
6603 <details>The pixel count of the full pixel array of the image sensor, which covers
6604 android.sensor.info.physicalSize area. This represents the full pixel dimensions of
6605 the raw buffers produced by this sensor.
6607 If a camera device supports raw sensor formats, either this or
6608 android.sensor.info.preCorrectionActiveArraySize is the maximum dimensions for the raw
6609 output formats listed in {@link
6610 android.hardware.camera2.params.StreamConfigurationMap|ACAMERA_SCALER_AVAILABLE_STREAM_CONFIGURATIONS}
6611 (this depends on whether or not the image sensor returns buffers containing pixels that
6612 are not part of the active array region for blacklevel calibration or other purposes).
6614 Some parts of the full pixel array may not receive light from the scene,
6615 or be otherwise inactive. The android.sensor.info.preCorrectionActiveArraySize key
6616 defines the rectangle of active pixels that will be included in processed image
6622 <entry name="whiteLevel" type="int32" visibility="public">
6624 Maximum raw value output by sensor.
6626 <range>&gt; 255 (8-bit output)</range>
6628 This specifies the fully-saturated encoding level for the raw
6629 sample values from the sensor. This is typically caused by the
6630 sensor becoming highly non-linear or clipping. The minimum for
6631 each channel is specified by the offset in the
6632 android.sensor.blackLevelPattern key.
6634 The white level is typically determined either by sensor bit depth
6635 (8-14 bits is expected), or by the point where the sensor response
6636 becomes too non-linear to be useful. The default value for this is
6637 maximum representable value for a 16-bit raw sample (2^16 - 1).
6639 The white level values of captured images may vary for different
6640 capture settings (e.g., android.sensor.sensitivity). This key
6641 represents a coarse approximation for such case. It is recommended
6642 to use android.sensor.dynamicWhiteLevel for captures when supported
6643 by the camera device, which provides more accurate white level values.
6646 The full bit depth of the sensor must be available in the raw data,
6647 so the value for linear sensors should not be significantly lower
6648 than maximum raw value supported, i.e. 2^(sensor bits per pixel).
6652 <entry name="timestampSource" type="byte" visibility="public"
6653 enum="true" hwlevel="legacy">
6657 Timestamps from android.sensor.timestamp are in nanoseconds and monotonic,
6658 but can not be compared to timestamps from other subsystems
6659 (e.g. accelerometer, gyro etc.), or other instances of the same or different
6660 camera devices in the same system. Timestamps between streams and results for
6661 a single camera instance are comparable, and the timestamps for all buffers
6662 and the result metadata generated by a single capture are identical.
6667 Timestamps from android.sensor.timestamp are in the same timebase as
6668 {@link android.os.SystemClock#elapsedRealtimeNanos},
6669 and they can be compared to other timestamps using that base.
6673 <description>The time base source for sensor capture start timestamps.</description>
6675 The timestamps provided for captures are always in nanoseconds and monotonic, but
6676 may not based on a time source that can be compared to other system time sources.
6678 This characteristic defines the source for the timestamps, and therefore whether they
6679 can be compared against other system time sources/timestamps.
6682 For camera devices implement UNKNOWN, the camera framework expects that the timestamp
6683 source to be SYSTEM_TIME_MONOTONIC. For camera devices implement REALTIME, the camera
6684 framework expects that the timestamp source to be SYSTEM_TIME_BOOTTIME. See
6685 system/core/include/utils/Timers.h for the definition of SYSTEM_TIME_MONOTONIC and
6686 SYSTEM_TIME_BOOTTIME. Note that HAL must follow above expectation; otherwise video
6687 recording might suffer unexpected behavior.
6689 Also, camera devices which implement REALTIME must pass the ITS sensor fusion test which
6690 tests the alignment between camera timestamps and gyro sensor timestamps.
6694 <entry name="lensShadingApplied" type="byte" visibility="public" enum="true"
6697 <value>FALSE</value>
6700 <description>Whether the RAW images output from this camera device are subject to
6701 lens shading correction.</description>
6703 If TRUE, all images produced by the camera device in the RAW image formats will
6704 have lens shading correction already applied to it. If FALSE, the images will
6705 not be adjusted for lens shading correction.
6706 See android.request.maxNumOutputRaw for a list of RAW image formats.
6708 This key will be `null` for all devices do not report this information.
6709 Devices with RAW capability will always report this information in this key.
6712 <entry name="preCorrectionActiveArraySize" type="int32" visibility="public"
6713 type_notes="Four ints defining the active pixel rectangle" container="array"
6714 typedef="rectangle" hwlevel="legacy">
6719 The area of the image sensor which corresponds to active pixels prior to the
6720 application of any geometric distortion correction.
6722 <units>Pixel coordinates on the image sensor</units>
6724 This is the rectangle representing the size of the active region of the sensor (i.e.
6725 the region that actually receives light from the scene) before any geometric correction
6726 has been applied, and should be treated as the active region rectangle for any of the
6727 raw formats. All metadata associated with raw processing (e.g. the lens shading
6728 correction map, and radial distortion fields) treats the top, left of this rectangle as
6731 The size of this region determines the maximum field of view and the maximum number of
6732 pixels that an image from this sensor can contain, prior to the application of
6733 geometric distortion correction. The effective maximum pixel dimensions of a
6734 post-distortion-corrected image is given by the android.sensor.info.activeArraySize
6735 field, and the effective maximum field of view for a post-distortion-corrected image
6736 can be calculated by applying the geometric distortion correction fields to this
6737 rectangle, and cropping to the rectangle given in android.sensor.info.activeArraySize.
6739 E.g. to calculate position of a pixel, (x,y), in a processed YUV output image with the
6740 dimensions in android.sensor.info.activeArraySize given the position of a pixel,
6741 (x', y'), in the raw pixel array with dimensions give in
6742 android.sensor.info.pixelArraySize:
6744 1. Choose a pixel (x', y') within the active array region of the raw buffer given in
6745 android.sensor.info.preCorrectionActiveArraySize, otherwise this pixel is considered
6746 to be outside of the FOV, and will not be shown in the processed output image.
6747 1. Apply geometric distortion correction to get the post-distortion pixel coordinate,
6748 (x_i, y_i). When applying geometric correction metadata, note that metadata for raw
6749 buffers is defined relative to the top, left of the
6750 android.sensor.info.preCorrectionActiveArraySize rectangle.
6751 1. If the resulting corrected pixel coordinate is within the region given in
6752 android.sensor.info.activeArraySize, then the position of this pixel in the
6753 processed output image buffer is `(x_i - activeArray.left, y_i - activeArray.top)`,
6754 when the top, left coordinate of that buffer is treated as (0, 0).
6756 Thus, for pixel x',y' = (25, 25) on a sensor where android.sensor.info.pixelArraySize
6757 is (100,100), android.sensor.info.preCorrectionActiveArraySize is (10, 10, 100, 100),
6758 android.sensor.info.activeArraySize is (20, 20, 80, 80), and the geometric distortion
6759 correction doesn't change the pixel coordinate, the resulting pixel selected in
6760 pixel coordinates would be x,y = (25, 25) relative to the top,left of the raw buffer
6761 with dimensions given in android.sensor.info.pixelArraySize, and would be (5, 5)
6762 relative to the top,left of post-processed YUV output buffer with dimensions given in
6763 android.sensor.info.activeArraySize.
6765 The currently supported fields that correct for geometric distortion are:
6767 1. android.lens.distortion.
6769 If all of the geometric distortion fields are no-ops, this rectangle will be the same
6770 as the post-distortion-corrected rectangle given in
6771 android.sensor.info.activeArraySize.
6773 This rectangle is defined relative to the full pixel array; (0,0) is the top-left of
6774 the full pixel array, and the size of the full pixel array is given by
6775 android.sensor.info.pixelArraySize.
6777 The pre-correction active array may be smaller than the full pixel array, since the
6778 full array may include black calibration pixels or other inactive regions.
6781 The data representation is `int[4]`, which maps to `(left, top, width, height)`.
6784 This array contains `(xmin, ymin, width, height)`. The `(xmin, ymin)` must be
6786 The `(width, height)` must be &lt;= `android.sensor.info.pixelArraySize`.
6788 If omitted by the HAL implementation, the camera framework will assume that this is
6789 the same as the post-correction active array region given in
6790 android.sensor.info.activeArraySize.
6795 <entry name="referenceIlluminant1" type="byte" visibility="public"
6798 <value id="1">DAYLIGHT</value>
6799 <value id="2">FLUORESCENT</value>
6800 <value id="3">TUNGSTEN
6801 <notes>Incandescent light</notes>
6803 <value id="4">FLASH</value>
6804 <value id="9">FINE_WEATHER</value>
6805 <value id="10">CLOUDY_WEATHER</value>
6806 <value id="11">SHADE</value>
6807 <value id="12">DAYLIGHT_FLUORESCENT
6808 <notes>D 5700 - 7100K</notes>
6810 <value id="13">DAY_WHITE_FLUORESCENT
6811 <notes>N 4600 - 5400K</notes>
6813 <value id="14">COOL_WHITE_FLUORESCENT
6814 <notes>W 3900 - 4500K</notes>
6816 <value id="15">WHITE_FLUORESCENT
6817 <notes>WW 3200 - 3700K</notes>
6819 <value id="17">STANDARD_A</value>
6820 <value id="18">STANDARD_B</value>
6821 <value id="19">STANDARD_C</value>
6822 <value id="20">D55</value>
6823 <value id="21">D65</value>
6824 <value id="22">D75</value>
6825 <value id="23">D50</value>
6826 <value id="24">ISO_STUDIO_TUNGSTEN</value>
6829 The standard reference illuminant used as the scene light source when
6830 calculating the android.sensor.colorTransform1,
6831 android.sensor.calibrationTransform1, and
6832 android.sensor.forwardMatrix1 matrices.
6835 The values in this key correspond to the values defined for the
6836 EXIF LightSource tag. These illuminants are standard light sources
6837 that are often used calibrating camera devices.
6839 If this key is present, then android.sensor.colorTransform1,
6840 android.sensor.calibrationTransform1, and
6841 android.sensor.forwardMatrix1 will also be present.
6843 Some devices may choose to provide a second set of calibration
6844 information for improved quality, including
6845 android.sensor.referenceIlluminant2 and its corresponding matrices.
6848 The first reference illuminant (android.sensor.referenceIlluminant1)
6849 and corresponding matrices must be present to support the RAW capability
6852 When producing raw images with a color profile that has only been
6853 calibrated against a single light source, it is valid to omit
6854 android.sensor.referenceIlluminant2 along with the
6855 android.sensor.colorTransform2, android.sensor.calibrationTransform2,
6856 and android.sensor.forwardMatrix2 matrices.
6858 If only android.sensor.referenceIlluminant1 is included, it should be
6859 chosen so that it is representative of typical scene lighting. In
6860 general, D50 or DAYLIGHT will be chosen for this case.
6862 If both android.sensor.referenceIlluminant1 and
6863 android.sensor.referenceIlluminant2 are included, they should be
6864 chosen to represent the typical range of scene lighting conditions.
6865 In general, low color temperature illuminant such as Standard-A will
6866 be chosen for the first reference illuminant and a higher color
6867 temperature illuminant such as D65 will be chosen for the second
6868 reference illuminant.
6872 <entry name="referenceIlluminant2" type="byte" visibility="public">
6874 The standard reference illuminant used as the scene light source when
6875 calculating the android.sensor.colorTransform2,
6876 android.sensor.calibrationTransform2, and
6877 android.sensor.forwardMatrix2 matrices.
6879 <range>Any value listed in android.sensor.referenceIlluminant1</range>
6881 See android.sensor.referenceIlluminant1 for more details.
6883 If this key is present, then android.sensor.colorTransform2,
6884 android.sensor.calibrationTransform2, and
6885 android.sensor.forwardMatrix2 will also be present.
6889 <entry name="calibrationTransform1" type="rational"
6890 visibility="public" optional="true"
6891 type_notes="3x3 matrix in row-major-order" container="array"
6892 typedef="colorSpaceTransform">
6898 A per-device calibration transform matrix that maps from the
6899 reference sensor colorspace to the actual device sensor colorspace.
6902 This matrix is used to correct for per-device variations in the
6903 sensor colorspace, and is used for processing raw buffer data.
6905 The matrix is expressed as a 3x3 matrix in row-major-order, and
6906 contains a per-device calibration transform that maps colors
6907 from reference sensor color space (i.e. the "golden module"
6908 colorspace) into this camera device's native sensor color
6909 space under the first reference illuminant
6910 (android.sensor.referenceIlluminant1).
6914 <entry name="calibrationTransform2" type="rational"
6915 visibility="public" optional="true"
6916 type_notes="3x3 matrix in row-major-order" container="array"
6917 typedef="colorSpaceTransform">
6923 A per-device calibration transform matrix that maps from the
6924 reference sensor colorspace to the actual device sensor colorspace
6925 (this is the colorspace of the raw buffer data).
6928 This matrix is used to correct for per-device variations in the
6929 sensor colorspace, and is used for processing raw buffer data.
6931 The matrix is expressed as a 3x3 matrix in row-major-order, and
6932 contains a per-device calibration transform that maps colors
6933 from reference sensor color space (i.e. the "golden module"
6934 colorspace) into this camera device's native sensor color
6935 space under the second reference illuminant
6936 (android.sensor.referenceIlluminant2).
6938 This matrix will only be present if the second reference
6939 illuminant is present.
6943 <entry name="colorTransform1" type="rational"
6944 visibility="public" optional="true"
6945 type_notes="3x3 matrix in row-major-order" container="array"
6946 typedef="colorSpaceTransform">
6952 A matrix that transforms color values from CIE XYZ color space to
6953 reference sensor color space.
6956 This matrix is used to convert from the standard CIE XYZ color
6957 space to the reference sensor colorspace, and is used when processing
6960 The matrix is expressed as a 3x3 matrix in row-major-order, and
6961 contains a color transform matrix that maps colors from the CIE
6962 XYZ color space to the reference sensor color space (i.e. the
6963 "golden module" colorspace) under the first reference illuminant
6964 (android.sensor.referenceIlluminant1).
6966 The white points chosen in both the reference sensor color space
6967 and the CIE XYZ colorspace when calculating this transform will
6968 match the standard white point for the first reference illuminant
6969 (i.e. no chromatic adaptation will be applied by this transform).
6973 <entry name="colorTransform2" type="rational"
6974 visibility="public" optional="true"
6975 type_notes="3x3 matrix in row-major-order" container="array"
6976 typedef="colorSpaceTransform">
6982 A matrix that transforms color values from CIE XYZ color space to
6983 reference sensor color space.
6986 This matrix is used to convert from the standard CIE XYZ color
6987 space to the reference sensor colorspace, and is used when processing
6990 The matrix is expressed as a 3x3 matrix in row-major-order, and
6991 contains a color transform matrix that maps colors from the CIE
6992 XYZ color space to the reference sensor color space (i.e. the
6993 "golden module" colorspace) under the second reference illuminant
6994 (android.sensor.referenceIlluminant2).
6996 The white points chosen in both the reference sensor color space
6997 and the CIE XYZ colorspace when calculating this transform will
6998 match the standard white point for the second reference illuminant
6999 (i.e. no chromatic adaptation will be applied by this transform).
7001 This matrix will only be present if the second reference
7002 illuminant is present.
7006 <entry name="forwardMatrix1" type="rational"
7007 visibility="public" optional="true"
7008 type_notes="3x3 matrix in row-major-order" container="array"
7009 typedef="colorSpaceTransform">
7015 A matrix that transforms white balanced camera colors from the reference
7016 sensor colorspace to the CIE XYZ colorspace with a D50 whitepoint.
7019 This matrix is used to convert to the standard CIE XYZ colorspace, and
7020 is used when processing raw buffer data.
7022 This matrix is expressed as a 3x3 matrix in row-major-order, and contains
7023 a color transform matrix that maps white balanced colors from the
7024 reference sensor color space to the CIE XYZ color space with a D50 white
7027 Under the first reference illuminant (android.sensor.referenceIlluminant1)
7028 this matrix is chosen so that the standard white point for this reference
7029 illuminant in the reference sensor colorspace is mapped to D50 in the
7034 <entry name="forwardMatrix2" type="rational"
7035 visibility="public" optional="true"
7036 type_notes="3x3 matrix in row-major-order" container="array"
7037 typedef="colorSpaceTransform">
7043 A matrix that transforms white balanced camera colors from the reference
7044 sensor colorspace to the CIE XYZ colorspace with a D50 whitepoint.
7047 This matrix is used to convert to the standard CIE XYZ colorspace, and
7048 is used when processing raw buffer data.
7050 This matrix is expressed as a 3x3 matrix in row-major-order, and contains
7051 a color transform matrix that maps white balanced colors from the
7052 reference sensor color space to the CIE XYZ color space with a D50 white
7055 Under the second reference illuminant (android.sensor.referenceIlluminant2)
7056 this matrix is chosen so that the standard white point for this reference
7057 illuminant in the reference sensor colorspace is mapped to D50 in the
7060 This matrix will only be present if the second reference
7061 illuminant is present.
7065 <entry name="baseGainFactor" type="rational"
7067 <description>Gain factor from electrons to raw units when
7068 ISO=100</description>
7071 <entry name="blackLevelPattern" type="int32" visibility="public"
7072 optional="true" type_notes="2x2 raw count block" container="array"
7073 typedef="blackLevelPattern">
7078 A fixed black level offset for each of the color filter arrangement
7079 (CFA) mosaic channels.
7081 <range>&gt;= 0 for each.</range>
7083 This key specifies the zero light value for each of the CFA mosaic
7084 channels in the camera sensor. The maximal value output by the
7085 sensor is represented by the value in android.sensor.info.whiteLevel.
7087 The values are given in the same order as channels listed for the CFA
7088 layout key (see android.sensor.info.colorFilterArrangement), i.e. the
7089 nth value given corresponds to the black level offset for the nth
7090 color channel listed in the CFA.
7092 The black level values of captured images may vary for different
7093 capture settings (e.g., android.sensor.sensitivity). This key
7094 represents a coarse approximation for such case. It is recommended to
7095 use android.sensor.dynamicBlackLevel or use pixels from
7096 android.sensor.opticalBlackRegions directly for captures when
7097 supported by the camera device, which provides more accurate black
7098 level values. For raw capture in particular, it is recommended to use
7099 pixels from android.sensor.opticalBlackRegions to calculate black
7100 level values for each frame.
7103 The values are given in row-column scan order, with the first value
7104 corresponding to the element of the CFA in row=0, column=0.
7108 <entry name="maxAnalogSensitivity" type="int32" visibility="public"
7109 optional="true" hwlevel="full">
7110 <description>Maximum sensitivity that is implemented
7111 purely through analog gain.</description>
7112 <details>For android.sensor.sensitivity values less than or
7113 equal to this, all applied gain must be analog. For
7114 values above this, the gain applied can be a mix of analog and
7119 <entry name="orientation" type="int32" visibility="public"
7121 <description>Clockwise angle through which the output image needs to be rotated to be
7122 upright on the device screen in its native orientation.
7124 <units>Degrees of clockwise rotation; always a multiple of
7126 <range>0, 90, 180, 270</range>
7128 Also defines the direction of rolling shutter readout, which is from top to bottom in
7129 the sensor's coordinate system.
7133 <entry name="profileHueSatMapDimensions" type="int32"
7134 visibility="system" optional="true"
7135 type_notes="Number of samples for hue, saturation, and value"
7141 The number of input samples for each dimension of
7142 android.sensor.profileHueSatMap.
7146 Saturation &gt;= 2,
7150 The number of input samples for the hue, saturation, and value
7151 dimension of android.sensor.profileHueSatMap. The order of the
7152 dimensions given is hue, saturation, value; where hue is the 0th
7159 <clone entry="android.sensor.exposureTime" kind="controls">
7161 <clone entry="android.sensor.frameDuration"
7162 kind="controls"></clone>
7163 <clone entry="android.sensor.sensitivity" kind="controls">
7165 <entry name="timestamp" type="int64" visibility="public"
7167 <description>Time at start of exposure of first
7168 row of the image sensor active array, in nanoseconds.</description>
7169 <units>Nanoseconds</units>
7170 <range>&gt; 0</range>
7171 <details>The timestamps are also included in all image
7172 buffers produced for the same capture, and will be identical
7175 When android.sensor.info.timestampSource `==` UNKNOWN,
7176 the timestamps measure time since an unspecified starting point,
7177 and are monotonically increasing. They can be compared with the
7178 timestamps for other captures from the same camera device, but are
7179 not guaranteed to be comparable to any other time source.
7181 When android.sensor.info.timestampSource `==` REALTIME, the
7182 timestamps measure time in the same timebase as {@link
7183 android.os.SystemClock#elapsedRealtimeNanos}, and they can
7184 be compared to other timestamps from other subsystems that
7185 are using that base.
7187 For reprocessing, the timestamp will match the start of exposure of
7188 the input image, i.e. {@link CaptureResult#SENSOR_TIMESTAMP the
7189 timestamp} in the TotalCaptureResult that was used to create the
7190 reprocess capture request.
7193 All timestamps must be in reference to the kernel's
7194 CLOCK_BOOTTIME monotonic clock, which properly accounts for
7195 time spent asleep. This allows for synchronization with
7196 sensors that continue to operate while the system is
7199 If android.sensor.info.timestampSource `==` REALTIME,
7200 The timestamp must be synchronized with the timestamps from other
7201 sensor subsystems that are using the same timebase.
7203 For reprocessing, the input image's start of exposure can be looked up
7204 with android.sensor.timestamp from the metadata included in the
7209 <entry name="temperature" type="float"
7211 <description>The temperature of the sensor, sampled at the time
7212 exposure began for this frame.
7214 The thermal diode being queried should be inside the sensor PCB, or
7215 somewhere close to it.
7218 <units>Celsius</units>
7219 <range>Optional. This value is missing if no temperature is available.</range>
7222 <entry name="neutralColorPoint" type="rational" visibility="public"
7223 optional="true" container="array">
7228 The estimated camera neutral color in the native sensor colorspace at
7229 the time of capture.
7232 This value gives the neutral color point encoded as an RGB value in the
7233 native sensor color space. The neutral color point indicates the
7234 currently estimated white point of the scene illumination. It can be
7235 used to interpolate between the provided color transforms when
7236 processing raw sensor data.
7238 The order of the values is R, G, B; where R is in the lowest index.
7242 <entry name="noiseProfile" type="double" visibility="public"
7243 optional="true" type_notes="Pairs of noise model coefficients"
7244 container="array" typedef="pairDoubleDouble">
7247 <size>CFA Channels</size>
7250 Noise model coefficients for each CFA mosaic channel.
7253 This key contains two noise model coefficients for each CFA channel
7254 corresponding to the sensor amplification (S) and sensor readout
7255 noise (O). These are given as pairs of coefficients for each channel
7256 in the same order as channels listed for the CFA layout key
7257 (see android.sensor.info.colorFilterArrangement). This is
7258 represented as an array of Pair&lt;Double, Double&gt;, where
7259 the first member of the Pair at index n is the S coefficient and the
7260 second member is the O coefficient for the nth color channel in the CFA.
7262 These coefficients are used in a two parameter noise model to describe
7263 the amount of noise present in the image for each CFA channel. The
7264 noise model used here is:
7268 Where x represents the recorded signal of a CFA channel normalized to
7269 the range [0, 1], and S and O are the noise model coeffiecients for
7272 A more detailed description of the noise model can be found in the
7273 Adobe DNG specification for the NoiseProfile tag.
7276 For a CFA layout of RGGB, the list of coefficients would be given as
7277 an array of doubles S0,O0,S1,O1,..., where S0 and O0 are the coefficients
7278 for the red channel, S1 and O1 are the coefficients for the first green
7283 <entry name="profileHueSatMap" type="float"
7284 visibility="system" optional="true"
7285 type_notes="Mapping for hue, saturation, and value"
7288 <size>hue_samples</size>
7289 <size>saturation_samples</size>
7290 <size>value_samples</size>
7294 A mapping containing a hue shift, saturation scale, and value scale
7298 The hue shift is given in degrees; saturation and value scale factors are
7299 unitless and are between 0 and 1 inclusive
7302 hue_samples, saturation_samples, and value_samples are given in
7303 android.sensor.profileHueSatMapDimensions.
7305 Each entry of this map contains three floats corresponding to the
7306 hue shift, saturation scale, and value scale, respectively; where the
7307 hue shift has the lowest index. The map entries are stored in the key
7308 in nested loop order, with the value divisions in the outer loop, the
7309 hue divisions in the middle loop, and the saturation divisions in the
7310 inner loop. All zero input saturation entries are required to have a
7311 value scale factor of 1.0.
7315 <entry name="profileToneCurve" type="float"
7316 visibility="system" optional="true"
7317 type_notes="Samples defining a spline for a tone-mapping curve"
7320 <size>samples</size>
7324 A list of x,y samples defining a tone-mapping curve for gamma adjustment.
7327 Each sample has an input range of `[0, 1]` and an output range of
7328 `[0, 1]`. The first sample is required to be `(0, 0)`, and the last
7329 sample is required to be `(1, 1)`.
7332 This key contains a default tone curve that can be applied while
7333 processing the image as a starting point for user adjustments.
7334 The curve is specified as a list of value pairs in linear gamma.
7335 The curve is interpolated using a cubic spline.
7339 <entry name="greenSplit" type="float" visibility="public" optional="true">
7341 The worst-case divergence between Bayer green channels.
7347 This value is an estimate of the worst case split between the
7348 Bayer green channels in the red and blue rows in the sensor color
7351 The green split is calculated as follows:
7353 1. A 5x5 pixel (or larger) window W within the active sensor array is
7354 chosen. The term 'pixel' here is taken to mean a group of 4 Bayer
7355 mosaic channels (R, Gr, Gb, B). The location and size of the window
7356 chosen is implementation defined, and should be chosen to provide a
7357 green split estimate that is both representative of the entire image
7358 for this camera sensor, and can be calculated quickly.
7359 1. The arithmetic mean of the green channels from the red
7360 rows (mean_Gr) within W is computed.
7361 1. The arithmetic mean of the green channels from the blue
7362 rows (mean_Gb) within W is computed.
7363 1. The maximum ratio R of the two means is computed as follows:
7364 `R = max((mean_Gr + 1)/(mean_Gb + 1), (mean_Gb + 1)/(mean_Gr + 1))`
7366 The ratio R is the green split divergence reported for this property,
7367 which represents how much the green channels differ in the mosaic
7368 pattern. This value is typically used to determine the treatment of
7369 the green mosaic channels when demosaicing.
7371 The green split value can be roughly interpreted as follows:
7373 * R &lt; 1.03 is a negligible split (&lt;3% divergence).
7374 * 1.20 &lt;= R &gt;= 1.03 will require some software
7375 correction to avoid demosaic errors (3-20% divergence).
7376 * R &gt; 1.20 will require strong software correction to produce
7377 a usuable image (&gt;20% divergence).
7380 The green split given may be a static value based on prior
7381 characterization of the camera sensor using the green split
7382 calculation method given here over a large, representative, sample
7383 set of images. Other methods of calculation that produce equivalent
7384 results, and can be interpreted in the same manner, may be used.
7390 <entry name="testPatternData" type="int32" visibility="public" optional="true" container="array">
7395 A pixel `[R, G_even, G_odd, B]` that supplies the test pattern
7396 when android.sensor.testPatternMode is SOLID_COLOR.
7399 Each color channel is treated as an unsigned 32-bit integer.
7400 The camera device then uses the most significant X bits
7401 that correspond to how many bits are in its Bayer raw sensor
7404 For example, a sensor with RAW10 Bayer output would use the
7405 10 most significant bits from each color channel.
7410 <entry name="testPatternMode" type="int32" visibility="public" optional="true"
7414 <notes>No test pattern mode is used, and the camera
7415 device returns captures from the image sensor.
7417 This is the default if the key is not set.</notes>
7421 Each pixel in `[R, G_even, G_odd, B]` is replaced by its
7422 respective color channel provided in
7423 android.sensor.testPatternData.
7427 android.testPatternData = [0, 0xFFFFFFFF, 0xFFFFFFFF, 0]
7429 All green pixels are 100% green. All red/blue pixels are black.
7431 android.testPatternData = [0xFFFFFFFF, 0, 0xFFFFFFFF, 0]
7433 All red pixels are 100% red. Only the odd green pixels
7434 are 100% green. All blue pixels are 100% black.
7439 All pixel data is replaced with an 8-bar color pattern.
7441 The vertical bars (left-to-right) are as follows:
7452 In general the image would look like the following:
7463 (B = Blue, K = Black)
7465 Each bar should take up 1/8 of the sensor pixel array width.
7466 When this is not possible, the bar size should be rounded
7467 down to the nearest integer and the pattern can repeat
7470 Each bar's height must always take up the full sensor
7473 Each pixel in this test pattern must be set to either
7474 0% intensity or 100% intensity.
7477 <value>COLOR_BARS_FADE_TO_GRAY
7479 The test pattern is similar to COLOR_BARS, except that
7480 each bar should start at its specified color at the top,
7481 and fade to gray at the bottom.
7483 Furthermore each bar is further subdivided into a left and
7484 right half. The left half should have a smooth gradient,
7485 and the right half should have a quantized gradient.
7487 In particular, the right half's should consist of blocks of the
7488 same color for 1/16th active sensor pixel array width.
7490 The least significant bits in the quantized gradient should
7491 be copied from the most significant bits of the smooth gradient.
7493 The height of each bar should always be a multiple of 128.
7494 When this is not the case, the pattern should repeat at the bottom
7500 All pixel data is replaced by a pseudo-random sequence
7501 generated from a PN9 512-bit sequence (typically implemented
7502 in hardware with a linear feedback shift register).
7504 The generator should be reset at the beginning of each frame,
7505 and thus each subsequent raw frame with this test pattern should
7506 be exactly the same as the last.
7509 <value id="256">CUSTOM1
7510 <notes>The first custom test pattern. All custom patterns that are
7511 available only on this camera device are at least this numeric
7514 All of the custom test patterns will be static
7515 (that is the raw image must not vary from frame to frame).
7519 <description>When enabled, the sensor sends a test pattern instead of
7520 doing a real exposure from the camera.
7522 <range>android.sensor.availableTestPatternModes</range>
7524 When a test pattern is enabled, all manual sensor controls specified
7525 by android.sensor.* will be ignored. All other controls should
7528 For example, if manual flash is enabled, flash firing should still
7529 occur (and that the test pattern remain unmodified, since the flash
7530 would not actually affect it).
7535 All test patterns are specified in the Bayer domain.
7537 The HAL may choose to substitute test patterns from the sensor
7538 with test patterns from on-device memory. In that case, it should be
7539 indistinguishable to the ISP whether the data came from the
7540 sensor interconnect bus (such as CSI2) or memory.
7545 <clone entry="android.sensor.testPatternData" kind="controls">
7547 <clone entry="android.sensor.testPatternMode" kind="controls">
7551 <entry name="availableTestPatternModes" type="int32" visibility="public" optional="true"
7552 type_notes="list of enums" container="array">
7556 <description>List of sensor test pattern modes for android.sensor.testPatternMode
7557 supported by this camera device.
7559 <range>Any value listed in android.sensor.testPatternMode</range>
7561 Defaults to OFF, and always includes OFF if defined.
7564 All custom modes must be >= CUSTOM1.
7569 <entry name="rollingShutterSkew" type="int64" visibility="public" hwlevel="limited">
7570 <description>Duration between the start of first row exposure
7571 and the start of last row exposure.</description>
7572 <units>Nanoseconds</units>
7573 <range> &gt;= 0 and &lt;
7574 {@link android.hardware.camera2.params.StreamConfigurationMap#getOutputMinFrameDuration}.</range>
7576 This is the exposure time skew between the first and last
7577 row exposure start times. The first row and the last row are
7578 the first and last rows inside of the
7579 android.sensor.info.activeArraySize.
7581 For typical camera sensors that use rolling shutters, this is also equivalent
7582 to the frame readout time.
7585 The HAL must report `0` if the sensor is using global shutter, where all pixels begin
7586 exposure at the same time.
7592 <entry name="opticalBlackRegions" type="int32" visibility="public" optional="true"
7593 container="array" typedef="rectangle">
7596 <size>num_regions</size>
7598 <description>List of disjoint rectangles indicating the sensor
7599 optically shielded black pixel regions.
7602 In most camera sensors, the active array is surrounded by some
7603 optically shielded pixel areas. By blocking light, these pixels
7604 provides a reliable black reference for black level compensation
7605 in active array region.
7607 This key provides a list of disjoint rectangles specifying the
7608 regions of optically shielded (with metal shield) black pixel
7609 regions if the camera device is capable of reading out these black
7610 pixels in the output raw images. In comparison to the fixed black
7611 level values reported by android.sensor.blackLevelPattern, this key
7612 may provide a more accurate way for the application to calculate
7613 black level of each captured raw images.
7615 When this key is reported, the android.sensor.dynamicBlackLevel and
7616 android.sensor.dynamicWhiteLevel will also be reported.
7619 The data representation is `int[4]`, which maps to `(left, top, width, height)`.
7622 This array contains (xmin, ymin, width, height). The (xmin, ymin)
7623 must be &gt;= (0,0) and &lt;=
7624 android.sensor.info.pixelArraySize. The (width, height) must be
7625 &lt;= android.sensor.info.pixelArraySize. Each region must be
7626 outside the region reported by
7627 android.sensor.info.preCorrectionActiveArraySize.
7629 The HAL must report minimal number of disjoint regions for the
7630 optically shielded back pixel regions. For example, if a region can
7631 be covered by one rectangle, the HAL must not split this region into
7632 multiple rectangles.
7637 <entry name="dynamicBlackLevel" type="float" visibility="public"
7638 optional="true" type_notes="2x2 raw count block" container="array">
7643 A per-frame dynamic black level offset for each of the color filter
7644 arrangement (CFA) mosaic channels.
7646 <range>&gt;= 0 for each.</range>
7648 Camera sensor black levels may vary dramatically for different
7649 capture settings (e.g. android.sensor.sensitivity). The fixed black
7650 level reported by android.sensor.blackLevelPattern may be too
7651 inaccurate to represent the actual value on a per-frame basis. The
7652 camera device internal pipeline relies on reliable black level values
7653 to process the raw images appropriately. To get the best image
7654 quality, the camera device may choose to estimate the per frame black
7655 level values either based on optically shielded black regions
7656 (android.sensor.opticalBlackRegions) or its internal model.
7658 This key reports the camera device estimated per-frame zero light
7659 value for each of the CFA mosaic channels in the camera sensor. The
7660 android.sensor.blackLevelPattern may only represent a coarse
7661 approximation of the actual black level values. This value is the
7662 black level used in camera device internal image processing pipeline
7663 and generally more accurate than the fixed black level values.
7664 However, since they are estimated values by the camera device, they
7665 may not be as accurate as the black level values calculated from the
7666 optical black pixels reported by android.sensor.opticalBlackRegions.
7668 The values are given in the same order as channels listed for the CFA
7669 layout key (see android.sensor.info.colorFilterArrangement), i.e. the
7670 nth value given corresponds to the black level offset for the nth
7671 color channel listed in the CFA.
7673 This key will be available if android.sensor.opticalBlackRegions is available or the
7674 camera device advertises this key via {@link
7675 android.hardware.camera2.CameraCharacteristics#getAvailableCaptureResultKeys|ACAMERA_REQUEST_AVAILABLE_RESULT_KEYS}.
7678 The values are given in row-column scan order, with the first value
7679 corresponding to the element of the CFA in row=0, column=0.
7683 <entry name="dynamicWhiteLevel" type="int32" visibility="public"
7686 Maximum raw value output by sensor for this frame.
7688 <range> &gt;= 0</range>
7690 Since the android.sensor.blackLevelPattern may change for different
7691 capture settings (e.g., android.sensor.sensitivity), the white
7692 level will change accordingly. This key is similar to
7693 android.sensor.info.whiteLevel, but specifies the camera device
7694 estimated white level for each frame.
7696 This key will be available if android.sensor.opticalBlackRegions is
7697 available or the camera device advertises this key via
7698 {@link android.hardware.camera2.CameraCharacteristics#getAvailableCaptureRequestKeys|ACAMERA_REQUEST_AVAILABLE_RESULT_KEYS}.
7701 The full bit depth of the sensor must be available in the raw data,
7702 so the value for linear sensors should not be significantly lower
7703 than maximum raw value supported, i.e. 2^(sensor bits per pixel).
7709 <entry name="opaqueRawSize" type="int32" visibility="system" container="array">
7714 <description>Size in bytes for all the listed opaque RAW buffer sizes</description>
7715 <range>Must be large enough to fit the opaque RAW of corresponding size produced by
7718 This configurations are listed as `(width, height, size_in_bytes)` tuples.
7719 This is used for sizing the gralloc buffers for opaque RAW buffers.
7720 All RAW_OPAQUE output stream configuration listed in
7721 android.scaler.availableStreamConfigurations will have a corresponding tuple in
7725 This key is added in legacy HAL3.4.
7727 For legacy HAL3.4 or above: devices advertising RAW_OPAQUE format output must list this
7728 key. For legacy HAL3.3 or earlier devices: if RAW_OPAQUE ouput is advertised, camera
7729 framework will derive this key by assuming each pixel takes two bytes and no padding bytes
7735 <section name="shading">
7737 <entry name="mode" type="byte" visibility="public" enum="true" hwlevel="full">
7740 <notes>No lens shading correction is applied.</notes></value>
7742 <notes>Apply lens shading corrections, without slowing
7743 frame rate relative to sensor raw output</notes></value>
7745 <notes>Apply high-quality lens shading correction, at the
7746 cost of possibly reduced frame rate.</notes></value>
7748 <description>Quality of lens shading correction applied
7749 to the image data.</description>
7750 <range>android.shading.availableModes</range>
7752 When set to OFF mode, no lens shading correction will be applied by the
7753 camera device, and an identity lens shading map data will be provided
7754 if `android.statistics.lensShadingMapMode == ON`. For example, for lens
7755 shading map with size of `[ 4, 3 ]`,
7756 the output android.statistics.lensShadingCorrectionMap for this case will be an identity
7759 [ 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,
7760 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,
7761 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,
7762 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,
7763 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0,
7764 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0 ]
7766 When set to other modes, lens shading correction will be applied by the camera
7767 device. Applications can request lens shading map data by setting
7768 android.statistics.lensShadingMapMode to ON, and then the camera device will provide lens
7769 shading map data in android.statistics.lensShadingCorrectionMap; the returned shading map
7770 data will be the one applied by the camera device for this capture request.
7772 The shading map data may depend on the auto-exposure (AE) and AWB statistics, therefore
7773 the reliability of the map data may be affected by the AE and AWB algorithms. When AE and
7774 AWB are in AUTO modes(android.control.aeMode `!=` OFF and android.control.awbMode `!=`
7775 OFF), to get best results, it is recommended that the applications wait for the AE and AWB
7776 to be converged before using the returned shading map data.
7779 <entry name="strength" type="byte">
7780 <description>Control the amount of shading correction
7781 applied to the images</description>
7782 <units>unitless: 1-10; 10 is full shading
7783 compensation</units>
7788 <clone entry="android.shading.mode" kind="controls">
7792 <entry name="availableModes" type="byte" visibility="public"
7793 type_notes="List of enums (android.shading.mode)." container="array"
7794 typedef="enumList" hwlevel="legacy">
7799 List of lens shading modes for android.shading.mode that are supported by this camera device.
7801 <range>Any value listed in android.shading.mode</range>
7803 This list contains lens shading modes that can be set for the camera device.
7804 Camera devices that support the MANUAL_POST_PROCESSING capability will always
7805 list OFF and FAST mode. This includes all FULL level devices.
7806 LEGACY devices will always only support FAST mode.
7809 HAL must support both FAST and HIGH_QUALITY if lens shading correction control is
7810 available on the camera device, but the underlying implementation can be the same for
7811 both modes. That is, if the highest quality implementation on the camera device does not
7812 slow down capture rate, then FAST and HIGH_QUALITY will generate the same output.
7817 <section name="statistics">
7819 <entry name="faceDetectMode" type="byte" visibility="public" enum="true"
7823 <notes>Do not include face detection statistics in capture
7824 results.</notes></value>
7825 <value optional="true">SIMPLE
7826 <notes>Return face rectangle and confidence values only.
7828 <value optional="true">FULL
7829 <notes>Return all face
7832 In this mode, face rectangles, scores, landmarks, and face IDs are all valid.
7835 <description>Operating mode for the face detector
7837 <range>android.statistics.info.availableFaceDetectModes</range>
7838 <details>Whether face detection is enabled, and whether it
7839 should output just the basic fields or the full set of
7842 SIMPLE mode must fill in android.statistics.faceRectangles and
7843 android.statistics.faceScores.
7844 FULL mode must also fill in android.statistics.faceIds, and
7845 android.statistics.faceLandmarks.
7849 <entry name="histogramMode" type="byte" enum="true" typedef="boolean">
7854 <description>Operating mode for histogram
7855 generation</description>
7858 <entry name="sharpnessMapMode" type="byte" enum="true" typedef="boolean">
7863 <description>Operating mode for sharpness map
7864 generation</description>
7867 <entry name="hotPixelMapMode" type="byte" visibility="public" enum="true"
7871 <notes>Hot pixel map production is disabled.
7874 <notes>Hot pixel map production is enabled.
7878 Operating mode for hot pixel map generation.
7880 <range>android.statistics.info.availableHotPixelMapModes</range>
7882 If set to `true`, a hot pixel map is returned in android.statistics.hotPixelMap.
7883 If set to `false`, no hot pixel map will be returned.
7890 <namespace name="info">
7891 <entry name="availableFaceDetectModes" type="byte"
7893 type_notes="List of enums from android.statistics.faceDetectMode"
7900 <description>List of face detection modes for android.statistics.faceDetectMode that are
7901 supported by this camera device.
7903 <range>Any value listed in android.statistics.faceDetectMode</range>
7904 <details>OFF is always supported.
7907 <entry name="histogramBucketCount" type="int32">
7908 <description>Number of histogram buckets
7909 supported</description>
7910 <range>&gt;= 64</range>
7913 <entry name="maxFaceCount" type="int32" visibility="public" hwlevel="legacy">
7914 <description>The maximum number of simultaneously detectable
7915 faces.</description>
7916 <range>0 for cameras without available face detection; otherwise:
7917 `>=4` for LIMITED or FULL hwlevel devices or
7918 `>0` for LEGACY devices.</range>
7921 <entry name="maxHistogramCount" type="int32">
7922 <description>Maximum value possible for a histogram
7923 bucket</description>
7926 <entry name="maxSharpnessMapValue" type="int32">
7927 <description>Maximum value possible for a sharpness map
7928 region.</description>
7931 <entry name="sharpnessMapSize" type="int32"
7932 type_notes="width x height" container="array" typedef="size">
7936 <description>Dimensions of the sharpness
7938 <range>Must be at least 32 x 32</range>
7941 <entry name="availableHotPixelMapModes" type="byte" visibility="public"
7942 type_notes="list of enums" container="array" typedef="boolean">
7947 List of hot pixel map output modes for android.statistics.hotPixelMapMode that are
7948 supported by this camera device.
7950 <range>Any value listed in android.statistics.hotPixelMapMode</range>
7952 If no hotpixel map output is available for this camera device, this will contain only
7955 ON is always supported on devices with the RAW capability.
7960 <entry name="availableLensShadingMapModes" type="byte" visibility="public"
7961 type_notes="list of enums" container="array" typedef="enumList">
7966 List of lens shading map output modes for android.statistics.lensShadingMapMode that
7967 are supported by this camera device.
7969 <range>Any value listed in android.statistics.lensShadingMapMode</range>
7971 If no lens shading map output is available for this camera device, this key will
7974 ON is always supported on devices with the RAW capability.
7975 LEGACY mode devices will always only support OFF.
7978 <entry name="availableOisDataModes" type="byte" visibility="public"
7979 type_notes="list of enums" container="array" typedef="enumList" hal_version="3.3">
7984 List of OIS data output modes for android.statistics.oisDataMode that
7985 are supported by this camera device.
7987 <range>Any value listed in android.statistics.oisDataMode</range>
7989 If no OIS data output is available for this camera device, this key will
7996 <clone entry="android.statistics.faceDetectMode"
7997 kind="controls"></clone>
7998 <entry name="faceIds" type="int32" visibility="ndk_public"
7999 container="array" hwlevel="legacy">
8003 <description>List of unique IDs for detected faces.</description>
8005 Each detected face is given a unique ID that is valid for as long as the face is visible
8006 to the camera device. A face that leaves the field of view and later returns may be
8009 Only available if android.statistics.faceDetectMode == FULL</details>
8012 <entry name="faceLandmarks" type="int32" visibility="ndk_public"
8013 type_notes="(leftEyeX, leftEyeY, rightEyeX, rightEyeY, mouthX, mouthY)"
8014 container="array" hwlevel="legacy">
8019 <description>List of landmarks for detected
8020 faces.</description>
8022 The coordinate system is that of android.sensor.info.activeArraySize, with
8023 `(0, 0)` being the top-left pixel of the active array.
8025 Only available if android.statistics.faceDetectMode == FULL</details>
8028 <entry name="faceRectangles" type="int32" visibility="ndk_public"
8029 type_notes="(xmin, ymin, xmax, ymax). (0,0) is top-left of active pixel area"
8030 container="array" typedef="rectangle" hwlevel="legacy">
8035 <description>List of the bounding rectangles for detected
8036 faces.</description>
8038 The coordinate system is that of android.sensor.info.activeArraySize, with
8039 `(0, 0)` being the top-left pixel of the active array.
8041 Only available if android.statistics.faceDetectMode != OFF</details>
8043 The data representation is `int[4]`, which maps to `(left, top, width, height)`.
8047 <entry name="faceScores" type="byte" visibility="ndk_public"
8048 container="array" hwlevel="legacy">
8052 <description>List of the face confidence scores for
8053 detected faces</description>
8054 <range>1-100</range>
8055 <details>Only available if android.statistics.faceDetectMode != OFF.
8058 The value should be meaningful (for example, setting 100 at
8059 all times is illegal).</hal_details>
8062 <entry name="faces" type="int32" visibility="java_public" synthetic="true"
8063 container="array" typedef="face" hwlevel="legacy">
8067 <description>List of the faces detected through camera face detection
8068 in this capture.</description>
8070 Only available if android.statistics.faceDetectMode `!=` OFF.
8073 <entry name="histogram" type="int32"
8074 type_notes="count of pixels for each color channel that fall into each histogram bucket, scaled to be between 0 and maxHistogramCount"
8080 <description>A 3-channel histogram based on the raw
8081 sensor data</description>
8082 <details>The k'th bucket (0-based) covers the input range
8083 (with w = android.sensor.info.whiteLevel) of [ k * w/N,
8084 (k + 1) * w / N ). If only a monochrome sharpness map is
8085 supported, all channels should have the same data</details>
8088 <clone entry="android.statistics.histogramMode"
8089 kind="controls"></clone>
8090 <entry name="sharpnessMap" type="int32"
8091 type_notes="estimated sharpness for each region of the input image. Normalized to be between 0 and maxSharpnessMapValue. Higher values mean sharper (better focused)"
8098 <description>A 3-channel sharpness map, based on the raw
8099 sensor data</description>
8100 <details>If only a monochrome sharpness map is supported,
8101 all channels should have the same data</details>
8104 <clone entry="android.statistics.sharpnessMapMode"
8105 kind="controls"></clone>
8106 <entry name="lensShadingCorrectionMap" type="byte" visibility="java_public"
8107 typedef="lensShadingMap" hwlevel="full">
8108 <description>The shading map is a low-resolution floating-point map
8109 that lists the coefficients used to correct for vignetting, for each
8110 Bayer color channel.</description>
8111 <range>Each gain factor is &gt;= 1</range>
8113 The map provided here is the same map that is used by the camera device to
8114 correct both color shading and vignetting for output non-RAW images.
8116 When there is no lens shading correction applied to RAW
8117 output images (android.sensor.info.lensShadingApplied `==`
8118 false), this map is the complete lens shading correction
8119 map; when there is some lens shading correction applied to
8120 the RAW output image (android.sensor.info.lensShadingApplied
8121 `==` true), this map reports the remaining lens shading
8122 correction map that needs to be applied to get shading
8123 corrected images that match the camera device's output for
8126 For a complete shading correction map, the least shaded
8127 section of the image will have a gain factor of 1; all
8128 other sections will have gains above 1.
8130 When android.colorCorrection.mode = TRANSFORM_MATRIX, the map
8131 will take into account the colorCorrection settings.
8133 The shading map is for the entire active pixel array, and is not
8134 affected by the crop region specified in the request. Each shading map
8135 entry is the value of the shading compensation map over a specific
8136 pixel on the sensor. Specifically, with a (N x M) resolution shading
8137 map, and an active pixel array size (W x H), shading map entry
8138 (x,y) ϵ (0 ... N-1, 0 ... M-1) is the value of the shading map at
8139 pixel ( ((W-1)/(N-1)) * x, ((H-1)/(M-1)) * y) for the four color channels.
8140 The map is assumed to be bilinearly interpolated between the sample points.
8142 The channel order is [R, Geven, Godd, B], where Geven is the green
8143 channel for the even rows of a Bayer pattern, and Godd is the odd rows.
8144 The shading map is stored in a fully interleaved format.
8146 The shading map will generally have on the order of 30-40 rows and columns,
8147 and will be smaller than 64x64.
8149 As an example, given a very small map defined as:
8151 width,height = [ 4, 3 ]
8153 [ 1.3, 1.2, 1.15, 1.2, 1.2, 1.2, 1.15, 1.2,
8154 1.1, 1.2, 1.2, 1.2, 1.3, 1.2, 1.3, 1.3,
8155 1.2, 1.2, 1.25, 1.1, 1.1, 1.1, 1.1, 1.0,
8156 1.0, 1.0, 1.0, 1.0, 1.2, 1.3, 1.25, 1.2,
8157 1.3, 1.2, 1.2, 1.3, 1.2, 1.15, 1.1, 1.2,
8158 1.2, 1.1, 1.0, 1.2, 1.3, 1.15, 1.2, 1.3 ]
8160 The low-resolution scaling map images for each channel are
8161 (displayed using nearest-neighbor interpolation):
8163 ![Red lens shading map](android.statistics.lensShadingMap/red_shading.png)
8164 ![Green (even rows) lens shading map](android.statistics.lensShadingMap/green_e_shading.png)
8165 ![Green (odd rows) lens shading map](android.statistics.lensShadingMap/green_o_shading.png)
8166 ![Blue lens shading map](android.statistics.lensShadingMap/blue_shading.png)
8168 As a visualization only, inverting the full-color map to recover an
8169 image of a gray wall (using bicubic interpolation for visual quality) as captured by the sensor gives:
8171 ![Image of a uniform white wall (inverse shading map)](android.statistics.lensShadingMap/inv_shading.png)
8174 <entry name="lensShadingMap" type="float" visibility="ndk_public"
8175 type_notes="2D array of float gain factors per channel to correct lens shading"
8176 container="array" hwlevel="full">
8182 <description>The shading map is a low-resolution floating-point map
8183 that lists the coefficients used to correct for vignetting and color shading,
8184 for each Bayer color channel of RAW image data.</description>
8185 <range>Each gain factor is &gt;= 1</range>
8187 The map provided here is the same map that is used by the camera device to
8188 correct both color shading and vignetting for output non-RAW images.
8190 When there is no lens shading correction applied to RAW
8191 output images (android.sensor.info.lensShadingApplied `==`
8192 false), this map is the complete lens shading correction
8193 map; when there is some lens shading correction applied to
8194 the RAW output image (android.sensor.info.lensShadingApplied
8195 `==` true), this map reports the remaining lens shading
8196 correction map that needs to be applied to get shading
8197 corrected images that match the camera device's output for
8200 For a complete shading correction map, the least shaded
8201 section of the image will have a gain factor of 1; all
8202 other sections will have gains above 1.
8204 When android.colorCorrection.mode = TRANSFORM_MATRIX, the map
8205 will take into account the colorCorrection settings.
8207 The shading map is for the entire active pixel array, and is not
8208 affected by the crop region specified in the request. Each shading map
8209 entry is the value of the shading compensation map over a specific
8210 pixel on the sensor. Specifically, with a (N x M) resolution shading
8211 map, and an active pixel array size (W x H), shading map entry
8212 (x,y) ϵ (0 ... N-1, 0 ... M-1) is the value of the shading map at
8213 pixel ( ((W-1)/(N-1)) * x, ((H-1)/(M-1)) * y) for the four color channels.
8214 The map is assumed to be bilinearly interpolated between the sample points.
8216 The channel order is [R, Geven, Godd, B], where Geven is the green
8217 channel for the even rows of a Bayer pattern, and Godd is the odd rows.
8218 The shading map is stored in a fully interleaved format, and its size
8219 is provided in the camera static metadata by android.lens.info.shadingMapSize.
8221 The shading map will generally have on the order of 30-40 rows and columns,
8222 and will be smaller than 64x64.
8224 As an example, given a very small map defined as:
8226 android.lens.info.shadingMapSize = [ 4, 3 ]
8227 android.statistics.lensShadingMap =
8228 [ 1.3, 1.2, 1.15, 1.2, 1.2, 1.2, 1.15, 1.2,
8229 1.1, 1.2, 1.2, 1.2, 1.3, 1.2, 1.3, 1.3,
8230 1.2, 1.2, 1.25, 1.1, 1.1, 1.1, 1.1, 1.0,
8231 1.0, 1.0, 1.0, 1.0, 1.2, 1.3, 1.25, 1.2,
8232 1.3, 1.2, 1.2, 1.3, 1.2, 1.15, 1.1, 1.2,
8233 1.2, 1.1, 1.0, 1.2, 1.3, 1.15, 1.2, 1.3 ]
8235 The low-resolution scaling map images for each channel are
8236 (displayed using nearest-neighbor interpolation):
8238 ![Red lens shading map](android.statistics.lensShadingMap/red_shading.png)
8239 ![Green (even rows) lens shading map](android.statistics.lensShadingMap/green_e_shading.png)
8240 ![Green (odd rows) lens shading map](android.statistics.lensShadingMap/green_o_shading.png)
8241 ![Blue lens shading map](android.statistics.lensShadingMap/blue_shading.png)
8243 As a visualization only, inverting the full-color map to recover an
8244 image of a gray wall (using bicubic interpolation for visual quality)
8245 as captured by the sensor gives:
8247 ![Image of a uniform white wall (inverse shading map)](android.statistics.lensShadingMap/inv_shading.png)
8249 Note that the RAW image data might be subject to lens shading
8250 correction not reported on this map. Query
8251 android.sensor.info.lensShadingApplied to see if RAW image data has subject
8252 to lens shading correction. If android.sensor.info.lensShadingApplied
8253 is TRUE, the RAW image data is subject to partial or full lens shading
8254 correction. In the case full lens shading correction is applied to RAW
8255 images, the gain factor map reported in this key will contain all 1.0 gains.
8256 In other words, the map reported in this key is the remaining lens shading
8257 that needs to be applied on the RAW image to get images without lens shading
8258 artifacts. See android.request.maxNumOutputRaw for a list of RAW image
8262 The lens shading map calculation may depend on exposure and white balance statistics.
8263 When AE and AWB are in AUTO modes
8264 (android.control.aeMode `!=` OFF and android.control.awbMode `!=` OFF), the HAL
8265 may have all the information it need to generate most accurate lens shading map. When
8266 AE or AWB are in manual mode
8267 (android.control.aeMode `==` OFF or android.control.awbMode `==` OFF), the shading map
8268 may be adversely impacted by manual exposure or white balance parameters. To avoid
8269 generating unreliable shading map data, the HAL may choose to lock the shading map with
8270 the latest known good map generated when the AE and AWB are in AUTO modes.
8273 <entry name="predictedColorGains" type="float"
8277 type_notes="A 1D array of floats for 4 color channel gains"
8282 <description>The best-fit color channel gains calculated
8283 by the camera device's statistics units for the current output frame.
8285 <deprecation_description>
8286 Never fully implemented or specified; do not use
8287 </deprecation_description>
8289 This may be different than the gains used for this frame,
8290 since statistics processing on data from a new frame
8291 typically completes after the transform has already been
8292 applied to that frame.
8294 The 4 channel gains are defined in Bayer domain,
8295 see android.colorCorrection.gains for details.
8297 This value should always be calculated by the auto-white balance (AWB) block,
8298 regardless of the android.control.* current values.
8301 <entry name="predictedColorTransform" type="rational"
8305 type_notes="3x3 rational matrix in row-major order"
8311 <description>The best-fit color transform matrix estimate
8312 calculated by the camera device's statistics units for the current
8313 output frame.</description>
8314 <deprecation_description>
8315 Never fully implemented or specified; do not use
8316 </deprecation_description>
8317 <details>The camera device will provide the estimate from its
8318 statistics unit on the white balance transforms to use
8319 for the next frame. These are the values the camera device believes
8320 are the best fit for the current output frame. This may
8321 be different than the transform used for this frame, since
8322 statistics processing on data from a new frame typically
8323 completes after the transform has already been applied to
8326 These estimates must be provided for all frames, even if
8327 capture settings and color transforms are set by the application.
8329 This value should always be calculated by the auto-white balance (AWB) block,
8330 regardless of the android.control.* current values.
8333 <entry name="sceneFlicker" type="byte" visibility="public" enum="true"
8337 <notes>The camera device does not detect any flickering illumination
8338 in the current scene.</notes></value>
8340 <notes>The camera device detects illumination flickering at 50Hz
8341 in the current scene.</notes></value>
8343 <notes>The camera device detects illumination flickering at 60Hz
8344 in the current scene.</notes></value>
8346 <description>The camera device estimated scene illumination lighting
8347 frequency.</description>
8349 Many light sources, such as most fluorescent lights, flicker at a rate
8350 that depends on the local utility power standards. This flicker must be
8351 accounted for by auto-exposure routines to avoid artifacts in captured images.
8352 The camera device uses this entry to tell the application what the scene
8353 illuminant frequency is.
8355 When manual exposure control is enabled
8356 (`android.control.aeMode == OFF` or `android.control.mode ==
8357 OFF`), the android.control.aeAntibandingMode doesn't perform
8358 antibanding, and the application can ensure it selects
8359 exposure times that do not cause banding issues by looking
8360 into this metadata field. See
8361 android.control.aeAntibandingMode for more details.
8363 Reports NONE if there doesn't appear to be flickering illumination.
8366 <clone entry="android.statistics.hotPixelMapMode" kind="controls">
8368 <entry name="hotPixelMap" type="int32" visibility="public"
8369 type_notes="list of coordinates based on android.sensor.pixelArraySize"
8370 container="array" typedef="point">
8376 List of `(x, y)` coordinates of hot/defective pixels on the sensor.
8379 n <= number of pixels on the sensor.
8380 The `(x, y)` coordinates must be bounded by
8381 android.sensor.info.pixelArraySize.
8384 A coordinate `(x, y)` must lie between `(0, 0)`, and
8385 `(width - 1, height - 1)` (inclusive), which are the top-left and
8386 bottom-right of the pixel array, respectively. The width and
8387 height dimensions are given in android.sensor.info.pixelArraySize.
8388 This may include hot pixels that lie outside of the active array
8389 bounds given by android.sensor.info.activeArraySize.
8392 A hotpixel map contains the coordinates of pixels on the camera
8393 sensor that do report valid values (usually due to defects in
8394 the camera sensor). This includes pixels that are stuck at certain
8395 values, or have a response that does not accuractly encode the
8396 incoming light from the scene.
8398 To avoid performance issues, there should be significantly fewer hot
8399 pixels than actual pixels on the camera sensor.
8406 <entry name="lensShadingMapMode" type="byte" visibility="public" enum="true" hwlevel="full">
8409 <notes>Do not include a lens shading map in the capture result.</notes></value>
8411 <notes>Include a lens shading map in the capture result.</notes></value>
8413 <description>Whether the camera device will output the lens
8414 shading map in output result metadata.</description>
8415 <range>android.statistics.info.availableLensShadingMapModes</range>
8416 <details>When set to ON,
8417 android.statistics.lensShadingMap will be provided in
8418 the output result metadata.
8420 ON is always supported on devices with the RAW capability.
8426 <clone entry="android.statistics.lensShadingMapMode" kind="controls">
8430 <entry name="oisDataMode" type="byte" visibility="public" enum="true" hal_version="3.3">
8433 <notes>Do not include OIS data in the capture result.</notes></value>
8435 <notes>Include OIS data in the capture result.</notes>
8436 <sdk_notes>android.statistics.oisSamples provides OIS sample data in the
8437 output result metadata.
8439 <ndk_notes>android.statistics.oisTimestamps, android.statistics.oisXShifts,
8440 and android.statistics.oisYShifts provide OIS data in the output result metadata.
8444 <description>A control for selecting whether OIS position information is included in output
8445 result metadata.</description>
8446 <range>android.statistics.info.availableOisDataModes</range>
8450 <clone entry="android.statistics.oisDataMode" kind="controls">
8452 <entry name="oisTimestamps" type="int64" visibility="ndk_public" container="array" hal_version="3.3">
8457 An array of timestamps of OIS samples, in nanoseconds.
8459 <units>nanoseconds</units>
8461 The array contains the timestamps of OIS samples. The timestamps are in the same
8462 timebase as and comparable to android.sensor.timestamp.
8465 <entry name="oisXShifts" type="float" visibility="ndk_public" container="array" hal_version="3.3">
8470 An array of shifts of OIS samples, in x direction.
8472 <units>Pixels in active array.</units>
8474 The array contains the amount of shifts in x direction, in pixels, based on OIS samples.
8475 A positive value is a shift from left to right in active array coordinate system. For
8476 example, if the optical center is (1000, 500) in active array coordinates, a shift of
8477 (3, 0) puts the new optical center at (1003, 500).
8479 The number of shifts must match the number of timestamps in
8480 android.statistics.oisTimestamps.
8483 <entry name="oisYShifts" type="float" visibility="ndk_public" container="array" hal_version="3.3">
8488 An array of shifts of OIS samples, in y direction.
8490 <units>Pixels in active array.</units>
8492 The array contains the amount of shifts in y direction, in pixels, based on OIS samples.
8493 A positive value is a shift from top to bottom in active array coordinate system. For
8494 example, if the optical center is (1000, 500) in active array coordinates, a shift of
8495 (0, 5) puts the new optical center at (1000, 505).
8497 The number of shifts must match the number of timestamps in
8498 android.statistics.oisTimestamps.
8501 <entry name="oisSamples" type="float" visibility="java_public" synthetic="true"
8502 container="array" typedef="oisSample" hal_version="3.3">
8507 An array of OIS samples.
8510 Each OIS sample contains the timestamp and the amount of shifts in x and y direction,
8511 in pixels, of the OIS sample.
8513 A positive value for a shift in x direction is a shift from left to right in active array
8514 coordinate system. For example, if the optical center is (1000, 500) in active array
8515 coordinates, a shift of (3, 0) puts the new optical center at (1003, 500).
8517 A positive value for a shift in y direction is a shift from top to bottom in active array
8518 coordinate system. For example, if the optical center is (1000, 500) in active array
8519 coordinates, a shift of (0, 5) puts the new optical center at (1000, 505).
8524 <section name="tonemap">
8526 <entry name="curveBlue" type="float" visibility="ndk_public"
8527 type_notes="1D array of float pairs (P_IN, P_OUT). The maximum number of pairs is specified by android.tonemap.maxCurvePoints."
8528 container="array" hwlevel="full">
8533 <description>Tonemapping / contrast / gamma curve for the blue
8534 channel, to use when android.tonemap.mode is
8535 CONTRAST_CURVE.</description>
8536 <details>See android.tonemap.curveRed for more details.</details>
8538 <entry name="curveGreen" type="float" visibility="ndk_public"
8539 type_notes="1D array of float pairs (P_IN, P_OUT). The maximum number of pairs is specified by android.tonemap.maxCurvePoints."
8540 container="array" hwlevel="full">
8545 <description>Tonemapping / contrast / gamma curve for the green
8546 channel, to use when android.tonemap.mode is
8547 CONTRAST_CURVE.</description>
8548 <details>See android.tonemap.curveRed for more details.</details>
8550 <entry name="curveRed" type="float" visibility="ndk_public"
8551 type_notes="1D array of float pairs (P_IN, P_OUT). The maximum number of pairs is specified by android.tonemap.maxCurvePoints."
8552 container="array" hwlevel="full">
8557 <description>Tonemapping / contrast / gamma curve for the red
8558 channel, to use when android.tonemap.mode is
8559 CONTRAST_CURVE.</description>
8560 <range>0-1 on both input and output coordinates, normalized
8561 as a floating-point value such that 0 == black and 1 == white.
8564 Each channel's curve is defined by an array of control points:
8566 android.tonemap.curveRed =
8567 [ P0in, P0out, P1in, P1out, P2in, P2out, P3in, P3out, ..., PNin, PNout ]
8568 2 <= N <= android.tonemap.maxCurvePoints
8570 These are sorted in order of increasing `Pin`; it is
8571 required that input values 0.0 and 1.0 are included in the list to
8572 define a complete mapping. For input values between control points,
8573 the camera device must linearly interpolate between the control
8576 Each curve can have an independent number of points, and the number
8577 of points can be less than max (that is, the request doesn't have to
8578 always provide a curve with number of points equivalent to
8579 android.tonemap.maxCurvePoints).
8581 A few examples, and their corresponding graphical mappings; these
8582 only specify the red channel and the precision is limited to 4
8583 digits, for conciseness.
8587 android.tonemap.curveRed = [ 0, 0, 1.0, 1.0 ]
8589 ![Linear mapping curve](android.tonemap.curveRed/linear_tonemap.png)
8593 android.tonemap.curveRed = [ 0, 1.0, 1.0, 0 ]
8595 ![Inverting mapping curve](android.tonemap.curveRed/inverse_tonemap.png)
8597 Gamma 1/2.2 mapping, with 16 control points:
8599 android.tonemap.curveRed = [
8600 0.0000, 0.0000, 0.0667, 0.2920, 0.1333, 0.4002, 0.2000, 0.4812,
8601 0.2667, 0.5484, 0.3333, 0.6069, 0.4000, 0.6594, 0.4667, 0.7072,
8602 0.5333, 0.7515, 0.6000, 0.7928, 0.6667, 0.8317, 0.7333, 0.8685,
8603 0.8000, 0.9035, 0.8667, 0.9370, 0.9333, 0.9691, 1.0000, 1.0000 ]
8605 ![Gamma = 1/2.2 tonemapping curve](android.tonemap.curveRed/gamma_tonemap.png)
8607 Standard sRGB gamma mapping, per IEC 61966-2-1:1999, with 16 control points:
8609 android.tonemap.curveRed = [
8610 0.0000, 0.0000, 0.0667, 0.2864, 0.1333, 0.4007, 0.2000, 0.4845,
8611 0.2667, 0.5532, 0.3333, 0.6125, 0.4000, 0.6652, 0.4667, 0.7130,
8612 0.5333, 0.7569, 0.6000, 0.7977, 0.6667, 0.8360, 0.7333, 0.8721,
8613 0.8000, 0.9063, 0.8667, 0.9389, 0.9333, 0.9701, 1.0000, 1.0000 ]
8615 ![sRGB tonemapping curve](android.tonemap.curveRed/srgb_tonemap.png)
8618 For good quality of mapping, at least 128 control points are
8621 A typical use case of this would be a gamma-1/2.2 curve, with as many
8622 control points used as are available.
8625 <entry name="curve" type="float" visibility="java_public" synthetic="true"
8626 typedef="tonemapCurve"
8628 <description>Tonemapping / contrast / gamma curve to use when android.tonemap.mode
8629 is CONTRAST_CURVE.</description>
8631 The tonemapCurve consist of three curves for each of red, green, and blue
8632 channels respectively. The following example uses the red channel as an
8633 example. The same logic applies to green and blue channel.
8634 Each channel's curve is defined by an array of control points:
8637 [ P0(in, out), P1(in, out), P2(in, out), P3(in, out), ..., PN(in, out) ]
8638 2 <= N <= android.tonemap.maxCurvePoints
8640 These are sorted in order of increasing `Pin`; it is always
8641 guaranteed that input values 0.0 and 1.0 are included in the list to
8642 define a complete mapping. For input values between control points,
8643 the camera device must linearly interpolate between the control
8646 Each curve can have an independent number of points, and the number
8647 of points can be less than max (that is, the request doesn't have to
8648 always provide a curve with number of points equivalent to
8649 android.tonemap.maxCurvePoints).
8651 A few examples, and their corresponding graphical mappings; these
8652 only specify the red channel and the precision is limited to 4
8653 digits, for conciseness.
8657 curveRed = [ (0, 0), (1.0, 1.0) ]
8659 ![Linear mapping curve](android.tonemap.curveRed/linear_tonemap.png)
8663 curveRed = [ (0, 1.0), (1.0, 0) ]
8665 ![Inverting mapping curve](android.tonemap.curveRed/inverse_tonemap.png)
8667 Gamma 1/2.2 mapping, with 16 control points:
8670 (0.0000, 0.0000), (0.0667, 0.2920), (0.1333, 0.4002), (0.2000, 0.4812),
8671 (0.2667, 0.5484), (0.3333, 0.6069), (0.4000, 0.6594), (0.4667, 0.7072),
8672 (0.5333, 0.7515), (0.6000, 0.7928), (0.6667, 0.8317), (0.7333, 0.8685),
8673 (0.8000, 0.9035), (0.8667, 0.9370), (0.9333, 0.9691), (1.0000, 1.0000) ]
8675 ![Gamma = 1/2.2 tonemapping curve](android.tonemap.curveRed/gamma_tonemap.png)
8677 Standard sRGB gamma mapping, per IEC 61966-2-1:1999, with 16 control points:
8680 (0.0000, 0.0000), (0.0667, 0.2864), (0.1333, 0.4007), (0.2000, 0.4845),
8681 (0.2667, 0.5532), (0.3333, 0.6125), (0.4000, 0.6652), (0.4667, 0.7130),
8682 (0.5333, 0.7569), (0.6000, 0.7977), (0.6667, 0.8360), (0.7333, 0.8721),
8683 (0.8000, 0.9063), (0.8667, 0.9389), (0.9333, 0.9701), (1.0000, 1.0000) ]
8685 ![sRGB tonemapping curve](android.tonemap.curveRed/srgb_tonemap.png)
8688 This entry is created by the framework from the curveRed, curveGreen and
8692 <entry name="mode" type="byte" visibility="public" enum="true"
8695 <value>CONTRAST_CURVE
8696 <notes>Use the tone mapping curve specified in
8697 the android.tonemap.curve* entries.
8699 All color enhancement and tonemapping must be disabled, except
8700 for applying the tonemapping curve specified by
8701 android.tonemap.curve.
8703 Must not slow down frame rate relative to raw
8709 Advanced gamma mapping and color enhancement may be applied, without
8710 reducing frame rate compared to raw sensor output.
8715 High-quality gamma mapping and color enhancement will be applied, at
8716 the cost of possibly reduced frame rate compared to raw sensor output.
8721 Use the gamma value specified in android.tonemap.gamma to peform
8724 All color enhancement and tonemapping must be disabled, except
8725 for applying the tonemapping curve specified by android.tonemap.gamma.
8727 Must not slow down frame rate relative to raw sensor output.
8732 Use the preset tonemapping curve specified in
8733 android.tonemap.presetCurve to peform tonemapping.
8735 All color enhancement and tonemapping must be disabled, except
8736 for applying the tonemapping curve specified by
8737 android.tonemap.presetCurve.
8739 Must not slow down frame rate relative to raw sensor output.
8743 <description>High-level global contrast/gamma/tonemapping control.
8745 <range>android.tonemap.availableToneMapModes</range>
8747 When switching to an application-defined contrast curve by setting
8748 android.tonemap.mode to CONTRAST_CURVE, the curve is defined
8749 per-channel with a set of `(in, out)` points that specify the
8750 mapping from input high-bit-depth pixel value to the output
8751 low-bit-depth value. Since the actual pixel ranges of both input
8752 and output may change depending on the camera pipeline, the values
8753 are specified by normalized floating-point numbers.
8755 More-complex color mapping operations such as 3D color look-up
8756 tables, selective chroma enhancement, or other non-linear color
8757 transforms will be disabled when android.tonemap.mode is
8760 When using either FAST or HIGH_QUALITY, the camera device will
8761 emit its own tonemap curve in android.tonemap.curve.
8762 These values are always available, and as close as possible to the
8763 actually used nonlinear/nonglobal transforms.
8765 If a request is sent with CONTRAST_CURVE with the camera device's
8766 provided curve in FAST or HIGH_QUALITY, the image's tonemap will be
8767 roughly the same.</details>
8771 <entry name="maxCurvePoints" type="int32" visibility="public"
8773 <description>Maximum number of supported points in the
8774 tonemap curve that can be used for android.tonemap.curve.
8777 If the actual number of points provided by the application (in android.tonemap.curve*) is
8778 less than this maximum, the camera device will resample the curve to its internal
8779 representation, using linear interpolation.
8781 The output curves in the result metadata may have a different number
8782 of points than the input curves, and will represent the actual
8783 hardware curves used as closely as possible when linearly interpolated.
8786 This value must be at least 64. This should be at least 128.
8789 <entry name="availableToneMapModes" type="byte" visibility="public"
8790 type_notes="list of enums" container="array" typedef="enumList" hwlevel="full">
8795 List of tonemapping modes for android.tonemap.mode that are supported by this camera
8798 <range>Any value listed in android.tonemap.mode</range>
8800 Camera devices that support the MANUAL_POST_PROCESSING capability will always contain
8801 at least one of below mode combinations:
8803 * CONTRAST_CURVE, FAST and HIGH_QUALITY
8804 * GAMMA_VALUE, PRESET_CURVE, FAST and HIGH_QUALITY
8806 This includes all FULL level devices.
8809 HAL must support both FAST and HIGH_QUALITY if automatic tonemap control is available
8810 on the camera device, but the underlying implementation can be the same for both modes.
8811 That is, if the highest quality implementation on the camera device does not slow down
8812 capture rate, then FAST and HIGH_QUALITY will generate the same output.
8817 <clone entry="android.tonemap.curveBlue" kind="controls">
8819 <clone entry="android.tonemap.curveGreen" kind="controls">
8821 <clone entry="android.tonemap.curveRed" kind="controls">
8823 <clone entry="android.tonemap.curve" kind="controls">
8825 <clone entry="android.tonemap.mode" kind="controls">
8829 <entry name="gamma" type="float" visibility="public">
8830 <description> Tonemapping curve to use when android.tonemap.mode is
8834 The tonemap curve will be defined the following formula:
8835 * OUT = pow(IN, 1.0 / gamma)
8836 where IN and OUT is the input pixel value scaled to range [0.0, 1.0],
8837 pow is the power function and gamma is the gamma value specified by this
8840 The same curve will be applied to all color channels. The camera device
8841 may clip the input gamma value to its supported range. The actual applied
8842 value will be returned in capture result.
8844 The valid range of gamma value varies on different devices, but values
8845 within [1.0, 5.0] are guaranteed not to be clipped.
8848 <entry name="presetCurve" type="byte" visibility="public" enum="true">
8851 <notes>Tonemapping curve is defined by sRGB</notes>
8854 <notes>Tonemapping curve is defined by ITU-R BT.709</notes>
8857 <description> Tonemapping curve to use when android.tonemap.mode is
8861 The tonemap curve will be defined by specified standard.
8863 sRGB (approximated by 16 control points):
8865 ![sRGB tonemapping curve](android.tonemap.curveRed/srgb_tonemap.png)
8867 Rec. 709 (approximated by 16 control points):
8869 ![Rec. 709 tonemapping curve](android.tonemap.curveRed/rec709_tonemap.png)
8871 Note that above figures show a 16 control points approximation of preset
8872 curves. Camera devices may apply a different approximation to the curve.
8877 <clone entry="android.tonemap.gamma" kind="controls">
8879 <clone entry="android.tonemap.presetCurve" kind="controls">
8883 <section name="led">
8885 <entry name="transmit" type="byte" visibility="hidden" optional="true"
8886 enum="true" typedef="boolean">
8891 <description>This LED is nominally used to indicate to the user
8892 that the camera is powered on and may be streaming images back to the
8893 Application Processor. In certain rare circumstances, the OS may
8894 disable this when video is processed locally and not transmitted to
8895 any untrusted applications.
8897 In particular, the LED *must* always be on when the data could be
8898 transmitted off the device. The LED *should* always be on whenever
8899 data is stored locally on the device.
8901 The LED *may* be off if a trusted application is using the data that
8902 doesn't violate the above rules.
8907 <clone entry="android.led.transmit" kind="controls"></clone>
8910 <entry name="availableLeds" type="byte" visibility="hidden" optional="true"
8918 <notes>android.led.transmit control is used.</notes>
8921 <description>A list of camera LEDs that are available on this system.
8926 <section name="info">
8928 <entry name="supportedHardwareLevel" type="byte" visibility="public"
8929 enum="true" hwlevel="legacy">
8934 This camera device does not have enough capabilities to qualify as a `FULL` device or
8937 Only the stream configurations listed in the `LEGACY` and `LIMITED` tables in the
8938 {@link android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession
8939 createCaptureSession} documentation are guaranteed to be supported.
8941 All `LIMITED` devices support the `BACKWARDS_COMPATIBLE` capability, indicating basic
8942 support for color image capture. The only exception is that the device may
8943 alternatively support only the `DEPTH_OUTPUT` capability, if it can only output depth
8944 measurements and not color images.
8946 `LIMITED` devices and above require the use of android.control.aePrecaptureTrigger
8947 to lock exposure metering (and calculate flash power, for cameras with flash) before
8948 capturing a high-quality still image.
8950 A `LIMITED` device that only lists the `BACKWARDS_COMPATIBLE` capability is only
8951 required to support full-automatic operation and post-processing (`OFF` is not
8952 supported for android.control.aeMode, android.control.afMode, or
8953 android.control.awbMode)
8955 Additional capabilities may optionally be supported by a `LIMITED`-level device, and
8956 can be checked for in android.request.availableCapabilities.
8962 This camera device is capable of supporting advanced imaging applications.
8964 The stream configurations listed in the `FULL`, `LEGACY` and `LIMITED` tables in the
8965 {@link android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession
8966 createCaptureSession} documentation are guaranteed to be supported.
8968 A `FULL` device will support below capabilities:
8970 * `BURST_CAPTURE` capability (android.request.availableCapabilities contains
8972 * Per frame control (android.sync.maxLatency `==` PER_FRAME_CONTROL)
8973 * Manual sensor control (android.request.availableCapabilities contains `MANUAL_SENSOR`)
8974 * Manual post-processing control (android.request.availableCapabilities contains
8975 `MANUAL_POST_PROCESSING`)
8976 * The required exposure time range defined in android.sensor.info.exposureTimeRange
8977 * The required maxFrameDuration defined in android.sensor.info.maxFrameDuration
8980 Pre-API level 23, FULL devices also supported arbitrary cropping region
8981 (android.scaler.croppingType `== FREEFORM`); this requirement was relaxed in API level
8982 23, and `FULL` devices may only support `CENTERED` cropping.
8988 This camera device is running in backward compatibility mode.
8990 Only the stream configurations listed in the `LEGACY` table in the {@link
8991 android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession
8992 createCaptureSession} documentation are supported.
8994 A `LEGACY` device does not support per-frame control, manual sensor control, manual
8995 post-processing, arbitrary cropping regions, and has relaxed performance constraints.
8996 No additional capabilities beyond `BACKWARD_COMPATIBLE` will ever be listed by a
8997 `LEGACY` device in android.request.availableCapabilities.
8999 In addition, the android.control.aePrecaptureTrigger is not functional on `LEGACY`
9000 devices. Instead, every request that includes a JPEG-format output target is treated
9001 as triggering a still capture, internally executing a precapture trigger. This may
9002 fire the flash for flash power metering during precapture, and then fire the flash
9003 for the final capture, if a flash is available on the device and the AE mode is set to
9010 This camera device is capable of YUV reprocessing and RAW data capture, in addition to
9011 FULL-level capabilities.
9013 The stream configurations listed in the `LEVEL_3`, `RAW`, `FULL`, `LEGACY` and
9014 `LIMITED` tables in the {@link
9015 android.hardware.camera2.CameraDevice#createCaptureSession|ACameraDevice_createCaptureSession
9016 createCaptureSession} documentation are guaranteed to be supported.
9018 The following additional capabilities are guaranteed to be supported:
9020 * `YUV_REPROCESSING` capability (android.request.availableCapabilities contains
9022 * `RAW` capability (android.request.availableCapabilities contains
9026 <value hal_version="3.3">
9029 This camera device is backed by an external camera connected to this Android device.
9031 The device has capability identical to a LIMITED level device, with the following
9034 * The device may not report lens/sensor related information such as
9035 - android.lens.focalLength
9036 - android.lens.info.hyperfocalDistance
9037 - android.sensor.info.physicalSize
9038 - android.sensor.info.whiteLevel
9039 - android.sensor.blackLevelPattern
9040 - android.sensor.info.colorFilterArrangement
9041 - android.sensor.rollingShutterSkew
9042 * The device will report 0 for android.sensor.orientation
9043 * The device has less guarantee on stable framerate, as the framerate partly depends
9044 on the external camera being used.
9049 Generally classifies the overall set of the camera device functionality.
9052 The supported hardware level is a high-level description of the camera device's
9053 capabilities, summarizing several capabilities into one field. Each level adds additional
9054 features to the previous one, and is always a strict superset of the previous level.
9055 The ordering is `LEGACY < LIMITED < FULL < LEVEL_3`.
9057 Starting from `LEVEL_3`, the level enumerations are guaranteed to be in increasing
9058 numerical value as well. To check if a given device is at least at a given hardware level,
9059 the following code snippet can be used:
9061 // Returns true if the device supports the required hardware level, or better.
9062 boolean isHardwareLevelSupported(CameraCharacteristics c, int requiredLevel) {
9063 int deviceLevel = c.get(CameraCharacteristics.INFO_SUPPORTED_HARDWARE_LEVEL);
9064 if (deviceLevel == CameraCharacteristics.INFO_SUPPORTED_HARDWARE_LEVEL_LEGACY) {
9065 return requiredLevel == deviceLevel;
9067 // deviceLevel is not LEGACY, can use numerical sort
9068 return requiredLevel <= deviceLevel;
9071 At a high level, the levels are:
9073 * `LEGACY` devices operate in a backwards-compatibility mode for older
9074 Android devices, and have very limited capabilities.
9075 * `LIMITED` devices represent the
9076 baseline feature set, and may also include additional capabilities that are
9078 * `FULL` devices additionally support per-frame manual control of sensor, flash, lens and
9079 post-processing settings, and image capture at a high rate.
9080 * `LEVEL_3` devices additionally support YUV reprocessing and RAW image capture, along
9081 with additional output stream configurations.
9083 See the individual level enums for full descriptions of the supported capabilities. The
9084 android.request.availableCapabilities entry describes the device's capabilities at a
9085 finer-grain level, if needed. In addition, many controls have their available settings or
9086 ranges defined in individual entries from {@link
9087 android.hardware.camera2.CameraCharacteristics|ACameraManager_getCameraCharacteristics}.
9089 Some features are not part of any particular hardware level or capability and must be
9090 queried separately. These include:
9092 * Calibrated timestamps (android.sensor.info.timestampSource `==` REALTIME)
9093 * Precision lens control (android.lens.info.focusDistanceCalibration `==` CALIBRATED)
9094 * Face detection (android.statistics.info.availableFaceDetectModes)
9095 * Optical or electrical image stabilization
9096 (android.lens.info.availableOpticalStabilization,
9097 android.control.availableVideoStabilizationModes)
9101 A camera HALv3 device can implement one of three possible operational modes; LIMITED,
9104 FULL support or better is expected from new higher-end devices. Limited
9105 mode has hardware requirements roughly in line with those for a camera HAL device v1
9106 implementation, and is expected from older or inexpensive devices. Each level is a strict
9107 superset of the previous level, and they share the same essential operational flow.
9109 For full details refer to "S3. Operational Modes" in camera3.h
9111 Camera HAL3+ must not implement LEGACY mode. It is there for backwards compatibility in
9112 the `android.hardware.camera2` user-facing API only on legacy HALv1 devices, and is
9113 implemented by the camera framework code.
9115 EXTERNAL level devices have lower peformance bar in CTS since the peformance might depend
9116 on the external camera being used and is not fully controlled by the device manufacturer.
9117 The ITS test suite is exempted for the same reason.
9120 <entry name="version" type="byte" visibility="public" typedef="string" hal_version="3.3">
9122 A short string for manufacturer version information about the camera device, such as
9123 ISP hardware, sensors, etc.
9126 This can be used in {@link android.media.ExifInterface#TAG_IMAGE_DESCRIPTION TAG_IMAGE_DESCRIPTION}
9127 in jpeg EXIF. This key may be absent if no version information is available on the
9131 The string must consist of only alphanumeric characters, punctuation, and
9132 whitespace, i.e. it must match regular expression "[\p{Alnum}\p{Punct}\p{Space}]*".
9133 It must not exceed 256 characters.
9138 <section name="blackLevel">
9140 <entry name="lock" type="byte" visibility="public" enum="true"
9141 typedef="boolean" hwlevel="full">
9146 <description> Whether black-level compensation is locked
9147 to its current values, or is free to vary.</description>
9148 <details>When set to `true` (ON), the values used for black-level
9149 compensation will not change until the lock is set to
9152 Since changes to certain capture parameters (such as
9153 exposure time) may require resetting of black level
9154 compensation, the camera device must report whether setting
9155 the black level lock was successful in the output result
9158 For example, if a sequence of requests is as follows:
9160 * Request 1: Exposure = 10ms, Black level lock = OFF
9161 * Request 2: Exposure = 10ms, Black level lock = ON
9162 * Request 3: Exposure = 10ms, Black level lock = ON
9163 * Request 4: Exposure = 20ms, Black level lock = ON
9164 * Request 5: Exposure = 20ms, Black level lock = ON
9165 * Request 6: Exposure = 20ms, Black level lock = ON
9167 And the exposure change in Request 4 requires the camera
9168 device to reset the black level offsets, then the output
9169 result metadata is expected to be:
9171 * Result 1: Exposure = 10ms, Black level lock = OFF
9172 * Result 2: Exposure = 10ms, Black level lock = ON
9173 * Result 3: Exposure = 10ms, Black level lock = ON
9174 * Result 4: Exposure = 20ms, Black level lock = OFF
9175 * Result 5: Exposure = 20ms, Black level lock = ON
9176 * Result 6: Exposure = 20ms, Black level lock = ON
9178 This indicates to the application that on frame 4, black
9179 levels were reset due to exposure value changes, and pixel
9180 values may not be consistent across captures.
9182 The camera device will maintain the lock to the extent
9183 possible, only overriding the lock to OFF when changes to
9184 other request parameters require a black level recalculation
9188 If for some reason black level locking is no longer possible
9189 (for example, the analog gain has changed, which forces
9190 black level offsets to be recalculated), then the HAL must
9191 override this request (and it must report 'OFF' when this
9192 does happen) until the next capture for which locking is
9193 possible again.</hal_details>
9198 <clone entry="android.blackLevel.lock"
9201 Whether the black level offset was locked for this frame. Should be
9202 ON if android.blackLevel.lock was ON in the capture request, unless
9203 a change in other capture settings forced the camera device to
9204 perform a black level reset.
9209 <section name="sync">
9211 <entry name="frameNumber" type="int64" visibility="ndk_public"
9212 enum="true" hwlevel="legacy">
9214 <value id="-1">CONVERGING
9216 The current result is not yet fully synchronized to any request.
9218 Synchronization is in progress, and reading metadata from this
9219 result may include a mix of data that have taken effect since the
9220 last synchronization time.
9222 In some future result, within android.sync.maxLatency frames,
9223 this value will update to the actual frame number frame number
9224 the result is guaranteed to be synchronized to (as long as the
9225 request settings remain constant).
9228 <value id="-2">UNKNOWN
9230 The current result's synchronization status is unknown.
9232 The result may have already converged, or it may be in
9233 progress. Reading from this result may include some mix
9234 of settings from past requests.
9236 After a settings change, the new settings will eventually all
9237 take effect for the output buffers and results. However, this
9238 value will not change when that happens. Altering settings
9239 rapidly may provide outcomes using mixes of settings from recent
9242 This value is intended primarily for backwards compatibility with
9243 the older camera implementations (for android.hardware.Camera).
9247 <description>The frame number corresponding to the last request
9248 with which the output result (metadata + buffers) has been fully
9249 synchronized.</description>
9250 <range>Either a non-negative value corresponding to a
9251 `frame_number`, or one of the two enums (CONVERGING / UNKNOWN).
9254 When a request is submitted to the camera device, there is usually a
9255 delay of several frames before the controls get applied. A camera
9256 device may either choose to account for this delay by implementing a
9257 pipeline and carefully submit well-timed atomic control updates, or
9258 it may start streaming control changes that span over several frame
9261 In the latter case, whenever a request's settings change relative to
9262 the previous submitted request, the full set of changes may take
9263 multiple frame durations to fully take effect. Some settings may
9264 take effect sooner (in less frame durations) than others.
9266 While a set of control changes are being propagated, this value
9269 Once it is fully known that a set of control changes have been
9270 finished propagating, and the resulting updated control settings
9271 have been read back by the camera device, this value will be set
9272 to a non-negative frame number (corresponding to the request to
9273 which the results have synchronized to).
9275 Older camera device implementations may not have a way to detect
9276 when all camera controls have been applied, and will always set this
9279 FULL capability devices will always have this value set to the
9280 frame number of the request corresponding to this result.
9284 * Whenever a request differs from the last request, any future
9285 results not yet returned may have this value set to CONVERGING (this
9286 could include any in-progress captures not yet returned by the camera
9287 device, for more details see pipeline considerations below).
9288 * Submitting a series of multiple requests that differ from the
9289 previous request (e.g. r1, r2, r3 s.t. r1 != r2 != r3)
9290 moves the new synchronization frame to the last non-repeating
9291 request (using the smallest frame number from the contiguous list of
9292 repeating requests).
9293 * Submitting the same request repeatedly will not change this value
9294 to CONVERGING, if it was already a non-negative value.
9295 * When this value changes to non-negative, that means that all of the
9296 metadata controls from the request have been applied, all of the
9297 metadata controls from the camera device have been read to the
9298 updated values (into the result), and all of the graphics buffers
9299 corresponding to this result are also synchronized to the request.
9301 _Pipeline considerations_:
9303 Submitting a request with updated controls relative to the previously
9304 submitted requests may also invalidate the synchronization state
9305 of all the results corresponding to currently in-flight requests.
9307 In other words, results for this current request and up to
9308 android.request.pipelineMaxDepth prior requests may have their
9309 android.sync.frameNumber change to CONVERGING.
9312 Using UNKNOWN here is illegal unless android.sync.maxLatency
9315 FULL capability devices should simply set this value to the
9316 `frame_number` of the request this result corresponds to.
9322 <entry name="maxLatency" type="int32" visibility="public" enum="true"
9325 <value id="0">PER_FRAME_CONTROL
9327 Every frame has the requests immediately applied.
9329 Changing controls over multiple requests one after another will
9330 produce results that have those controls applied atomically
9333 All FULL capability devices will have this as their maxLatency.
9336 <value id="-1">UNKNOWN
9338 Each new frame has some subset (potentially the entire set)
9339 of the past requests applied to the camera settings.
9341 By submitting a series of identical requests, the camera device
9342 will eventually have the camera settings applied, but it is
9343 unknown when that exact point will be.
9345 All LEGACY capability devices will have this as their maxLatency.
9350 The maximum number of frames that can occur after a request
9351 (different than the previous) has been submitted, and before the
9352 result's state becomes synchronized.
9354 <units>Frame counts</units>
9355 <range>A positive value, PER_FRAME_CONTROL, or UNKNOWN.</range>
9357 This defines the maximum distance (in number of metadata results),
9358 between the frame number of the request that has new controls to apply
9359 and the frame number of the result that has all the controls applied.
9361 In other words this acts as an upper boundary for how many frames
9362 must occur before the camera device knows for a fact that the new
9363 submitted camera settings have been applied in outgoing frames.
9366 For example if maxLatency was 2,
9368 initial request = X (repeating)
9374 where requestN has frameNumber N, and the first of the repeating
9375 initial request's has frameNumber F (and F < 1).
9377 initial result = X' + { android.sync.frameNumber == F }
9378 result1 = X' + { android.sync.frameNumber == F }
9379 result2 = X' + { android.sync.frameNumber == CONVERGING }
9380 result3 = X' + { android.sync.frameNumber == CONVERGING }
9381 result4 = X' + { android.sync.frameNumber == 2 }
9383 where resultN has frameNumber N.
9385 Since `result4` has a `frameNumber == 4` and
9386 `android.sync.frameNumber == 2`, the distance is clearly
9389 Use `frame_count` from camera3_request_t instead of
9390 android.request.frameCount or
9391 `{@link android.hardware.camera2.CaptureResult#getFrameNumber}`.
9393 LIMITED devices are strongly encouraged to use a non-negative
9394 value. If UNKNOWN is used here then app developers do not have a way
9395 to know when sensor settings have been applied.
9401 <section name="reprocess">
9403 <entry name="effectiveExposureFactor" type="float" visibility="java_public" hwlevel="limited">
9405 The amount of exposure time increase factor applied to the original output
9406 frame by the application processing before sending for reprocessing.
9408 <units>Relative exposure time increase factor.</units>
9409 <range> &gt;= 1.0</range>
9411 This is optional, and will be supported if the camera device supports YUV_REPROCESSING
9412 capability (android.request.availableCapabilities contains YUV_REPROCESSING).
9414 For some YUV reprocessing use cases, the application may choose to filter the original
9415 output frames to effectively reduce the noise to the same level as a frame that was
9416 captured with longer exposure time. To be more specific, assuming the original captured
9417 images were captured with a sensitivity of S and an exposure time of T, the model in
9418 the camera device is that the amount of noise in the image would be approximately what
9419 would be expected if the original capture parameters had been a sensitivity of
9420 S/effectiveExposureFactor and an exposure time of T*effectiveExposureFactor, rather
9421 than S and T respectively. If the captured images were processed by the application
9422 before being sent for reprocessing, then the application may have used image processing
9423 algorithms and/or multi-frame image fusion to reduce the noise in the
9424 application-processed images (input images). By using the effectiveExposureFactor
9425 control, the application can communicate to the camera device the actual noise level
9426 improvement in the application-processed image. With this information, the camera
9427 device can select appropriate noise reduction and edge enhancement parameters to avoid
9428 excessive noise reduction (android.noiseReduction.mode) and insufficient edge
9429 enhancement (android.edge.mode) being applied to the reprocessed frames.
9431 For example, for multi-frame image fusion use case, the application may fuse
9432 multiple output frames together to a final frame for reprocessing. When N image are
9433 fused into 1 image for reprocessing, the exposure time increase factor could be up to
9434 square root of N (based on a simple photon shot noise model). The camera device will
9435 adjust the reprocessing noise reduction and edge enhancement parameters accordingly to
9436 produce the best quality images.
9438 This is relative factor, 1.0 indicates the application hasn't processed the input
9439 buffer in a way that affects its effective exposure time.
9441 This control is only effective for YUV reprocessing capture request. For noise
9442 reduction reprocessing, it is only effective when `android.noiseReduction.mode != OFF`.
9443 Similarly, for edge enhancement reprocessing, it is only effective when
9444 `android.edge.mode != OFF`.
9450 <clone entry="android.reprocess.effectiveExposureFactor" kind="controls">
9454 <entry name="maxCaptureStall" type="int32" visibility="java_public" hwlevel="limited">
9456 The maximal camera capture pipeline stall (in unit of frame count) introduced by a
9457 reprocess capture request.
9459 <units>Number of frames.</units>
9460 <range> &lt;= 4</range>
9462 The key describes the maximal interference that one reprocess (input) request
9463 can introduce to the camera simultaneous streaming of regular (output) capture
9464 requests, including repeating requests.
9466 When a reprocessing capture request is submitted while a camera output repeating request
9467 (e.g. preview) is being served by the camera device, it may preempt the camera capture
9468 pipeline for at least one frame duration so that the camera device is unable to process
9469 the following capture request in time for the next sensor start of exposure boundary.
9470 When this happens, the application may observe a capture time gap (longer than one frame
9471 duration) between adjacent capture output frames, which usually exhibits as preview
9472 glitch if the repeating request output targets include a preview surface. This key gives
9473 the worst-case number of frame stall introduced by one reprocess request with any kind of
9474 formats/sizes combination.
9476 If this key reports 0, it means a reprocess request doesn't introduce any glitch to the
9477 ongoing camera repeating request outputs, as if this reprocess request is never issued.
9479 This key is supported if the camera device supports PRIVATE or YUV reprocessing (
9480 i.e. android.request.availableCapabilities contains PRIVATE_REPROCESSING or
9487 <section name="depth">
9489 <entry name="maxDepthSamples" type="int32" visibility="system" hwlevel="limited">
9490 <description>Maximum number of points that a depth point cloud may contain.
9493 If a camera device supports outputting depth range data in the form of a depth point
9494 cloud ({@link android.graphics.ImageFormat#DEPTH_POINT_CLOUD}), this is the maximum
9495 number of points an output buffer may contain.
9497 Any given buffer may contain between 0 and maxDepthSamples points, inclusive.
9498 If output in the depth point cloud format is not supported, this entry will
9503 <entry name="availableDepthStreamConfigurations" type="int32" visibility="ndk_public"
9504 enum="true" container="array" typedef="streamConfiguration" hwlevel="limited">
9510 <value>OUTPUT</value>
9511 <value>INPUT</value>
9513 <description>The available depth dataspace stream
9514 configurations that this camera device supports
9515 (i.e. format, width, height, output/input stream).
9518 These are output stream configurations for use with
9519 dataSpace HAL_DATASPACE_DEPTH. The configurations are
9520 listed as `(format, width, height, input?)` tuples.
9522 Only devices that support depth output for at least
9523 the HAL_PIXEL_FORMAT_Y16 dense depth map may include
9526 A device that also supports the HAL_PIXEL_FORMAT_BLOB
9527 sparse depth point cloud must report a single entry for
9528 the format in this list as `(HAL_PIXEL_FORMAT_BLOB,
9529 android.depth.maxDepthSamples, 1, OUTPUT)` in addition to
9530 the entries for HAL_PIXEL_FORMAT_Y16.
9534 <entry name="availableDepthMinFrameDurations" type="int64" visibility="ndk_public"
9535 container="array" typedef="streamConfigurationDuration" hwlevel="limited">
9540 <description>This lists the minimum frame duration for each
9541 format/size combination for depth output formats.
9543 <units>(format, width, height, ns) x n</units>
9545 This should correspond to the frame duration when only that
9546 stream is active, with all processing (typically in android.*.mode)
9547 set to either OFF or FAST.
9549 When multiple streams are used in a request, the minimum frame
9550 duration will be max(individual stream min durations).
9552 The minimum frame duration of a stream (of a particular format, size)
9553 is the same regardless of whether the stream is input or output.
9555 See android.sensor.frameDuration and
9556 android.scaler.availableStallDurations for more details about
9557 calculating the max frame rate.
9561 <entry name="availableDepthStallDurations" type="int64" visibility="ndk_public"
9562 container="array" typedef="streamConfigurationDuration" hwlevel="limited">
9567 <description>This lists the maximum stall duration for each
9568 output format/size combination for depth streams.
9570 <units>(format, width, height, ns) x n</units>
9572 A stall duration is how much extra time would get added
9573 to the normal minimum frame duration for a repeating request
9574 that has streams with non-zero stall.
9576 This functions similarly to
9577 android.scaler.availableStallDurations for depth
9580 All depth output stream formats may have a nonzero stall
9585 <entry name="depthIsExclusive" type="byte" visibility="public"
9586 enum="true" typedef="boolean" hwlevel="limited">
9588 <value>FALSE</value>
9591 <description>Indicates whether a capture request may target both a
9592 DEPTH16 / DEPTH_POINT_CLOUD output, and normal color outputs (such as
9593 YUV_420_888, JPEG, or RAW) simultaneously.
9596 If TRUE, including both depth and color outputs in a single
9597 capture request is not supported. An application must interleave color
9598 and depth requests. If FALSE, a single request can target both types
9601 Typically, this restriction exists on camera devices that
9602 need to emit a specific pattern or wavelength of light to
9603 measure depth values, which causes the color image to be
9604 corrupted during depth measurement.
9609 <section name="logicalMultiCamera">
9611 <entry name="physicalIds" type="byte" visibility="hidden"
9612 container="array" hwlevel="limited" hal_version="3.3">
9616 <description>String containing the ids of the underlying physical cameras.
9618 <units>UTF-8 null-terminated string</units>
9620 For a logical camera, this is concatenation of all underlying physical camera ids.
9621 The null terminator for physical camera id must be preserved so that the whole string
9622 can be tokenized using '\0' to generate list of physical camera ids.
9624 For example, if the physical camera ids of the logical camera are "2" and "3", the
9625 value of this tag will be ['2', '\0', '3', '\0'].
9627 The number of physical camera ids must be no less than 2.
9629 <tag id="LOGICALCAMERA" />
9631 <entry name="sensorSyncType" type="byte" visibility="public"
9632 enum="true" hwlevel="limited" hal_version="3.3">
9636 A software mechanism is used to synchronize between the physical cameras. As a result,
9637 the timestamp of an image from a physical stream is only an approximation of the
9638 image sensor start-of-exposure time.
9643 The camera device supports frame timestamp synchronization at the hardware level,
9644 and the timestamp of a physical stream image accurately reflects its
9645 start-of-exposure time.
9649 <description>The accuracy of frame timestamp synchronization between physical cameras</description>
9651 The accuracy of the frame timestamp synchronization determines the physical cameras'
9652 ability to start exposure at the same time. If the sensorSyncType is CALIBRATED,
9653 the physical camera sensors usually run in master-slave mode so that their shutter
9654 time is synchronized. For APPROXIMATE sensorSyncType, the camera sensors usually run in
9655 master-master mode, and there could be offset between their start of exposure.
9657 In both cases, all images generated for a particular capture request still carry the same
9658 timestamps, so that they can be used to look up the matching frame number and
9659 onCaptureStarted callback.
9661 <tag id="LOGICALCAMERA" />
9665 <section name="distortionCorrection">
9667 <entry name="mode" type="byte" visibility="public" enum="true" hal_version="3.3">
9670 <notes>No distortion correction is applied.</notes></value>
9671 <value>FAST <notes>Lens distortion correction is applied without reducing frame rate
9672 relative to sensor output. It may be the same as OFF if distortion correction would
9673 reduce frame rate relative to sensor.</notes></value>
9674 <value>HIGH_QUALITY <notes>High-quality distortion correction is applied, at the cost of
9675 possibly reduced frame rate relative to sensor output.</notes></value>
9677 <description>Mode of operation for the lens distortion correction block.</description>
9678 <range>android.distortionCorrection.availableModes</range>
9679 <details>The lens distortion correction block attempts to improve image quality by fixing
9680 radial, tangential, or other geometric aberrations in the camera device's optics. If
9681 available, the android.lens.distortion field documents the lens's distortion parameters.
9683 OFF means no distortion correction is done.
9685 FAST/HIGH_QUALITY both mean camera device determined distortion correction will be
9686 applied. HIGH_QUALITY mode indicates that the camera device will use the highest-quality
9687 correction algorithms, even if it slows down capture rate. FAST means the camera device
9688 will not slow down capture rate when applying correction. FAST may be the same as OFF if
9689 any correction at all would slow down capture rate. Every output stream will have a
9690 similar amount of enhancement applied.
9692 The correction only applies to processed outputs such as YUV, JPEG, or DEPTH16; it is not
9693 applied to any RAW output. Metadata coordinates such as face rectangles or metering
9694 regions are also not affected by correction.
9696 Applications enabling distortion correction need to pay extra attention when converting
9697 image coordinates between corrected output buffers and the sensor array. For example, if
9698 the app supports tap-to-focus and enables correction, it then has to apply the distortion
9699 model described in android.lens.distortion to the image buffer tap coordinates to properly
9700 calculate the tap position on the sensor active array to be used with
9701 android.control.afRegions. The same applies in reverse to detected face rectangles if
9702 they need to be drawn on top of the corrected output buffers.
9707 <entry name="availableModes" type="byte" visibility="public"
9708 type_notes="list of enums" container="array" typedef="enumList" hal_version="3.3">
9713 List of distortion correction modes for android.distortionCorrection.mode that are
9714 supported by this camera device.
9716 <range>Any value listed in android.distortionCorrection.mode</range>
9718 No device is required to support this API; such devices will always list only 'OFF'.
9719 All devices that support this API will list both FAST and HIGH_QUALITY.
9722 HAL must support both FAST and HIGH_QUALITY if distortion correction is available
9723 on the camera device, but the underlying implementation can be the same for both modes.
9724 That is, if the highest quality implementation on the camera device does not slow down
9725 capture rate, then FAST and HIGH_QUALITY will generate the same output.
9732 <clone entry="android.distortionCorrection.mode" kind="controls" hal_version="3.3">