Google Assistant - "Ok Google" Detection Problem - OOS OB9 (Android 7) - OnePlus 3 Questions & Answers

I'm currently running a rooted version of the OxygenOS Open Beta 9. I tried to enable the Google Assistant, it does work, but I can't enable "Trusted Voice" or "Say Ok Google any time". In other words, I need to be in the app for it to detect my voice. It says that "This feature is currently unavailable for this language." even though I'm running English (US), and updated it with the latest update(s). I've seen people mentioning Xposed Framework, however that would be for Android 6 (Marshmallow), there is no Xposed for Android 7 (Nougat) yet as far as I know. Perhaps someone has had the same issue as I have, or has Google Assistant working properly.
Also, another thing I've noticed on many phones is that you need to activate the screen in order for the device to start detecting your voice. Is there any way that this can be "fixed" so you can do it while screen is off?
EDIT:
Now it seems like the only problem is that the voice model isn't saving. Because when I say "Ok Google", it'll react, but it'll ask me to teach it how to recognize my voice. This happens over and over.
EDIT2:
It's partly working. I was reading the thread about enabling it on any Android device. (http://forum.xda-developers.com/showpost.php?p=70146853&postcount=2047), ChopAssistant is a partly fix. It'll not work in Pixel Launcher at least (I have that installed on my OP3), I've not had any success elsewhere. It won't let you enable the "Say "Ok Google" anywhere", it'll either be grayed out or automatically turn itself off. As far as I understand, this is a known issue, and no known full solution for Android 7 on OP3 yet, well, not for the OOS Beta 9 at least.
If you happen to have a solution, I'd love it if you shared it with me!

I have assistant enabler xposed module and it works with the screen off and everywhere else.
Edit: accidentally quoted op lol

MrWilsonxD said:
I have assistant enabler xposed module and it works with the screen off and everywhere else.
Edit: accidentally quoted op lol
Click to expand...
Click to collapse
The problem with Xposed is that it doesn't yet support Android 7. Otherwise I'd do that too.

Nozemi said:
The problem with Xposed is that it doesn't yet support Android 7. Otherwise I'd do that too.
Click to expand...
Click to collapse
Oh : didn't know you were on n.. Not sure then.. Sorry man.

MrWilsonxD said:
Oh : didn't know you were on n.. Not sure then.. Sorry man.
Click to expand...
Click to collapse
No problem, hopefully someone has a solution, or finds a solution. Unfortunately I'm not very experienced with such things, I know how to search and find guides, but that's about it hehe.

have you tried to flash nano gapps over the rom? doing that usually solves my problems with the google app.
---------- Post added at 06:12 PM ---------- Previous post was at 06:07 PM ----------
and after you do that, here's a guide how to enable the assistant just like on the pixel
http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879

bombaglad said:
have you tried to flash nano gapps over the rom? doing that usually solves my problems with the google app.
---------- Post added at 06:12 PM ---------- Previous post was at 06:07 PM ----------
and after you do that, here's a guide how to enable the assistant just like on the pixel
http://forum.xda-developers.com/android/software/guide-how-to-enable-google-assistant-t3477879
Click to expand...
Click to collapse
Assistant is enabled and installed, just not detecting "Ok Google" command. Never heard of nano gapps. Mind linking me? Or confirm that this; http://opengapps.org/ is the same thing as what you were talking about. And thanks for your reply! Much appreciated!
EDIT:
Tried to flash the nano package I found there, it got me further. Now I can at least enable it, but it'll instantly disable it again. However, earlier it was grayed out with the message specified in my OP.

Nozemi said:
Assistant is enabled and installed, just not detecting "Ok Google" command. Never heard of nano gapps. Mind linking me? Or confirm that this; http://opengapps.org/ is the same thing as what you were talking about. And thanks for your reply! Much appreciated!
Click to expand...
Click to collapse
well, if you're on beta9 i guess you have a working twrp-recovery. what you need to do is, download the nano gapps package (be careful to pick the 7.0 version for arm64!) from opengapps.org, and flash the zip via recovery, then clear cache and dalvik. this should do a clean install of the google app on your rom and solve it's problems.
however, before you do that, make sure you have set assistant up properly, enabled voice detection on any screen in the google app under settings, and take a look into battery optimization settings, and disable the optimization of the google app. try that first, if it doesn't help, continue flashing
hope you get it working, "ok google" is an awesome feature

bombaglad said:
well, if you're on beta9 i guess you have a working twrp-recovery. what you need to do is, download the nano gapps package (be careful to pick the 7.0 version for arm64!) from opengapps.org, and flash the zip via recovery, then clear cache and dalvik. this should do a clean install of the google app on your rom and solve it's problems.
however, before you do that, make sure you have set assistant up properly, enabled voice detection on any screen in the google app under settings, and take a look into battery optimization settings, and disable the optimization of the google app. try that first, if it doesn't help, continue flashing
hope you get it working, "ok google" is an awesome feature
Click to expand...
Click to collapse
I can't enable it under voice settings. It doesn't allow me, it keeps automatically disabling itself. Earlier it was grayed out. (as I mentioned in my previous reply) And I can't find anything to disable in battery optimization. I have aggressive doze and high power usage apps disabled. This is getting really frustrating! Why couldn't Google just release this for everyone!? xD Got any more ideas as to why the on/off switch keeps turning back to off automatically?

Nozemi said:
I can't enable it under voice settings. It doesn't allow me, it keeps automatically disabling itself. Earlier it was grayed out. (as I mentioned in my previous reply) And I can't find anything to disable in battery optimization. I have aggressive doze and high power usage apps disabled. This is getting really frustrating! Why couldn't Google just release this for everyone!? xD Got any more ideas as to why the on/off switch keeps turning back to off automatically?
Click to expand...
Click to collapse
you say your phone's language is english us, but what about the google voice language? try to go to this settings, and long-press english to set it as default

bombaglad said:
you say your phone's language is english us, but what about the google voice language? try to go to this settings, and long-press english to set it as default
Click to expand...
Click to collapse
That is indeed English (US) right now, I could try to change it to something else and back again, just to see what happens.

if that doesn't do anything, you'll have to go the flashing way
it surely has nothing to do with your location, as i'm in slovakia (central europe), it's not available in slovak but i can use "ok google" just fine in english, although on resurrection remix...

bombaglad said:
if that doesn't do anything, you'll have to go the flashing way
Click to expand...
Click to collapse
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.

Nozemi said:
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.
Click to expand...
Click to collapse
then it must be a bug with the beta, sorry.. i suggest you check out resurrection remix, it is really fast and stable, and full of customizations

bombaglad said:
then it must be a bug with the beta, sorry.. i suggest you check out resurrection remix, it is really fast and stable, and full of customizations
Click to expand...
Click to collapse
Perhaps, but I'll stick with this, and will be waiting for Xposed to support Android N. Thanks for your help anyway, much appreciated!

Nozemi said:
I did that as well, it seems that it doesn't save my voice training. Because it does react to me saying "Ok Google" now, but it wants me to teach it how to recognize my voice.
Click to expand...
Click to collapse
I have the same issue as you... how did you get it to react to saying "Ok Google"... I've flashed pixelfy, when that didn't work, I ran the GetAssistant app... I installed GApps... It still will not react to Ok Google from any screen other than the Assistant screen.

dpicts said:
I have the same issue as you... how did you get it to react to saying "Ok Google"... I've flashed pixelfy, when that didn't work, I ran the GetAssistant app... I installed GApps... It still will not react to Ok Google from any screen other than the Assistant screen.
Click to expand...
Click to collapse
Still haven't found a good solution. I believe it works in the OTA version of OOS (running Android 6) with Xposed Framework and Assistant Enabler. I'm actually trying that right now. As for enabling it on Android 7 (N), it's a known issue for now, as far as I read at least. So I guess we'll just have to wait for a complete solution. Otherwise, you can read my OP for a incomplete fix. Under the "Edit 2" part I wrote something about this.

Related

Smart Lock broken in 8.1

I downloaded the 8.1 OTA build OPM1.171019.011 from Google and installed via adb sideload. After reboot I noticed that the lock screen requires authentication every time. Looking at Smart Lock (Settings>Security & location>Smart Lock) there is no option to add a smart lock option, the screen is completely blank.
I have been using Smart Lock with Wear (Currently LG Urbane) for years, and the watch is currently connected.
See attached screenshots.
TROUBLESHOOTING
I have unpaired, factory reset and repaired the watch
Rebooted the phone
Haven't gone down the rabbit hole of phone factory reset yet, trying to avoid it of course.
Anyone else seeing this?
Completely Stock Software
Never been rooted, unlocked
Purchased through Best Buy
Carrier is Verizon
Wow thats weird.. its showing up on mine, I adb flashed 8.1.
germanmarky said:
Anyone else seeing this?
Click to expand...
Click to collapse
Wow, same issue here. Sideloaded OTA last night...
Stock, Project Fi...
Just noticed it now as well. Sideloaded via ADB, because I didn't want to take the beta from my notifications.
Is the common denominator here all that we dirty flashed?
dirtdigginjoe said:
Is the common denominator here all that we dirty flashed?
Click to expand...
Click to collapse
I used the official OTA, not the full image, and not the beta, so shouldn't require a factory reset after the load.
Same behavior here. Official OTA ADB sideload.
I do have the option to set up a face unlock, but no BT device or GPS option any longer.
Figured it out.
Settings>Security & location>Trust Agents>Disable Smart Lock
Back out to home screen, then enable Smart Lock as a Trust Agent again.
Smart Lock is available again.
germanmarky said:
Figured it out.
Settings>Security & location>Trust Agents>Disable Smart Lock
Back out to home screen, then enable Smart Lock as a Trust Agent again.
Smart Lock is available again.
Click to expand...
Click to collapse
This didn't work for me, I still only have "Trusted Face".
---------- Post added at 04:36 PM ---------- Previous post was at 04:06 PM ----------
germanmarky said:
Figured it out.
Settings>Security & location>Trust Agents>Disable Smart Lock
Back out to home screen, then enable Smart Lock as a Trust Agent again.
Smart Lock is available again.
Click to expand...
Click to collapse
Can you post some screenshots showing your update version, and that smart lock works? Going to have some transcript snippets soon from a Google Support Chat Convo. Want this for ammo to prove them wrong.
---------- Post added at 04:42 PM ---------- Previous post was at 04:36 PM ----------
Google Chat support stated:
I have checked the details and I would like to inform you that its the new feature improvement with the update. You will not find trusted agent and trusted device options on your device instead you would find trusted face options with the update.
Click to expand...
Click to collapse
and
You could also check this link for reference: https://support.google.com/pixelphone/answer/6093922?hl=en
Click to expand...
Click to collapse
to which I replied:
For what it's worth, that page you just linked states:
You're carrying your device with you
Your device is in a certain place
You've connected a specific Bluetooth device
Your device recognizes your face
and it's option 1, 2, and 3 that are missing for me
Click to expand...
Click to collapse
Here you go @lyric911
germanmarky said:
Here you go @lyric911
Click to expand...
Click to collapse
Update: I did @germanmarky's process, then rebooted, and now it is working. Huzzah!
lyric911 said:
Update: I did @germanmarky's process, then rebooted, and now it is working. Huzzah!
Click to expand...
Click to collapse
Can confirm this works as well!
Now I just need to get WiFi calling back...
dirtdigginjoe said:
Can confirm this works as well!
Now I just need to get WiFi calling back...
Click to expand...
Click to collapse
Settings>Mobile Network>Advanced>Wi-Fi Calling
Does it not show up?
I have heard that if you purchased an unlocked device, WiFi Calling won't show up but can't validate on my own.
germanmarky said:
Settings>Mobile Network>Advanced>Wi-Fi Calling
Does it not show up?
I have heard that if you purchased an unlocked device, WiFi Calling won't show up but can't validate on my own.
Click to expand...
Click to collapse
I only have (in this order)
Mobile Data
Roaming
Data usage
Preferred network type
System select
Access Point Names
I'm Verizon, fully stock. Only dirty flashed from Nov sec patch to 8.10 via ADB sideload
Funny thing is, it shows in the search results when you search for it in Settings- but if I touch the result, nothing happens.
dirtdigginjoe said:
I only have (in this order)
Mobile Data
Roaming
Data usage
Preferred network type
System select
Access Point Names
I'm Verizon, fully stock. Only dirty flashed from Nov sec patch to 8.10 via ADB sideload
Funny thing is, it shows in the search results when you search for it in Settings- but if I touch the result, nothing happens.
Click to expand...
Click to collapse
Have you tried this?
https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/
germanmarky said:
Have you tried this?
https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/
Click to expand...
Click to collapse
I did just now. Did the airplane mode toggle and a reboot, and still no luck. I'm thinking I'll download the full system image, and remove the -w in the flash-all.bat and see if it makes a difference.
---------- Post added at 07:45 PM ---------- Previous post was at 07:31 PM ----------
Was able to resolve the issue by doing the following:
Go to Dialer and enter *#*#4636#*#* this will bring up the Advanced menu
Go to Phone Information and enable the following sliders
-VoLTE Provisioned
-Video Calling Provisioned
-Wifi Calling Provisioned
-EAB/Presence Provisioned (Only if you use SIP calling accounts)
Once I exited the menu by backing out, the options were immediately available again.
i managed to get smart lock to work with deactivating trust agent, going to home screen and re authorizing the trust agent...
but now my Gmail, T-mobile app, Google app, all constantly crash upon using them.... SMH
germanmarky said:
Figured it out.
Settings>Security & location>Trust Agents>Disable Smart Lock
Back out to home screen, then enable Smart Lock as a Trust Agent again.
Smart Lock is available again.
Click to expand...
Click to collapse
This seems to have worked after a restart. :good:
factory reset fixed all my constant app crashing issues..
Confirmed! germanmarky's suggestion to turn off Smart Lock as a trusted agent combined with lyric911 reboot suggestion did the trick.
Got all my smart lock options back and now voice unlock is working again.
Thanks! Much better support than Google, they didn't have a clue, just wanted me to reset the phone--their go to solution which is crap.
I followed these tips which got Smart Lock working for me again, however, after some time Smart Lock becomes disabled again. At that point if I go to Smart Lock in settings, I see just a white screen with no options. Is anyone else seeing this?
Edit: following the steps gets it to work again, for a while, but not permanently

s9+ with new pie update. google home voice commands not working.Just searches.ideas?

s9+ in Canada.
Installed update
Did a factory reboot (I was due anyways)
Installed everything. Things run smooth!
Set up my google home/assistant/LIFX lights. Everything works, except when I say "ok google turn on lights" it just does a search.
Remove/uninstall assistant/home and reinstall and set everything up again. Still doesnt work. Kind of frustrating as it was working fine before update and I did regular troubleshooting like uninstlaling and re-installing. Curious if anyone has had similar issue?!
gemini8026 said:
s9+ in Canada.
Installed update
Did a factory reboot (I was due anyways)
Installed everything. Things run smooth!
Set up my google home/assistant/LIFX lights. Everything works, except when I say "ok google turn on lights" it just does a search.
Remove/uninstall assistant/home and reinstall and set everything up again. Still doesnt work. Kind of frustrating as it was working fine before update and I did regular troubleshooting like uninstlaling and re-installing. Curious if anyone has had similar issue?!
Click to expand...
Click to collapse
noone will answer, many read but don't want try. i did same question for this phone. this is a problem of android pie in samsung s9 devices. the google assistant when screen is off receives command but doesn't execute..... the google assistant doesn't execute the routines (try)... like all problems of samsung devices, i think never will come a solution. we yet wait bixby and continue conversations ok google in other languages, but from s7 devices....

Android auto issues?

Anyone else having problems with AA? When I unplug from either of my head units, the phone AA app fires up and music keeps playing on the phone. Sometimes it's just the music that keeps playing in the background, so I have to start the app on the phone to stop it.
Oh, and then in AA Waze will show my car traveling sideways on the screen instead of actually orienting the road top to bottom.
It's working fine for me on the N9860. I have next to the system app version of AA also AA for phone screens installed so I can set preferences for AA on my phone. No display issues at all. I do experience sound routing problems in combination with some sound assistant settings. Multi Sound and Separate App Sound conflict with AA audio routing. You need to keep rhse settings off in Sound Assistant.
Sent from my SM-N9860 using Tapatalk
Works Fine for me on My AT&T Note20 Ultra 5G 512GB Snapdragon
Running On SM-N986U Galaxy Note20 Ultra 5G 512GB
https://youtu.be/SXmO8l6iyJs
Damn, I was really hoping it was a known issue.
I have not had the audio issue however I do see that my car is not oriented properly on the map.
Make sure location setting is set for greatest accuracy.
Try clearing the System cache on the boot menu.
Try clearing cache and data if necessary on associated apks .
Is the GPS sensor working properly... check it with maps make sure it's not intermittent.
Yea, if I hop over to maps, it's running correctly. I've uninstalled and reinstalled waze. It also only does it with AA. If I unplug the phone, waze runs fine.
Waze is pretty worthless; it's dependent on Goggle maps running in the background to operate.
Just pretty face with no brains.
Try it in Safe Mode. If it runs correctly, it's a 3rd party apk.
blackhawk said:
Waze is pretty worthless; it's dependent on Goggle maps running in the background to operate.
Just pretty face with no brains.
Try it in Safe Mode. If it runs correctly, it's a 3rd party apk.
Click to expand...
Click to collapse
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
barry99705 said:
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
Click to expand...
Click to collapse
You can't uninstall gmaps normally... it's running in the background when waze is being used.
When I package blocked gmaps, waze went doa; it needed it.
Works just fine on my phone with maps disabled. Waze doesn't use any code, or services from maps. They're still a separate entity, just owned by google.
barry99705 said:
Uhh, what?! They use totally different mapping services.. They're based off open street maps. It will run just fine with maps uninstalled.
Also, android auto doesn't work in safe mode.
Click to expand...
Click to collapse
barry99705 said:
Works just fine on my phone with maps disabled. Waze doesn't use any code, or services from maps. They're still a separate entity, just owned by google.
Click to expand...
Click to collapse
Haven't used it in 2 years. I saw this behavior though.
Blocked or disabled? I blocked it so gmaps couldn't run in the background which it loves to do.
Just an update, Waze told me to just lock north up, which kinda sucks as a fix. September update didn't fix the issue.
I have this persistent music issue junt one time, but I just can´t get the notifications in the right language. Don't matter if I set the car and everything on my phone to my native language, it always read the notifications in english
rafafischer said:
I have this persistent music issue junt one time, but I just can´t get the notifications in the right language. Don't matter if I set the car and everything on my phone to my native language, it always read the notifications in english
Click to expand...
Click to collapse
This is a know issue with AA and Android 10 that is not affecting only Brazil. Google acknowledged it AFAIK but a fix was never delivered. Not sure if someone with Android 11 that used to have this problem can report if it still happens.
I read somewhere (sorry, can't recall where) that if you change the assistant language to English somehow it will read your messages in the right language in AA. Or maybe it was about changing the phone language to English and keeping the assistant in your language.
May have ended up causing more confusion than helping.
antinun said:
This is a know issue with AA and Android 10 that is not affecting only Brazil. Google acknowledged it AFAIK but a fix was never delivered. Not sure if someone with Android 11 that used to have this problem can report if it still happens.
I read somewhere (sorry, can't recall where) that if you change the assistant language to English somehow it will read your messages in the right language in AA. Or maybe it was about changing the phone language to English and keeping the assistant in your language.
May have ended up causing more confusion than helping.
Click to expand...
Click to collapse
I've tried this process of change the Assistant language, but not solved the issue... Maybe Android 11 came to save us :laugh:

Question Google assistant: "...yes, but first you need to unlock the phone."

Hi to all,
I have encounter a boring problem with op9 pro paired with bluetooth headset (more than one).
every time I said on assistant by my bluetooth headsets (aftershokx aeropex, oneplus bullets wireless Z) any commands like "call mom" "open garage Stefano" "turn on stairs light", and so on, assistant telle me to unlock phone first (????). On assistant the option of "personal results on lockscreen" and the one relative to bluetooth devices is activated, but: "[...]yes, but first you need to unlock the phone.".
on my op7 pro i try same commands without any problems. So... which is the problem?
It's very boring, expecially driving, unlock the phone to use it to make a simple call or to open my garage door.
+1
Turn on smart lock -> trusted devices
craznazn said:
Turn on smart lock -> trusted devices
Click to expand...
Click to collapse
This is not the solution... Is a workaround that I don't want to use for security reasons at work.
Don't use the screen lock.
Treat your phone like your hand and you don't need it.
Please reply with intelligent solution...
stefal639 said:
Please reply with intelligent solution...
Click to expand...
Click to collapse
I tried... for you, none.
You want security yet look what you're doing
Bank, g pay and other apps want security lock to function... So it's obvious that security lock screen need to be applied.
stefal639 said:
Bank, g pay and other apps want security lock to function... So it's obvious that security lock screen need to be applied.
Click to expand...
Click to collapse
I see what you mean... sorry.
I don't use any of those apps and especially voice assistant. Bixby is even worse.
Try this:
How to Use Google Assistant Without Unlocking Your Android Phone
Google Assistant is a handy companion to have on your Android smartphone or tablet. To really get the most out of Assistant’s hands-free features, you’ll want to make sure it can work even when your device is locked.
www.google.com
blackhawk said:
I see what you mean... sorry.
I don't use any of those apps and especially voice assistant. Bixby is even worse.
Try this:
How to Use Google Assistant Without Unlocking Your Android Phone
Google Assistant is a handy companion to have on your Android smartphone or tablet. To really get the most out of Assistant’s hands-free features, you’ll want to make sure it can work even when your device is locked.
www.google.com
Click to expand...
Click to collapse
It's yet activated...
stefal639 said:
It's yet activated...
Click to expand...
Click to collapse
Try clearing Goggle Play Services data.
Clear system cache.
Try a network reset (can't hurt).
You may have to delete/recreate the account if nothing else works.
Play with it... eventually you'll get it working.
made it, also clean flash of last ota...seems that something goes wrong with assistant because the problem still stay here also before a clean install.
stefal639 said:
made it, also clean flash of last ota...seems that something goes wrong with assistant because the problem still stay here also before a clean install.
Click to expand...
Click to collapse
Check permissions, notifications and make sure no power management is enabled.
Possible conflict with another app.
Lol, sounds like it's settings could be screwed up by default.
Try searching Google for the same issue even on different makes/models as you're no alone... someone has found the solution.
OK Google [to do that you need to unlock your phone] - Google Assistant Community
Seems that is a problem that appear randomly from 2 years (expecially on OP).
no solution from google
stefal639 said:
OK Google [to do that you need to unlock your phone] - Google Assistant Community
Seems that is a problem that appear randomly from 2 years (expecially on OP).
no solution from google
Click to expand...
Click to collapse
You can try contacting Google tech support. Occasionally they can be quit helpful... if they choose to.
A Bing search etc may yield better results.
I really try to keep my use of Google apps to a bare bones minimum.
I don't trust them... they earned it.
here is how i solve similar problem that not exactly the same but when i ask google assistance to turn flashlight for example it ask to unlock the screen 1st
1-open google app and press MORE
2-setting
3-google assistant
4-personalization
and final check every toggle on that screen (personal result, lock screen, etc. )
that should not ask to unlock the screen again check and let me know how it gose
yosry said:
here is how i solve similar problem that not exactly the same but when i ask google assistance to turn flashlight for example it ask to unlock the screen 1st
1-open google app and press MORE
2-setting
3-google assistant
4-personalization
and final check every toggle on that screen (personal result, lock screen, etc. )
that should not ask to unlock the screen again check and let me know how it gose
Click to expand...
Click to collapse
Still don't work
stefal639 said:
Still don't work
Click to expand...
Click to collapse
Why it look different so you use custom rom
yosry said:
Why it look different so you use custom rom
Click to expand...
Click to collapse
it's the latest OOS11, no custom rom. (italian language)
I am clueless did you did the voice match thing

Question Google Assistant: Cannot reach Google at the moment.

My Google Assistant suddenly stopped working. Whenever I tried to issue a command, it returns "Cannot reach Google at the moment.".
Tried in my old phone, there are no problems.
Tried restarting but the problem still persists.
Anyone experienced this? Any solution?
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried, didn't work.
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Sea21 said:
Same here, brand new Pixel 6. Go into Assistant settings, scroll all the way down to "Your Apps (manage how Assistant works with installed apps)." Click on the Chrome browser and make sure "let your assistant choose this browser" is checked on. THEN, in the same settings, go to whatever other browsers you have installed and UNCHECK those.
Apparently Assistant got confused by too many options. (it might work if you check another browser and uncheck Chrome, but I quit playing with it once it was working again.)
Click to expand...
Click to collapse
Did this one but didn't work. Also, I only have Chrome as browser so I guess this isn't the problem.
Thiviru Gunarathna said:
HI YOU HAVE MANY WAYS TO FIX THAT
1-TRY FORCE CLOSE GOOGLE ASSISTANCE AND CLEAR ALL DATA AND CACHE .
2-IF YOU ARE USING A DATA PACKAGE ,USE A VPN
IF THOSE METHODS DON'T WORK UNINSTALL APP AND REINSTALL IT
Click to expand...
Click to collapse
Tried uninstalling, rebooting and re-updating the Google app. The Assistant is working again but Continued Conversations doesn't work. There were also times after I did this, the problem returned.
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Starzboy77 said:
I had the same problem yesterday and fixed it by doing the following:
Google app->settings->Google Assistant->Assistant Voice-> and switch Phone to full.
I also purchased universal safetynet fix 2.2 and now pass Safetynet. Did both in conjunction with each other so that combo should work if you are rooted with the correct Magisk Canary.
Click to expand...
Click to collapse
Not rooted and already set to Full, Continued Conversations still doesn't work.
danw_oz said:
dont need to shout.
The problem is nomally related to internet not working, be it service, or vpn stalled
Click to expand...
Click to collapse
ok i forgot to off capital letteres
I have struggled with this recently. Here's what worked for me. I noticed that on cellular it worked, but on my WiFi it did not although it had in the past. The trick was to go into WiFi settings and tell it not to randomly change the Mac address (use Device MAC). I suppose that -- maybe only with some routers -- the changing MAC is upsetting the NAT translation and your phone is making an outbound connection but that's just a theory.
I had the same problem, had used adaway and blocked some dns requests, cleared these and Hey Google worked again. Cheers.
Usually, the only times I have trouble with the Assistant this way are when I get in my car, hook it up for Android Auto, and in my driveway, I'm kinda in range of my Wi-Fi but not very well. It doesn't usually take very long for my phone to switch to mobile data on its own in this situation (and it took my Samsung way longer), but once it establishes a reliable connection via mobile data, then it's fine.
Necro'd thread to post POSSIBLE FIX:
Go into Developer options and disable 'App Wi-Fi Multi/Broadcasting Filter'. I'd turned it on randomly and forgotten, and have been suffering ever since. Turning it back off allows the app to connect to the internet, despite your phone being locked until standby.
Going off to cross-post this elsewhere because I've searched SO many pages trying to find a fix, and nobody mentioned trying this.

Categories

Resources