csipsimple / Tickets / #954 Echo on HTC Sense and Samsung Galaxy Tab

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

In fact in android - previously to android 2.3 - the audio API is absolutely not designed to do voice over IP. Even after android 2.3 it's not as good as it could be on all other platforms you may know.

The android audio API is not really well defined to do audio streaming and as consequence each manufacturer has its own interpretation of the API.
Some do things cleanly. HTC does. Other, like Samsung do really weird things and each of their device is really hard to support.
In your case, I think that the echo is produced by the Galaxy Tab. It's known to have a very bad audio layer. Latency is very high and a correct audio routing is obtained by a lot of hacks.
If you have a look to the code and to the method I use to get it working, you'll be afraid... And we are lucky, the method I found for the galaxy S (and that also work for the Galaxy Tab) could not have been there at all.

However, you can try to play with audio hacking options.
You should read :
https://code.google.com/p/csipsimple/wiki/FAQ?wl=en#Audio_routing_troubleshooting
And this issue comment too :
https://code.google.com/p/csipsimple/issues/detail?id=119#c38

You could also try to play with echo options (there is a software echo canceller, the one of pjsip), you can try speex echo mode (AEC) or simple echo canceller implementation and also try to increase the echo tail length.

However in your case the software echo canceller is not really useful cause the problem is about an high latency + materials and audio layer that loop the speaker to the micro.

When you'll play with audio workarounds you'll see that both device does not get optimal settings with the same settings. By default CSipSimple tries to detect device and based on users feedback set up the "best" settings.
If you find better settings do not hesitate to share, I'll integrate it as default settings for these devices.

Last point about echo, the future release of android are really promising regarding this point. Since google now need something reliable they now force manufacturer to implement correctly things in order to support their own stock SIP application and google Talk VoIP.
As consequence SIP application will benefit it. I had the luck to test on an Acer Iconia tab running android 3.0 and results regarding echo cancellation and latency are impressive.

Mergedinto: 119
Status: Duplicate

Tickets: #119

*Originally posted by:* [r3gis...@gmail.com](http://code.google.com/u/103053537395257486222/)

The android audio API is not really well defined to do audio streaming and as consequence each manufacturer has its own interpretation of the API. 
Some do things cleanly. HTC does. Other, like Samsung do really weird things and each of their device is really hard to support.
In your case, I think that the echo is produced by the Galaxy Tab. It's known to have a very bad audio layer. Latency is very high and a correct audio routing is obtained by a lot of hacks. 
If you have a look to the code and to the method I use to get it working, you'll be afraid... And we are lucky, the method I found for the galaxy S \(and that also work for the Galaxy Tab\) could not have been there at all.

However, you can try to play with audio hacking options. 
You should read :
[https://code.google.com/p/csipsimple/wiki/FAQ?wl=en\#Audio\_routing\_troubleshooting](https://code.google.com/p/csipsimple/wiki/FAQ?wl=en#Audio_routing_troubleshooting)
And this issue comment too :
[https://code.google.com/p/csipsimple/issues/detail?id=119#c38](#119)

You could also try to play with echo options \(there is a software echo canceller, the one of pjsip\), you can try speex echo mode \(AEC\) or simple echo canceller implementation and also try to increase the echo tail length.

However in your case the software echo canceller is not really useful cause the problem is about an high latency + materials and audio layer that loop the speaker to the micro.

When you'll play with audio workarounds you'll see that both device does not get optimal settings with the same settings. By default CSipSimple tries to detect device and based on users feedback set up the "best" settings. 
If you find better settings do not hesitate to share, I'll integrate it as default settings for these devices.

**Mergedinto:** 119
**Status:** Duplicate

Add attachments
Cancel

You seem to have CSS turned off. Please don't fill out this field.

Echo on HTC Sense and Samsung Galaxy Tab

Searches

Help

#954 Echo on HTC Sense and Samsung Galaxy Tab

Related

Discussion

Related

Related