#89 [Manufacturer driver] Echo on Xperia X10

[Anonymous]

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

This is an intermittent problem that occurs sometimes when dialing an extension that is not registered. 

csipsimple hangs on the 'Confirmed' dialing screen.  This seems to hang audio in the phone as well as hanging the dialer.  I have to restart the phone to restore functionality.

What version of the product are you using? On what operating system?
Sony Ericsson X10 (and X10 mini), Android 1.6, Csipsimple 12

Please provide any additional information below.
I have previously provided logs via email, but wanted to file an issue report to track it.

[Anonymous]

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

For galaxy S users particularly, worth to try :
https://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-24.apk

This one has a big change in the way audio record is created.

[Anonymous]

Originally posted by: m...@ufritz.de

so, I'm back from holiday. I did try it out, and there is something understandable in on the other line.
Now i'm running the 12-26 build and when I do speak very slowly, I can understand it on the other line, if I do speak normal, there is all times a strange noise if the speaking volume goes up and down, like between different words.
I will send a log file by mail to you, r3gis.
Maybe a recording of the call will help, or not?

[Anonymous]

Originally posted by: m...@ufritz.de

forgot to say, I have the galaxy I9000

[Anonymous]

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

Well thanks a lot for the test (and the logs), that confirm exactly what we get with another device with alsa (alsa is the audio driver used by the samsung galaxy S).
So there is still something I have to work on, but since progress is the same on all device that use ALSA, that's a really good news for me :)

[Anonymous]

Originally posted by: m...@ufritz.de

Then more interesting for me is:
what sound system using the other devices?

For alsa:
what higher-level sound toolkits, such as SDL, OpenAL is used in the android phone?

when I lsmod the loaded modules in my galaxy, I see no alsa module so I can not find any particular information from the device...

[Anonymous]

Originally posted by: m...@ufritz.de

When using other sound software with my galaxy i9000, there are no special sound issues. I tried now the sipdroic client with no special problems. I do not know anything about the android and java decencies, but maybe looking at other open source solutions will help to fix the problem?

[Anonymous]

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

Yes I'm currently diving into what is done by sipdroid. Their implementation is much more mature than mine and they probably already encounter this kind of problem. Although what I do is done in native (C) side, concepts can be reused.
There is something I'm currently trying to add regarding record process.
I'll keep you in touch when it will be done.

As for your first question (comment 32), there is not really high level sound system used on other devices. Most of the time they use their own private driver directly plugged to the android sound api. However there is a recent effort to port a real sound api to android.
There is also some effort on OpenCore framework (http://www.opencore.net/files/opencore_framework_capabilities.pdf) that comes on the top of alsa I think.

But all of these nice libs can't be directly used by application developers (since it can deeply depends on the device). - It is technically possible, (my first version of csipsimple was based on privates api) but that is dead end since maintaining one version per device (in best case by manufacturer) is really hard to do.

If you are interested in what are the "known" audio implementation you can quickly have an overview in each package on the android git : http://android.git.kernel.org/?p=platform/hardware/alsa_sound.git;a=summary (this one is the glue for alsa).
If you click "projects" you'll see other specific implementation for htc for example -- or at least .ko they provide to the community.

Another interesting link on this subject : http://www.kandroid.org/android_pdk/audio_sub_system.html . It's a little bit outdated and intended for porting android on a device, but really interesting to read.

[Anonymous]

Originally posted by: m...@ufritz.de

samsung will soon provide a update to android 2.2. maybe things will get better or more worse, who knows.
Yes, the links are all interesting, but not very helpful for the sound issues, to find a solution..

> Their implementation is much more mature than mine
but the sipdroid client has a horrible echo for the other call party, this seems much more better on csipsimple.

If you changed something again, I will test it.

[Anonymous]

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

Yeah, I noticed echo problem with sipdroid also. Even you select gain to min. there is still echo. Also there are greater delay that csipsimple. Still I think that csipsimple is better. I just wish that there will be solution for audio problems. Outgoing voice is still mess.

[Anonymous]

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

Last version (-12-27) includes an implementation based on sipdroid methods to read micro stream.
Not sure it will improves things but worth to try.

Else I have another thing that I can try to see if things are better.

[Anonymous]

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

Issue 178 has been merged into this issue.

[Anonymous]

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

I tested this version https://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-27-archos.apk

and with iLBC, quality 4, 16kHz, mic and speaker gain 0.1 it seems to work fine with 3G. When trying to 8kHz it was little bit worse quality than with 16 kHz. So very good so far!

[Anonymous]

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

Great, we should say thanks to sipdroid guys ! Their method to get record frames only when needed was the solution at least for this choppy sound.

Just for information, archos edition is intended for Archos 5 internet tablets - that has no GSM application, so my android integration is done one level upper using privates API of android. So should probably not be used on other devices. However it is the same code, the only thing that change is the manifest file. I've just pushed 0.00-12-28 that fixes a regression introduced in -12-27.

I've still to find out why like on the X10 there is this awful echo. I think that the reason is the same (line and mic are mixed up so I record both what come from the mic and what I diffuse on the earpiece/speaker.

In worse case (will be the case for X10 I think since there is no hope in the 1.6 api), I'll try to tune echo cancellation feature to remove the echo produced by this hardware implementation.

Just another question, on galaxy S, do speaker/earpiece switch work fine?

[Anonymous]

Originally posted by: m...@ufritz.de

I use the gain of mic and speaker gain 0.2, the codec choice seems to does not make a big different here with my SIP provider.
Using 16kHz is also quite better, than the 8kHz, but the phone reacts a little bit slower. Using 32kHz, the phone nearly hangs.
The Quality setting is 3, the voice detection switched off and echo canc is on.
The echo on the other line end is now something between nothing and very quiet, testing over 3G call. The delay is about quarter a second.
So in overall, this are the best results, compared to the other available SIP clients for android.

Great work!!

[Anonymous]

Originally posted by: m...@ufritz.de

Forgot, the volume up/down on the side of the phone is not working on the galaxy i9000

[Anonymous]

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

Speaker mode works fine but I noticed that mute (if it is mic mute) doesn't work.

[Anonymous]

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

Ok; for mute issue you can track issue 161.

I think that i'll not use the android mute feature (as it's done now) but the one included in the sip stack... much more reliable ;)

[Anonymous]

Originally posted by: m...@ufritz.de

> Just another question, on galaxy S, do speaker/earpiece switch work fine?

no, I can switch to the speaker, but not able to switch back to earspeaker. Same issue with sipdroid...

[Anonymous]

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

>no, I can switch to the speaker, but not able to switch back to earspeaker. Same issue with sipdroid...

Yeah, more test and I also confirm that issue.

[Anonymous]

Originally posted by: m...@ufritz.de

I have found a new sound relevated issue:

If I answer a call (incoming). my earphone is dead, so I can't hear anything.

There are two reasons:
1. I have to pause the call, then resume it, to hear anything.
2. I need to set the speaker gain to 1.0

If I set the speaker gain to 0.2, I do not hear anything on incoming calls, but on outgoing it is fine. Gain 0.2 on other hand is the best choice.
Maybe, if the volume up/down button is working, it will be fine. I guess at the moment I do hear with gain 1.0 the highest possible volume.

I'm talking here only about the speaker (ear piece), not the microphone.

I will send a log to r3gis.3R, here I will receive a call, pause it and resume it, until I do hear the other caller.

[Anonymous]

Originally posted by: m...@ufritz.de

update to comment 48:
Ok. I see, it happens not all times and also the pause and resume do not help on all calls. I will test more for this.

Someone have similar issues?

[Anonymous]

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

Ok for comment 45/46 I've got a little idea about what I can do to solve it.

For 48, do you reproduce when it doesn't ring? (set ringing volume to vibrate or none ).
I ask this because I think that the fact there is a really short time when both ringing and voice are both active. It can maybe affect voice call.
If when you deactivate ringing you get something equivalent to outgoing call, I can quickly try something to solve it.

[Anonymous]

Originally posted by: m...@ufritz.de

the ringing was deacitvated. Now I find out, after opening the settings dialog but change noting, it was working. Now I will check out, if it happens after I switched from WLAN to UMTS and back. Outgoing is working, incoming has no sound. With ringing and vibrate the same.

[Anonymous]

Originally posted by: m...@ufritz.de

Ok. I found the behaviour:
After returning from UMTS to wlan, csipsimple re register the account (can see it on the symbol). But incoming calls have no sound (earspeaker).
If I do deactivate and then reactivate the account (account settings). There is still no sound.
If I open the settings dialog, go to settings -> media and then go back, not change anything, there is a re register again, but then I will have sound.

Maybe need to uninstall complete and install again?

[Anonymous]

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

Ok !
That's issue 126 !
STUN is not re-resolved and you probably re-register with the old ip address. (Going to settings and then back, restart all the stack while ip changes detection only re-register - and that's not enough if public IP has changed).