Related
http://code.google.com/p/android/issues/detail?id=1181
The voice dialer in the Android platform is so incredibly flawed yet it doesn't seem as if they notice/care. This issue needs to be starred by more people for it to become something they will look at IMO.
Why should a voice dialer require user input? Isn't the point of a voice dialer such that you can use it by simply pressing the button on your BT headset and instructing the application to choose for you?
Thanks for your time.
Bump. Please support. This issue needs to be resolved!
Isn't this function available in Donut??
What feature? Voice search? Yes, but it requires an internet connection to work. So for those of us that don't have a data plan, it's worthless. Also, the button on a BT headset will activate the voice dialer, not voice search so we still have the same issue.
BUMPED. Honestly, why is it so hard just to open the link and star the issue?
Going to keep on bumping this no matter how long it takes for people to help.
Looks like this is working a little. Got 6 more stars over the weekend! C'mon people, it's just TWO clicks!
rickytenzer said:
why is it so hard just to open the link and star the issue?
Click to expand...
Click to collapse
Why is it so hard to write a decent title to a post?
brucemcl said:
Why is it so hard to write a decent title to a post?
Click to expand...
Click to collapse
Because I didn't have a PR man in charge like I do now, Bruce.
Ricky i completely agree with you but I starred that defect a day or two after I got my phone and tried the flawed voice dialing system.
I have never in my life known a person who actually uses a Voice Dialer. As far as I'm concerned they can remove it from the OS entirely, I'd rather that Google devotes their resources to something useful.
chefgon said:
I have never in my life known a person who actually uses a Voice Dialer. As far as I'm concerned they can remove it from the OS entirely, I'd rather that Google devotes their resources to something useful.
Click to expand...
Click to collapse
You happen to be one of the lucky ones who DOESN'T live in an area where headsets are required by law while driving. If a cop so much as sees a phone in my hand, I can get a $300 ticket.
For us, it's absolutely imperative. I can't really explain to a cop that Android requires me to input my selection when using the Voice Dialer.
So please, for us unlucky people, give us 30 seconds of your time and star the issue.
Thank you
Bump bump bump bump
This would be so much easier if a mod just made this a sticky...
Getting more and more support every day! Thanks guys
Its an app I never used, and probly never will, but ill star it cause I'm a nice guy.
i have no problems with this on donut? If i use google voice search it is perfect gets exactly what i ask for, Also the voice dial works fine? Are you shouting at the phone?
bonesy said:
i have no problems with this on donut? If i use google voice search it is perfect gets exactly what i ask for, Also the voice dial works fine? Are you shouting at the phone?
Click to expand...
Click to collapse
+1 works for me ok too. No issues.
cardiak said:
+1 works for me ok too. No issues.
Click to expand...
Click to collapse
So you guys do not have to click something on the phone when using the voice dialer? We are not saying that the voice recognition does work we are saying that it is not completely hands free.
Here's a Quote from the defect that accurately describes the problem.
http://code.google.com/p/android/issues/detail?id=1181 said:
Requiring the user to tap on the phone to confirm the function of the voice
dialer reduces the desired functionality. For example, if when wearing a
hands-free device while driving, one tries to access voicemail, the
following process is required:
1. Unlock handset.
2. Access the voice dialer via handset.
3. Visual prompt for using voice dialer
4. Speak "Call voicemail."
5. Visual prompt: "Call voicemail, call voicemail mobile"
6. Select voicemail option
7. Dials voicemail.
In an ideal voice dialer, the process might look something like this:
1. Unlock not required.
2. Access the voice dialer via handsfree device (e.g., long press on
headset "answer button")
3. Aural prompt: "Say a command."
4. Speak "Call Voicemail"
5. Aural prompt "Would you like to call voicemail?"
6. Speak "Yes/No"
7. Aural prompt "dialing voicemail"
Click to expand...
Click to collapse
works with my ps3 bluetooth headset
I know this has been discussed with other devices, but as far as I can see, no one yet has brought this for the S4, I can't tell you if it worked before I de-bloated it on Monday, but now that I needed the S Voice it opens but once you give the command it gives the sound that says that it gets the command, but then the Screen goes black for up to 10 seconds and then it pops up the error saying that S Voice stopped working.
Like I said I never used it before, so I don't really know if after the command I give it suppose to say something back to me confirming it and then does the magic, so I have doubts if what is really failing is S Voice or the Speech App, I already cleared all data and cache for S Voice, Google Text To Speech and Samsung Text to Speech, but nothing works.
Anybody with the same issue or know how to fix this? Thanks.
erasat said:
I know this has been discussed with other devices, but as far as I can see, no one yet has brought this for the S4, I can't tell you if it worked before I de-bloated it on Monday, but now that I needed the S Voice it opens but once you give the command it gives the sound that says that it gets the command, but then the Screen goes black for up to 10 seconds and then it pops up the error saying that S Voice stopped working.
Like I said I never used it before, so I don't really know if after the command I give it suppose to say something back to me confirming it and then does the magic, so I have doubts if what is really failing is S Voice or the Speech App, I already cleared all data and cache for S Voice, Google Text To Speech and Samsung Text to Speech, but nothing works.
Anybody with the same issue or know how to fix this? Thanks.
Click to expand...
Click to collapse
I had the same exact issue... Possibly because you removed ChatOn and ChatOnV.... Its required in one of the voice command menus which probably blew it up.
Only way is to download Kies and do a Kies restore. Thats how I got it back working.
Lag Reduction Guide in General section will tell you how its done.
Thanks for the info, I was guessing that Chat on was the issue... however, for me reset to factory is not an option as of now, I really don't use the S Voice, I was just testing it, and if in order to get this back to work, I need to reset and set again all my apps and settings in general, I better not do it. I even prefer just to uninstall S Voice for now until I'm force to do a reset.
Thanks anyway.
Truthfully, for my restore and initialization through keys, my apps were still there after I restored.
Not sure if this will be your case but you can try it.
Thanks, after reading your experience I got the courage to do it myself and for my surprise, there were all my apps and settings, and there I have S Voice back. Thanks a lot.
As the title says, when I do a search using ok google now, I no longer get voice results back.
Asking what time is it or do I need an umbrella only returns text search results.
Any idea?
My phone is completely stock, the only thing I have done is unlocked the bootloader.
FSXv13 said:
As the title says, when I do a search using ok google now, I no longer get voice results back.
Asking what time is it or do I need an umbrella only returns text search results.
Any idea?
My phone is completely stock, the only thing I have done is unlocked the bootloader.
Click to expand...
Click to collapse
Isn't there a setting for touchless control that sets when you want a voice reply
Sent on my Moto X
If there is, I don't know.
I unlocked my dev ed on Monday and it did a factory wipe. I just tried touchless controls for the first time since then and I'm not getting any voice responses.
FSXv13 said:
If there is, I don't know.
I unlocked my dev ed on Monday and it did a factory wipe. I just tried touchless controls for the first time since then and I'm not getting any voice responses.
Click to expand...
Click to collapse
That's the default settings, it only replies when speech is appropriate I.e. reading emails, text messages but I do remember seeing the settings somewhere that gives you the ability of changing this. I don't use touchless control, actually i removed it completely
Sent on my Moto X
FSXv13 said:
As the title says, when I do a search using ok google now, I no longer get voice results back.
Asking what time is it or do I need an umbrella only returns text search results.
Any idea?
My phone is completely stock, the only thing I have done is unlocked the bootloader.
Click to expand...
Click to collapse
Try this:
Go into Google Now.
Tap the 3 dot menu and tap settings.
Find the Voice Section and go into that
Make sure your language is English(US) (Not sure if others work, I haven't tried)
Make sure speech output is set to always on
alu0506 said:
Try this:
Go into Google Now.
Tap the 3 dot menu and tap settings.
Find the Voice Section and go into that
Make sure your language is English(US) (Not sure if others work, I haven't tried)
Make sure speech output is set to always on
Click to expand...
Click to collapse
I have tried that, I even downloaded the offline voice recognition.
I've reset/uninstalled updates on google play services and google search, didn't work.
Just did a factory reset and still not working. I'm not sure what it is. I'm going to have to call Motorola, all I did was unlock the bootloader but I didn't root or do anything extra to it.
@flashallthetime I am using appropriate questions. If you ask the time it should say the time out loud, and if you ask if you need an umbrella it should tell you the weather. As of now it googles "need an umbrella" and displays results.
EDIT: AAAAAaaaaaaaaaand of course it is now just magically working. Thanks everyone for your help. It didn't work after the factory reset and now it just magically does...
FSXv13 said:
I have tried that, I even downloaded the offline voice recognition.
I've reset/uninstalled updates on google play services and google search, didn't work.
Just did a factory reset and still not working. I'm not sure what it is. I'm going to have to call Motorola, all I did was unlock the bootloader but I didn't root or do anything extra to it.
@flashallthetime I am using appropriate questions. If you ask the time it should say the time out loud, and if you ask if you need an umbrella it should tell you the weather. As of now it googles "need an umbrella" and displays results.
EDIT: AAAAAaaaaaaaaaand of course it is now just magically working. Thanks everyone for your help. It didn't work after the factory reset and now it just magically does...
Click to expand...
Click to collapse
You're a magician, abra cad Abra or something like that, my magically powers made touchless controls disappear
Up here in Canada and no we don't live in igloo's, touchless control did a quarter if what it is capable of, so bye bye
Sent on my Moto X
Sounds like it didn't know your location, it doesn't like to answer any weather, location or time based questions if it doesn't know where you are.
I have moto voice enabled and it works wonderfully as long as the phone is unlocked, but if I check the Google commands over lock screen button, things don't work properly.
If I ask it to check the weather or something like that, it works fine, but if I ask it to make a reminder, it will go through all the steps then when I tell it to save and it will confirm that it's saving... But it never actually saves the reminder. If i actually click the save button it will then save it, but that defeats the whole purpose of it being hands free. This is on stock Feb. security update. It's always done this. Anybody else have this problem or know how to fix it? Moto voice is enabled in accessibility if that matters.
elite001mm said:
I have moto voice enabled and it works wonderfully as long as the phone is unlocked, but if I check the Google commands over lock screen button, things don't work properly.
If I ask it to check the weather or something like that, it works fine, but if I ask it to make a reminder, it will go through all the steps then when I tell it to save and it will confirm that it's saving... But it never actually saves the reminder. If i actually click the save button it will then save it, but that defeats the whole purpose of it being hands free. This is on stock Feb. security update. It's always done this. Anybody else have this problem or know how to fix it? Moto voice is enabled in accessibility if that matters.
Click to expand...
Click to collapse
Have had this issue for some time now, really irritating. I encounter this most occasions when attempting to set a timer and alarm.
Another issue I keep getting is that when the device is locked, the first command will be be carried out, but a 2nd command will return a failed sound - as if the command was not recognized, even though it was. I then have to unlock the device to continue making commands.
Anyone else had this issue?
krohme said:
Have had this issue for some time now, really irritating. I encounter this most occasions when attempting to set a timer and alarm.
Another issue I keep getting is that when the device is locked, the first command will be be carried out, but a 2nd command will return a failed sound - as if the command was not recognized, even though it was. I then have to unlock the device to continue making commands.
Anyone else had this issue?
Click to expand...
Click to collapse
I have Moto Voice on and OK Google off.
Moto Voice still works for all the listed commands "call X", "post to Facebok", "play on Youtube", "take a photo", "take a selfie". (both with screen on and off)
However it seems that Google commands have stopped working. I used to say "create event" and then I could dictate a calendar event, "set an alarm", "navigate me/drive to..."
All these commands seem they are not working anymore. Moreover, it seems that it can't listen to me or show a previous search.
It's a mess. It's like I just can use only the commands from the Moto Voice list.
Can anyone confirm that the previous commands work for them?
Corduroy-21 said:
I have Moto Voice on and OK Google off.
Moto Voice still works for all the listed commands "call X", "post to Facebok", "play on Youtube", "take a photo", "take a selfie". (both with screen on and off)
However it seems that Google commands have stopped working. I used to say "create event" and then I could dictate a calendar event, "set an alarm", "navigate me/drive to..."
All these commands seem they are not working anymore. Moreover, it seems that it can't listen to me or show a previous search.
It's a mess. It's like I just can use only the commands from the Moto Voice list.
Can anyone confirm that the previous commands work for them?
Click to expand...
Click to collapse
Yeah that's the problem I have. The Google commands have never worked for me through moto voice. BUT if I tell it to do something like "check the weather", it'll do that. It's almost like the Google or moto app needs some kind of storage or access permission to actually ~save~ reminders, events, alarms, etc. I don't know why it does this but I have a hard time believing that we are the only ones having this problem. Creating reminders without having to unlock the phone or use "ok Google" was one of the reasons I liked this phone to begin with and it doesn't even work.
Sent from my XT1575 using XDA Labs
Today is the first time, since the Google Assistant update, that I've really text anyone.... I tend to use the voice to text feature on my keyboard for long text/posts. So when I use SwiftKey, I press the microphone and it brings up the "Google voice to text" and I'll say what I want, but when I look at it - t's in there 2 or 3 times?? I noticed it first in Facebook Messenger, then when texting my wife.....So it's not just one app.
I just switched to Gboard (Google Keyboard) and it does the same thing.... I switched to Swype and it's fine, but Swype uses it's own voice to text software (Dragon) instead of Google.
Like I said, this just started today and I'm not sure if it has to do with the Google Assistant update, or just something screwy is going on with Google?
Anyone else getting this?
[UPDATE]
I've found several people having this same issue:
http://androidforums.com/threads/vo...ce-to-text-keeps-repeating-sentences.1124892/
[UPDATE]
Well, it seems to have fixed itself over-night?
A little more insight into what it was actually doing....
When I would press the microphone (on my keyboard) and speak, it would put three variations of what you said in the field you were adding text to....For example, when I said the phrase "Testing one (comma) two (period).....It would come out like this:
Testing one, two. Testing 1 comma 2 period testing 1, 2.
Click to expand...
Click to collapse
The error seems to be that it is typing out every single possible interpretation of what you're saying instead of the most likely one.
Like I said, it seems to be fixed now? But I am in a different location now (work vs home). I'll have to check it this evening too.
tele_jas said:
[UPDATE]
I've found several people having this same issue:
Voice to Text keeps repeating voice-to-text keeps repeating sentences
http://androidforums.com/threads/vo...ce-to-text-keeps-repeating-sentences.1124892/
Click to expand...
Click to collapse
Thanks for finding the thread where other people also had that issue. Various complaints were popping up in ROM threads for other devices and it's NOT a ROM issue.
Replied by mistake to this topic.....Disregard this reply :highfive: