#145 Speakerphone always runs Galaxy S/Vibrant

[Anonymous]

Originally created by: troy.gla...@gmail.com
Originally owned by: r3gis...@gmail.com

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.

[Anonymous]

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

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).

[Anonymous]

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

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

[Anonymous]

Originally posted by: dr.seamu...@gmail.com

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.

[Anonymous]

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

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]

[Anonymous]

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

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.

Owner: r3gis.3R
Status: Accepted

[Anonymous]

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

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

Summary: Speakerphone always runs Galaxy S/Vibrant

[Anonymous]

Originally posted by: uwe.fr...@edor.eu

Yes, I read something of one moth delay.

[Anonymous]

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

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.

[Anonymous]

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

@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.

[Anonymous]

Originally posted by: giulio.m...@gmail.com

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

[Anonymous]

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

@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 https://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?

[Anonymous]

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

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

[Anonymous]

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

@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.

[Anonymous]

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

Issue 247 has been merged into this issue.

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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:

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

So I tried the version you recommended in there:

https://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.

[Anonymous]

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

@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).

[Anonymous]

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

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.

[Anonymous]

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

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

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

The next release after this, namely:

https://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.

[Anonymous]

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

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!! :)

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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).

Status: Started