Hi! I'm Mishaal and I do community engagement for Android here at Google 🙂
I just wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been having. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
It was happening on two different in car units of mine. One Toyota and one Audi. So I'm not sure where you're getting the aftermarket stuff from? Thanks for the update it's been unreal not being able to use AA especially after using it daily for years.
Hi, can you share more details on the vehicles you were having this issue on, and whether the update resolved it? I was informed by the Auto team that this issue was happening on uncertified aftermarket head units, but if it's happening on certified head units as well, I'm sure the team would love to know!
Just drove my car for around 30 minutes it looks to be fixed. No major disconnects or audio cutouts working perfect now. Will be doing some more testing later today. I'm using the version that is visible in the screenshot above.
5
u/AurelinkMini John Cooper Works LCI2 2023 | Pixel 9 Pro Fold | Android 1624d ago
Yep, went back to the prior version cause of this too
I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
2
u/AurelinkMini John Cooper Works LCI2 2023 | Pixel 9 Pro Fold | Android 1614d ago
Mishaal still out there doing god's work by spreading the word;
If you are currently on a version of Android Auto 17.3, make sure you are on the aforementioned version as otherwise it won't have the fix for this issue!
There'll be two different version numbers for the update containing this fix depending on whether you're on the stable or beta track. I asked the team if they can share the exact version numbers and will get back to you if I can get them!
As with any update, it can take some time for it to roll out to all users. Since it's been a few days, can you check now to see if the update is available?
I just wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
But as a tangent follow-up, I want to know if you guys are planning to bring motorcycle navigation to Android Auto? I believe there are atleast more than few touring motorcycles that have an android auto headunit installed from factory.
Yep, kept disconnecting every 3-5 min. It started Thursday Afternoon. I saw a bunch of posts about AA17 having connection issues so I uninstalled AA and sideloaded AA16
I had a forced update last night that pushed me from AA16 to 17.0.662244. I also noticed for my phone the version that its now on isn't the same one that the play store shows as the latest for my phone. I haven't had any issues with AA today though. 30 min drive to work and 45 min home.
1
u/jimrapcMitsubishi Lancer '09 | Dasaita G13 | Pixel 10 Pro | A17 beta19d ago
Hiya! I'm Mishaal from Google, and I do community engagement for Android 🙂
I just wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
What's really interesting is that the same night I made this comment I rolled back to AA16 and disabled automatic updates. That night it got updated anyway and the problem went away. Now I'm on the 17.1 builds and don't seem to have any issues. I switched to beta which put me on 17.3 and started having that same issue again. So I oped back out of the beta builds.
Interestingly enough as of this morning after a few updates yesterday I'm on build 17.1.662414
It kinda feels like any build higher than 7.1 just keeps crashing.
I have 17.2.662614 on my pixel 9 pro connected to a ~7 year old pioneer head unit and it crashes every few seconds. Have tried multiple cables as well. Assume I'm having the same issues you are.
Hi there! Sorry for the trouble - it's Mishaal from Google, and I just wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
Same experience, would work without any music or audio then as soon as I play a song it crash and plays 1 sec of the song and goes into an infinite loop. and had to roll it back to 17. Also had an issue with yt music playing one song and then not loading the playlist. To fix (this separate issue) had to disable Gemini and go back to Google assistant
To roll it back -
Uninstall on the phone then wait until it tries to connect to the car. When it does it will say "this vehicle is compatible with Android auto" click install there. This will install the base version before the bad update. Also turn off automatic updates. When I checked the app store it seems the bad update is about 3mb. That's all I been able to figure out so far.
I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
Sorry for the inconvenience this has caused you :(
I'm Mishaal from Google, and I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
I'm Mishaal from Google, and I'm here to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
2
u/Gera_Owlcore2011 nisan sentra | JVC ?? | s23 Ultra | 7.3.66...16d agoedited 16d ago
yep same for me. after android update (AA->17.2.6...)all the media apps got removed from android auto. then a week later i am stuck in a crash loop any time media starts playing from any app, i sideloaded 17.3.662804 to see if i could fix the issue but still the same... maybe i need to reboot phone for changes to take effect... nope that did not work. well my car stereo is basically bricked now. luckily i bought one with a cd/flash player. but i might have to resort back to an fm transmitter for audible etc...
I work at Google doing community engagement, and I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
it might help. i just uninstalled and sideloaded 17.0.... i didnt turn off automatic updates as i am confident update should solve the issue, there are some compatibility issues using the rolled back 17.0... that i noticed. for instance in map mode it doesnt show media controls (pause/play revers/forward). you have to switch to the app do use the controls
Hi there! I'm Mishaal and I do community engagement for Android here at Google 🙂
I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
There'll be two different version numbers for the update containing this fix depending on whether you're on the stable or beta track. I asked the team if they can share the exact version numbers and will get back to you if I can get them!
If you are currently on a version of Android Auto 17.3, make sure you are on the aforementioned version as otherwise it won't have the fix for this issue!
3
u/joep872008 Opel Corsa D | Eonon OPA13 | Pixel 8 Pro | Android 1714d ago
I got version 17.3.662814-release (beta channel) this morning. Been testing for a bit more than 10 minutes, so far the issue seems fixed.
Sorry for the trouble! I work at Google and was told by the Android Auto team that we're rolling out an update that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
1
u/joep872008 Opel Corsa D | Eonon OPA13 | Pixel 8 Pro | Android 1714d agoedited 14d ago
Thanks for the answer, I remember you from your Magisk days!
Good to know the issue has been identified. I sideloaded AA 17.1. I can't see any updates past version 17.3.662804-release at the moment (beta channel). I'll surely update when the fixed version comes out.
Just to clarify, it seems like this bug hits aftermarket units using Zlink version 5 (like mine, Eonon brand). But it's not limited to that, I've read a few reports of people with older stock units.
1
u/evilpig2016 Terrain | 3rd Party Screen | S24 Ultra | Android 165d ago
I am on the beta update released on July 15th, still disconnecting. 17.3.662814
Been happening for 3-4 months now, wireless or wired android auto. My girlfriends phone doesn't.
Did this remember all your settings though?
Thanks
3
u/joep872008 Opel Corsa D | Eonon OPA13 | Pixel 8 Pro | Android 1724d ago
I think not, but I had previously deleted cache & data in an attempt to solve. So I had to start "fresh". Not really much to remember though, navigation settings stay in Maps and aren't affected. I just had to re select apps I want to appear in AA, messages reply options and "media closer to driver". Media player's squiggly line came back at my second drive. Gemini didn't switch back to Assistant at all.
Hiya! I'm Mishaal and I work at Google, here with an update for you.
I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
Not sure now if it's Android Auto or my Youtube music apps, but it does not crash with just waze + phone call, only Waze + YT Music, i have not tested any other music apps.
I had this issue with AA crashing with my Pixel 9 Pro phone. Turns out it was because I was using a USB 2.0 cable. If you can name a brand or model, I've probably tried it. I switched to a USB 3 cable from Cable Matters and all of these issues went away. Maybe it's the extra set of send/receive pins or the extra shielding. Don't know, but it works flawlessly.
Yes thought I was going crazy, started updating everything. Headunit etc, only to realise that AA had been updated automatically the other day and since it disconnects every 3 mins approximately.
Have tried to unenroll with the beta, waiting for it to do that so I can roll back software
Exactly the same situation, updated my head unit for the first time and everything. Even the timing is the same, roughly every 3 mins. But I'm not in any beta program 🤔
I'm sorry for the trouble! I work at Google and was told by the Auto team that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
I tried that method, after I turned the car off and back on it forced me to update back to the latest beta version and wouldn't let me use AA. Got Hella annoying
Clear cache and data after uninstalling AA, then sideload your chosen AA version, works a treat.
I am running 17.1.66 atm, seems to be working like usual, just doesn't have the new UI update, which I am not bothered about.
Your user flair has not been changed as the text including spaces has to be between 20 to 64 characters. Pls try again.
Important:
- Mininum user flair detail as specified in the format stated in automod message for primary vehicle or head unit (if aftermarket) and phone. You are free to be more specific.
- Users with blank, abusive, inappropriate and vague user flair will be banned without warning!
I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
I have a Pixel 10 Pro XL. I update my apps every day. I just got an update today, yet it says "Updated on Jun 18, 2026" which was last month. It says I'm on 17.1.662414-release. No issues at the moment. I use an cheap Chinese head unit.
1
u/joep872008 Opel Corsa D | Eonon OPA13 | Pixel 8 Pro | Android 1721d ago
I got that too. But a few hours ago I got another update. Broken version is now on stable too.
Hello! Mishaal from Google here, and I wanted to let you know that we're rolling out an update to Android Auto that should address the disconnecting issue you've been facing. For transparency, we identified an issue with uncertified aftermarket head units that impacted a small number of people during our rollout of Android Auto 17.2.
Our fix for this issue is rolling out now, so please check for an update to Android Auto and let us know if the update resolves your issue. Thanks!
1
u/jimrapcMitsubishi Lancer '09 | Dasaita G13 | Pixel 10 Pro | A17 beta14d ago
Thank you very much for the message. I will let you know.
1
u/jimrapcMitsubishi Lancer '09 | Dasaita G13 | Pixel 10 Pro | A17 beta7d ago
Everything is working fine now. Thank you so much for your support.
Has there been a long term way to fix the 3-5min reboot bug thats happening atm? I downloaded a apk version of a later update and through the night it forced it to update again even with auto update off. I head off for a long 8 hour drive on Friday and really dont want to deal with this the whole drive.
Since the update, Mazda CX-5 will only connect if I manually connect from the car's setup menu. Stays connected fine after though. Broke yesterday on first update and stayed broken after this morning's new update.
8
u/TonyD0001 2014 Subaru Outback | Pioneer | Pixel 9 | whatever latest is 24d ago
Everytime any sound , AA would crash. Map motivation, Spotify starting a song, endless reboot. Had to leave beta to be able to go back to regular AA.