Introduction to Android Automotive OS and Custom UIs

Android Automotive OS (AAOS) is Google’s full-stack, open-source platform powering in-car infotainment systems. Unlike Android Auto, which is a projection solution, AAOS runs directly on the vehicle’s hardware, offering deep integration with car systems. This native integration enables manufacturers and developers to create highly customized user experiences, including bespoke controls for essential vehicle functions like Heating, Ventilation, and Air Conditioning (HVAC).

Developing a custom HVAC control UI on AAOS involves interacting with the vehicle’s hardware abstraction layer (HAL) through Android’s CarService. This guide provides a practical walkthrough, from understanding the underlying architecture to implementing a functional custom HVAC interface.

Understanding the AAOS Vehicle HAL and CarService

At the core of AAOS’s vehicle integration is the Vehicle Hardware Abstraction Layer (VHAL). The VHAL defines a standardized interface for accessing vehicle properties (sensors, actuators, vehicle-specific settings). CarService acts as an intermediary, providing Android applications with a high-level API to interact with the VHAL without needing to understand the low-level hardware specifics.

Key Components:

• VHAL (Vehicle HAL): A hardware abstraction layer that defines a standardized interface for vehicle properties. OEMs implement this to expose vehicle data and controls.
• CarService: A system service in AAOS that provides a high-level Java API for applications to interact with vehicle properties, including HVAC, through the VHAL.
• CarPropertyManager: An API within CarService used for reading and writing vehicle properties.
• CarHvacManager: A specialized manager within CarService that provides HVAC-specific functionalities, simplifying interaction with common climate control properties.

For HVAC, properties like fan speed, temperature setpoint, air distribution mode, and defrost status are exposed as standardized integer or float values through the VHAL and accessible via CarHvacManager.

Setting Up Your Development Environment

To develop for AAOS, you’ll primarily need the Android Studio IDE and an AAOS emulator or a physical development board. While a full AOSP build environment is necessary for deep system modifications, app-level development can begin with the SDK.

Steps for basic setup:

1. Install Android Studio: Ensure you have the latest stable version.
2. Install AAOS System Images: In Android Studio’s SDK Manager, navigate to ‘SDK Platforms’ and enable ‘Show Package Details’. Under Android 10 (Q) or higher, select an ‘Automotive Intel x86 Atom System Image’.
3. Create an AAOS Emulator: Go to ‘Tools’ > ‘AVD Manager’, click ‘Create Virtual Device’, select ‘Automotive’ category, choose a device definition (e.g., ‘Automotive (1024p landscape)’), and select your downloaded AAOS system image.

Accessing HVAC Properties via CarService

The primary entry point for HVAC control is the CarHvacManager, obtained from CarManager. You’ll need the android.car.permission.CAR_HVAC permission in your app’s AndroidManifest.xml.

<uses-permission android:name="android.car.permission.CAR_HVAC" />

Initializing CarService and CarHvacManager:

import android.car.Car;import android.car.CarNotConnectedException;import android.car.hardware.CarHvacManager;import android.content.ComponentName;import android.content.ServiceConnection;import android.os.IBinder;public class HvacControlActivity extends Activity {    private Car mCar;    private CarHvacManager mCarHvacManager;    private ServiceConnection mCarConnection = new ServiceConnection() {        @Override        public void onServiceConnected(ComponentName name, IBinder service) {            mCar = (Car) service;            try {                mCarHvacManager = (CarHvacManager) mCar.getCarManager(Car.HVAC_SERVICE);                // Now you can interact with mCarHvacManager            } catch (CarNotConnectedException e) {                Log.e(TAG, "Car not connected", e);            }        }        @Override        public void onServiceDisconnected(ComponentName name) {            mCarHvacManager = null;            mCar = null;        }    };    @Override    protected void onStart() {        super.onStart();        if (mCar == null || !mCar.isConnected()) {            mCar = Car.createCar(this, mCarConnection);            mCar.connect();        }    }    @Override    protected void onStop() {        if (mCar != null) {            mCar.disconnect();        }        super.onStop();    }    // ... rest of your activity ...}

Reading and Setting HVAC Properties:

Each HVAC property has a unique integer ID (e.g., CarHvacManager.CAR_HVAC_FAN_SPEED). You can read its current value and write new values.

// Read current fan speed (example for a single zone)try {    int fanSpeed = mCarHvacManager.getIntProperty(CarHvacManager.CAR_HVAC_FAN_SPEED, CarHvacManager.ZONE_GLOBAL);    Log.d(TAG, "Current fan speed: " + fanSpeed);} catch (CarNotConnectedException e) {    Log.e(TAG, "Car not connected", e);}// Set fan speed to 3try {    mCarHvacManager.setIntProperty(CarHvacManager.CAR_HVAC_FAN_SPEED, CarHvacManager.ZONE_GLOBAL, 3);} catch (CarNotConnectedException e) {    Log.e(TAG, "Car not connected", e);}// Read target temperature (example)try {    float targetTemp = mCarHvacManager.getFloatProperty(CarHvacManager.CAR_HVAC_TEMPERATURE_SETPOINT, CarHvacManager.ZONE_GLOBAL);    Log.d(TAG, "Target temperature: " + targetTemp);} catch (CarNotConnectedException e) {    Log.e(TAG, "Car not connected", e);}// Set target temperature to 22.5 Ctry {    mCarHvacManager.setFloatProperty(CarHvacManager.CAR_HVAC_TEMPERATURE_SETPOINT, CarHvacManager.ZONE_GLOBAL, 22.5f);} catch (CarNotConnectedException e) {    Log.e(TAG, "Car not connected", e);}

Note the use of ZONE_GLOBAL for properties that apply to the entire vehicle or when zone-specific control isn’t needed or available. For multi-zone systems, you would query available zones using CarHvacManager.getHvacFanSpeedZones() and use the appropriate zone ID.

Listening for Property Changes:

To keep your UI updated, you should register a listener for property changes.

private final CarHvacManager.CarHvacEventCallback mHvacCallback = new CarHvacManager.CarHvacEventCallback() {    @Override    public void onPropertyChange(CarHvacManager manager, int propertyId, int zone) {        switch (propertyId) {            case CarHvacManager.CAR_HVAC_FAN_SPEED:                try {                    int fanSpeed = manager.getIntProperty(propertyId, zone);                    // Update UI with new fan speed                } catch (CarNotConnectedException e) { /* handle error */ }                break;            case CarHvacManager.CAR_HVAC_TEMPERATURE_SETPOINT:                try {                    float temp = manager.getFloatProperty(propertyId, zone);                    // Update UI with new temperature                } catch (CarNotConnectedException e) { /* handle error */ }                break;            // Handle other HVAC properties            default:                break;        }    }    @Override    public void onError(CarHvacManager manager, int propertyId, int zone) {        Log.e(TAG, "Error on HVAC property: " + propertyId + " in zone: " + zone);    }};@Overrideprotected void onServiceConnected(ComponentName name, IBinder service) {    // ... existing connection logic ...    if (mCarHvacManager != null) {        mCarHvacManager.registerCallback(mHvacCallback);    }}@Overrideprotected void onServiceDisconnected(ComponentName name) {    if (mCarHvacManager != null) {        mCarHvacManager.unregisterCallback(mHvacCallback);    }    // ... existing disconnection logic ...}

Designing the Custom UI for Automotive

When designing an AAOS UI, consider the unique automotive context:

• Safety First: Minimize driver distraction. Use large touch targets, clear iconography, and simple layouts.
• Readability: High contrast, appropriate font sizes.
• Theming: Adhere to brand guidelines. AAOS allows extensive UI customization.
• Responsiveness: Ensure the UI responds quickly to user input.
• Accessibility: Support voice commands and other assistive technologies where appropriate.

Your layout will typically use standard Android UI components like SeekBar for fan speed, TextView for displaying values, ImageView for icons, and Button or ToggleButton for modes (e.g., AC on/off, defrost).

Integrating UI with CarService

Once you have your UI components, link them to the CarHvacManager:

1. Initialize UI Elements: In your Activity’s onCreate or onViewCreated (for fragments), find your views by ID.
2. Display Initial State: After CarHvacManager is initialized (in onServiceConnected), query the current state of all relevant HVAC properties and update your UI.
3. Handle User Input: Attach listeners (e.g., OnClickListener for buttons, OnSeekBarChangeListener for seek bars) to your UI elements. Inside these listeners, call the appropriate mCarHvacManager.setIntProperty() or setFloatProperty() methods to send commands to the vehicle.
4. Update UI on Property Changes: Ensure your mHvacCallback implementation correctly updates the UI elements whenever the vehicle’s HVAC state changes (e.g., if the passenger adjusts their temperature).

Deploying and Testing Your HVAC UI

Build your Android app as a standard APK. You can deploy it to your AAOS emulator or physical device using ADB (Android Debug Bridge).

./gradlew assembleDebugadb install path/to/your/app-debug.apkadb shell am start -n your.package.name/your.package.name.HvacControlActivity

Test thoroughly on the emulator first, then on physical hardware if available. Pay attention to how your UI responds to various HVAC settings, including edge cases like min/max values or unsupported modes (though CarService attempts to abstract this).

Advanced Considerations

• Permissions: Be mindful of all necessary Android permissions for accessing vehicle data.
• Multi-zone HVAC: Design your UI to elegantly handle multiple climate zones (driver, passenger, rear).
• Custom VHAL Properties: For highly bespoke vehicle features not covered by standard VHAL properties, OEMs might expose custom vendor properties. This requires deeper integration and knowledge of the specific vehicle’s VHAL implementation.
• Error Handling: Implement robust error handling for CarNotConnectedException and other potential issues when interacting with CarService.

Conclusion

Developing a custom HVAC control UI for Android Automotive OS offers a powerful way to create a unique and integrated in-car experience. By leveraging CarService and the CarHvacManager API, developers can access and control vehicle HVAC properties effectively. Understanding the AAOS architecture, adhering to automotive UI/UX principles, and meticulous testing are crucial for delivering a safe, intuitive, and high-performance climate control interface.