if I call bank of america, or verizon or anyone and if i'm on any rom i've noticed the number pad doesn't work whenever i open/close it during a call to enter options, does anyone else experience these issues....... i've tried everything on every rom.
edit - i have the dial pad sounds on, and it always makes the noise. and sometimes i can enter the correct password 5x times in a row and it won't take it, then they'll just transfer me, or other times it just wont recognize i typed anything at all.............
i've flashed different radios, bootloaders, etc. i'm on vzw, tried chroma rom, 5.1, 5.1.1 stock roms, etc....... automated systems and my dial pad doesn't work..
That has never happened to me on any rom I have flashed. Do you have any other mods installed?
I do not no. And full stock Roms.
Sent from my Nexus 6 using XDA Free mobile app
This happens to me ALL the time. It seems like ever since I updated to LMY47E I have noticed this issue. Maybe it has to do with the call being a data call?
Glad I'm not alone. My phone came on E. Now I manually flashed international boot loader radio and ROM rooted and unlocked and unencrypted. Stock though. Issue still occurs.
Sent from my Nexus 6 using XDA Free mobile app
Is it a data call? I just use volte but that doesn't mean its a data call that means you can use data and make a phone call at the same time. Right ??
Sent from my Nexus 6 using XDA Free mobile app
Related
Do a lot of conference calls and have all numbers set dial access codes and pins using the (p) Pause. With LP they do not fully send when automated system repeats what was sent was never the full number. Example 8778741777,,,,1234567890#
The systems might just get 1234567 of the access code and this is for all company numbers I call.
Anyone have same experience?
Anyone have a fix?
parcou said:
Do a lot of conference calls and have all numbers set dial access codes and pins using the (p) Pause. With LP they do not fully send when automated system repeats what was sent was never the full number. Example 8778741777,,,,1234567890#
The systems might just get 1234567 of the access code and this is for all company numbers I call.
Anyone have same experience?
Anyone have a fix?
Click to expand...
Click to collapse
What rom are you using? It works for me on stock and on slimlp, our systems use webex which i dial into and have to use codes and they work fine.
Was using LS and now on Chroma but happened to me on stock... What I did to slow it down was put a (p) after 3 numbers seems it was sending it too fast for that system to handle...so think its now a phone issue more so how the other end was getting to numbers.
Thx for the reply
Same issue for me, using Chroma ROM and the latest radio (MDM9625_104446.01.02.95R). Not only are pauses not recognized, generally dialing digits after connection does not work. Huge issue, might try reverting the radio.
swamp2 said:
Same issue for me, using Chroma ROM and the latest radio (MDM9625_104446.01.02.95R). Not only are pauses not recognized, generally dialing digits after connection does not work. Huge issue, might try reverting the radio.
Click to expand...
Click to collapse
I seem to have found a reliable way to correct this. Was playing around with VoLTE and found this to be a contributor. If you have VoLTE enabled in 5.1 ROM, that is under Settings>Wireless&networks>More>Cellular networks>Enhanced 4G LTE Mode. When I turn off this option, post connected call digit dialing seems pefect. Switching it back on goes right back to not able to recognize.
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
incisivekeith said:
Hi, I've noticed recently that sometimes when I try to call a number, it does not call; instead the dialpad goes blank. This occurs especially trying to dial numbers from Google maps or from contacts. Does anyone know a solution to this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
No one with that issue?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
I have a similar issue! WHen calling someone it says dialing for like 10 seconds. Sometimes i miss calls because when someone calls me it says the netwrk is busy or something like that,
Not sure why this is happening. The only "system" change I've made is installing themes.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Has anyone come across a fix for this?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
stu5797 said:
Yes and unfortunately it is that the 3 or 4 of us have defective phones. We need new ones
Click to expand...
Click to collapse
Not sure that's the solution. The issue wasn't present since the day I bought the phone.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
if i recall, i having this problem on galaxy s5 or note4 edge, cant remember.
when i make a call, i always turn off wifi, it fixed the problem for me.
Did you swap the SIM from your previous phone to this phone without activating the new one? I did this and had issues. I called AT&T, and they said my IMEI from my old phone was showing and not the new one. You might try giving them a call and make sure the IMEI showing on their side is that of your new phone.
I notice that this frequently occurs if I start a call while connected to Wifi and then walk/drive outside the Wifi range. Toggling Airplane mode always fixes it for me.
eventer289 said:
I have an issue like that, but the dial pad doesn't go blank. the call just sits there in silence and never connects. I have to toggle Airplane mode to fix it.
Click to expand...
Click to collapse
I have this exact issue and the airplane mode toggle fixes it. I would like to know what is going on , whether my device is defective or if there is a better fix.
Same issue (not connecting calls, not the screen blank issue)
It comes and goes without a change of setting g, but instead of a phone ringing or vibrating it just shows a new voicemail. My wife complains that I never answer my phone but it never rings, even with all the sounds at their highest. Any ideas what might cause this?
On pure rom
Sent from my Nexus 6 using Tapatalk
Bad/weak signal?
Have you tried having her call you again to see if it rings - while in the same room? I feel like it could be a rom issue, but it's probably more related to service.
Carrier or rom. Need to reflash stock and start from scratch. If works on stock which I believe will be the case since mine works then clean flash the rom. It's not rocket science.
If you check the Sprint thread in General you'll see that a lot of people, including myself, have the same problem. It happens when you're connected to LTE and WiFi at the same time. Until a patch is released by Sprint, it seems the only thing we can do is turn off WiFi or change the preferred network type to 3G.
The bug is present on stock M P3 too.
Sent from my Nexus 6 using Tapatalk
Hi guys. Been having issues receiving calls lately. The phone doesn't ring and the caller says it goes straight to voicemail. I read through some support forums on Verizon's website and it looked like other people were having the same issue. Verizon suggested making sure Advanced Calling was on. However, it DOES work for me when Advanced Calling is OFF. Has anyone experienced this? It's pretty frustrating. I'm on Computerfreek's 1.5 build. Thanks in advance.
Sent from my XT1254 using XDA Free mobile app
I too have been having this issue; it does not occur consistently but every few days I am told by people trying to contact me that their calls are going straight to voicemail. I do have Advanced Calling on but I noticed the last time it happened (last Friday afternoon 10-23 at my office where I always have service) that when I made a phone call, I could not access data / internet simultaneously also. After a reboot, everything was back to normal though; I too am on Computerfreek's 1.5B Pon-3 Base w. IOS Emoji build.
met the same issue in China, everyday received several SMS says somebody called you but not answered...
Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app
papstar said:
Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I use Google Voice strictly for voicemail (no calling), but I do not have the app installed on my phone. I just receive vm notifications via gmail.
I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app
papstar said:
I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I have used google voice since its inception on other phones but have been having issues with it since advanced calling was added to this phone; at first with kitkat, I would get calls and see if I missed calls, but if someone left me a voicemail, I would not receive it. On rooted lollipop roms, I have tried using GV with and without the app installed but it never seems to work perfectly. On a positive note, I haven't noticed the issue occurring since the last time I posted about it but I will most likely make the switch to vzw if it does.
So I was talking with someone on the phone at night and when I ended the call, I put my phone on charge and went to sleep. The morning after, I tried to make a call, the dialer rings, but right after the other person picks up, they cannot hear me, nor can I hear them. Aside from the stock dialer app, I have tried using google's dialer app, but it crashes instantly after allowing permissions to my contact and dialer access. I have tried reflashing radio as well as kernel which didn't seem to solve the problem.
I had this problem a month back when Nougat image was first released (this problem happened when i was unrooted as well), I factory resetted the device which solved the issue. I am currently on PN 10-25-16 build and the problem has returned, has anyone had this same issue or know of any fix. I really don't want to reset to factory as of now as it's too much of a hassle to re-setup the device and what's to say that the problem will come back one month later, looking for a permanent fix. (maybe it has something to do with the google dialer app crashing instantly after opening?)
Also I am on Verizon
It's because of volte
Sent from my Vivo 5R using XDA-Developers mobile app
903tex said:
It's because of volte
Sent from my Vivo 5R using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried disabling it, same problem
Try running pure nexus