I've used this function successfully in the past, but recently when I tried to have Google assistant "text my brother" she came back asking "who is your brother?". I told her using his name, as it appears in my contacts, but she just repeated the question, as though I'd never answered. This loop goes on indefinitely. I'm running the latest factory image on a pixel 2 XL, and am wondering if anyone else is having this problem, and/or if anyone knows of a possible fix.
OneNutShort said:
I've used this function successfully in the past, but recently when I tried to have Google assistant "text my brother" she came back asking "who is your brother?". I told her using his name, as it appears in my contacts, but she just repeated the question, as though I'd never answered. This loop goes on indefinitely. I'm running the latest factory image on a pixel 2 XL, and am wondering if anyone else is having this problem, and/or if anyone knows of a possible fix.
Click to expand...
Click to collapse
Just tried and worked fine for me.
Sent from my Pixel 2 XL using Tapatalk
OneNutShort said:
I've used this function successfully in the past, but recently when I tried to have Google assistant "text my brother" she came back asking "who is your brother?". I told her using his name, as it appears in my contacts, but she just repeated the question, as though I'd never answered. This loop goes on indefinitely. I'm running the latest factory image on a pixel 2 XL, and am wondering if anyone else is having this problem, and/or if anyone knows of a possible fix.
Click to expand...
Click to collapse
I've seen this on a few pixels. In my case, it was a rogue app. The app had accessed the mic and was doing funky stuff. I removed the app and all was well after a reboot. Know this doesn't help as you don't know which app it is. Look at you permissions list, that will tell you what apps have access to your mic.
works fine for me.
possibly try adding the nickname prior to issuing the text command. IE: tell the assistant john doe is my brother
Related
I have a Rooted Galaxy S-II. Aside from that it's basically stock. Just removed some of the bloatware.
Up until recently Skype was working just fine on my phone. As of (I think) the most recent update, whenever I start up Skype and try to log in, it gives me an error message to the likes of: "Skype has stopped working - Would you like to sign in again or exit Skype?" with the options to Exit or Sign In. If you pick "Sign In" it just sits there.
I've tried clearing data both through the phone and through Titanium Backup, and I've also tried deleting and reinstalling the app. Nothing is working.
I thought I read somewhere on the internet (not to say that that's a reliable or specific source to say the least) that with the newest update there's an inherent bug with Rooted phones and Skype not working. Don't know if that's accurate but it seems like it might be.
Anyone else seeing this? Have a fix? A workaround?
Thanks!
Happened to me too but I got signed in I just kept exiting and trying again it took about 5 times for me
Sent from my SGH-T989
hexagon_sun said:
I have a Rooted Galaxy S-II. Aside from that it's basically stock. Just removed some of the bloatware.
Up until recently Skype was working just fine on my phone. As of (I think) the most recent update, whenever I start up Skype and try to log in, it gives me an error message to the likes of: "Skype has stopped working - Would you like to sign in again or exit Skype?" with the options to Exit or Sign In. If you pick "Sign In" it just sits there.
I've tried clearing data both through the phone and through Titanium Backup, and I've also tried deleting and reinstalling the app. Nothing is working.
I thought I read somewhere on the internet (not to say that that's a reliable or specific source to say the least) that with the newest update there's an inherent bug with Rooted phones and Skype not working. Don't know if that's accurate but it seems like it might be.
Anyone else seeing this? Have a fix? A workaround?
Thanks!
Click to expand...
Click to collapse
Tango
Update? After reading your post I used Skype and worked fine. I'm on rooted phone using Darkside Evolution 3 V8.
Sent from my SGH-T989 using xda app-developers app
Ever since December 23rd or so, when I first rooted my stock Nexus 5X, Google Messenger has been behaving strangely. Long SMS messages have seemingly random characters attached to the end of them, which do not show up on the sender's end. The most common is a "¿", but occasionally I get a delta ∆ on the end. I cannot find anyone else with this problem either here or elsewhere online. Does anyone have ideas? It's not necessarily a problem, but it is a mysterious inconvenience.
I am running the latest update of Marshmallow (stock ROM), with systemless root (SuperSU 2.61 I believe) and TWRP recovery. Nothing else out of the ordinary. This did only become a problem after rooting my phone, which may be part of the problem. Any help would be appreciated!
Edit: it should be noted that while these are valid characters, they do not appear when searched for with Messenger's built-in search function.
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Broken303 said:
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Click to expand...
Click to collapse
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
OGNatan said:
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
Click to expand...
Click to collapse
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
plwalsh88 said:
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have switched to Textra indefinitely, as this does not solve the problem, but does support many features that Messenger is lacking. If you find a way to submit a bug report, I would be interested in that information
This surely isn't Pixel-specific, but I figured I'd ask here before jumping to a more general forum...
Since I got my new Pixel XL, I always get a push notification from Google Play services a minute-or-so after boot up titled, "Change your phone number?" Clicking on the notification takes me through a wizard that first requests my password, then asks for my "new" phone number. (Mind you, my phone number has never been changed.) After completing the previous steps, the notification disappears — until I reboot. Then it reappears.
I tried rebooting after clearing the cache for Google Play + Google Play Services, but the notification still appears. I also tried removing my recovery phone number, rebooting, and using the notification's wizard to re-add the number. No dice.
Anyone experience a similar issue?
Try logging out of your Gmail, go HERE, do whatever it says, and then make sure it is YOUR phone number for your Gmail recovery.
After youre done, log back in on your phone, and you should be good
Removing and re-adding my Google account didn't fix the issue.
N00B_IN_N33D said:
Removing and re-adding my Google account didn't fix the issue.
Click to expand...
Click to collapse
Did you do any of the other stuff that he pointed you to. There's more to do then just remove and then add back your account.
toknitup420 said:
Did you do any of the other stuff that he pointed you to. There's more to do then just remove and then add back your account.
Click to expand...
Click to collapse
Sorry, although I didn't mention it, I did try it. I sort of list it in the OP as one of the steps I tried before posting here — although I did try again while following the instructions provided by noidea24.
I ended up blocking notifications from Google Play Services as a temp fix, but nothing I've tried thus far has seemed to truly resolve the problem. I also reached out to Google's Customer Support, but am still waiting for their specialist to reach out..
Btw, I appreciate you both taking the time to chime in on this issue! Although it's not a breaking issue, it's been really annoying ?
N00B_IN_N33D said:
Btw, I appreciate you both taking the time to chime in on this issue! Although it's not a breaking issue, it's been really annoying
Click to expand...
Click to collapse
Hey, did you ever work out how to fix this? I'm having the same issue and it's pretty annoying!
Same issue on my end. Nexus 6p worked fine, but then just switched to Pixel XL, using the transfer-to-android-phone feature. This "change your phone number" message appears after each reboot for me. My gmail recovery phone has remained the same, and it matches the phone number on the Pixel XL (same as Nexus as well, but I swapped sims upon setup).
EDIT: should note pixel on android 8, and 6p was on 7.1.2
I'm having the same issue after moving from a 6P to a Pixel 2 XL. Signing out and setting up my account recovery option hasn't helped. I've reached out to Google support, but so far no luck.
EDIT: Clearing cache and user data for Google Play services appears to have done the trick. Several reboots and no further notifications.
I'm having the exact same issue since switching to the Pixel 2 XL. I've cleared cache and user data for play services multiple times, but this comes up about once a week for me.
same issue on Pixel 2
I have had this problem since I got my Pixel 2. totally not phone-breaking but really anoying. I reached out to support on this and they had me do a factory reset. when that did not solve the issue, they directed me here. I still have my Nexus 6P, and I DID see that notification show up once after I re-updated my phone number on my Pixel 2, but it hasn't shown up again on the 6P. Still appearing on every reboot of the Pixel 2 though. like annoying clockwork.
*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!
Have yet to get an answer to this and was wondering if the community had experienced anything like this or had any advice.
On October 1st I cleaned up my Pixel 6 Pro (from sd main pro to wiping ALL chrome browsing history) so anything I'm signed into automatically logs me out.
The first time I came back to XDA I went to login and someone else's name was on my screen and it showed they had a notification.. I've never seen this before. When I clicked on his name it prompted me to log in again, as him.
Could this be a server side issue?
I believe that's a server side issue
Hand76 said:
Have yet to get an answer to this and was wondering if the community had experienced anything like this or had any advice.
On October 1st I cleaned up my Pixel 6 Pro (from sd main pro to wiping ALL chrome browsing history) so anything I'm signed into automatically logs me out.
The first time I came back to XDA I went to login and someone else's name was on my screen and it showed they had a notification.. I've never seen this before. When I clicked on his name it prompted me to log in again, as him.
Could this be a server side issue?
Click to expand...
Click to collapse
I'll make the Admins aware of this. Thank you.
@Hand76 I can pass on the assurances that we've seen this before, that it's a known bug, that this used to happen back in the vBulletin forum software days too, that this bug doesn't actually let anyone log in under a different user's account, and they're continuing to look into it.