[Manufacturer driver] Echo on Xperia X10

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by mcampbel...@gmail.com on 14 Jul 2010 at 1:26

[GoogleCodeExporter]

Changed tag of the issue.
Still waiting for Sony upgrade for X10... and really hoping they'll fix their 
audio driver... With the time they make us wait would be a shame if they don't 
fix their driver !

Original comment by r3gis...@gmail.com on 23 Oct 2010 at 9:13

• Changed title: [Manufacturer driver] Echo and crashes on Xperia X10

[GoogleCodeExporter]

Issue 361 has been merged into this issue.

Original comment by r3gis...@gmail.com on 8 Nov 2010 at 9:48

[GoogleCodeExporter]

Sorry for my late post. I upgraded my X10 Mini Pro to 2.1 a week ago. 
CSipSimple runs flawlessly, no freezes etc. But we are not there yet.

During a call, the other person can't hear me and the connection is broken, I 
know this because the person I called is calling me back. CSipSimple still 
shows the call though, as if the call is still running. 

I tested this on a WiFi connection with very good reception on a 20Mbit/s 
internet connection. Also tested on 3G, the audio was poor, WiFi was very good. 

So I can make calls and receive calls, but I don't understand why the 
connection gets interupted. This doesn't happen when I use Fring. Also, 
CSipSimple should show the call had ended.

Original comment by rudhra%y...@gtempaccount.com on 15 Nov 2010 at 2:34

[GoogleCodeExporter]

Ok good news if sony has fixed their audio driver.

As for connection that's a strange behavior. What you describe could happen if 
the wifi connection is lost for example or if your IP is changed by the network.

For audio quality, on 3G, you should try with a low bandwidth codec. For 
example try to enable only GSM codec or only iLBC (PCMU has no compression).  
The other side (or your sip server must also support the codec, else call will 
directly finish).

Maybe could be a great things if you can get logs if you can reproduce the 
issue.
If you can try the latest version available on the download section, there is a 
facility to collect logs in menu > Help (press record logs, reproduce the issue 
and once reproduced, go back in settings and stop & send logs).

Original comment by r3gis...@gmail.com on 15 Nov 2010 at 9:56

[GoogleCodeExporter]

Not working in X10 with Android 2.1

Original comment by anjo...@gmail.com on 16 Nov 2010 at 3:48

[GoogleCodeExporter]

Well, anyway I've planned to test on a colleague X10 today. Maybe we'll see 
some improvements on x10 once I'll be able to test and see the exact symptoms.

(Cause just "Not working" doesn't help me a lot to understand what is 
happening... ;) )

Original comment by r3gis...@gmail.com on 16 Nov 2010 at 7:20

[GoogleCodeExporter]

I'll do some testing tonight. I had the same (audio-driver) issues with 
SipDroid but Sipdroid works perfectly on 2.1 X10 mini pro now. I prefer 
CSipSimple since it's much more integrated for instance when you start a call 
etc. So I'll try to produce logs and play with audio codecs :)

Original comment by rudhra%y...@gtempaccount.com on 16 Nov 2010 at 2:56

[GoogleCodeExporter]

Hi, me again. GOOD NEWS:

The first time I tried CsipSimple on 2.1 I accidentally modified the order of 
the audio codecs (the behaviour of this menu could be improved, see below). I 
succesfully made several calls and received calls via both WIFI (11g) and UMTS 
and sometimes HSDPA. 

There are 3 other issues (on my X10 Mini Pro) wich I suppose can be fixed 
easily, perhaps I should create new issues?

(1)
The screen orientation of the settings/accounts menu don't change! Even when 
typing on my keyboard, the screen orientation stays vertical.

(2)
The Codecs menu works different from any other Android menu: when you scroll 
(touching the screen) you are actually moving one codec up or down, modifying 
the order of the codecs unintendedly! Could you change this or at least add a 
RESET button with a warning not to mess with the order if there is no need for 
it?

(3)
Only once CsipSimple crashed. While I was doing nothing, Sip accounts were 
registered and my phone was idle. I think the cause could be in the logs, but I 
have no idea where the logfiles are, hints? So I can upload them for you.

At this point I can already recommend all X10 Mini Pro owners on Android 2.1 to 
use CsipSimple!

Original comment by rudhra%y...@gtempaccount.com on 18 Nov 2010 at 1:02

[GoogleCodeExporter]

@rudhra :
Great :)

Well for point 1, portrait mode is locked cause it introduce bugs. I've to 
focus on this particular issue but that's not critical for me. I've just 
received a X10 mini and if something is not useable on QVGA I'll fix it 
directly in the layout.

For point 2 : it works just like the stock music application on android but 
you've not this one on the x10 mini so you are probably not used to this kind 
of interface :
Actually to scroll down, drag the left part of the screen. To reorder codec tap 
and drag the right part of the screen (where there is the little icon that 
indicate that lines can be reordered).
For the reset feature good idea, I'll keep that in mind when I'll refactor this 
view (there is another issue about codec priorities ... so I've to add features 
on this view I'll take the reset order in the same time).

For point 3 : 
If you are using the development version (available on this website) there is 
something in Help that allow to start log recording and stop log recording (and 
then send it directly to me - it avoid to publish on the web logs that's a bad 
idea for your privacy ;) ).

But I think that I know what you get, I had this one on the X10 mini I've just 
received, actually it's an ANR not a Force Close (ANR = application non 
responding). I've to check why we get that on the mini. But as I've the device 
now should be easy... :) 

I've also noticed some layout issues on the mini (that probably all devices 
with QVGA experiment). I'll fix all of that ones ! (You'll have to thanks 
donators to the projects that allowed me to buy the x10 mini ;) ).

Just a remark, I'm pretty impressed by the X10 mini. Sony really succeeded in 
the android integration on this QVGA device and the speed of the device is 
impressive. It sounds even better than the big X10. As they have fixed their 
audio driver in 2.1 it is really useable now. (I did benchmark on the GPU ... 
x10 mini : 45fps - nexus one 25fps.... well nexus one screen is twice bigger so 
it's normal but however, it means that the GPU of this device is really good).

Original comment by r3gis...@gmail.com on 18 Nov 2010 at 1:46

[GoogleCodeExporter]

(Rudhra)
Wow you got a X10 Mini :D why not the Pro? The keyboard is great. 

I have another issue: caller ID is not working: when I call someone, he/she 
cannot see my number although I set it up in the menu. A friend who also uses a 
X10 Mini pro has the same, but with a different Voip provider.

Original comment by zil...@gmail.com on 18 Nov 2010 at 7:16

[GoogleCodeExporter]

Since installing Android 2.1 CSipSimple is quite usable on the X10 mini.
Maybe it is time to close this issue?

Original comment by bokhorstm on 8 Dec 2010 at 9:21

[GoogleCodeExporter]

I've observed echo on X10 of a colleague. My X10 mini works fine (still some 
little things to fix with layout on QVGA screen but that's another issue).

On X10, I think that there is some default value to change on mic & speaker 
amplification to get something usable. We get something without echo but was 
hard to find good values and we didn't spent too much time to find the optimal 
value (if too loud other not ear enough or the other part doesn't ear you). But 
there is probably something optimal that could be found.

But no more crash. So I update the issue to only mention Echo.

Original comment by r3gis...@gmail.com on 8 Dec 2010 at 11:01

• Changed title: [Manufacturer driver] Echo on Xperia X10

[GoogleCodeExporter]

Perhaps closing is better, I've mentioned a few issues in post 109 but I can 
create new ones since this is not  suppose to be a topic for all X10 issues. 
And I suppose audioquality/echo would improve after 729 codec is implemented.

Original comment by zil...@gmail.com on 12 Dec 2010 at 9:13

[GoogleCodeExporter]

g729 is already available ;) go in Settings > Media > Codecs (long press on a 
row to activate)

Yes for this issue, I'll close it that's true that now there is a lot of 
comments. 

However, if X10 owner want to propose some default values (for micro 
amplification and speaker amplification), to avoid echo, they can do it here. I 
know that there is some optimal values (just like for galaxy S) but don't know 
which to apply by default ;).

Original comment by r3gis...@gmail.com on 12 Dec 2010 at 9:27

• Changed state: Fixed

[GoogleCodeExporter]

Do you have a old version of the csipsimple, before we tweaked it for the 
galaxy phone?
I would like to test it with the froyo updated phone, to see if we still need 
all the tweaks.

Original comment by m...@ufritz.de on 13 Dec 2010 at 10:01