Hi there,
I'm a rather frustrated owner of an I9300 SGS3 (I live in Israel, using the phone on English [US] system language, and the same language on the Google TTS Engine which is the currently enabled TTS Engine).
My phone is running on stock JB4.1.2, unrooted, with Maps 7.3.0. I have an issue with Google Maps. Every time I factory reset the phone, it actually does read street names on its first operation (e.g. "Turn right onto Jerusalem Road", and Google Maps has Hebrew names written in English letters so it actually works).
Then, upon the next operation onwards, it only says "Turn right", "Turn left" etc. I've tried clearing cache and Data for both Maps and Google TTS Engine. I've tried reverting back to the stock version of Maps (didn't work either). Reinstalling the update. Nothing works!
By the way, forgot to mention that - one of the tips I've found over the internet is switching the TTS engine, supposedly changing the narrator but effectively fixing the issue. While I didn't like the idea of switching the voice (I really got used to Google's American narrator), I tried to do that for the sake of fixing the issue, however the voice didn't change at all! And of course the issue persists. When I change it to either Samsung TTS or Ivona (which I had to download), the voice of Google Maps remains the same and the issue persists.
One of the tips I've found over the internet is switching the TTS engine, supposedly changing the narrator but effectively fixing the issue. While I didn't like the idea of switching the voice (I really got used to Google's American narrator), I tried to do that for the sake of fixing the issue, however the voice didn't change at all! And of course the issue persists. When I change it to either Samsung TTS or Ivona (which I had to download), the voice of Google Maps remains the same and the issue persists.
What can I do to fix this issue? Please help me, I'm seriously desperate about it, and I REALLY don't like Waze.
Related
When using navigation I just get prompts of "turn left" etc. rather than hearing "turn left on Main Street." I've done some Googling on this problem and it seems it was a bug in an update to maps a few months ago, but has since been fixed (I am running the latest maps build. I also found that it was an issue running Android 4.0.2, and the release of Android 4.0.4 fixed it (which is the build of Liquid's ROM).
The first time I opened Navigation I was prompted to install a text-to-speech engine, which I did. I assumed Liquid's build just didn't include one since it is so bare bones. The one I was prompted to install was called Speech Synthesis. I also went into my TTS settings and see that PICO TTS is checked (only option I have now). My Google Maps Locale says "en." I've tried using both the "en United Kingdom" and the "en_US" options for the TTS engine neither works correctly. Other apps TTS work fine, just the issue in navigation.
Anyway, any one else have this issue or know of a fix? Uninstalling and reinstalling Maps didn't do the trick either as others have reported to work. What is the best TTS engine to install?
I appreciate any help.
I bought SVOX a couple years ago. The voices sound more natural than Pico by a bunch.
Yeah, I've heard good things about SVOX, but I'd rather not pay for different voices when the free solution isn't working properly.
I know what you mean. SVOX almost certainly won't fix the issue. I didn't mean to imply that it will. I was just recommending a better TTS app, IMO.
Slim1023 said:
Yeah, I've heard good things about SVOX, but I'd rather not pay for different voices when the free solution isn't working properly.
Click to expand...
Click to collapse
Actually, I think it does, I noticed a while ago on my old S2 that if I used the Samsung voices I would only get "Turn left", Google (Pico) gave me "In 50 metres Turn Left onto Booga Street"
SVOX gives me the full street and lead up.
I'm wondering though if it might be based on language. My boss doesn't like the idea of buying a TTS if it already comes with one but he used to use the navigation on the old HTC Desire (now on a GT-I9305T).
I'm wondering since the included TTS usually come as en_US or en_UK, but the system is set to en_AU, maybe it doesn't fill in the rest (I use SVOX with the Olivia en_AU voice and I have no issues)
I tried it at lunch on my bosses phone, Set the System Language to the same as the Google Voice (en_UK) and it started spouting street names and full directions.
If that works for you as well then I think we have a winner.
I had the same problem. I switched to Liquid ICS v1.5 MRV JMOD version and the navigation now says the street names. Also I am using Maps version 6.12.0.
I downloaded the IVONA TTS engine and all started working.
I've been having issues when I go to Google search. When I launch the app the mic is solid at the time of launching but then becomes hollow and is not possible to activate via saying Google now. I've looked around and tried everything. Changing language to a different language and back to USA English. Clearing cache. Uninstalling and reinstalling. Make sure hotword detection is on. Nothing seems to work and this has only started less than a week ago. Just curious if I'm the only one of if there are others
I've done a lot of searching for a solution for this problem. Google maps doesn't read street names. It has nothing to do with the time of day as suggested by other threads. Also, clearing the data/cache and rebooting doesn't solve the issue for me. Changing to Ivonna or another engine does nothing. Maps insists on using the faulty google tts.
I have seen this behavior on Sense 6 Roms including Viper and the ATT Debloated with integrated voicemail into messages.
The problem appears to involve Google TTS because whenever I go into setting/language & keyboard/text to speech I see that the system is stuck on "checking default"
Skydragon Sense 6 on the other hand works fine.
I've been trying to see what the difference is without coming up with a solution.
Have others seen this?
Any fixes?
What language are you trying to use? All but english french and spanish were removed from the one i put out for users...This would explain why no sound with streets if using another language...works with english here with no issues....
Hi xda! (been awhile since I last was here...)
I seem to have a problem with my Ultra (C6833), Android version 4.4.4 (official), not rooted, just plain stock Nordic rom via OTA. But using Google Now Launcher.
I can't seem to make "ok google" work with voice only. The settings -> input -> voice search -> "ok Google" detection -> From any screen -page doesn't register my voice *at all*, nothing happens on that screen. Also on any launcher screen or Google Now, saying "ok google" doesn't have any effects what so ever. When I manually click on the mic icon on any of these pages, Google now works perfectly and most of the time I don't have any trouble it understanding me (not native English speaker).
I tried installing OpenMic+ and tried that, but almost the same happens with that. It works when the actual OpenMic+ program is open, but NOT when it is in the background.
The same settings DO work on my Note 8.0 just fine, and the mic works on the Xperia when making calls (or after clicking the mic icon, voice search works fine). So what gives?
if you still need help with this first make sure your play services google (search or now whichever u decide to call it)play store an gmail are up-to-date last two may not be necessary not i an others have had issues when not once thats done clear cache an data in apps section under settings for Google an play services
Oh, thanks and yeah, haven't gotten it to work. I forgot to clear the caches, silly me. I did check that everything is up to date. I'll try clearing caches.
Ok everything is up to date and clearing the cache still doesn't do it this should be magic goto Google now go to settings go go to voice go to offline speech recognition set auto update to always over data or WiFi go and download UK English language for offline once it's done go back to the installed tab press and hold English UK the selected close Google now open it back go back in that same section and press and hold English us language to select it now try your okay Google
techdeisel said:
Ok everything is up to date and clearing the cache still doesn't do it this should be magic goto Google now go to settings go go to voice go to offline speech recognition set auto update to always over data or WiFi go and download UK English language for offline once it's done go back to the installed tab press and hold English UK the selected close Google now open it back go back in that same section and press and hold English us language to select it now try your okay Google
Click to expand...
Click to collapse
I think what that says is use english US the language for OK Google
hmmm?
---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------
yes i know but the switch to uk an then switching back is what works
EDIT: SOLUTION FOUND! SEE BELOW
I'm having the exact same problem with my Xperia Z2.
Any further advice would be amazing. I'm running Android 4.4.4 and read that some apps can interfere with 'ok google', but I can't track down this problem.
Changing languages doesn't seem to help (I tried Australian in the past). Can someone confirm the above worked? I'm running on limited data plan here and would like to avoid recklessly using it up ;(
EDIT: After browsing for a few hours a few days ago looking for a solution, just after writing this post, THAT article showed up. And 'ok google' works now!
http://ausdroid.net/2014/05/08/fix-google-now-voice-commands/
It was LastPass accessibility service running in background! After turning it off, 'ok google' works now
For the record, to this day I haven't been able to make it work on my Xperia. It works perfectly on my Galaxy Note 8.0 and my HTC One M7, but for the life of me, I have not been able to get it to work on this Sony device. It keeps working the same as always - works perfectly with manual activation, but I cannot get the "Ok Google Detection" to do ANYTHING. (the page where it asks you to say "ok google" three times to "learn" your voice). It just does nothing, it does not register my voice at all on that page.
So glad found this post!
dark_skeleton, you are my HERO!
I couldn't find a solution for this problem for around 4 month!
I was already thinking that there is a hardware problem in my phone,
and just for the chance of succession checked Google again, and SO GLAD I DID!
I used 'OK Google' detection on a daily basis!
In my case, the problem was the application "Informer for SmartWatch".
It was using an accessibility service and blocked the voice recognition.
AnttiV, try going to the accessibility menu and check what services there are external (not pre-installed by Sony).
Seems like it really helps!
Thanks again dark_sekeleton!!
Another app, which is making problems with "Ok Google" is Smart Extension - Hangouts.
stemer said:
Another app, which is making problems with "Ok Google" is Smart Extension - Hangouts.
Click to expand...
Click to collapse
Yeah, it was that for me. I've been testing a week or so now without it and everything seems to be working fine. Sadly there's now no way to have hangouts on my SW2, which sucks. But the extension doesn't work with Lollipop anyway, so...
Time to upgrade to Android Wear / Apple Watch?
Hi all:
I'm trying to get Assistant voice typing and Auto punctuation to work on my new Pixel 6. Both options are greyed out in Gboard settings right now. Is anyone else seeing this behavior, or is it working correctly for you?
did you train voice assistant to recognise your voice?
mdimbler said:
Hi all:
I'm trying to get Assistant voice typing and Auto punctuation to work on my new Pixel 6. Both options are greyed out in Gboard settings right now. Is anyone else seeing this behavior, or is it working correctly for you?
Click to expand...
Click to collapse
I got the exact same problem where on my son's phone this works
Update, got it enabled now and it works with multiple languages. Since I'm from Germany I have German and English enabled. I don't know what exactly was the trigger, but I played around with language, language settings and offline languages, re-configured everything, re-downloaded languages and so on in assistant settings. The problem must be somewhere there. Maybe someone finds the exact spot
I really want someone to get back to me, as I have the same issue with my phone. I will try the google assistant training first
originali said:
did you train voice assistant to recognise your voice?
Click to expand...
Click to collapse
Yes, the voice is already trained.
I'm having the same issue. Out of curiosity, for anybody having the problem, do you have a work profile set up on your phone? I know that with my Pixel 4, some of the new Google Assistant settings were unusable when I added my work account because my employer didn't have some setting enabled in Google Workspace.
I'm wondering if this is related to the same thing. I haven't gotten around to removing that account to see if that clears up the issue yet. I can report when I have time to try that.
Edit: That does appear to the culprit for me. As soon as I deleted my work account, I was able to activate that setting.
So far after re-adding my account, it's stayed enabled, but we'll see... If this is the culprit, I believe it's likely related to this:
Turn Search and Assistant on or off for users - Google Workspace Admin Help
Google Assistant is not available for managed Chromebooks. As an administrator, you can control who uses Google Search and Assistant services with their Google Account. Just turn the service on or of
support.google.com
Thank you brc64! I don't have a work profile set up on the phone, but I did have one work Google account and one Google account from a non-profit I volunteer for on here. I removed the non-profit Google account and the options became available. I, too, added the account back, and both Assistant voice typing and Automatic Punctuation are still enabled.
I haven't gotten it to work yet. Figures I'd run into this! Have us English set everywhere only and downloaded us offline English. Hopefully I'll be able to sort it out! Of all the silly things that's not enabled by default when we turn on voice typing... Thanks Google
Update: I think it might actually be server side change or from an app update. I updated all my apps and it started working shortly thereafter.
I tried all the solutions listed but nothing worked. What fixed it for me was to force stop Gboard. Clear cache. Then select uninstall updates. Let's Google play store update it. Then repeat the same with Google app (force stop, clear cache, uninstall updates then update.) Initially had to force stop Gboard again then open and that's it, boom it worked. Hopefully this helps.
nEUTRon666 said:
Update, got it enabled now and it works with multiple languages. Since I'm from Germany I have German and English enabled. I don't know what exactly was the trigger, but I played around with language, language settings and offline languages, re-configured everything, re-downloaded languages and so on in assistant settings. The problem must be somewhere there. Maybe someone finds the exact spot
Click to expand...
Click to collapse
Is it working for you in both languages? Because I'm bilingual as well and although I can switch the toggle, the true assistant voice typing is only working in English. When I switch to German, it uses the old voice typing method. You can tell the difference by the icon the little microphone has. The assistant voice typing has the newer logo.
It's something on the server side. I was on the phone with them yesterday for 90 minutes trying to get the problem resolved, then this morning some type of download came through and it was fixed. Fixed. Just be patient and you'll get it resolved. As a matter of fact, I'm using the service right now
I concur with the server side assumption. I finally got it to work, when I revmoved a second language both from Gboard and the assistant. But since I need to be able to switch to English regularly, this was too much of a hassle, so I reactivated the second language. This took me back to the regular voice input and grayed out the option for the assistant for voice typing.
I did not change anything since then, but I just found, that I now could switch on Assitant voice typing again and it works with multiple languages at once. There have been some auto updates over the play store this morning, so this might have to do with this.
Try to update all apps in your Play Store profile. If this does not help, I guess patience is all that can.
ThoroSOE said:
I concur with the server side assumption. I finally got it to work, when I revmoved a second language both from Gboard and the assistant. But since I need to be able to switch to English regularly, this was too much of a hassle, so I reactivated the second language. This took me back to the regular voice input and grayed out the option for the assistant for voice typing.
I did not change anything since then, but I just found, that I now could switch on Assitant voice typing again and it works with multiple languages at once. There have been some auto updates over the play store this morning, so this might have to do with this.
Try to update all apps in your Play Store profile. If this does not help, I guess patience is all that can.
Click to expand...
Click to collapse
What language are supported?
ofrias said:
What language are supported?
Click to expand...
Click to collapse
In my case I am running German (Germany) and English (US)
I can confirm this is caused by multiple language, and specifically it is in your google voice assitant setting.
..
BunkMoreland said:
Is it working for you in both languages? Because I'm bilingual as well and although I can switch the toggle, the true assistant voice typing is only working in English. When I switch to German, it uses the old voice typing method. You can tell the difference by the icon the little microphone has. The assistant voice typing has the newer logo.
Click to expand...
Click to collapse
I have the same setup and issue. tried everything. did you manage to get it working?
gattacus said:
I have the same setup and issue. tried everything. did you manage to get it working?
Click to expand...
Click to collapse
Unfortunately I did not. It works fine in English, but no shot getting it to work in German when I have both languages in my assistant, the phone and the Gboard turned on.
Mine just stopped working this week without me doing anything. It's greyed out.