I'm trying to use voice actions since Google added spanish support. It works fine in the sense that it recognizes commands easy enough. But when I tell it to "Call whatever" sometimes it will look up a contact in my contacts but some times, to my infinite annoyance, it will show some random person I'm assuming it found on the internet or google or god knows what.
Any idea how this is happening??
Thanks
So I say "text..." and Google now prepares my message but still makes me hit "send message" on the screen. I just want it to send without me touching it help?
Sent from my XT1056 using Tapatalk 2
I don't think there is a way, the fault is on Google now and not touchless controls. I was a little bummed about this to, with my sgs3 I was able to send texts through voice command and say "send"... Though, vice command was pretty useless on it, if I wanted to text anything longer than 4 words it would take me 10 tries to get it right... At least with the moto x, it gets it deadnuts 99% of the time. For now, I'll take the trade off of having to do one click and it actually working. Hopefully some day it will work the exact way that we want it... Until then, I am content.
Sent from my XT1058 using XDA Premium 4 mobile app
Semi-related but didn't want to start another thread about touchless control.
When using touchless control to send a text, I assume that because it is being routed through GoogleNow, the actual text that is sent out doesn't save in the proper threaded message history? Is there a setting or a way to keep the text in a running conversation?
I'm on Sprint stock.
Mine gets added to existing text conversions... Though, I haven't used it since I updated to hangouts 2.0 and I think there may be a bug when using hangouts as default SMS.
AT&T Moto X rocking 4.4
deanwoof said:
When using touchless control to send a text, I assume that because it is being routed through Google Now, the actual text that is sent out doesn't save in the proper threaded message history? Is there a setting or a way to keep the text in a running conversation?
I'm on Sprint stock.
Click to expand...
Click to collapse
On Verizon stock it shows up in my threaded message history. Strange.
it's not every time.. id say a good half of them don't show up.
deanwoof said:
it's not every time.. id say a good half of them don't show up.
Click to expand...
Click to collapse
the commands are being ran by different things. Don't know which one is putting it in the thread and which one isn't. But from the moto site, it says that moto trys to run any command you say into google now, if it recognizes it, it acts on it, if it doesn't recognize it, it sends it to google now to recognize it. Basically, even though it looks like google now is the app running, after you say something, moto trys to recognize the voice command. So sometimes moto recognizes it and sends the text itself, sometimes it doesn't and sends it to google services that then sends the text. You can try saying like send text message instead and see if that always sends it to google or always sends it to moto. Like i said, idk which system is the one that is showing the text correctly, but if it is google, then saying something that moto won't recognize but google will should solve your problem. If it is moto that is running the command correctly, than i guess you just have to be extremely clear when saying "text" for moto to pick it up.
pathtologos said:
So I say "text..." and Google now prepares my message but still makes me hit "send message" on the screen. I just want it to send without me touching it help?
Click to expand...
Click to collapse
I originally had the same experience; however, this behaviour _just_ changed for me over the past couple of days. As of today, when I ask Google Now to send a text, it performs all steps (from beginning to send the text to actually sending the text) via voice prompts. I assume that this is thanks to the recent updates that have been sent out over the past couple of days. Regardless, WHOO HOO!
I have xvoice+ xposed module installed and it does a great job at intercepting Google Voice text messages and routing them to the stock SMS app. However, they are not read in the driving mode.
I tried to find out if this is a common issue for all moto x users, but got no response in the app's thread.
Maybe this is expected behavior, since these are not Verizon text messages, but rather rerouted google voice text messages.
I just wanted to check if I'm alone with this issue, or if it affects everybody the same way.
... Moto X VZW DE ...
Hi,
I was wondering if anyone has encountered this nonsense issue:
When trying to send a sms or Whastapp message with ok google assistant, when you specify who you want to send it and what is the message, then the watch forces you to press the screen for send or cancel the message. Whats the use of saying everything out loud if you need to confirm the sending of the message with your finger?? If you are using voice commands it's because you cannot press the screen!
When adding a new reminder it does not do that. It shows a button with an x and a circle counter line so if you don't stop it, it will save the reminder. That really makes sense and its the way I usuallty send messages on wear 1.5.
Is it the Ok Google app?
Thanks!!
I thought it was confirming it's transcription of my message
roebling said:
I thought it was confirming it's transcription of my message
Click to expand...
Click to collapse
Yes of course, but it does not make any sense to have to press the screen to send it. When talking to the watch it´s because you can not press the watch screen. For example: biking. I think some developers design and develope software that they don´t use and that´s a shame.
I am using Android Auto with my 2017 Honda Pilot and Galaxy S7. Maps, music, phone calls work fine. OK Google works great. I am encountering a problem consistently with replying to text messages. A text message would show up, I would play the message. Google asks me if I want to reply. I say yes. But it keeps asking me "do you want to reply" or "I am done" repeatedly. For some reason, it's not listening/hearing my answer. Anyone run into this?