Xiaomi Redmi Note 8 Pro 128Gb+6Gb Dual LTE [104/132] Memory and storage
Макгруп McGrp.ru
Задайте вопрос
Зарегистрироваться

Xiaomi Redmi Note 8 Pro 128Gb+6Gb Dual LTE [104/132] Memory and storage

Xiaomi Redmi Note 8 Pro 128Gb+6Gb Dual LTE [104/132] Memory and storage
[C-0-3] MUST support the YV12 format (as denoted by the android.graphics.ImageFormat.YV12
constant) for camera previews for both front- and rear-facing cameras for
android.hardware.Camera . (The hardware video encoder and camera may use any native pixel
format, but the device implementation MUST support conversion to YV12.)
[C-0-4] MUST support the android.hardware.ImageFormat.YUV_420_888 and
android.hardware.ImageFormat.JPEG formats as outputs through the android.media.ImageReader API
for android.hardware.camera2 devices that advertise
REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE capability in
android.request.availableCapabilities .
[C-0-5] MUST still implement the full Camera API included in the Android SDK
documentation, regardless of whether the device includes hardware autofocus or other
capabilities. For instance, cameras that lack autofocus MUST still call any registered
android.hardware.Camera.AutoFocusCallback instances (even though this has no relevance to a
non-autofocus camera.) Note that this does apply to front-facing cameras; for instance,
even though most front-facing cameras do not support autofocus, the API callbacks must
still be “faked” as described.
[C-0-6] MUST recognize and honor each parameter name defined as a constant on the
android.hardware.Camera.Parameters class. Conversely, device implementations MUST NOT
honor or recognize string constants passed to the android.hardware.Camera.setParameters()
method other than those documented as constants on the android.hardware.Camera.Parameters
. That is, device implementations MUST support all standard Camera parameters if the
hardware allows, and MUST NOT support custom Camera parameter types. For instance,
device implementations that support image capture using high dynamic range (HDR)
imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR .
[C-0-7] MUST report the proper level of support with the android.info.supportedHardwareLevel
property as described in the Android SDK and report the appropriate framework feature
flags .
[C-0-8] MUST also declare its individual camera capabilities of android.hardware.camera2 via
the android.request.availableCapabilities property and declare the appropriate feature flags ;
MUST define the feature flag if any of its attached camera devices supports the feature.
[C-0-9] MUST broadcast the Camera.ACTION_NEW_PICTURE intent whenever a new picture
is taken by the camera and the entry of the picture has been added to the media store.
[C-0-10] MUST broadcast the Camera.ACTION_NEW_VIDEO intent whenever a new video is
recorded by the camera and the entry of the picture has been added to the media store.
[C-SR] Are STRONGLY RECOMMENDED to support a logical camera device that lists
capability CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA
, for devices with multiple cameras facing the same direction, consisting of each physical
camera facing that direction, as long as the physical camera type is supported by the
framework and CameraCharacteristics.INFO_SUPPORTED_HARDWARE_LEVEL for the physical
cameras is either LIMITED , FULL , or LEVEL_3 .
7.5.5. Camera Orientation
If device implementations have a front- or a rear-facing camera, such camera(s):
[C-1-1] MUST be oriented so that the long dimension of the camera aligns with the
screen’s long dimension. That is, when the device is held in the landscape orientation,
cameras MUST capture images in the landscape orientation. This applies regardless of
the device’s natural orientation; that is, it applies to landscape-primary devices as well as
portrait-primary devices.
7.6. Memory and Storage
Page 104 of 132

Содержание

Похожие устройства

Скачать