Related
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
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.
Never had an issue with this app doing this before, but here we are. I've made sure my number was correct, and even added the Messages app to MagiskHide (which I've never had to do before). It still is stuck. Eventually it gives up trying to verify, but tapping the button just repeats the same issue again. Any ideas?
GuyInDogSuit said:
Never had an issue with this app doing this before, but here we are. I've made sure my number was correct, and even added the Messages app to MagiskHide (which I've never had to do before). It still is stuck. Eventually it gives up trying to verify, but tapping the button just repeats the same issue again. Any ideas?
Click to expand...
Click to collapse
It's really annoying I've had this before. What I did I'd clear data cache in the messages app restart phone then do same again delete data cache then open messages app and try again. If that fails then you have to turn chat off for 7 days don't try turning chat on within the 7 days otherwise it resets to 7 days again. It's a right pain in the but.
I wish I had a answer for you. I was having the same issue on stock, switching to global, switching to eu, etc. Just a couple nights ago I installed magisk and no modules and left my phone alone for a bit (maybe a hour?), When I picked it back up I had 10 encrypted messages I couldn't read come in from a friend that must have came in over the past couple weeks. It was just random.
dalelindley76 said:
It's really annoying I've had this before. What I did I'd clear data cache in the messages app restart phone then do same again delete data cache then open messages app and try again. If that fails then you have to turn chat off for 7 days don't try turning chat on within the 7 days otherwise it resets to 7 days again. It's a right pain in the but.
Click to expand...
Click to collapse
Seven days?
Seems excessive. How/where did you get this length of time?
Jhoopes517 said:
I wish I had a answer for you. I was having the same issue on stock, switching to global, switching to eu, etc. Just a couple nights ago I installed magisk and no modules and left my phone alone for a bit (maybe a hour?), When I picked it back up I had 10 encrypted messages I couldn't read come in from a friend that must have came in over the past couple weeks. It was just random.
Click to expand...
Click to collapse
That's unfortunate. Have you ever had this issue with any other device?
GuyInDogSuit said:
Seven days?
Seems excessive. How/where did you get this length of time?
That's unfortunate. Have you ever had this issue with any other device?
Click to expand...
Click to collapse
Not that wasn't cleared up with a wipe data/cache and restarting the app.
Jhoopes517 said:
Not that wasn't cleared up with a wipe data/cache and restarting the app.
Click to expand...
Click to collapse
I tried Dale's suggestion, clearing data and cache and rebooting the phone. After a minute it popped up the message "enabling chat features, we'll let you know when it's ready." Checked the settings 15 minutes later, and it said "Trying to verify..." STILL but the button to manually verify was usable.
This sucks.
This had happened to me ever since I got the phone and since my carrier is Verizon, It didn't work right out the gate and tried so many different solutions.
then I read that it could still be linked to your old phone so i put my sim card back and then turned off features and then popped it back to the OP and then just left the messages app run in the background and then it suddenly said chat features enabled.
I don't know if this will help you but it worked for mine.
wooo000 said:
This had happened to me ever since I got the phone and since my carrier is Verizon, It didn't work right out the gate and tried so many different solutions.
then I read that it could still be linked to your old phone so i put my sim card back and then turned off features and then popped it back to the OP and then just left the messages app run in the background and then it suddenly said chat features enabled.
I don't know if this will help you but it worked for mine.
Click to expand...
Click to collapse
I turned it off on my old device (doesn't have service anyway). Still no dice. Ugh!!
I've had multiple issues with apps not sending OTP codes or being able to log in completely, and I even think I've had the same issue you are having when I had "dns.adguard.com" set as my private dns setting. Also, if you use AdAway, that could cause the issue. For some reason I have to disable AdAway to use the Amazon app. Weird.
GuyInDogSuit said:
I tried Dale's suggestion, clearing data and cache and rebooting the phone. After a minute it popped up the message "enabling chat features, we'll let you know when it's ready." Checked the settings 15 minutes later, and it said "Trying to verify..." STILL but the button to manually verify was usable.
This sucks.
Click to expand...
Click to collapse
If you have some sort of vpn running, try disabling it and activating chat features. For me it won't work until I turn my vpn off.
is Google carrier services app is up to date on your phone?
TheKnux said:
I've had multiple issues with apps not sending OTP codes or being able to log in completely, and I even think I've had the same issue you are having when I had "dns.adguard.com" set as my private dns setting. Also, if you use AdAway, that could cause the issue. For some reason I have to disable AdAway to use the Amazon app. Weird.
Click to expand...
Click to collapse
Oh yep, in fact I had another thread about that. Turns out the new AdAway seems to inadvertently block a lot of things. Try adding "*amazon*" (without quotation marks) to the whitelist. PayPal was another I needed to add to the whitelist. I also added Google to see if it'd work for this, but nah... No such luck.
chetly968 said:
If you have some sort of vpn running, try disabling it and activating chat features. For me it won't work until I turn my vpn off.
Click to expand...
Click to collapse
No VPN in my case, that I'm aware of.
dexlemaffo said:
is Google carrier services app is up to date on your phone?
Click to expand...
Click to collapse
Yes. I did find it disabled, oddly, so it's enabled and up to date now. Matter of fact, I even installed the latest from APKmirror.
GuyInDogSuit said:
Oh yep, in fact I had another thread about that. Turns out the new AdAway seems to inadvertently block a lot of things. Try adding "*amazon*" (without quotation marks) to the whitelist. PayPal was another I needed to add to the whitelist. I also added Google to see if it'd work for this, but nah... No such luck.
No VPN in my case, that I'm aware of.
Yes. I did find it disabled, oddly, so it's enabled and up to date now. Matter of fact, I even installed the latest from APKmirror.
Click to expand...
Click to collapse
Thanks for the Amazon tip! I was trying to figure it out for the longest time. Even tried the hard way of adding it a long time ago. Just got used to disabling it to use the app or using Amazon through a browser.
It always takes a minute for my chat features to be enabled. Whenever I get a new phone, I always get the message saying "chat features are unavailable for this device" then after a few hours/days, the pop up says that they're ready. I think I leave Messages open in the background. Never had to disable it on the previous device. T-Mobile user here.
TheKnux said:
Thanks for the Amazon tip! I was trying to figure it out for the longest time. Even tried the hard way of adding it a long time ago. Just got used to disabling it to use the app or using Amazon through a browser.
It always takes a minute for my chat features to be enabled. Whenever I get a new phone, I always get the message saying "chat features are unavailable for this device" then after a few hours/days, the pop up says that they're ready. I think I leave Messages open in the background. Never had to disable it on the previous device. T-Mobile user here.
Click to expand...
Click to collapse
Sure thing, glad I could help. If anything, though, you should thank @terlynn4 for that whitelisting suggestion.
In my case this has been going on for a good few days. I've done websearches and researched all the possible causes and solutions I could find, but nothing has worked in my case. Yet. I think the main issue is that I'm not getting the authorization code that Google sends via a short-code service text or whatever those are called.
GuyInDogSuit said:
Sure thing, glad I could help. If anything, though, you should thank @terlynn4 for that whitelisting suggestion.
In my case this has been going on for a good few days. I've done websearches and researched all the possible causes and solutions I could find, but nothing has worked in my case. Yet. I think the main issue is that I'm not getting the authorization code that Google sends via a short-code service text or whatever those are called.
Click to expand...
Click to collapse
Usually when I don't receive the code, it's because AdAway or private DNS settings as stated before. But since you're not using any of those, I'm not sure what else would be preventing from sending the code. Is there any way you can use the Messages for Web feature, bring up your messages on PC, send the code that way and see if it comes up on the web?
I had the exact same issue as you, the issue was that Verizon still had my old phone associated with my account. Verizon support asked my for my iccid (16 digit number physically printed on the sim card), and after they associated it with my new phone I received the backlog of all the sms from short codes that I had missed and rcs verified after 15 minutes and a reboot.
R. Daneel Olivae said:
I had the exact same issue as you, the issue was that Verizon still had my old phone associated with my account. Verizon support asked my for my iccid (16 digit number physically printed on the sim card), and after they associated it with my new phone I received the backlog of all the sms from short codes that I had missed and rcs verified after 15 minutes and a reboot.
Click to expand...
Click to collapse
LMAO, was that what it was? Funnily enough, now that you mention that, that might be the case for me as well. I had recently jumped from a OnePlus 7T to the 9 Pro, and everything had transitioned smoothly, other than this.
TheKnux said:
Usually when I don't receive the code, it's because AdAway or private DNS settings as stated before. But since you're not using any of those, I'm not sure what else would be preventing from sending the code. Is there any way you can use the Messages for Web feature, bring up your messages on PC, send the code that way and see if it comes up on the web?
Click to expand...
Click to collapse
I could give that a try, sure. I do have access to a PC/web browser.
GuyInDogSuit said:
LMAO, was that what it was? Funnily enough, now that you mention that, that might be the case for me as well. I had recently jumped from a OnePlus 7T to the 9 Pro, and everything had transitioned smoothly, other than this.
I could give that a try, sure. I do have access to a PC/web browser.
Click to expand...
Click to collapse
Let me know if it works for you. Sounds ridiculous, but it might actually work.
TheKnux said:
Let me know if it works for you. Sounds ridiculous, but it might actually work.
Click to expand...
Click to collapse
I don't think it did. Or would. Still no message on either end. Something isn't allowing it to be sent in the first place, it seems.
R. Daneel Olivae said:
I had the exact same issue as you, the issue was that Verizon still had my old phone associated with my account. Verizon support asked my for my iccid (16 digit number physically printed on the sim card), and after they associated it with my new phone I received the backlog of all the sms from short codes that I had missed and rcs verified after 15 minutes and a reboot.
Click to expand...
Click to collapse
I had the exact same issue on verizon, but with a globel version. Wouldnt recognize the phone at all. After calling, they pushed me to tech support. Because the phone isnt in their system, the guy had to take an IMEI from another CDMA-Less phone, and enable the CDMA-Less feature. Then he put my IMEI back. Rebooted, and got 2 days worth of texts, and chat features enabled instantly.
The guy said there's a chance that "cleaners" will comb through accounts and reset it, but if it happens, I just have to do the same thing again.
Good morning. Does anyone have any idea how I can solve the problem I have with the google dialer? When I am called, it takes a long time for the screen to turn on while the sound is ringing and it is generally slow to show who is calling .... I have tried to clear the application cache .... I have checked that irrelevant applications do not have access to the phone application but nothing .... Is there a solution? Thanks
I have the same issue, it actually started with my Pixel 4 XL. Back then I thought maybe it's just getting old. Now I'm having the exact same issue with my P6P. Tried a factory reset thinking it might have been something that migrated with my backup but that did not help.
I'm chiming in only to say I haven't seen this problem, and hope you figure it out. Not rooted? No custom kernel?
Not rooted and no custom kernel, been considering those as a solution
I never tried the google dialer. Didn't trust the phone enough to put a sim in it until I had self-built google-free aosp (now grapheme) installed. I have not experienced this with aosp dialer.
eddiedimitris said:
Good morning. Does anyone have any idea how I can solve the problem I have with the google dialer? When I am called, it takes a long time for the screen to turn on while the sound is ringing and it is generally slow to show who is calling .... I have tried to clear the application cache .... I have checked that irrelevant applications do not have access to the phone application but nothing .... Is there a solution? Thanks
Click to expand...
Click to collapse
Did you ever solve this? Not even a factory reset seems to solve it for me
slimfady said:
Did you ever solve this? Not even a factory reset seems to solve it for me
Click to expand...
Click to collapse
Which update is your phone on? November or December? If November, maybe try manually flashing the December update, potentially removing the "-w " so that it doesn't wipe your phone.
roirraW edor ehT said:
Which update is your phone on? November or December? If November, maybe try manually flashing the December update, potentially removing the "-w " so that it doesn't wipe your phone.
Click to expand...
Click to collapse
I'm on the December update, but had it even on the November build
When I open the Google dialer and click on the button to pop up the numbers it's very slow to open up
slimfady said:
I'm on the December update, but had it even on the November build
Click to expand...
Click to collapse
When you factory reset, did you test the Google dialer without restoring any of your old apps or data?
If the January update doesn't fix it for you when it comes out, I'd consider trying that.
Tried before restoring the apps, but I did restore my contacts and SMS. Same result. Could it be something related to my contacts (around 1400 contacts)?
slimfady said:
Tried before restoring the apps, but I did restore my contacts and SMS. Same result. Could it be something related to my contacts (around 1400 contacts)?
Click to expand...
Click to collapse
I doubt it, although I "only" have 635 contacts. Right now I'd say everything is suspect, however. You've got to eliminate every possibility.
I might suspect the number/size of SMS before the number of contacts, but it's worth eliminating both at the same time just to see. Or, as I said, wait until the late January update, but if you still have the problem then you'd have to start from scratch yet again to eliminate those possibilities.
roirraW edor ehT said:
I doubt it, although I "only" have 635 contacts. Right now I'd say everything is suspect, however. You've got to eliminate every possibility.
I might suspect the number/size of SMS before the number of contacts, but it's worth eliminating both at the same time just to see. Or, as I said, wait until the late January update, but if you still have the problem then you'd have to start from scratch yet again to eliminate those possibilities.
Click to expand...
Click to collapse
Thanks, will give it a shot after the January update drops
My best guess is that this delay happens when you have got paired an android wear with your phone. Just for testing, I paired amazfit gtr 3 pro with my P6P and this delay does not occur.
But at the same time, If you are running aosp rom, this delay doesn't happen with the dialer even with android wear paired. Strange
asif4self said:
My best guess is that this delay happens when you have got paired an android wear with your phone. Just for testing, I paired amazfit gtr 3 pro with my P6P and this delay does not occur.
But at the same time, If you are running aosp rom, this delay doesn't happen with the dialer even with android wear paired. Strange
Click to expand...
Click to collapse
Interesting thought, I don't have an Android wear watch paired but I have a fitbit Versa. I haven't had this issue since the January update plus a full wipe.
I had a seperate theory which is related to the number of Google accounts I have on my phone (I had 4 before wiping). I'll keep an eye on it and try to unpair the watch if it re-occurs.
slimfady said:
Interesting thought, I don't have an Android wear watch paired but I have a fitbit Versa. I haven't had this issue since the January update plus a full wipe.
I had a seperate theory which is related to the number of Google accounts I have on my phone (I had 4 before wiping). I'll keep an eye on it and try to unpair the watch if it re-occurs.
Click to expand...
Click to collapse
Well well well, I acted as per your theory and deleted all my google account except one that is linked to contacts and I am experiencing quite instant call-in and call-out screen and the contacts also show almost instantly.
Its a shame that android is google's own product and these issues (having more than google account) jeopardize the whole experience. I have read a lot of posts on reddit and other forums for the the same issue and all what google guys suggest is factory reset which is not a pleasant way and the problem persists after that.
Maybe I am too quick to give my feedback and this issue resurfaces even with 1 account. Will keep an eye on that and will post my further findings.
asif4self said:
Well well well, I acted as per your theory and deleted all my google account except one that is linked to contacts and I am experiencing quite instant call-in and call-out screen and the contacts also show almost instantly.
Its a shame that android is google's own product and these issues (having more than google account) jeopardize the whole experience. I have read a lot of posts on reddit and other forums for the the same issue and all what google guys suggest is factory reset which is not a pleasant way and the problem persists after that.
Maybe I am too quick to give my feedback and this issue resurfaces even with 1 account. Will keep an eye on that and will post my further findings.
Click to expand...
Click to collapse
I think it's confirmed. I've added two more accounts and the call screen is now back to taking forever to showup when I get a call
slimfady said:
I think it's confirmed. I've added two more accounts and the call screen is now back to taking forever to showup when I get a call
Click to expand...
Click to collapse
Yeah I reconfirm it as well, no delay in call screens if having 1 Gmail account only.
Culprit is Google phone app I guess, may be it goes through all accounts to search n display the contact that cause this delay. I have tried Google phone app on samsung s21 ultra too n there is same delay with having more than 1 accounts while Samsung own dialer app doesn't suffer this issue.