Overview

This guide describes how to migrate your automotive camera implementations to the Camera2 APIs from the Extended View System (EVS) APIs. We plan to deprecate EVS APIs for camera functionality. This transition aims to standardize camera development on Android Automotive OS (AAOS) by using the Camera2 framework.

Reasons to migrate

These factors underpin the migration.

  • Unified API: Camera2 provides a single, consistent API for all camera development on Android, across all form factors (phones, tablets, TV, and vehicles).

  • Broader access: Camera2 is available to system, first-party, and third-party apps. This is unlike EVS, which is restricted to system and first-party apps.

  • Reduced fragmentation: Camera2 eliminates the need for OEMs to maintain and support two separate camera stacks.

  • Standard features: Camera2 benefits from ongoing enhancements and features developed for the core Android camera framework.

Affected EVS components

When EVS is deprecated, these EVS components could be affected:

EVS to Camera2 compatibility library

We plan to provide a compatibility library (shim layer) to support the transition of EVS clients to Camera2.

Test suite compliance

All Camera2 implementations must pass these Android compliance tests:

  • Compatibility Test Suite (CTS) verifies overall Android compatibility.
  • Vendor Test Suite (VTS) tests the Camera HAL interface.
  • Image Test Suite (ITS) verifies image quality and correctness.

To learn more, see Camera HAL testing.

Feedback

We value your feedback specific to migrating from EVS to Camera2. To provide input, see Report and track bugs. When you file an issue, include "EVS to Camera2 Migration Guide" in the title.