Install APK on Android Automotive OS (AAOS)
Android Automotive OS is the full embedded Android in your car's infotainment system — not phone mirroring, not Android Auto, but a complete OS with a Play Store. When an app isn't available in the automotive Play Store variant, AnExplorer's APK installer lets you sideload it directly.
Supported Vehicles
Any vehicle with Android Automotive OS and a Play Store is compatible. This includes:
- Polestar 2 / 3 / 4 / 5 — all AAOS variants
- Volvo — EX40, EX30, EX90, C40, XC40 (2023+ with Android built-in)
- Honda Prologue / Accord (2026+)
- GM / Chevrolet / Cadillac — Equinox EV, Blazer EV, LYRIQ, CELESTIQ
- Ford — Explorer, Expedition, Lincoln models
- BYD / Renault / Nissan — AAOS variants
- Volkswagen ID. series — ID.3, ID.4, ID.5, ID.7, ID.Buzz (MIB3)
Method 1 — USB Drive (Most Reliable)
No network required. Works on all AAOS vehicles with a USB-A or USB-C media port.
- On your PC, download the APK and copy it to a FAT32-formatted USB drive
- Plug the USB drive into the car's USB media port (not the charging-only port — check your manual)
- In the car, open AnExplorer → USB Storage
- Navigate to the APK file → tap it
- If prompted, enable Install Unknown Apps for AnExplorer in the car's Settings → Security
- Tap Install — the app appears in the car's launcher
Method 2 — WiFi Transfer from Phone
No USB drive needed. Requires both phone and car on the same WiFi network (car's built-in hotspot or home WiFi).
- On your phone, open AnExplorer → navigate to the APK → tap WiFi Share
- In the car's AnExplorer, open Network → WiFi Receive
- Connect and accept the transfer — APK arrives in car's internal storage
- Tap the received APK in AnExplorer to install
Method 3 — Remote Install via ADB from Phone
AnExplorer's Remote Install installs silently on the car without showing the Android confirmation dialog — ideal for deploying multiple apps or testing builds without touching the infotainment screen.
WiFi ADB (recommended — no cable):
- In the car's Settings → About → tap Build Number 7 times to enable Developer Options
- Settings → Developer Options → Wireless Debugging → ON
- Tap Pair device with pairing code — note the IP, port, and 6-digit code shown on screen
- On your phone, navigate to the APK in AnExplorer → tap Remote Install
- Enter the IP address and pairing code shown in the car
- Tap Pair, then Install — the app installs silently on the car's infotainment
USB ADB:
- In the car: Developer Options → USB Debugging → ON
- Connect the car's USB-C port to your phone
- Navigate to the APK in AnExplorer on your phone → tap Remote Install
- Accept the "Allow USB Debugging" prompt on the car screen
- Tap Install — done
ADB is the recommended method for fleet installations (e.g., ride-share vehicles or commercial fleets deploying the same APK on multiple AAOS units).
Enabling Unknown Sources in AAOS till Android 12
AAOS security settings are per-app (same as Android 8+):
- Settings → Apps → Special App Access → Install Unknown Apps
- Find AnExplorer in the list → toggle Allow from this source ON
This only needs to be done once. The setting persists across reboots.
OEM-Specific Notes
| Vehicle | Notes |
|---|---|
| Polestar Cars | Developer Mode available in car settings; USB-A media port on centre console |
| Volvo Cars | USB-A port near centre console; Play Store available via Google Account |
| GM / Chevrolet | USB-A in centre console tray; some variants restrict sideloading by policy |
| VW OS series | USB-C media port; Google Built-in required |
| Honda Cars | USB-A in console; standard AAOS security settings |
