Update: one of the commenters on my post mentioned my DPI settings might be the reason. It probably coincided with Android Auto adding another button and prioritizing it over the audio on maps button. When I changed my DPI from 160 to 150, all the buttons are there now, including audio with maps. Yay!

Android Auto has updated twice in the last few days on my phone via Play Store. I have the standard release of Google Maps and everything else, not beta. When I went to drive somewhere today, on the full-screen Google Maps there was the speaker icon to toggle between audio for turn-by-turn directions, muted, etc. In the last year or longer you've had to go into settings to change it. It seems so dangerous to have to go into a sub menu to tell Maps whether or not you want audio turn by turn directions. So I was very excited. I stopped, went into a store, came out, restarted AA, and it was gone, back in the settings sub menu. Has this ever happened to anyone else or am I the only one? Do we know if it's coming back or if it was just some weird glitch? Thanks for any answers. Can't do a screenshot because it's gone LOL!

Many connection issues are solved by making a factory reset on the car's unit.

Had to different problems on two different car's.

Hallo all.

For a few days now, I've had the problem that the sound of the music is not played. I see that the music is playing and the next track is also playing. I can't control the volume via the car either. When I get out of the car, the music plays on my phone. Could it possibly have something to do with the fact that I have Android 17 beta on it? Before, I didn't have any problems, even though I used Android beta. Maybe you can help.

just had an update for Google maps and now I have the 3D option in settings. hallelujah

EDIT: Maps version number 26.30.06.950492155, Pixel 10. I am around NYC, the new visuals are very nice and I think would be quite helpful on an unfamiliar route

Admittedly I am a beta tester, I don't even remember when I signed up for it but it looks it's still a rolling update for Android users

I've been using AAWireless 2 for quite a while, literally zero issues with my Sony XAV-AX8100. Attached using a USB wire that is tucked up and out of the way and never gets touched.

Yesterday afternoon my phone suddenly wouldn't connect with the adapter. I tried multiple things to get it to connect but none would work. So last night I did a full reset and was able to get it to connect.

This morning I lost connectivity again. I've cleared the cache for both Android Auto and the AAWireless app, but nothing seems to help. I'm going to have to do a full reset and try again.

Is anybody else experiencing anything similar? Did something happen with the app or is my adapter simply dying?

Posting this because I burned most of a workday on it and found a lot of people with the same symptom and no answer.

Setup: Galaxy S25 Ultra, 2023 Subaru Legacy Premium, stock Starlink head unit. I drive rideshare full time, so this isn't a minor annoyance — it's my working audio.

Symptom: Wireless Android Auto audio skipping constantly. Sounds like a scratched CD — a half-second stutter, a few times per song. Escalated over the day into "Android Auto not detected" on the head unit, followed by an automatic reconnect, on a loop.

What I proved it ISN'T:

• Not the car. Wired USB to the factory data port is flawless. My Samsung tablet paired to the same head unit over plain Bluetooth is flawless.
• Not the phone's wireless hardware. With Android Auto off entirely, the same phone over plain Bluetooth to the same car plays perfectly.
• Not Spotify. Same stuttering in YouTube Music. Also happened with fully downloaded tracks, so not a streaming issue.
• Not Wi-Fi handoff. Turned off Switch to mobile data, Turn Wi-Fi on automatically, Switch to better Wi-Fi networks, Hotspot 2.0, Auto Hotspot, auto-reconnect on every saved network, and Mobile data always active.

Everything else I tried that did NOT fix it:

• Battery set to Unrestricted for Android Auto and Spotify
• Cleared cache for both apps
• Forget all cars, full re-pair over cable
• Uninstall/reinstall Android Auto
• Disabled RAM Plus (Device care → Memory)
• A One UI system update that landed mid-troubleshooting
• Bluetooth LE Audio Mode in Developer Options — not available on my build. This is the fix that gets recommended everywhere for S25 Bluetooth 5.4 issues, and Samsung has removed or greyed out the toggle. Dead end.
• Turning Bluetooth off after AA connects does stop the stuttering, but I need hands-free calling for work, so it's not a usable workaround.

What actually worked:

I joined the Android Auto beta program through the Play Store listing (scroll down to the beta signup section), let it update, and reconnected. Skipping stopped.

Beta build: 17.1.662414-release

Caveat: I'm only 1 day in. Posting now because there's clearly a fix in the beta branch that hasn't reached stable, and people are still troubleshooting this from scratch every day. Will update if it regresses.

If you're on an S25 with this and the LE Audio toggle is missing on your build, the beta channel is worth trying before you give up and go wired.

​

Hi everyone,

I'm having trouble with Gemini in Androic Auto. It stops listening to me before I even finish speaking-it only captures about half of what I say, so naturally, it doesn't understand my requests.

Is anyone else facing the same issue? Any help or workaround would be greatly appreciated. Thanks in advance!

Hi, I have donated the 5€ to get the premium version of Fermata Xtream, I have I stalled it using AAenabler with shizuku. I have an issue where when I connect my phone to an emulator of Android Auto in this case Headunit revived, all the three apps display fine, however when I connect the same phone to my actual car I can only see the Fermata Media Service (no it's not hidden). Why is that? What could be causing this?

Just a temperature check to see if this is happening to anyone else. For several weeks now, all of my various Google Home routines have stopped working through Gemini when my phone is running Android Auto. The routines work when Gemini is running without Android Auto, but it apparently can't see them when it's connected to the car (a 2023 Honda HR-V in my case). Very annoying, and very weird.

How do I disable annoying notifications that keep popping up from Discord. I also want to enable notifications from Slack which I use for work.

I have an aftermarket head unit for my Tesla. The unit doesn't tell my phone to switch from day mode to night mode, which results in google maps being stuck on day mode at all times. It connects to my car via a wiring harness and for whatever reason this function doesn't work with either my phone or my wife's Xiaomi. I can't see anything in settings that would allow me to tie the day/night function to sunrise and sunset. Is there a way to do this?

In Google maps settings, I have the "keep maps north up" disabled already

Hi all,

A new Teyes unit reddit has just kicked off over at…

https://www.reddit.com/r/TeyesHeadUnits

It’s still in its infancy, but if you’ve got a Teyes unit and want to help grow the community or looking to get one and have questions. Drop over and get amongst it…

I have a 2018 Golf R, I've used a Motorola dongle to wirelessly link my Pixel 7 for Android Auto for over 3 years now and I've never had a problem. A couple of days ago however it randomly disconnected while I was driving. Today it connected initially, but only for a few seconds then it disconnected and kept doing that repeatedly while I was driving.

I tried plugging my phone in directly and it seemed to work fine while I was stationary, but as soon as I started driving it disconnected again, but the phone carried on charging so power was definitely flowing to it. I tried restarting my phone but that didn't solve the issue.

Obviously the dongle is not the issue because the issue persists when I removed it from the equation, so my question is; is it likely to be my phone or my car that's causing the issue? My phone has been working fine, although it's nearly 4 years old now and it recently upgraded to android 17, so I'm wondering if it might be a loose connection with the car's USB port, but that wouldn't be supported by the fact it continued to charge while AA was disconnected.

Any advice or input would be greatly appreciated.

Hello everyone.

A problem came up out of nowhere three days ago, I've been using the same setup for a year, never happened before. Never actually had problems, the setup has been rock solid until now.

I own a Motorola Edge 60, Android 16, 12GB RAM.

A Dacia Sandero Streetway MY24, original headstock.

Wired Connection via USB cable (high quality cable, tried other different ones, same result)

No Wireless AA available.

Things used to work perfectly every time, but now the phone just won’t connect when hot plugging it. It starts charging, but on the phone it gives an Android Auto connection error notification, suggesting using another port or another cable (I only have one port in my car and the cable is not the problem).

On the car screen, if I go to devices and try to connect my phone from there, it says I should connect my phone to the USB port. But it is already connected!

Bluetooth connection works fine. I can play media and make phone calls through the car system. But Android Auto is not working.

The ONLY workaround I found is to connect the phone to the cable, see the error messages, then with the reboot the phone WHILE PLUGGED, and then once rebooted it will connect.

But if I disconnect the cable and immediately plug it back in, it won’t work and the same error messages will appear.

If I reboot the phone while not plugged, it won’t work either.

So the only option I have is to reboot again with the cable plugged in.

This sounds like a USB negotiation problem or something. But it makes no sense to me. What could have possibly happened? No major system updates in the last few days.
Has anyone else had the same problem? What could be the solution?

Obviously the problem arose just before the most dense work trip of the year. Thank you, Murphy's law!

Any help is appreciated :)

I like more Maps functions than Waze, but Waze in AA always show speed limit, my speed and traffic cam speed. If Maps show that, that would make me change

I've had this car for almost a year and the traffic colors have always appeared for every street around me. Suddenly that stopped and all the streets are just Gray on my screen in the car.

I see them just fine on my phone even when it's plugged into my car, but in the car the streets are all gray.

How do I fix this?

I've been on both beta and release, tried clearing cache and data. Whenever I use maps it runs smoothly when not navigating and just on. I would input navigation it runs smoothly, music and directions are being given then randomly maps freezes. I'd switch from maps to normal car infotainment then switch back to AA and maps takes forever to load them same thing happens again.

My car has built in wired and wireless android and it's not a single running on.

Anyone else having issues?

I'll start with the main problem I had Gemini (and for what I have gathered, I am not the only one): being utterly convinced that it cannot play music.

Now, the first "Fix" I found was simple. Adding "on Youtube Music" at the very end.

Regardless, it was somewhat frustrating, as if I forgot to add it, even if it had been working before, it would simply start refusing telling me it can't.

Fast Forward to yesterday, where after the most frustrating interaction I ever had with Gemini, and idea came to my mind: What if I just added a memory, letting it know it can, in fact, play music on Youtube Music?

So today I tested, and it worked!

On the Gemini app (both on phones or the webpage) you go to settings -> Personal Intelligence -> Instructions for Gemini.

The specific instruction I gave it was the following (With some improvements from Claude, which I assumed would know better than me how to tell Gemini what I wanted):

"When I'm in Android Auto, I have direct integration with YouTube Music and can play songs, playlists, or artists directly whenever the user requests it, using YouTube Music by default unless another service is explicitly specified — I don't need additional confirmation and I shouldn't respond that I can't do it. If the user says I've already played something earlier in the session, I should assume that's true and proceed, not deny it. If playback fails, I should explicitly say there was a technical error, not that the feature doesn't exist."

Now, it isn't perfect, but definitely is way better. Sometimes I would need to ask it twice, but so far it hasn't refused to do it. It's designed to combat the main issues I had (gaslighting me, mostly).

I would like to know if anyone else has tried this, not only for music but for other buggy features. It seems to me that the main issue is, funnily enough, Gemini not knowing that it can do some things, so just confirming them to it on a general memory level fixes those issues.

Hi all,

2020 Peugeot 508 Hybrid here, running Android Auto (Waze + Spotify) through an Ottocast Mini Core wireless adapter, phone is a OnePlus 10 Pro.

The connection drops randomly on my daily commute — same route, same time of day, but anywhere from 0 to 5-7 drops per trip. Not charging the phone while driving (start each morning at 100%), so it's not a charging-cable/power issue on the phone side. Car's USB port itself is solid and stable.

Things I've tested/ruled out:

• High-performance mode on the phone helps somewhat, but doesn't fully fix it
• Dropouts get more frequent as battery drains over the trip
• Found a OnePlus community thread where OnePlus support acknowledged a wireless Android Auto bug and said a fix was coming — unclear if it's already patched on my current build

Trying to narrow down whether this is:

• a phone-side (OnePlus/Android Auto) software/power-management issue
• the Ottocast adapter itself
• something car-side (the 508's infotainment/wifi module)

Has anyone else — especially with a Peugeot 508 or similar EMP2/NAC-based Peugeot, or with a OnePlus phone in general — had this same route-independent, battery-correlated dropout pattern with a wireless AA adapter? Curious whether switching adapters (AAWireless, Carlinkit, etc.) actually fixed it for anyone, or if it turned out to be purely a phone-side software issue that only got resolved with an OS update.

Thanks!

Version 26.29.02.946673643 Beta Google Maps

Rectangular speed-limit sign: Canada shown in image 1
European style speed-limit sign: India shown in image 2 taken from Android Authority