Multi-Camera Support

Android 9 introduces API support for multi-camera devices via a new logical camera device composed of two or more physical camera devices pointing in the same direction. The logical camera device is exposed as a single CameraDevice/CaptureSession to an application allowing for interaction with HAL-integrated multi-camera features. Applications can optionally access and control underlying physical camera streams, metadata, and controls.

Multi-camera support

Figure 1. Multi-camera support

In this diagram, different camera IDs are color coded. The application can stream raw buffers from each physical camera at the same time. It is also possible to set separate controls and receive separate metadata from different physical cameras.

Examples and sources

Multi-camera devices must be advertised via the logical multi-camera capability.

Camera clients can query the camera ID of the physical devices a particular logical camera is made of by calling getPhysicalCameraIds(). The IDs returned as part of the result are then used to control physical devices individually via setPhysicalCameraId(). The results from such individual requests can be queried from the complete result by invoking getPhysicalCameraResults().

Individual physical camera requests may support only a limited subset of parameters. To receive a list of the supported parameters, developers can call getAvailablePhysicalCameraRequestKeys().

Physical camera streams are supported only for non-reprocessing requests and only for monochrome and bayer sensors.


Support checklist

To add logical multi-camera devices on the HAL side:

The camera device must support replacing one logical YUV/RAW stream with physical streams of the same size (RAW size is an exception) and format from two physical cameras.

Stream configuration map

For a logical camera, the mandatory stream combinations for the camera device of a certain hardware level is the same as what's required in CameraDevice.createCaptureSession. All the streams in the stream configuration map should be fused/logical frames.

If certain stream combinations cannot be fused, they should not be included in the logical camera's stream configuration map. Instead the application can look up the stream configuration map of the individual physical camera and configure the stream using the physical camera ID.

This means that the logical camera's hardware level may be lower than that of individual cameras. One such example is when the two physical cameras have different raw sizes. The logical camera does not have RAW capability, so it cannot be a LEVEL_3 device, but the individual physical cameras can be LEVEL_3 devices.

For both the logical camera and the underlying physical cameras, the directly configured processed streams, RAW streams, and stall streams should not exceed the predefined android.request.maxNumOutputStreams.

Guaranteed stream combination

Both the logical camera and its underlying physical cameras must guarantee the mandatory stream combinations required for their device levels.

A logical camera device should operate in the same way as a physical camera device based on its hardware level and capabilities. It's recommended that its feature set is a superset of that of individual physical cameras.

Additionally, for each guaranteed stream combination, the logical camera must support:

  • Replacing one logical YUV_420_888 or raw stream with two physical streams of the same size and format, each from a separate physical camera, given that the size and format are supported by the physical cameras.

  • Adding two raw streams, one from each physical camera, if the logical camera doesn't advertise RAW capability, but the underlying physical cameras do. This usually occurs when the physical cameras have different sensor sizes.

Using physical streams in place of a logical stream of the same size and format must not slow down the frame rate of the capture, as long as the minimum frame duration of the physical and logical streams are the same.

Performance and power considerations

  • Performance:

    • Without attaching physical camera settings, physical streams should not slow down capture rate.
    • Applying physical camera settings may slow down the capture rate if the underlying cameras are put into different frame rates.
  • Power:

    • HAL's power optimization continues to work in the default case.
    • Configuring or requesting physical streams may override HAL's internal power optimization and incur more power use.


You can customize your device implementation in the following ways.

  • The fused output of the logical camera device depends entirely on the HAL implementation. The decision on how fused logical streams are derived from the physical cameras is transparent to the application and Android camera framework.
  • Individual physical requests and results can be optionally supported. The set of available parameters in such requests is also entirely dependent on the specific HAL implementation.


Logical multi-camera devices must pass Camera CTS like any other regular camera. The test cases that target this type of device can be found in the LogicalCameraDeviceTest module.

These three ITS tests target multi-camera systems to facilitate the proper fusing of images:

The scene1 and scene4 tests run with the ITS-in-a-box test rig. The test_multi_camera_match test asserts that the brightness of the center of the images match when the two cameras are both enabled. The test_multi_camera_alignment test asserts that camera spacings, orientations, and distortion parameters are properly loaded. If the multi-camera system includes a Wide FoV camera (>90o), the rev2 version of the ITS box is required.

Sensor_fusion is a second test rig that enables repeated, prescribed phone motion and asserts that the gyroscope and image sensor timestamps match and that the multi-camera frames are in sync.

All boxes are available through AcuSpec, Inc. (, and MYWAY Manufacturing (, Additionally, the rev1 ITS box can be purchased through West-Mark (,