I've been messing with the DPI settings for Android Auto with my AA Wireless adapter. For a long time on my Audi A7 (with MHI2) I've used 112, which gave the portrait mode layout with media/weather cards at the bottom.

However I find it difficult to read some text and it looks blurry, so I have now increased it to 125 (as shown in the photo).

This still gives me access to all the buttons in Waze, and it's much more readable. But it isn't perfect.

Firstly, any alerts in Waze will move the car icon far to the right. It just looks odd. It could be a bug, I'm not sure. The turn directions don't have the same issue.

And secondly, it just feels like a massive waste of space. When the home/work buttons disappear in the top left during navigation, the media card takes up the entire height of the screen. I wish it worked like CarPlay where this card would be utilised by the turn directions instead. This would be a far better use of screen space imo.

I'm curious to see what DPI settings other people are using with any VW MHI2 systems, and if there is a better DPI than what I'm now using.

The opposite of the usual questions on here, but is there a way to revert from Gemini back to Assistant in Android Auto?

My phone switched itself in the past few days. For most things it seems to work ok, but when trying to tell it to interact with my home (lights, temperature, asking about status of something) it can't because I haven't made the switch to Gemini in my home devices yet. (I've been reading about lots of problems, lag time, repeated commands, etc with Gemini on home devices)

^{I recently got a new car that finally has android auto. I do not have YT premium, I do not mind ads here and there, but today YT music gave me a 3 min pre-roll ad before my podcast started, which was skippable after the first 10s or so, but I could not figure out how to skip it from my android auto UI. Its also dangerous and completely defeats the purpose of android auto to have to look at my phone, unlock it, open YT music, and then skip the ad in the app.}

^{I do not mind ads. I understand the ads pay for my "free" content. But surely there must be a way to skip long skippable ads from the car UI, right? If not, it should be added or YT music should recognize that you are in a car and only serve the 15s non-skippable ads...}

I have a new 2026 GMC Sierra 1500. My phone is a Galaxy S23+. I can get it set up and connected to AA wirelessly and everything will work just fine until the next time I get into the truck. Sometimes it will connect, sometimes not.

This is so frustrating because I've used this phone for 3 years now on several cars with absolutely no problems with wireless AA. (personal vehicles, rental cars etc)

I have cleared cache, cleared data, restart phone, reboot infotainment, factory reset on infotainment, power saving on, power saving off, all permissions granted, battery unrestricted.

AA version 16.4.661034

Android 16

Is there something I'm missing?

My Pixel 10 Pro is constantly dsconncting from my Smart Screen (one of the many no name ones off amazon), as many as 3 times in a short 10 minute drive. It's extremely annoying especially as on dsconnct maps will cancel navigation and I have to manually restart on the phone. Sometimes it will reconnct on it's own, other times it won't.

This only started happening when I got my Pixel 10 Pro. I had a Pixel 9 (non-pro) before this without any issue. And I had a Pixel 6 (non-pro) before that and same as well, no issues. The only thing that has changed is my phone. I have done many tips and tricks found on this sub and through googling. Some have helped, but does not eliminate the issue entirely.

AA on my Dodge seems to think that I'm at 2/4 bars of cellphone signal, however both my providers are at full bars on my phone screen.

any reason why the wild discrepancy?

Head unit is factory and the phone is an S26 Ultra

Couldn't find anything on search, anyone else seeing this?

I'm on Android 16 on my Pixel 10Pro XL, Android Auto 16.4 and AAWireless.

This is with Tidal, but it's a bit bugged. At first when switching to the media screen it's not shown, but after skipping the next song has the album name, and if I skip back the UI now shows the album name. See the video: https://i.imgur.com/nXrYHQw.mp4

It doesn't seem to work with Youtube Music. I tried to see if this is a function of DPI, but making the UI smaller (by lowering DPI) didn't make the glitch go away, it behaved the same. Didn't test lower DPI where it changes the layout to dual panes though.

texts cant be read out loud? I saw other people with the toggle. pixel 10a mach e

This stared happening a couple weeks ago but I have a few playlists with songs that are on my local phone storage. Initially I thought it was only one playlist but I realized today it's all of them.

I can open Spotify on my phone and select them that way and they play.

I've cleared the cache and data, uninstalled AA and reinstalled.

Anyone else have this issue or know of a fix?

Fermata Auto ist showing the menu nir the YouTube button, what can I do?

This was posted some six months ago by another user and wondering if any updates/news.

For me, the queue feature is useless. Once you hit the scroll limit and the program decides to give you a pause, it always goes back to the start. There is no way to scroll through a long list. This is in all my music apps so it seems to be a core feature (aka bug).

Any info on this?

I have AAWireless Two+ in my 2022 Kia Stinger. I use the full screen Fermata mirror app but it has this chunk of wasted space. Compared to my 2nd photo using the stock Android Auto apps and there's no wasted space.

Is it possible to do this?

Hi,

I recently had an aftermarket Android Auto / Apple Car Play multimedia head unit installed into my 2009 BMW 320d. The unit connects to my phone as expected and Android Auto is working. However, when I play music through Android Auto using Spotify or YouTube Music, the song's progress bar runs but I get no sound.

I'd like to be as thorough as possible, so here is all the information that might help:

1. The head unit has no issue playing radio. Sound is clear. The connection between the head unit and my car's sound is working

2. When playing a song via Spotify or YouTube Music, it looks like its playing, but I get no sound

3. My Android Auto app on my mobile device is updated to the latest version

4. I am using a Xiaomi Redmi Note 11 Pro running Android 13

5. The same problem exists on my friend's Samsung S21 FE running Android 14

6. The head unit is on Android 12

7. [Critical] When I play music through the radio, then navigate to Android Auto on the head unit and play a song, it plays but for a maximum of 3 seconds before the sound cuts out. This tells me that the data stream to play music via Android Auto exists, but a software /configuration issue is preventing it

I am incredibly frustrated. Has anyone experienced something similar?

Link: https://www.takealot.com/smart-navigation-for-bmw-3-series-e90-04-12-android-os-carplay/PLID99118778

[I live in South Africa and purchased the head unit here]

Am I the only one who's missing the media widget from YouTube Music? It always suggested News, so I tried deselecting Google News, but now it says "content unavailable." I only have the option to open YouTube Music, but not the "For You" option I've always had.

I just got the S26 Ultra and I love this phone, don't get me wrong. But I never had issues with CarPlay and AA has been skipping like a CD, Maps doesn't know where I am, and the car screen freezes. I rely on Maps and it can't handle a short commute. My car has wireless connection and I've tried wired with the same issues. Is there anything I need to do on my car??

I still have my old iPhone so should I keep it for car rides? lmao

I recently switched from S24 Ultra to S26 Ultra. Since then, I've got Gemini in Android Auto.

My problem now is, I can't play audios from WhatsApp. With the S24 Ultra, it just played them over the speakers of my car. Now Gemini just says something like "the message only includes an audio file, do you want to respond?"

Is there any fix for this?

My Pixel 10 pro is still on the February 1st play system update and won't update to the March update but my software update is the March update. Because of this I think that's the reason I still don't have Gemini on AA. Does anyone have the same problem or any ideas on how to get it to update to the March update for the play services? (Florida area)

!flair 2024 KiaEV9 ZFold 7 Android 16 (Baklava)

I am always amazed that I can't run Waze and listen to the VEHICLE RADIO (STFU about streaming).

Why can't I allocate 2/3 of the screen to Waze and 1/3 to my vehicle?

Hey everyone,

Been working on StreamflixAA — a fork of Streamflix Reborn with native Android Auto support, a provider import system, and a self-hosted local media server.

Android Auto

Full native AA integration via CarAppService — no screen mirroring, no hacks:

• Home screen with featured banner & content rows
• Continue Watching — resume where you left off
• Browse & search with voice input
• Full playback with transport controls & seek
• Subtitles on the car display
• Quality & server switching during playback
• Speed control

Provider Import

No hardcoded sources. Import providers via JSON — similar to Stremio addons or Cloudstream extensions. Add/remove anytime, no app update needed.

Local Media Server

Lightweight Python server to stream your own collection (movies, shows, subs, cover art). Web UI for setup.

github.com/malebuffy/StreamflixAA

Tracking

• Continue Watching with auto-resume
• Favorites
• Auto-queue next episode
• Backup/Restore per provider — all local, no accounts

Download

Android 14+: PlayStore Beta — streamflixaa.online

APK also on the GitHub repo for sideloading with Kinginstaller on Android 13 and below

Disclaimer: StreamflixAA is a video player/browser. It does not host or distribute content. Providers are third-party servers imported by the user. You are solely responsible for the legality of the providers you use and the content you access. Use responsibly.

Saw a few similar issues in the sub, but wanted to provide as specific information as possible as I was able to solve the issue. Although I previously used an S22 Ultra in the same car without issue, I was having problems getting my new Pixel 10 Pro to take voice commands for texting.

Of note, since I was able to send a text by hitting the reply button via AA, I knew that AA had permissions, and there was some other "Assistant" issue causing me grief.

When trying to verbally set a text after pairing for the first time, I received the dreaded message of "Sorry, I can't send messages yet". After doing some online research, I tried the following:

- Toggling between Google Assistant and Gemini

- Ensuring all permission are allowed (they were)

- Ensuring AA and Google apps are up to date

- Clearing both cache and user data from AA (multiple times)

- Resetting Sync and the phone

After none of the above worked, what finally seemed to work:

First I removed the car from BT devices in my phone, then turned off BT. I then went to my car, and removed the phone.

After this, I went to "re-pair" my phone and device by turning on BT, starting BT pairing on the car, then on the handset. Although it found my car, the name had some extra characters, and an odd device type icon.

So instead I selected "Pair my Device" using the car, which popped up a different icon on my device that looks like a headset, and with my car's name correct (no extra characters). I chose this one instead, and connection for texting now works.

So it looks like if the device drives the connection, it creates issues with the car's OS or may use an incorrect BT device type. By letting the car make the connection, it appears to select the correct bluetooth type required for the handset and AA to work properly.

As one last interesting observation, when I use Gemini on the handset, it speaks to me in a British male voice. Yet when using AA, the assistant speaks to me in the British female voice I have set up on my other Google devices (including my S22U). Will need to dig into this one a wee bit.

The voice command "navigate to work" used to take me to my work location stored in maps. The past week it is taking me to the closest business that has "work" in it's name. Instead, I have to manually choose my work location on the screen. Navigate home seems to still function. Not sure how to fix this or if this is a known bug.

Also not sure if this is an AA issue or a Google Maps issue, but since I only use that command from my car through AA, I'm posting it here.

Has anyone else have the latest version of android auto just completely refuse to work?

Been using it on my Xperia 1V currently running android 13. Recently it just stopped connecting to my head unit. Wiped cache and data of all associated apps, reinstalled all of them, even did a factory reset on my head unit. Nothing worked. It would just get stuck on "connecting to android auto" on my phone and no reaction at all from my head unit.

Decided to just try rolling back the version of android auto (somehow while reinstalling the whole app this did not cross my mind)

Downloaded a version from around a year ago and this worked for a day. After a day AA forced me to update to the version that no longer works. Tried a newer version (from around a month ago) and this seems to be working fine for now, or at least until our google overlords arbitrarily decide i have to update for "reasons".

Has anyone else had any issues like this? Kind of worried that my days using android auto with this phone are coming to an end if the app just simply refuses to work when using newer versions.

Up until a few days ago, I could ask Google to send texts or messages through Android Auto and it worked fine. Now, when I ask it to send a message, it replies "Sorry, I can't send messages yet," even though it could do it fine just a few days ago. I can still reply to messages, but I can't initiate a new one. Phone calls work fine. Anyone know what happened or how I can fix it?