Related
Hello,
i have strange bug (?), i have installed cm13 android 6 with pico opengapps, my problem is, when i try to configure google now, it's only show detect 'OK google from app', on stock i have 3 options, from app, from any screen and last was something about unlocking device, so i'm just curious what's going on, where is google now on tap and other stuff.
Thanks for help and regards
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.
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?
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...
Thanks LineageOS team for the source.
First boot takes time, just wait patiently
What works:
Audio
WIFI
USB
BT
Camera
Gravity
HW video fixed Thanks Tegra team( @Steel01 and others ) for the fix. Link for fix.
Not works:
GPS.
LTE version , don't work LTE. Use WiFi version.
Device Tree : (Force encryption disabled)
https://github.com/LineageOS/android...e_htc_flounder
Kernel https://github.com/vartom/android_kernel_flounder/tree/gtest+mm215SB+O
Lineage-15.1-20200313-UNOFFICIAL
Changes:
- fix sepolicy
- selinux = enforcing
Download Lineage Builds: (03/13/2020)
Lineage-15.1-20200725-UNOFFICIAL
Changes:
- Google security updates
Download Lineage Builds: (07/25/2020)
Great, friend! Congratulations!
Just when you think "Nexus development is no more" along comes Vartom. Thank you
Everything seems smooth. A couple of observations so far:
- Lost Vulkan. Not sure if I will miss it though.
- LiveDisplay can't turn on. The setting doesn't stick.
Thanks for putting up your work. Greatly appreciated
Thanks for your work. It works well for the most part, performance is good.
2 issues I've found so far:
- LiveDisplay doesn't work
- Setting screen lock pattern makes SystemUI unresponsive for a long time (it will finish eventually), and when unlocking first time after setting pattern, it may also stuck a little while. Pin or password not tested, but I guess they would be same, because this also happens after reverting screen lock to just swipe.
iKirby said:
- Setting screen lock pattern makes SystemUI unresponsive for a long time (it will finish eventually), and when unlocking first time after setting pattern, it may also stuck a little while. Pin or password not tested, but I guess they would be same, because this also happens after reverting screen lock to just swipe.
Click to expand...
Click to collapse
I can confirm the issues with the lock screen.
Thank you Vartom for all your hard work!
is there a possibility to get this one ot work on l t e model as well. willing ot test for you.
mrk2815 said:
is there a possibility to get this one ot work on l t e model as well. willing ot test for you.
Click to expand...
Click to collapse
You can install the wifi version. Testing the LTE version does not make sense. It is already clear that the drivers for supporting the LTE modem do not work correctly.
thanks will take a look. again do i have to decript to install this build as i have an unofficial lineage 14.1 build on the device, but i am not sure if its decripted or not. how do i go about decripting it to isntall your build. thanks again for keeping he device alive with the issue it had with HW video playback.
---------- Post added at 08:10 PM ---------- Previous post was at 07:32 PM ----------
what are the recommended gapps to use for the installation.
Thank you very much for your work!!!!!!!!!!!!!!!!!
Can I Flash this Rom in LTE device?
Sent from my ELE-AL00 using Tapatalk
sheenswizner said:
Can I Flash this Rom in LTE device?
Sent from my ELE-AL00 using Tapatalk
Click to expand...
Click to collapse
I just flashed this Rom on my LTE model!
This Rom is fantastic and butter smooth!
Special thanks for devs for hard work and makes smiles on our faces.
Sent from my Nexus 9 using Tapatalk
mrk2815 said:
thanks will take a look. again do i have to decript to install this build as i have an unofficial lineage 14.1 build on the device, but i am not sure if its decripted or not. how do i go about decripting it to isntall your build. thanks again for keeping he device alive with the issue it had with HW video playback.
---------- Post added at 08:10 PM ---------- Previous post was at 07:32 PM ----------
what are the recommended gapps to use for the installation.
Click to expand...
Click to collapse
I used opengapps for arm64 8.1 micro. Regarding decryption, I did not check the performance of encryption, but judging by the reports of a problem with unlocking, encryption can also be a problem. I did not check this moment.
I've installed it tonight from 14.1 - booted into TWRP, factory wiped, added 15.1 zip and gapps, installed, wiped caches then rebooted in less than 10 minutes.. Amazing the difference in speed, very quick. All my apps installed a lot quick than previous version did.
I'm not having the slow down at the lock screen (using PIN).
I am however unable to install Netflix from the Play store (not compatible with your device), and using the apk results in an error "This device is not supported by the app".
Fubsy said:
I've installed it tonight from 14.1 - booted into TWRP, factory wiped, added 15.1 zip and gapps, installed, wiped caches then rebooted in less than 10 minutes.. Amazing the difference in speed, very quick. All my apps installed a lot quick than previous version did.
I'm not having the slow down at the lock screen (using PIN).
I am however unable to install Netflix from the Play store (not compatible with your device), and using the apk results in an error "This device is not supported by the app".
Click to expand...
Click to collapse
I think that it is connected with DRM, I will check it.
For some reason, I can't get past setup. I'm stuck at the voice assistant step of setup after flashing and factory resetting.
If I accept to use Google Assistant, I am required to train it to my voice with "ok Google" except nothing happens. Or I can tap no thanks, which should skip this section. Only, no thanks loops back to the beginning of the voice assistant setup. How do I move forward?
Fubsy said:
I am however unable to install Netflix from the Play store (not compatible with your device), and using the apk results in an error "This device is not supported by the app".
Click to expand...
Click to collapse
I have no problem installing and using Netflix. I had to select Google Play Services in Magisk Hide for Netflix to appear on play store. Alternatively, IIRC, the APK from apkmirror worked too.
gk1984 said:
For some reason, I can't get past setup. I'm stuck at the voice assistant step of setup after flashing and factory resetting.
If I accept to use Google Assistant, I am required to train it to my voice with "ok Google" except nothing happens. Or I can tap no thanks, which should skip this section. Only, no thanks loops back to the beginning of the voice assistant setup. How do I move forward?
Click to expand...
Click to collapse
Pass the Google assistant wizard twice and done!
I tried to ignore but still showing me in settings !
Sent from my Nexus 9 using Tapatalk
sheenswizner said:
Pass the Google assistant wizard twice and done!
I tried to ignore but still showing me in settings !
Click to expand...
Click to collapse
But how? The voice training step won't accept my voice. I speak ok Google and nothing happens. I try to skip it and it loops back to the assistant settings again. There is no passing it. Every time I say no thanks, it loops back again. I've tried countless times. And I don't understand why it won't accept my voice either.