Android Auto

[stani]

My findings on the Jazz 4G FL:

if there is no problem with the phone settings or cable for example, the USB connection works quite well. But only the connection, see below.
The Wi-Fi connection only worked me on one phone.

So connecting via USB cable is quite problem-free, you can browse the phone menu, play music, everything works until the navigation starts.
I've tried three different navigation systems and it's always the same: Android Auto crashes and stops working after about 5 to 20 minutes.

At first I thought it was the phone (I tried three different phones) or the cable, but it is most likely a problem in the Honda software.

I have a reasonable suspicion that the Honda system simply cannot handle the flow of so much data - not only Android Auto itself, but mainly processing data from the external navigation system and, with all that perhaps the FM radio turned on, and most importantly it also has to take care of the system itself in the car - which, of course, has priority.

Therefore, Android Auto is unusable for me in its current form on the Jazz. 

[Kremmen]

With my old Jazz I had Google Maps running, plus playing music through the car speakers from my phone via AIMP. Plus running Speedtrap Alert for speed cam warnings

I was connected via cable and had zero problems

Samsung S10 then a Samsung S23+

Wireless was hit and miss so I went into the behind the scenes menu and disabled both Android and Carplay wireless

[stani]

Kremmen: It's possible. But I'm writing about FL. It's quite possible that the HW remained the same, but the SW is more. I also tried the Samsung S10.

[Kremmen]

The only thing I will add is to make sure you use a good quality data cable as some USB cables are only designed for charging

The data cables are noticeably thicker

[stani]

Well, I'm not that silly to use only the charging cable (I would have to buy it extra). I've tried about 5 types of cables in total. And with the thick cable, it may not be true, as I wrote about it here, that one person bought an expensive thick cable, only to have to replace it with the weak original Samsung one.

[Steve_M]

What language is your phone in Czech? Change the phone language to English and try that.

You should have revived an Audio update via Over The Air, have you checked for updates to the Audio?

[NetworkMan]

AA is fine on my ~1 month old Jazz Advance with a Samsung S23.  As suggested try changing the phone (and the Honda, if possible) to English and restarting both.  Can you reset the car to factory defaults?  That might help.

I don't want to be anglo-centric but if you can get close to the UK setup it might just work, then you can start to back out the changes and find the culprit.

Personally I have never had a problem that can be pinned on a cable.

[stani]

It would be very sad if Android Auto only worked in English and maybe only set to UK.
Of course, I rebooted (repeatedly), I write about it here.

There are problems with AA in general, just type it into Google.
But I'm no beginner at this, the system in my Jazz simply doesn't handle external navigation via AA.

And in my case, we're not talking about whether AA works or not (yes, it does), but that external navigation via AA stops working - that's the problem.

[Bristol_Crosstar]

I have to say I think Android Auto isn't worth all the faff, it's temperamental at best. If I want to use satnav I use the one in the car and if I want to play audio from the phone I use the Bluetooth connection which works fine.

[stani]

I have to say I think Android Auto isn't worth all the faff, it's temperamental at best. If I want to use satnav I use the one in the car and if I want to play audio from the phone I use the Bluetooth connection which works fine.

Well, yes, but the navigation in Jazz isn't worth much, the graphics aren't great, the voice is as if "from a barrel", the maps aren't up to date...
All other navigation apps from Google Play are much better, such as HERE WeGo, Organic Maps, or the clear number one, Mapy.com.

[Steve_M]

The Android Auto navigation freezing when using a phone which is not set to English is an item that is fixed in the latest audio update.

Setting the phone language to English was a temporary fix as the issue relates to the phone language settings and how the information between the phone and the audio is treated.

[stani]

Ah, so that's news... I will try....
------------
Edit: Before I try it (probably tomorrow), I asked Copilot:

"According to user reports and Google's release notes, a bug with navigation freezing when using a phone language other than English was fixed in Android Auto version 11.2 (stable release), which began rolling out in early August 2024. The fix was part of a broader update to Android Auto's audio and voice subsystem."

But I have version 14.7 on my phone...

So I asked Copilot further and here is his answer:

"The fact that you have Android Auto 14.7 and your navigation is still freezing unfortunately makes sense — this version did bring some internal adjustments and preparation for a “clean mode” of the interface, but Google does not list any targeted fix for the navigation freezing bug in the changelog when using a non-English language.
In addition, new reported problems have appeared in 14.7, such as the so-called “Error 7”, which is related to communication between the phone and the car’s infotainment and can cause navigation to crash or freeze. This means that even if the original language bug was fixed earlier, other bugs with similar symptoms may appear in newer versions."

Well, I'm not too smart about it...

[stani]

So I just tried it out on a short 5km ride. And it seems to work.
Phone set as main language US English and use Mapy.com voice navigation in Czech.
The phone wasn't even on the dashboard because of the satellite signal, but in the compartment in front of the gear lever - I was quite surprised that it worked.
The fact that voice navigation worked in Czech is probably because Mapy.com has its own and does not use the Google TTS module.

I will then try, for example, HERE WeGo which uses Google TTS.
I will also try navigating in AA over a longer distance.

---------

Edit: so again, the remaining two were tested at a short distance: HERE WeGo and Organic Maps. Google TTS has no effect on freezing. I have Czech and English on my phone. 

Both have switched to automatic night mode - the phone is set to US English and it is night in the USA. While switching to day mode in Organic Maps is possible via the Jazz display, with HERE WeGo you have to go to the menu on your phone.

Organic Maps started automatically navigating in Czech, HERE WeGo only in English - I had to change it in the phone settings.
HERE WeGo has completely switched to the American system, I had to manually change it to metric on this navigation on my phone.

Ranking according to me.

Graphics, display:  1) Mapy.com (clear winner), 2) Organic Maps, 3) HERE WeGo

Voice navigation clarity and detail:  1) HERE WeGo (clear winner), 2)  Mapy.com, 3)  Organic Maps

Note: The built-in navigation in the Jazz is no match for any of these three.

When I get a chance, I'll try external navigation via AA for a longer route - see if it freezes.

[CB72]

AA wireless works for me using a Samsung A54, sometimes AA crashes, then I use the inbuilt navigation for a while and that seems to fix AA. Now and again wireless doesn't connect so I use a cable, just a basic Amazon cable, for one trip, that fixes AA wireless again.

[Hicardo]

I find AA works pretty well overall with my Samsung phone.  If there is a glitch, i find its usually to do with phone reception, not an issue with AA. We live in a sometimes dodgy reception area, exacerbated in certain weather conditions.   

The 2025 Jazz has a MUCH improved Sat Nav inbuilt, but its still not as good (imo) as Waze or Google Maps.  So i'm a confirmed AA user I'm afraid.