Google Maps/Navigation no longer speaking street names

[ByteMaster0]

Please post here: https://groups.google.com/a/googlep...archin/maps/6.6/maps/7yCnPk9P8I8/-fM3Kpyqu5oJ

 

[zulu308]

i'm rooted and running liquidsmooth, the gps did the same thing to me last night but I was prompted to installed the voice Synthesiser from the marketplace, rebooted, and it work. the female audio seem to be a bit harsher than what I was used too.

 

[dwappo]

Please post here: https://groups.google.com/a/googlep...archin/maps/6.6/maps/7yCnPk9P8I8/-fM3Kpyqu5oJ

Thank you for this, it's also effecting optimus v as well.

Sent from my LG-VM670 using Tapatalk

 

[Wilson421]

Verizon Galaxy Nexus - This same thing started happening after I installed Waze to see what all the fuss was about. Waze has "Full" and "Minimal" voice prompting in both female and male voices, so it must include some hidden TTS engine or language profile. Immediately after I installed, the Waze female voice sounded somewhat mixed--like 2 different voices--depending on the prompting. Waze's "Minimal" prompting sounds like a different voice, slightly higher-pitched and faster. The "full" prompting sounded different when reading street names vs. pre-recorded directions like "Turn left".

The problem seems to be that once I set Waze to minimal prompting, it changed Google Nav to Waze minimal prompting (weird), and there it stayed--even after setting Waze back to full prompting and then uninstalling the app.

I'm going to try clearing maps and nav cache and report back this evening after the ride home.

 

[radgatt]

It has to be the maps/navigation app not stating the names. Nothing to do with whether or not you're rooted. Google will probably put an update out that will bring this back. I'm not too worried.

 

[pool_shark]

I used mine yesterday to find my way to a basketball game. It worked as expected.

 

[ByteMaster0]

I used mine yesterday to find my way to a basketball game. It worked as expected.

Are you running a ROM based on 4.0.4?

 

[pool_shark]

Are you running a ROM based on 4.0.4?

No, Sourcery is 4.0.3, I believe.

 

[ByteMaster0]

No, Sourcery is 4.0.3, I believe.

And your device properly speaks all the names of the streets, using the default new TTS in ICS? If so, then the new version of Maps is not compatible with 4.0.2 - and probably for good reason. We're the last people on earth still using 4.0.2, as everyone else (even Sprint on CDMA) already has a higher version number. Thanks Verizon....

 

[droidman0922]

Stock Galaxy Nexus from VZW - same problem. I have missed many exits lately. I only get "take the exit" or "turn left" or "turn right"...no more street names. So frustrating.

 

[ByteMaster0]

All, please go here: https://groups.google.com/a/googlep...ategory-topic/maps/mobile-android/7yCnPk9P8I8 and post your answers to the question by the Google employee chindych. Looks like they are aware of the problem and want some feedback. Maybe this can be fixed soon!

 

[TSX05]

same here, stock nexus, no root, just gives turn left, right, get off exit. nothing else

 

[sranger#CB]

Update to maps today ... wonder if it will fix this ....

 

[ByteMaster0]

Update to maps today ... wonder if it will fix this ....

Today's Maps update does NOT fix this.

 

[TJH132]

Confirmed No Go on stock GNex 4.0.2

Sent from my Xoom using Tapatalk 2

 

[ByteMaster0]

As a note, Google devs stated this in 6.7 release notes:

"Bugs that we're currently investigating:

• Navigation voice issue for 4.0.2 "

 

[dwappo]

As a note, Google devs stated this in 6.7 release notes:

"Bugs that we're currently investigating:

• Navigation voice issue for 4.0.2 "

Nice :-D

Sent from my LG-VM670 using Tapatalk

 

[wakebrdrnc]

Today I got "turn right, slight right, go straight" when I tested it after update. Bahahahaha. Glad I knew where I was going.

 

[greydarrah]

Maps voice sucks anyway. I don't know why everyone is complaining...just look at the screen and turn where it shows you to turn. Or, if you're really interested in solving the problem, root your phone and run a newer OS (that's kind of the whole point of getting a Nexus).

 

[yodatom10]

running a newer os wont fix the problem seeing that we are on the newest os. google is aware of the issue and working on a fix they just need some time.