When i connect my i9195 into my car, i can hear the person that dials me, but unfortunetly that person hears himself as well. That must be because of the car speakers, but is there a way to reduce that echo voice like in every navi cars, or voiip software?
update:
another interesting thing... I have tested the same situation with diffrent phone - Samsung Galaxy S3 with original firmware, and voice echo cancelling works just great. So the solution may be to abandon cm10 and install original firmware, but i really love cm, any solutions?
Related
Hi all
When using my Hero in my car via its AUX input the remote calling party gets their voice echo'd back to them. Now I'm used to this as I am using this as a cheap car kit solution and have had this on all my previous phones except a nokia 5800. I've done some reading and found that this is due to Echo cancellation issues.
Does anyone know if this is a software of hardware feature in a phone?
My car pairs to my phone without any issue, but none of the voice apps I've tried (Google Now, S-Voice, AVX) can hear me when I attempt to talk with them. The closest I've gotten is it hearing me but playing my voice as a delayed echo over the speakers so anything longer than 3 words and the speakers drowns out what I'm asking.
Using BT Mono I can use the voice apps the way I should be able to, but it needs to be connected before turning on. I came up with a really hokey workaround using Tasker and BT Mono with screen gestures, but it's inelegant and not %100 reliable.
I've looked into this and still haven't found an answer, is there a way to force the Note II (ATT version) to always use Mono over Bluetooth without passing voice back to he speaker while I'm talking?
This occurred with stock kernel and I've just switched to the Perseus Kernel http://forum.xda-developers.com/showthread.php?t=1983658 (Thank you AndreiLux!). on a rooted phone. If anyone has a better way of handling this or knows why the Note II is wonky with several of the other Bluetooth apps (with the echo issue) please tell me?
Hi everyone. I just got a Galaxy note 3 and its pretty great but I am having one issue. I have a Bluetooth headset that I love and it doesn't seem to be compatible with my new phone. When I make a call the sound on my side is very distorted and almost impossible to understand at any volume. The caller on the other end says that they can hear me fine. I know it's not an issue with the bluetooth headset as it worked fine with my last phone (Galaxy Note 1).
Any ideas on what would be causing the issue and how to fix it?
It would really bum me out if this headset won't work with my new phone. I went through about 5 other bluetooth headsets before I found one that the noise cancellation actually worked on.
Headset I have is the VXI Blue Parrot Express
I have a Nexus 4. The main VOIP I use is Comcast's Voice 2GO, but I also have tried others. The common denominator is the caller on the other side always complains about echo of his own voice.. It doesn't seem to matter how I am using the N4, no speaker, speaker, bluetooth hand free headphone. No matter what I try they complain about echo. On my side it sounds
Any way to avoid the echo?
No replies? Am I the only one with the echo problem?
No problem here with Mobilevoip application.
Having the best possible internet connection also it's important.
I prefer using cabled earphones on phone calls but it's very annoying on this device as I can hear my own voice through the headphones when I speak. This is a feature called "sidetone" or "microphone monitoring" and for example on windows it can be disabled.
It's surely not related to the headset because it's only when making calls through the phone app but not on whatsapp, skype, etc calls.
My phone is rooted and I am running crdroid on a11. I never ran it on stock so I don't even know if this related to crdroid or not.
Is there anyway to disable this feature or maybe install another phone app which doesn't have this?
Google is not showing much when searching for this, except for some Pixel users having this problem after updating to a13:
Pixel 4a(android 13) call issues when using a wired earphones with mic - Google Pixel Community
Edit: Just installed another dialer which didn't help, so it's something which has to be changed in the system.
Edit2: My girlfriend solved it. When using the Apple USBC to 3.5mm adapter (instead of the one I was using before) the issue is not there.