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 |
Troubleshooting APK Installation on AAOS
"Install blocked" or "Unknown sources not allowed"
- Navigate to Settings → Apps → Special App Access → Install Unknown Apps
- Find AnExplorer (or Files) and toggle "Allow from this source" ON
- Some OEMs (notably GM) enforce a policy-level block — check for system updates that may unlock developer settings
APK installs but crashes immediately
- The APK may be built for a different CPU architecture (ARM vs x86). Most AAOS head units use ARM64, but some older models use x86.
- Check APK compatibility: download the correct variant (arm64-v8a) from the source
- The app may require Google Play Services features not available on automotive builds
"Parse error" when tapping APK
- Incomplete download — re-download the APK and verify file size matches the source
- APK requires a newer Android version than your car's AAOS. Check the app's minimum SDK version against your vehicle's Android version (Settings → About → Android version)
- Corrupted file on USB — try a different USB drive or re-format as FAT32
USB drive not detected
- Ensure the drive is FAT32 or exFAT formatted (NTFS is not universally supported on AAOS)
- Use the media USB port, not the charging-only port (check your vehicle manual for which is which)
- Try a smaller capacity drive (some head units have issues with 128 GB+ drives)
- Remove and reinsert — some vehicles require the car to be in Park to detect USB
WiFi transfer not connecting
- Both devices must be on the same network (use the car's built-in hotspot or your home WiFi)
- Disable VPN on either device if active
- Restart AnExplorer on both phone and car
Best Practices for AAOS Sideloading
- Keep APKs updated manually. Sideloaded apps don't auto-update via Play Store. Bookmark the APK source and check periodically for new versions.
- Test in Park. Always install and test apps while the vehicle is parked. Many AAOS vehicles disable certain interactions while driving.
- Use minimal permissions. When the sideloaded app requests permissions, grant only what's necessary. Automotive apps shouldn't need camera, contacts, or phone access unless they specifically serve those functions.
- Back up APKs. Keep a folder on your USB drive with known-good versions of sideloaded APKs. If an update breaks something, you can reinstall the previous version.
- Check app compatibility notes. Not all phone apps work well on automotive displays. Landscape-only or large-screen-friendly apps adapt best to car infotainment screens (typically 10-15 inches).
- Avoid system-level APKs. Don't sideload launchers, system UI modifications, or root tools. These can brick the infotainment system and may require a dealer visit to reset.
What Apps Work Well When Sideloaded on AAOS
| App category | Compatibility | Notes |
|---|---|---|
| Media players (VLC, MX Player) | ✅ Good | Landscape UI, large controls |
| Navigation (offline maps) | ✅ Good | Full-screen map works well on car displays |
| Music streaming (alternative clients) | ⚠️ Varies | Some require Play Store services |
| Productivity (file managers, note apps) | ✅ Good | Useful for commercial/fleet vehicles |
| Games | ❌ Poor | Touch-dependent UIs don't work with car controls |
| Social media | ⚠️ Varies | Portrait-only apps display poorly |
| Camera/photo apps | ❌ N/A | No camera hardware on most head units |
AAOS vs Android Auto — Understanding the Difference
| Aspect | Android Automotive OS (AAOS) | Android Auto |
|---|---|---|
| Runs on | Car's built-in hardware | Phone (mirrored to car screen) |
| APK installation | ✅ Yes — sideload supported | ❌ No — phone apps only |
| Play Store | ✅ Automotive variant | ❌ Uses phone's store |
| File management | ✅ Full (USB, network, cloud) | ❌ No file access |
| AnExplorer use | ✅ Install and run natively | ❌ Not supported |
| OTA updates | From car manufacturer | From phone OS updates |
AnExplorer's APK installer is specifically for AAOS vehicles — those with Android built into the car's hardware. It does not apply to Android Auto (phone mirroring).