Waze on Android Auto operated through a 2018 Audi S5's MMI
#1
Waze on Android Auto operated through a 2018 Audi S5's MMI
I have a 2018 Audi S5 Sportback and I have loaded Android auto onto the MMI; and Waze onto my Samsung S9+. Google Maps runs well through the MMI when my phone is connected via the USB; however Waze does not. When attempting to run Waze, I can advance all the way to the window which reads "Go" to my desired destination, but cannot engage the system past this point. On only one occasion so far, Waze seemed to automatically engage my desired destination from a drop down list of several destinations, but I could not replicate same. Any suggestions? Thank you.
#2
AudiWorld Member
Android Waze certainly has its share of bugs connected to this MMI. The highlighting of what button you are actually on is really poor (white vs off white???). The cursor ends up on the wrong end of some menus (it's on the last selection to start, so you have to rotate counter clockwise to get it to appear)). Etc. etc. etc. And using Google voice commands, the destination often does not get sent to Waze properly, just like you mention, where the address is listed, but you can't actually make it start the nav. I don't think there are any solutions other reporting it to Waze/Google.
Also, with the Samsungs, if you have battery saver on, the GPS location will not update at all in Waze if your phone screen is off. This is despite Google Maps working just fine. So how that app receives GPS info differs with how Waze does it. (At least the last time I checked several months ago).
Also, with the Samsungs, if you have battery saver on, the GPS location will not update at all in Waze if your phone screen is off. This is despite Google Maps working just fine. So how that app receives GPS info differs with how Waze does it. (At least the last time I checked several months ago).
#3
Android Waze certainly has its share of bugs connected to this MMI. The highlighting of what button you are actually on is really poor (white vs off white???). The cursor ends up on the wrong end of some menus (it's on the last selection to start, so you have to rotate counter clockwise to get it to appear)). Etc. etc. etc. And using Google voice commands, the destination often does not get sent to Waze properly, just like you mention, where the address is listed, but you can't actually make it start the nav. I don't think there are any solutions other reporting it to Waze/Google.
Also, with the Samsungs, if you have battery saver on, the GPS location will not update at all in Waze if your phone screen is off. This is despite Google Maps working just fine. So how that app receives GPS info differs with how Waze does it. (At least the last time I checked several months ago).
Also, with the Samsungs, if you have battery saver on, the GPS location will not update at all in Waze if your phone screen is off. This is despite Google Maps working just fine. So how that app receives GPS info differs with how Waze does it. (At least the last time I checked several months ago).
#4
AudiWorld Senior Member
All I can say are that these are all known issues .... the poor contrast and default position of the focus treatment is something you can get used to, although the usability is not great.
I use Waze for my commute to have it help evaluate which of several routes it thinks is fastest for me, and also to let me know of road conditions. Outside of that, Google Maps is far better for controller and touch-based Android Auto cars for finding and navigating to a new place.
I have to wonder whether the Waze iOS implementation for CarPlay will be better.
I use Waze for my commute to have it help evaluate which of several routes it thinks is fastest for me, and also to let me know of road conditions. Outside of that, Google Maps is far better for controller and touch-based Android Auto cars for finding and navigating to a new place.
I have to wonder whether the Waze iOS implementation for CarPlay will be better.
#5
I have a 2018 Audi S5 Sportback and I have loaded Android auto onto the MMI; and Waze onto my Samsung S9+. Google Maps runs well through the MMI when my phone is connected via the USB; however Waze does not. When attempting to run Waze, I can advance all the way to the window which reads "Go" to my desired destination, but cannot engage the system past this point. On only one occasion so far, Waze seemed to automatically engage my desired destination from a drop down list of several destinations, but I could not replicate same. Any suggestions? Thank you.
#6
AudiWorld Member
Weird...I don't really have any of these weird problems. When I send a voice nav to Google, it reports "sending to Waze" and then it loads into AA every time. I do have to rotate the selector around to select "go", but its always worked.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.
#7
AudiWorld Member
Only just recently, (cr)apple has allowed other apps to show up on carplay, but not sure when/if it'll actually roll out.
Trending Topics
#8
All I can say are that these are all known issues .... the poor contrast and default position of the focus treatment is something you can get used to, although the usability is not great.
I use Waze for my commute to have it help evaluate which of several routes it thinks is fastest for me, and also to let me know of road conditions. Outside of that, Google Maps is far better for controller and touch-based Android Auto cars for finding and navigating to a new place.
I have to wonder whether the Waze iOS implementation for CarPlay will be better.
I use Waze for my commute to have it help evaluate which of several routes it thinks is fastest for me, and also to let me know of road conditions. Outside of that, Google Maps is far better for controller and touch-based Android Auto cars for finding and navigating to a new place.
I have to wonder whether the Waze iOS implementation for CarPlay will be better.
#9
Weird...I don't really have any of these weird problems. When I send a voice nav to Google, it reports "sending to Waze" and then it loads into AA every time. I do have to rotate the selector around to select "go", but its always worked.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.
#10
AudiWorld Member
Weird...I don't really have any of these weird problems. When I send a voice nav to Google, it reports "sending to Waze" and then it loads into AA every time. I do have to rotate the selector around to select "go", but its always worked.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.
Using AA with Samsung Galaxy 8.
I would probably recommend an uninstall and reinstall of AA and Waze to see if that helps your inability to select "Go" and launch into navigation.