#1356 Audio routing on alcatel 890d

[Anonymous]

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

What steps will reproduce the problem?
1. Make incoming or outgoing call

What is the expected output? What do you see instead?
Rear speaker is working instead of earpiece. So I have to use headset (it works fine).

What version of the product are you using? On what operating system?
I tried market version and CSipSimple-[r1075]-trunk.apk.
Alcatel OT-890D firmware 2.2.2 kernel 2.6.32.9

Please provide any additional information below.
I tried play with options listed in "Audio routing troubleshooting".

The best result is with Use Mode API on:
1) Earpiece is working.
2) Mic is not working.
3) Something goes wrong after first call and I can't make next call before reboot

[Anonymous]

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

Based on the GPL CSipSimple version : 0.02-03 [r1075]
Here are important informations about Device :
android.os.Build.BOARD : BBDDS
android.os.Build.BRAND : TCT
android.os.Build.DEVICE : one_touch_890D_gsm
android.os.Build.ID : FRG83G
android.os.Build.MODEL : ALCATEL one touch 890D
android.os.Build.PRODUCT : one_touch_890D_ALRU
android.os.Build.TAGS : release-keys
android.os.Build.VERSION.INCREMENTAL : v43BNR0
android.os.Build.VERSION.RELEASE : 2.2.2
android.os.Build.VERSION.SDK : 8

[Anonymous]

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

Thx for the feedback.
Seems a little bit like implementation done by samsung on their device.
Did you try with mode api to change the micro source to something different than default?

Unfortunately, on some samsung that behaves this way, there is no solutions to get a proper routing. :S. In fact they do things so that it will only plug micro to gsm chipset. The only thing I found was a hack (the galaxy hack) to fake things from the point of view of the audio driver, but it does not work in all cases :/.

[Anonymous]

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

Thanks for fast reply and sorry for my bad english.

> Did you try with mode api to change the micro source to something different than default?

Well, I just tested them all (It took long time cause i have to reboot phone each time):
MIC
VOICE_CALL
VOICE_COMMUNICATION
VOICE_CALL_UP
VOICE_CALL_DOWN
CAMCORDER
VOICE_RECOGNITION.

I also tried the galaxy hack. Still have no luck.

I wonder if mic connected directly to gsm chipset  then how google voice search is working fine? Does it mean csipsimple can use mic properly in theory? If so, how can I help with debugging to make csipsimple to work properly on this rather cheap phone? Sip and linux is not a problem for me, but I'm newbie android user.

[Anonymous]

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

On google voice search you do not need to route audio through earpiece.

Unfortunately, manufacturers does not really test the use case needed for voice over IP.
Prior to android 2.3 there is nothing clear on android about this use case. And even on android 2.3 manufacturers does not always do things cleanly because they do not really care about this use case.

If you are interested in more details you can read my long comment here : https://code.google.com/p/csipsimple/issues/detail?id=119#c38 (comment 38). I tried to explain current knowledge about the problem. There is possibly still things I missed or I don't know about how manufacturers did the implementation on their phone. That's empiric results. But for now, there is not really more workaround than the one proposed in the app. And when some voip app succeed in doing a correct routing, it usually match one of my workarounds. (I contributed for example the galaxy hack to other opensource projects).

Even Google, on their project "WebRTC" has to write hardcoded workarounds for samsung device explicitely in their code. So, Google knows that manufacturers does crappy things with the audio layer.
( https://code.google.com/p/webrtc/source/browse/trunk/src/modules/audio_device/main/source/Android/org/webrtc/voiceengine/AudioDeviceAndroid.java?r=156#396 )
-- I'm currently working on integrating this back to csipsimple in order to have alternates audio device implementation than mine. But regarding their code, they are still far to support as many devices as csipsimple supports thanks to users feedback ;).

If none of the hack works on your device, I really fears that we will fall in the bad case that is already known for one samsung's device... we have to wait for an update from the manufacturer that fixes this issue. (samsung and motorola already did this kind of fixes on 3 devices that has exactly the same problem).

If you find another voip app that can get rid of this problem let me know, there is maybe a chance. So let me know :).
But on my side, without the phone in the hand to test several android methods and see logs, it will be very hard to support.
BTW, regarding logs you collected, it seems that their audio driver is still in verbose debug mode o_O... Sounds they didn't really finished it :S.
Do you know if there is an update to android 2.3 planned for your device?

[Anonymous]

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

Of course, I keep the issue open and accepted : if anybody else find a good combination of hacks, or if there is progress on alcatel mobile side.

Really sorry that I can't do more for now :(

Labels: Manufacturer-driver
Status: Accepted

[Anonymous]

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

In fact I can't catch only one thing. When I use default settings (without hacks) i can talk using rear speaker and the mic. Can we route audio input to this mic and audio output to earpiece. Is there any way to test this case remotely? Anyway, I'm ready to spend some time to make tests for you. Or the problem is we can't take input and output from different input-output "pairs"?

I didn't find any information about plans for further firmware updates. I'll ask alcatel's support about firmware upgrade plans for 890d and earpiece problems on voip-softphones (but i think i should learn more about audio api and basics to build application for android to do it correctly)

I also tried 3cxphone and got the same result.