Introduction: Unlocking Multi-Display Potential with AAOS Content Zones

Modern automotive experiences are evolving rapidly, moving beyond a single central display to complex multi-screen environments. Android Automotive OS (AAOS) provides a robust platform for these advanced infotainment systems. A critical capability for managing multiple displays effectively, especially when catering to diverse user needs like passenger entertainment and driver-specific information, is the implementation of custom content zones. These zones allow developers to precisely define areas on physical or virtual displays where specific content can be rendered, optimizing user experience and adhering to safety regulations. This guide will walk you through the process of defining, integrating, and managing custom content zones within AAOS.

Understanding Display & Zone Management in AAOS

AAOS leverages Android’s core display management capabilities, extending them with automotive-specific services. Traditionally, Android applications interact with a single primary display, or optionally, create virtual displays. However, in a vehicle, you might have a cluster display, a central infotainment unit, and multiple rear-seat entertainment screens, each with potentially different use cases and safety classifications. Content zones address this by providing a programmatic way to carve out specific regions on any display for dedicated content.

Key Components of AAOS Display & Zone Management

• DisplayManager & WindowManager: The foundational Android services for managing displays and windows.
• CarDisplayManager: The AAOS-specific service providing automotive-contextual display information.
• CarDisplayRegionManager: A crucial service within AAOS that allows defining and managing content regions (zones) on displays. This is where the core logic for custom zones resides.
• DisplayContentChangeListener: An interface for listening to changes in display content, useful for dynamic zone management.
• ActivityOptions: Used to specify target display and launch parameters when starting activities.

By defining zones, the system can enforce rules, manage focus, and control visibility more granularly than with full-screen activities on separate displays alone. This is particularly vital for safety-critical driver information, which must not be obscured by passenger entertainment.

Step-by-Step Implementation Guide for Custom Content Zones

Step 1: Define Your Custom Content Zones in XML

Content zones are typically defined in an XML configuration file, often located in the device’s system resources (e.g., /vendor/etc/car_display_config.xml or similar path accessible by the CarService). This file declares the properties of each zone.

Here’s an example of how you might define content zones:

<display_regions>
    <display_region
        id="passenger_entertainment_zone"
        displayId="1" 
        x="0" y="0" width="1280" height="720"
        priority="100"
        allowedActivities="com.example.passengerapp/com.example.passengerapp.EntertainmentActivity"
    />
    <display_region
        id="driver_info_widget_zone"
        displayId="0" 
        x="100" y="10" width="300" height="150"
        priority="200"
        allowedActivities="com.example.driverapp/com.example.driverapp.SpeedWidget"
    />
    <display_region
        id="driver_nav_panel_zone"
        displayId="0" 
        x="0" y="180" width="800" height="480"
        priority="150"
        allowedActivities="com.example.navapp/com.example.navapp.NavPanelActivity"
    />
</display_regions>

• id: A unique identifier for the content zone.
• displayId: The ID of the physical or virtual display this zone belongs to (0 for primary, higher for others).
• x, y, width, height: The coordinates and dimensions of the zone in pixels relative to the display.
• priority: Determines rendering order or focus priority (higher value usually means higher priority).
• allowedActivities: A comma-separated list of activity component names (package/class) that are permitted to launch into this zone. This is crucial for security and safety.

Step 2: Integrate Zones into Your System UI/CarService

Once defined, the CarService reads these configurations. Your application or System UI components can then interact with these zones via the CarDisplayRegionManager.

To access the manager and monitor zone changes:

// Kotlin example
import android.car.Car
import android.car.drivingdisplay.CarDisplayRegionManager
import android.car.drivingdisplay.DisplayContentChangeListener
import android.content.Context

class MyDrivingDisplayManager(context: Context) {

    private val car = Car.createCar(context, null)
    private val carDisplayRegionManager: CarDisplayRegionManager?

    init {
        carDisplayRegionManager = car.getCarManager(Car.CAR_DISPLAY_REGION_SERVICE) as? CarDisplayRegionManager
        carDisplayRegionManager?.registerDisplayContentChangeListener(object : DisplayContentChangeListener {
            override fun onDisplayContentChanged(displayId: Int, contentRegions: List<android.graphics.Rect>) {
                // Handle content changes for a specific display
                // E.g., update UI elements based on active content zones
                println("Display $displayId content changed: $contentRegions")
            }
        })
    }

    fun getPassengerZoneId(): String? {
        val displayRegions = carDisplayRegionManager?.getDisplayRegions(CarDisplayRegionManager.REGION_TYPE_CONTENT)
        return displayRegions?.firstOrNull { it.id == "passenger_entertainment_zone" }?.id
    }

    // Remember to unregister listener and disconnect Car object when no longer needed
    fun cleanup() {
        // carDisplayRegionManager?.unregisterDisplayContentChangeListener(listener)
        car.disconnect()
    }
}

Step 3: Develop Content Providers for Zones

To launch an activity into a specific content zone, you need to specify the target display ID and potentially the specific zone ID using ActivityOptions.

For passenger entertainment, assume EntertainmentActivity should launch into `passenger_entertainment_zone` on displayId=1.

// Kotlin example for launching an activity into a specific zone
import android.app.ActivityOptions
import android.content.Intent
import android.os.Bundle

fun launchPassengerEntertainment(context: Context, targetDisplayId: Int) {
    val intent = Intent(context, EntertainmentActivity::class.java)
    // Create ActivityOptions to target the specific display
    val options = ActivityOptions.makeBasic()
    options.setLaunchDisplayId(targetDisplayId)
    // For specific content zones, the system typically uses `ActivityOptions.setLaunchBounds()`
    // or relies on the `allowedActivities` in the XML definition for the zone.
    // In more advanced scenarios, `setLaunchDisplayId` is sufficient, with the CarService
    // managing which zone within that display the activity goes to based on its `allowedActivities`.
    
    context.startActivity(intent, options.toBundle())
}

The system’s CarService will then use the allowedActivities definition in display_regions.xml to determine if EntertainmentActivity is permitted in the requested zone on displayId=1. If multiple zones on the same display allow the activity, further logic (like priority or user interaction) might dictate the final placement.

Step 4: Managing Zone Visibility and Interactivity

AAOS provides mechanisms to control the visibility and input focus of activities launched into zones. For example, driver-facing zones might have stricter visibility rules, automatically dimming or hiding content that could distract the driver if the vehicle is in motion. Passenger zones, on the other hand, might offer full interactivity.

• ActivityVisibilityController: Can be used by the system to manage activity visibility based on vehicle state (e.g., speed, gear).
• Input Focus Management: The WindowManager, in conjunction with CarService, handles which display or zone currently receives input events. This is critical for preventing driver distraction from passenger input.

Developers generally don’t directly manipulate these low-level visibility controllers but rather define the behavior and allowed activities in their XML configurations and manifest files. The CarService enforces these policies.

Step 5: Testing and Debugging

Testing multi-display and content zone setups often requires an emulator configured with multiple displays or a physical AAOS development board connected to external screens.

• List Displays: Use ADB to list active displays and their IDs:adb shell dumpsys display
• Simulate Virtual Displays: For quick testing without physical hardware, you can create virtual displays on an emulator or device:adb shell wm display create 1280x720 320dpi virtual_display_nameThis command creates a new virtual display that you can then target for content zones.
• Monitor CarService Logs: The logs from CarService (adb logcat -s CarService) will provide valuable insights into how content zones are being processed and if activities are being launched correctly within them.

Considerations for Passenger Entertainment & Driver Info

• Safety and Regulatory Compliance: Content in driver-facing zones must adhere to strict safety guidelines, often prohibiting video playback or complex interactive content while the vehicle is in motion. Passenger-facing zones have more flexibility.
• Resource Management: Running multiple displays and content zones concurrently can be resource-intensive. Optimize your applications for performance and memory usage to ensure a smooth user experience across all screens.
• Input Handling: Carefully design how input (touch, physical buttons, voice) is routed to the correct zone or display to avoid confusion and ensure safety.
• Contextual Awareness: Leverage vehicle data (speed, gear, occupant detection) to dynamically adjust zone behavior, content, or visibility.

Conclusion

Implementing custom content zones in AAOS is a powerful way to enhance the multi-display automotive experience. By carefully defining zones, integrating with CarDisplayRegionManager, and developing zone-aware applications, developers can create sophisticated, safe, and engaging infotainment systems. This approach allows for a tailored user experience, delivering the right information to the right occupant on the right display at the right time, paving the way for the next generation of in-car digital environments.