This article provides guidance and recommendations for launching playback of Dolby Vision content in Android Automotive media applications. Developing a detailed test plan that covers all relevant aspects remains at the discretion of developers.

To help design a test plan or test an application, this article includes a list of test scenarios and test cases.

Note: When obtaining test signals for Dolby Vision testing, use only non-DRM (clear) content. DRM-protected content is not supported in the Dolby Vision and Atmos Automotive Emulator Image. Additionally, AAC support is not included in this release, so any test signals containing AAC audio will play back as video-only.

Test content can be found here.

Details on enabling Dolby Vision Playback on Android Automotive OS Media Apps can be found here.

Introduction

The listed test areas include test scenarios that may help creating a test plan for a media app. Playback should proceed smoothly without dropped frames, visual corruption, temporal glitches, or any other objectionable visual anomalies. Content should be displayed without loss of visual information.

Basic Playback

1. Verify playback with relevant files and streaming formats that are supported by your app. 

• • Content with different Dolby Vision profiles that are supported by your app.
    • Dolby Vision Profile 5
    • Dolby Vision Profile 8.1
    • Dolby Vision Profile 8.4
  • Dolby Vision playback with different framerates.
    • 30 fps
    • 60 fps
  • Streaming input formats that applies to your service(s).
    • DASH
    • HLS

System Interaction

1. Verify that operating controls repeatedly does not cause any issues during playback of Dolby Vision content. Examples of operating controls are:
   • Play/Pause
   • Seek
   • Stop
   • Next/Previous

Format Switching

Verify transitions between Dolby Vision content to SDR content. Transition between Dolby Vision content and SDR content should be smooth, without noticeable brightness ramps or "flash bang" effect.