I just got the latest Google Search update, which opened up the "From any screen" and "From lock screen" options for "Ok Google" Detection.
When I turn either of those on, Google Search works beautifully. However, I lose in-call audio after 1 or 2 uses of "Ok Google." I can't hear anything in the call, and folks on the other side can't hear me. I have to reboot (sometimes pull the battery) to get it back.
When I disable those two options, in-call audio is fine, but I lose this cool new feature.
I'm on HyperDrive 16, but it also happens with the latest HyperDrive 17. Not sure if it happens in stock, or if I should try different modems, etc. Anyone else seeing this who might be able to give me some insight?
Related
Just wondering if my experience matches others:
I have factory reset my device three times in an attempt to triage waking my device by voice. Using both S-Voice and "OK Google" configurations. This is what I have seen:
S-Voice is still touch and go. Seems to work when it wants and other times not. Confirmed that it does respond best if you do not launch -or- configure Google Now Voice Detection. Once you have activated Google Now, you have less likelihood of having S-Voice respond properly, let alone wake the device.
Google Now "OK Google" seems to work flawlessly as long as the device is in any one of the following states:
on a wireless charging pad
plugged in
screen on
This last configuration/reset S-VOICE was stable and responsive until I launch Google Now and configured Voice Detection. Even turning off Voice Detection, clearing cache, uninstalling did not restore S-VOICE to waking the device consistently. I chose to just press-on without S-VOICE and live with the configuration. Hoping for a future patch or fix.
SeeBeatty said:
Just wondering if my experience matches others:
I have factory reset my device three times in an attempt to triage waking my device by voice. Using both S-Voice and "OK Google" configurations. This is what I have seen:
S-Voice is still touch and go. Seems to work when it wants and other times not. Confirmed that it does respond best if you do not launch -or- configure Google Now Voice Detection. Once you have activated Google Now, you have less likelihood of having S-Voice respond properly, let alone wake the device.
Google Now "OK Google" seems to work flawlessly as long as the device is in any one of the following states:
on a wireless charging pad
plugged in
screen on
This last configuration/reset S-VOICE was stable and responsive until I launch Google Now and configured Voice Detection. Even turning off Voice Detection, clearing cache, uninstalling did not restore S-VOICE to waking the device consistently. I chose to just press-on without S-VOICE and live with the configuration. Hoping for a future patch or fix.
Click to expand...
Click to collapse
Can't speak for s voice but Google now is only supposed to work when you have it charging or the screen on.
Sent from my SM-G925V using XDA Free mobile app
Google Now works perfectly fine to wake my device by voice on my Nexus 6 and OnePlus one.
I do believe it is the Snapdragon processor,... However, I know that SVoice works on he Exonose to wake,... So that tells me the device is listening.
I used S-Voice to wake the phone a few times. Sometimes it works very well and sometimes it doesn't. I use "Galaxy" as the wake up command and it works 50/50 depending on how I say it when the phone is off. So you can definitly wake the phone with s-voice. I actually like how they implemented s-voice in the s6 as an overlay.
If the phone is locked you don't even need to wait for S-Voice to activate. You can say for example "Galaxy...what time is it" and it will recognize "what time is it". If it does not recognize anything it will say that it's listening and you need to speak (again).
Google Now is supposed to only wake the phone on Nexus Devices. Google has not implemented it to work on all devices.
I can confirm that with activated google now s-voice does not work or only sometimes. I think only one app can listen all the time.
For this kind of situation "OK Google " is working fine for most of the phones.
I've had 2 S6 Edges now and both times , people at the other end of the call say there cant hear me for about 5 seconds, and it sounds like i'm either, under water, screwing up paper next to the mix, or i sound very muffled. Then it goes back to normal for a while, and the does it again.
I've read somewhere that turning of "ok Google" wakeup feature off will cure it. I have had 1 incoming call so far with success and no problems at all, but requires more testing.
On regards to the location, i am however very close to a building site (eg intercoms) which may interfere with signal.
A phone call with "ok google" feature on, and builders using intercoms resulted in problem with muffled noise.
A second call with "ok google" off, resulted in a prefect call with no sound issue, but equally the builders had gone home (hence no intercoms).
I have also experienced the muffled problem while not near the building site.
This was also with the "ok google" feature on.
Will post results from further calls.
My point being, Has anyone else had this problem? And if so, What location (with possible interference) did you experience it?
Hi everyone,
I want to use Tasker to wake up the phone by saying a some pharse, but not "Okay Google". Since Tasker can't turn on the display on the Nexus 4, I'm using the Secure Settings plugin. I know for a fact this plugin works because I managed to wake up the device by shaking it, just to try. Issuing the voice command is something else entirely.
For this I downloaded Autovoice, and set it to continuous listening. For some reason, it doesn't respond (even when the screen is on), unless I use Google now. By watching one of Armando Ferreira tutorials on Tasker (https://www.youtube.com/watch?v=J259WzkO3-Y) I learned that by setting continuous on in Autovoice, you can issue voice commands without saying "Ok Google" but it doesn't work for me.
Any ideas why and what I can do?
Thanks.
It's possible that I just don't really understand how to do it - can anyone explain, or link to any tutorial?
Hi, can anyone suggest what I can do to try to nudge sound output back to life in Google Now. It did work for me when I first set it up but now it's silent. I've read around this one before posting and I have cleared the cache for the Google App, checked the system volume (of course) and checked that all the necessary voice/TTS downloads are correct and working so I can hear an example announcement. I've tried every permutation of setting with OK Google on/off, sound on/headphone-only, etc. etc.
I've worked it out! It was the NuPlayer setting in developer options that needed to be turned off; then reboot.
I had tried setting Nuplayer on to fix my 'no sound during calls' issue http://forum.xda-developers.com/showpost.php?p=65590028&postcount=232
My assistant seems to work Ok for a while (after configuration), recognizing my voice locked, unlocked, in any screen. But after a while it simply stops working, not recognizing any voice. I noticed that when i put my headphones (with mic) on and say "Ok google" the it works again, and when i remove my headphone it keeps working for a while (maybe a few hours) before stop again. I think that is something on miui shutting down the mic sensor, and when i plug my headphone it reactivates. I dont know if theres any solution for this problem. Google app seems not to be a "commom" app that we can chance permissions and disable battery optimization, so i dont know what to do. Thanks!
Anyone?
Been observing this issue for the past 3 builds i guess.....must be some app management issue just as u anticipated....ive enabled trigger the assistant on pressing the power button for 0.5 seconds in button and gesture settings.... currently this seems to be the only plausible workaround.
Been observing the issue as well for the past 3-4 builds. I just cleared the data of google app and somehow it works again.. though i don't know if it will last.
Holy hell! How did you get the assistant working in the first place, tell me. It doesn't even respond to me even when I'm inside google app. 'Ok Google' thing hasn't worked for me for many months.
Alternative to launch assistant
peleya said:
Been observing this issue for the past 3 builds i guess.....must be some app management issue just as u anticipated....ive enabled trigger the assistant on pressing the power button for 0.5 seconds in button and gesture settings.... currently this seems to be the only plausible workaround.
Click to expand...
Click to collapse
Have you tried connecting bluetooth earphones, and using the button to launch the assistant ?
It works for me on an older xiaomi phone(redmi 3), using a ROM. Pretty reliable.