Earpiece on I5800

[GoogleCodeExporter]

What steps will reproduce the problem?
1. call anywhere

What is the expected output? What do you see instead?
Expected to hear sound through the handset, however,nothing is heard UNLESS I 
activate the rear speaker! Then I can hear the other party! However, it is not 
possible to switch to handset, only read speaker can be used for audio output. 

What version of the product are you using? On what operating system?
Android 2.1
Version 15

Please provide any additional information below.
I know this seems to be a problem for most SAMSUNG Androids, however, maybe a 
workaround is possible. 
Than kyou

Original issue reported on code.google.com by Allstar...@googlemail.com on 10 Nov 2010 at 4:20

[GoogleCodeExporter]

Same issue with my Galaxy I5700

Original comment by kayahan...@gmail.com on 11 Nov 2010 at 4:40

[GoogleCodeExporter]

Unfortunately, the only workaround I know on these devices is to use the 
alternative ROM of Samdroid that has explicitely fix the bug in samsung ROMs. 
(Don't know if Samdroid roms are available on 5800).

Original comment by r3gis...@gmail.com on 11 Nov 2010 at 9:36

• Changed state: Duplicate

[GoogleCodeExporter]

@Alistar. Oh... ok, indeed sounds to be a different problem.
So I'll need more infos :
* If you deactivate again the rear speaker does earpiece work?
* If response to last question is yes, if you use the hold button (pause) and 
then re-activate the call (just press again on the play button) ?

Original comment by r3gis...@gmail.com on 11 Nov 2010 at 10:00

• Changed state: New

[GoogleCodeExporter]

No, deactivating the speaker will just turn all audio off. 

Original comment by Allstar...@googlemail.com on 11 Nov 2010 at 10:21

[GoogleCodeExporter]

Ok. So probably more or less linked to issues I have with these samsung devices 
i5*** and i7*** ... sounds samsung try to make voip developpers crazy ;).
As slightly different from i5700, I'll keep that as a separate issue. But 
solving the other issue can maybe helps on this one.

Original comment by r3gis...@gmail.com on 11 Nov 2010 at 10:32

• Changed title: Earpiece on I5800
• Changed state: Accepted
• Added labels: Manufacturer-driver

[GoogleCodeExporter]

I've done an update that could help to debug the problem :

Could you try to install 
http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-15-16.
apk .

It include 3 hidden settings. To activate it :
Go in Settings > press menu and switch to "Expert mode".
Then in Settings > Media scroll to the bottom.
The 3 settings are :
Use Routing API => It enforce to use the old API that is deprecated in android 
2.0. Some ROM however are based on old audio drivers but are > to 2.0. In this 
case activating this setting can help
Use Mode API => It enforce to use something that is actually not an API but 
that is considered by some manufacturer to be the way to route audio... It's a 
very bad idea to use that on some device cause it use mode_in_call that 
directly plug GSM chipset to audio hardware. But sometimes on some devices 
that's the only way to get routing goes through earpiece.
In Call Mode => (Useless if you use "Mode API"), Force to use one audio mode. 
On most device should be set to Normal. But sometimes could be interesting to 
test others.

Let me know if one of these option helps, if so I can maybe make something that 
automatically configure for i5800

Thanks

Original comment by r3gis...@gmail.com on 26 Nov 2010 at 11:52

[GoogleCodeExporter]

In this version, no matter what setting i use, i cannot activate ANY audio, 
neither on the speaker nor the headset. 

Original comment by Spamschu...@gmail.com on 1 Dec 2010 at 1:47

[GoogleCodeExporter]

Issue 473 has been merged into this issue.

Original comment by r3gis...@gmail.com on 9 Dec 2010 at 9:51

[GoogleCodeExporter]

Thanks for moving issue 473 into this one and directing me to the above link. I 
have installed it, and like comment 7, I get no audio at all.

I have tried the following combinations of settings:

Use routing API - ON
Use Mode audio API - OFF
Audio mode for SIP calls - all sub-settings UNCHECKED

--

Use routing API - ON
Use Mode audio API - ON
Audio mode for SIP calls - all sub-settings UNCHECKED

--

Use routing API - OFF
Use Mode audio API - OFF
Audio mode for SIP calls > IN_CALL selected

--

Use routing API - ON
Use Mode audio API - ON
Audio mode for SIP calls > IN_CALL selected

Thanks for your attention to this issue.

Original comment by jonatha...@gmail.com on 9 Dec 2010 at 8:30

[GoogleCodeExporter]

Ok I've now a I5800 to test on :)

Well.... Samsung samsung samsung... why?!??? I don't know who codes audio 
drivers for android at samsung but I think that's a trainee.... 

That's really amazing what I discovered is that with standard options, you can 
get it working through earpiece.
(Routing API OFF, Mode Audio OFF and Audio Mode NORMAL)

It will work for incoming calls each time... and for outgoing calls, you have 
to produce a sound with the phone just 3s< before to start the call (for 
example pressing volume button or using dialpad audio feedback).... 
If you do so, the audio driver goes in a good audio mode and let streamed audio 
be rendered by the audio driver. Funny isn't it :)
And even better worse than in my nightmares, to make the speaker work I've to 
use IN_CALL mode ... IN CALL goes through speaker by default while NORMAL goes 
through earpiece....

So I think that I can have a tweaked version for this phone.... but it is just 
unbelievable the way they do their driver...
Had a quick look this morning to forum threads on XDA and have seen a lot of 
ROM makers crying about bugs on the audio driver of samsung device...

Well fortunately they've opensourced their driver so openfully custom ROM 
makers will contribute to these crappy audio drivers.

Original comment by r3gis...@gmail.com on 12 Dec 2010 at 4:35

[GoogleCodeExporter]

So... I've just found a workaround for that.
That's crappy but due to the fact samsung driver is awful ...

Could you try to install : 
http://nightlies.csipsimple.com/trunk/CSipSimple-r433-trunk.apk

Go in settings > Media > And activate Tone hack.
(Should be automatically activated on i5800).

Original comment by r3gis...@gmail.com on 12 Dec 2010 at 6:47

[GoogleCodeExporter]

Thanks. I tried the app at the link you posted. It connects but I can't hear 
the party I have called.  If I call another phone it rings and i can hear 
anything I say back as an echo about 1/2 second later.

This is on a Virgin Mobile Samsung Intercept with 2.1.

Original comment by jonatha...@gmail.com on 14 Dec 2010 at 7:31

[GoogleCodeExporter]

@jonathanyb : For the fact you can't hear other party : 
http://code.google.com/p/csipsimple/wiki/FAQ#The_other_party_can_hear_me_but_I_c
an_not_hear_them
May help

For the echo-ing : if echo is present on the CSipSimple part, it mean that it 
is the other part that produce the echo. 
If the echo is present on the other side it means that CSipSimple produce the 
echo. If so, you should simply try to reduce sound level (by default on Teos is 
really loud. There is a settings (in ExpertSettingMode that may allow you to 
reduce that by default for each calls).

Original comment by r3gis...@gmail.com on 14 Dec 2010 at 7:47

[GoogleCodeExporter]

Hi, I have the very same speaker/earpiece problem with my Sony Ericsson Xperia 
X10 Mini Pro.
Can you help me please ?

Original comment by nilcasd...@gmail.com on 3 Jan 2011 at 1:30

[GoogleCodeExporter]

Make that two with the issue on Virgin Mobile Samsung Intercept (running 
Android 2.2)

Original comment by danielro...@gmail.com on 3 Jan 2011 at 7:24

[GoogleCodeExporter]

you need to open a new bug for other devices, all android sip for sumsung have 
the same sound bug. samsug coding is very bad look at kies big fail imo

Original comment by shabangu...@gmail.com on 3 Jan 2011 at 11:07

[GoogleCodeExporter]

I've had the same issue with a ZTE Blade/Orange San Francisco, albeit with a 
custom firmware (Japanese Jellyfish RLS3b, which is froyo). Setting Use Mode 
API fixed it on that.

Original comment by m...@monki.org.uk on 3 Jan 2011 at 11:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Life keeps just getting weirder. 
I just got my I5800 with Android 2.2 back, and reinstalled Csipsimple r578. 
Turns out, the headset now works great, however, the MIC stopped working. And 
it is definetly a MIC problem, because I can hear the DTMFs clearly.

Original comment by Allstar...@googlemail.com on 18 Jan 2011 at 2:01

[GoogleCodeExporter]

I would have thought that this would be the ticket to success for my Samsung 
Spica i5700 but even with the tone hack checked and all the combinations for 
the API routing and Mode audio API, it still does not produce a sound out of 
the earpiece.

Original comment by mac10688 on 21 Jan 2011 at 8:49

[GoogleCodeExporter]

@mac : on i5700 you should consider upgrade the phone ROM. There is some known 
bugs on old samsung ROM that they have fixed meanwhile AFAIK.

Original comment by r3gis...@gmail.com on 22 Jan 2011 at 10:08

[GoogleCodeExporter]

Hey r3gis.3R, are you still reading this threat or should I open a new one, 
about the problem with the mic of the I5800?
Thanks

Original comment by Allstar...@googlemail.com on 26 Jan 2011 at 8:52

[GoogleCodeExporter]

@Allstar : yes I read. The issue is still opened so I consider this problem as 
not fixed.

I think that your current configuration is to use "Mode API". With some device 
and some samsung driver version it's cause GSM chipset is directly connected to 
micro (and in this case apps can't record anything in this case).

I'd advise you to try to play with audio hacks : Use routing api (on/off), use 
mode api (on/off), use tone hack (on/off).

If you find some good combination I'll be pleased to set this as default hack 
for the device. 
But definitely that's cause of Samsung driver ! What I propose here is just 
workarounds cause of the VERY BAD audio drivers from Samsung.
I also have to add that I have a i5800 to test on and now with Tone hack set to 
ON it works better (routing and mode api to off).
They recently (probably thanks to the fact they worked with google on the nexus 
S), fixed a little bit their driver on some models.
So I'd also advise if available on your phone to upgrade the phone to the 
latest version too.

Original comment by r3gis...@gmail.com on 26 Jan 2011 at 9:15

[GoogleCodeExporter]

Thanks, I tried all the different hacks. 
Basically, none is needed anymore with the latest version of Android 2.2. You 
are right about the Mic and GSM set. Without a GSM Card, no App can hear the 
Mic. If I put the GSM Card in, Apps can hear the mic again - why not Csip? 

Original comment by Allstar...@googlemail.com on 30 Jan 2011 at 8:47

[GoogleCodeExporter]

Mmm strange that SIM card is required on mine i5800 I do not need one to get it 
working. Probably some weird samsung thing again that they fixed in the version 
I have and not in the one you have...

As for the fact you do not observe in other apps could be explain I think : 
CSipSimple use a different method to record audio that allow almost "real time" 
recording while other apps use an higher API where samsung do probably their 
strange (and private) things before calling the lower interface I use. As 
consequence you can observe diffs between apps cause of that.

Original comment by r3gis...@gmail.com on 30 Jan 2011 at 10:26

• Changed state: Fixed

[GoogleCodeExporter]

Issue 366 has been merged into this issue.

Original comment by r3gis...@gmail.com on 30 Jan 2011 at 11:08

[GoogleCodeExporter]

Which version of the Phone do you have? I do have the latest 2.2 Android I 
think. 

Original comment by Allstar...@googlemail.com on 31 Jan 2011 at 9:50

[GoogleCodeExporter]

I still have this issue with the Samsung Intercept running 2.1. I have tried 
all the options and in different combinations, but no joy. Any idea about this, 
or will it always remain a mystery?

Original comment by phil...@gmail.com on 21 Feb 2011 at 7:08

[GoogleCodeExporter]

I, too, have a stock Samsung Intercept (Virgin Mobile) running 2.1-1.
I also have the same echo / rear speaker issue. I've tried messing with the 
suggestions above. But the sound always comes out of the rear speaker and never 
the earpiece (causing the echo). I understand its a driver issue, but in case 
it helps, here are the results to all of the combinations I tested.

 SETTINGS           :    RESULTS
Routing Mode    Galaxy  Tone    :   AUDIO   ECHO    SPEAKER
API API Hack    Hack

off off off off :   yes yes on
ON  off off off :   yes yes on
off ON  off off :   none    none    on
off off ON  off :   yes yes on
off off off ON  :   yes yes on
ON  ON  off off :   none    none    on
ON  off ON  off :   yes yes on
ON  off off ON  :   yes yes on
off ON  ON  off :   none    none    on
off ON  off ON  :   yes yes on
off off ON  ON  :   yes yes on
ON  ON  ON  off :   no  no  on
off ON  ON  ON  :   yes yes on
ON  ON  ON  ON  :   yes yes on

Original comment by depin...@gmail.com on 30 Mar 2011 at 8:41

[GoogleCodeExporter]

Hello, I have the same problem that audio goes through the rear speaker.
I have a Samsung Intercept 2.2, running the latest svn version of csipsimple 
#885.

I tried all the options listed here and also all the combinations possible and 
none worked, the only one that worked was the tone hack, but sadly the other 
party won't hear me :(

Any help is welcomed, thanks!

Original comment by salvator...@gmail.com on 25 May 2011 at 7:38

[GoogleCodeExporter]

Hi, The audio fix (tonegenerator) indeed fixes the problem and audio is being 
routed through the earpiece. (GT-I5801)
However, when the call is completed, the audio is not routed back to its 
original and the ringtone of the next incoming call is also played through the 
earpiece.

I've tried modifying your code and tested some options (like playing the sound 
again after setting it to in_call),... but no success.

Is there a possibility to set the phone back to its initial state when the call 
is disconnected? Going back to it's saved state does not seem to work.

Regards,

K.

Original comment by kevin.degryse@gmail.com on 6 Jun 2011 at 1:56

[GoogleCodeExporter]

Issue 366 has been merged into this issue.

Original comment by r3gis...@gmail.com on 16 Jan 2014 at 9:37