I have the Pixel 3 XL, and I have a frustrating issue. When the screen is on the lockscreen, using Google Assistant to call someone, read emails, or read messages doesn't seem to work properly. It will try to call, but nothing happens, and it will display my messages but not read them. If I go to the homescreen and repeat, everything works. This also happens on the lockscreen with smart lock enabled. I verified that voice match and lock screen personal results are both enabled.
Is anyone else experiencing this, and if so is this normal?
dcorrea said:
I have the Pixel 3 XL, and I have a frustrating issue. When the screen is on the lockscreen, using Google Assistant to call someone, read emails, or read messages doesn't seem to work properly. It will try to call, but nothing happens, and it will display my messages but not read them. If I go to the homescreen and repeat, everything works. This also happens on the lockscreen with smart lock enabled. I verified that voice match and lock screen personal results are both enabled.
Is anyone else experiencing this, and if so is this normal?
Click to expand...
Click to collapse
This is by design. No longer doing voice unlock. You will only get non-personal info.
Really?? You're saying that Google has removed the capability to use Google Assistant when the Pixel 3 is locked (i.e. voice unlock)? This seems like a step backwards. Can you provide a link to an official Google statement on this?
JWadle said:
Really?? You're saying that Google has removed the capability to use Google Assistant when the Pixel 3 is locked (i.e. voice unlock)? This seems like a step backwards. Can you provide a link to an official Google statement on this?
Click to expand...
Click to collapse
I've actually read that this will be an option moving forward. From the lockscreen without unlocking the phone. If you've been able to use assistant without unlocking the phone, this is news to me. I know they're making it so you can't unlock the phone with your voice, hey Google, whatever though. Security apparently.
gettinwicked said:
I've actually read that this will be an option moving forward. From the lockscreen without unlocking the phone. If you've been able to use assistant without unlocking the phone, this is news to me. I know they're making it so you can't unlock the phone with your voice, hey Google, whatever though. Security apparently.
Click to expand...
Click to collapse
Ok my wife just got home and I tried it on her Pixel with the same result. Guess it is a feature now...which I think sucks. I understood that you could no longer unlock the pixel with your voice, but I figured that you could still make calls and check messages with your voice. Why would the assistant show me my messages but not read them aloud from the lockscreen? That makes no sense.
dcorrea said:
Ok my wife just got home and I tried it on her Pixel with the same result. Guess it is a feature now...which I think sucks. I understood that you could no longer unlock the pixel with your voice, but I figured that you could still make calls and check messages with your voice. Why would the assistant show me my messages but not read them aloud from the lockscreen? That makes no sense.
Click to expand...
Click to collapse
Yeah. Doesn't make sense that it shows your notifications, but won't read them. I would not mind it if was enabled with Smart Lock. Like if my watch is paired, then it will read everything like before.
JWadle said:
Really?? You're saying that Google has removed the capability to use Google Assistant when the Pixel 3 is locked (i.e. voice unlock)? This seems like a step backwards. Can you provide a link to an official Google statement on this?
Click to expand...
Click to collapse
https://www.androidpolice.com/2018/10/19/pixel-3-drops-support-voice-match-unlocking/
No please say it's a bug I just 2 days ago tried to turn off my lights and i was annoyed because i needed to go and pickup my phone to do that. I was thinking it just a bug and tried to fix it for a while, and was thinking i need to do factory reset. But apparently it's not ;/
And it was on Pixel 2 XL
I read an article from 9 to 5 that said this may be how all phones run the Okay google unlock command in future updates not just Pixel 3.
Edit
I have a Google Assistant Routine that I activate for bedtime. From the Lockscreen, it is able to read my personal calendar events for tomorrow outloud but it is unable to play "sleep sounds". Absolutely silly to me.
This is a Google devised plot to sell more google home devices. Until this changed, our phones could do everything a smart speaker could.
Wow.. I allowed my smartwatch to unlock the phone via Smart Lock with Bluetooth.
Google Assistant still won't let me do calls, nor will it open apps from the lockscreen.
It recognizes the command just fine saying "calling person xy" but it won't do anything at all. Same with opening apps. For example if I ask it to open Spotify it says "opening Spotify" but nothing happens.
If it's by design, why wouldn't it tell me that a proper unlock is required?
It seems to me that this is more likely a bug than by design?!
dcorrea said:
I have the Pixel 3 XL, and I have a frustrating issue. When the screen is on the lockscreen, using Google Assistant to call someone, read emails, or read messages doesn't seem to work properly. It will try to call, but nothing happens, and it will display my messages but not read them. If I go to the homescreen and repeat, everything works. This also happens on the lockscreen with smart lock enabled. I verified that voice match and lock screen personal results are both enabled.
Is anyone else experiencing this, and if so is this normal?
Click to expand...
Click to collapse
same problem,but when I unlock my pixel3(rooted), open phone app and exit, then lock the screen,when you said:"call xx's mobile ",she asked you to unlock the phone.(what's the necessary of this function)the calling is working........
same question,Is anyone else experiencing this?
I've realized that some of the issues posted by the OP are related to smart lock being enabled. If I try and get Assistant to set an alarm or make a call from the lockscreen WITH smart Lock enabled it recognises the command but doesn't enact it. If I disable smartlock everything works even from the lockscreen. I have reported it to support and sent a bug report but I doubt anything will get done about it.
Sent from my Pixel 3 XL using Tapatalk
Related
I use this feature all the time but after i clean wiped my phone now it either pulls up 3 businesses with home in the name or it will pull up 2 contacts that happen to have home in the title. Not sure why it isn't working right. Telling it to navigate to work still works correctly.
I already have my home set in the google app and in google maps.
smac7 said:
I use this feature all the time but after i clean wiped my phone now it either pulls up 3 businesses with home in the name or it will pull up 2 contacts that happen to have home in the title. Not sure why it isn't working right. Telling it to navigate to work still works correctly.
I already have my home set in the google app and in google maps.
Click to expand...
Click to collapse
For myself, I say "OK Google, how do I get to home". Tells me how long it will currently take and I just need to tap navigate icon.
Sent from my Nexus 5X using Tapatalk
Here's what i found...
I have read about this problem so many places and seen so many solutions - none of which worked for me.
Today - I finally found out where my "work" and "home" were stuck and preventing navigate to... from working for these locations. Short form - they were stuck in my Google+ account, but NOT in the places category. It was my contact settings for home and work. They were set to blank in my Google plus profile. It didn't matter that I had them set in my phone. It didn't matter that I had them set in Google Maps (both on Android and on the web). Caches - meaningless. In the end, it came down to the fact that those values were blank in my Google+ account - THAT is what stopped the service from working.
Thank me if I helped.
:fingers-crossed:
Mikkey81 said:
Here's what i found...
I have read about this problem so many places and seen so many solutions - none of which worked for me.
Today - I finally found out where my "work" and "home" were stuck and preventing navigate to... from working for these locations. Short form - they were stuck in my Google+ account, but NOT in the places category. It was my contact settings for home and work. They were set to blank in my Google plus profile. It didn't matter that I had them set in my phone. It didn't matter that I had them set in Google Maps (both on Android and on the web). Caches - meaningless. In the end, it came down to the fact that those values were blank in my Google+ account - THAT is what stopped the service from working.
Thank me if I helped.
:fingers-crossed:
Click to expand...
Click to collapse
i can't even find contact settings on g+
smac7 said:
i can't even find contact settings on g+
Click to expand...
Click to collapse
Did you try my recommendation? I never had to do anything with contact settings on Google+.
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
Did you try my recommendation? I never had to do anything with contact settings on Google+.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thanks! i tried you're recommendation and now it also works when I say "navigate home". I was stalling on trying it at first cause my wife is sleeping next right next to me and i didn't want to wake her. I went for the whisper and it worked lol.
smac7 said:
thanks! i tried you're recommendation and now it also works when I say "navigate home". I was stalling on trying it at first cause my wife is sleeping next right next to me and i didn't want to wake her. I went for the whisper and it worked lol.
Click to expand...
Click to collapse
? Yeah I think I used to try that too and noticed it didn't work one time. Then I realized in a Google commercial they would say "How do I get to..." and gave that a try instead. So I just use that most of the time.
Sent from my Nexus 5X using Tapatalk
Go to google plus on your browser Click on your profile. (This is from my phone, mind you) click on the info button on the rightside (the circle lettered "i").
Your location should be stored there (make sure its private). Next turn off your accounts sync on your phone and then back on. Accounts/Google turn off on everything and then back on.
Installing a larger package of google apps fixed the navigation problem for me. It seems in the nano or smaller package some essentiell voice things are missing.
My work requires a password and encrypted phone. No biggie. However, OK Google does nothing with a locked device (we can't use Trusted Agents). On my Note 5, I could still do non-personal stuff ("what's the weather?," "wake me up at 6 AM"). With my Pixel XL, I can do nothing.
Is this personal assistant? Is there an alternative? Quite annoying to say the least.
jackburnt said:
My work requires a password and encrypted phone. No biggie. However, OK Google does nothing with a locked device (we can't use Trusted Agents). On my Note 5, I could still do non-personal stuff ("what's the weather?," "wake me up at 6 AM"). With my Pixel XL, I can do nothing.
Is this personal assistant? Is there an alternative? Quite annoying to say the least.
Click to expand...
Click to collapse
You can't use it if you don't allow trusted voice.
toknitup420 said:
You can't use it if you don't allow trusted voice.
Click to expand...
Click to collapse
I think the latest update knocked it sideways.
I never had any issues until the latest GA update.
Doing a little research I have found a bloom of complaints in the last couple of weeks.
I have to continually go back and check the trusted voice attribute.
i suspect it has to do with have multiple google accounts in my phone.
I am sure it will be addressed in future updates.
parakleet said:
I think the latest update knocked it sideways.
I never had any issues until the latest GA update.
Doing a little research I have found a bloom of complaints in the last couple of weeks.
I have to continually go back and check the trusted voice attribute.
i suspect it has to do with have multiple google accounts in my phone.
I am sure it will be addressed in future updates.
Click to expand...
Click to collapse
I have been having issues too, does your "Trusted Voice" setting keep getting disabled in the background? That's the problem I keep noticing in my Google App Settings (in hotword detection). I talked to a support rep, just keep sending feedback from that settings page by pressing the question mark in the upper right, then selecting Send Feedback at the bottom of the page that appears. Simply type in that Trusted Voice disabled itself and submit. The only way we get this fixed is by telling them about it.
*EDIT
This is a known issue per Google. Thread on their product forum here https://productforums.google.com/for...A/tMN4y-GZAAAJ A huge thank you to uicnren for finding it!
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally.
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Thanks in advance!
Click to expand...
Click to collapse
I would first try clearing the google phone dialer app cache and data, reboot, and see it helps. If not, then I would uninstall it, reboot, then dl it again from the play store :good:
Or, side load the April OTA update
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally.
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Do you use Google Voice at all?
Badger50 said:
I would first try clearing the google phone dialer app cache and data, reboot, and see it helps. If not, then I would uninstall it, reboot, then dl it again from the play store :good:
Or, side load the April OTA update
Click to expand...
Click to collapse
I'm going to try the April update, the rest didn't work.
igknight said:
Do you use Google Voice at all?
Click to expand...
Click to collapse
Yes I do use google voice. I hadn't even thought of that. COuld definitely ber a google voice issue.
paxderomano said:
Yes I do use google voice. I hadn't even thought of that. COuld definitely ber a google voice issue.
Click to expand...
Click to collapse
The pressing 1 to answer was what made me think of that. I know there is an option to enable/disable that. Not sure about the no ringing issue, however.
igknight said:
The pressing 1 to answer was what made me think of that. I know there is an option to enable/disable that. Not sure about the no ringing issue, however.
Click to expand...
Click to collapse
I just looked through the Gvoice settings and didn't find anything (that I could tell) that does that. But thanks for the suggestion!
I think it is the Screen Calls option, under the Calls settings in the web interface. Don't quote me on that.
I have the same problem regarding not hearing the ringing sound when making a call. I also use Google Voice. I have not experienced the press option 1 to answer problem.
machostallion said:
I have the same problem regarding not hearing the ringing sound when making a call. I also use Google Voice. I have not experienced the press option 1 to answer problem.
Click to expand...
Click to collapse
Okay so I was able to get rid of that (it's the option that asks if you want to hear the name of the caller, definitely doesn't work like I thought it would).
Loaded the April update and still have the issue with outgoing calls.
"Loaded the April update and still have the issue with outgoing calls. "
Same here. It stated happening after installing google voice and uninstalling it.
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Press 1 to talk? What do you mean?
paxderomano said:
I can't seem to find other reported instances of this when web browsing so thought I'd try here.
For the past week or so, anytime I make a phonecall there is no sound to indicate the phone is actually ringing. It's just silent until someone picks up, I get voicemail, etc.
Conversely every single time someone calls me I'm having to press option 1 to talk to them instead of just answering normally. (this part is a user option I've since disabled).
Not sure if I did something to settings, if this a bug, etc. It's driving me nuts though so any suggestions would be appreciated. I have not tried a factory reset yet because if I can about the hassle I'd like to.
Currently running 8.1 March update, on the non Verizon version. Bootloader is locked, not rooted.
Should also add that I use Google Voice, so maybe the issue is on that end.
Thanks in advance!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
uicnren said:
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
Click to expand...
Click to collapse
Yes, that is it exactly! For whatever reason, I was having zero luck finding anything about it on the product pages. Thank you, I'm glad that it's a known issue and not just me.
uicnren said:
maybe? https://productforums.google.com/forum/#!msg/voice/48CgSY067GA/tMN4y-GZAAAJ
Click to expand...
Click to collapse
pcloadletter1 said:
"Loaded the April update and still have the issue with outgoing calls. "
Same here. It stated happening after installing google voice and uninstalling it.
Click to expand...
Click to collapse
pcloadletter, this is apparently a known issue. thread on google product page above. Thanks again uicnren!
On the pixel 3 XL sometimes when I say Hey Google it takes a moment to work, and when I say Call __ the screen shows the command but it will not call. I have to open the Phone app and manually call them. Anyone else get that?
I have the same issue a quick reboot fixes the issue, but it's super annoying to have to constantly reboot your phone to make a call via the google assistant.
doesnt work when i say a nickname while using maps. i have to say the complete persons name.
I guess the word hasnt really got out yet that feature has been taken away by Google because they deemed it a security risk. I think that is the worlds worst decision and has taken the choice out of our hands. Google could have easily just placed a warning that if used it "could" pose a security risk. But, that goes against all the new "Titan" security that they peddling now. Remember what is used to say here in Google App settings/voice? Well this is what is says now!
Archangel said:
I guess the word hasnt really got out yet that feature has been taken away by Google because they deemed it a security risk. I think that is the worlds worst decision and has taken the choice out of our hands. Google could have easily just placed a warning that if used it "could" pose a security risk. But, that goes against all the new "Titan" security that they peddling now. Remember what is used to say here in Google App settings/voice? Well this is what is says now!
Click to expand...
Click to collapse
What feature was taken?
Novakingwai said:
What feature was taken?
Click to expand...
Click to collapse
If the phone is on the lockscreen, OK GOOGLE will not make calls, or display personal results. More specifically, it will not read your messages, but it will display the messages on the screen. To be clear, it doesnt matter if you the lockscreen personal results option is turned on.
Very stupid IHMO. I get Google removing this "feature" due to security, but I will say that in the very least they should have the phone alert you that it cannot make a phonecall, read your personal messages aloud, etc instead of just not working and making people think something is broken.
https://www.theverge.com/2018/10/19/18001460/google-pixel-3-xl-google-assistant-voice-match-removed
So... The other day I tried to access voice detection via "Hey Google" and it didn't activate.
Upon further research, I found that 'voice detection' setting in the Google app was toggled off. No biggie. Toggle it on and it worked again. Tried it again because I'm an OCD fool when it comes to not trusting Google after my woes with this device. Low and behold it didn't work. Returning to the same screen as previously viewed showed that it was again toggled to disabled.
At this point, I'm in WTF mode.
I reenable it and launch the Google app manually and click the mic. Speak command. Command executes. "Hey, Google." Assistant activates and subsequent command executes. "Hey, Google" again fails and it is now disabled in the options again.
Anyone else experienced this?
i had trouble with that. i cleared data from google app and reset permissions and waited an hour and it started working again or something... wish i had better advice. might want to contact google support.
dipstik said:
i had trouble with that. i cleared data from google app and reset permissions and waited an hour and it started working again or something... wish i had better advice. might want to contact google support.
Click to expand...
Click to collapse
I'll give that a go... Thank you.
dipstik said:
might want to contact google support.
Click to expand...
Click to collapse
Sadly, I really REALLY don't. I've had to RMA and now requested a refund through their support. If you have never dealt with them, be glad.
I have had pretty good experiences with their support ever since the Google one thing started.