*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!
Related
Howdy,
Before I upgraded to CyanogenMod 9.0, I would get a Google Voice message notification for a text message. I'd go into the web version of Google Voice, answer the text and then after a bit, the notification would go away on my phone.
Now switched to CM9 and the notification doesn't go away unless I answer the text on my phone or clear it out on the phone.
I've tried GummyNex and CM9 and they both do it.
Has anyone else seen this? I've done the thing where I've uninstalled GV, did the *73, deleted all the Verizon VMs and the reinstalled GV but it still does it.
Don't think its related to your ROM as I'm having the exact same issue on stock 4.0.4 and have always been on stock. Seems to have started a couple weeks ago....
Been pulling my hair out trying to figure out what's going on and was about to start a thread myself asking if anyone else had the issue. Thought I was just crazy at first, but I know for a fact this is not how the app acted before. I've tried changing all kinds of things for my browser use of voice.google.com, deleted/re-installed the app, and nothing works.
I'll be texting using just the browser for a bit and look at my phone and I'll have a notification for "25 Google Voice Messages" or whatever. They never clear. I notice that when opening the GV app to the thread I'm texting in, it hasn't synced in the background, and takes a few seconds for the messages I had sent to show up in the thread. It seems as though Google Voice isn't getting background sync anymore.
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Argh.
Yeah - nothing I've found has fixed the issue.
Seijin said:
Aww man So it was just highly coincidental that it happened around the same time I switched over to a different rom.
It's surprisingly frustrating for such a little thing. I just use it so much that it forces me to check the phone and clear it manually to make sure I don't *actually* have a new message when I'm using both my phone and the web app.
Click to expand...
Click to collapse
Yes I think it's actually a coincidence as I said I've been on stock and it all of a sudden stopped working as it was. This is just really weird because there's been no update to the app or anything.
It's extra frustrating because Google Voice is my primary #, so I'm doing about 99.9% of my texting with it, and really enjoy being able to use voice.google.com. Dealing with clearing GV notifications every time I pick my phone up is very lame.
I don't believe I'm experiencing this, gv on GSM nexus, stock 4.0.4 rooted. Straight talk tmo mvno
Sent from my Galaxy Nexus using Tapatalk 2
I don't currently have this with my yakju 4.0.4 OTA stock ROM, but I have seen it before on this phone and every other phone I've owned across stock & custom ROMs. Fairly confident it's a problem with the app itself
@crachel - are you on cdma or gsm?
crachel said:
Fairly confident it's a problem with the app itself
Click to expand...
Click to collapse
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Seijin said:
@crachel - are you on cdma or gsm?
Click to expand...
Click to collapse
GSM
martonikaj said:
What could it be though? I've done everything short of a factory reset. Nothing about the app itself or the settings I used changed and it started happening out of nowhere.
Click to expand...
Click to collapse
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
crachel said:
I don't know.. I agree though that the problem just comes and goes, which is odd. Just a couple weeks ago they weren't clearing for me, but right now it's working fine. I remember thinking that's it's ridiculous this happens on stock firmware
Click to expand...
Click to collapse
Even moreso ridiculous if this is a known issue and they haven't addressed it even with these several early 2012 updates to the GV app, which made it a lot better overall in UI and UX. I just don't see how it can come and go with no changes whatsoever to your settings.
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
xur17 said:
Mine definitely does the same thing... I thought it used to clear them for me, but I wasn't sure, and figured I was just thinking of how Google Talk clears the messages.
Not a huge deal to me, but it would definitely be nice if they would fix this. Our best bet is to make a post on the help forums with a bunch of posts in it.
Click to expand...
Click to collapse
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
martonikaj said:
If I get some time I'll put up a bug report on Google Groups/Google Code.
Edit: Nevermind! Someone's on it already from February: https://code.google.com/p/android/i...on&colspec=ID Type Status Owner Summary Stars
I'd appreciate if you're having this issue to star and comment there (as well as here).
Click to expand...
Click to collapse
Thanks for the link!
If anyone has a chance, they should make a post in the Google Voice forums here (I'll try to do it later when I have a chance if no-one else gets to it): http://productforums.google.com/forum/#!categories/voice/using-google-voice-on-a-mobile-device. I heard that Google Engineers do monitor / read these sometimes, so if we all post in a thread there is a chance it will get read / fixed.
I really wish there was a better way to get stuff like this fixed.
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Note: I think that if you use the GV widget, you will see that the notification on the widget DOES clear after checking the web interface (or at least it did in GB because I just tested this on my current phone and widget doesn't clear it either). I suppose this means that GV is pushing the "read" status of an sms to our phones. The notification on the notification bar, however, still persists despite this.
EDIT: Given my last test on my current phone, it looks like the widget doesn't clear the notification like it used to on GB. It looks like it is, in fact, a syncing issue.
LeoBloom. said:
Bit late to the party. Just wanted to chime in that in my experience I don't think I've ever seen the GV notification clear itself after checking the web interface on my computer.
I've been using android for a year now and have gone through 3 phones and the asus transformer tablet. My current phone is running a CM9 based rom, but still it doesn't clear these notifications.
Man, I'd love it if it did.
Click to expand...
Click to collapse
I can confirm that it actually did used to clear when viewed on another device, and this is the intended action. It should work exactly like an IMAP e-mail account (say, the GMail app). If you view a message on the device or in a web browser, it is cleared as read on the other. Google Voice used to do the same, and stopped doing so randomly. It's completely a backend problem.
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
xdp said:
Really wish they would fix this. Still happening on JB. Very annoying for those of us who text from the web all day.
Click to expand...
Click to collapse
Still a problem, go over to the google group link posted above and star the issue to (hopefully) increase it's priority and visibility:
https://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=25301
I'm liking the phone a lot but what bothers me the most is the dialer app. Is non responsive at times, you press a contact from any call log and it doesn't do anything until the third time you try it, now it got stuck into a recent calls log and I haven't found a way to go back, it's features are great, there are a lot of them (block list, recording...), I'm only missing it being smart as the Motorola dialer for dual sim where it automatically learned which line you preferred to call your contacts with and sim switch one you initiated a call.
Anyone having dialer issues too?
Thanks
With updates phone is almost perfect for me EXCEPT THE DAMN DIALER, I can't believe anyone else has this issues too. Basically you have to press 2-3 times over a contact so it will bring the sim selection screen, maybe very few people actually uses both sims? Is the last thing that bothers me with it.
Litoven said:
With updates phone is almost perfect for me EXCEPT THE DAMN DIALER, I can't believe anyone else has this issues too. Basically you have to press 2-3 times over a contact so it will bring the sim selection screen, maybe very few people actually uses both sims? Is the last thing that bothers me with it.
Click to expand...
Click to collapse
Have you tried wiping cache and data
Sent from my ASUS_Z00AD using Tapatalk 2
Have you tried restarting the phone? Please ensure to update firmware and ASUS dialer app to latest version.
Sincerely,
ASUS_USA
[email protected]
Yes, phone is on 2.19, have done it since the beginning, recently wiped all data too, still same thing, you press a contact from the call history, it makes the click sound and all but does nothing, have to touch the contact two-three times more and then the sim selection screen comes, if you dont touch it again, it just stays there doing nothing, also after the first touch, the click doesn't sound anymore, even when it actually opens. I assume that the people that only has a one sim maybe don't see this.
I use 2 sims and I have never faced this issue.
Sent from my ASUS_Z00ADA using Tapatalk
Ok, found that issue worsens a lot with bluetooth active on the car, sometimes need to hit a contact 4-5 times.
Update, the issue was more frequently present when connected to car's Bluetooth but since 2.20.40.40 it's working as expected, sim selection screen takes 1-2 seconds to show but has come every time it has been requested. Good job.
Sent from my Nexus 9 using Tapatalk
I'm facing the same issue. It's irritating, need to touch 8-10 times or even more to make a call. Has anyone know the solution to it. Model No ASUS_Z010D. Just FYI, I have already updated to latest firmware & latest dialer, but issue persists.
Pls help
Asusarpit said:
I'm facing the same issue. It's irritating, need to touch 8-10 times or even more to make a call. Has anyone know the solution to it. Model No ASUS_Z010D. Just FYI, I have already updated to latest firmware & latest dialer, but issue persists.
Pls help
Click to expand...
Click to collapse
copy all contacts to google before doing below
if 5.0
go to settings > apps> all
find
androidsystem, asuscallingscreen, asusconfigupdater,asuscontacts, asus zenui, asus zenuiservices, contacts, contact storage, device config,google play services, google play store,setting,settingstorege, systemui, zenuikeyboard,zenuilauncher
clear data of all above apps
for 6.0 setting>apps and click thre dots and click show system and clear data of above apps.
restart device and allow permissions if required and tell if still the same
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.
Anyone else get the update for Phone by Google last night and visual voicemail tab at the bottom disappeared ? Also when clicking on Voice Mail in settings, the options flash quickly and disappears. Or is just me.
Yeah, the same for me.
I looked and I'm apparently on the beta channel of the Phone app, which hasn't been updated since 12/8/2021. I don't use visual voicemail since I use Google Voice, and I don't have a problem when I click on the Voicemail settings.
roirraW edor ehT said:
I looked and I'm apparently on the beta channel of the Phone app, which hasn't been updated since 12/8/2021. I don't use visual voicemail since I use Google Voice, and I don't have a problem when I click on the Voicemail settings.
Click to expand...
Click to collapse
I might switch to beta. On this latest update they did fix the favorites sort order. It doesn't change automatically like it did.
I got the update last night, the tab says "voice mail", I'm not sure if it said "visual voice mail" before, but the voice mail settings don't quickly flash and disappear for me, they work as usual.
I'm also on protonAOSP, maybe that's why.
wolfeyes30 said:
I might switch to beta. On this latest update they did fix the favorites sort order. It doesn't change automatically like it did.
Click to expand...
Click to collapse
Finally! It seems like years that I've tried keeping them in my own order and they would get switched back eventually, so I gave up. Or did they fix it before and then broke it again?
roirraW edor ehT said:
Finally! It seems like years that I've tried keeping them in my own order and they would get switched back eventually, so I gave up. Or did they fix it before and then broke it again?
Click to expand...
Click to collapse
No with this last update it keeps the order you leave them in but you never know what tomorrow will bring by Google
bouchigo said:
I got the update last night, the tab says "voice mail", I'm not sure if it said "visual voice mail" before, but the voice mail settings don't quickly flash and disappear for me, they work as usual.
I'm also on protonAOSP, maybe that's why.
Click to expand...
Click to collapse
It might be. You're right it was voicemail not visual voicemail as a tab but its still the same.
Just went into phone app settngs and now Direct my Call is gone as well. It was there when I did the screen record this morning lmao.