#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: m...@ufritz.de

ok. can confirm this, after disabling STUN and enabling ICE (settings -> media) it is working. So this was the STUN Server setting.

[Anonymous]

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

I'll try to fix it in next release. I'll follow advises from pjsip (the native sip stack on which csipsimple is based) and fully restart all the sip stack on network change.
Will probably fix the issue in a first time but will consume more CPU (and so battery) when network change is detected (but I assume there is not a lot of network change so that can be considered as a minor impact).

[Anonymous]

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

> and fully restart all the sip stack on network change

maybe the fully restart is only made, if STUN is activated?

In my case. I have a lot of network changes, because if I go outside (my garden) and go inside back, I have already 2 changes, and I go outside a lot at day.

[Anonymous]

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

I don't remember to tell that with older version and with newest TCP transport doesn't work. If I unselect UDP and only TCP is selected will csipsimple crash or it is hard to get back to settings menu (because it want to jump to androids default screen).

[Anonymous]

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

To galaxy S owners :
I've released a -12-29 version.
It add an option to change a parameter called ptime. I would like to test and change it to 20.
I ask this because, -12-27 that solve the micro issue for you has both a changed ptime value (this value is linked to latency) (from 20 to 30), and also the implementation tweak that wait before asking micro frames. If you confirm that 20 works as fine as 30 I'll put 20 as the default value (latency will be better - I mean audio latency, small compared to network latency -> so you'll not ear a big difference).

@jarsiv : for tcp/udp issue can you send me your logs?
Well in all case both TCP and UDP ~should~ be always activated (unless it's a really specific configuration), if you want to use TCP you should change it into the account configuration, but still interested in crash logs :) unless it's an ANR (application not responding) and so I think that I know the reason. (The application doesn't thread everything yet and sometimes it tries to register/resolve things in the user interface thread which mean a lack of responsiveness. So if your STUN server/registrar server or another server doesn't support TCP it can wait for a network timeout in the UI thread. This is a big point I have to fix but I keep it in mind.

@mail : New version restart everything. As you said, it's not really optimized. I don't know exactly what impact it could have on the battery. I don't think that it's so huge but for now it will solve *a lot* of problems (included wifi lock that could remains - and maybe drain more battery). Let me know if you observe a big difference with this version. Anyway I'll need to optimize this later but could help me on the priority of the task.

[Anonymous]

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

I tested ptime 20 and I don't hear any differens. So I think it's ok set it default to 20.

Also mailed logs of tcp issue.

[Anonymous]

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

I found a new sound issue:
If i receive a call, the speaker-phone on the back is on (hands free speaking). If I make a call, it is off (correct).

I can not switch it off or on.
This also produce an echo.

[Anonymous]

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

Is it possible to add feature that while you are calling and phone is on your ear csipsimple will shut down the display. And after you tilt the phone to stop calling it will put on display?

Now display is on whole time so it will drain battery quite fast.

[Anonymous]

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

comment 62 seems to be in the wrong place.

But anyway, the display on the galaxy just dims, if the sensor comes close to the head.

With the android standard dialer (GSM), the display dims more, goes to black dark.

With sipdroid, the display shut down after timeoff, after the call you have to unlock the display an can hang up

How to tilt the phone to stop calling?

[Anonymous]

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

Just try to untick the option "Keep awake while in call" in UI settings. It's a work around for nexus one.
In future release for other devices than nexus one it will be un-ticked but for now since it has a deep impact on communication on nexus one it is by default enabled.

Besides :
- I think that the tilt to stop should be done by a third party app ;)
- I'll try to implement soon the real proximity sensor usage (screen goes off when proximity sensor is activated) - But it requires the usage of a private android API. So for now, *if you disable the "keep awake while in call" option* => Screen will goes off when near of your head after a while (same time than the one configured in standard case). In the future (with private api) it will goes off immediately (if it is not the nexus one on wifi !)

[Anonymous]

Originally posted by: enciso.d...@gmail.com

Hi There r3gis.3R,
first I want to say that I love your app, it integrates flawlessly with my Android. I am having a problem though, when I make a call there is no sound on my ear piece, or headphones, mic works great, the person on the other line can hear me no problem but I can not hear the callee, I have change the codecs, I have follow all and any instruction and nothing resolve the issue. i would really like some advise, my phone is HTC Desire (nortamerican model), runing android 2.1 sip provider freephoneline.ca (I have used other sip clients without problem with this sip provider). Thank you.

[Anonymous]

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

@enciso : really strange since should works fine with HTC. Probably a configuration issue. Can you provide me some logs (follow the wiki page about how to collect logs). I'll open a new bug/issue for your one when I'll get the logs.

@galaxyS owners : I modified the way audio is routed to speaker / earpiece in -12-30, can probably help to solve the issue. -You should probably reboot phone after installing the new version in order to ensure audio API is in a good state when you'll do tries with new version-

@X10 and i7500 owners : does last version helps with previous crashes? I guess that what I did to make it work on Galaxy S (and alsa driver) would help to avoid audio stack crash on X10 & i7500.

[Anonymous]

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

@enciso : was not able to reply to your mail (I get a 550 550 No such user delivery failure mail). But can you re do the test with logs activated (see https://code.google.com/p/csipsimple/wiki/HowToCollectLogs the second paragraph "How to turn on logging"). Will help me to know what is happening :).

[Anonymous]

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

@enciso : thanks we will continue on issue 209 > there is some extra question for you ;)

[Anonymous]

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

First short test on the galaxy.
The speaker on the back is now off by default. Great!
Switching between the ear and back speaker is now the same behaviour like on sipdroid. To switch on is working, to switch off again, does not work. But this is not really important.
At the first test I had no sound again, only after opening the settings screen and close it again. STUN is activated, but this issue is fixed already. I will keep an eye on it, maybe I will find a way to reproduce it.

[Anonymous]

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

Great, thanks a lot for the test.
For the switch off again issue there is something I can try to solve the issue. It sounds like the one I get on bluetooth and simply stop and restart the streaming with good params set before opening the stream made things work.( since for now it is done while streaming is done and switching from earpiece to speaker doesn't stop audio stream)
The same technique could maybe solve the speaker switching issue.

For reference, still issues on X10 (thanks Mark for the report).
I'll try to test on a colleague X10 next Monday (at work colleagues start to own android phones....samsung S (one received it today), a X10, and a htc desire :)... so will be easier for me to debug issues on these device... just have to convince to test my app on their phone for a couple of hour ;) )

[Anonymous]

Originally posted by: authapon

I have the same problem with Comment 61. When someone call to me, their sound is always on the back speaker. And when I make a call, the sound is ear speaker(that is correct). I cannot mute it also. I use samsung galaxy s in Thailand. I try both with CSipSimple_0.00-12-29.apk and CSipSimple_0.00-12-30.apk. I also reboot the phone after installed.

ps. I love your app so much, I will wait it to work correctly with my galaxy s. :)

[Anonymous]

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

@authapon : are you sure version 0.00-12-30 doesn't solve the issue? (At least for the default behavior, switching is still broken, but I'm working on it).

For the mic mute, it is quietly sure that it work properly now with 0.00-12-30 : I changed the method and now it's not managed by the android system but by the sip stack which is more reliable and doesn't depend on the device.
So I guess something went wrong when you installed the 0.00-12-30 you had the micro mute issue. Try to fully uninstall the app and reinstall the 0.00-12-30 and let me know if you are not in the case of comment 69 now.

[Anonymous]

Originally posted by: authapon

@r3gis.3R : I try to reinstall the version 0.00-12-30 again and reboot my phone. It still doesn't solve my problem. My back speaker is on when someone call to me and the mute function is not working too. I am not sure what wrong with my phone or my sip server. T_T

I try with fring and it is working correctly. I saw that fring will enter to silent mode(silent mode notification is shown in the task bar) when I accept the calling. I think that may be the secret for my phone.

[Anonymous]

Originally posted by: authapon

@r3gis.3R : Oh..I have some misunderstand, the mute function is working correctly. Now I have only the back speaker problem. :)

[Anonymous]

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

Ok. Yesterday I made a short test and the back speaker was off. But I spoke not very loud, because I didn't wake up my kids, but I was sure all is fine.

I don't know what was happens yesterday night...maybe I was sleeping already. But it is true, the backspeaker is on all time :-(
Tested today again.
The Mute Button is working.

[Anonymous]

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

@mail : maybe you where in ringing mode silent yesterday?
As authapon proposed, I'll try to set ringer mode to silent during the call (really good idea, could be consistent with observed behavior).
So can be interesting to test that.
I'll also implement the workaround for switching between speaker and earpiece.

[Anonymous]

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

Yes, you are right, just tested it.
If the ringer is silent, the sound comes over the ear speaker.
If the ringer is not silent, the sound comes over the back speaker.

[Anonymous]

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

Well, 0.00-12-31
It set ringer mode to silent while in call. Let me know if it helps to solve the speakerphone issue.
I've also changed the way speakerphone mode is switched (same workaround than the one for Bluetooth).

[Anonymous]

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

No, it does not help. It seems it has to be silent before it is ringing.