Installation guide — Android SDK for Renault Group AAOS 15

Prerequisite: read the Overview for scope and guiding principles.

Outcome: at the end of this guide, Android Studio launches, the Android Automotive OS 15 platform (API 35) is installed, and the Android platform-tools (adb) are on your PATH.

This guide is intentionally thin. Google already documents the standard install flow very well; wherever that is the case, we link out. Only Renault Group–specific choices are spelled out.

1. Overview

You will:

  1. install Android Studio,
  2. install the Android SDK components required for AAOS 15 (Android Automotive OS 15 platform, matching build-tools, platform-tools),
  3. accept the SDK licenses,
  4. verify the install.

Steps 1–3 are done through the Android Studio SDK Manager UI on all three host OSes. Step 4 is done from a terminal.

Recommended Android Studio version. Android Studio and the Android Gradle plugin (AGP) evolve together. The AGP version your project uses imposes both a minimum Android Studio version and a minimum JDK version. The authoritative compatibility matrix is published by Google:

For AAOS 15 development:

  • Minimum: Android Studio Koala Feature Drop | 2024.2.1 with AGP 8.6.0 — the first combination that targets API 35.
  • Recommended: Android Studio Panda 4 or newer with the latest AGP, for the widest range of API 35 features.

Older Android Studio releases do not target API 35 and are therefore not supported for AAOS 15 development.

Download page: https://developer.android.com/studio ↗.

2. Install Android Studio

Follow Google’s official installer instructions for your host OS:

Verify — Android Studio launches, the Welcome to Android Studio window is displayed, and Help → About shows a version at or above the minimum listed in section 1 (Koala Feature Drop | 2024.2.1, Panda 4 or newer recommended).

3. Install the AAOS 15 SDK components

Open Android Studio and go to Settings/Preferences → Languages & Frameworks → Android SDK. If you prefer the command line, see Google’s sdkmanager reference ↗ after you have installed the cmdline-tools package.

Install the following packages (all available from the default Google channel — no Renault-specific repository is required).

3.1 SDK Platforms tab

3.2 SDK Tools tab

Enable Show Package Details (bottom-right) to pick exact revisions.

  • Android SDK Build-Tools 35.x.x — matching API 35.
  • Android SDK Platform-Tools — latest revision (provides adb, fastboot).
  • Android SDK Command-line Tools (latest) — provides sdkmanager, avdmanager.

Reference: Android SDK tools ↗.

Click Apply to trigger the download and install.

4. Accept the SDK licenses

Android Studio prompts for license acceptance during the install in step 3. If you skipped it or need to accept licenses again later, use:

Terminal window
# On any host OS, from the cmdline-tools install directory
sdkmanager --licenses

Press y at each prompt.

Reference: Command-line tools — sdkmanager ↗.

5. Put platform-tools on your PATH

The Android SDK is installed under a location that depends on your OS. The Android Studio SDK Manager pane displays it as Android SDK Location; call it $ANDROID_HOME from here on. Typical defaults:

Host OSDefault $ANDROID_HOME
Windows%LOCALAPPDATA%\Android\Sdk
Linux~/Android/Sdk
macOS~/Library/Android/sdk

Add $ANDROID_HOME/platform-tools to your PATH so adb is available from any terminal.

“Windows (PowerShell, current user)”

Terminal window
[Environment]::SetEnvironmentVariable(
"Path",
"$env:Path;$env:LOCALAPPDATA\Android\Sdk\platform-tools",
"User"
)

Open a new terminal for the change to take effect.

“Linux (bash)”

Terminal window
echo 'export PATH="$HOME/Android/Sdk/platform-tools:$PATH"' >> ~/.bashrc
source ~/.bashrc

“macOS (zsh)”

Terminal window
echo 'export PATH="$HOME/Library/Android/sdk/platform-tools:$PATH"' >> ~/.zshrc
source ~/.zshrc

Reference: Environment variables for Android tools ↗.

6. Verify the install

Open a fresh terminal (so it picks up the updated PATH) and run:

Terminal window
adb --version

Expected: a line starting with Android Debug Bridge version ….

Terminal window
sdkmanager --list_installed

Expected: the output contains lines that match at least:

  • platforms;android-35
  • build-tools;35.x.x
  • platform-tools
  • cmdline-tools;latest

If any of the four is missing, go back to section 3 and install it.

7. You are done

Your workstation is now provisioned for AAOS 15 development.

Next step: follow the Getting-started guide to create and build the default Google Automotive application.

Appendix — Troubleshooting

  • Android Studio cannot download SDK components — check that https://dl.google.com ↗ is reachable from your workstation. This guide assumes an unrestricted Internet connection; corporate proxy configuration on the reader’s side is out of scope of this documentation.
  • sdkmanager: command not found — you skipped installing Android SDK Command-line Tools (latest) in section 3.2, or you have not added $ANDROID_HOME/cmdline-tools/latest/bin to your PATH. Reference: Command-line tools install ↗.
  • License acceptance loop — re-run sdkmanager --licenses and answer y to every prompt. If the prompts keep re-appearing, check that your workstation clock is correct and that no HTTPS-inspecting proxy sits between the SDK Manager and https://dl.google.com ↗.