Open GoogleCodeExporter opened 9 years ago
FWIW, this should be a "feature request", not a "Defect", but I have no idea
how to
change that.
Original comment by sgunder...@bigfoot.com
on 6 Aug 2009 at 10:34
Give more details please. Who is hearing the echo? Sipdroid has echo cancelling
for
speakerphone.
Original comment by pmerl...@googlemail.com
on 6 Aug 2009 at 10:53
We were two ADP1 users calling each other; none of us were using speakerphone.
I heard
my own echo, and he heard his own echo. We didn't hear each other's echo.
Why is echo cancelling only enabled for speakerphone?
Original comment by sgunder...@bigfoot.com
on 7 Aug 2009 at 6:56
Strange, the people I called from my ADP1 did not hear their echo (and I did
not
either). You can try lowering the volume on your ADP1.
Original comment by pmerl...@googlemail.com
on 7 Aug 2009 at 11:05
The volume was already far enough down, really -- much lower and it would have
been
difficult hearing the other party.
What are the parameters for the echo cancellation (filter length etc.); where
in the
code can I find that?
Original comment by sgunder...@bigfoot.com
on 7 Aug 2009 at 10:16
The code is in RtpStreamSender (after record.read). Did you have any other
audio link
between the two ADP1, like standing in the same room or similar?
Original comment by pmerl...@googlemail.com
on 8 Aug 2009 at 6:28
(Sorry for not responding earlier, I didn't notice the comments.)
No, the ADP1s were several kilometers away from each other.
It's not unique to the combination of two G1s either: I've ordered POTS
breakout via a
company called Phonzo, and it works fine via pbxes.org (or rather, it works
fine
outgoing -- incoming not yet), but the other end was complaining about hearing
echo of
herself.
Original comment by sgunder...@bigfoot.com
on 23 Aug 2009 at 6:23
For what it's worth, I also experience this problem. The person I talk to can
hear an
echo of herself. I use a G1, and the other part uses an ordinary mobile phone or
land-bound phone. I also use Phonzo via pbxes.org which works great (both
incoming
and outgoing)
Original comment by rickyn...@gmail.com
on 31 Aug 2009 at 10:26
rickynils: How do you get incoming to work with Phonzo and pbxes.org? I can't
get it
to work at all -- just busy signal when someone tries to call me...
FWIW, I've tried enabling speakerphone, and it actually _reduces_ the echo
compared to
normal talking.
Original comment by sgunder...@bigfoot.com
on 31 Aug 2009 at 10:35
I used my HTC Hero to talk to another IP phone. The voice on my phone is
perfect,
but there is echo on the IP phone.
The echo will be gone if I mute on HTC. I think the TX gain from HTC is too
loud,
lower the RX gain on HTC does not help. Anyway to lower the TX gain?
Original comment by tommy.ht...@gmail.com
on 30 Nov 2009 at 9:48
Issue 214 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 30 Nov 2009 at 10:10
The parties I call also experience a strong and extremely annoying echo. I set
microphone and earpiece to low to minimize echo but people I call are still
complaining of echo.
Any progress on that matter?
Original comment by christia...@gmail.com
on 8 Mar 2010 at 8:24
Will you ever fix that honestly? Your app is without
this fix just unusable cause remote party will
always keep complaining about his own echo.
Please do something
Original comment by christia...@gmail.com
on 15 May 2010 at 9:44
My fix is to just turn down the volume on the earpiece. If there was a better,
more
technically involved way of doing echo cancellation, I would really appreciate
it.
Please forgive the demanding tone of the previous post. Most of us realize
this is a
community project run by people who donate their time and talent. Thank you!
Original comment by jamiehof...@gmail.com
on 15 May 2010 at 12:34
Yup, Sorry from me too. Just a bad day. My
apologies.
Original comment by christia...@gmail.com
on 15 May 2010 at 2:22
People I call (calling a PSTN user via SIP) hear significant echo.
Original comment by nickurak
on 1 Jun 2010 at 5:04
Interesting links:
Open Source Echo Canceller Part 2 - How Echo Cancellers Work
http://www.rowetel.com/blog/?p=21
Open Source Line Echo Canceller (OSLEC)
http://www.rowetel.com/ucasterisk/oslec.html
Original comment by pablog.u...@gmail.com
on 19 Jul 2010 at 12:16
This is a significant issue for the Serval BatPhone (true P2P mesh mobile
telephony - see servalproject.org for details). Whenever we have tried to
demonstrate our phones in speaker-phone mode, e.g., for filming the audio very
rapidly degrades to near-static due to feedback from the uncancelled echo. See
the following video for two brief examples at ~50sec and ~1:10 of this:
http://www.youtube.com/user/PaulGardnerStephen#p/a/f/1/K819ggBvkU0
Fortunately I know and live close to David Rowe (or rowetel.com). I will have
a chat to him about the feasibility of getting OSLEC into SIPDroid.
We also have some other patches on the way for allowing SIPDroid to talk to a
local instance of Asterisk on the phone (currently SIPDroid complains that
there is no data connection, and refuses, or worse, tries, but does not allow
any codecs).
Paul
Original comment by paul.gar...@gmail.com
on 23 Jul 2010 at 10:13
Issue 574 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 28 Jul 2010 at 8:20
Paul,
Speex has pretty decent AEC, and that's what SIPDroid tries to use. I'm
fighting with the same issue right now and I should say the problem here is
that Android has no real-time audio support. Speaker-to-Mic delay varies a lot,
even during a call. And this destroys AEC. I don't think OSLEC may help.
Original comment by alexander.chemeris
on 5 Aug 2010 at 10:29
This issue is NOT due to the echo cancelling features on the SAMUNG GALAXY S.
It's due to audio playing over the external (rear) speaker instead of the
earpiece.
Hope this is fixed soon!
Original comment by longmad
on 13 Aug 2010 at 2:18
I'd like to point out that this is still a problem. I strongly urge that echo
cancellation is incorporated, otherwise the program's main function is almost
unusable.
Original comment by tdfo...@gmail.com
on 30 Aug 2010 at 4:26
I am indeed noticing echo problems on the other end. Using SIPDroid with PBXes
tied to Gizmo5 (being routed through Google Voice).
Original comment by kni...@gmail.com
on 3 Sep 2010 at 2:44
Same for me using sipdroid and pbxes on a samsung i5500: i don't hear any noise
or echo but on the other phone it's very loud!
Original comment by woland...@gmail.com
on 15 Sep 2010 at 12:24
Oh, I should probably mention that I'm using a Droid Incredible with SkyRaider
2.5.2
Original comment by kni...@gmail.com
on 15 Sep 2010 at 1:40
I have a similar problem than the original reporter: I am using a Samsung
Galaxy S (or a Nexus One sometimes) with SipDroid using pbxes and VoipCheap for
outgoing, I call a landline and I hear my voice back after about 1s delay. It
is the same for Wifi and 3G also.
Original comment by r...@dlux.hu
on 21 Sep 2010 at 4:47
I am not an android developer. I also have a samsung galaxy s from T-mobile. I
have the Firmware version - 2.1-update1. I am experiencing the same problem
with my phone. The person at the other end is not able to hear me because of
very bad echo problem. Whereas, I am able to hear them loud and clear. I have
added a rubber case for the phone. It seems that the case also adds to the
problem (Not quite sure). Will this be because of a software problem or hard
ware ? It would be great if some one could help me out. I have to plan
accordingly to return the device incase if it is a hardware problem.
Original comment by rahul.su...@gmail.com
on 28 Sep 2010 at 3:26
I have a similar problem !
Equipment used:
Samsung Galaxy S
Sipdiscount.co.uk
Calling from Greece to Sweden
When I am using Siemens C475IP for the same call
i do not get any complains, I guess the problem must be related to SIPDROID
or the HW used.
I guess my Siemens phone have hardware solutions for noise and echo
cancellation.
I have tried some other sip clients for Android and they all show the same
problem.
Original comment by je.johan...@gmail.com
on 30 Sep 2010 at 7:40
Hi all,
I am having echo trouble too, but only for the party I call with Sipdroid.
I tried with and without the headphones: there is no change, the echo is there.
I was using it over wifi and without any vpn.
SIP provider: netappel.fr
Device: Samsung Galaxy I5500
many thanks,
rosch
Original comment by lucas...@gmail.com
on 2 Oct 2010 at 9:10
I heard myself with Samsung Galaxy S I9000 (International) when using some of
the low bitrate codecs. PCMA / PCMU (64 kbit) worked fine. We used PBX inside
the WIFI router's network.
Original comment by DGunchev
on 19 Oct 2010 at 6:24
I have a similar problem too. i don't hear any noise or echo but on the other
phone it's very loud.
Device : Samsung Galaxy S
SIP Provider : Gizmo5
Network : WLAN
Original comment by caglaroz...@gmail.com
on 26 Oct 2010 at 4:06
since the upgrade to 1.6.1 (from some 1.5.x version) i've no more problems with
echo.
Motorola Milestone
Android 2.1
Original comment by globifro...@gmail.com
on 4 Nov 2010 at 12:01
Well, remote party still has massive echo with 1.6.1 for me - htc magic android
2.2
Original comment by christia...@gmail.com
on 4 Nov 2010 at 8:32
We just tested echo cancellation using SipDroid, CSipSimple, and LinPhone on an
HTC Desire. SipDroid seems to use a squelching mechanism now which often just
squelches both sides. The other two apps work better (Speex 8-bit, volume one
below the maximum) but either the volume is too low or the feedback echo/noise
is too high.
Original comment by blon...@gmail.com
on 5 Nov 2010 at 7:20
I have the same problem and it makes the app unusable for me
Original comment by kur...@gmail.com
on 6 Nov 2010 at 8:30
I can confirm the problematic echo reported by all those I call with SipDroid
1.6.1 on an HTC Wildfire (even when using headsets), using phonzo via
pbxes.org.
Original comment by alanssol...@gmail.com
on 7 Nov 2010 at 8:41
I have a problem concerning echo, the person I call or the person which calls
me gets back everything he/she says. I've tried other sip clients too but I
want to stay with Sipdroid, and the problem occurs with every other client
anyway. I have a Samsung Galaxy S international i9000 with Android 2.2. If I
connect a headset or just headphones and use the internal microphone, the echo
is gone. So the problem seems to be between the internal mic and speakers. I
tried to set both mic and speakers to min volume, but that does not help
anything. Any hints on how to solve this issue?
Original comment by make...@gmail.com
on 8 Nov 2010 at 8:49
I have a galaxy s and I have this annoyng problem too
Original comment by angelo.b...@gmail.com
on 8 Nov 2010 at 11:19
me too the same problem samsung galaxy s, other person hears echo
came on guys so many complaints and no solution yet
Original comment by josip.ra...@gmail.com
on 11 Nov 2010 at 8:55
Hi, same problem with zte blade
Original comment by luis...@gmail.com
on 12 Nov 2010 at 10:54
Hello,
I have addressed the problem with my Samsung Galaxy S i9000 by testing out
CSipSimple, where you can set earpiece and mic gain manually in 0.1+- steps,
and I was able to solve the echo problem by just setting the gain to the
minimum available setting. So I request at the developers of Sipdroid, please,
could you add an advanced option for setting the mic/earpiece manually, because
it seems the Sipdroid minimum profile of 'Low' is not low enough for the i9000
for reducing the echo.
Original comment by make...@gmail.com
on 20 Nov 2010 at 5:14
In my opinion the echo cancellation should be handled by the hardware (and it
is actually done when using the devices as actual phones).
The resources required to do software echo cancellations are generally to much
for current devices. Skype is the only application that does it, but it takes
about 90% of the processor on my older T-mobile myTouch 3G. Nothing left for
video.
Original comment by ddrago...@gmail.com
on 30 Nov 2010 at 2:45
Hi,
I am using Samsung Galaxy S and I am very disappointed with SIP applications
available on Android market. I have tried all the SIP applications available on
the market including SIPDroid, CSimSimple, Nimbuz, Fring etc.
I have been a big fan of Android OS. As VOIP/SIP is very commonly used feature
in smartphones these days, I would have imagined that either Samsung or Android
app maker would have performed some tests on this.
My old Nokia gives way better results than Android driven smartphone.
Any kind of help or guidance in this regard would be greatly appreciated.
Thanks
Original comment by patelhar...@gmail.com
on 7 Dec 2010 at 12:27
CSipSimple in version 0.0.0-15 has added a microphone / loudspeaker sensitivity
setting. With low settings there is no echo on the other end of the line. I
think this would be the solution for the echo problem for sipdroid as well.
Please add this to sipdroid.
Original comment by felixloe...@gmail.com
on 7 Dec 2010 at 9:41
felixloesch8, on Sipdroid, there already are mic and speaker gain settings -
just go on Settings > Audio/Video.
The problem is that if you put them low, then you need to shout at the mic, and
compress the earpiece against your head to be able to communicate.
Original comment by BigRi...@gmail.com
on 7 Dec 2010 at 9:46
[deleted comment]
To patelhardik8090: you may try my "SMS Video" and "ddPhoneVideo" :-)
To felixloesch8: yes, the amplification levels impact the echo. Half-duplex is
another possible less processor intensive solution ( reduce the level of the
mic input when the speaker volume is high...)
But the thing is that all phones have echo canceling built in: that is how they
work well in speaker mode. My question is why is this not enabled by default or
by simply setting a flag in code?
Original comment by ddrago...@gmail.com
on 7 Dec 2010 at 12:59
Samsung Galaxy I9000. The same problem as above
Original comment by zshi...@gmail.com
on 8 Dec 2010 at 11:29
Here's a good writeup on echo and echo
cancellation:http://www.linuxjournal.com/article/8424?page=0,0
Original comment by k...@laberteaux.org
on 15 Dec 2010 at 7:33
HTC Incredible, 2.2, sipdroid up to date, same problem. Thanks for the awsome
program and keep up the good work!
Original comment by danp...@gmail.com
on 19 Dec 2010 at 6:02
Original issue reported on code.google.com by
sgunder...@bigfoot.com
on 6 Aug 2009 at 10:34