Ever since I've upgraded to Lollipop I've been having an issue with Moto Voice handoff to Google Now. Quite often once the command is received by GNow it doesn't catch the words and says "Didn't catch that". Am I being forced of this phone if I strongly use this feature?
Related
I have a moto droid which is no longer active with Verizon(that $30 a month was getting to be a bit much) and would like to use google voice to make calls. On install, it gives an option to use google voice for calls, but when I actually try to make one it routes me to Verizon's "we're sorry, this phone isn't in service" message.
I understand that this isn't really the intended use, but I can use google talk to make a call from my PC, why will it not let me use the same service from my droid. Is this a quirk of the device or a limitation from Verizon or google?
I'm using the latest Bugless Beast, if it makes a difference, though I have also tried with CM7 build 3 and CM 6.1.2.
--------------------edit------------------
Ah, nevermind. I figured it out myself. This is not possible with google voice alone, but I grabbed Sipdroid off the market. When paired with a google voice account(set to ring to gtalk as well as any other phone numbers) works rather well as a wifi phone. There is a bit of a delay sometimes in making a call, but no serious problems. call quality is quite good.
Whenever I get a phone call while not on WiFi the below image pops up and causes the screen to lock. How do I get rid of it???
No ideas?
Until Verizon's LTE calling update some time this fall, the Moto X can't support voice and data at the same time.
No such problem on AT&T....
Just like Chris said, VZW needs to release a sw update so we can have Advance Calling(http://phandroid.com/2014/09/20/verizon-moto-x-launch-without-simultaneous-voice-data/). Until then, you have to be on wifi if you want to simultaneously talk and surf...
I understand that there needs to be an update, is there anyway to get rid of that message? It screws up answering and hanging up calls. Thanks
This "feature" is one of the reasons I switched back to the HTC One M8... Not being able to use Data and Voice at the same time is so 10 years ago - no clue why the hell they took a step back like this. I really like the moto X 2014, but with that "feature" and bluetooth not working properly (stuttering when playing music) I just can't use the device. - Additionally root/native tethering without paying for it are show stoppers. All stuff I can do with the m8, hopefully the Nexus 6 isn't impeded by the same shortcomings of the moto x
I've noticed everything you said as well. I'm going to give the X to my wife to replace her GS4 and just get the nexus. When the X was ordered they hadn't announced that it would be on VZW yet...
Hi all
I am running lollipop and was wondering if I should use the moto custom voice to wake device with screen off, or use the one built into lollipop in Google now.
Is one better than the other ?
Besides being able to use a custom phrase on moto voice ?
I remember reading somewhere that the Google works better cuz its direct.
Any feedback would be much appreciated
Thanks and have a great weekend
captiv123 said:
Hi all
I am running lollipop and was wondering if I should use the moto custom voice to wake device with screen off, or use the one built into lollipop in Google now.
Is one better than the other ?
Besides being able to use a custom phrase on moto voice ?
I remember reading somewhere that the Google works better cuz its direct.
Any feedback would be much appreciated
Thanks and have a great weekend
Click to expand...
Click to collapse
Try them both, pick which one you like better.
Google Now can't wake your device unless it is charging.
Only Moto voice will work with the screen off of its not charging.
Mayze23 said:
Only Moto voice will work with the screen off of its not charging.
Click to expand...
Click to collapse
That's not correct. Lollipop has it built into the OS. Check under google now / settings and voice (voice detection). It's there. Screen off as well. And I think it works better than the moto x one after testing.
I'm well aware of it supposedly being built into lollipop. But it doesn't work with the screen off on the moto X unless its being charged. I've disabled moto voice, enabled google now voice detection from any screen and turned the screen off. Said "OK Google" nothing happens. There have been a few of us here that have tried it and it doesn't work. It does work, though, when it's being charged. If you're able to get it to work please let us know how you did it because I would rather use Google now.
My Google settings on CM 12. Does not work unless plugged in for me.
Haha my bad. I also have a nexus 6 so when I went to my moto X I assumed that it was the same. And I guess I tested it with the screen on. And alas, upon trying it, you are right. It doesn't work when the screen is off. Oops
This thread is close to the question I was researching but my question is more generic. I just got my new MotoX a couple days ago and I'm confused, what is the difference between Google Now or the Moto Voice apps? My old phone was a MotoX 2013 so I'm used to using Google Now for everything, now my new X seems to have two apps that do the same thing? What's the deal?
JoeHockey said:
This thread is close to the question I was researching but my question is more generic. I just got my new MotoX a couple days ago and I'm confused, what is the difference between Google Now or the Moto Voice apps? My old phone was a MotoX 2013 so I'm used to using Google Now for everything, now my new X seems to have two apps that do the same thing? What's the deal?
Click to expand...
Click to collapse
Moto Voice can wake up your phone, which Google Now cannot. Moto Voice can read your your new notifications (either on command, or during a set period of time), Google Now cannot. Most other voice commands are heard by Moto Voice, and then passed over to Google Now. The two don't really overlap in their abilities. They work together to give you the best of both worlds.
imaginaryenemy said:
Moto Voice can wake up your phone, which Google Now cannot. Moto Voice can read your your new notifications (either on command, or during a set period of time), Google Now cannot. Most other voice commands are heard by Moto Voice, and then passed over to Google Now. The two don't really overlap in their abilities. They work together to give you the best of both worlds.
Click to expand...
Click to collapse
Oh, now I get it! Thanks!
I have a Moto X 2014 XT1095 that is experiencing a strange issue, the Moto Voice Launch Phrase option keeps unchecking itself at random times of its own volition. Initially I thought it was one of the modifications I had made to the software of the phone, however this past weekend I returned my phone to full stock
System Version: 22.21.11.victara_tmp.tmp.en.US
Kernel Version: 3.4.42-gd7d30ea [email protected] #1
Build Number: LXE22.46-11
and am still experiencing the issue. I find that even if I reboot the phone, the option does not magically reenable itself and the result is that the phone is not listening for its "Ok Google now" hot phrase. Note that this is a full stock build and it has not been rooted, only the bootloader unlocked. I do have all of my normal programs installed that do not require root access, notably Trigger, but do not have any voice commands defined in that app, only location based triggers.
Additionally the "OK Google" detection is set to be hot from the app, but not from any screen and not as a "trusted voice" where it will unlock the device. There also is no voice model trained within google's application.
I cannot pinpoint any particular behavior that causes the launch phrase detection to disengage, however I usually don't notice it until the hot phrase doesn't work. I can upload a log if that would be helpful, but since I can't get the behavior to reproduce on command, I'm not sure how helpful this might be.
linuxbaby03 said:
I have a Moto X 2014 XT1095 that is experiencing a strange issue, the Moto Voice Launch Phrase option keeps unchecking itself at random times of its own volition. Initially I thought it was one of the modifications I had made to the software of the phone, however this past weekend I returned my phone to full stock
System Version: 22.21.11.victara_tmp.tmp.en.US
Kernel Version: 3.4.42-gd7d30ea [email protected] #1
Build Number: LXE22.46-11
and am still experiencing the issue. I find that even if I reboot the phone, the option does not magically reenable itself and the result is that the phone is not listening for its "Ok Google now" hot phrase. Note that this is a full stock build and it has not been rooted, only the bootloader unlocked. I do have all of my normal programs installed that do not require root access, notably Trigger, but do not have any voice commands defined in that app, only location based triggers.
Additionally the "OK Google" detection is set to be hot from the app, but not from any screen and not as a "trusted voice" where it will unlock the device. There also is no voice model trained within google's application.
I cannot pinpoint any particular behavior that causes the launch phrase detection to disengage, however I usually don't notice it until the hot phrase doesn't work. I can upload a log if that would be helpful, but since I can't get the behavior to reproduce on command, I'm not sure how helpful this might be.
Click to expand...
Click to collapse
The exact same thing is happening with mine too.
linuxbaby03 said:
I have a Moto X 2014 XT1095 that is experiencing a strange issue, the Moto Voice Launch Phrase option keeps unchecking itself at random times of its own volition. Initially I thought it was one of the modifications I had made to the software of the phone, however this past weekend I returned my phone to full stock
System Version: 22.21.11.victara_tmp.tmp.en.US
Kernel Version: 3.4.42-gd7d30ea [email protected] #1
Build Number: LXE22.46-11
and am still experiencing the issue. I find that even if I reboot the phone, the option does not magically reenable itself and the result is that the phone is not listening for its "Ok Google now" hot phrase. Note that this is a full stock build and it has not been rooted, only the bootloader unlocked. I do have all of my normal programs installed that do not require root access, notably Trigger, but do not have any voice commands defined in that app, only location based triggers.
Additionally the "OK Google" detection is set to be hot from the app, but not from any screen and not as a "trusted voice" where it will unlock the device. There also is no voice model trained within google's application.
I cannot pinpoint any particular behavior that causes the launch phrase detection to disengage, however I usually don't notice it until the hot phrase doesn't work. I can upload a log if that would be helpful, but since I can't get the behavior to reproduce on command, I'm not sure how helpful this might be.
Click to expand...
Click to collapse
Been having the same problem for the past month or two. Pure Edition on 4.4.4, bootloader unlocked, rooted. No other mods, no Xposed. My Ok Google settings mirror yours. When I notice the problem, I cannot recheck voice detection in the Moto app until I reboot first.
https://forums.motorola.com/posts/206a6fa1da
There have been some theories over on the Motorola forums. No fixes though.
me too, running 5.0 stock on XT1092 EU.
I thought it was the crap memory management which is killing random app to free memory, and in fact if I check on running apps i can't see the "Moto" app.
After a reboot everything is ok
Is anyone else constantly having problems with the voice recognition saying it can't reach google? My phone is a Nexus 5 on stock 5.1.1. Sometimes it fails immediately, sometime it transcribes but still supposedly can't reach google. Every time it's connected to my phone, and my phone has a working internet connection. For example, this morning, my watch alerted me to a new hangouts message, I hit the reply button, and it said "unable to reach google" after it transcribed what I had actually said. The transcription and then fail happens a lot when using autowear as well.
Yep. I have the same issue since very beginning. Any clues?
Yep same issue here, rebooting the watch sometimes helps but it's just very buggy