Wrong Sound Channels on Samsung Spica i5700

[GoogleCodeExporter]

Newest Version.

Sipdroid uses "Media" Sound Channel (so loadspeaker) instead of earphone for 
normal phone call.

Samsung Spica i5700 with Android 2.1.

Original issue reported on code.google.com by muellerr...@gmail.com on 11 Mar 2010 at 7:59

[GoogleCodeExporter]

Does anybody know how to install the patch from 
http://forum.samdroid.net/threads/983-Sipdroid-(VoIP)-i5700-problems ? They 
seem to know what they're talking about, but I haven't got a clue. All I want 
is to use my VoIP account!

Original comment by rogerkea...@gmail.com on 16 Aug 2010 at 4:45

[GoogleCodeExporter]

@roger: you can't simply install those patches. Look here: 
http://forum.samdroid.net/f28/spica-v-lk2-02-root-recovery-apps2sd-busybox-wifi-
tether-etc-04-15-2010-en-624/ and here: 
http://forum.samdroid.net/f28/samdroidmod-kitchen-v1-x-x-all-one-en-939/. 
Samdroid Mod has those patches included.

Original comment by jahs...@gmail.com on 17 Aug 2010 at 7:43

[GoogleCodeExporter]

Cross-post from Issue 173:

I have the same issue with a Samsung Moment running Android 2.1 - when I do a 
cat /proc/kmsg I notice that Sipdroid is routing the audio to 0x02 (Speaker 
output) and 0x21/0x22 (VOICEMEMO_MAIN and VOICEMEMO_SUB) which also happens to 
route to the back speaker.

Sircid - I know you fixed the Spica issues but was wondering if you could help 
with the Moment's kernel - it's not too far off.

Original comment by dethl.se...@gmail.com on 9 Sep 2010 at 5:49

[GoogleCodeExporter]

By the way, is this something that can be done in the SIPdroid code? Because if 
so, it might be better than patching all of our kernels.. 

Original comment by auz...@gmail.com on 9 Sep 2010 at 5:58

[GoogleCodeExporter]

same Problem with T Mobile Pulse / Huawei U8220 :(
(Android 2.1. Official UK Version)

Original comment by holger2...@gmail.com on 11 Sep 2010 at 8:45

[GoogleCodeExporter]

i did try about 5 VOIP Apps - and did find now  one that works, "Fring" - not 
really a solution because Voip integration with Sipdroid of course is much 
nicer, but Fring seems to know a way to use the Frons Speaker... (tried with  T 
Mobile Pulse / Huawei U8220 )

Original comment by holger2...@gmail.com on 14 Sep 2010 at 11:03

[GoogleCodeExporter]

Same problem with audio routing to back speaker (and echo for other user) on 
Orange's new San Fransciso, sipdroid 1.5.7beta, android 2.1

Original comment by philtord...@gmail.com on 27 Sep 2010 at 10:37

[GoogleCodeExporter]

Perhaps the title for this problem should be changed? Because the problem seems 
to be affecting many phones.

Original comment by auz...@gmail.com on 27 Sep 2010 at 11:16

[GoogleCodeExporter]

I had this problem on my SPH-D700 Epic 4G yesterday, but today it's working 
correctly.  I have no idea why, neither my phone nor my SIPdroid were updated 
in that time.

Original comment by kean...@gmail.com on 29 Sep 2010 at 6:55

[GoogleCodeExporter]

See issue 574 for a test APK that might also solve this issue for Samsung 
phones other than the i9000.

Original comment by pmerl...@googlemail.com on 1 Oct 2010 at 1:32

[GoogleCodeExporter]

I've tried the APK from pmerl..., but for my T-Mobile Pulse nothing has changed 
unfortunatelly.

Original comment by Martin.C...@googlemail.com on 1 Oct 2010 at 3:29

[GoogleCodeExporter]

pmerl's APK had no impact on audio routing on my Epic, and has FC issues.

Original comment by kean...@gmail.com on 1 Oct 2010 at 4:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Just how exactly is this an issue of medium priority? This is happening on ALL 
samsung phones as far as I can tell. That includes my i9000 as well and it is 
bugging me and the people that are hearing themselves echoing on the other end 
of the line alike. Please fix this!! Thanks!

Original comment by schip...@gmail.com on 11 Oct 2010 at 10:09

[GoogleCodeExporter]

Can confirm issue also happens on Samsung Intercept (SPH-M910).
Also, audio is extremely glitchy. (not just codec'd audio, the ringtone when 
sipdroid rings also glitches out and gets crazy.)

Original comment by necro...@gmail.com on 11 Oct 2010 at 4:04

[GoogleCodeExporter]

How exactly is this an issue for Sipdroid at all?  Sipdroid works fine on HTC 
and Motorola phones.  All VoIP apps have this problem on Samsung phones.  It 
seems to me like Samsung is at fault.  Sircid studied the problem and 
determined that it can be fixed in the phone's kernel.

Original comment by bala...@gmail.com on 11 Oct 2010 at 6:17

[GoogleCodeExporter]

balazer, flitchy audio problems do not occur with fring. (although I still 
cannot switch output speaker from loud speaker to front speaker)

Problem does occur with sipagent as well.

Original comment by necro...@gmail.com on 11 Oct 2010 at 11:04

[GoogleCodeExporter]

Oh wow... just used version 1.6.1 for the first time on my Samsung Galaxy S...

Sound now comes out the correct speaker (ie. the front) and the person on the 
other end was happy to report that the hideous echo was gone too!

The only issue was the 2-3 second lag... but I think that has more to do with 
the fact they were calling New Zealand from the USA ;)

Original comment by jared.ya...@gmail.com on 20 Oct 2010 at 8:25

[GoogleCodeExporter]

On Orange San Francisco there problem seems to be related to not working 
am.setSpeakerphoneOn call. Old am.setMode call sets correct speaker. 
I am attaching my build with forced  am.setMode call (and due to build problems 
commented some Bluetooth calls).

Original comment by devyx...@gmail.com on 22 Oct 2010 at 10:20

Attachments:

• Sipdroid-debug.apk
• patch-san_francisco.patch

[GoogleCodeExporter]

Unlike Jared's experience, 1.6.1 does not fix the audio problem for me on my 
Galaxy S device (Epic 4G) on 2.1.1, stock DI18.

Alternatively, anyone know of a non-stock kernel for any Galaxy S device that 
has fixed the issue?  I don't see a lot of mention of this issue on the XDA 
threads.

Original comment by rich...@sigil.org on 22 Oct 2010 at 3:34

[GoogleCodeExporter]

I should probably have mentioned that I am running the "official" 2.2 froyo 
release that was briefly available from kies... Albeit by hacking the registry 
to trick kies into thinking my phone was scandinavian ;)

Original comment by jared.ya...@gmail.com on 22 Oct 2010 at 8:11

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have Bell i9000M with stock Android. I had the same problem, voice going in 
rear speaker, no possibility to hear it in earpiece. After many days I made a 
phone shutdown. After restart, problem solved (at least for me).

Original comment by catalin....@gmail.com on 5 Nov 2010 at 5:22

[GoogleCodeExporter]

I can confirm that going back to sipdroid v. 1.3.7 fixes the problem on my 
Orange San Fran/ZTE Blade.
So the issue should obviously be fixable via sipdroid.

Unfortunately, applying the .patch from comment 69 on the latest sipdroid did 
not fix it for me.

Original comment by philip.g...@gmail.com on 9 Nov 2010 at 9:57

[GoogleCodeExporter]

I think devyxkun is definitely onto something. I have a Samsung Moment that is 
plauged with this odd behavior. I have had Linphone function properly, but 
after a reboot the problem returns. Sipdroid on the other hand has consistently 
routed the audio out the rear loudspeaker. Using devykun's Sipdroid-debug 
version (1.6.1) the audio is properly routed to the ear piece.

The problem with this modified version is that the Microphone is for some 
reason muted. This behavior was experienced in Linphone as well. The solution 
is to Mute, and then Un-Mute, and the microphone works again. The problem with 
this is that upon Un-Muting the microphone, the audio suddenly gets routed to 
the speakerphone again.

Original comment by ablo...@gmail.com on 27 Nov 2010 at 10:26

[GoogleCodeExporter]

Installed sipdroid (from Market) on the ePad (made by zenithink model zt180 
running android 2.1). Everything work well except no audio at all. I think some 
devices just can't do duplex audio.

Original comment by sip....@gmail.com on 2 Dec 2010 at 10:15

[GoogleCodeExporter]

try to enable the loudspeaker! Your mic will mute and it will not go back on.
How can this happen? Any solution?
Me: ZTE Blade. Same thing with 1.3.7 and the Sipgate-debug.apk from #69 (thanks 
for that)!

Original comment by dr.amer...@googlemail.com on 15 Dec 2010 at 10:06

[GoogleCodeExporter]

Having the same problem on a Pulse Mini (Huawei), running T-Mobile's official 
2.1 firmware.

Original comment by winefant...@googlemail.com on 20 Dec 2010 at 10:45

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Using devykun's Sipdroid-debug version (1.6.1) the audio is properly routed to 
the ear piece.
+1
just bluetooth headset is something that doesn't work. but it doesn't work also 
with 2.0
huawei 8230

Original comment by golu...@gmail.com on 22 Dec 2010 at 6:17

[GoogleCodeExporter]

I downloaded devykun's version for my Samsung Spica i5700 and it did not work.

Original comment by mac10688 on 22 Dec 2010 at 7:59

[GoogleCodeExporter]

on Pulse here 137 is working, newer versions only backspeaker :)

Original comment by holger2...@gmail.com on 22 Dec 2010 at 5:22

[GoogleCodeExporter]

Please, provide a workaround like csipsimple does. It's just a checkbox there 
and the sound is routing properly.

I must say the support for Sipdroid is pretty bad.
Had an answer after 5minutes from the CsipSimple Dev. Awesome.

You guys could consider http://code.google.com/p/csipsimple/
Please get the latest trunk for ZTE Blade or Sound-routing problems: 
http://nightlies.csipsimple.com/trunk/

Original comment by dr.amer...@googlemail.com on 29 Dec 2010 at 9:48

[GoogleCodeExporter]

I am getting a problem like chrisssshen:
There is no voice during a call until,
>"if I have answered an incoming call, then press hold, wait a few seconds, and 
then >press hold again, most of the times the audio gets correctly rerouted to 
the >earspeaker."

Do anyone have a solution for this? Please share with me?

Original comment by lhhan...@gmail.com on 6 Jan 2011 at 9:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

#56, What model do you have? I have Samsung Intercept and the voice comes 
through the back speaker no matter what I try.

Original comment by harid...@gmail.com on 24 Jan 2011 at 11:02

[GoogleCodeExporter]

How to apply a patch on post 69?

Original comment by jama...@gmail.com on 27 Jan 2011 at 9:33

[GoogleCodeExporter]

Issue 848 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 19 Feb 2011 at 9:18

[GoogleCodeExporter]

Issue 856 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 1 Mar 2011 at 9:30

[GoogleCodeExporter]

This is Spica kernel/driver bug !!!
Any application like Skype, Nimbuzz, ... output sound on loudspeaker, always!
Helps custom flash rom. http://forum.samdroid.net/ - Cyanogenmod.
Original flash and Cyanogenmod have their pluses and minuses, but in 
Cyanogenmod sound goes into ear speaker.

Original comment by vale...@gmail.com on 5 Mar 2011 at 9:43

[GoogleCodeExporter]

Issue 870 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 14 Mar 2011 at 7:50

[GoogleCodeExporter]

@91  - why version 1.3.7 works with the front speaker?

(Pulse here with CM6 - may Topic can be changed? after merge the threads this 
is not the right topic, many fons like pulse, san Fransico have the same 
Problems)

Original comment by holger2...@gmail.com on 27 Mar 2011 at 9:01

[GoogleCodeExporter]

Based on comment 55 by mal...@gmail.com, Apr 11, 2011 in the duplicate issue 
341 and referenced text, I have tried to patch the current SVN code (610) and 
have the front speaker working correctly on ZTE Blade. 

The question of course is, if it does not break the behavior on some other 
phone, but it should not. 

The patch seems to be really simple, modifying 4 lines of code total in 
RtpStreamReceiver.java.

Original comment by morav...@gmail.com on 9 May 2011 at 6:46

Attachments:

• patch-SipDroid-zte-fix.diff

[GoogleCodeExporter]

Basically you should not use setMode() on Android 2.0 and later (see issue 270 
). The Blade is just broken in this regard unfortunately since it implements 
pre 2.0 API behaviour in a 2.0+ API. See 
http://code.google.com/p/cyanogenmod/issues/detail?id=2858#c51 for details. Of 
course, even if Cyanogen fixes the problem, Blade users with stock firmwares 
still have a problem...

Original comment by haferfl...@gmail.com on 18 May 2011 at 7:30

[GoogleCodeExporter]

OK, so what can we do with this issue? It seems that not only Blade, but a 
bunch of other phones suffer from this (with all duplicates for this issue). 

Is there a API level from which the problem will clearly not appear/or is 
AudioManager.setMode() forbidden to use from some API level? If so, at least 
another if can be used prior using the setMode().

Otherwise I see the only solution which adheres to issue 270 by detecting the 
buggy phones and their SW versions...

Original comment by morav...@gmail.com on 20 May 2011 at 7:28

[GoogleCodeExporter]

Since the broken firmware behaviour cannot be detected in the app, I guess the 
only way to fix this properly in SipDroid is adding a configuration option that 
allows the user to enable/disable the setMode() hack on Android 2.0 and above.

Original comment by haferfl...@gmail.com on 21 May 2011 at 7:46

[GoogleCodeExporter]

I have the same problem. I own a Droid Charge. I have since switched to 
Csipsimple which has an option for Galaxy S users. PLEASE fix this and add an 
option in the advanced menu.

Original comment by bunkl...@gmail.com on 18 Aug 2011 at 11:54

[GoogleCodeExporter]

well the patch file worked-ish.. it forced audio to NOT come out speaker but it 
was bleed over audio obviously. i went back to an old version that works but is 
missing alot of the features i would like 

Original comment by aperseg...@gmail.com on 19 Aug 2011 at 7:45

[GoogleCodeExporter]

RtpStreamReceiver.java
add the line am.SetMode(AudioManager.MODE_IN_CALL); before 
am.SetSpeakerphoneOn(mode == AudioManager.MODE_NORMAL) in the setMode(int mode) 
function. 

It works perfectly with my Hauwei U8100 running android 2.2. 

Original comment by steve...@gmail.com on 24 Aug 2011 at 8:16