[Android Apps and Games] faku1810:
I agree with you and most of the previous post. I wouldn't leave Google Now as default but the "ask to repeat" setting and I think that extra voice prompt is the way to go (but make it play after the first time it didn't understand a command) Actually, i think it asked me to check the command list in the settings after a few times it didn't understand me; so it could do something like that the first time too:

"I didn't understand what you meant, if you're still learning to use me, you can check the command list or set up how I should react to unknown commands"

Then it shows a pop up with three buttons "Command List", "Set Try Again setting" (it would open the Advanced Settings, but the user would already know it has to look for "Try Again") and a "No, i'm fine" button that would set a flag so utter wouldn't give this warning again. It could wait for a voiced reply, but i think a pop up is more newbie-friendly and less code to write, maybe? :confused:

Anyways, that's just my opinnion on the matter. On a side note, I'm testing a few different things on utter and so I have a few questions..

1) Currently in my phone i use Google's recognition with Spanish (Spain) language files downloaded, but in Utter i chose Spanish (Argentina) as Native Recognition Language.

Problem is, whenever i test it offline, be it from the app or a custom shortcut for "Spanish (Argentina) it will give me a speech server error, or it will roll back to english recognition; but if I make a shortcut for Spanish (Spain) it will work almost perfectly. I say almost because my accent is not quite as that of Spain, so for example, whenever i say "perrito" it will hear "egipto" or "pe ji to" unless i pronounce the "rr" in a particular way.

Therefore, my question is... Am I stuck with this? I know it's not utter's fault, but Google's. As it seems the language files it downloads are only to be used with Spanish (Spain) and not any other kind of Spanish.. And probably, even if they were used, it would still not recognize a non-Spanish accent. Of course this is only an issue for offline use, on Wifi it works fine i think.

2) My default TTS Engine is Samsung's Spanish voice, but I don't want utter to use it until the translation has been done. This hasn't been a problem yet because utter! speaks in english anyways.

However, I've realized that if I explicitly choose Samsung's spanish voice when creating the shortcuts, it will work the first time, and roll back to the english voice when replying. Then I installed Ivona's Spanish voice, left Samsung's as default and made a shortcut with Ivona's voice; it would reply with samsung's voice, and then roll back to english. Finally I set Ivona as default, and then made a shortcut with Google's eng-usa voice engine.. it would reply all the time as Ivona Spanish.

Therefore, i conclude utter is unable to override the Default TTS selected, and can't work with Samsung's TTS either... Which in a word SUCKS, because Samsung's spanish voice is better than most i've tried (and free, on top of that). Is this some kind of incompatibility between utter! and Samsung TTS?

Sorry for the really long post, I've hidden my long explanation on Spoilers and resume the post in the following questions:

1) Is there a way to use Spanish (Spain) downloaded files for Google Recognition with any other kind of Spanish variant, or is it like English that needs a different package for UK, US, and Australia?

2) Is there some kind of compatibility issue between Samsung TTS and Utter, as it won't ever talk to me with that voice engine?

I guess this could also work, Screen StandBy has a first-run assistant setup that lets you choose between some pre-defined default settings (according to phone model and intended usage) or manually setting up the app on your own.