I'm having a bit of a problem. Sometimes when I use moto voice it doesn't work. I have to redo the phrase and it works. Does anyone have this problem ?
I have found since I upgraded to lollipop that it is a lot less responsive. I often have to say my phrase multiple times and when it does recognize it there's a long pause between my command and it forwarding it to Google voice command.
Which phrases you used when you faced the issue?
Responsiveness depends on the phrase, this is what I have learnt form my experience. If you have a very unique and strong phrase which is easy to recognize for your MotoX then it will not have issues in the long term. I have kept many phrases and finally reached to my current phrases.
In the mean time try switching off your customized phrase and use the "Ok Google Now" for the time being to makes sure that works perfectly fine in long term.
Related
First of all - congrats Incubus, dzo and Kalt Kaffe on getting froyo working on our Vogues, and doing such a great job of it !
The primary reason I have been looking forward to Froyo is so that my wife and I can finally LEGALLY use our Android Vogues for making calls from a car. I live in Ontario, Canada, but I believe that numerous other provinces and states ban using a handheld device while driving.
My old Motorola phone does a great job of this. My wife still complains that "eyes free" voice dialing does not work on the vogue. I hear comments like "I hate this stupid phone, why can't we just get another simple Motorola phone" Nooooooo! Heresy !!!
With Incubus' RLS 10 and DZOs latest NBH, we are ALMOST there.
When I press the voice dial button on my paired and connected blueant S1 speakerphone, the phone launches the voice dial application !!!! Great !!!
What it does NOT do (yet) is give any sort of voice feedback. It does not say "say voice command" after launching the voice dial in this manner. It does reckognise my voice and come up with the person(s) it thinks I have said to dial. But the results only come up on my phone's screen. It does NOT speak to me via bluetooth audio to confirm my choice.
This means I still have to hold my phone and look at the screen when using the voice dialer, and that is still breaking the law and still unsafe.
My first thought was perhaps bluetooth media audio was not working, but when I play a youtube video with my bluetooth speakerphone paired and connected, the sound does come through the speakerphone. Also when initially dialing the touch tones come through the speakerphone.
My understanding reading several google forums, and Froyo reviews is that voice feedback is supposed to be part of hands-free voice dialling in Froyo.
I already think very highly of all of you and am very thankful for the great work you have turned out. If you guys can get this feature going, you will be like gods to me and my wife will (hopefully) stop hating me for getting her a Vogue !
+1 !!!
~fitzbg
heh heh - silly me - forgot that we have to install the TTS engine and data.
I installed PICO TTS engine and data, and when I pressed the vd button on my bt speakerphone I heard the Vogue say "speak now" !!!!
Then I pressed the end button on my speakerphone and the voice app hung then crashed. :-(
Oh well - major progress anyways - time to reboot and play some more !
EDIT: update: if after hearing the "speak now" prompt, I say something like "call Joe Smith", I get a confirmation dialog on the screen, allowing me to choose "Joe Smith Mobile" or "Joe Smith Home", but unfortunately no voice prompt asking me which choice I want. The only way I can make a selection is to press the choice on the screen. Google you should be ashamed of yourself - this is PATHETIC.
Worse yet, if there is only one number for a contact, and android comes up with only one choice - it immediately dials that choice without voice confirmation or even screen confirmation - and it may be dialing the wrong person.
Better than nothing, but sad that this so called "smart phone" still remains a very dumb PHONE, even though it is a great mobile data device. My 7 year old Motorola is still vastly superior in PHONE functions. It has amazing customisable voice dialing and voice command built in by nuance. I sure do miss that.
Thanks for reading my rant - maybe I should go to sleep now - LOL
feel free to edit the source code and add the updates you want
Seriously though, BT has come a long way, is there room for improvement? Sure.. but we can only work with what google gives us
I hope I did not give the impression that I have anything other than enthusiasm and gratitude for all the chefs that have voluntarily produced such great work. The glass is 95% full - and I LOVE having Android on my phone instead of Windows Mobile. Thank-you, thank-you, thank-you !!!! I'm only frustrated by bluetooth voice dialing. Once you have had a good version of it, you can no longer live without it !!
Now back to the technical, if anyone is willing to look into this I would be thrilled, Sorry for being long - but I think a detailed reply is more helpful than one or two sentences.
After reading through numerous google android forums, bluetooth dialing SHOULD give audio prompts to confirm a voice dialer selection. That does not happen on my Vogue with Incubus' rls 10 and dzo's July 8 froyo nbh, system and data on NAND.
I found that the bluetooth dialer after a fresh install of ROM and speech data, does work up to a few times. What happens is the bluetooth voice dialer launches with the term "starting up", the audio prompt "speak now" is heard, and the term "listening" appears in the dialog box. Other than a lack of audio confirmation, voice dialing then works. One other note, the prompt "speak now" is very very quiet, even with audio turned all the way up - although call volume is loud.
When the bluetooth voice dialer fails after a couple uses, initially it still launches the dialog box which reads "starting up" and gives the audio prompt "speak now", and then it freezes - the term "listening" does not appear.
Once bluetooth voice dialing fails, all voice recognition features, such as voice search also stop working.
A reboot does not fix the problem.
Deleting and reinstalling the audio data, along with rebooting does not fix the problem.
Re-flashing the NBH does not fix the problem.
I have to reflash the ROM to get bluetooth dialing, or any voice recognition function to work again.
If anyone is able to look into this, I would greatly appreciate it, as would some others. Hope this information is helpful. Thanks again for all the great work!
mssmison said:
feel free to edit the source code and add the updates you want
Seriously though, BT has come a long way, is there room for improvement? Sure.. but we can only work with what google gives us
Click to expand...
Click to collapse
dpkform said:
I have to reflash the ROM to get bluetooth dialing, or any voice recognition function to work again.
Click to expand...
Click to collapse
Just clearing the data partition likely have the same effect and I wonder, just maybe "rm /data/misc/bluetoothd/*" would be enough?
Not a solution and you would need to redo the pairing but sure beats reinstalling everything.
thanks Kalt_Kaffe
on vacation now, will try when I get back next week
kallt_kaffe said:
Just clearing the data partition likely have the same effect and I wonder, just maybe "rm /data/misc/bluetoothd/*" would be enough?
Not a solution and you would need to redo the pairing but sure beats reinstalling everything.
Click to expand...
Click to collapse
The subject pretty much says it all. I know that Google Now won't work on my Nexus 7 offline (even with downloading the offline speech recognition). Can you do even the basic stuff (like make a call) via touchless control without Internet access?
EDIT: Arrgh! I meant to post this in questions. Could a mod please move it?
i put mine in airplane mode. okay google now woke up the phone but telling it to open an app said i was in airplane mode.
the only command that works without data is "find my phone" as far as i know...
jhnl33 said:
the only command that works without data is "find my phone" as far as i know...
Click to expand...
Click to collapse
"Call" works without data. I think text does too, but I never tried it.
ryude said:
"Call" works without data. I think text does too, but I never tried it.
Click to expand...
Click to collapse
It's a bit more complicated. On my Moto, when I have internet, it uses Google Search App to search contacts and place calls. When I disable wifi and mobile data, call command still works, but uses some internal app (which, in my opinion, is better than G. Search in contact name recognition, but nvm...)
But after few hours without connection, call command also stops working and you only get "Data issues error".
daemontus said:
It's a bit more complicated. On my Moto, when I have internet, it uses Google Search App to search contacts and place calls. When I disable wifi and mobile data, call command still works, but uses some internal app (which, in my opinion, is better than G. Search in contact name recognition, but nvm...)
But after few hours without connection, call command also stops working and you only get "Data issues error".
Click to expand...
Click to collapse
there are two things recognizing voice stuff. Moto and google. if moto can't figure out what you said, it sends it to google (you can't tell any of thise is going on just looking at the phone). Moto describes all of this on their website somewehere. This is also why when you do certain commands, sometimes different windows show up. If moto recognized it, they launch their stuff to do the command, if it doesn't, then google tries to recognize it and then does what it does with that comamnd.
i think you can activate the touchless control, but won't get result of your search as not internet access.
Pure Nexus 7.1.2_r17, Beans Gapps June 10 Mini. I can't seem a way to enable Trusted Voice. I don't have the option under Settings>Security>SmartLock. I have tries to look under Settings>Google but there isn't anything there that I can see either. Looking around the web I see an issue identified by Google in February but nothing else. Has anyone seen this and is there a known resolution to the issue?
Thanks.
Trusted voice is not available on the Nexus 6
snowrelyt said:
Trusted voice is not available on the Nexus 6
Click to expand...
Click to collapse
Trusted Voice should not be available for any device. The BBC ran a programme a few weeks ago where a twin was able to break into his brother's bank account despite the "impenetrable" security. Anyone who trusts any bio security deserves to live in poverty for his/her stupidity.
snowrelyt said:
Trusted voice is not available on the Nexus 6
Click to expand...
Click to collapse
I wasn't aware. Is there a specific reason. Is it the hardware the limits the usability of this function. I though if one the OS had the feature it would carry along to all devices covered by that OS, especially in the case of a Nexus/Google device.
Thanks
monty.2016 said:
I wasn't aware. Is there a specific reason. Is it the hardware the limits the usability of this function. I though if one the OS had the feature it would carry along to all devices covered by that OS, especially in the case of a Nexus/Google device.
Thanks
Click to expand...
Click to collapse
From this page:
Trusted voice isn't available for Nexus 6.
Doesn't cite anything specific
Not to beat a dead horse here.....
I was messing around with an old US Cellular Note 2 with a CM 5.1.1 ROM on it. I found it has Trusted Voice and it works. There has to be a way to allow it on a Nexus 6.
PS: I understand the security aspect of it, but I'm slightly more concerned about going hands free when I drive.
Schiben said:
Not to beat a dead horse here.....
I was messing around with an old US Cellular Note 2 with a CM 5.1.1 ROM on it. I found it has Trusted Voice and it works. There has to be a way to allow it on a Nexus 6.
PS: I understand the security aspect of it, but I'm slightly more concerned about going hands free when I drive.
Click to expand...
Click to collapse
What's wrong with google assistant?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Nothing is wrong with Assistant. It's Trusted Voice (so I can unlock my phone by voice). Assistant responds to the hot word fine, but I still have to manually unlock the phone to do anything with Assistant.
Schiben said:
Nothing is wrong with Assistant. It's Trusted Voice (so I can unlock my phone by voice). Assistant responds to the hot word fine, but I still have to manually unlock the phone to do anything with Assistant.
Click to expand...
Click to collapse
To the best of my knowledge, trusted voice was removed, permanently. In the car, the fact that my various Bluetooth devices are present and set as trusted devices, assistant can just do its thing whether the screen is on or not.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
That's something I'm considering. My hangup with that is I tend to turn my Bluetooth of when I'm not using it and I don't actually have anything Bluetooth in my car. I'm considering NFC unlock too. Ultimately, the best option in my mind would be trusted voice.
So I was having all sort of reliability problems with Android Auto not recognizing some voice commands, not recognizing contact names, etc. It was inconsistent and sporadic (and appears it still is for a lot of users.) Extremely frustrating. I found things like "Send message to (contact)" or "Send text to (contact)" wouldn't be recognized most if not all the time but "Text (contact)" would. Go figure. At various points in the chain of commands Google would eventually say "Sorry I don't know how to help with that", again it was inconsistent when it would happen using the exact same voice commands. I finally found a chain of commands that would consistently get me to the last step of sending a messaging where Google asks "send it or change it?" But saying "send it" or "send" never worked, it always resulted in "Sorry I don't know how to help with that."
After spending many hours troubleshooting and then eventually someone in the Google forums suggested adding "PLEASE" Now I'm a polite person and I taught my kids to always say please. But given the context of driving my car, I think efficiency and user-friendliness trumps politeness in this circumstance, especially considering I'm talking to a computer (in lieu of typing on a keyboard) not talking to a person.
I couldn't believe it.
https://youtu.be/ZmbbcVQbQpM
So much wasted time!
Looks to be a language/localisation specific issue, if I'm honest, I couldn't understand what you were saying in the video first time round, so the minimal version of GA running in AA won't be able to either
x13 said:
Looks to be a language/localisation specific issue, if I'm honest, I couldn't understand what you were saying in the video first time round, so the minimal version of GA running in AA won't be able to either
Click to expand...
Click to collapse
So if I understand this right, you are saying the problem is I'm not speaking clearly enough??? That's pretty funny. Do you live near Seattle? You can come over and try speaking into it yourself, and I'll bet you a large sum of money you won't get it to work.
This is actually a bug confirmed by Google. https://productforums.google.com/d/msg/android-auto/UAAnywf312w/D-aTMLv5AgAJ
And there are other users experiencing the same problem.
jazee said:
So if I understand this right, you are saying the problem is I'm not speaking clearly enough??? That's pretty funny. Do you live near Seattle? You can come over and try speaking into it yourself, and I'll bet you a large sum of money you won't get it to work.
This is actually a bug confirmed by Google. https://productforums.google.com/d/msg/android-auto/UAAnywf312w/D-aTMLv5AgAJ
And there are other users experiencing the same problem.
Click to expand...
Click to collapse
A fix was pushed for the bug you linked, on 2018-09-26 it was confirmed that the fix had rolled out.
I am on a different continent, and use a different localisation, so it is unlikely that I would experience the same issue.
In your video, I noted the following points:
Your AA instance locale seems to be en_AU or similar, or at least, the TTS module used does
You pronounce "Harry" much the same as "hairy"
You say "send it", as opposed to "send" or "send message", which, in my testing, has a lower success rate
I'm speculating here, but I believe the device is not actually registering "send it" as the phrase "send it", however, "please send it" registers the "please", which is enough to trigger the send action
Your AA instance locale seems to be en_AU or similar, or at least, the TTS module used does
How would you tell that? Are you assuming that because of the voice's accent? Ha, did you not know you can change the accent of the voice from the default to a different accent or gender? It has nothing to do with changing language locality.
You pronounce "Harry" much the same as "hairy"
Sometimes it works sometimes it doesn't with "harry" but this is also the case with many other contact names. I don't expect it to be perfect and the point of my original message was pointing out the failure to recognize "Send" or "Send It" without "Please" The "Harry" issue is relatively insignificant to me for the purpose of this thread.
You say "send it", as opposed to "send" or "send message", which, in my testing, has a lower success rate
I of course have tried all three multiple times. It seems the case here, which I've seen many times over the years, is many people tend to assume their experience is the "right" one or in the "vast majority" From a software development standpoint, the goal is to make the software work for ALL users. The simple answer here is that there is a bug in the software that for whatever reason doesn't affect 100% of the user population but does affect some users such as myself.
Of the users that are experiencing the same problem, none have yet to determine a solution, which is probably only able to be implemented by Google in a future update. But for the users experiencing the issue, it is quite a major bug causing much frustration.
Based on reading hundreds of messages regarding Android Auto in multiple forums posted over the past 6 months, it appears Android Auto is more problematic relative to many other Google products I use which is very disappointing considering this particular product as a very beneficial use in my life relative to the other products (when it works.)
I have no idea what is going one w new look version and old versions of android auto. Either way, most commands or calling a contact, get driving directions or text someone are decli ed saying something like sorry, not sure how to do that or not know how to handle requests. Kinda frustrating and settings appear to be correct as I can see music apps, google maps etc.
Any suggestions or is it an issue somewhere else. Any other android phone and AA works fine w it whether new look version or old AA version.
Tia,
Ian B
Same problems here, Android Auto is borked big time on my fold but is still OK on my Pixel 3a. Problems are:-
1) When connected to my vehicles head unit it often disconnects for no reason
2) When I get a stable connection, and ask it to "navigate to xxxx" by voice it responds that it cannot do this "while in driving mode".
3) If I ask it to make a call or send a sms it responds "sorry I cant make calls yet" or "sorry I cant send texts yet"
4) After AA has been opened (even outside the car), Google assistant will no longer make calls or send texts via voice commands. Disabling the Google app, clearing the cache doing a restart brings the assistant functionality back but only until I use AA again.
The whole thing is a complete mess and given it is intended to be used WHILE DRIVING it is a very dangerous distraction - Google/ Samsung need to get on top of this or I can see them getting sued because they killed someone.
UPDATE: Iwas running a beta of google play services, when I uninstalled that and went back to the general release version, everything seems to be working OK with Android Auto.