As mentioned in this article it seems to be an issue with the dialer https://www.hackread.com/mans-smartphone-reboots-whenever-he-calls-911/
Related
I'm on Slim 3.3 but searching around has lead me to believe this is a problem across many ICS implementations.
I'm still on build 17 and I have encountered the following bug: while using the speaker phone and calling an automated IVR system, any DTMF tones inputted in the dial pad are sent incorrectly and thus recognized incorrectly by the IVR system. Switching the speaker phone off and using the handset solves the problem.
For example, let's say you call your banking system and it asks you to enter your account number and you have the phone on speaker phone and you enter:
1 3 2 3 2 4 5 6
The system will not recognize the digits entered correctly and almost always some digits will be duplicated, such as:
1 3 3 2 2 3 4 4 5 5 6
Again, turning the speaker phone off and using the headset directly works. This is easily reproducible for me.
Is anyone else experiencing this bug? Does the latest KANG build resolve this issue?
Click to expand...
Click to collapse
I can't find the setting for sending DTMF tones. This is really annoying as I can't log into conference calls or use services that require keyed in numbers.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
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.
Does anyone else have a large delay when trying to dial numbers while on a call? For example, when inputting a conference call number I have to wait 2-3 seconds between numbers otherwise I get an error.
I am using an unlocked N6 on Verizon running LMY47Z for reference.
Thanks in advance.
Hi, My device is Nmo-L31
Android version 7 and Emui 5
When I dial any ussd code its calling like a voice phone call and I am unable to see the result.
Is there any Solution
Google Voice did not ring on incoming calls for my Pixel 5. I tried all the online advice I could find but still failed. After 2 weeks of experimenting, I stumbled on a workaround today! I am still asking this question online so that I can share it with the public.
Many online blogs acknowledge this is a Google bug and the most prevalent workaround is to “use carrier only” for “Making and receiving calls” under Google Voice settings.
"Use carrier only" unfortunately is not much of a solution for those who travel internationally! Google Voice would expect this carrier to be a U.S. company during configuration. Roaming internationally on a U.S. carrier number runs up a HUUUGE phone bill! It begs the question of why even bother with GV if I want to involve my U.S. carrier number when I travel overseas. If I were in the U.S. today, with my unlimited plan, I would see no reasons to use GV either except if I just want to have a separate phone number that is always mine. "use carrier only" is totally brain dead from the cost perspective.
When I was on my Samsung S4, I didn't have this problem. Finally, I decided to upgrade to Pixel 5 and GV stopped ringing for an incoming call.
After I upgraded to Pixel 5, I wiped clean my S4 thinking I would either donate it or give it to a kid as a toy. Out of curiosity, I installed GV again on my S4 today to see if it still works. GV does NOT treat my S4 as a separate device but as the same "Android Device" on my Pixel 5. I guess this is due to both phones are logging into the same account. I then called my GV number and my Pixel started to ring! Curiously, S4 didn't ring. As an experiment, I opened the notification settings of the GV app on my S4 and customized it to the way I wanted it. Now, when I called my GV number, the Pixel didn't ring but the S4 rang! After that, I tried both disabling notifications on the S4 for GV and turning off S4, both methods would enable the Pixel to ring again!
Since the Pixel 5 would ring when the S4 is turned off, what would happen if GV is uninstalled from the S4? Well, the Pixel 5 stops ringing! I re-installed GV on the S4 and called my GV number, the S4 started to ring while the Pixel remained silent. This contrasts the situation after the 1st installation, ie. the Pixel rang instead.
Here is my observation:
*Both phones must have GV installed to work.
*GV would only ring one of the 2 phones, but it's hard to say which phone would ring if both are on and the notifications are enabled on both
*By disabling notifications on the S4 or turning off the phone, the Pixel always rings
*Now I can use GV either over Wi-Fi or my European SIM (traveling in Eu currently) to receive and make calls
For those who are writing these what to do with an old phone blogs, I guess they can add this workaround to their list, ie. to fix a bug for Google! I assume the old one has to be a device that doesn't have this problem to begin with. Haha.