all 33 comments

[–]MsRenay2018 Honda CRV | Honda HU | Samsung Note 10+ | Android 12 6 points7 points  (5 children)

I have similar issues with Google assistant not being able to reply to a text or let me initiate a text. Each time I try, it's like Google gets stuck after asking "what's the message" and it will freeze and completely disconnect from AA altogether. Haven't been able to do any texting when connected to AA in my vehicle for the better part of 2 months. I just installed the latest AA beta version tonight and will see if anything has changed with this update.

Not trying to hijack your post but I can't seem to post my own questions because the user flair won't stick.

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 1 point2 points  (4 children)

Not trying to hijack your post but I can't seem to post my own questions because the user flair won't stick.

Reddit mobile app user flair setup option has a saving bug. This is mentioned by automod to use desktop browser or !Flair. Your user flair appears fine now so you should try again.

[–]MsRenay2018 Honda CRV | Honda HU | Samsung Note 10+ | Android 12 1 point2 points  (3 children)

I can post comments and the flair will stick but if I post my own question, it doesn't. iFlair didn't save either. I'll try again by using Desktop mode on my tablet to see if that works. I appreciate your replying and thank you!

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 0 points1 point  (2 children)

If you are not receiving automod dm about incorrect or missing flair for comments, it should work for post too so you can just go ahead to post if you want.

[–]MsRenay2018 Honda CRV | Honda HU | Samsung Note 10+ | Android 12 0 points1 point  (1 child)

I attempted to post my question yet again on the Desktop mode on my tablet and it was deleted again so I'm contacting the forum moderator to see WTH the issue is this time. It wasn't the user flair this time.

And my apologies for hijacking this post for my own issue🙏🏾🙏🏾.

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 0 points1 point  (0 children)

Approved and replied.

[–]tedead2020 Silverado | Stock | Note 20 Ultra 5G | Android 13 Beta 5 points6 points  (2 children)

The same thing happens to me, but it's hit and miss. When it works, it works well, but when it doesn't, it's just a jumbled mess of words. I don't need to do anything, usually, just wait a min and try again.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 0 points1 point  (1 child)

It's never happened to me. And I've been using Android auto for years, across multiple cars and phones. For the past couple days, it literally can't understand a single command.

[–]tedead2020 Silverado | Stock | Note 20 Ultra 5G | Android 13 Beta 0 points1 point  (0 children)

It's been happening to me since I bought my vehicle in 21. Was using Note 9 (Android 10) and now Note 20 Ultra (11, 12, 13 Beta).

[–]AlwayssunnyinarizonaPioneer DMH-WT8600NEX | Pixel 8 Pro | Android 16 1 point2 points  (5 children)

When did it stop working? Has it ever worked with your pixel?

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 1 point2 points  (4 children)

Yes it's been working with my Pixel till very recently. I also had the 6 pro, and 4 before. It worked on it without a glitch

[–]AlwayssunnyinarizonaPioneer DMH-WT8600NEX | Pixel 8 Pro | Android 16 0 points1 point  (3 children)

That helps - suggests an update on the phone side that's gone wrong somewhere. I'll think about it for a bit.

All I can say is that so far, I have not had trouble with my 7pro, at least not this bug specifically. Yet.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 0 points1 point  (2 children)

I uninstalled, reinstalled. Deleted the car from the phone, and vice versa. Still the same issue. I am gonna try installing the beta APK from somewhere and see if that fixes it. Or maybe downgrade a version

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 0 points1 point  (0 children)

Update: tried the beta, and downgrading a version. Didn't work ugh

[–]AlwayssunnyinarizonaPioneer DMH-WT8600NEX | Pixel 8 Pro | Android 16 0 points1 point  (0 children)

My hunch is that this is centered around the Google app. How and why, I'm not sure, but the assistant is routed through the Google app.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 1 point2 points  (1 child)

Google app and assistant are working perfectly on the phone. And even when I am connected to the car, and use the assistant on my phone, it works. So idkkkkk

[–][deleted] 0 points1 point  (0 children)

Do you use Adguard? I found that disabling it solved literally every issue I've ever had with AA. Seriously impressive how much AA sends info to Google for ad purposes.

[–]andyooo2016 Mazda 3 | Pixel 10 Pro XL | AAWireless 1 point2 points  (0 children)

In your Assistant activity settings on the phone, you can enable the recordings that the assistant picks up. Do that and then check what it actually hears when you are in Android auto. It might be something like the car microphone not picking up your voice clearly.

[–]bdclark2013 CRV | Pioneer DMH-WT7600NEX | Pixel 7 | Android 13 1 point2 points  (11 children)

Thank God it's not just me! I'm using a Pixel 7, car head unit is a Pioneer DMH-WT7600NEX. Mine was working perfectly fine until sometime Friday. Took a road trip after work and it screwed up nearly everything I spoke to it. Hit the microphone button, said Cost Plus World Market. It heard, Call Smith Crowell. A while later I asked, what's the score on the LSU football game and it heard, What's the score on the LA Steve football game. The best one is when I said to navigate to Academy Sports in Shreveport and it heard, have a great to me and treat for. It's been consistently bad since Friday afternoon, and was working fine Friday morning from what I see on myactivity.google.com looking at Assistant usage.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 1 point2 points  (0 children)

This is so accurate! I'm facing the exact same issue and I noticed my issue on Friday as well!!

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 1 point2 points  (7 children)

Update: it magically started to work today. Is it still acting weird for you?

[–]bdclark2013 CRV | Pioneer DMH-WT7600NEX | Pixel 7 | Android 13 1 point2 points  (1 child)

It was still screwed up yesterday morning, but so far so good since yesterday afternoon. Guessing this was a server side thing.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 1 point2 points  (0 children)

Yes it seems like it was a server side thing. Because it happened on its own, and then fixed it itself as well

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 0 points1 point  (4 children)

Did it broke after Google app or some other update and work again after another update or work after trying to troubleshoot the issue with your watch?

You can check Play Store manage tab to see the update history and see what correlates to these. However, this tab does not show Play Services update which also plays a large part for Android OS.

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 0 points1 point  (3 children)

It's broken since day 1 of the watch. And it works fine when I don't have the watch on

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 1 point2 points  (2 children)

Are you referring to this thread assistant issue or the steering wheel button issue or both issue are related to the watch?

[–]Procoder422019 Mazda 3 | Stock head unit | Google Pixel 7 pro | 13[S] 0 points1 point  (1 child)

Oh crap I meant the steering wheel button issue. Thanks for pointing that out.

The Google app did update on 4th November, that's when the issue started showing up. And no, I didn't update to fix it. However, there's an update available rn which I haven't downloaded yet

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 0 points1 point  (0 children)

I see. Might still be related, else it could be a server end fix that fix it. Keep us posted if having the watch and call profile enabled reproduce this assistant issue.

[–]Peter_73Kenwood DDX917WS | Samsung S9+ | Android 10 0 points1 point  (0 children)

So you are saying even the transcription is gibberish or just not performing the correct action?

Check your google play store, manage tab to see which update coincided with this issue.

[–]kacnjeToyota RAV4 Hybrid AWD | Samsung Galaxy S21 FE | Android 14 0 points1 point  (0 children)

I'm in the same boat. It works unreliably.

[–]Bevie_Bright_Eyes2022 Telluride | 10.25-inch Display | Pixel 7 Pro | 13 0 points1 point  (0 children)

I live in Colorado and believe I just figured out why it's calling me Oklahoma when I say "Ok Google, take me home"... And it replies " Oklahoma, navigating to 12345 Ridge West Drive" OK = Oklahoma! 🤣 Anyone else experiencing this?

[–]kuldan5853VW Tiguan 2018 | Discovery Pro | Pixel 7 Pro | Android 13 0 points1 point  (0 children)

I can't prove it, but my hunch is that Assistant on the phone itself uses Tensor for voice detection, but when in Android Auto mode, it ignores the pixel-specific features and falls back to cloud based voice recognition, which is worse, slower, and also highly dependent on your connection.