Related
Hi
So while I playing around with Google Now, I decided to try calling someone from my Contacts through voice. To my surprise, the message "This action requires Device State and Content..." is displayed, implying that the phone doesn't support the command. Is this really a phone issue, or an android-related issue?
My money is on it being a "user" issue.
I believe you just need to give Google permission to access the contacts in your phone.
bigdfmartin said:
I believe you just need to give Google permission to access the contacts in your phone.
Click to expand...
Click to collapse
I've synced my contacts with my Google account and allowed Google to search through my contacts. Anything else I need to do?
As I recall, Google prompted me for the permissions the first time I asked it to make a call. It's been working ever since.
bigdfmartin said:
As I recall, Google prompted me for the permissions the first time I asked it to make a call. It's been working ever since.
Click to expand...
Click to collapse
Looks like you were right, tried again the other night, and the issue was solved: google asked for permission. Don't know what I did to get it to work though: all I did was access google settings, ticked and unticked some checkboxes under search and now, and for some reason, the command worked afterwards.
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!
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
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.