Related
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.
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 .
I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?
Keeps resetting at the Bring your data from... step.
Whether I tap 'Don't Copy' or 'A backup from the cloud'. It attempts it, then just goes back to the same screen. Then after a second or third attempt it says Android Setup keeps stopping and I can only close the app.
Everything seems to be fine though, I can use my phone like normal. Just every time I pull down notifications, there is that bug blue notification that I need to continue with Setup.
I installed the mini MindTheGapps package if that could have anything to do with it.
Should I just reset everything and start over? Dont want to if possible since I have set up everything else at this point heh...
I have read other threads about this issue over the years but nothing has seemed to help.
Not sure if relevant but this in on a Oneplus One
Thank you all.
Thats a GApps issue. I don't use that Google APPs
The only solution I've seen to that is reinstall LOS (and twrp 3.3.3 if you want), reboot to recovery, install gapps, reboot to system. I believe I got that flow from one of the install guides.
I'm going to assume you also didn't get the full google login experience setting language and account and all that jazz either.
I've had to do the same as above for a LOS update too which is a bit annoying. But I have not experimented too much.
Hi all,
I've tried to update my chrome application (the pre-installed on my Global Poco F3 which is under MIUI Global 12.02 stable global) I have tried multiple times to update the Chrome app from the Google Play Store with no success to this day.
I've investigated using adb logcat and I've seen a specific error trigger itself :
4-10 00:34:14.008 17140 17170 E Finsky : [993] tvh.apply(44): IQ::GROUP_INSTALL: Error validating group. Rejecting requests: [com.google.android.trichromelibrary, com.android.chrome]
04-10 00:34:14.008 17140 17170 E Finsky : com.google.android.finsky.installqueue.impl.preprocessor.GroupInstallValidator$InvalidGroupException: GROUP_INSTALL: Group com.google.android.trichromelibrary and com.google.android.trichromelibrary have overlapping module [com.google.android.trichromelibrary, com.android.chrome]
Obfuscated long Java backtrace...
Click to expand...
Click to collapse
I have tried to update chrome on a Redmi Note 8 pro without success as well. However, under LOS (Lineage OS 18.1) another phone has successfully updated the Chrome app, meaning this issue is probably not due to a weird Google Play Store bug but most likely due to MIUI 12.
Anyone has encountered this issue ? And is there any way we could work around this ? (instead of waiting for a potential fix in MIUI 12.5)
Thanks for any help on this matter, I can provide the whole backtrace if anyone want to see it but I doubt it would help anyway since she looks pretty obfuscated to me (the only thing I could understand was some execute function being called but all the classes names have been randomized and most functions call names too).
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
UPD: Or you can download right now from apkmirror.com, if you want
Xoby said:
Hi! This is usually a problem for those who have set up the system for the first time. I also encountered this, after a while Google Chrome was updated on its own. The same applies to the Android System WebView application. Wait for a while and the app will update.
Click to expand...
Click to collapse
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
AkechiShiro said:
But my Redmi Note 8 Pro isn't brand new, but I still encounter an issue to upgrade Chrome at least, I'm not too sure how long should I be waiting ? (like 6 months or just even a few weeks I guess ?)
Click to expand...
Click to collapse
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
I cannot understand the mistake. I updated Chrome to the latest version 3 days ago.
Xoby said:
Okay, try log out from your Google account, then clear data & cache Google Play Services, Service Framework and Google play store too, then reboot and login again, but not sure about this method
Click to expand...
Click to collapse
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
AkechiShiro said:
You were correct, I had unfinished the device configuration (the first time you have to connect your Google account etc.) hence it didn't work to update Chrome and Android Web View, I just finished it right now and Chrome did successfully update. That's weird I think Android should change (if this issue is at the Android level).
In the end I didn't need to do all this logging out, clearing data & cache and so on, just finishing the device configuration solved the issue.
Click to expand...
Click to collapse
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Fabio Bertelli said:
Hey mate, what did you exactly did for solve this?
I'm facing the same problem for update my chrome and web view.
Click to expand...
Click to collapse
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
AkechiShiro said:
I had a somewhat permanent notification that said something along the lines of "Finish configuration of your device" I clicked on it and then I pressed next and tweaked the last options, once that notification was cleared, all the Google Apps kinda of updated themselves somehow (I saw some of them even reinstalled themselves that was a bit weird but everything went fine afterwards).
Click to expand...
Click to collapse
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Fabio Bertelli said:
Thank you for your help.
Unfortunately I didn't have this message to "Finish configuration". So, I followed a tutorial on internet and erase all Google play store and Google Play services data.
After that rebooted the phone and put my information again on Play Store and than the update starts working for it self.
Click to expand...
Click to collapse
Good thing you figure it out, and also thanks for explaining how for others who will face this issue, maybe sometimes the notification disappears for some reason or the configuration doesn't finish successfully and this issue happens.