Database Info

[Q] Voice search not available for your carrier.. Is that a joke?

Hello all,
I just cannot believe what I am seeing!
I currently use CyanogenMod 7 and was sad because I couldn't find voice search in the Market.
After a quick look in the Web Market, I just learn that my Carrier (Base, Belgium) does not allow (see attached screenshot)
After Googling, I just feel alone because no one else reported same issue

Just installed Market Enabler and everything is fine.
I am just astonished to see that such a basic app is country-dependant

Same thing happened to me i just reflashed the rom.. and ofcourse wipe dalvik and wipe data/cache and it went away hope it helps
Sent from my Nexus S using XDA App

Lol! Funny thread

Why is that a funny thread?
Because you live in America and you have access to all Google services?
Please think about all other countries that have to cross their fingers each time there is a new product/service/application to know if that will be available in their country.
That's just amazing that we have no information on why we have access to a limited services and having restriction on basic stuff like voice search because we live in other country than America.

I guess voice search is tailored for each language? Hence the lack of support. I know voice search initially supported only English, more languages were added later on. If your language is currently not supported, I guess that would be the reason why it's not available in your country.

Google voice search work pretty well in english and french-dutch-german (our 3 national langages)
Just tried every langage with amazing results.

I had the same issue with YouTube.apk. Market Enabler fixed it again for me, but I remember Google having removed the region-related conditions on app-purchasing... what's up with that?

[Q] Google Nav and SVOX Classic

Hi,
I am at a complete loss. In Language and Input Settings the default language set is English (United States). I have SVOX Classic installed and legitimately purchased the Grace (US) voice. I have SVOX enabled and set as the default engine. In settings with I tap listen to sample, it tells me it is SVOX Classic. All my apps that support TTS use the SVOX Grace voice.
However, whenever I use Google Navigation, I get the window asking me to install a voice, which is weird, because I do have SVOX Installed. I then proceed through the steps, by clicking install anyway, but it's as if Google Nav doesn't seem to recognize that SVOX is installed. I make sure to select Grace as the voice, but instead of getting street names read, etc like it should, Google Nav just tells me when a turn is approaching in X number of miles or feet, and when I approach the turn it just says "Turn Left" or "Turn Right." No reading of street names, etc.
I've tried every trick I read online in all sorts of forums. I tried uninstalling the Grace voice and SVOX Classic. Rebooting the phone, then reinstalling svox and the grace voice. For some reason or another, I cannot get Google Nav to recognize and use the default SVOX TTS engine.
Does anyone have any insight?
Thanks!
--Q
PS - Samsung Galaxy S2 Skyrocket, rooted, stock ROM (v2.3.6 build UCLA3)

I have a Galaxy S3 with ICS and had this same symptom.
Both my google navigation and my talking assistant spoke in that monotone google tts instead of the SVox that I could hear if I pressed listen to a sample.
the trick was to install Text-To-Speech_Extended_3.1.apk
you may not find this on google play or if you do it may say it is not compatible with your device.
download it from here http://www.freewarelovers.com/android/app/text-to-speech-extended
then open it with your file explorer and install by clicking on the apk.
you will find that your svox will work with google navigation on ics with the galaxy s3 and I presume the s2 as well.
if no luck after install, try swapping back to old speech engine and back to svox in android settings.

Uninstall google now? Reinstall ICS voice recognizer? Eva voice assistant issue

Running latest synergy at the moment but same problem happened with beans 9 and prior. Basically eva voice assistant works for a while and then it never responds to any command, even though i can see it here me it never proccesses what I say. Only way to get it working is uninstall, delete eva folder, then reinstall. I am in contact with developer but i suspect google now may be causing it, even tho google now voice search hears me fine and responds. Is there a way to uninstall google now and go back to ICS voice search and voice recignizer?

sfetaz said:
Running latest synergy at the moment but same problem happened with beans 9 and prior. Basically eva voice assistant works for a while and then it never responds to any command, even though i can see it here me it never proccesses what I say. Only way to get it working is uninstall, delete eva folder, then reinstall. I am in contact with developer but i suspect google now may be causing it, even tho google now voice search hears me fine and responds. Is there a way to uninstall google now and go back to ICS voice search and voice recignizer?
Click to expand...
Click to collapse
Have you figured this out any further? I'm on Synergy but I think it's definitely the Google Search engine and perhaps changes with Jelly Bean. I really wanted to explore voice assistants more, but I don't think I'd be willing to give up Google Now and restored local search etc

I am currently using cm10 but did this on cleanrom and synergy. The fix i am using is to search the market for voice search app to install the pre jellybean voice search. Then in language and input I select voice recognizer, which shows google twice. I select the 2nd one. I then choose voice search to confirm the background is black, which means ics voice search is selected. Using the market voice search eva has been working fine. Peter, the author of eva, said he released an update today that should have eva work with jellybean voice search, but it didnt work for me, so i am continuing with ics voice search from market.

With my workaround if you want to use google now and eva i assume you would have to switch the voice recognizer each time you wanna use one or the other. If you use eva or wanna try it the new version is 2.34, free 30 day trial version called eva intern. The author said it should work so try it with yours and see.

Thanks, I'll give the new build a try. I see what you're saying with the workaround but I'd rather just use Google Now and S Voice without fussing with it. Nice of the developers to work with the issue.
Sent from my SCH-I535 using Tapatalk 2

[Resolved] Help! Weird problem with text-to-speech setting

I ran into a problem with the recent update to the Google Text-To-Speech app.
I was testing out and trying to decide between the new high quality US and UK English voices. Somehow my default language for speech got locked into UK English: I can no longer change it to anything else, even though my default device language is US English and I have downloaded both the low and high quality US English voices.
See my screenshots - despite me changing my chosen language to US English in the Google Text-to-speech Engine settings in the 1st screenshot, once I hit the back button (or exit via the home / recent apps buttons), my default language reverts to UK English as per the 2nd screenshot.
Is there any system file I can edit to change this absurd behaviour? I'm rooted and willing to get my hands dirty...
UPDATE:
I played around with settings and managed to resolve the problem.
Clearing data from / un- and re-installing the app / restoring data from another device didn't work - what did work was choosing another default device language (NOT the voice language under Text-to-speech output). This somehow released the "lock" on UK speech and allowed me to choose US instead. I then reverted the default device language to US English.
All is now good in the world :victory:

Trying going to Google Text-to-speech or Google TTS, whichever one it is, in the app settings and clear data.
Sent from my Nexus 5

Lethargy said:
Trying going to Google Text-to-speech or Google TTS, whichever one it is, in the app settings and clear data.
Sent from my Nexus 5
Click to expand...
Click to collapse
That was one of the first things I tried, but it didn't help.
Anyway I managed to resolve the problem already. Gonna update the OP.

mlj11 said:
That was one of the first things I tried, but it didn't help.
Anyway I managed to resolve the problem already. Gonna update the OP.
Click to expand...
Click to collapse
At least you got it worked out.
Sent from my Nexus 5

[Q] Google navigation not speaking street names?

Anyone notice their Google Maps is not speaking street names? It was the first thing I checked when I got this phone because my S3, Galaxy Tab, Galaxy Tab S and Nexus 7 are all doing the same thing. Ironically, my IOS devices work just fine.
None of these devices have been rooted.
I've read somewhere that the TTS voices don't match my system language but on my Telus and Rogers devices, I don't have US English available for a system language. Any clues?

Bell s6 edge...Google navigation working perfectly fine with voice and street view
sent from my s6 edge

Not street names for me on Rogers as well.

Spent a few days trying to figure this out. I've tried the clear cache in Maps and Google TTS, even a full device reset. I've set it up as a new device and it still doesn't speak street names. I can understand why this would happen on my S3, it's old hardware but an out of the box S6?
It does work.... if I flip the system language to French tho.
A full wipe also fixed my Nexus 7.

I've noticed google maps doesn't consistently annonce street names on several devices I've owned but maybe try uninstalling then reinstalling. Always seemed to work for me across all devices.

Unfortunately, I can't uninstall maps. It only removes updates and reverts back to the version that came with the phone which also has this problem.