Up until now my voice search results have been spoken in a male voice with a british accent. Suddenly this evening my Nexus 10 has turned into a female american. In addition, and probably more importantly, it has stopped reading back results for some queries. It will still read back the result for "How many teaspoons in 500 liters", but not "how far to alpha centauri", for example, when it always read back both before. I've changed no settings.
What had changed and how can I get my british male voice back for all results?
i'm suddenly experiencing similar craziness. it seems like google's servers are borked
Interesting, I wonder if its location dependent.
Mine has always been in the same female voice as on the nexus 7 TV commercial in the states.
Ok, the search reading or not reading results seems to be the result of how particular the search is about whether or not it returns on a card or just directs to the google results. Fine, I can live with that.
The loss of the british voice seems like it's possibly related to android issue #8463 - "Language setting ignored in google navigation" (I can't post links yet). People who have languages other than american english selected as their default text-to-speech language are still getting american english in other google apps, and have been for years.
Related
Is there any app out there that will allow speech to text from within any application, or whenever you pull up the keybord or something? Preferably multi-lingual.
HTC_IME
You can install the modified HTC_IME keyboard that comes with the speech-to text-button on it, you can make a modified version of it at gimpsta. com/themer/index.php. It uses the google speech thingy, so you should be able to speak in more than English I think.
Then to use it, if you go settings > Language & Keyboard, yuo should be able to eck HTC_IME mod. Then long click any text area > Input method and chose HTC_IME mod.
What is REALLY stupid thing by google/android is that they dont offer a text-to-speech / speech-to-text/ voice search to languages that literally pronounce every single letter the way theyre written. It would be the easiest thing in the world to do. This would offer a solution to many languages (such as Finnish thats heavily ignored by google/android in every other aspect too).
Just my 2cents. Ppl at google plz read this.
wardy666 said:
You can install the modified HTC_IME keyboard that comes with the speech-to text-button on it, you can make a modified version of it at gimpsta. com/themer/index.php. It uses the google speech thingy, so you should be able to speak in more than English I think.
Then to use it, if you go settings > Language & Keyboard, yuo should be able to eck HTC_IME mod. Then long click any text area > Input method and chose HTC_IME mod.
Click to expand...
Click to collapse
JuniperFIN said:
What is REALLY stupid thing by google/android is that they dont offer a text-to-speech / speech-to-text/ voice search to languages that literally pronounce every single letter the way theyre written. It would be the easiest thing in the world to do. This would offer a solution to many languages (such as Finnish thats heavily ignored by google/android in every other aspect too).
Just my 2cents. Ppl at google plz read this.
Click to expand...
Click to collapse
Thanks for the replies. First, HTC IME does have speech to text, but only in english. Choose another language and the mic button automatically becomes just a simple settings button. SO much for that...
As for Juniper's rant, I agree. I love Google. I mean, I'm a God damn fanboy! I live and breathe Google and have tried to convert all my friends and family and misc forum users to Google services whenever possible. But the fact that they mainly play for the big boys (English speaking countries) and always try their services in a fixed set of countries first, kinda annoys the hell out of me and makes me feel left out. ****, I even went as far as to buy a Nexus One online for almost double their worth because they didn't go on sale in Portugal for a very long time. I just consider myself lucky I was able to sell it on for a small profit despite the already ridiculously high price I had paid for it to begin with. But even after that I opted for a HTC Desire just because I wanted the best Android experience possible (at the time). I am a Google advocate. ****, Google has probably made (what to them must be a small amount but to normal folks would be) a metric ****load of money just on services bought by people I have recommended use Google over the past decade or so. Me, myself, I use Google for just about all my online needs from shopping to social networking. So no, this issue won't make me want to stop using Google, for sure, but it does make me feel my "relation" with Google is just that little bit less "special". They do tend to be biased and not support the little guys.
That said, I still have no solution to my question. Ideas?
Good afternoon.
Hope someone can help as I have never expereinced a problem like this on my previous S3, I just got a new S7E and I set it up to use UK English, when I click on the microphone button in the message box (either text or WhatsApp), it beeps and says "OFFLINE MODE UNAVAILABLE".
I then clicked on the gear icon and looked at the language settings, the US English is up to date and set as the default, I also d/l'ed the French language pack without any issues, but when I tried the UK English, nothing happens, the pack is there looking like its ready to d/l and I can cancel it, but nothing is actually happening. This is with SwiftKey. I have also tried it with the Samsung keyboard & Google speech and its the same. The UK language pack just isnt being downloaded
I am based in Dubai and I have tried this on my home WiFi, via a friends VPN connection and via my mobile data so it's not something specific to the Middle East (and I had no issues with the S3). The phone is completely upto date with all the software etc done.
Could anyone point out what I am doing wrong or if it is a general error and I am not admitting defeat to my Apple friends who said I should swap from 'droid to IOS - they can bugger right off...!
Many thanks
Claire
check out this one... asked it to "give me cycle directions"....
got directions from a place called "mecycle" in the north of england.
Interestingly the actual speech to text heard what i said correctly..
So I was wondering how many of you had gone through with implementing the buildprop change that enables Google AI. I decided to do it the other night and have been fiddling around with it since then. If you haven't done it, it basically turns Now-on-Tap into "Voice Search by default," but you can still do screen searches for things like USPS Tracking and Phone/Address Lookup. Voice searches are vastly improved; it will auto-start Navigation, fetch links as a list of cards (for example, miniaturized news feeds), open apps instantly (provided the phone isn't locked), and essentially just be all around snappier than Google Now/Now-on-Tap.
That said, it does bother me that the phone literally had to be rebranded as a Pixel to make this work. A) It's not the most stable change, and 2) that change is now reflected on any device/prompt that interacts with my phone. It managed to be picked up by adware on a sketchy site (don't ask what sketchy sites I go to), and my desktop also mislabels it on USB connection. Does anyone know if Motorola allows you to change the device name for USB connection? I know LG lets you.
But yeah, those are my thoughts on it. I might try it out for a week or two, and if I'm not exactly bowled over by it, I'll probably just go back to Now-on-Tap. But I wanted to hear your guys' thoughts.
I don't even use now-on-tap, and I've done the assistant bulildprop trick before, and it made little to no difference on how often I use both of them. I understand what you mean by having to rebrand it to a pixel though - Google shouldn't make this Pixel exclusive
XE24 with the search apk : "ok glass" (native to the XE24 release) is close to impossible to use by speech recognition.
Asking a google question, is surprisingly perfect, even with odd city names in norwegian, it recognizes "every" question perfectly.
Was/Is there some "ok glass" training for hardware detection of that phrase in the glasses? - anyone know how to trigger that learning?
We have an XE23 at work, and from what I remember, it is equally "impossible" get to recognize "ok glass".
the thing I noticed is that if you say it with an english pronounciation, it always works (saying the A as in "ah"), while saying it the american way doesn't always work (saying the A as the E in mess), maybe that helps. and yes, the speech recognition is bad, but it's based on an android that is almost 8 years old
You are absolutely right, I found that out by myself since then, except I found that the "ass" the three last letters needed a little different pronunciation.
I changed my habit and it's reliable now.