Google App v6.9.36.21.arm64, Viper ROM v4.4.0 and v4.5.0 (both clean installs), S-Off, Bootloader unlocked, TWRP v3.0.3.0_Unofficial.
Anyone else having issues with "Ok Google" detection not working when "From any screen" is selected? Even from within the Google app open with the search bar that states " "Say OK Google" ", I can't get the phone to respond to the "Ok Google" voice command. In other words, it never brings up a voice activated search.
If I deselect "From any screen", then it works from within the app with the search bar, as expected. But the moment I select "From any screen", and no matter how many times I've tried retraining the voice model, it never responds to "Ok Google".
Microphone is verified working.
The strange thing is that it was working a week ago, and nothing had changed since that time. I was running Viper 4.4.0 (Full ROM, not Magisk version) up until today (it was yesterday while on v4.4.0 that I noticed it wasn't working anymore), and today the v4.5.0 update came out, so I opted for a completely clean install to rule out any bad settings I may have mucked up at any point. Still, on v4.5.0 Full ROM (non-Magisc version), I can't get it working. I also tried installing Google Now Launcher to see if it would work with a different launcher, and still no luck.
Google App has permissions to Microphone (have also tried clearing data from app, and resetting it up, completely uninstalling Google App and reinstalling/setting up - still no joy). I've removed Google App from battery optimization, no change. I just can't make heads or tails of it. My wife's phone (Samsung GS7) has the same version of the Google App installed, and hers works fine, so it can't be the app.
Anyone out there care to verify on their phone if "Ok Google" detection from any screen works for them? And what is your ROM, Root, Bootloader, and S-on/S-off situation? I'm just a little curious with all the "Feature blocking for rooted devices" that's been going on lately, if Google blocked the use of "Ok Google" voice detection from any screen for rooted and/or bootloader unlocked devices for some strange reason.
Thanks! Any hits/tips/tricks would be greatly appreciated.
Can anyone at least verify if "OK Google" detection from any screen is working on their HTC 10?
Sent from my HTC 10 using Tapatalk
It's working fine here . Try to delete ok Google detection sample from voice search settings in Google now .
hamud.q said:
It's working fine here . Try to delete ok Google detection sample from voice search settings in Google now .
Click to expand...
Click to collapse
Just so I'm clear, are you suggesting to delete, then retrain the voice model from the Google App? Just want to be sure I understand, since I've performed the voice model training countless times since the issue popped up.
For the record, I don't have the Google Now Launcher installed. I only installed it once after noticing OK Google detection wasn't working, and when I noticed it didn't change anything, I removed it.
Thanks, and if you don't mind sharing your phone's setup?
Boostjunky said:
Just so I'm clear, are you suggesting to delete, then retrain the voice model from the Google App? Just want to be sure I understand, since I've performed the voice model training countless times since the issue popped up.
For the record, I don't have the Google Now Launcher installed. I only installed it once after noticing OK Google detection wasn't working, and when I noticed it didn't change anything, I removed it.
Thanks, and if you don't mind sharing your phone's setup?
Click to expand...
Click to collapse
You don't need to delete it, just retrain it. I've had to do this myself a few weeks ago.
xunholyx said:
You don't need to delete it, just retrain it. I've had to do this myself a few weeks ago.
Click to expand...
Click to collapse
OK, well, I've done it both ways (simply retraining, as well as deleting, then retraining). Nothing seems to restore functionality.
Thank you for the input.
Yes exactly ! Retrain ok google . But if that doesn't solve the problem . don't know what to do next .
Well, as an informational update to this issue, I flashed a stock RUU for my variant (US Unlocked, 2.38.617.6), and everything functions as intended. So, there's something funky going on with the custom ROM I was running. Attempting the Magisk version next to see if it all works there.
Boostjunky said:
Well, as an informational update to this issue, I flashed a stock RUU for my variant (US Unlocked, 2.38.617.6), and everything functions as intended. So, there's something funky going on with the custom ROM I was running. Attempting the Magisk version next to see if it all works there.
Click to expand...
Click to collapse
I believe I'm on the same ROM as you, and am using the classic SuperSU version, and it is working for me. I wish I had an answer for you, but I don't.
I'll try and see if I can find one for you though.
Further testing shows that it works on the Magisk version, but then immediately flashing back to the classic version with PHH Superuser, it ceases to function. I'll try testing with the classic version of the ROM using SuperSU, instead.
One last update for the day. Installing Viper v4.5.0 with SuperSU insteaed of PHH seems to have solved the issue, as well. Seems something about PHH is interfering with Google App voice detection from any screen.
Thanks for the input, guys.
I have magisk / phh r2 installed and my "OK Google" detection from the Google now on tap screen works very poorly. I've been thinking I had to yell at it to detect my voice, but even that is hit or miss. When I enable OK Google detection from any screen, it works just fine.
Edit: running 2.38.617.6 with latest magisk, included root, magisk hide enabled, and systemless host enabled for AdAway 3.2.
adamjmacdonald said:
I have magisk / phh r2 installed and my "OK Google" detection from the Google now on tap screen works very poorly. I've been thinking I had to yell at it to detect my voice, but even that is hit or miss. When I enable OK Google detection from any screen, it works just fine.
Edit: running 2.38.617.6 with latest magisk, included root, magisk hide enabled, and systemless host enabled for AdAway 3.2.
Click to expand...
Click to collapse
Odd... Man, I've tried so many things to get it working on a fresh install of 4.5.0 with PHH, and could never get it to work.
I would even do a fresh, full wipe install, then I wouldn't install any apps, set up voice model for OK Google, and still couldn't get it to work.
Related
I tried every possible way of using Google assistant on my CM 13. Used Android N-fy, edited build prop but nothing worked.
It showed "This account isn't connecting to the feed"
Anyone running google assistant on their device? Help! Thanks.
ShiShTuBaBu said:
I tried every possible way of using Google assistant on my CM 13. Used Android N-fy, edited build prop but nothing worked.
It showed "This account isn't connecting to the feed"
Anyone running google assistant on their device? Help! Thanks.
Click to expand...
Click to collapse
It works for me on OP3. Follow this tutorial and let me know if it still gives you an error.
mymmx said:
It works for me on OP3. Follow this tutorial and let me know if it still gives you an error.
Click to expand...
Click to collapse
I think its my location issue. It says while loading feed "This account is not eligible for the feed"
join the beta version of the google app, make sure n-ify experimental is enabled and the google assistant thing is checked to enable, reboot and it should work
note: "ok google" didn't work for me but I just set long press home to google assistant. also i found that this drained my battery significantly so i uninstalled it a day later
Hi, I just updated my Nexus 5X with the last version of Resurrection Remix (5.8.1), like the older version 5.8.0 the "Ok Google" options (saying any time, from any application) doesn't seems to work (you can see in the video below what the problem is):
vimeo.com/202420699
And a little question, I see everywhere that the "Cast Screen" option doesn't seems to work as well, is there any way I can make it work? Right when the TV goes black and it need to start the cast, the TV goes back to the previous menu and zero (the "Enable wireless diplay" option is turned on).
In order to solve OK Google issue try to install the beta version of Google
That's a problem with OpenGapps. Did you use them?
I flashed the micro pack.
And I joined the beta on Google app and still nothing.
Try Dynamic Gapps and keep the beta
I tried minimal Dynamic Gapps with clean install of RR and Google App Beta, "Ok Google" seemed to work but after I modified some settings (language i think) I had the same story. I was unable to activate it again ("Ok Google" from any screen, even when the phone is locked).
Many apps were crashing with that Gapps...so I switched back to RR with micro Gapps.
Hello again,
Can you give me some info about this warning? I received this right after I updated my Nexus 5X to RR 5.8.2 .
"Ok Google" any time still doesn't want to activate .
Can anybody make a port of the Google phone app for our phone? The in-built version doesn't have the Google exclusive features, like Called ID, local business search, etc. which are supposed to ship with Android One devices. Simply trying to install the apk doesn't work, with the app saying "not compatible with your device".
Its available on XDA forum, just search google phone apk and install downloaded mod apk
Oh thanks.
Here's the link if anybody else is looking for it. Caller ID and Spam detection DO NOT work.
What i don't understand is why we don't have native support for the app, seeing how the Mi A1 is Android One, and all.
Just a heads up, version 11.0.164102751 as stated in op works best, the newer ones have bugs when calling someone from favorites tab. I installed just for the sale of the contact pictures in in call, because otherwise it looks very stupid with contact name and blue screen. For now I can live without nearby search and caller id.
You can install the older version of the Google dialer. Am attaching the file. The Caller ID picture and the local search both works fine. The only bug I saw was that in the Call logs, the incoming, outgoing & the missed calls symbols are messed up. Everything else works just fine.
Or install "google framework" Magisk module and after reboot you can install and use Google Phone app from Play store.. Caller ID, nearby search, favorites, logs, accept/reject call from notification work without any issues, at least I didn't encounter any problem.
Don't wait Use patched version
https://drive.google.com/file/d/0B4zm5uCToKPOa1dwSjFEWTAxbGc/view
Use it as default & disable stock phone app
Its working fine
Sent from my Mi A1 using XDA Labs
_mysiak_ said:
Or install "google framework" Magisk module and after reboot you can install and use Google Phone app from Play store.. Caller ID, nearby search, favorites, logs, accept/reject call from notification work without any issues, at least I didn't encounter any problem.
Click to expand...
Click to collapse
Which Magisk version do you have?
I tried to install Google Framework module on Magisk 14.5 but it failed... :-/
tonycapuozzo said:
Which Magisk version do you have?
I tried to install Google Framework module on Magisk 14.5 but it failed... :-/
Click to expand...
Click to collapse
It is working with official beta 14.4 and 14.5 and google framework module from repository. What error do you see?
_mysiak_ said:
It is working with official beta 14.4 and 14.5 and google framework module from repository. What error do you see?
Click to expand...
Click to collapse
See attached screenshot...
tonycapuozzo said:
See attached screenshot...
Click to expand...
Click to collapse
Which other modules did you install? Try total uninstall of Magisk (not only restore stock boot), reboot, install official beta 14.5 Magisk again and then install only Google framework module. I have been experiencing this with some old/unsupported (?) modules, they somehow damaged magisk.img and I couldn't install or update otherwise working modules anymore.
_mysiak_ said:
Or install "google framework" Magisk module and after reboot you can install and use Google Phone app from Play store.. Caller ID, nearby search, favorites, logs, accept/reject call from notification work without any issues, at least I didn't encounter any problem.
Click to expand...
Click to collapse
I did it and is working, but when i receive a call the screen stay off, i only can hear sound
FerrarisIV said:
I did it and is working, but when i receive a call the screen stay off, i only can hear sound
Click to expand...
Click to collapse
Don't forget to enable all permissions, including change of system settings. Mine works without any issues whatsoever.
_mysiak_ said:
Don't forget to enable all permissions, including change of system settings. Mine works without any issues whatsoever.
Click to expand...
Click to collapse
It already has... but also 2x zoom crash
Any idea?
FerrarisIV said:
It already has... but also 2x zoom crash
Any idea?
Click to expand...
Click to collapse
I missed something, 2x zoom in the dialer app?
_mysiak_ said:
I missed something, 2x zoom in the dialer app?
Click to expand...
Click to collapse
Sorry friend... It is my mistake!!!
I was talking of camera stock now, but it is not the right place.
Sorry again
FerrarisIV said:
Sorry friend... It is my mistake!!!
I was talking of camera stock now, but it is not the right place.
Sorry again
Click to expand...
Click to collapse
Hehe, no problem, just wasn't sure who was in the wrong topic
_mysiak_ said:
Hehe, no problem, just wasn't sure who was in the wrong topic
Click to expand...
Click to collapse
Anyaway i tried again, i also rebbot device but problem persist.
FerrarisIV said:
Anyaway i tried again, i also rebbot device but problem persist.
Click to expand...
Click to collapse
Haven't you disabled the notifications, or lowered their priority for the phone app? All I did was installed the google framework, installed the dialer, enabled all permissions, allowed system changes, set it as the default phone app and it works with no hiccups.
Edit: someone reported that ambient display doesn't work with disabled screen security feature (PIN, pattern,..) in December update - just for the troubleshooting purpose, make sure that you have pattern set with lock set to very short timeout and smart lock disabled and try calling your phone again.
_mysiak_ said:
Haven't you disabled the notifications, or lowered their priority for the phone app? All I did was installed the google framework, installed the dialer, enabled all permissions, allowed system changes, set it as the default phone app and it works with no hiccups.
Edit: someone reported that ambient display doesn't work with disabled screen security feature (PIN, pattern,..) in December update - just for the troubleshooting purpose, make sure that you have pattern set with lock set to very short timeout and smart lock disabled and try calling your phone again.
Click to expand...
Click to collapse
I wrong something in build.prop file and i had to flash orginal rom. So for some days no modding, pause for me
Thanks again for your suggestions
Hi,
Few month ago, I noticed that Ok Google doesn't work. I tried to configure the voice match with 4x "Ok Google" but it doesn't detect my voice. Same thing with Gboard when I'm tring to text with my voice, it cannot hear my voice.
Yesterday, I re-install all my OnePlus 5T with the last OxygenOS, I erased everything for a clean install. When I'm coming to the Voice match with 4x "Ok Google" it still doesn't work...
The mic is working with calls and videos but seems not working with Google Assistant and I don't know why !!!
The only thing that I did during the installation of OxygenOS was reinstall Magisk but when I'm looking for something about Magisk and Google Assistant, I found nothing !!!
Do you have any solution ?
Did you maybe accidentally deny it microphone permissions somehow? Check the Google app's permissions in your device's settings.
banana_bender said:
Did you maybe accidentally deny it microphone permissions somehow? Check the Google app's permissions in your device's settings.
Click to expand...
Click to collapse
I already saw permissions but microphone is on and just in case, I reinitiate all permissions but nothing...
I was on Open Beta since the OB17 and Google Assistant stopped working for me around the 30s. When OnePlus released the final stable OOS I clean installed it and got Google Assistant functionality back. Which OOS are you on?
I'm on the official and the last version of OxygenOS.
As I said, I did a clean install and the only things I let TWRP 3.2.3-1 codeworkx and re-installed Magisk.
I just followed this thread like I always did --> https://forum.xda-developers.com/oneplus-5t/how-to/official-oxygenos-4-7-2-7-1-1-ota-t3709265
Well, the only thing I didn't flash is the "xXx No Verity 4.0.zip", I don't know if it's very useful...
Don't shoot me, I've done some searching but found no answer...
Ok / Hey Google is not activating the Google assistant on my stock android 10, Nov 19 updated phone.
Squeeze works and manually starting the assistant works but not via speech. It always used to.
When I try switch it on in settings, it switches off saying '
Something went wrong. Try again.'
Anyone else had this? And if so how did you fix it?
Cheers
afr33s said:
Don't shoot me, I've done some searching but found no answer...
Ok / Hey Google is not activating the Google assistant on my stock android 10, Nov 19 updated phone.
Squeeze works and manually starting the assistant works but not via speech. It always used to.
When I try switch it on in settings, it switches off saying '
Something went wrong. Try again.'
Anyone else had this? And if so how did you fix it?
Cheers
Click to expand...
Click to collapse
I haven't had hotword detection problems in a while but try deleting Google App and OK Google Enrollment data then rebooting.
hawkswind1 said:
I haven't had hotword detection problems in a while but try deleting Google App and OK Google Enrollment data then rebooting.
Click to expand...
Click to collapse
How to delete the Google app? It's baked in on Pixel phones. Cheers.
afr33s said:
How to delete the Google app? It's baked in on Pixel phones. Cheers.
Click to expand...
Click to collapse
I meant wipe Google app's data. Settings>apps & notifications>see all apps>click show system from overflow menu. Then clear all data from Google and OK google enrollment and reboot then set up Google app settings again
hawkswind1 said:
I meant wipe Google app's data. Settings>apps & notifications>see all apps>click show system from overflow menu. Then clear all data from Google and OK google enrollment and reboot then set up Google app settings again
Click to expand...
Click to collapse
Did all that and sadly same result!
afr33s said:
Did all that and sadly same result!
Click to expand...
Click to collapse
Hmm. A few more ideas if you're interested in trying
1. type "trust agent" into search settings and make sure it's toggled on under security settings. Maybe try toggling it off, reboot, then turn it back on.
2. uninstall google app updates and see if it starts working (settings>apps>google>overflow menu)
If none of those work I would think about flashing the factory image from https://developers.google.com/android/images
hawkswind1 said:
Hmm. A few more ideas if you're interested in trying
1. type "trust agent" into search settings and make sure it's toggled on under security settings. Maybe try toggling it off, reboot, then turn it back on.
2. uninstall google app updates and see if it starts working (settings>apps>google>overflow menu)
If none of those work I would think about flashing the factory image from https://developers.google.com/android/images
Click to expand...
Click to collapse
Thanks for the help. 1 & 2 did not work.
Contemplating whether to do 3 or see if December update fixes my issue!
So I reinstalled Android 10 from factory image with ADB. Not the OTA. Did not reinstate any back up and still hey Google does not work... "There was a problem".
Pants!
try these steps that will completely bring back Assistant to as close to stock as possible without totally resetting the device...
go into Settings/Apps & Notifications/See all apps
*you may need to display “all apps”
Google Play Services
Clear data from within “storage & cache”
Assistant
Clear data from within “storage & cache”
Uninstall
open Google Play Store
Go to menu/sandwich bars in the top left location
Go to “My apps & games”
Re-search, download, & install Google Assistant
launch Google app
Go under the “More” tab section
Go & Select the “Voice” section
Select “Voice Match” section
Select “delete voice model”
Choose “retrain voice model” (if possible – I don’t wish to delete mine)
Follow prompts and re-set up voice match model…
Make sure “Access with Voice Match”
I had/have to frequently reset Google Assistant and “hotword” set up, so this is the steps I take to reset Assistant so it will respond to me saying the “hotword”….it works 95% of the time where the other 5% is rebooting my device and then running through all of these steps……
Hope this ends up being helpful and good luck!
afr33s said:
So I reinstalled Android 10 from factory image with ADB. Not the OTA. Did not reinstate any back up and still hey Google does not work... "There was a problem".
Pants!
Click to expand...
Click to collapse
I would try deleting and retraining your voice model.
I had noticed a while back that Ok Google wasnt activating assistant on my phone. I deleted the voice model and retrained it and Ok Google as been working fine now to activate assistant. So letting the OP know that this worked for me.
FFS. Have tried all methods suggested here and I can't get ok Google or get Google to work. It works in my old Yotaphone but not my Google Pixel! Go figure!
I guess I will learn to live without it.
Thanks for all your help.
March update has fixed my issue! Hey Google working well again no.
Mods please close this thread.
Thread closed at OP's request