Speakerphone always runs Galaxy S/Vibrant

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Calls

What is the expected output? What do you see instead?

Speakerphone always run during calls. 

What version of the product are you using? On what operating system?
Latest from market Samsung Vibrant android 2.1-update1

Please provide any additional information below.

Original issue reported on code.google.com by troy.gla...@gmail.com on 17 Aug 2010 at 4:22

[GoogleCodeExporter]

I think that I already corrected it in the trunk (was reported previously). You 
can download the latest build on the download section. 
Uninstall the version from the market before installing this one. (I should 
really quickly push on the market the latest one... but there so much thing to 
do :) ). If you need help to install the dev version, just ask me.

Just an additional question. Samsung Vibrant is another name for Galaxy S and 
i9000, isn't it? Just for my information (since other users with galaxy S/i9000 
are experimenting issue with micro), can you say me what is the firmware 
version (In android Settings > About phone > Firmware (should be something like 
XXJM2 or XXJF3).

Original comment by r3gis...@gmail.com on 17 Aug 2010 at 5:23

[GoogleCodeExporter]

hi, i´ve teste it and i still get the speakerphone active, and also the 
register on the sip provider gives error a lot of times.

with the market version the regiter is 100% ok.

I have sgs with xxjm6

Original comment by nemo...@gmail.com on 31 Aug 2010 at 10:09

[GoogleCodeExporter]

I can confirm that this is still a problem on my Galaxy S Vibrant with 
CSipSimple_0.00-12-29.apk and my settings > firmware says 2.1-update 1 (Build 
number says ECLAIR.UGJG9). The speaker phone button works by making the output 
audio slightly louder but the back speaker is on at all times. r3gis.3R let me 
know if you want me to help you debug any Galaxy S problems (I have got several 
:-( ). I know my way around a debugger if needed.

Original comment by dr.seamu...@gmail.com on 9 Sep 2010 at 3:04

[GoogleCodeExporter]

Comment by Chris Hack; Sept 17 2010
Speakerphone ON during all calls.
Using T-Mobile G1 unlocked WIFI ONLY phone (no T-Mobile service), NOT rooted, 
CSipSimple_0.00-12-33-mjmd5.apk,
 android version- [firmware v1.6; baseband v62.50sc.20.17h_2.22.23.02; kernel v2.6.29-00479-g3c7df37 android-build@apa26 #19; build number DMD64] 

Original comment by telephon...@gmail.com on 18 Sep 2010 at 12:00

[GoogleCodeExporter]

Just to report my progress on this point on this issue (was also discussed on 
issue 89).

Seems that there is something samsung did strangely with speakerphone/earpiece 
routing.
If you disable ringer (set phone to vibrate for example) it will goes through 
earpieace.
But... if you activate speakerphone, you'll never be able to switch back to 
earpiece (which is coherent with the fact when the phone rings, then sound goes 
through speaker).

That's really a strange behavior, and I decided to wait for the samsung update 
to 2.2 (that is announce for the next weeks) since it seems to be something 
samsung do not correctly. There is probably a workaround for current rom (as 
fring has a solution... they don't share ;) ), but I guess it's a workaround.
If with 2.2 we reproduce the issue, I'll spend time on this issue to solve it.

Original comment by r3gis...@gmail.com on 19 Sep 2010 at 6:01

• Changed state: Accepted

[GoogleCodeExporter]

Samsung has delayed their update... :/ Hope they'll release something soon

Original comment by r3gis...@gmail.com on 25 Sep 2010 at 6:37

• Changed title: Speakerphone always runs Galaxy S/Vibrant

[GoogleCodeExporter]

Yes, I read something of one moth delay.

Original comment by uwe.fr...@edor.eu on 25 Sep 2010 at 7:29

[GoogleCodeExporter]

Unfortunatly I still have this loudspeaker issue when running a leaked build of 
froyo xxJPH. Unfortunatly it appears that samsung still has not solved the 
problem : ( Appart from the loudspeaker problem this app its fantastic.  Cheers.

Original comment by mitchelm...@gmail.com on 25 Sep 2010 at 11:18

[GoogleCodeExporter]

@mitchel : Really interesting. Thanks a lot for this information.

It means that I can already have a closer look to find out how to solve this 
problem. 
Can you confirm that Fring with incoming call  - and a ringing state before - 
redirect output to earpiece?
If so, can be a good starting point for me to do reverse engineering on what is 
done by Fring ... maybe they add a delay before call establishment or use 
another audio mode.

Original comment by r3gis...@gmail.com on 26 Sep 2010 at 7:15

[GoogleCodeExporter]

Hello, I confirm Fring works ok for me. It also switches back from speaker to 
earpiece correctly.

Original comment by giulio.m...@gmail.com on 26 Sep 2010 at 7:33

[GoogleCodeExporter]

@r3gis.3R How to try another open source sound app. It it is working (switch 
erarpiece / back speaker), you could look at it?
Maybe something like http://code.google.com/p/musikcube/

I don't know, if it helps, because it is not a phone app, but maybe the 
solution isn't so complicated if we know more?

Bad news, that froyo don't make things better :-(
Maybe waiting for the final release?

Original comment by m...@ufritz.de on 26 Sep 2010 at 8:22

[GoogleCodeExporter]

I went back and tested 3 sip applications that work / sort of work with the ear 
piece.

Fring:
- I can confirm there is a ring state and a slight lag before I hear audio 
though the ear piece.
- After that slight lag the call seems to work fine however audio can be rather 
laggy / choppy.

Nimbuzz:
- App manages to redirect audio to the ear piece but shortly after the call 
disconnects.
- There is a very noticeable lag-time from when I answer the call to when I 
hear the conversation through the earpieces.

3CX:
- Calls work fine, noticeable delay between when I answer to when I hear audio 
through the ear piece.

Additional information:
- For all three applications I have used the sip provider Voxalot.
- 3CX seems to have the best and most reliable sip calls out of the three 
applications.
- All apps seem to experience lag time when audio is redirected to the ear 
piece.

Anyway hope that helps, and if you need me to test anything else just ask : )
Cheers

Original comment by mitchelm...@gmail.com on 26 Sep 2010 at 8:38

[GoogleCodeExporter]

@mail : yes if we found an opensource project that can manage that would be 
fine. However I didn't found anything on musikcube about speaker/earpiece 
switch and besides they manage directly MediaPlayer -that do a lot of thing to 
be able to play music- while for a SIP application we have to use AudioTrack.

@mitchel : ok. Thanks a lot for these tests. I'll test more on the phone of a 
colleague Monday. Key point seems to be the delay between answer and audio 
stream start. I'll have a closer look and keep you informed.

Original comment by r3gis...@gmail.com on 26 Sep 2010 at 9:22

[GoogleCodeExporter]

Issue 247 has been merged into this issue.

Original comment by r3gis...@gmail.com on 28 Sep 2010 at 3:16

[GoogleCodeExporter]

I also have issues with speaker phone always being on.  It doesn't matter if I 
toggle the speaker button on the screen.  

Samsung Moment m900
Sprint
Android 2.1

Original comment by swan...@gmail.com on 28 Sep 2010 at 7:59

[GoogleCodeExporter]

Well.
I had some time with a galaxy S to test on :D... And pleased to announce that I 
found a way to solve this problem.
However it's more a hack than a clean way... but seems to work on the phone of 
my colleague (galaxy S with official current ROM).

However, there is still something strange with earpiece volume. It's really 
loud...even if I reduce volume using volume buttons - however the setting in 
Setting > Media > Speaker amplification does the trick.

So 0.00-13 available on download section (remember to uninstall if using market 
version).

I'm also interested with what do you think about micro media quality. I've 
-once again- refactored the audio driver in order to find a good way that works 
on all devices.

Original comment by r3gis...@gmail.com on 29 Sep 2010 at 10:26

[GoogleCodeExporter]

Sorry not 0.00-13 but 0.00-13-02 of course. 
http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-13-02.
apk

Original comment by r3gis...@gmail.com on 29 Sep 2010 at 10:36

[GoogleCodeExporter]

Hi,
I am having a similar issue with a T-mobile pulse (Huawei U8220) on the latest 
dev builds. Looking at the output on logcat I noticed I was getting this 
messasge:

W/AudioFlinger( 1067): RecordThread: buffer overflow 

This led me the the following thread:

http://code.google.com/p/csipsimple/issues/detail?id=146

So I tried the version you recommended in there:

http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-18.
apk 

And voila, I was getting sound through the ear-set speaker. Is there a later 
version I could try that still uses the same method of audio routing?

Thanks very much for such a great app.

Original comment by averylon...@gmail.com on 1 Oct 2010 at 12:32

[GoogleCodeExporter]

@comment 18 : The audioflinger log is not really relevant of your issue (it can 
appear sometimes on many phones)
As for your issue, it was reported in private by somebody else. I would need 
your android version. Is that android 1.6? I guess that I introduced a 
regression recently while refactoring to make it work another device.
What could help me a lot if you have some time to spend is testing from 12-18 
until the sound goes through the speaker and say me the last version that works 
OK for you.
Since in fact for this kind of issue, logs are not really helpful since it 
depends only on the interpretation of the phone of android functions (which are 
more or less deprecated or useful according to the device/android version).

Original comment by r3gis...@gmail.com on 1 Oct 2010 at 4:02

[GoogleCodeExporter]

Hi,
Thanks for the reply. I am running android 2.1 (T mobile's updated ROM) with 
2.6.29 kernel. I'll give your suggestion a shot and will report back later.

Original comment by averylon...@gmail.com on 1 Oct 2010 at 4:34

[GoogleCodeExporter]

Hi,
The last version of the currently hosted releases which worked with the pulse 
was:

http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-19.
apk 

The next release after this, namely:

http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-22.
apk ,

reverted back the playing the calls through the rear speaker. I believe the 
intermediary releases 12-20 and 12-21 have been removed from the download 
section so I could not try these.

Original comment by averylon...@gmail.com on 1 Oct 2010 at 5:11

[GoogleCodeExporter]

Hi r3gis.3R,

Thanks for finding the 'hack' :)  I just tried the latest beta apk and it does 
indeed seem to fix the outgoing call loud speaker issue, but when I receive 
incoming calls it still routes to the loud speaker.  

I noticed you posted on the sipdroid issues page, THANKS!! :)

Original comment by gum...@gmail.com on 12 Oct 2010 at 1:32

[GoogleCodeExporter]

Mmh that's strange for other users it seems to work properly with galaxy s for 
incoming (in csipsimple hack was needed only for incoming actually ).
Could you try 0.00-13-02 (that has been validated to solve this issue). I guess 
you tried 0.00-13-06b. I hope that I didn't introduce a regression in this one. 
Let me know.
Another thing : you should uninstall sipdroid and other sip app to be sure 
there is nothing that change routing when testing the app

Original comment by r3gis...@gmail.com on 12 Oct 2010 at 6:13

[GoogleCodeExporter]

Using http://csipsimple.googlecode.com/files/CSipSimple_0.00-13-02.apk

Incoming seems to work correctly and the volume of the incoming call is 
'normal'.  The outgoing calls still seem to be routing through my rear speaker. 
 However, if I turn the speaker phone on (bottom right button I think, and then 
turn it off) it seems to route correctly.

Not sure if the same work around would work in the latest beta.  I will try 
that in a min.

(2 mins later)

So I tried the same thing with the latest beta 0.00-13.06b and indeed am 
hitting the same problem.  Perhaps my issue is a different problem to this?  If 
the fix was only for incoming calls maybe this is a problem I am seeing with 
outgoing?

My phone is run JH2 firmware on the Bell Samsung Galaxy S (I9000M) this is the 
canada branding, but I have been told on XDA that this is the same as the 
I9000.  I am also running 2.1 Eclair update 1. 

Original comment by gum...@gmail.com on 12 Oct 2010 at 6:33

[GoogleCodeExporter]

Yes indeed could be a different problem. 
When you dial for outgoing, are you using csipsimple dialer? And if yes, when 
you press a dialpad key is there a sound? 
If I well remember, I did my tests without sound feedback from dialpad and as 
it produce sound it could conflict the outgoing sound stream then.
Also, if you can try to reboot the phone just before testing. If another app 
has set the audio routing in a bad state, CSipSimple can be impacted.
I'll try to ask my colleague to borrow me his phone today to see if I can 
reproduce your problem (I'll also try to solve the volume issue).
Anyway, could you send me logs? (See HowToCollectLogs on the wiki - there is a 
particular manipulation).

Last point I'm really interested in (not directly linked to your issue), with 
I9000M and 0.00-13-06b installed (with all previous version uninstalled 
before); if you go in settings > media , are speaker amplification and micro 
amplification set to 0.2 and 0.4? (These default values should be populated by 
0.00-13-06b automatically if freshly installed to avoid echo problems).

Original comment by r3gis...@gmail.com on 12 Oct 2010 at 6:48

• Changed state: Started

[GoogleCodeExporter]

I am hitting this issue using the csipsimple dialer and the phone dialer.  I 
has the haptic feedback was enabled before so there was sound and vibration 
when dialing. I tested again by disabling this with no sound or vibration in 
the UI settings in csipsimple.

I have set the log level to 4 and reran the test (with haptic feedback enabled) 
and have installed log collector to send to your gmail.  This is my first, so 
hopefully I got you the data logs you needed.

Speaker and micro amps settings are 0.2 and 0.4 respectively.  I did uninstall 
and reboot the phone before testing.

Again, thanks for looking into this.  I love the UI of this client!

Original comment by gum...@gmail.com on 12 Oct 2010 at 7:08

[GoogleCodeExporter]

Same issue with HTC G1 running 1.6.  Sipdroid works with earpiece.  Be good 
when we can move to csip as it works much better with sipsorcery (as you can 
change the register/alive timouts).

Original comment by kro...@gmail.com on 19 Oct 2010 at 10:20

[GoogleCodeExporter]

Ok; downgraded my HTC G2 (magic) to 1.6 and reproduced... and fixed :)
Will be in next release.

Original comment by r3gis...@gmail.com on 19 Oct 2010 at 3:18

[GoogleCodeExporter]

Can't wait.  No literally.  Tried to download.  Where is it? :-)

Original comment by kro...@gmail.com on 20 Oct 2010 at 6:22

[GoogleCodeExporter]

For 1.6 problem -> fixed in 0.00-15-03 (I hope so).

For galaxy S owners... I have (once again) refactored the audio driver cause 
changes I did to make it compatible with Galaxy S (and all alsa based devices), 
had a deep impact on 1.6 and lower devices. 
So if you can test the latest version and say me if there is no regression for 
your device, would be nice :). I did changes that stay in the same idea but 
changed the flow and how delays of the micro are managed.

@gumpwa : I didn't borrow the phone of my friend to add breakpoints yet. But 
I'll do. So I don't think this version will help with your problem. I'll keep 
you in touch.

Original comment by r3gis...@gmail.com on 22 Oct 2010 at 9:31

[GoogleCodeExporter]

Hi r3gis.3R, first of all many thanks for your great job,
I would like to tell you my experience with my HTC MAGIC v. 1.6 and your 
csipsimple 0.00-15-03:
- Rear speaker is now off when I start a call, I can make a regular call using 
the standard handset.
- the buttons of the volume in the side of the phone move "multimedia app 
volume", but I can't hear any difference in my ear. The level that really 
influence the level is "Call volume".
- when I start a call, I can see a disabled speaker on the notify area; if I 
click on the speaker icon in the bottom right , I can see the icon on the 
notify area disappearing and then reappearing immediatly, but speaker is always 
off.
- after touching the icon button, I can see many audio channels (notify volume, 
system volume etc) to level 0 till I close my call.

I used "Audiomanager" to see these changes.

hope this could help

thanks again
Guido

- 
-  

Original comment by guido.ca...@gmail.com on 23 Oct 2010 at 6:16

[GoogleCodeExporter]

For the "notification speaker icon" > you should read that :
http://code.google.com/p/csipsimple/wiki/FAQ#There_is_a_mute_icon_in_the_notific
ation_bar_while_in_call

It's the ringer mode that you see in notification bar.

I'll check if on my HTC magic downgraded to 1.6 (Cyanogen) speaker mode works. 
For the volume, you're right, there is a problem I've noticed too. 
The media volume was my last temptative to make it work (and I forgot to remove 
it ;) .. 

Original comment by r3gis...@gmail.com on 23 Oct 2010 at 7:25

[GoogleCodeExporter]

Great, R3gis! 
Everything work as expected in my magic 1.6 official vodafone!
- Call starts. to my handset
- Side level buttons move call volume and I hear difference
- Speaker icon enable (and disable) the rear speaker

Really great (and fast) work!
I'd really like to be a programmer like you : )

Thanks
Guido

Original comment by guido.ca...@gmail.com on 24 Oct 2010 at 10:11

[GoogleCodeExporter]

Good news :).
I close (NextRelease) the issue since 1.6 regression was the latest thing to do 
regarding this problem.

For Galaxy S owners, there is the issue 254 for specific audio volume change.

I think that I'll do a soft volume change instead of delegating it to the 
android sound system (which is really inconsistent...)

Original comment by r3gis...@gmail.com on 24 Oct 2010 at 10:29

• Changed state: NextRelease

[GoogleCodeExporter]

Noticed this thread is quite old but thought it's perfect for the issue I'm 
facing as the same problem is occurring. I got a Samsung Galaxy S and upgraded 
it to FroYo.DXJPE. Downloaded the latest CSipSimple-0.01.apk using Market but 
it's also automatically going to Speaker. Can't seem to turn speaker off when 
making outgoing calls. I've not tried incoming calls yet. 

Is there something I need to do to fix it? :)

Love this program, thanks for creating it!!!

Original comment by chery...@gmail.com on 12 Feb 2011 at 7:07

[GoogleCodeExporter]

@chery : this is a bug on Samsung side. They fixed it in most recent ROM 
versions. 
On my SGS on Eclair XXJPY it works fine.

Original comment by r3gis...@gmail.com on 12 Feb 2011 at 8:31

[GoogleCodeExporter]

Old thread but issue still appearing on my phone with version 0.02-03 (latest 
on market)

Android 2.1 (Last TCT Mod) on Huawei U8100-9

An earlier version of csipsimple viz 0.00-12-19 linked below works for me.
http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-19.
apk

Original comment by mattbb...@gmail.com on 28 Jul 2011 at 2:33