field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<java.lang.Integer> REQUEST_PARTIAL_RESULT_COUNT;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<java.lang.Byte> REQUEST_PIPELINE_MAX_DEPTH;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<java.lang.Float> SCALER_AVAILABLE_MAX_DIGITAL_ZOOM;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<int[]> SCALER_AVAILABLE_ROTATE_AND_CROP_MODES;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<java.lang.Integer> SCALER_CROPPING_TYPE;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<android.hardware.camera2.params.MandatoryStreamCombination[]> SCALER_MANDATORY_STREAM_COMBINATIONS;
field @NonNull public static final android.hardware.camera2.CameraCharacteristics.Key<android.hardware.camera2.params.StreamConfigurationMap> SCALER_STREAM_CONFIGURATION_MAP;
* <p>List of rotate-and-crop modes for {@link CaptureRequest#SCALER_ROTATE_AND_CROP android.scaler.rotateAndCrop} that are supported by this camera device.</p>
* <p>This entry lists the valid modes for {@link CaptureRequest#SCALER_ROTATE_AND_CROP android.scaler.rotateAndCrop} for this camera device.</p>
* <p>Starting with API level 30, all devices will list at least <code>ROTATE_AND_CROP_NONE</code>.
* Devices with support for rotate-and-crop will additionally list at least
* <code>ROTATE_AND_CROP_AUTO</code> and <code>ROTATE_AND_CROP_90</code>.</p>
* <p><b>Range of valid values:</b><br>
* Any value listed in {@link CaptureRequest#SCALER_ROTATE_AND_CROP android.scaler.rotateAndCrop}</p>
* <p><b>Optional</b> - The value for this key may be {@code null} on some devices.</p>
* <p>Capture results will contain the actual value selected by the API;
* <code>ROTATE_AND_CROP_AUTO</code> will never be seen in a capture result.</p>
* <p>Applications can also select their preferred cropping mode, either to opt out of the
* backwards-compatibility treatment, or to use the cropping feature themselves as needed.
* In this case, no coordinate translation will be done automatically, and all controls
* will continue to use the normal active array coordinates.</p>
* <p>Cropping and rotating is done after the application of digital zoom (via either
* {@link CaptureRequest#SCALER_CROP_REGION android.scaler.cropRegion} or {@link CaptureRequest#CONTROL_ZOOM_RATIO android.control.zoomRatio}), but before each individual
* output is further cropped and scaled. It only affects processed outputs such as
* YUV, PRIVATE, and JPEG. It has no effect on RAW outputs.</p>
* <p>When <code>CROP_90</code> or <code>CROP_270</code> are selected, there is a significant loss to the field of
* view. For example, with a 4:3 aspect ratio output of 1600x1200, <code>CROP_90</code> will still
* produce 1600x1200 output, but these buffers are cropped from a vertical 3:4 slice at the
* center of the 4:3 area, then rotated to be 4:3, and then upscaled to 1600x1200. Only
* 56.25% of the original FOV is still visible. In general, for an aspect ratio of <code>w:h</code>,
* the crop and rotate operation leaves <code>(h/w)^2</code> of the field of view visible. For 16:9,
* this is ~31.6%.</p>
* <p>As a visual example, the figure below shows the effect of <code>ROTATE_AND_CROP_90</code> on the
* outputs for the following parameters:</p>
* <ul>
* <li>Sensor active array: <code>2000x1500</code></li>
* <p>Capture results will contain the actual value selected by the API;
* <code>ROTATE_AND_CROP_AUTO</code> will never be seen in a capture result.</p>
* <p>Applications can also select their preferred cropping mode, either to opt out of the
* backwards-compatibility treatment, or to use the cropping feature themselves as needed.
* In this case, no coordinate translation will be done automatically, and all controls
* will continue to use the normal active array coordinates.</p>
* <p>Cropping and rotating is done after the application of digital zoom (via either
* {@link CaptureRequest#SCALER_CROP_REGION android.scaler.cropRegion} or {@link CaptureRequest#CONTROL_ZOOM_RATIO android.control.zoomRatio}), but before each individual
* output is further cropped and scaled. It only affects processed outputs such as
* YUV, PRIVATE, and JPEG. It has no effect on RAW outputs.</p>
* <p>When <code>CROP_90</code> or <code>CROP_270</code> are selected, there is a significant loss to the field of
* view. For example, with a 4:3 aspect ratio output of 1600x1200, <code>CROP_90</code> will still
* produce 1600x1200 output, but these buffers are cropped from a vertical 3:4 slice at the
* center of the 4:3 area, then rotated to be 4:3, and then upscaled to 1600x1200. Only
* 56.25% of the original FOV is still visible. In general, for an aspect ratio of <code>w:h</code>,
* the crop and rotate operation leaves <code>(h/w)^2</code> of the field of view visible. For 16:9,
* this is ~31.6%.</p>
* <p>As a visual example, the figure below shows the effect of <code>ROTATE_AND_CROP_90</code> on the
* outputs for the following parameters:</p>
* <ul>
* <li>Sensor active array: <code>2000x1500</code></li>
