Menu

#119 Echo problems tracking issue

Accepted
nobody
None
Medium
Defect
2013-12-13
2010-07-30
Anonymous
No

Originally created by: tdbj...@gmail.com
Originally owned by: r3gis...@gmail.com

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.

Related

Tickets: #1135
Tickets: #1160
Tickets: #1174
Tickets: #1356
Tickets: #1422
Tickets: #1453
Tickets: #1915
Tickets: #2378
Tickets: #569
Tickets: #81
Tickets: #815
Tickets: #954

Discussion

<< < 1 2 3 (Page 3 of 3)
  • Anonymous

    Anonymous - 2011-06-11

    Originally posted by: brendonc...@gmail.com

    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   

     
  • Anonymous

    Anonymous - 2011-07-03

    Originally posted by: k...@laberteaux.org

    @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?

     
  • Anonymous

    Anonymous - 2011-07-20

    Originally posted by: r3gis...@gmail.com

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

    Summary: Echo problems tracking issue

     

    Related

    Tickets: #1160

  • Anonymous

    Anonymous - 2011-08-07

    Originally posted by: boss...@yahoo.fr

    Hi all,
    We had the same issue in IMSDroid (https://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 (https://code.google.com/p/webrtc/).
    The source code of our implementation is available here: https://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyDAV/src/audio/tdav_webrtc_denoise.c

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

     
  • Anonymous

    Anonymous - 2011-08-08

    Originally posted by: r3gis...@gmail.com

    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.

     
  • Anonymous

    Anonymous - 2011-08-09

    Originally posted by: r3gis...@gmail.com

    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.

     
  • Anonymous

    Anonymous - 2011-08-09

    Originally posted by: r3gis...@gmail.com

    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?

     

    Related

    Commit: [r995]

  • Anonymous

    Anonymous - 2011-08-09

    Originally posted by: boss...@yahoo.fr

    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.

     
  • Anonymous

    Anonymous - 2011-08-09

    Originally posted by: k...@laberteaux.org

    @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.

     
  • Anonymous

    Anonymous - 2011-08-09

    Originally posted by: r3gis...@gmail.com

    @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

     
  • Anonymous

    Anonymous - 2011-08-10

    Originally posted by: r3gis...@gmail.com

    -- 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 :).

     

    Related

    Commit: [r995]

  • Anonymous

    Anonymous - 2011-11-09

    Originally posted by: brucej1...@gmail.com

    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.

     
  • Anonymous

    Anonymous - 2012-08-18

    Originally posted by: raoul2ja...@gmail.com

    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.

     
  • Anonymous

    Anonymous - 2013-03-05

    Originally posted by: derju...@gmail.com

    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. 

     
  • Anonymous

    Anonymous - 2013-06-02

    Originally posted by: jung.rup...@gmail.com

    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.

     
  • Anonymous

    Anonymous - 2013-09-01

    Originally posted by: q...@mt2014.com

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

     
  • Anonymous

    Anonymous - 2013-09-06

    Originally posted by: red...@gmail.com

    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!

     
  • Anonymous

    Anonymous - 2013-12-13

    Originally posted by: will.e.c...@gmail.com

    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.

     
<< < 1 2 3 (Page 3 of 3)

Log in to post a comment.