Hi everyone,
I have an issue with Autovoice Continuous vocal recognition (a great tasker plugin, which basically makes your phone listening to you at all time - or at the times you want if you're concerned about battery usage) since I updated to KitKat a few days ago.
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Thanks
nuts77 said:
Hi everyone,
I have an issue with Autovoice Continuous vocal recognition (a great tasker plugin, which basically makes your phone listening to you at all time - or at the times you want if you're concerned about battery usage) since I updated to KitKat a few days ago.
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Thanks
Click to expand...
Click to collapse
It might help you: http://www.youtube.com/user/taskertutorials/videos
nuts77 said:
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Click to expand...
Click to collapse
I have/had the same issue and it took me some time to dig it down.
On my Note 10.1 2014 LTE it is caused by the latest update of Google search which I installed yesterday via PlayStore.
After reverting that (luckily my device is rooted and I use Titanium backup), the beep is gone.
So somehow, Google has introduced that and AutoVoice can (yet) not disable it.
akxak said:
I have/had the same issue and it took me some time to dig it down.
On my Note 10.1 2014 LTE it is caused by the latest update of Google search which I installed yesterday via PlayStore.
After reverting that (luckily my device is rooted and I use Titanium backup), the beep is gone.
So somehow, Google has introduced that and AutoVoice can (yet) not disable it.
Click to expand...
Click to collapse
Yes, solved it by reverting to an older version of google search as well and there is no other way around yet.
The problem is that in the latest versions of GS, the "beep" notification sound is pushed through the media sound channel instead of the notification one (which autovoice is muting and unmuting, since continuous mode is basically just a voice search triggered every 5 seconds).
I have the same problem. Currently, there is no other solution then reverting google search to previous version. Hopefully next autovoice update will solve this issue.
There is already an update.
Unfortunately, the change of google in the search function (together with the update) causes parallel running apps using the speakers to be muted every 5 secs for a moment. That is anoying (eg. Internet radio).
Yes, there is new version, I was using an old one. It's all good now.
Послато са LG-D802
After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.
intothevoid said:
After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.
Click to expand...
Click to collapse
I've been experiencing this to but only when I'm driving in my truck with the radio on.
neopolotin75 said:
I've been experiencing this to but only when I'm driving in my truck with the radio on.
Click to expand...
Click to collapse
Good to know I am not the only one!
Delete the app Data , start fresh.
Dxtra said:
Delete the app Data , start fresh.
Click to expand...
Click to collapse
Yeah I did that this morning to see if it happens again. It has been ok so far.
Happens to me a lot while I am giving training and the training was in Arabic ?
Sent from my Nexus 6 using Tapatalk
Since the last Wear update (5.1.1) I noticed that the 'Ok Google" command is less responsive.
Sometimes I have to say it three times before it is recognized, I also stumbled on this thread: https://www.reddit.com/r/AndroidWear/comments/3784f5/anyone_else_notice_ok_google_less_responsive/ so it seems others are also experiencing this.
Before the 5.1.1 update it was almost always working the first time. Maybe they lowered the sensitivity cause of false positives. Does anybody else experience the same?
Would be nice to have an option to adjust the sensitivity.
For some reason the responsive time for my watch is completely random. Sometimes it works quick and other times its waiting and waiting and even at times it tells me its off line even though the phone is right next to me.
Ginxeng said:
For some reason the responsive time for my watch is completely random. Sometimes it works quick and other times its waiting and waiting and even at times it tells me its off line even though the phone is right next to me.
Click to expand...
Click to collapse
This also happens occasionally, but it's the initial "ok Google" that seems to be less responsive.
Same problem here, any idea? :/
The same here. The last update has pretty much ruined voice control for me
Even though I don't have a solution, it's good to know that more people are experiencing this.
Probably we have to wait till the next Android Wear update to fix this.
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
Curious to see if anyone else is having success with using their voice to start commands on this watch. I have the "OK Google" recognition turned on. However, it never responds. If I restart the device, then it will recognize the command and proceed as normal.
All other voice prompts work as normal (after touching the screen of course). Not sure if I need to enable another setting.
thanks!
I just got this watch and had a similar issue. It seemed to work ok with one account on the watch. If I put my work account on it stopped working. It was set to the correct account etc. I reset 4 times, and each time the second account would mess it up. Eventually I discovered that there was an app update to androidwear on the watch that happened in the back ground that may actually be the culprit (discovered by some trials). I've only had the watch 3 days ago I'm still working on it. Last night when I went to bed, it was working. We'll see this morning. Also found out that needed to say "OK Google" slower. This is my 4th search watch and most finicky for sure!
i think I just found the answer: http://www.androidpolice.com/2017/1...-android-wear-fix-smartwatchs-stuttering-lag/
to summarize, disable the ok google detection, and the watch speeds up dramatically. i can confirm this. but I really did not want to lose the ok google feature. but I read (and tested) that my long-pressing on the big button, google assistant pops up. this is an acceptable alternative for me.
hope this helps others.
When I was on Ver 2.0, "Ok Google" seldom worked. I gave up on it working.
I have reverted back to Ver 1.5 about a month ago and now, "Ok Google" works every time and very quickly.