Google Assistant on 6.0.1? - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

Has anyone successfully gotten Google Assistant to work on their Turbo? I'm rooted running Xposed with the Assistant Enabler module, but no luck. Thanks for your advice in advance.

Yes. I have an XT1225 but am running RR 6.1 with Nova Launcher and xposed module Assistant Enabler.
In Nova Launcher I have OK Google hotword enabled. Not sure if all that makes a difference (using Nova Launcher), but even with my phone locked (pattern code), I can say "OK Google" and the Google Assistant will unlock the phone and verbally answer.
I know you are running rooted stock, but I can't see how that makes any difference since it's xposed module doing the work.

Related

Moto Voice on KitKat after downgrade from Lollipop

I have an unlocked XT1060 (not dev edition). Was running Krypton 1.4 KitKat (4.4.4) for a long time, but decided to try out Lollipop. Didn't like it, so restored KitKat from TWRP backup. Everything is working fine, except Google Play Store is showing an update for Moto Voice app. If I install this update, it prompts me to retrain activation phrase, but microphone doesn't recognize any sound during retraining, and "OK Google Now" doesn't work. If I uninstall the Moto Voice update, "OK Google Now" works again. Any way I can prevent Play Store from wanting to update Moto Voice?
DudeWaffle said:
I have an unlocked XT1060 (not dev edition). Was running Krypton 1.4 KitKat (4.4.4) for a long time, but decided to try out Lollipop. Didn't like it, so restored KitKat from TWRP backup. Everything is working fine, except Google Play Store is showing an update for Moto Voice app. If I install this update, it prompts me to retrain activation phrase, but microphone doesn't recognize any sound during retraining, and "OK Google Now" doesn't work. If I uninstall the Moto Voice update, "OK Google Now" works again. Any way I can prevent Play Store from wanting to update Moto Voice?
Click to expand...
Click to collapse
Fixed it. In case anyone else runs into this problem, the solution was to turn off Touchless Control in settings and then freeze it using TB, reboot, defrost Touchless Control, allow Play Store to update it, then enable in settings.

Long-press for Google Now not working

Since I have installed SLiMM ROM,specifically version 3.1,long-press for Google Now doesn't work,before I used to set a custom action to open the Google App with GravityBox to open the Google app.
The problem is now I want the Google Assistant to work,but that trick doesn't work since it only opens the Google app,and if I do go to the settings of the app it does say "Assistant Settings" so I know that part is good.
Any advice?

Google Assistant - Any way to change the "OK Google" hotword?

there used to be a way to do this pre-Nougat, but all i'm finding in my searches is that this is not possible on Nougat.
i'm running FreedomOS 2.6.1-1, Android Nougat 7.1.1.
does anyone know if there IS a way to do this?
Play Store ... search Replace OK Google
Sent from my ONEPLUS A3000 using Tapatalk

Google app wake lock

Hi guys,
My Google app is triggering tons of wake locks. Any of you encountered similar problem?
Already tried wiping the Google play services data.
Thanks in advanced.
Do you have Google Assistant always detecting voice when the screen is off?
Anova's Origin said:
Do you have Google Assistant always detecting voice when the screen is off?
Click to expand...
Click to collapse
Just disabled that. I'll see how it works out tomorrow.
Thanks bro.
JayYip said:
Just disabled that. I'll see how it works out tomorrow.
Thanks bro.
Click to expand...
Click to collapse
That would have been my thought, that the Google app would need to have a wakelock in order to detect the "OK Google" phrase when the screen is off.
What ROM you running? On my (stock OOS 4.1.1) Battery screen, the stop app right now has that same icon, but says "Google Play Services", so not sure if that is related to the Google app (Google Assistant).
redpoint73 said:
That would have been my thought, that the Google app would need to have a wakelock in order to detect the "OK Google" phrase when the screen is off.
What ROM you running? On my (stock OOS 4.1.1) Battery screen, the stop app right now has that same icon, but says "Google Play Services", so not sure if that is related to the Google app (Google Assistant).
Click to expand...
Click to collapse
I'm running OB4. That seems is the problem. But need more time to collect data to confirm it.
I have enabled Google assistant for a pretty long time and didn't have this problem until now. Not sure who to blame though.
redpoint73 said:
That would have been my thought, that the Google app would need to have a wakelock in order to detect the "OK Google" phrase when the screen is off.
What ROM you running? On my (stock OOS 4.1.1) Battery screen, the stop app right now has that same icon, but says "Google Play Services", so not sure if that is related to the Google app (Google Assistant).
Click to expand...
Click to collapse
After disabling the 'OK Google', my device can doze now. However, the wakeup triggers of Google app is still like crazy... And I use adb top command to see what is eating up my battery. I think that is exactly Google app.
I thought it's because of the OS, so I flashed OOS 4.1.1. But the problem remains. Now I can only get around 3 hours SOT now. It's affecting my life...
Please help... I don't know what to do now.
Are you sure you're not using Google Assistant?

Voice wake up Google App

So I use the "ok Google" wake up feature quite a bit, but a couple of days ago it just stopped working and the on off setting for it is grayed out. Any ideas? I'm running stock.
GadgetMonger said:
So I use the "ok Google" wake up feature quite a bit, but a couple of days ago it just stopped working and the on off setting for it is grayed out. Any ideas? I'm running stock.
Click to expand...
Click to collapse
May be something that inadvertently made Bixby the default assistant? (Just ballparking) Also I've been going nuts wondering why sometimes when I access APPS I have to re-register for some... Found out it was because I had left Secure Folder active in my button array.
Sent from my Sprint Samsung Galaxy Note 8 using XDA Labs
I thought about that too. Google is still my default assistant app. It comes up and works fine when I hold my home button. Might try disabling Bixby all together.
Bixby should work with Google Assistant perfectly fine. Have you installed any other voice app? Cortana? Alexa?
Try to re-train Google for your voice again if you can.
Was Google Assistant updated recently?

Categories

Resources