• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Google Navigation doesn't say street names

M

Mister F

Newbie
I know this issue has been discussed before on the forums, but it's always been left unresolved or the solutions in the threads don't work for me. I have an HTC One S running Jelly Bean 4.1.1 with Maps 6.12.0. When I'm in navigation all I get is "in 200 metres turn right" or "in 500 metres take the ramp". Never any street or highway names.

I also have a Nexus 7 tablet (JB 4.2.2, fully up to date Maps) and there's no issue on it at all - street names work perfectly. Could this be an issue with this version of Jelly Bean? A search comes up with suggestions like uninstalling Maps updates, clearing the cache, and clearing data on Maps and the Google TTS engine. I've done all that but the problem persists. I don't think it's device specific - a Galaxy S3 user running the same version of Android has the same problem - link

I've tried a few other apps but none of them are as good as Google Maps. Waze says street names but the audio quality is terrible. MapQuest does too but has no 3D mapping for some reason. Plus the navigation just isn't as good. What I really need is for Google Maps to work properly!
http://forums.hardwarezone.com.sg/a...ion-does-not-say-out-street-name-4019017.html
 
I've switched to Waze last month. I found that the audio is way better and louder on Waze than on Google Maps. I have difficulty hearing the audio on Google Maps. I play music over BT from my phone, so turning up the volume is not an option as it would make my music too loud. With Waze, the volume level is appropriate for the volume I set to listen to my music.

I find that in addition the audio volume, Waze has a lot of cool features not available on Google Maps. It also provides me with better traffic information and presents it better than Google Maps. Waze also selects better routes than Google Maps.
 
Mister F said:
I know this issue has been discussed before on the forums, but it's always been left unresolved or the solutions in the threads don't work for me. I have an HTC One S running Jelly Bean 4.1.1 with Maps 6.12.0. When I'm in navigation all I get is "in 200 metres turn right" or "in 500 metres take the ramp". Never any street or highway names.
Click to expand...

I had the same exact issue. It started after the OTA update for JB on the Droid Razr.

Solution: Uninstall Maps and then re-install.
 
Stuntman said:
I've switched to Waze last month. I found that the audio is way better and louder on Waze than on Google Maps. I have difficulty hearing the audio on Google Maps. I play music over BT from my phone, so turning up the volume is not an option as it would make my music too loud. With Waze, the volume level is appropriate for the volume I set to listen to my music.

I find that in addition the audio volume, Waze has a lot of cool features not available on Google Maps. It also provides me with better traffic information and presents it better than Google Maps. Waze also selects better routes than Google Maps.
Click to expand...
You really found that the audio was better? I found it to be terrible sound quality and half the street name is cut out - Woodbine becomes "bine". It also doesn't route the audio through the car's speakers through Bluetooth - not a big deal but it's a minus.

NealJ777 said:
I had the same exact issue. It started after the OTA update for JB on the Droid Razr.

Solution: Uninstall Maps and then re-install.
Click to expand...
I've tried uninstalling the Maps updates and reinstalling them but it didn't work. It still has the same issue.
 
Mister F said:
You really found that the audio was better? I found it to be terrible sound quality and half the street name is cut out - Woodbine becomes "bine". It also doesn't route the audio through the car's speakers through Bluetooth - not a big deal but it's a minus.
Click to expand...

My experience with Waze is much better than yours. I have never had a street name cut off. I can also route the audio through my car's speakers via BT. When Waze is about to speak, it shuts off the music as well. I also play music over my speakers via BT.
 
Stuntman said:
My experience with Waze is much better than yours. I have never had a street name cut off. I can also route the audio through my car's speakers via BT. When Waze is about to speak, it shuts off the music as well. I also play music over my speakers via BT.
Click to expand...

I'm jealous. I reinstalled Waze and it was the same thing - music from my phone is syncing to the car speakers and when Waze gives voice prompts it mutes the music but the prompts come from the phone itself. Awful sound quality and street names half cut off. Which is strange because the audio from the introductory video goes through the car speakers and sounds fine. Something to do with the speech engine? :confused:

Well if there's no fix for Google Nav I think Mapquest might be my best bet. For audio prompts anyway, which sound really good. I haven't used it enough to see how good the actual navigation is.
 
NealJ777 said:
Did you try a complete reset of the phone?

Sent from my Nexus 7 using Tapatalk HD
Click to expand...
I did, reluctantly, although it didn't take long to get my phone back the way it was. Reseting the phone didn't do anything - still the same issues with both Google and Waze.
 
Well I think I've solved the problem. It appears that the voice for the TTS engine has the be from the same country as the system language. I had the phone's system language set to Canadian English and the voice set to US English, being the closest language available. As soon as I set the system language to US English, Navigation starts saying street names.

Another option is to use a 3rd party TTS engine like Ivona. It seems to work regardless which version of English is selected as the system language.
 
Mister F said:
Well I think I've solved the problem. It appears that the voice for the TTS engine has the be from the same country as the system language. I had the phone's system language set to Canadian English and the voice set to US English, being the closest language available. As soon as I set the system language to US English, Navigation starts saying street names.

Another option is to use a 3rd party TTS engine like Ivona. It seems to work regardless which version of English is selected as the system language.
Click to expand...

I use IVONA and can no longer use any voice other than US English (I think "her" name is Kendra) if I want it to work with Google Navigation. British English ("Amy") worked fine until the JB update. This happened the exact same way when I used SVOX and it updated from Froyo to GB; British voice worked fine on Froyo, had to switch to US on GB. I was lurking the forums tonight searching for a solution to this, but apparently there isn't one. Too bad; the British voices are definitely more pleasing than the US ones.
 
Mister F said:
Well I think I've solved the problem. It appears that the voice for the TTS engine has the be from the same country as the system language. I had the phone's system language set to Canadian English and the voice set to US English, being the closest language available. As soon as I set the system language to US English, Navigation starts saying street names.

Another option is to use a 3rd party TTS engine like Ivona. It seems to work regardless which version of English is selected as the system language.
Click to expand...

Can you tell me where you set the system language to US English? I can see it in the TTS engine settings. The only other language settings I can find are in Language and Input. There the options are only English, Francais and Korean.
 
Mister F said:
Well I think I've solved the problem. It appears that the voice for the TTS engine has the be from the same country as the system language. I had the phone's system language set to Canadian English and the voice set to US English, being the closest language available. As soon as I set the system language to US English, Navigation starts saying street names.

Another option is to use a 3rd party TTS engine like Ivona. It seems to work regardless which version of English is selected as the system language.
Click to expand...

Yeah. I was going to post about this. I just discovered this last week. My system language is US English and I had another app (Enhanced Caller ID) set to use Ivona British (I love the accent).

I like having street names on Google Navigation, so I ditched Ivona.

Sent from my DROID RAZR using Tapatalk 2
 
Sorry to bump an old thread. Had the same issue on my Galaxy S4 running CM12 nighties.

Solution for me was to set my SYSTEM language (different to the TTS language) to English (United States).

You must also have Google TTS installed.
 
Tealight said:
Sorry to bump an old thread. Had the same issue on my Galaxy S4 running CM12 nighties.

Solution for me was to set my SYSTEM language (different to the TTS language) to English (United States).

You must also have Google TTS installed.
Click to expand...
Great thanks searched for solution this worked. Thx for bumping old thread.
 
You must log in or register to reply here.
Back
Top Bottom