Echo problems tracking issue

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Using google voice
2.  Gizmo 5 servers
3.  And csipsimple speex codec 16 and bandwith audio set at 16

What is the expected output? What do you see instead?
Clear audio, callee received massive echoes after everything they said

What version of the product are you using? On what operating system?
Using the latest in the download section 12.06

Please provide any additional information below.
Massive echo on the call received end after everything they say.  Seems to be a 
polar issue as the callee either has a massive echo or does not.  All my 
settings are the stock settings.

Original issue reported on code.google.com by tdbj...@gmail.com on 31 Jul 2010 at 2:31

[GoogleCodeExporter]

Changed the amperage to 5 now it works perfectly no echo at all.

Original comment by sofly...@gmail.com on 11 Jun 2011 at 1:36

[GoogleCodeExporter]

@sofly : really interesting ! How did you changed amperage? 
I guess some other users will be really interested in that point (maybe I could 
document that somewhere too).

Original comment by r3gis...@gmail.com on 11 Jun 2011 at 10:50

[GoogleCodeExporter]

In expert mode/media settings/Micro amplification/changed from 1 to 5. Also did 
the'Use routing API'/'Use mode API'/'Audio mode for SIP calls'/& Micro source 
changes that you mentioned in comment 38.                                       
                                Device: Droid Incredible    

Original comment by brendonc...@gmail.com on 11 Jun 2011 at 6:46

[GoogleCodeExporter]

@mykohsu on my Nexus one with Blandroid 2.3.4, the only way to remove echo is 
to select Use Mode audio API.  I tried VOICE_RECOGNITION, and it had little or 
no impact.  My default settings are micro source: VOICE_COMMUNICATION and audio 
mode IN_COMMUNICATION.

Note that echo is cancelled well when I use Mode audio API, but only when I use 
the normal handset pressed to my ear.  If I turn on either the speaker phone, 
or if I plug in a wired headset, the echo returns.  That again points to the 
fact that audio routing is the culprit. 

@r3gis, is there any way to do some re-routing hacks when I use my wired 
headset?

Original comment by k...@laberteaux.org on 3 Jul 2011 at 7:02

[GoogleCodeExporter]

Issue 1160 has been merged into this issue.

Original comment by r3gis...@gmail.com on 20 Jul 2011 at 10:30

[GoogleCodeExporter]

Helpful hack for HTC Incredible (with android 2.3) : Issue 1160 .

Original comment by r3gis...@gmail.com on 20 Jul 2011 at 10:32

• Changed title: Echo problems tracking issue

[GoogleCodeExporter]

Issue 1135 has been merged into this issue.

Original comment by r3gis...@gmail.com on 21 Jul 2011 at 10:54

[GoogleCodeExporter]

Hi all,
We had the same issue in IMSDroid (http://code.google.com/p/imsdroid/) and we 
were using Speex echo canceler. We finally fixed the issue in our latest 
release (imsdroid-2.0.448-webrtc) by using Google's WebRTC AEC 
(http://code.google.com/p/webrtc/).
The source code of our implementation is available here: 
http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/sr
c/audio/tdav_webrtc_denoise.c

Please note that for now we only enable AEC on ARMv7 device to avoid CPU 
overhead.

Original comment by boss...@yahoo.fr on 7 Aug 2011 at 4:37

[GoogleCodeExporter]

Very interesting point. I'll also try to include as much things as possible 
from webRTC. Thanks a lot for sharing !

I was first thinking about codecs, but indeed echo canceller is probably also 
very interesting to add.

Original comment by r3gis...@gmail.com on 8 Aug 2011 at 12:29

[GoogleCodeExporter]

Well, WebRTC echo canceller is ready to land in CSipSimple. (was pretty easy to 
integrate to pjsip). 
It will be available to test in next build. For now there is not the noise 
suppressor yet.

@mamadou : did you try the aecm (mobile) implementation? I was wondering if it 
was not something interesting to try out for armeabi target.

Original comment by r3gis...@gmail.com on 9 Aug 2011 at 9:41

[GoogleCodeExporter]

Available as r995 : http://nightlies.csipsimple.com/trunk/
Let me know how it goes, maybe could be default instead of speex echo canceller 
for armeabi-v7a devices?

Original comment by r3gis...@gmail.com on 9 Aug 2011 at 12:03

[GoogleCodeExporter]

I downloaded CSipsimple.ak from here: 
http://nightlies.csipsimple.com/trunk/CSipSimple-latest-trunk.apk
To enable the echo canceler: Menu -> Options -> Média -> Annulation de l'echo.
I'm using Samsung Galaxy S (Android 2.2) and calling iPhone client with 
built-in echo canceler but I have echo. I can't say if it's better or not 
because the last time I tested CSipSimple it was in 2010. What is sure is that 
it's possible to get it working on CSipSimple (not the case for all Android 
VoIP clients) because the audio delay is low.
Which values are you using for echo tail and skew?

About AECM, we haven't tried it yet because the initial implementation based on 
WebRTC was for Windows and MAC OS X.

Original comment by boss...@yahoo.fr on 9 Aug 2011 at 4:24

[GoogleCodeExporter]

@boss, just to be sure, the echo you hear is the lack of cancellation on the 
other phone, in this case, the iPhone.  If the other caller isn't complaining 
about echo, it is because your phone is canceling echo properly.

Original comment by k...@laberteaux.org on 9 Aug 2011 at 6:58

[GoogleCodeExporter]

@ken : the iPhone has a true hardware echo canceller and from test results it 
is pretty good.

@mamadou : in CSipSimple, by default it use the speex echo canceller (for 
armv7), you have to change the echo canceller method in settings. 
To do so, you have to activate the expert setting mode (in settings, press menu 
and select expert mode, then in media settings choose the cancller mode to be 
WebRTC. You can also change the tail length).
About skew, I use 0 for now. Do you have a suggestion for a better value?

I've seen that in doubango code you said that 16 and 32kHz produce weird 
results. On my side it does not sound so bad. What do you observe with 
doubango? 

Also, in this case, I was wondering in this case what would be the best way to 
do :
bufferFarend, process, bufferFarend, process 
or
bufferFarend, bufferFarend, process, process

Original comment by r3gis...@gmail.com on 9 Aug 2011 at 8:01

[GoogleCodeExporter]

-- correction, build r995 was not build with webrtc available (my auto build 
script had not the option to build with webrtc), I'm currently running a new 
r995 build with webrtc inside :).

Original comment by r3gis...@gmail.com on 10 Aug 2011 at 12:20

[GoogleCodeExporter]

I have tried different providers and called and had callers with cell and land 
lines call me and in all cases, they hear an echo.  Turning the sound down to 
where I can barely hear the caller does eliminate the problem.  I also tried 
both 3g and wifi with the same results.  I tested all of this with an Android 
2.2 Samsung Galaxy Precedent.

Original comment by brucej1...@gmail.com on 9 Nov 2011 at 4:13

[GoogleCodeExporter]

Issue 1422 has been merged into this issue.

Original comment by r3gis...@gmail.com on 29 May 2012 at 3:52

[GoogleCodeExporter]

Issue 1255 has been merged into this issue.

Original comment by r3gis...@gmail.com on 17 Aug 2012 at 2:36

[GoogleCodeExporter]

csimple install� sur un Galaxy note ne fonctionne pas, abonn� sfr libertalk
l'appel fonctionne mais il n'y a pas de son ni dans un sens ni dans l'autre.

Original comment by raoul2ja...@gmail.com on 18 Aug 2012 at 9:14

[GoogleCodeExporter]

Issue 1915 has been merged into this issue.

Original comment by r3gis...@gmail.com on 27 Aug 2012 at 3:39

[GoogleCodeExporter]

Issue 1915 has been merged into this issue.

Original comment by r3gis...@gmail.com on 27 Aug 2012 at 9:39

[GoogleCodeExporter]

I have a Nexus 4 running 4.2 that is rooted and unlocked running the stock ROM. 
 I have calls setup to only use wifi with a business class comcast connect, or 
a 35/35mb frontier fiber connection at home.  At either location the callees 
hear themselves and have a really bad echo after about .1 to .3 seconds after 
everything they say  The only thing I have found that stops the echo completely 
is if I mute the mic in the dialer.  If I turn down the speaker/earpiece volume 
to about 6-7 notches up that usually helps alot and the echo is not nearly as 
loud.  I just loaded the march 5th nightly, and tried a few test calls which 
also had the echo.  I have asked other Nexus 4 users some have the issue some 
do not. I have attempted countless configurations of echo canceling in the main 
section and the audio troubleshooting section.  I think I have almost tried all 
the settings, and nothing makes any difference whatsoever.  If I knew how to I 
would send you a log of what my settings are now and try to list some of the 
settings I have tried. If there are any suggested settings I should try I'm 
completely open to suggestions at this point.  I really like the software and 
would love to get it working.  

Original comment by derju...@gmail.com on 5 Mar 2013 at 6:21

[GoogleCodeExporter]

Issue 2226 has been merged into this issue.

Original comment by r3gis...@gmail.com on 9 Mar 2013 at 8:32

[GoogleCodeExporter]

I got a Nexus 4 (Android 4.2.2) and no matter how I configure the app, it just 
makes absolutely no difference (and I tried ALOT). I can hear myself even when 
making the built-in audio test. Echo lasts for about 0.5 s and is repeated 2-3 
times. It's not usable at all for me. I'm giving up.

Original comment by jung.rup...@gmail.com on 2 Jun 2013 at 2:33

[GoogleCodeExporter]

Select "Open-SL ES" -> "Java" and select WebRTC routing implementation and 
default WebRTC echo canceler mode.

Original comment by q...@mt2014.com on 2 Sep 2013 at 12:20

[GoogleCodeExporter]

Using Nexus 4, JB 4.3, sound quality is absolutely phenomenal.
Here are the steps that work for me:

1. Reset audio to default settings.
2. Uncheck absolutely everything, even under the Audio Troubleshooting section.
3. Check: "IO Queue" and "Use mode audio api".
4. Force close application (seems to be needed to reinitialise settings).
5. Profit!

Original comment by red...@gmail.com on 6 Sep 2013 at 6:34

[GoogleCodeExporter]

I can confirm this problem exists on the Nexus 5 for both the CSipsimple app 
and the native dialer. 

Fix: In CSipSimple, settings > media > audio troubleshooting > audio mode for 
SIP calls > IN_Call

Completely fixes echo problems. 

Original comment by will.e.c...@gmail.com on 13 Dec 2013 at 4:17