Related
Google Assistant used to work seamlessly with Google Maps which began voice navigation promptly. Now assistant will take me to Maps but it only shows the route and no way to begin navigation (much less voice). Anyone with this problem? I've tried this on several ROMs with same result.
Daisymae said:
Google Assistant used to work seamlessly with Google Maps which began voice navigation promptly. Now assistant will take me to Maps but it only shows the route and no way to begin navigation (much less voice). Anyone with this problem? I've tried this on several ROMs with same result.
Click to expand...
Click to collapse
If I say a location to Google Assistant a box comes up with choices and selecting directions opens Google Maps. Pressing the car icon starts navigation. Are you trying to use Google assistant to start navigate without any physical interaction with phone?
Yes and it always worked before. All I had to do was ask assistant to take me to a destination. It would open maps and voice directions began.
Sent from my Nexus 6P using XDA-Developers Legacy app
Daisymae said:
Yes and it always worked before. All I had to do was ask assistant to take me to a destination. It would open maps and voice directions began.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
If I say a location to Google Assistant a box comes up with choices and selecting directions opens Google Maps. Pressing the car icon starts navigation. Are you trying to use Google assistant to start navigate without any physical interaction with phone?
Click to expand...
Click to collapse
Sent from my Nexus 6P using XDA-Developers Legacy app
When did it stop working like that?
Not sure exactly. I flash ROMs constantly and hadn't tried this feature in a while. In fact I can't get voice navigation in Maps even if I open that application directly. If I hit the start button after entering a location it just shows the route but nothing else happens. ?
6P, 7.1.1, nmf26f: this happens to me in my vehicle and i turn the bluetooth connection to my car audio (android 5.1.1) off and she begins to tell me what to do again. ymmv.
Hmmm. Don't know about that. I did notice the "while driving" (works with google maps) toggle on ok google detection is grayed out.
Edit--The problem isn't with GA it is with Google maps. I tried all the things I found on the net (turning off bluetooth, turning off play voice over bluetooth in map settings) still no voice navigation.
When you are navigating there should be a little speaker icon under the magnifying glass. Did you try toggling that? It can mute and unmute voice navigation. If you are on a custom ROM you can also try reinstalling GApps.
Thanks. Tried both of those but still doesn't work. Uninstalled maps and reinstalled also. Still no voice navigation.
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
rhickers said:
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
Click to expand...
Click to collapse
Didn't work for me. Oh well, I guess I'll just have to wait.
Gary
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
astephon88 said:
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
Click to expand...
Click to collapse
Alright, I let it sit for a couple hours, and it's working now. Though, still can't launch it from the microphone button in the google app or the google search bars on the home screens. That still launches the old voice search. Have to long touch the home button or use the "ok google" launch phrase. It's a shame it can't use the always-on mic from moto voice though.
I'm seeing some similar things. Google Assistant came down to my phone automatically. Set up the OK Google voice command. Seems to work fine when launching from the mic button on the assistant, but will not respond to always on mic when the phone is idle.
You do have to disable Moto Voice, or change the voice phrase to something other than OK Google. Phone still responds to Moto Voice command on idle, but not OK Google.
Yea, so unless there's a software update for Moto Voice, we're likely not going to get the always-on mic to work with assistant. There's a dedicated processor on the SoC that handles the always-on mic, and it's tied directly to Moto Voice. Moto voice really doesn't do a whole lot other than listen for the launch phrase. Everything after that point is basically handed off to Google Voice search. It really should be quite a easy fix (pass the requests onto assistant instead of voice search), but I doubt that will happen.
smiley4017 said:
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
Click to expand...
Click to collapse
I woke up this morning and I finally got the assistant. just an FYI
I got it too. However, while it unlocks the phone when locked and the screen being on, it will not wake the phone when saying ok google. You hear the sound prompt that it heard you, but nothing ever follows up and the screen stays black
I've rooted my J320A, installed the beta versions of Google Play Services and the Google App, cleared all storage for each app and I'm still not seeing Google Assistant. Is anyone else having this problem?
mines not rooted, but i'm having the same problem
I have a stock SM-J327P with the beta Google App and Google Play services too and it's not on my phone yet either.
---------- Post added at 02:13 AM ---------- Previous post was at 01:40 AM ----------
Also we could try posting to https://productforums.google.com/forum/#!msg/websearch/RC1pw4QhcfE/GCZx2ZbMBgAJ with answers to Ron's and hopefully prompt a better response.
Maybe im confused, but isnt the screenshot google assistant?
Didnt do anything, just updated stock thru playstore.
Guess what I posted above isn't assistant, just Google on tap...I've tried a lot to get this working
The non rooted methods out there can get to assistant in a round about way (launching some settings menu), but after assistant is activated I still could not launch it.
Using current versions of Google app the only way I could access assistant is thru rooted terminal, using the following command
Code:
am start -n "com.google.android.googlequicksearchbox/com.google.android.apps.gsa.staticplugins.opa.OpaActivity"
But typing that is a half and I couldn't come up with a practical way of using (I plan to learn tasker tho, that might help)
Only decent way I can launch it is by using an old version, 6.11.21.21 works. And installing the xposed module assistant enabler (n-ify's experimental settings has this feature too)
You must also disable auto update in your play store.
Using old versions has it's drawbacks. For instance Pixel launcher doesn't get read your weather card, so no weather widget. Who knows what else.
[EDIT]
I was able to update and it still work, it didn't last tho... Needs more testing
[/EDIT]
DamienMc said:
I was able to update and it still work, it didn't last tho... Needs more testing
Click to expand...
Click to collapse
Great work! Any further progress on this?
sjowns said:
Great work! Any further progress on this?
Click to expand...
Click to collapse
Nah havent really messed with tasker yet.
Only really have time to play on the weekends, and worked on another project last weekend (that alt root thing). Now with the holliday im not sure what ill have time for...i did work out the highest version assistant enabler works for us tho (6.13.25.21 works)
Ill be sure to report any updates
Think this is the best i can do with tasker using the command above (and updated google app)
Install tasker and autovoice
In tasker click the profile tab and import the two attached profiles
In autovoice goto google now
Choose not enabled
Turn on both autovoice and tasker accessibility options
Back out then check enable and uncheck voice only
Now goto advanced and check always cancel
And thats it
Now when you say 'ok google' (or use voice search) voice search will popup and close and google assistant will launch...holding the home button will bring up on tap, auto close and launch assistant.
It will probably fail the first time, but itll work afterwards.
Also the first time you open the google app itll activate assistant, but again, itll work afterwards.
Enjoy
-D
Btw im still looking for another method, i dont like the delay
I had a little luck using Google Assistant Launcher, which seems to launch the same intent you suggested and may be easier than messing around with tasker.
Here's what I've done:
De-enroll from the Google App beta, uninstall the beta, and then install the latest (non-beta) Google app.
Then run the Google Assistant Launcher and click on the "My Stuff" tab, create a new reminder and train the voice model
Go to settings / apps / defaults and change the default assistant to Google Assistant Launcher
If the Assistant Launcher doesn't launch the Assistant, clear storage for the Google app and Google Play services and try again
sjowns said:
If the Assistant Launcher doesn't launch the Assistant, clear storage for the Google app and Google Play services and try again
Click to expand...
Click to collapse
Hmm for me this would always bring up the settings were you set the reminder
[Edit]
Google app must have changed. Now what you wrote will bring up plain old voice search here...what version are you on?
[/Edit]
DamienMc said:
Think this is the best i can do with tasker using the command above (and updated google app)
Install tasker and autovoice
Click to expand...
Click to collapse
So, I have Tasker and AutoVoice. I am running your (@DamienMc) "pixel experience" ROM for J320A with root and Xposed. When I try to enable AutoVoice's accessibility setting, it tells me "Universal switch does not support the current system language. The text to speak language will be set to English (United States), but this might cause unexpected behavior." I click Turn On, and then it says unfortunately, settings has stopped. This happens every time I try to enable any accessibility setting for any app. So please consider this in an update to your ROM.
sjowns said:
I had a little luck using Google Assistant Launcher, which seems to launch the same intent you suggested and may be easier than messing around with tasker.
Here's what I've done:
De-enroll from the Google App beta, uninstall the beta, and then install the latest (non-beta) Google app.
Then run the Google Assistant Launcher and click on the "My Stuff" tab, create a new reminder and train the voice model
Go to settings / apps / defaults and change the default assistant to Google Assistant Launcher
If the Assistant Launcher doesn't launch the Assistant, clear storage for the Google app and Google Play services and try again
Click to expand...
Click to collapse
The Assistant Launcher is working for me. However, pressing and holding the home button does not work.
I have Google Assistant on my phone and I installed it without rooting my phone I found the following video that shows you how to install Google Assistant on any Android phone without having to root the phone.
https://www.youtube.com/watch?v=pSP6gICNfLY
Just install Google Assistant Launcher apk(180kb) and update Google Application to latest version.
Press and Hold home button, and voila Google Assisten Launched
How about the Assistant Enabler Xposed module? DamienMc added it to the J320A ROM. It works great
I think that's work.
Try ^^
Maybe i was trying the wrong app when I tried. Only one I see is 149kb
DamienMc said:
Maybe i was trying the wrong app when I tried. Only one I see is 149kb
Click to expand...
Click to collapse
Nope, it's right app ^^
I have Samsung galaxy j3 and qhen nnyni try to install Google assistant it say,"this version is not compatible with your device." So I deleted date from Google and Google play services plus I became beta tester. And guess what.GOOGLE ASSISTANT STILL WAS NOT ABLE TO BE INSTALLED ON MY DEVICE!!!!! I NEED HEEELP!!!
I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
SomebodySysop said:
I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
Click to expand...
Click to collapse
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
SomebodySysop said:
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Click to expand...
Click to collapse
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
SomebodySysop said:
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
Click to expand...
Click to collapse
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
Acoustichayes said:
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Click to expand...
Click to collapse
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
SomebodySysop said:
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
Click to expand...
Click to collapse
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
SomebodySysop said:
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
Click to expand...
Click to collapse
My apologies for not responding! Got caught up with root searching and things of the sort. But im glad you figured it out!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
FINALLY! This is how you link AutoVoice (or any 3rd party app) to Google Assistant: https://productforums.google.com/d/msg/websearch/HwJUpkrHPr4/xIJACIlEAwAJ
So, you have to say "OK, Google, ask Autovoice to...." followed by your AutoVoice command. Still wish I could just say "OK, Google" then command, but this will do for now.
Have You got any ideas, how to force phone to use GA commands, instead of google app voice commands? The only way to use it I know, is to say "open assistant" and then use final verb. But awakening twice every time?
Hey man
I installed automagic and configured a flow that launches google assistant when the google search application runs
The flow has some conditions, so that google assistant doesn't run when I'm manually searching in google
Unfortunately it is not perfect, because it doesn't automatically run google assistant with the screen off, you have to say the command "open assistant" to launch it, but if it works in any other situation
I'm looking for some way to modify the moto voice apk to change google now to google assistant by default, but I don't know enough about programming, so it's still a long way off
If you have any news about it, I would appreciate it if you let me know