#553 Audio incorrectly routing on Samsung Moment

[Anonymous]

Originally created by: ablo...@gmail.com

What steps will reproduce the problem?
1.Install CSipSimple [r513] (http://nightlies.csipsimple.com/trunk/CSipSimple-r513-trunk.apk) on a Samsung Moment (SPH-M900) with Android 2.1 (DJ07).
2. Setup a sipgate account (sipgate.com)
3. Call 10005@sipgate.com (Echo service)
4. Audio gets routed to the speakerphone (rear loud speaker).

What is the expected output? What do you see instead?
Audio to be sent to the ear piece.

What version of the product are you using? On what operating system?
CSipSimple [r513] (http://nightlies.csipsimple.com/trunk/CSipSimple-r513-trunk.apk)
Samsung Moment (SPH-M900) with Android 2.1 (DJ07).

Please provide any additional information below.
I started out with Android 1.5, but couldn't make any progress as far as getting the audio to route to the ear piece. So I thought I'd give a shot with the latest Android 2.1 for the Samsung Moment. There was no significant change.

The only difference that I noticed was that it now consistently routes to the rear speaker, and doesn't require changing of the In-Call Volume to hear anything. So right from the beginning of the call, I can hear the audio routed through the loud speaker.

I posted before on a similar issue with a different phone here: https://code.google.com/p/csipsimple/issues/detail?id=372#c3

Unfortunately I'm not able to even reproduce the behavior that I described there.

One thing that I've noticed is that while the audio is being routed incorrectly, the responsiveness of the phone is significantly reduced. It takes several seconds to end a call and return back to the dial screen.

I can provide the logs described in the FAQ upon request.

[Anonymous]

Originally posted by: Yichi.C...@gmail.com

The same situation as abloxom described, but my phone is Huawei U8150, Android 2.2, CSipSimple 0.00-16.

I had tried many many SIP clients, only fring and Sipdroid 1.6.1beta that someone hacked it could route audio to earpiece correctly, others would sound from speaker.

In fring, the speaker will switch off and status bar shows like |||X (Speaker off), not as CSipSimple switch to vibration mode. For your reference.

I had built own asterisk server, don't want to use fring coz that depends on fring server. I appreciate if could solve this problem.

[Anonymous]

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

@Yichi : if someone hacked the audio routing on sipdroid, I think that my pool of available hacks on csipsimple may also works for you too.
So :
1 - Install a dev version (HowToInstallDevVersion wiki page)
2 - Switch to ExpertSettingMode (wiki page) global setting section
3 - Try to play with these settings :
* Use Mode API (the first to try cause for most of special audio implementation it helps) => once activated do a test call.
* Use Routing API (as your device use 2.2, I don't think it will help but how knows)
* Use tone hack

If one or a combination of that modes helps... well good news for you, you have CSipSimple running correctly on your phone ;). You can then share with me which setting helps so that I can automatically turn on one of the correct hack by default for U8150 owners; To do so, I need the exact device info (the infos announced by android to the application about the device). An easy way to collect these info is to send me logs using my embedded tool : see HowToCollectLogs (wiki page). If it doesn't work you can install other apps on the market such as "Device Info" and tell me what are the "Device" and "Product" values.

[Anonymous]

Originally posted by: Yichi.C...@gmail.com

@r3gis.3R

As ur advise, I setup "Use Mode API", it work fine. Thanks a lot.
In fact, this problem puzzle me about one month.
But new problems may be not suitable here?
1. The phone will switch to vibration mode automatically when sip connected.
2. Using iLBC codec, voice quality is too bad and CSipSimple almost crash. It is useless.
Thanks again for ur effort.

Based on the GPL CSipSimple version : 0.00-16 [r573]
Here are important informations about Device :
android.os.Build.BOARD : U8150
android.os.Build.BRAND : Huawei
android.os.Build.DEVICE : U8150
android.os.Build.ID : FRF91
android.os.Build.MODEL : Ideos
android.os.Build.PRODUCT : U8150
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : eng.huawei.20100903.194753
android.os.Build.VERSION.RELEASE : 2.2
android.os.Build.VERSION.SDK : 8
android.os.Build.VERSION.SDK_INT : 8

[Anonymous]

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

Ok.
For vibration mode it should be when you enter in call and is restored after. (if call crash cause of the use of ilbc it is not restored and may be your problem). But switching to vibrate while in cal is absolutely normal.if I do not and an incoming gsm call arrive it will explode your ear! And I think you want to keep the capacity to ear ;p.
For ilbc as your device's cpu do not support floating point you should not use ilbc. I leave the passivity for armv6 and less to activate cause some armv6 have enough cpu to get rid of their fix point limitation.but ilbc as it is a floating point implementation is suitable only on devices that support floating point (armv7).on your device ilbc is de activated by default.
You will find no open source software that support ilbc on fixed point device.there is an existing close source implementation in fix point from nokia but it is not available for developers.

[Anonymous]

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

Normally the problem is fixed with recent builds
http://nightlies.csipsimple.com/trunk/

The switching has also been improved and now it doesn't put phone in vibrate mode anymore.

Status: Obsolete