[Q] Google voice recognition over distance - Android Q&A, Help & Troubleshooting

Hi all,
I´m new to this forum and hope that i put the thread into the correct subsection.
I have a question regarding google´s voice recognition, which I use together with tasker, autovoice and a lg g pad 7.0 (currently no root) for home automation. My problem is that the tablet recognizes the "ok google" phrase at almost every distance in my room and starts the voice search, but all following words/commands are ignored, when I am more than half a meter away. When holding the tablet erverything works as it should.
After lots of internet research it seems that I am alone with my problem or maybe I searched for the wrong terms.
So hopefully you can help me.
Is there a solution that makes the voice recognition work over some distance (maybe 1-5 meters)?
Note:
I already checked the recording quality, which is good.
There is no background noise in my room.
"ok google" is recognized, no matter where I am standing.
My suspicion is that it has to do with android´s noise reduction feature, which seems to filter my voice by mistake, but I am not sure as I haven´t found a way to disable it.
BR
David

Related

Android Voice Actions not hearing voice

I seem to be having a problem with voice actions.
When I use an app, let's say Google Voice Search, the mic comes up to accept speech but almost immediately it says "no speech heard".
I have to start it again and start speaking quickly so it won't time out.
Vlingo works fine and gives me plenty of time.
What could be affecting this?
Thanks
Jeff

Voice recognition not working

I'm not sure what's causing this. It seems to have started when I first rooted the phone. Voice recognition isn't working. When I try to use google search the circle around the microphone icon will move, but the icon doesn't turn red as it does when it recognizes voice. If I cup my hands around the microphone on the phone and pretty much yell, sometimes I can get it to work. Other times I can't. Tried another test, downloaded a voice recording app and when I recorded, I could hear my voice but it was INCREDIBLY quiet. I couldn't make out what I was saying at full volume. I have had no complaints about my voice when on phone calls. Does anyone have any idea what this is, or what a fix would be? I'm rooted currently, have tried multiple different roms with the same outcome. Am I just missing a setting somewhere?

[Q] Voice Accuracy Tips?

Are there any tips for the voice search? Its a bit hit and miss for me, have a few questions:
1. Is there a textbook way to pronounce "OK Google", that will make it detect all the time? I find that my way of pronouncing it, it gets detected only 70% of the time.
2. How loud and how close should we speak to the watch? I am assuming that if we speak too loud too close the mic will pick up distortion instead of the voice?
3. Is the Voice Model from the phone used? I find that the Phone is a lot more accurate to pick up my "Ok Google", then the watch.

Is it possible to make incoming hangouts call trigger servo?

Hello
I'm in the middle of building a funny little hangouts box and although I've done my research on this topic I couldn't find any concrete answers - and would like to hear opinions of people in the know before putting in more time and money into this project.
Would it be possible to trigger a motor when the device receives an incoming hangouts video call? (the servo motor of a music box movement - to be precise)
I know it would be possible via tasker and arduino for normal voice calls, but from what I read hangouts events are quite different.
I'd appreciate any kind of input.
Best
Emre

S-Voice and Bluetooth (on but not connected)

Hey All,
So, I've been searching all over for an answer to this, I've found a lot of information about S-Voice's problems being used over a bluetooth device but I haven't been able to find any direct discussion of the issue I'm experiencing.
What I've found is that when I have S-Voice's voice wake-up feature enabled, it'll work totally fine with bluetooth off. However, as soon as I toggle bluetooth on the wake-up feature just completely stops working. I don't even need to be connected to a device, as long as bluetooth is on S-Voice Wake-Up does not work. I can manually launch S-Voice and it will hear me just fine, but saying the wake-up command does nothing. As soon as I toggle bluetooth back off, it'll wake up again just fine. I do get that with a bluetooth device connected the microphone on the device needs to be active, so I could understand if this was happening while I was paired with a headset or something, but it seems really odd to me that just having bluetooth on at all would disable the wake-up command feature.
I did try Ok Google and found that it works whether bluetooth is on or off, but I really like the increased functionality that S-Voice offers and I think that for the most part the updates Samsung has done on it are great, so I'd like to get this working if possible.
Has anyone else experienced this, either on the Note 4 or on any of the other Galaxy devices? Anyone have any ideas or solutions?
Thanks!
I'm having the same issue with svoice, thought it was just the bluetooth in the car at first til I red your post
Widespread
I've got exactly the same problem.... Lovely new note 4 which is forcing me to use my hands on the phone whilst driving... Samsung need to think about this.
Apparently an issue for a few years due to Bluetooth /svoice conflicts, but not acceptable to leave it unaddressed.
I can still use my car system to skip music tracks on the phone, or dial numbers from the car stereo touch screen, but surely this is one of the most valuable areas for voice control?!
Bluetooth off then everything works fine, but Bluetooth on and svoice just fails. No wake up or voice recognition.
I don't use a headset, and the car doesn't have an inbuilt mic, so phone mic is used for calls (which is still fine incidentally.. Only svoice which is screwed.)
Looking forward to someone finding a simple solution to this, as I have spent hours in the menus trying to make a difference but Samsung might have just let us down I'm afraid... And if that's the case then I look forward to hearing them fix it, and update our ware to get everyone on track again.
Resolved and simple
After much fckin about I managed to get this sorted and the answer is simple..... You can't have both apps always trying to recognise the voice all the time.
Go to the settings for ok Google and voice detection then always on... Uncheck it and suddenly svoice is working again... On my way to the car for final checking now,but preliminary checking says all should be good.
Nope
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
When driving, set to hands free mode, this allows use of svoice on bluetooth
Ooof said:
Ok... It works until the system is fully connected.
As soon as the connection is made then the handset microphone switches off again.
Note 4 s voice is officially dangerous to Road users and Samsung are ultimately proving themselves irresponsible for creating a system which forces use of hand and eye coordination when in Bluetooth and car mode.... Seriously Samsung... Sort this sht out.
Click to expand...
Click to collapse
Note 4 and above have it listed as car mode.
svoice works perfectly with blue tooth when car mode is enabled.
Set it up at home before you use it the first time.

Categories

Resources