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.
Related
Hi All,
Just the other day my speaker phone stopped working. I can hear the people I am calling, but the microphone doesn't seem to work. They cant' hear me. Not at all, it is like I have the phone muted-- but it is not.
Any body else with this? Any ideas, besides hard reset to try?
Thanks
cameraddict said:
Hi All,
Just the other day my speaker phone stopped working. I can hear the people I am calling, but the microphone doesn't seem to work. They cant' hear me. Not at all, it is like I have the phone muted-- but it is not.
Any body else with this? Any ideas, besides hard reset to try?
Thanks
Click to expand...
Click to collapse
There are loads of software apps that could interfere with sound, have you installed anything recently that you can remember?
have you applied any "tweaks" that you can remember.
Does it only happen when on speaker-phone or during normal calls.
It may be worth removing the back cover to make sure that nothing has interfered with the Mic Mute button on the rear of the device.
Give us some more info an I'll try to help further.
Cheers,
Beasty
Hi Beast0898
Here is a list of software that I have installed in the last 2 weeks:
CarlosP ToneManager
cRaCKwHoRe's Snooze options
merlot mToolbox
Shubaroo Contact Fix
tarkim Keyboard controller.
I had not used the speaker phone for a while. Not since I installed any of the above, so if it is a software interference, it could be any of the above. Ideas?
The mute button is not blocked. And it happens when I enter speaker phone by turning it upside down, and when enabling it with the button on the dialer.
Any ideas?
Did you get it to work? I've encountered a weird problem recently myself where suddenly all system sounds seem to stop, including dialing tones etc.. but if I let the phone go into speaker phone mode, that does work. I hang up the call and suddenly sounds are back.
It seems to only happen when I use Groovefish and/or Nitrogen, so I wonder if one of those is causing some weirdness, just haven't pinned it down yet.
if this is the same bug I had on mine, you can either toggle the speaker phone button twice or do this:-
There is an easy workaround for this problem. On your Touch Pro 2 go to the home screen. Slide to the "Settings" tab. Tap the "Menu" softkey and choose "All Settings". Tap "Personal" then "Phone". Open the "Advanced" tab and change "Reduce noise in phone calls" to "Never".
Reference:-
http://www.chazco.co.uk/post.php?po=38
Here is a fix without turning off noise cancellation.
http://forum.xda-developers.com/showthread.php?t=826396
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
Has anyone with the verizon lg g3 experienced problems with phone volume and clarity during calls? When I use speakerphone, there is a bad echoing on the other person's end. When using normal phone speaker, the person on the other end sounds very quiet and sometimes hard to hear. Have tried disabling/enabling the phone privacy option, as well as the voice enhancement option. Phone is rooted so deciding if this is a problem worth unrooting for and getting an exchange (14 day period window ends wednesday the 13th) or if this a common issue a software update could fix. Input appreciated!
I also have had several reports of echo when on speakerphone? Has anyone else had this problem? I've flashed several roms....
I have the same issue - lg3 rooted and on cm13. People tell me they have a hard time hearing me (a lot of echo), and in most sessions volume is too low for me to hear them (in my car, especially). Doesn't appear to be a solution to this...
hey-my-knee-grows said:
Has anyone with the verizon lg g3 experienced problems with phone volume and clarity during calls? When I use speakerphone, there is a bad echoing on the other person's end. When using normal phone speaker, the person on the other end sounds very quiet and sometimes hard to hear. Have tried disabling/enabling the phone privacy option, as well as the voice enhancement option. Phone is rooted so deciding if this is a problem worth unrooting for and getting an exchange (14 day period window ends wednesday the 13th) or if this a common issue a software update could fix. Input appreciated!
Click to expand...
Click to collapse
had this issue. speaker phone basically echos no matter what for me. i have to decrease the volume so the other person doesn't hear me 8 times. friend of mine had a quite microphone issue. Returned the phone to fix it. but if all that's happening is you not being able to hear them. you can use lg volume booster to change the stock volume for calls. actual apps is on the playstore (Volume Booster LG G3 (Root)
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.
Hello, I have been having this problem with my previous s10+ and it has continued into my zfold3 so this is not specific to the zfold3 but it is where I am experiencing this issue currently.
So the problem is when I am in a call and someone texts me I get a barely audible notification sound that I almost never actually hear. I have gone into the in call settings and only see an option to turn on/off in call notifications but no customization such as what tone to use nor the volume. I also tested this with notification volume set to around 25% vs 100% and it goes from no audible sound at all to a ding that is barely hearable in a completely quiet setting, but once you are in an actual real world situation of talking to someone you will not hear it.
I talk on the phone while using headphones, specifically buds live editions. I include this info in case its relevant, but I have tested while not using the earbuds and had the same result so I don't the headphones are the problem.
Am I missing something in the settings somehow where I can actually have control of in call notifications? With my previous phone I dont remember having this issue early on. After at least a year of using the s10+ this issue started happening and I couldnt figure it out, got the new phone and purposely did not connect the transfer cable and set it up and transfered files manually to avoid potentially having a bad setting transfer over and continuing this problem. Yet the problem still continues regardless. My best guess is its something that started after a big UI update or something like that. Hoping someone can give me some insight or advice on fixing this cause its causing me a lot of strife.