Introduction: Customizing Android Automotive OS (AAOS)

Android Automotive OS (AAOS) represents a significant evolution in in-vehicle infotainment, providing a full-stack open-source platform deeply integrated with the vehicle’s hardware. For automotive manufacturers and Tier 1 suppliers, customizing AAOS is crucial to differentiate their offerings and implement unique features. One common requirement is to integrate custom system applications directly into the AOSP build. This allows for tighter integration with vehicle services, privileged permissions, and ensures the application cannot be uninstalled by the end-user.

This expert-level guide will walk you through the process of creating a simple custom Android application and embedding it into an AAOS AOSP build. We’ll cover everything from application creation to build system integration and testing.

Why Add a Custom System Application?

• Privileged Access: System applications can be signed with platform keys, granting them access to system-level APIs and permissions (e.g., interacting with vehicle HALs).
• Deep Integration: Seamlessly integrate with the system UI, background services, and core system functionalities.
• Persistence: Installed as part of the system image, these apps cannot be uninstalled by standard users, ensuring critical functionalities remain available.
• OEM Branding: Essential for incorporating manufacturer-specific features and branding directly into the core OS experience.

Prerequisites

Before you begin, ensure you have the following:

• A working AOSP build environment set up for AAOS.
• The AAOS source code cloned and synchronized.
• Basic knowledge of Android application development.
• Familiarity with the AOSP build system (Makefiles or Android.bp).

Step 1: Create Your Custom Android Application

First, create a basic Android application. For this guide, we’ll make a simple app that displays