I think I saw it as something different once in a review but I can't remember. Could I change it to like 'Google' or something else?
Hopefully I'll have my own Moto X soon!
I'd love for this to happen, but afaik it's not something we can change.
stearic said:
I'd love for this to happen, but afaik it's not something we can change.
Click to expand...
Click to collapse
Perhaps when some ROMs start being made? I'd love to say "JARVIS" to call Google Now.
Epsilon707 said:
Perhaps when some ROMs start being made? I'd love to say "JARVIS" to call Google Now.
Click to expand...
Click to collapse
I wanted to say "Computer", a la Star Trek. Maybe not on touchless control, it'd be nuts, having the phone turn itself on I mention the word "computer". But with headset or stuff like that? "Computer. How's the weather like?"
I've gotten it to work just saying 'Okay Google......now' during the training.
Now I can just say 'Okay Google' and it activates. I don't know if this will work with anything else, and at times it activates when I didn't mean for it to, but I like it better than 'Okay Google Now'
I trained mine just by saying "okay Google" I didn't even need to say "now".
I always can activate it by saying "Hey Google"
The only problem with shortening the activation phrase is I noticed it would activate and start listening when I was talking to someone sometimes. It accidentally 'thinks' it hears the phrase when I said nothing near it.
Sent from my XT1058 using xda app-developers app
I want mine to respond to "ok R-2"
jncryer said:
I want mine to respond to "ok R-2"
Click to expand...
Click to collapse
Not" Jarvis" from iron man? You could mount it to your arm and be like Tony Stark lol.
Sent from my XT1058 using xda app-developers app
Xaroc8 said:
Not" Jarvis" from iron man? You could mount it to your arm and be like Tony Stark lol.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Lol. Either way, I'd like to think that I look cool using that feature, but in reality I'd look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I use "OK google" to record the command, and it works fine, it won't activated when I just easily say "google"
desperadoxzg said:
I use "OK google" to record the command, and it works fine, it won't activated when I just easily say "google"
Click to expand...
Click to collapse
Yeah setting it to "OK Google" worked for me too and seems to recognize it better.
ok google works for me too, since i use this alot, im happier
Got it to recognized k google
Edit k oogle works
Sent on my Moto X
flashallthetime said:
Got it to recognized k google
Edit k oogle works
Sent on my Moto X
Click to expand...
Click to collapse
Step by step, getting it to just "'ey g!".
Was just able to set up touchless controls with the wake phrase "OK moto" I trained it by saying "OK moto.. Google now" with a slight pause between moto and Google... Works pretty well, not as good as "OK Google now" does... But at least I know it can be done
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 12:00 PM ---------- Previous post was at 11:53 AM ----------
Just retrained as "hey moto" and it works just as good as "OK Google now" but I'll see how it works in the field, but it has no problem picking up the phrase in a noisy room.
Sent from my XT1058 using XDA Premium 4 mobile app
theraffman said:
Was just able to set up touchless controls with the wake phrase "OK moto" I trained it by saying "OK moto.. Google now" with a slight pause between moto and Google... Works pretty well, not as good as "OK Google now" does... But at least I know it can be done
Sent from my XT1058 using XDA Premium 4 mobile app
---------- Post added at 12:00 PM ---------- Previous post was at 11:53 AM ----------
Just retrained as "hey moto" and it works just as good as "OK Google now" but I'll see how it works in the field, but it has no problem picking up the phrase in a noisy room.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When I tried things like this I found it always wakes up randomly too much. I think its because the algorithm used to compare must have something to do with the three words and not just what you say during the training. What I'm trying to say is that it now thinks you say ok google now like ok moto or whatever you chose. This seems to make it finicky and wake itself up far too often. Even in class with just a professor talking my phone was waking up a few times.
jayboyyyy said:
When I tried things like this I found it always wakes up randomly too much. I think its because the algorithm used to compare must have something to do with the three words and not just what you say during the training. What I'm trying to say is that it now thinks you say ok google now like ok moto or whatever you chose. This seems to make it finicky and wake itself up far too often. Even in class with just a professor talking my phone was waking up a few times.
Click to expand...
Click to collapse
Undoubtedly. When I trained it for "OK Google now" it almost never randomly woke up during conversation. When I trained it for "OK Google" it would occasionally wake up during random conversation, and with "hey moto" it was waking up quite often... What's funny, is that the only time it ever wakes up randomly is when I'm with one my employees... Even with "hey moto" it would be fine for the most part, but as soon as he gets in my truck and we start talking, sure enough it starts waking up, doesn't really happen with anyone else. Definitely seems as though, the shorter the wake up command, the more prone it is to false positives... Which makes a lot of sense.
The "hey moto" though convenient wasn't ideal for consistent operation... It works great for the first few hours, but then it would take 2 or more tries to get it to recognize the command. Went back to"OK Google" hopefully, in the future, Motorola or developers will tweak this system to add different command phrases, but if not, it still works great if used as intended.
Sent from my XT1058 using XDA Premium 4 mobile app
My problem is that I trained it with the phrase "OK, Google Now," but it seems to start after "OK Google" a large percentage of the time. This messes up the command. When I say "OK Google Now, text Tom hello," it should record "Text Tom hello" and show a card to text contact Tom with the message "Hello." However, often the words showing up in the search will read "Now text Tom hello," and Google does a search rather than executing the command. It is frustrating. I tried just using "OK, Google, text Tom hello," but this fails to activate it. I think I will try retraining it this afternoon to "OK Google."
Paddington said:
My problem is that I trained it with the phrase "OK, Google Now," but it seems to start after "OK Google" a large percentage of the time. This messes up the command. When I say "OK Google Now, text Tom hello," it should record "Text Tom hello" and show a card to text contact Tom with the message "Hello." However, often the words showing up in the search will read "Now text Tom hello," and Google does a search rather than executing the command. It is frustrating. I tried just using "OK, Google, text Tom hello," but this fails to activate it. I think I will try retraining it this afternoon to "OK Google."
Click to expand...
Click to collapse
Yeah i was trying to get my wife to set it up on her Droid Mini, and i noticed this exact problem. "Okay Google" may be the way to go.
I got it to accidently accept bu** s**t, i was playing call of duty black ops and I said bu** s**t and it activated touchless control search, twice
Sent on my Moto X
Related
Is there a possibility of stopping Moto Voice to say "opening google.." every time it passes the command to ggl search?
It didn't do that before i updated moto voice. And is really annoying
sent from XT1092 using Tapatalk
It is. I'm also finding out that the "what's up?" command is very hit or miss. Sometimes it reads my notifications and others it just looks up "what's up" in Google.
I am also looking for the answer for shutting down "opening google"...can someone tell us how, please! Thanks!
This is from the update right? Id uninstall the updates. Revert back to the old version
But the old version is really bugy and missing many commands like "good morning" "talk to me" "good night" etc.
All in all the update is very good! Only "opening google.." disturbs me
sent from XT1092 using Tapatalk
gotzaDroid said:
It is. I'm also finding out that the "what's up?" command is very hit or miss. Sometimes it reads my notifications and others it just looks up "what's up" in Google.
Click to expand...
Click to collapse
The command is supposed to be "what's new?" I think. The video tutorial says what's up, but the command list says what's new.
GRS10 said:
The command is supposed to be "what's new?" I think. The video tutorial says what's up, but the command list says what's new.
Click to expand...
Click to collapse
I think it depends on your system language.
For me in English(US) it is "what's up?" and in German it is "Was gibt's Neues?"
So i would say "What's new?" Is for English(UK) may be..
__________
sent from XT1092
I hate this so much.
OliveJeans said:
But the old version is really bugy and missing many commands like "good morning" "talk to me" "good night" etc.
All in all the update is very good! Only "opening google.." disturbs me
sent from XT1092 using Tapatalk
Click to expand...
Click to collapse
None of those commands work for me. Good morning, good night, talk to me, they all just come back with opening Google followed by a Google search result in those words.
Hating that opening Google part.
Sent from my XT1095
Im also hating this "opening google" makes me feel like it took away what made this phone special. Its like now the only thing special is i can wake it up with my voice when the screen is off
Well, Google is grabbing just about everything that Motorola developed and adding it into lollipop.
tgerbracht said:
Well, Google is grabbing just about everything that Motorola developed and adding it into lollipop.
Click to expand...
Click to collapse
Gotta take advantage of all that intellectual property while you still can.
I get it and they probably developed it all while owning Motorola, but it will likely unlock "me" to buying outside of Motorola again if they can simulate active notifications, assist, and voice well enough. First time I've bought the same manufacturer back to back in the past four years and 8-10 phones.
gotzaDroid said:
Gotta take advantage of all that intellectual property while you still can.
Click to expand...
Click to collapse
Google keeps the intellectual property. That's all they wanted with the purchase, and they aren't giving it up with the sale.
Sent from my XT1095
opening google
Also hate "Opening Google" can't wait for lilipop to enable okay Google natively on my Moto X from standby (off) mode.
umdkevin said:
Also hate "Opening Google" can't wait for lilipop to enable okay Google natively on my Moto X from standby (off) mode.
Click to expand...
Click to collapse
If i have to wait that, i will sell my moto x.
I bought this for the voice command instead of my beautifull Nexus 5. I paied 499€ to have a nexus 5.2 with wood back? No thank's.
Opening google !!!
Yeah, this last update to Voice addressed the latency issues, but created a whole new set of problems as "set alarm" now just gets passed to Google instead of actually setting the alarm. If I have to actually click "Set Alarm" on the resulting Google search page, it kind of defeats the point of having it be a voice command. I'm hoping that their "solution" for the high latency of the original version wasn't simply punting and handing everything over to Google.
Motorola needs to get a third rev of this out, hopefully without regression bugs. And from their forums, it looks like they're on the case.
sogrady said:
Yeah, this last update to Voice addressed the latency issues, but created a whole new set of problems as "set alarm" now just gets passed to Google instead of actually setting the alarm. If I have to actually click "Set Alarm" on the resulting Google search page, it kind of defeats the point of having it be a voice command. I'm hoping that their "solution" for the high latency of the original version wasn't simply punting and handing everything over to Google.
Motorola needs to get a third rev of this out, hopefully without regression bugs. And from their forums, it looks like they're on the case.
Click to expand...
Click to collapse
According to a bunch of android tech blogs, it seems the issue with setting alarms and timers is with Google's search update. Though, it would be nice if moto voice could set alarms and timers went without Google now's help.
http://www.androidheadlines.com/2014/10/google-search-experiencing-timer-alarm-setting-problems.html
I used to gave problems with "good morning" & "Good night" but figured out the trick recently
Do not give a break between good and morning/night. Say it in one word like goodmorning or goodnight and it works everytime(atleast for me)
and for time being, we can avoid the opening google sound by creating a tasker profile which will set the media volume to 0 for 2 seconds whenever google search is opening
[Original Post]
"Ok Google" works fine for me when the phone is on/unlocked without any training. However, to have it work even when the screen is off or the phone is locked it requires training your voice. For the life of me I can't get it to accept the training. It wants to record you saying "Ok Google" three times and it will move on to the second and third recordings after a previous recording is successful. I can't get it to move past the first recording. It just listens for a while and then times out. Anyone else have this issue? Any thoughts on how to resolve it?
[Update 1]
Clearing Google Search data made voice training quick and easy, but my option to have it always on has disappeared. See my post below. Thoughts?
[Update 2]
I just rebooted the phone and my "always on" option has returned but it wants me to retrain my voice. Now I can't get past the first recording again...
I don't have that issue. Voice training went off without a hitch. Did you go to a quiet place like the instructions said?
jakester99 said:
I don't have that issue. Voice training went off without a hitch. Did you go to a quiet place like the instructions said?
Click to expand...
Click to collapse
Thanks for the response. Yes, I was in a location with no sound.
Since posting the original post I found this thread where someone suggested clearing Google Search app data. I tried it and voice training was quick and easy. However, I don't seem to have the option for this to work with the screen off anymore. I can only do it when the screen is on, locked or unlocked.
Here is what the options used to look like (not my screenie, I just found this image on the web, probably from an N9 or something):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now here is what my screen looks like:
I no longer have the "always on" option. One step forward, one step backward.
@Marcellus1 I see that no one has offered any help here and I can't either. My N6 has the issue that your first picture shows. I am running Validus 5.0.1 alpha 1.0 Rom. I have read that this is an issue with all AOSP ROMs right now but there isn't very much being discussed about it. If you find a solution, please let me know. If I find one I'll definitely post it here.
The odd thing is that my my N5, N7(2013) and N9 all have this feature working flawlessly, all running Lollipop. My N6 is the only device with issues and I have tried 3 different ROMs as well as several different gapps packages to try to solve it to no avail.
you can try this thread, as thats what fixed my ok google everywhere and with screen off and unplugged http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716
btw, im on rastapop.
I appreciate the replies. It seems that the fix is only a 50-50 chance of working AND it requires a custom ROM. I'm on stock, no root, no custom recovery, no anything special. I'll probably switch to a custom ROM at some point, but for now I don't think I'm ready to make the switch. One post mentioned in that thread referenced this other thread: http://forum.xda-developers.com/showpost.php?p=57335716&postcount=295
The suggestion is to clear search and play data in order for the changes to survive a reboot, but that you lose the option for always on while not plugged in. That doesn't seem optimal either. Word is Android 5.1 due out in February or so will address "Ok Google" issues, which hopefully means this issue. Maybe I'll just sit tight until 5.1 rolls out before trying factory resets, custom ROMs or the like.
I had a Pressy inserted into my headphone port. Ok Google worked fine on the homescreen with the Pressy inserted, but it would not work with the voice training with the Pressy installed. If i did the voice training without the Pressy, then put the Pressy in, Google Now still worked ok on the homescreen, but not with screen off.
EDIT: I am rooted on stock ROM.
PaisanNYC said:
I had a Pressy inserted into my headphone port. Ok Google worked fine on the homescreen with the Pressy inserted, but it would not work with the voice training with the Pressy installed. If i did the voice training without the Pressy, then put the Pressy in, Google Now still worked ok on the homescreen, but not with screen off.
EDIT: I am rooted on stock ROM.
Click to expand...
Click to collapse
That's interesting. I've had a pressy in my headphone jack. When I try training my voice with Pressy inserted, the phone just endlessly listens and eventually times out. When I removed it and tried voice training again I immediately got "something went wrong" and "It's a little too noisy in here. Please find a quieter place and try again". (and I'm in a quiet place).
[EDIT]: As a follow-up, I've uninstalled Pressy and the AutomateIt Pressy plugin. I've cleared my search data, and installed the new Google (search) app (http://www.androidpolice.com/2015/01/07/google-app-hits-version-4-1-now-cards-settings-apk-download/), but still no luck training my voice.
getting ok google to work, we have found a solution that should work for you.. http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716
simms22 said:
getting ok google to work, we have found a solution that should work for you.. http://forum.xda-developers.com/nexus-6/general/ok-google-everywhere-aosp-rom-t2963716
Click to expand...
Click to collapse
Thanks for your suggestion but it did not work. I saw your suggestion previously and put it off because I didn't want to have to root my device. However, after getting the updated google (search) app today and it still not working, I decided to give it a go. Unlocked the device, rooted it, etc, then copied the files mentioned in your solution to the appropriate locations. Rebooted the device and now my "always on" feature is grayed out and disabled--it says this feature is currently unavailable for this language. The language is set to English (US). I cleared the search app data and was able to train the device immediately, but it was just like my post above where the always on is limited to when the screen is on and unlocked or when charging. Rebooting the phone and/or re-installing the updated google (search) app (because I lost it during the rooting process) takes me back to "this feature is currently unavailable for this language".
[EDIT]: I was looking through that thread some more and saw that some were having some success with flashing the zip by hlxanthus that was a little bit different from the original suggestion. I took my root a step further and installed a custom recovery and then flashed hlxanthus's zip. There is no change.
[EDIT 2]: As a follow-up to the previous edit, after flashing hlxanthus's zip, clearing search data no longer makes a change to enable voice training.
sledge3n8 said:
@Marcellus1 I see that no one has offered any help here and I can't either. My N6 has the issue that your first picture shows. I am running Validus 5.0.1 alpha 1.0 Rom. I have read that this is an issue with all AOSP ROMs right now but there isn't very much being discussed about it. If you find a solution, please let me know. If I find one I'll definitely post it here.
The odd thing is that my my N5, N7(2013) and N9 all have this feature working flawlessly, all running Lollipop. My N6 is the only device with issues and I have tried 3 different ROMs as well as several different gapps packages to try to solve it to no avail.
Click to expand...
Click to collapse
Sledge, I don't know if you ever got your Ok Google working, but I thought I'd post that it's working now for me with the 5.1 update without any tweaks or workarounds.
Marcellus1 said:
Sledge, I don't know if you ever got your Ok Google working, but I thought I'd post that it's working now for me with the 5.1 update without any tweaks or workarounds.
Click to expand...
Click to collapse
Thank you very much for the update! I was still having the issue and just forgot about it. I was thinking about trying out the 5.1 update but just haven't gotten around to it.
Me too, does not work with marshmallows, you have found a solution?
works fine on marshmallow over here. i even taught it to listen for ok nexus instead of ok google.
Do you have Now on Tap or Smart Lock enabled? Some people have reported that these cause issues with hot word detection.
simms22 said:
works fine on marshmallow over here. i even taught it to listen for ok nexus instead of ok google.
Click to expand...
Click to collapse
Would you mind sharing how? I'd love to have that on my phone.
Face_Plant said:
Do you have Now on Tap or Smart Lock enabled? Some people have reported that these cause issues with hot word detection.
Would you mind sharing how? I'd love to have that on my phone.
Click to expand...
Click to collapse
on tap is enanled. how? the normal way, it just works.
simms22 said:
on tap is enanled. how? the normal way, it just works.
Click to expand...
Click to collapse
Interesting. It must listen for "OK" instead of the whole "OK, Google".
Face_Plant said:
Interesting. It must listen for "OK" instead of the whole "OK, Google".
Click to expand...
Click to collapse
ahh, the ok nexus you meant.. yea, i think it listens for the ok mostly. but the second word cant be too different than google in syllables.
This Feature is Broken Again!!!
I've noticed this is broken on Android N. I often clean install custom ROM and then the latest OpenGApps only to find that when I toggle on OK Google "Always On" the toggle instantly turns itself back off the moment I turn it on. There's some work arounds on the forums and I can usually make it work by Installing and old version of the Google App clearing all data for Google App then training voice model and setting OK Google "Always On" toggle to "On". Then after everything is working I go ahead and update Google App from Play Store and usually it keeps working. Sometimes it breaks again. I'm tired of working around this. I wanna know if it will ever again be possible to use this feature. This has been going on for months. Perhaps they should just remove the feature all together then at least it won't be there broken and useless.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
why did I just fine out about this today!? By enabling "trusted voice in Google now under " voice " then "ok Google detection" you can now wake you're device by saying "ok Google" just like the Moto X. [emoji1] woot woot!
Be careful though it might not be as safe as a pin code or pattern but I'm still going to use it for convenience.
Just unlock not wake up??
OptimusVDarwin said:
View attachment 3325740 why did I just fine out about this today!? By enabling "trusted voice in Google now under " voice " then "ok Google detection" you can now wake you're device by saying "ok Google" just like the Moto X. [emoji1] woot woot!
Be careful though it might not be as safe as a pin code or pattern but I'm still going to use it for convenience.
Click to expand...
Click to collapse
I guess you can´t "wake up" your device like moto X, just unlock it when the screen is already on. Did you tested it?
Says not available in uk English. It's OUR LANGUAGE! I set it to USA English but that robot American chick does my head in. She's sooo perky!
SENT BY ENTANGLEMENT
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
dadomonte said:
I guess you can´t "wake up" your device like moto X, just unlock it when the screen is already on. Did you tested it?
Click to expand...
Click to collapse
I tried it and you can phone text etc
SENT BY ENTANGLEMENT
OptimusVDarwin said:
View attachment 3325740 why did I just fine out about this today!? By enabling "trusted voice in Google now under " voice " then "ok Google detection" you can now wake you're device by saying "ok Google" just like the Moto X. [emoji1] woot woot!
Be careful though it might not be as safe as a pin code or pattern but I'm still going to use it for convenience.
Click to expand...
Click to collapse
I don't have this option. Mine says "personal results" and allows searches from a locked phone. I tried putting a lock on my phone in a few different ways and nothing. What's weird is there is a "trusted voice" in the smart lock section. Guess this is an update rolling out?
Our phones have the hardware capability to do always listening Google Now but do to licensing [email protected]@@@ it is turned off. One of the devs from a big dev team even had a proof of concept video showing that it worked and he was contacted and told to cease and desist development.
http://www.xda-developers.com/always-on-listening-mode-proof-of-concept-demoed-on-the-nexus-5/
snappycg1996 said:
I don't have this option. Mine says "personal results" and allows searches from a locked phone. I tried putting a lock on my phone in a few different ways and nothing. What's weird is there is a "trusted voice" in the smart lock section. Guess this is an update rolling out?
Click to expand...
Click to collapse
It's in Google now settings, then go to "voice" then "ok Google" detection then you should see "trusted voice".
I was wondering what was new because I received an update on the Google app and that's how I came across this.
Sent from Mars
OptimusVDarwin said:
It's in Google now settings, then go to "voice" then "ok Google" detection then you should see "trusted voice".
I was wondering what was new because I received an update on the Google app and that's how I came across this.
Sent from Mars
Click to expand...
Click to collapse
I know this man lol it isn't there for me. I haven't got a google app update either I don't think. Maybe it is rolling out.
Trusted voice, trusted devices, trusted face, trusted places...google is undermining security.
While it could be nice, I wonder the impact it will have on battery performance. I recall reading that Moto X has a dedicated low power chipset for it whereas Nexus does not.
4K2K said:
While it could be nice, I wonder the impact it will have on battery performance. I recall reading that Moto X has a dedicated low power chipset for it whereas Nexus does not.
Click to expand...
Click to collapse
It has but its just shut down..
It actually doesn't. Works only when it's charging for me. Everything turned on, trusted voices and everything. Tried all security options too. Doesn't work when unplugged .
zerosum0 said:
Says not available in uk English. It's OUR LANGUAGE! I set it to USA English but that robot American chick does my head in. She's sooo perky!
SENT BY ENTANGLEMENT
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
I tried it and you can phone text etc
SENT BY ENTANGLEMENT
Click to expand...
Click to collapse
Sure, she needs to listen in US English, but can still be set to talk back in perky robot UK English -- that's the way I have mine set up.
Actually, She does seem to speak in different voices depending on the source material, but I'm enjoying that. (And she's perky UK about 80% of the time.)
While this is not exceptionally secure, I'm really just worried about protecting the phone from some dude who picks it up if ever I leave it in a bar. In my limited testing, nobody's been able to unlock the phone by trying to imitate my voice. Knowing the potential trade-off, I'm really enjoying the feature - being able to start a query, play music, listen to NPR, etc,. all without having to swipe and enter my pattern, or even look at the screen, is neat-o! For the almost-Moto effect try it with Gravity Screen!
Remember, all smart locks time-out after 4 hours unused so don't expect it to work when you get up in the morning.
Is it possible to use your phone dialer (using the phone itself) while AA is connected? I have alot of contact shortcuts on my screen for direct dial, but my Mate 20 pro dosnt let me use my phone for making calls while it ist connected to Audi MMI via Android Auto. Like it is blocking the dialer app.
It takes me 1 sek. to make a call when I'm using my phone screen to do this, but when I use cars screen to make a call in AA, it takes ages. And I'm faaaar more distracted from the road then when I'm searching contact on my cars display. So please any advice how to do this?
Did you try to disable "Lock phone while driving" in AA settings?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N975F using Tapatalk
uhi711 said:
Did you try to disable "Lock phone while driving" in AA settings? View attachment 4958845
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.
Spartai said:
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.
Click to expand...
Click to collapse
Latest AA is 5.1.5006, but i don't think this is your problem. I have the same AA version as you, and the setting works on Note 10+. It is probably related to your phone.
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:57 AM ---------- Previous post was at 07:52 AM ----------
Spartai said:
Yes, it is disabled. Could it be a bug in AA? I have version 5.0.500224.
Click to expand...
Click to collapse
You could still try to Enable/Disable the setting. Sometimes it helps.
Sent from my SM-N975F using Tapatalk
uhi711 said:
Latest AA is 5.1.5006, but i don't think this is your problem. I have the same AA version as you, and the setting works on Note 10+. It is probably related to your phone.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Hm... I'll try to download google phone (or some other dialer app) and give it a try. It could be a problem in Huaweis dialer app then. Not happy with it anyway. Samsung has the bes dialer app there is, exactly what I need. Tried to find some port for my Mate 20 pro, but no luck...
I don't think your problem is related to your phone dialer, as I understood, you can't reach your phone's screen during driving with AA in service. Are you able to get to other apps during driving? Usually this is forbidden for safety reasons. I'm even astonished that there is such a setting in AA, but probably this is provided for the case when the passenger is using the phone.
Sent from my SM-N975F using Tapatalk
uhi711 said:
I don't think your problem is related to your phone dialer, as I understood, you can't reach your phone's screen during driving with AA in service. Are you able to get to other apps during driving? Usually this is forbidden for safety reasons. I'm even astonished that there is such a setting in AA, but probably this is provided for the case when the passenger is using the phone.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Well I tried using Viber to place a call, and it kind of worked (call was placed, but active call wasnt shown on my screen), so I hat to close Viber from (swipe it from recent apps) to end the call. Other thing I tried is google maps and that also doesnt want to open. Just like the dialer.
Screen itself works on the phone, but seems the apps dont. At least those that are also awailable on AA. I'll try your suggestion to en/disable lock phone option.
For me it is far les risky to tape once on my phone for something I need, like copyng a phone number, direkt dial etc., then to try to find a way to do that on my car screen or to disconnect the USB cable each time...
Spartai said:
Well I tried using Viber to place a call, and it kind of worked (call was placed, but active call wasnt shown on my screen), so I hat to close Viber from (swipe it from recent apps) to end the call. Other thing I tried is google maps and that also doesnt want to open. Just like the dialer.
Screen itself works on the phone, but seems the apps dont. At least those that are also awailable on AA. I'll try your suggestion to en/disable lock phone option.
For me it is far les risky to tape once on my phone for something I need, like copyng a phone number, direkt dial etc., then to try to find a way to do that on my car screen or to disconnect the USB cable each time...
Click to expand...
Click to collapse
One more suggestion/question: why don't you try to use voice command to dial numbers? The process is not so fast, especially if there is more than one number defined for each of the contacts you need to call, but it works fine. Just say "Call nnnnn (name of contact as saved in your contacts)". You could make new contacts with only nicknames and one single phone number for all the contacts you need to call during driving, in order to shorten the voice dialing process.
Sent from my SM-N975F using Tapatalk
uhi711 said:
One more suggestion/question: why don't you try to use voice command to dial numbers? The process is not so fast, especially if there is more than one number defined for each of the contacts you need to call, but it works fine. Just say "Call nnnnn (name of contact as saved in your contacts)". You could make new contacts with only nicknames and one single phone number for all the contacts you need to call during driving, in order to shorten the voice dialing process.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Problem is that I work alot with foregn customers, so it doesnt recognize a German or Croatian name. Also, when a client calls, they mostly have few numbers in their office so I get alot of calls from new numbers during a day. And that is my problem... Or my office sends me a mail that a customer called and I must call back on that and that number. It is impossible to use anything but the phone screen to do all that.
I see. In that case I think I can't help you further. I hope you'll find a solution finally, but before anything, be safe when driving and keep others on the road safe also.
Sent from my SM-N975F using Tapatalk
uhi711 said:
I see. In that case I think I can't help you further. I hope you'll find a solution finally, but before anything, be safe when driving and keep others on the road safe also.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I will, thank you. If I do find a solution, I'll write you...
Spartai said:
I will, thank you. If I do find a solution, I'll write you...
Click to expand...
Click to collapse
I see you again with your "dialer issue" in separate thread here
I have two points:
- testing Google Maps as a app to be run when the phone is connected to Android Auto head unit is not good idea as this app is controlled via Google Services to be locked for AA only then
- your issue with dialer is probably related to Huawei dialer so try to use the Google Dialer. I know you tried with some dialer but remember that it should be patched. You can try to use one of these dialers:
https://forum.xda-developers.com/de...PUgvgMVvWC-46V8_msoKqVAySgQ80-tYxeM#downloads
Hope it helps. Good luck.
Sent from my SM-N960F via Tapatalk
zencooler said:
I see you again with your "dialer issue" in separate thread here
I have two points:
- testing Google Maps as a app to be run when the phone is connected to Android Auto head unit is not good idea as this app is controlled via Google Services to be locked for AA only then
- your issue with dialer is probably related to Huawei dialer so try to use the Google Dialer. I know you tried with some dialer but remember that it should be patched. You can try to use one of these dialers:
https://forum.xda-developers.com/de...PUgvgMVvWC-46V8_msoKqVAySgQ80-tYxeM#downloads
Hope it helps. Good luck.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
Yes, I'm looking for an answer since this way it is difficult to do my job. I do a lot from my car and I try to be efficient. I also save addresses in my google maps on the phone when I'm in office, but now I see when maps are in AA you have no option to see "labeled" things. You can search it by name and it will show, but that means I need to keep everything in my head. But when you save "Warehouse B+S Koblenz" and you have many similar names in your head, it isn't easy. Thank you very much for the dialers. Do you perhaps know if it is possible to port Samsungs Dialer to Huawei Mate 20 pro? I receive daily 20+ phonecalls from unknown numbers (clients) and samsungs dialer shows "contact history" when you receive a call (e.g. it shows a preview of a last message from that number or when was the last call made, all while your phone rings). And for me that was helpful since I knew if that number called me yesterday or 30 days ago. Also, Huawei only shows Country from where the number is coming from, Samsung showed a City name. End when I see Berlin or Frankfurt, I know which client it may be. But when I see "Germany" it doesn’t tell me anything
Spartai said:
Yes, I'm looking for an answer since this way it is difficult to do my job. I do a lot from my car and I try to be efficient. I also save addresses in my google maps on the phone when I'm in office, but now I see when maps are in AA you have no option to see "labeled" things. You can search it by name and it will show, but that means I need to keep everything in my head. But when you save "Warehouse B+S Koblenz" and you have many similar names in your head, it isn't easy. Thank you very much for the dialers. Do you perhaps know if it is possible to port Samsungs Dialer to Huawei Mate 20 pro? I receive daily 20+ phonecalls from unknown numbers (clients) and samsungs dialer shows "contact history" when you receive a call (e.g. it shows a preview of a last message from that number or when was the last call made, all while your phone rings). And for me that was helpful since I knew if that number called me yesterday or 30 days ago. Also, Huawei only shows Country from where the number is coming from, Samsung showed a City name. End when I see Berlin or Frankfurt, I know which client it may be. But when I see "Germany" it doesn’t tell me anything
Click to expand...
Click to collapse
Sorry I know nothing about Samsung Dialer port project.
First of all try to overcome first basic obstacle (using phone dialer when the AA is connected). So, try to install the Google Dialer and check if it works for you. If you get the satisfactory result it will be a first step and then you can think about next level
Regards,
Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks
Note 10 plus too lol can't stop it , shows bad words in voice assistant tho
shftn2gear97 said:
Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks
Click to expand...
Click to collapse
Did you disable it in the text correction sections of the Gboard app? I had to re enable it and disable it to get it to work.
I'm cursing just fine here. [emoji23]
Sent from my Pixel 4 XL using Tapatalk
Omg this is happening to me now too. For years I've had no problem and now it's censoring my curse words. I disabled options that block curse words in both texting and voice text through Gboard but it still replaces curse words with ***
Since changing the options do not give a different result my assumption is this is somehow server side with Google
Oddly enough as you get older you tend to like cursing less and less, at least as a crutch instead of actually having a vocabulary. Still sometimes nothing quite works as well as a proper curse; an interesting tidbit is that the one that starts with F is the word most taken from the English language and used by others in their language with OK as a distant number 2. All that being said I'd try adding them to the dictionary, this got it working for me although it's kind of a work around. Not that I curse. Ok, maybe a little here and there...
1dopewrx05 said:
Omg this is happening to me now too. For years I've had no problem and now it's censoring my curse words. I disabled options that block curse words in both texting and voice text through Gboard but it still replaces curse words with ***
Since changing the options do not give a different result my assumption is this is somehow server side with Google
Click to expand...
Click to collapse
I'm still not being blocked it's gotta be a phone setting... Did you disable it through the Google app as well?
odd, never thought this block offensive words was mainly for voice typing, but now that I tried it, it's f****** censoring my s*** too! this f****** sucks!! definitely has to be a bug unless Google's gotten soft like people these days
dimm0k said:
odd, never thought this block offensive words was mainly for voice typing, but now that I tried it, it's f****** censoring my s*** too! this f****** sucks!! definitely has to be a bug unless Google's gotten soft like people these days
Click to expand...
Click to collapse
Clear your app data and try again. I would post a screenshot or video recording of all the curses I was just able to do perfectly fine but I don't want to get in trouble on the forums. [emoji23]
Sent from my Pixel 4 XL using Tapatalk
EeZeEpEe said:
Clear your app data and try again. I would post a screenshot or video recording of all the curses I was just able to do perfectly fine but I don't want to get in trouble on the forums. [emoji23]
Click to expand...
Click to collapse
Cleared app data completely and set it up from scratch and it's still censoring. It's really annoying and inconvenient but also I'm glad this is the only problem I've had with my pixel. Some people have had much bigger and worse issues. I hope whatever it is does get sorted soon.
You have to disable it in the Google App under voice and then under Gboard as well. Under Gboard it's under text correction, unselect Block offensive words and it works now.
1dopewrx05 said:
Cleared app data completely and set it up from scratch and it's still censoring. It's really annoying and inconvenient but also I'm glad this is the only problem I've had with my pixel. Some people have had much bigger and worse issues. I hope whatever it is does get sorted soon.
Click to expand...
Click to collapse
And you definitely have this option off?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 4 XL using Tapatalk
EeZeEpEe said:
And you definitely have this option off?
Click to expand...
Click to collapse
Yup have both ticked to the off position. Also, I was saying earlier how I've had this phone for months and it worked without problems for the majority of my ownership of the phone and I haven't changed any Gboard options since setting the phone up but it just all of a sudden one day decided it was going to start censoring everything. Annoying AF
I had it randomly start doing this. Toggling the censorship on and back off didn't work. Clearing data for gboard and setting everything up again did fix it. Back to freedom of speech.
1dopewrx05 said:
Yup have both ticked to the off position. Also, I was saying earlier how I've had this phone for months and it worked without problems for the majority of my ownership of the phone and I haven't changed any Gboard options since setting the phone up but it just all of a sudden one day decided it was going to start censoring everything. Annoying AF
Click to expand...
Click to collapse
Mine started doing this today... smh
The fix is to disable Faster Voice Typing
https://www.reddit.com/r/GooglePixe..._medium=Search&utm_name=Bing&utm_content=PSR1
shftn2gear97 said:
Google Voice Typing and Censorship of my potty mouth.. So I have all of the settings configured to not block offensive language on both the Google keyboard settings and the Google voice typing settings within language and input on my Pixel 4. Is there a setting I'm missing because every time I say a curse word I still get the crazy asterisks
Click to expand...
Click to collapse
I am not going to read all of the threads in here, but the culprit seems to be Faster Voice Typing. Turn it off and things should be ****ing wonderful for you again. Seems to have started around April 20, 2020. Again, make sure you have "Block Pottymouth Words" disabled, and I think there are like three places you'll need to check.