I need to access menu based phone systems using the key pad on phone calls sometimes and the many of the systems don't recognize the DTMF tones anymore but some do. Not sure if this changed because of a google update or what. I tried toggling the "dial pad tones" and rebooting my phone with no success. Anyone else having this problem or find a solution?
Same problem. Haven't figured out a solution. Seems like a recent update changed the DTMF behavior.
Sent from my Pixel 2 XL using Tapatalk
i have very practical solution for you have a recording of all the numbers and symbol tones and play them back in to the mic with some headphones or carry another phone around with you to play in to the mic
Related
Had some issues with the touch tones not working correctly with the speakerphone enabled. Didn't find any threads here on XDA but found a few over on a couple other android forums.
Basically it seems that when using the touch tones with speakerphone enabled, the mic picks up the speaker phone and the receiving end hears each touch tone twice.
I had the issue when trying to call verizon wireless to enter my passcode, as well as trying to setup my voice mail. I have 3 separate Galaxy Nexus phones in my family, and the issue can be replicated on all 3 phones.
Also noticed lowering the volume on the speakerphone can alleviate the issue too, but it's just kind of annoying as I don't want to hold the phone up next to my ear when I'm trying to enter things on the dial pad.
I've also tried switching the DTMF setting between long and normal, the problem still exists
Hoping with a firmware update they can filter out the touch tone, or just not make the touch tones audible to ourselves. (I'm assuming
this is because the speaker is so close to the mic on the GN)
Anyway, I don't think there's a fix for it yet, but I'm just posting here to see if anyone else is experiencing the same issue, and to make people aware of it.
Also found the issue on google support here:
http://code.google.com/p/android/issues/detail?id=24467
Bump,
Anyone else run into the same issue? Or have some secret fix I don't know about? (Other than turning off the speaker lol)
Sent from my Galaxy Nexus using XDA App
This explains the problems I was having the other day trying to join a Go-To-Meeting - would not accept my pin.
I was on speaker phone too - ty for this !
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
_Gir_ said:
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
Click to expand...
Click to collapse
Just realized this before I came to post, thanks for pointing it out too! Mute FTW!!!
i too noticed this as well when i first got it and think that it ridiculous that it wasnt thought out better.
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
ConanOBrien said:
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
Click to expand...
Click to collapse
This is the workaround I've been using for about a month now with no issues. I had the same issue where the conference call service wasn't getting my pass code entered correctly.
Only issue now is the headset echo heard by connected parties, which has been reported and hope to be fixed soon. I've tried several workarounds here but none have been bulletproof.
Problem: Instead of playing the selected ringtone when I get phone calls I hear the bonk sound hear when I adjust my volume? This remains even after reboot.
Solution: It was an application called CallBlocker. I had enabled a setting called Pre-Mute Ring which was causing the issue.
Call controll does work very well, however this feature does have a caveat indicating it might not work correctly on all phones. I think the purpose is to mute the ring until it can identify if the call is on the blacklist or not. After that, I think it's supposed to unmute so you can hear the ring.
I finally figured it out after numerous reboots and a kernel upgrade. The problem remained so I figured it had to be some piece of software that messed with the call settings.
Sent from my SPH-D710 using Tapatalk 2
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
Like i said in the title, i cant hear the dial tone when making a call(unless on the speaker), if the person im calling answer the call, i cant hear him, if its me answering the call, the other person cant hear me neither. I tried to use the SMMI Test to see if it was a hardware problem, but when i use the code on the calculator nothing happens, also i tried safe mode to see if it was a software problem but the problem remains. It's the Asus Zenfone 2 ZE551ML if it matters.
Well you can turn on the dial pad tone in the phone settings. but the problem with you not hearing them and them not hearing you, that's something else. I've had to send my phone back twice for an issue like that. they say they replace the Motherboard, but the issues is still there. on and off. maybe this thread can stay around to get some different views on the issue.
Razen4 said:
Like i said in the title, i cant hear the dial tone when making a call(unless on the speaker), if the person im calling answer the call, i cant hear him, if its me answering the call, the other person cant hear me neither. I tried to use the SMMI Test to see if it was a hardware problem, but when i use the code on the calculator nothing happens, also i tried safe mode to see if it was a software problem but the problem remains. It's the Asus Zenfone 2 ZE551ML if it matters.
Click to expand...
Click to collapse
Me too facing the same problem..any solution to this?
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Disable ok Google from any screen option or uninstall Google update which is causing this problem then test.
After uninstall Google wipe cache partition then reboot.
Third Party App "SoundAbout" may be helpful
Razen4 said:
Like i said in the title, i cant hear the dial tone when making a call(unless on the speaker), if the person im calling answer the call, i cant hear him, if its me answering the call, the other person cant hear me neither. I tried to use the SMMI Test to see if it was a hardware problem, but when i use the code on the calculator nothing happens, also i tried safe mode to see if it was a software problem but the problem remains. It's the Asus Zenfone 2 ZE551ML if it matters.
Click to expand...
Click to collapse
I had similar problem with my HTC one X , after I flashed some patch for sound enhancements. I searched on google then found a solution on reddit which suggested to use a third party app named "SoundAbout". It routes the speaker sound to earpiece. has many settings and thus may be useful. I could still use my old HTC one X with this and satisfied. This is not a permanent solution to the root cause but at least it is useful to some extent.
Hello,
Recently I have my Nexus 5x antenna repaired. But the guy messed up some other things during the process. I sorted out other problems but one still remains. The mic used during handsfree talk broken I guess. It works without problem as a handset. But when I open speaker other party can't hear me. It wasn't working with whatsapp calls neither. At the moment my N5x runs DP4. After some search I found a solution: forcing phone to use other mics by editing mixer_paths.xml. this way I was able to get it work on other apps. now I can record videos with sound, can speak handsfree mod on video and voice calls in whatsapp. But normal phone still doesn't work. What I did was to change the default value "dmic3" of "speaker-mic" with "dmic1" of "handset-mic" this way I think it uses the mic that which is used in handset use. But I couldn't figure out how to achieve the same result with normal voice calls. Anyone familiar enough with mixer_paths.xml to indicate me correct paths to edit?
Thanks in advance.
Noone?