Bluetooth support

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Pair and connect headset
2.Initiate a call with cSipSimple ( cSip Simple )
3.Press bluetooth button

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

My bluetooth headset should take over the audio for the call.

What version of the product are you using? On what operating system?

Latest version as of this issue submission.

Please provide any additional information below.

Not sure if this is an enhancement request or what, but bluetooth should work 
seamlessly.

Original issue reported on code.google.com by Djonas2...@gmail.com on 14 Jun 2010 at 4:29

[GoogleCodeExporter]

As for bluetooth with android 2.3 or upper there were a recent regression due 
to the fact I integrate the new audio mode. I've just fixed that to exclude 
Bluetooth from the new mode with hardware echo cancellation. So will fix be 
available in r832 and upper.
If you don't want to wait for the nightly build, you can simply use audio 
troubleshoting workarounds and set Audio mode to MODE_NORMAL (instead of 
MODE_IN_COMMUNICATION), and it will solve the problem.

Original comment by r3gis...@gmail.com on 7 May 2011 at 11:01

[GoogleCodeExporter]

Thanks for your response, Regis. Ok, I'll wait for r832, then. Hope there is 
some progress there. Nevertheless, I'd like to tell you that I always install 
the nightly build as soon as I notice it has been released, but, unfortunately, 
bluetooth mic handling has never worked. Why Android can correctly pick the 
bluetooth microphone during phone calls, but not CSipSimple? By the way, my 
audio mode has always been set to normal. I've just played with it a little 
bit, but CSipSimple simply rebooted my phone (after hanging my phone for some 
time, first) after trying the audio test. So, no joy there.

Original comment by casou...@gmail.com on 7 May 2011 at 1:48

[GoogleCodeExporter]

The phone calls has absolutely no problem with that because it IS the phone app 
that manage Bluetooth connection.
Third party apps has to ask the telephony app to share its own connection with 
the bluetooth SCO headset... and some manufacturer did crappy things there. 

Keep in mind, a third party application is not a core application. There is 
much more abstracted layer between a third party application and the core 
Telephony app. The core telephony app directly talk with the headset and 
establish raw connection with it.
A third party app has to ask using the API (that finally ask the Telephony 
application as far as I can tell after reading the android source code), to 
stream its own audio to the connection that was established between the 
Telephony app and the headset.

The audio layer in android is really not done to perform voip (start to be 
after android 2.3 cause google was needing it to provide their stock SIP 
application). But users has to be aware about that. 
Streaming audio for input/output is something that is not well supported by the 
android system before 2.3. Latency is high, I have to do hacks for each 
manufacturers to have the correct routing (and even for standard routing - 
earpiece - mic - spearker...).
And that's just about the way each manufacturer implement things.
So just imagine ... Bluetooth SCO that is managed by another app which is 
highly dependent of the GSM chipset...
If where Bluetooth AD2P would have been by far easier cause this is managed at 
android OS level... but problem ... no micro on Bluetooth AD2P :S.

So try to be indulgent with this kind of problem. I really do my best to 
support as much device as possible, but keep in mind that just not plug and 
record... That's plenty of hacks.

Original comment by r3gis...@gmail.com on 7 May 2011 at 2:53

[GoogleCodeExporter]

Hi Regis, really sorry if I've sounded harsh or impatient in my previous posts. 
I really didn't mean it. I do understand your point. And thousand thanks to 
you. You've been spending too much time and hard work to make CSipSimple such a 
fantastic application. I like it very, very much, and regardless this BT 
headset's mic noise issue, will keep installing each and every nightly build 
you release.

Original comment by casou...@gmail.com on 7 May 2011 at 3:28

[GoogleCodeExporter]

No problem don't worry, that was just to explain why this issue is still open 
and running :). 
And your feedback is really welcome.
I always try to explain why things are going bad cause I think that an 
opensource software also has to learn things to its users ;). Besides I think 
that it's always less frustrating to understand why something does not work.

Original comment by r3gis...@gmail.com on 7 May 2011 at 3:34

[GoogleCodeExporter]

Small feedback after running r836 nightly build on my Defy (Froyo UK 3.4.3-11 
ROM): unfortunately, mic distorted voice issue is still there. Thanks, anyway. 
Wainting for your next release...

Original comment by casou...@gmail.com on 8 May 2011 at 2:00

[GoogleCodeExporter]

Hi Regis, voice distortion through BT headset's mic is still present in r839. 
Thanks for your efforts, anyway.

Original comment by casou...@gmail.com on 9 May 2011 at 4:38

[GoogleCodeExporter]

Hi, Regis, a little bit off-topic here, but, for the first time ever, I'm being 
offered to upgrade the nightly build by the market version. Should I proceed? 
Or, rather, should I uninstall the nightly build beforehand? Or, othewise, keep 
the nightly build?

Original comment by casou...@gmail.com on 9 May 2011 at 4:30

[GoogleCodeExporter]

@casou : ok :(. Do you know what kind of headset you own? Is it ad2p or pure 
sco only?

About update, nightly and market version are compatible with each other (I sign 
with the same key). I think that downloading from the market should be 
equivalent that downloading from the nightly repo (unless google market does 
things in the middle). So you can try to upgrade to market version, the only 
risk is that it refuse to install ;).

Original comment by r3gis...@gmail.com on 9 May 2011 at 8:10

[GoogleCodeExporter]

Most of the time, I use a SE HBH-IS800 model, which is A2DP compatible. 
However, I only activate its A2DP feature in my Defy's BT settings when I want 
to listen to music. At the moment I tested CSipSimple through it, it was 
handling HFP/HSP only. By the way, I also tested with a monaural Cardo S800, 
but the results are the same, i.e. microphone distorts my voice. 

Thanks for your reply on the update process. You see, the market version being 
offered to be updated is 0.02-01, whereas r839 is still 0.02-00.

Original comment by casou...@gmail.com on 9 May 2011 at 8:54

[GoogleCodeExporter]

Update: market version 0.02-01 still has the same problem with BT mic handling: 
voice it highly distorted.

Original comment by casou...@gmail.com on 9 May 2011 at 9:10

[GoogleCodeExporter]

Not working in nightly build r842 yet...

Original comment by casou...@gmail.com on 10 May 2011 at 2:56

[GoogleCodeExporter]

Have just tested with nightly build r846: issue not solved yet.

Original comment by casou...@gmail.com on 11 May 2011 at 3:22

[GoogleCodeExporter]

With r855, pattern of distortion seems to be different. Maybe you get some clue 
with this information...

Original comment by casou...@gmail.com on 13 May 2011 at 10:42

[GoogleCodeExporter]

Ok, would mean you have the "use mode api" activated for the Defy? 
You did it by changing the configuration or that's was the default setting?

Original comment by r3gis...@gmail.com on 13 May 2011 at 12:18

[GoogleCodeExporter]

No, both 'Mode audio API' and 'Routing API' are unticked. And my 'Audio Mode 
for SIP calls' is set to 'normal', as always. It's hard to explain, but my 
voice is just distorted slightly differently. It's pretty subjective, though. 
It might be a false alarm...

Original comment by casou...@gmail.com on 13 May 2011 at 2:39

[GoogleCodeExporter]

with csipsimple market version 0.02-01.apk sometimes bluetooth is working 
sometimes not, but the bluetooth behavior seems unpredictable. 
I'm using an HTC desire with gingerbread 2.3.4
anyway, marvellous app :)

Original comment by sgn...@gmail.com on 26 May 2011 at 7:06

[GoogleCodeExporter]

Hi Regis, do you have any plans to touch the bluetooth stack (actually, the 
microphone part for the headset and handsfree profiles) anytime soon?

Thanks for your efforts, anyway. Have a nice weekend!

Original comment by casou...@gmail.com on 27 May 2011 at 11:12

[GoogleCodeExporter]

I was wondering that as well. I think the BT stack was recently updated in the 
latest versions of CM as of last month and the month before. Im just kinda 
upset that they have kicked D/S users to the curb.

Original comment by Djoneslo...@gmail.com on 27 May 2011 at 11:16

[GoogleCodeExporter]

Issue 1008 has been merged into this issue.

Original comment by r3gis...@gmail.com on 31 May 2011 at 10:58

[GoogleCodeExporter]

I have kind of a 'half way' solution with using the Bria app on my moto Ddefy.  
It isn't ideal but the bluetooth will route the audio to the bluetooth speaker 
and the regular microphone on the phone will work as normal.  You have to shout 
but at least you can answer a call while driving.

I think this works because Bria (rymes with inferior :-) doesnt have bluetooth 
support and the audio is simply hijacked by the bluetooth.

I tried the same trick with csipsimple by turning bluetooth option button off.  
The audio still routes to the speakers but the Mic now has not connection.

Original comment by paulblac...@gmail.com on 31 May 2011 at 7:40

[GoogleCodeExporter]

You have an A2DP bluetooth device?

If so it would explain, what you observe : in fact when you use an AD2P device, 
nothing has to be done to route the audio.

Unfortunately, since CSipSimple tries to do things to activate the SCO mode of 
your BT device (and grab the micro that is not available on AD2P).
On AD2P quality should be by far better (obviously AD2P is stereo and 16kHz 
;)... but has no micro capture feature ;) ).

I could try to add an option to "do nothing with BT" so that it would run the 
same way than apps that does not try to support BT. (It was what was previously 
done by CSipSimple before BT was added ;) ... )

Original comment by r3gis...@gmail.com on 31 May 2011 at 9:07

[GoogleCodeExporter]

Please, implement that option, Regis. I think it might work, somehow. Will let 
you know , then...

Original comment by casou...@gmail.com on 31 May 2011 at 9:44

[GoogleCodeExporter]

Yeah that would be better than it is now.
Ultimately it would be good to get BT working, of course, but this is a good 
alternative for now.

Just a wee note though...With this method, the call, be it incomming or 
outgoing, will not silence your music or radio. You have to manually switch the 
car stereo to BT audio (as if you were playing MP3 for example) and then you 
get the audio.  But hey it works.

Original comment by paulblac...@gmail.com on 31 May 2011 at 9:58

[GoogleCodeExporter]

Ahh folks this is a bit embarrassing but I have my defy working on Bluetooth 
now!!
Basically I deleted the Bluetooth pairing and recreated it and now i get 2 way 
audio no problem. The old paring was leftover from an earlier firmware (stock 
rom) and now running CM7.1

I still need to manually switch my car stereo to "AUX" but that is no biggie.  
Regular cell calls will mute the car stereo and switch to Bluetooth audio 
automatically, which is nice, but you just have to remember to do this manually 
when receiving a call on csipsimple.

Thank you for your help and I hope my solution will work for others also.

Original comment by paulblac...@gmail.com on 7 Jun 2011 at 6:11

[GoogleCodeExporter]

Glad that it worked for you. It might be due to a different kernel in CM7. I'm 
running Froyo (UK 3.4.3-11 ROM), and, for me, the bluetooth microphone is 
highly distorted. I don't upgrade my Defy to CM7 (or, better yet, the newer 
leaked 4.5.1-112 ROM) because it has a green camera, and theses ROMs are buggy 
whilst taking pictures or shooting videos.

Original comment by casou...@gmail.com on 7 Jun 2011 at 6:11

[GoogleCodeExporter]

r3gis I thought i would let you know that Bluetooth is sorta working on a 
Motorola Droid, latest froyo and a blueant t1 with the latest nightly build.. 
Rate is set at 16 and in a call I have to turn on speakerphone. That puts sound 
and Mic through the headset. If the speakerphone would just come on when using 
Bluetooth them i wouldn't have to set that at all. all sound is through the 
headset, none on the phone speaker.

Original comment by tlkhor...@gmail.com on 8 Jun 2011 at 10:22

[GoogleCodeExporter]

Regis, I don't know whether this kind of infornmation would be of some help in 
your attempt to solve the blueotooth mic distortion problem on my Motorola Defy 
or not, but I gave SipDroid (also an open project) a try, and sound through 
bluetooth is pretty flawless.

Hope you are able to solve this issue pretty soon, because CSipSimple is such 
the greatest voip application for Android, far superior than SipDroip in all 
aspects, but this particular one.

Tahnks, anyway.

Original comment by casou...@gmail.com on 11 Jun 2011 at 7:46

[GoogleCodeExporter]

first off great app. really like the integration with android.

i am having issues with Bluetooth on the tmobile g2x (lg 2x), with bluetooth 
enabled is not transmitting nothing to the car stereo, willing to provide any 
information you need.

thanks

Original comment by davidpes...@gmail.com on 16 Jun 2011 at 10:22

[GoogleCodeExporter]

I will have to amend my comment, 77. It works most of the time. Every once in a 
while it will not work at all. No sound at all and I have to hang up and try 
again. Once is worked without the speaker phone. I can't find any rhyme or 
reason for it so no pattern that I can give you.

Original comment by tlkhor...@gmail.com on 17 Jun 2011 at 3:27

[GoogleCodeExporter]

For me CSipSimple works almost perfect. I use SGS2 (Gingerbread 2.3.3). The 
only issue I have is lack of usability of BT in a car when the phone is 
connected to car BT system. If I try to make a call using CSS, the connection 
is established but no audio on both sides. With my Jabra BT3030 (stereo) calls 
are OK so some work should be done to solve car BT system problems. If this 
could be solved, this app would be the best on (android) market solution for 
VoIP.

Original comment by Tadeusz...@gmail.com on 21 Jun 2011 at 3:38

[GoogleCodeExporter]

Hmm i'm a bit confused. Do you support Bluetooth or not? Cause i didn't find 
anything in the settings menu.
Today i tried just for fun to make a phone call via CSipSimple with my car 
stereo connected but i did not hear anything.

Original comment by DanielDa...@googlemail.com on 5 Jul 2011 at 6:46

[GoogleCodeExporter]

I have been getting no sound issues as well with my Jawbone Icon.  I like 
CSipSimple's implementation and I would be willing to pay money for this app.  
Unfortunately, no bluetooth is a major issue and I have to switch to the sip 
client built into the phone.

Original comment by lordb...@gmail.com on 7 Jul 2011 at 5:03

[GoogleCodeExporter]

Regis, any estimations about when that 'do nothing with bluetooth' option will 
be made available? Thanks, anyway.

Original comment by casou...@gmail.com on 7 Jul 2011 at 10:25

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Like #82, I am a bit confused about the BT support. My SGS1 with 
Gingerbread.xwjvh shows a BT button during active calls, but this button is 
greyed out (deactivated).
After installing the dev version, I see some BT related settings but I do not 
get the BT button enabled. All sound is routed to the phone's internal speaker 
and mic. My headset is a HBH-DS980 from SonyEricsson and is paired with the 
phone.

Original comment by fami...@tamm-tamm.de on 18 Jul 2011 at 9:37

[GoogleCodeExporter]

Issue 1156 has been merged into this issue.

Original comment by r3gis...@gmail.com on 18 Jul 2011 at 11:29

[GoogleCodeExporter]

@ #86 : if the BT button is grayed out, it's usually cause your BT headset is 
seen as paired by the android SDK. It can be due to a miss in the way 
SonyEricsson implemented the api for BT, or with something not compatible on 
android OS side, that do not allow to share the BT SCO socket with the 
Telephony app.

Is the BT headset working for GSM calls?

Original comment by r3gis...@gmail.com on 18 Jul 2011 at 11:32

[GoogleCodeExporter]

Thank you for the fast reply Regis.
Yes, my BT headset works fine with both GSM calls and media files. It is paired 
with the phone and connected for both telephony and media.

Original comment by fami...@tamm-tamm.de on 19 Jul 2011 at 8:35

[GoogleCodeExporter]

After upgrading to Gingerbread 2.3.4, my BT button now is active, but touching 
it does not change audio routing, the phone still uses its internal speaker and 
mic. I will try some more of the advanced tweaks in Audio settings when I get 
the time.

Original comment by fami...@tamm-tamm.de on 21 Jul 2011 at 9:56

[GoogleCodeExporter]

Hi Regis,
I have to admit, last versions are really very stable. I am using it as my main 
phone at the moment. Thanks for your work. 
The only problem, I have is this BT <-> Car BT system issue. I have strange 
results.
1. It works perfectly well with my Jabra BT3030 stereo head set.
2. it works perfectly well with my NaviHeaven car stereo system nin one of my 
cars, in Phone calls and listening to audio from the phone (same as with my 
Jabra headset).
3. no audio on both sides of the call with my Mini (car) audio system with BT 
built in.
4. no audio on both sides with my friend's Mercedes audio system with BT built 
in.

NaviHeaven is an after market car audio (Chinese) installed in my other car. It 
has all possible features and works perfectly with both, standard phone app in 
my Galaxy S II as well as cSS installed in the same phone. 
My Galaxy works on Gingerbread 2.3.3 XXKF2 version.

Original comment by Tadeusz...@gmail.com on 3 Aug 2011 at 9:15

[GoogleCodeExporter]

By the way, Regis, I run small voIP commercial network. I would be glad if I 
could help in some way. I could provide you open voip accounts for tests, in 
example. I also plan to include links to CSS page, if I can. I plan to make 
some donation as well.

Original comment by Tadeusz...@gmail.com on 3 Aug 2011 at 9:24

[GoogleCodeExporter]

Hello,
Recently I have upgraded my phone (Sonyercisson Xperia X10) to Android 2.3.3, 
and I was hoping that the bluetooth support will work for the application.
Although the button no longer is grayed and I am able to enable the feature, 
there is no sound at all. The strange thing is that as long as I have bluetooth 
enabled on my phone, there is no sound at all not even over the mic and speaker 
of the phone, or even the loudspeaker. 
Is there something I am missing in terms of configuration, or it is just an 
incompatibility with my phone?

Original comment by cloukmob...@gmail.com on 8 Aug 2011 at 6:46

[GoogleCodeExporter]

Just another data point...

I generally keep up with the nightly builds on my Acer Iconia A500 running 
Honyecomb 3.1, but to date, using my Jawbone (old cheese grater version) I'm 
seeing the Bluetooth button not grayed, indicating that the bluetooth is paired 
and seen by the device, but sound does not route to the headset and the headset 
mic does not work.

I can hear some switching going on when I tap the bluetooth, but nothing 
happens on the jawbone.

Original comment by scree...@gmail.com on 8 Aug 2011 at 9:36

[GoogleCodeExporter]

Hi Regis,
I just have come to new experience.
I have made some tests with my to cars, Smart with NaviHavean radio with BT 
including stereo audio transmission and my Mini with its Mini + navigation +BT 
(without stereo audio transmission).
I have noticed that I can make a call from CSS on my Galaxy in Smart when radio 
is set to Phone screen only. If I am on radio screen (listening to radio) and I 
try to initiate a call from CSS: no way. When I do it using standard phone 
feature in my Galaxy, it is OK.
So I have made similar test in my Mini. I have initiated a call from the list 
off numbers shown in the Mini radio (downloaded from my phone by BT). Then the 
standard page giving an option to select the app to make a call was shown in 
the phone, so I've selected CSS, than the call was established and I could 
communicate through Mini BT feature, but only for few seconds. Then the call 
was disconnected and the Radio has shown an info: "Call end".
This suggests, that Radio in Mini waites for some confirmation of the call 
being established and while not receiving it, the call is disconnected.
I wonder if this can help you in resolving this issue. If you need any more 
help or tests or whatever, just let me know.

Original comment by Tadeusz...@gmail.com on 12 Aug 2011 at 2:16

[GoogleCodeExporter]

Hi Regis,

I am using a Jabra BT320s stereo BT headset with my Acer Iconia Tab A501 with 
Android 3.0.1 (Kernel 2.6.36.3. I prefer CSipSimple over SipDroid due to the 
much better sound quality. However on CSipSimple I do not get any sound on my 
BT headset, while it works with SipDroid.
May be, a peak in the SipDroid code can help you to find the missing link?
Keep up the good work.

Original comment by gunnar.h...@gmail.com on 18 Aug 2011 at 7:54

[GoogleCodeExporter]

PROBLEM SOLVED!!! After upgrading my Defy to Gingerbread v2.3.4, the bluetooth 
SOC microphone distortion issue has just disappeared. CSS is simply PERFECT now 
on my phone. Anyway, thank you very much for you effort and time, Regis!

Original comment by casou...@gmail.com on 2 Sep 2011 at 6:02

[GoogleCodeExporter]

Great news. :)

You should thanks Motorola ;). The problem was more likely on their side in 
their previous ROM (or at least now it ~also~ work the way I expect it should 
work).

But that's a good news cause it means motorola has their audio driver better in 
2.3.4 versions. Hopefully it will helps with their other devices too.

Original comment by r3gis...@gmail.com on 3 Sep 2011 at 8:30

[GoogleCodeExporter]

Hi Regis,

I have the same Problem as Comment 95.
I am trying to connect my Car Audi A5 with MMI Navigation Plus. If I make a 
call from my car then the call was disconnected and the Radio has shown an 
info: "Call end" and "Feature not supported by Phone".
Normal Calls via GSM will work. My Phone ist HTC Wildfire S

Regards Olaf

Original comment by okenfenh...@googlemail.com on 12 Sep 2011 at 10:30

[GoogleCodeExporter]

today I've installed the latest nightly, but bluetooth is not working yet

Original comment by sgn...@gmail.com on 7 Oct 2011 at 3:50