Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
repsol89 said:
Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
Click to expand...
Click to collapse
I never had the issue on my LG G2 but it happens now. Also happens often on my Galaxy Tab S2 really often. I think its a Google thing and they have made things too sensitive.
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
natboy said:
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
Click to expand...
Click to collapse
Well, actually that's not a solution, more like a "workaround"... I like the "Ok Google" From Any Screen feature, I use it once in a while.
It's like asking "I have bad call quality, what can I do?" and receive "stop doing voice calls" as an answer...
Update: I flashed 3.5.4 yesterday, same issue experienced today.
I tried to install google assistant, but it showing "This account is not eligible for the feed"
Related
Anyone else having random disconnects when right by the phone? Disconnecting and reconnecting via the wear app on my phone doesn't seem to fix the issue either. Could it be that I'm on a network extender attached to my wifi for cell signal boosting because it appears to sync the apps, just nothing internet related.
I'm having the same issues. Just got mine yesterday and I have frequent connection drops and have to reset Bluetooth on my phone to reconnect. The android wear app says that it is connecting, but no matter what I do it won't pair up again until I reset that Bluetooth.
I saw somewhere else someone said they had a similar issue on CyanogenMod. I'm running the latest CM11 nightly on a VZW S4. What phone and ROM are you using? May help us troubleshoot.
Sent from my SCH-I545 using XDA Free mobile app
The GPE 4.4.4 on GS4.
I'll say "Ok, Google Call X" and it just does the spinning circle and soon after disconnected. Resetting bluetooth, restarting watch and phone does nothing for it. I'm thinking maybe it's the phone rom. I may go back to stock and try completely stock with it just to rule out any 3rd party bluetooth issues and what not.
Regarding the spinning circle after saying something after "OK Google", ...
I had this too. To help diagnose, I took my phone out and said "OK Google" and the phone didn't respond. So I concluded it was the phone. To fix this, I kill'ed the Google process and let it start again by trying "OK Google" on the phone again. After that works, I then try using the Moto 360 and then it responds.
The "OK Google" functionality makes up a big chunk of what the Moto 360 can do (and perhaps all other Android Wear watches). Without a reliable Google process working, that functionality falls apart.
In my case, my ROM was not quite right. I ended up doing a factory reset and re-flashing. I'm on Note 3 N900T DNF9. So far so good. But as soon as I see the spinning circle, I don't even wait. I test it by saying "OK Google" followed by "weather".
Dennis
Hi All,
When I use "ok google" to do a command for example say text. It would text once and then another time when I unlock my phone. Similar issue with everything else be it calling, setting a timer (once on the watch and once on the phone when i unlock) etc. Not exactly sure what the issue is - be it android wear update or the phone itself or a setting I don't know about. So what happens is I've been having this issue ever since I got a new phone.
Any advice or answers would be helpful.
Thanks
Hello there guys,
i've recently been looking for a way to use something else rather than "Ok" to summon the assistant, and i found out that Google actually released the "Hey Google" hotword for it.
Before it, i've been able to use the assistant using my voice just fine, but when i've been prompted to retrain the assistant, it asked me to record 4 things (Ok, Hey, Ok, Hey, as far as i know, cause i've never gotten to the "hey" part) instead of 3 (Ok 3 times).
Problem is, when i say "Ok Google", nothing happens. It just stays there, waiting for me to say it, even though i did. And the only solution is to revert the Google app to the factory version, retrain the assistant with the 3 "Ok Google", and then re-update the Google app. Point is, if i even try to retrain the assistant while the Google app latest version is installed, i get stuck, and have to re-do all the process.
Is there any way i can solve this?
I have a OnePlus 5T running Android 8.0.0.
Thank you so much.
I've also been prompted by Google via notification to train the assistant using "Hey Google" as well... but the same bug occurs.
I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.
... and has a way to fix them?
1. the phone will decrease its refresh rate from time to time and stays there, and the "stuttering" is only fixed by rebooting. Yes, I am aware, that Whatsapp and Telegram voice messaging is occasionally linked to it, and can be handled by removing the apps from memory. But not in the mentioned cases.
2. "Ok, Google" accessing the assistant doesnt work from now and then. And is back to normal a few tries later.
3. When talking over the phone with speaker mode and browsing on the phone, the notification bar cannot be pulled down any more, which is annoying cause I cant easily open the phone tab to end the call.
Anyone, guys?
2. I have a similar bug with quick tap, it seems that a system app freezes/crashes, and without knowing the exact culprit the entire system needs to be rebooted to enable the function again.
Plus my "Ok, Google" also stopped working in the past, found no way to fix it yet. It's probably an Android 12 bug.
Since yesterday I noticed my AOD does not work when on a call, screen goes dark. I go into AODsettings and it still turned ON.
There's only been one update since the phones been released, besides the FPS update, after a few updates it'll be fine
I have noticed "OK Google" not responding at times as well.. not as bad as my 2XL was at times, only a reboot would fix that...but is annoying to say the least especially when driving. And I don't think it works while using Waze or Maps for navigation either which stinks, maybe I need to use Android Auto for that integration to work right.