Related
I mean, it's supposed to transcribe messages, right? Mine sure doesn't.
Not a single answer?
I didn't think anyone ever used it. Visual voicemail has always sucked, regardless of phone. T-Mobile I'm assuming? I'll test mine for you shortly and report back my results.
JoeMoDo said:
I didn't think anyone ever used it. Visual voicemail has always sucked, regardless of phone. T-Mobile I'm assuming? I'll test mine for you shortly and report back my results.
Click to expand...
Click to collapse
Nah, MetroPCS. Their built-in app sucks. I miss the Google Phone app, with VM transcription. It's a shame I can't get even the SDK 23 versions to work on this phone.
GuyInDogSuit said:
Nah, MetroPCS. Their built-in app sucks. I miss the Google Phone app, with VM transcription. It's a shame I can't get even the SDK 23 versions to work on this phone.
Click to expand...
Click to collapse
Dur, if I tried reading, it's all over this post that you're using Metro. In my time with MetroPCS I never had the visual voicemail work.
And you're trying to use android dialer? Yeah, since this phone uses a custom LG UI it will be a bit of a pain.
JoeMoDo said:
Dur, if I tried reading, it's all over this post that you're using Metro. In my time with MetroPCS I never had the visual voicemail work.
And you're trying to use android dialer? Yeah, since this phone uses a custom LG UI it will be a bit of a pain.
Click to expand...
Click to collapse
Google Contacts worked, though it's pointless without the dialer.
*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'm not sure if this is a Oreo issue or not, as soon as I got the phone I updated it to Oreo and wiped it. When I go into my call log and try to view the details of a call, the app crashes non stop no matter what I do. I can go into either Contacts app and look at a contact and get call details there just fine. Anyone have any ideas? I went to the phone app and cleared the app cache and data but its still doing it.
Also, anyone know why Razer duplicated what seems like random apps? Calculator, Contacts?
Can anyone looking at this at least try it and report back? I use call details a ton for keeping track of call time and right now its a huge pain in the butt.
I am reporting in. I have come across this bug. Honestly we should report it on the Razer insider forum....
Alright I'll get on there and report it too.
Yeah, same thing is happening to me as well.
They are wanting me to upload a bug report which I'll be doing sometime later today. The thing that really sucks, the phone app doesn't appear to be listed on the play store so they will have to issue a system OTA, which I'm assuming is going to take longer.
I also just noticed, voicemail notification cause the dialer app to crash. I have 4 voicemails I was not notified about.
I'm almost positive that I've gotten voicemail notices just fine.. but I'll test this later today to see.
Anyone get a fix or update on this?
gatorgal88 said:
Anyone get a fix or update on this?
Click to expand...
Click to collapse
Are you still experiencing this on O MR1?
All of these issues are fixed according to some users on XDA or the Razer forum. I wouldn't know cause I sent mine back. Hopefully the 2nd one is a little less of a mess.
lonetormenter said:
Are you still experiencing this on O MR1?
Click to expand...
Click to collapse
My phone is not experiencing a problem. My sister, however, started having the problem after upgrading to Oreo and she is up to date and still has the issue.
Very bizarre.
We have cleared cache and data and no change. She is currently using a 3rd party dialer in the mean time.
gatorgal88 said:
My phone is not experiencing a problem. My sister, however, started having the problem after upgrading to Oreo and she is up to date and still has the issue.
Very bizarre.
We have cleared cache and data and no change. She is currently using a 3rd party dialer in the mean time.
Click to expand...
Click to collapse
Problem solved. She factory reset her phone and all is good!
Oops. Didn't see all the other replies before replying. Couldn't delete post so had to edit.
I have not experienced this bug, I'm on latest firmware O MR1
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.