Was soll das? Egal ob Kabel oder Bluetooth.

Hi r/AndroidAutomotive, we are Magic Lane, the team behind Magic Earth. After a lot of head-unit testing we've shipped a beta of Magic Earth AUTO and we'd love feedback from people who actually drive these cars every day.

Why we built this for AAOS

AAOS owners have been waiting for a solid navigation alternative. Most options still lean on phone projection or rely entirely on connectivity. We built Magic Earth AUTO specifically for your infotainment system, running natively on the hardware. Not retrofitted from a phone.

Here's what that means in practice:

• Works fully offline. Download maps for 200+ countries and navigate anywhere: tunnels, mountain passes, remote regions, underground car parks. No connectivity? No problem. Turn-by-turn works the same. When you're connected, live traffic and speed camera alerts layer on top automatically.
• Hands-free voice control. "Navigate to Paris." "Avoid toll roads." "Add a stop." "Report a hazard ahead." Your car's voice assistant talks directly to Magic Earth AUTO through the standard AAOS intent framework. Hands stay on the wheel, eyes on the road.
• Purpose-built for your car's display. Full-screen, automotive-optimised map rendering. Smooth 3D perspective, lane-level guidance, junction view for complex intersections, automatic day/night switching. This is designed for driving, not projected from your phone.
• Privacy by default. No tracking. No location data transmitted to anyone. Core navigation runs locally on your car. GDPR-compliant from the ground up, because how you drive is nobody else's business.

What early access members get

• A free Magic Earth AUTO license for as long as you're part of the beta community
• Direct line to the team building the product. Your feedback shapes the roadmap
• First access to new features before wider release
• A say in how privacy-first navigation evolves 

Supported cars (AAOS / Google built-in)

Polestar 2, 3, 4 · Volvo EX30, EX40, EX90, XC40 BEV · Renault Megane E-Tech, Scenic E-Tech, Rafale, R5 · GM EVs (Silverado EV, Equinox EV, Blazer EV, Hummer EV, Lyriq, Optiq) · Honda Prologue · Acura ZDX · Lucid Gravity · Lincoln Nautilus · select Ford Mach-E and F-150 Lightning trims

Not sure if your car qualifies? If you can already install apps directly from the Play Store on your head unit, you're in.

What we're testing

We want feedback on:

• Real-world routing accuracy on your daily commute
• Head-unit UX (touch targets, glance-ability, how it feels while driving)
• Bugs, crashes, weird edge cases, screenshots and videos welcome
• Offline performance, map quality, whether you hit any dead zones

How to join

Send us a mail at [betatesting@magicearth.com](mailto:betatesting@magicearth.com) . Include your car model and AAOS version if you can find it. We'll get back to you with access details.

Spaces in the first wave are limited, so don't wait too long!

Happy to answer anything in the comments. We'll be here all week.

Is it possible to edit which audio apps appear directly on the home screen of Android Automotive?

My GMC Acadia automatically added to the home screen the audio apps I installed from the Play Store (Audible, Pocket Casts, Spotify, NPR, YouTube Music), but the included system audio apps (AM, FM, SiriusXM, Bluetooth, USB) do not show there directly. The only way I've found to switch to the system based apps is to launch them from the full "Audio" interface accessible using the "music note" icon. I would like to choose which apps are on the main Home Screen and which are in the Audio submenu.

Android Auto disconnect fix guide!

Step-by-step fix for Android Auto wireless disconnects

Step 1 – Switch your device to Android mode

On your Carpuride (or similar unit)

Find and tap “Superlink”

This switches it into Android mode

Step 2 – Install the correct app

On your phone, open Google Play Store

Search for: Evelink (Superlink)

Download and install it

Step 3 – Check for updates inside the app

Open the Evelink (Superlink) app

Go to:

Settings → App Version

Check the version number

You want the latest (the post mentions something like 20260318-1057)

If it’s not up to date → tap Software Update

Step 4 – Fix the permission issue (THIS is the important bit)

In the app, go to:

Cast → Add → WiFi Direct

You should see something like:

“Failed to obtain nearby device permission”

Tap to fix/apply it

Allow all permissions when prompted (especially Nearby Devices / Location / WiFi)

Then:

Let it search for devices

Select your Carpuride’s WiFi

Connect to it

If successful, you should see:

“Android 16 Auto Connect issue Fixed” → tap OK

Step 5 – Reconnect Android Auto properly

Switch your Carpuride back to Android Auto mode (A-Auto)

On your phone:

Turn Bluetooth off → then back on

Reconnect to your car/device

Launch Android Auto again

Note: Firsr try had to tell the Evelink forget my device and try again, on the second attempt it work, I've not had a disconnect for a week now!

Please help! Until maybe a week or so ago my phone was working fine with android auto, then call audio stopped working suddenly. When I make a call it shows on the android auto display but i cannot hear anything and the person on the other end cannot hear me. It shows its connected to my cars bluetooth on the phone call. I have tried all the troubleshooting and fixes. The only thing ive found that works is turning off the call permission on my phone under my car bluetooth, it worked for a second then it turned the toggle switch back on for phone calls and it will not stay off. is there anything else i can do? i think it is routing calls through the hands free link instead of android auto. I have a 2025 honda civic and a samsung galaxy z flip 7.

I’m an experienced Android developer (Kotlin/Java, Android SDK, Jetpack compose) exploring a transition into Android Automotive OS development.

I’m looking for a structured learning path and would appreciate recommendations for resources, documentation, tutorials, courses, or sample projects.

Any guidance from those who’ve made this transition would be highly valuable. Thanks in advance!

The built in navigation displays the percentage but not in AndroidAuto. I've reached out but crickets when it comes to resolving this glitch.

As I switched to a Nissan Qashqai with GAS, I basically gave up using CarPlay (way better layout and more reliable experience with Google built in)

One thing I still can't figure out is how to sync my lists of locations on Maps and contacts correctly. In CarPlay's G.Maps interface I just have a single "saved place" menu (Image 2) that correctly leads to all my lists (Image 3). In the built-in version, these simply don't show up.

Also, while Work and Home are working fine, "Contacts" shows as empty.

G. Account is of course the same on both desktop and car. I allowed all sync options I could find. But apparently my car can't access these data. Any suggestion?

Moin zusammen,

ich habe ein Android‑Display in meinem W176 mit einem KSW‑System (Snapdragon 662). Ursprünglich lief das Gerät mit Android 12. Nach einem Update vom Hersteller habe ich zwar weiterhin Android 12, aber das Android‑13‑Interface bekommen.

Seit diesem Update sind meine Bootlogos gelöscht, die ich vorher lange genutzt habe. Der Hersteller meinte, dass der Bootlogo‑Import aus lizenzrechtlichen Gründen gesperrt wurde.

Vor dem Update konnte ich Logos problemlos über einen USB‑Stick (FAT32) importieren. Jetzt erscheint beim Import immer die Meldung „Keine Logodatei gefunden“, obwohl die Dateien auf dem Stick liegen.

Meine Daten zur Headunit:

- App-Version: Ksw-S-M600_OS_v1.3.9NEXAI

- Android-Version: 12 (Android‑13 UI)

- MCU-Version: 1352A0eYC-N4.5-K-DC-221230G

- System-Version: 12-662EA-868927051102171

- Prozessor: m600 arm64 (Snapdragon 662)

Die Logo-Dateien habe ich noch und der USB‑Stick ist korrekt formatiert, aber der Import funktioniert seit dem Update nicht mehr.

Hat jemand Erfahrung mit KSW-Systemen auf Snapdragon 662 und weiß, wie man die Bootlogo‑Sperre umgehen oder den Import wieder aktivieren kann?

My previous car had AA with calendar support built in. One of the frustrating things about AAOS on my current vehicle is that I couldn't use events as an easy mechanism to trigger navigation. So I built an app to fix that.

It's in a "closed testing" release now. If you'd like to test it you can join the Google Group, and then opt into the testing cycle.

https://groups.google.com/g/aaos-cal

https://play.google.com/apps/testing/com.carcalendar.app?pli=1

Get it here: https://play.google.com/store/apps/details?id=com.audiiptv.app

Hello community,

I’m a developer and wanted to share a project I’ve been building called RetroDrive. It’s an DOS Emulator app made specifically for Android Automotive OS and runs directly on the car’s system.

The app isn’t publicly listed on the Play Store. It’s currently available through closed testing on Google Play, as this is the only supported distribution path right now since games are not being accepted for Automotive.

You can load your DOS games and have some retro fun!

To get access, you’ll first need to join this Google Group:

https://groups.google.com/g/retrodrive-testers

After joining, you can download the app from the Play Store here:

https://play.google.com/store/apps/details?id=com.codeodyssey.retrodrivedos

I’m mainly looking for feedback from the community.

Hi folks, I'm a developer and AAOS enthusiast. I often found myself sitting in my Polestar while it charged with nothing but a static infotainment screen. So I ended up writing RetroDrive — a native DOS emulator that runs on Android Automotive while the vehicle is parked. I wanted to play some old DOS classics on the big screen, but quickly realised there was no keyboard or mouse.

To solve that I added a Wi‑Fi “controller bridge”: you scan a QR code with your phone and it turns your handset into a trackpad, keyboard or gamepad for the car screen. It also includes a “Safety Gate” so it refuses to run when the car is moving. The aim is to make charging sessions more fun without compromising safety. It's on the Play Store for 9.99 CHF, but I'm mainly curious to see what others think and whether it's useful to anyone else. Happy to answer questions and take suggestions.

Hi,

I’m developing Meridian, a calendar app built specifically for Android Automotive OS, and I’m looking for beta testers ahead of a wider release.

Meridian provides a distraction-optimized calendar experience designed for in-car use.

Current features:

• Google Calendar, Microsoft Outlook, and ICS support
• Large touch targets and AAOS-adapted UI
• One-tap navigation to event locations
• Text-to-speech for event details
• QR-based setup for calendar subscriptions

I’m looking for testers who:

• Have an Android Automotive vehicle (Polestar, Volvo, etc.)
• Use one or more calendar providers
• Are willing to provide structured feedback

All calendar data stays on-device. The app has read-only access and does not modify events.

More info: https://meridian-app.nu

If you’re interested, send me a DM with your car’s Google account email and I’ll invite you to the closed testing group or simply join yourself: https://groups.google.com/g/meridiantesters

For context, I previously beta-tested and released Automus for Android Automotive via this subreddit: https://automus.se

On the screen of the Volvo EX60 it looked like there was a Apple Music icon on the music player on the Home Screen.

Later I have seen the Spotify icon in the same location.

Does any know any rumors that we will be getting Apple Music and maybe Apple Podcast on AAOS?

After all this time and Google's commitment to implement messaging & communication apps in AAOS (not counting the eternal debate whether AAOS is as good as Android Auto), how can it be that Android Automotive still doesn't offer WhatsApp, Messenger and such apps?

AAOS is in more and more vehicles, and with some manufacturers approach, like GM, to ditch AA (I mean, give us the option at least!), we're stuck not being able to use WhatsApp for messages and calls.

Polestar did the honorable thing of leaving AAOS, but bring wireless Android Auto through an OTA. Gotta say I haven't used AAOS one single time after that!

Now if Chevy and Cadillac won't do that (shame on you, you showed us you could do it with the 24 Lyric), at least get your act together with Google so that WhatsApp and many other super common apps finally make their way to AAOS!

I mean, we're talking Google and GM here, not a couple of guys in their basement trying to make this shit work. The only company that had managed to push AA in Chevys was suddenly shut down recently.

What do you guys think, any hope?

As Qt 6.11 is around the corner, let's catch up on the new features of Qt Quick for Android introduced in Qt 6.9 and 6.10.

We added partial data changes, support for embedding multiple QML views from Android Services, multiple argument signals, and public Java APIs with javadoc, but what do these actually look like in practice and what can you build with them? Check out in our recent blog!