AARE is an open-source Android app that reimplements Android Auto’s phone-side projection, drawing its own interface on a compatible car display. It doesn’t require Google Play Services, but it can’t host Google Maps’ or Waze’s private in-car interfaces. AARE’s project documentation also sets out feature-specific Android requirements and vehicle-compatibility reports.
Before relying on AARE on the road, try it with the phone and car you plan to use.
What AARE does in the car
Android Auto projection sends a phone’s car-compatible apps to a vehicle’s head unit, the screen and system built into the car. AARE reimplements the phone side of that connection using the Android Auto projection protocol, or AAP. It’s a separate app with its own car interface, not Android Auto itself.
AARE lists navigation apps built for AndroidX Car App Library, including CoMaps, Organic Maps and OsmAnd. It also supports media apps that use Media3 or MediaBrowserService. Messaging works through notifications: messages can be read aloud and marked as read, while replies are available when parked.
Navigation, apps and screen mirroring
AARE can’t display Google Maps’ or Waze’s private Android Auto interface. If either app is navigating on the phone, though, AARE can show directions, distance and arrival information from its notifications. Spoken prompts can go to the car over the phone’s Bluetooth connection.
| Capability | AARE | Android Auto |
| Google Maps and Waze on the car display | Can’t host their private car interfaces; phone notifications can provide turn, distance and arrival details | Their own car interfaces are available |
For apps without a supported car interface, AARE offers phone-screen mirroring. It requires screen-capture permission and accessibility access to relay touch input, and the phone must stay unlocked. Mirroring pauses while driving, except when a navigation app is in front and guiding.
The AARE phone app groups its connection preview, setup checklist and settings for apps, messages, voice assistance, the car screen and audio.
Android requirements depend on the feature
AARE lists Android 8 as its baseline. Some connection and audio options require newer versions:
| Feature | Minimum Android version | Condition |
| AARE baseline | Android 8 | The project lists Android 8 or newer as the general requirement. |
| Screen-capture car audio | Android 10 | Android 8 and 9 have more limited audio-routing options; privileged installation or the car’s Bluetooth audio are alternatives. |
| WPA3-only car Wi-Fi | Android 10 | Required when the car’s Wi-Fi uses WPA3 only. |
| Shizuku car audio | Android 12 | Required for this audio-routing method. |
The project also lists system audio routing, which requires root access or privileged installation. The right audio setup therefore depends on the Android version and the method you want to use.
Why compatibility varies by car
AARE’s project-maintained compatibility list includes different outcomes for specific phone and head-unit combinations. It records user-reported operation in a 2022 Hyundai Kona Electric after a touch fix and Android Auto key extraction. A 2024 Toyota RAV4 head unit rejected AARE’s self-signed certificate. In a 2025 Honda CR-V, USB did not make the car recognize the phone; wireless connected but produced a black screen.
These reports reflect particular configurations, not a standard test across vehicles. The project describes AARE as early software and advises trying it in your own car before relying on it while driving.
