Hi, I'm running a Nexus 6 on the latest 14.1 LineageOS nightly. It's 7.1.2. I am using elementalX kernel. For a while now I have had an issue with google assistant turning on at random times, as if I had said "ok google". It happens more frequently when I'm listening to music (I think), but it happens other times too. Sometimes there are headphones plugged in, other times a bluetooth speaker, and sometimes nothing. It's hard to find a pattern.
Like I said in the title, sometimes the phone is locked and the asleep, and the screen will wake and prompt me to put in my pin, while making the google assistant prompt noise.
I've tried looking online but most people just recommend turning the feature off altogether, which is not optimal. Even still, I've turned off some of the activation settings, but I feel like I'm missing something here.
Any help is appreciated. Thanks a bunch!
Related
I flashed CLoudy 1.4 on my VZ980 a few days ago, and only today did I go the use Google Now and noticed the "Ok Google" hot word doesn't work. No problem, I tapped on the mic and get the familiar sound like the microphone starts to listen, but then it stops after 2-3 seconds and doesn't hear me at all.
SO I tried installing Open Mic+ to see if that works...and the hotword works flawlessly. With the screen off, I can say "Ok Google" and it turns on and changes to the google now interface and the mic button turns red as if listening and then turns off again.
There must be a check box or download I'm missing, but what? I've went thru the settings in google now and the hotword detection is on, setting all look correct.
I'm thinking it has to be a phone issue more than a ROM issue that is why I am asking here.
bump?
Xsoldier2000 said:
bump?
Click to expand...
Click to collapse
Wow, no one has this issue?
try the openmike+ threads
send from the jungle
I had this happen too on the stock rom, but determined it was g2 xposed causing the issue. Once I disabled long press to launch voice search, this stupid bug stopped. Really annoying, I feel your pain.
-VZW LG G2 VS980
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.
For some reason when I'm trying to use ok Google on any screen it is very spotty if it works or not. Occasionally it will work, but most of the time it just doesn't do anything. I have any screen turned on and I also have it turned on so that should detected when the screen is off. Very rarely do either of these work, & I have to go back to the home screen and hit the microphone for it to work. Anyone know how to fix this? I have tried retraining a couple of times also.
Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model
The service that does that apparently gets killed after a while, requiring a reboot. It's happened to me a bunch of times, for more than a year now, since the N6. It happens with other random stuff too. The N6 has a "safety" (according to a Moto rep at their forums) feature that rings the first 2 seconds or so of a phone call or alarm/timer at very low volume before it rings at full volume. Also for when you switch to speakerphone. Whatever service causes this behavior does get killed as well after a while, and the N6's alarms and rings sound off at full volume immediately, until after a reboot.
Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.
isimme said:
Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model
Click to expand...
Click to collapse
I mentioned that I already tried that
tropazr said:
Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.
Click to expand...
Click to collapse
Yes, the Nexus 5 was much more reliable.
Hello, I have had my V20 for a couple of months now but seem to have an odd issue with Google Assistant responding to "Ok Google". Basically it does not respond unless the phone is a bout 10cm away from my mouth but when it does eventually respond and starts listening it picks up my voice flawlessly.
I have re-registered my voice multiple times.
Registered my voice from different distances
Wiped the google cache.
Tried it just the stock google launcher.
Excluded google enrolment from the optimised battery settings.
Had a search round XDA and cant find any other suggestions
General phone calls are working without issue.
Phone - H990ds
Software - V10f-TWN-XX
Build - NRD90M
So before I go and wipe the phone any suggestions?
Thanks in advance.
Hi I've got the same issue have you found a solution yet.
Hi I have the same issue.
Have you always had this problem or is it a recent change?
I have Mi Airdots S and to summon the Google Assistant, you double-tap the button on either headphone . If the screen is on and unlocked, everything works as expected. But if the screen is off and you want to talk to the Assistant while the phone is in your pocket (which would be a normal scenario when using headphones), all I get is a notification on the lock screen saying that you can use the Assistant with headphones while the phone is locked.
I've tried using a different pair of wireless headphones, and the result is the same. What I notice is that the microphone activates, but the phone does not receive its input. Which leads me to conclude it is not the fault of the Airdots, but this phone or MIUI 12. I've tried playing with all possible GA and phone settings, but to no avail.
Your help is appreciated.
https://support.google.com/assistant/thread/286844?hl=en
The last post
Sent from my Mi Note 10 using XDA Labs
Thanks for the answer, but that is not the issue I'm having. I don't need to wake up the phone by saying "ok google", I just want it to respond properly when I call for the Assistant using the double-tap on the headphone button.
Any other ideas?