Getting started guide — Build your first Renault Group AAOS 15 app
Prerequisite: Installation guide completed — Android Studio launches, API 35 platform is installed,
adbis onPATH.Outcome: at the end of this guide you have an APK for the default Google Automotive application on disk, at
app/build/outputs/apk/debug/app-debug.apkinside your project.
This guide, like the installation guide, is intentionally thin. Google already documents standard Android Studio and Gradle behavior; we link out. Only the Renault Group / AAOS 15–specific choices are spelled out.
1. Overview
You will:
- create a new Android Automotive project from the Google project template shipped with Android Studio,
- adjust the module configuration for AAOS 15 (SDK levels, Automotive library, manifest features),
- build the APK with the Gradle wrapper,
- locate the APK on disk.
The whole procedure is identical on Windows, Linux, and macOS — Android Studio and the Gradle wrapper abstract away OS differences. The only per-OS variation is the shell used in §4 and §5 (PowerShell on Windows, POSIX shell on Linux and macOS).
Renault Group allows partner to leverage some priviledged vehicle properties or distraction-optimized UI for their apps. If your app need one of those both capatibility, please contact RG business.
2. Create the project
Follow Google’s official guide for creating an Android Automotive project: Build media apps for cars — create an app ↗. The same New Project → Automotive wizard applies to any Automotive app category (not just media).
In the Android Studio wizard:
- Templates category: Automotive.
- Template: No Activity (produces the minimum Google Automotive skeleton — enough to build an APK). If you want the media-app skeleton instead, pick Media service; it also builds an APK end to end.
- Language: Kotlin (recommended by Google for new Android projects) or Java. Both produce an APK. This guide’s build command is language-agnostic.
- Minimum SDK: API 29 (“Android 10”) or higher — see the Renault Group note below for the AAOS 15 rationale.
- Build configuration language: Kotlin DSL (recommended by Google) or Groovy. Snippets below are shown in both.
Reference: Create a project in Android Studio ↗.
3. Configure the module for AAOS
Open the app-module build.gradle.kts (or build.gradle for Groovy) and
verify / adjust the following sections.
3.1 SDK levels and package identifier
Set the following in the app-module build.gradle(.kts):
-
applicationId— the platform package name that identifies your app on the device.For standard partner applications, you may use your own package name.
If your application requires access to privileged vehicle properties, contact Renault Group Partner Support to obtain an approved applicationId of the form
com.ampere.car.[your-slug]and the required permissions. The applicationId must match the platform privileged-permission allow-list — request procedure in §3.4. -
namespace— the Kotlin/Java package used for generatedRandBuildConfigclasses. Keeping it identical toapplicationIdis the simplest choice. -
versionCode— the internal integer version used by the platform to decide upgrade eligibility. On the Renault Group emulator platforms,versionCodemust be>= 20to be accepted as an update to a pre-installed stub — lower values are rejected at install time. -
SDK levels for AAOS 15:
compileSdk = 35,targetSdk = 35,minSdk = 29or higher.
android { namespace = "com.ampere.car.[your-slug]" compileSdk = 35
defaultConfig { applicationId = "com.ampere.car.[your-slug]" minSdk = 29 targetSdk = 35 versionCode = 20 versionName = "0.1" } } android { namespace 'com.ampere.car.[your-slug]' compileSdk 35
defaultConfig { applicationId 'com.ampere.car.[your-slug]' minSdk 29 targetSdk 35 versionCode 20 versionName '0.1' } }Reference: Configure the app module ↗ and Set the application ID ↗.
3.2 Declare the Automotive library
The android.car library is provided by the Automotive platform. To
compile against it, add useLibrary("android.car") inside the
android { … } block.
android { // …existing config… useLibrary("android.car") } android { // …existing config… useLibrary 'android.car' }Reference: useLibrary declaration ↗
and the Car library overview ↗.
3.3 Manifest — declare Automotive requirements
Open app/src/main/AndroidManifest.xml and make sure the following two
entries exist inside the <manifest> root and the <application> block
respectively.
Inside <manifest>, above <application>:
<uses-feature android:name="android.hardware.type.automotive" android:required="true" />Inside <application>:
<meta-data android:name="com.android.automotive" android:resource="@xml/automotive_app_desc" />Then create app/src/main/res/xml/automotive_app_desc.xml:
<?xml version="1.0" encoding="utf-8"?><automotiveApp> <!-- Declare the app category. Adjust to your actual category: media | template | video | messaging | ime | notification --> <uses name="template" /></automotiveApp>References:
uses-featuremanifest element ↗.- Distribute Automotive apps ↗ —
explains the
<automotiveApp>metadata block and the supported<uses name="…"/>categories. - Build media apps for cars ↗ — full reference example for the media category.
3.4 Privileged-app configuration (allow-listed platform stub APKs)
If the targeted application requires usage of priviledged vehicle properties, the Renault Group emulator platforms delivered to partners ship with pre-installed codeless stub APKs. The app package name is registered in the platform privileged-permission allow-list. To exercise those privileged permissions from your own APK, you update the pre-installed APK with a build of your app that:
- uses the exact package name of the stub APK as its
applicationId(set in §3.1), - if the targeted application needs usage of priviledged vehicle properties,
Renault Group will provide you a development signing key required for
deployment on “the openR evo emulator for Partners” (also the key the stub APK
itself was signed with, so
adb install -raccepts the replacement), - declares each privileged permission with
<uses-permission>in its manifest.
Reference on the underlying AOSP mechanism: Privileged permission allowlisting ↗.
Both the allow-listed package name and the corresponding signing keystore are provided to you by your Renault Group business contact — you cannot self-provision them. If you miss those data, please contact the RG technical support.
Contact Renault Group partner support
If you want to request the following from Renault Group partner support, contact us
You will receive:
- your allow-listed package name (used as Gradle
applicationId), - the signing keystore file (JKS or PKCS12),
- the key alias and the store / key passwords,
- the list of privileged permissions allow-listed for your package.
Configure the signing config
Add the keystore file provided by Renault Group support as a Gradle
signingConfig and apply it to the build type you will install on the
emulator.
Reference: Sign your app — Gradle ↗ and Application signing schemes ↗.
Store your credentials outside the project, in ~/.gradle/gradle.properties
(create the file if it does not exist):
RENAULT_KEYSTORE_PATH=/absolute/path/to/renault-partner.jksRENAULT_KEYSTORE_PASSWORD=<store-password>RENAULT_KEY_ALIAS=<alias-provided-by-renault-support>RENAULT_KEY_PASSWORD=<key-password>Then declare the signing config in the module build script and apply it to your build types:
android { signingConfigs { create("renaultPartner") { storeFile = file(project.property("RENAULT_KEYSTORE_PATH") as String) storePassword = project.property("RENAULT_KEYSTORE_PASSWORD") as String keyAlias = project.property("RENAULT_KEY_ALIAS") as String keyPassword = project.property("RENAULT_KEY_PASSWORD") as String // AGP 8.6+ enables APK signing schemes v1, v2, and v3 by // default; v3 is required for API 35 privileged installs. } }
buildTypes { getByName("debug") { signingConfig = signingConfigs.getByName("renaultPartner") } getByName("release") { signingConfig = signingConfigs.getByName("renaultPartner") } } } android { signingConfigs { renaultPartner { storeFile file(project.property('RENAULT_KEYSTORE_PATH')) storePassword project.property('RENAULT_KEYSTORE_PASSWORD') keyAlias project.property('RENAULT_KEY_ALIAS') keyPassword project.property('RENAULT_KEY_PASSWORD') } }
buildTypes { debug { signingConfig signingConfigs.renaultPartner } release { signingConfig signingConfigs.renaultPartner } } }Declare the privileged permissions in the manifest
Every allow-listed privileged permission must be declared with a
<uses-permission> element in AndroidManifest.xml. Without the
declaration, the platform will not grant the permission at runtime, even
if the allow-list contains it for your package.
Reference: Declare app permissions ↗.
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<!-- Privileged permissions allow-listed for this package on the delivered Renault Group emulator platforms. Replace the list below with the one provided by Renault Group support. --> <uses-permission android:name="android.car.permission.CAR_ENERGY" /> <uses-permission android:name="android.car.permission.CAR_INFO" /> <!-- ... -->
<application> <!-- ... --> </application></manifest>Reference for the android.car permission catalogue:
android.car package summary ↗.
3.5 Enable driving-safe UI with distraction-optimized activities
Android Automotive OS blocks non-driving-safe activities while the
vehicle is in a restricted driving state and replaces them on screen
with a system “activity blocking” overlay. To let an activity of your
app stay usable during driving, mark it as distraction-optimized
(DO) in AndroidManifest.xml.
The declaration is a single <meta-data> entry — no platform image
rebuild, no allow-list update, and no touch of the /system/priv-app
partition is required. Car Service reads the metadata at install or
update time, including when the APK is pushed with adb install -r
over a pre-installed stub. Runtime check is performed by
CarPackageManager.isActivityDistractionOptimized(...) ↗.
Two scopes are supported.
Application-level — every activity in the app is DO:
<application> <meta-data android:name="distractionOptimized" android:value="true" /> <!-- ... --></application>Activity-level — only the tagged activities are DO:
<activity android:name=".MainActivity"> <meta-data android:name="distractionOptimized" android:value="true" /></activity>4. Build the APK
From the project root (where the gradlew / gradlew.bat wrapper lives),
run the assemble task for the debug build type.
“Windows (PowerShell)”
.\gradlew.bat assembleDebug“Linux / macOS”
./gradlew assembleDebugExpected — the last lines of Gradle output are:
BUILD SUCCESSFUL in <time><n> actionable tasks: <n> executedIf Gradle fails, see the Troubleshooting appendix at the bottom of this page.
Reference: Build your app from the command line ↗.
5. Locate the APK
The APK is written to:
app/build/outputs/apk/debug/app-debug.apkVerify from a terminal:
“Windows (PowerShell)”
Get-Item .\app\build\outputs\apk\debug\app-debug.apk“Linux / macOS”
ls -l app/build/outputs/apk/debug/app-debug.apkExpected — the file exists and its size is a few megabytes. If the file is missing, the Gradle build in section 4 did not succeed; re-check the output.
Reference: Android build outputs ↗.
6. You are done
You have built the default Google Automotive application against AAOS 15 and produced a debug APK locally.
What comes next is out of scope of this documentation set and will be published separately on the Renault Group Developer Portal Develop section:
- installing and booting the openR evo emulator on a Linux host,
- installing your APK on the partner-compatible emulator,
- running instrumented tests and vehicle-property test harness scenarios,
- Renault Group UX/UI constraints your app must respect for later certification.
Watch the Develop section of the developer portal for updates.
Appendix — Troubleshooting
Failed to find target with hash string 'android-35'— the Android 15 platform (API 35) is not installed. Return to the installation guide and install it.Package 'android.car' does not existat compile time — theuseLibrary("android.car")declaration from section 3.2 is missing or is outside theandroid { … }block.Manifest merger failed: uses-feature android.hardware.type.automotive— the<uses-feature>entry from section 3.3 is missing fromAndroidManifest.xml.- Gradle downloads hang or fail — the Gradle wrapper needs to reach https://services.gradle.org ↗. This documentation assumes an unrestricted Internet connection; corporate proxy configuration on the reader’s side is out of scope of this documentation.
- APK is not at the expected path — Android Studio’s Build → Locate Bundle/APK Analyzer menu displays the exact output location for your build variant. Reference: APK Analyzer ↗.

