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]

Quietly normal, bluetooth is not yet implemented :)

Don't really know if it will be in the beta release (the application is still 
an alpha version). Seems not so easy to implement in order to be compatible 
with 1.5 to 2.2 devices. So will maybe not in the scope of the first stable 
release.

If so the button will not be present. The bluetooth button and the add call 
button too will be probably deleted/deactivated since not in the scope of the 
first stable release.

But, after the first stable release, this feature will become a priority for me.

Original comment by r3gis...@gmail.com on 14 Jun 2010 at 9:52

• Changed state: Accepted
• Added labels: Type-Task
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Have there been any updates on this issue ? 
Android 2.2 and the new sdk is out i think does that help?

Kind Regards,
Tiff

Original comment by TPnolan...@gmail.com on 12 Jul 2010 at 3:38

[GoogleCodeExporter]

Not yet.
The big issue is to succeed in doing something backward compatible (even if 
feature is not present on 1.5, 1.6 and 2.0).

Unfortunately, the dalvik doesn't really allow to make things dynamically and 
it's a little bit complex to wrap new methods into something that doesn't crash 
at running time on older OS. But that's possible.

As I previously said, for me that's not yet a priority. 
The first reason is that I have still a lot of work to do on the rest of the 
app.
The second reason is that I have no bluetooth devices (so it will be hard to 
test for me).

But... If anybody is interesting in developing this part of the soft, he is 
welcome. It's an opensource project !! :).
If nobody take this point before the first stable release, I'll take it and 
implement something.

Original comment by r3gis...@gmail.com on 12 Jul 2010 at 3:57

[GoogleCodeExporter]

HI.

i could send you a spare headset if that would help

Original comment by TPnolan...@gmail.com on 12 Jul 2010 at 9:07

[GoogleCodeExporter]

Really nice!
I'll probably ask you when I'll start the implementation if nobody do it before.

Thanks !

Original comment by r3gis...@gmail.com on 13 Jul 2010 at 11:47

[GoogleCodeExporter]

hey tiff! thats really cool of you to offer the dev like that, i have some 
headsets and stuff i dont use either if that helps as well. REALLY WANT TO SEE 
THIS GET DONE!

Original comment by Djoneslo...@gmail.com on 13 Jul 2010 at 10:23

[GoogleCodeExporter]

Any updates on this ?

I have an extra headset i found i could definitely drop in the post.
Also could you please upgrade the feature request priority to [High] .

It is a enhancement request after all with its own tag. Can't think of any 
other feature people are outcrying more for than this right now in a SIP client.
The fing feature request thread speaks volumes.

www.fring.com/forums/showthread.php?t=15877

Also i've been doing some testing on different SIP and softphone apps, i did 
come across one that is able to use the stereo bluetooth features of a 
bluetooth headset.
Its called Tubaloo but the quality was down right horrible and i had constant 
audio dropout on both sides.

I'm starting to wonder if this is even possible :(

Original comment by Djoneslo...@gmail.com on 27 Jul 2010 at 5:55

[GoogleCodeExporter]

So this issue will not been updated to High.
This is not a blocking feature. 
There is other people for how the application doesn't work at all. And theses 
issues has to be fixed before.
An important thing is that csipsimple is still an *alpha* version!!! Keep this 
in mind!!! It's developped by 3 people on their own time and I think that an 
issue about the use of an extra device is not a blocking issue for the beta 
release. 

I consider this as a nice to have *for* the beta release. But can be postponed 
for next versions. If you work all your nights, week ends and holidays on an 
opensource project, you'll understand that my first goal is to release 
something *stable* and useable for a *daily use* for all users. 

Though, this request is absolutely technically reachable. I've not time to take 
this point right now. 
Micheal has just committed a great improvement that allow to take call with a 
Bluetooth handset and he will maybe continue on this issue. 
So there is chance that this issue will be fixed before beta. But considering 
the overall project, this is is not a high priority feature.

So keep in touch of what is happening here. And if you have coding skills, you 
can contribute to the project (it is opensource & GPL!), you'll be welcome ;).

Original comment by r3gis...@gmail.com on 27 Jul 2010 at 6:54

[GoogleCodeExporter]

My last comment doesn't mean that I do not consider this feature as an 
important feature, just that for now it isn't.
It's just from the project management point of view, not from the feature and 
user experience point of view.

Original comment by r3gis...@gmail.com on 27 Jul 2010 at 6:59

[GoogleCodeExporter]

I want you to know i greatly appreciate you taking time out and explainging all 
of this ...schtuff! :P

Thank you so much for that.  I have a small question about the way Michael is 
tackling the approach to bluetooth support, is this going to be through the 
A2DP profile ?
( over stereo bluetooth ) .

Because from what I recall many MANY other developers have attempted to use 
that and it didn't work out well at all. Simply put. it just doesn't work.

Original comment by Djoneslo...@gmail.com on 28 Jul 2010 at 7:27

[GoogleCodeExporter]

I don't really know if Micheal will take the point actually. He did an 
implementation for take/end call using bluetooth device.

But good news for bluetooth users, I get a bluetooth device today at work. 
(That only support SCO bluetooth). 
I get my first csipsimple call using bluetooth working after about 2 hours of 
code  (Nexus One 2.2 + Jabra BT125). 
There is still things not stable and not clear, (such as if it will be possible 
to switch bluetooth on/off while in call), but sounds not so difficult for a 
first try...

Original comment by r3gis...@gmail.com on 28 Jul 2010 at 7:48

[GoogleCodeExporter]

Well that is the most wonderful news i have heard all month.
That and the word trickling down froyo is to be officially released this week!

I have 5 headsets (one of which i can't find).

- Motorola h710 bluetooth headset with no A2DP  (this is the one i can't find)

- Plantronics with no A2DP

- Sony erricson that has much support for different profiles.

- 2 x Jabra JX10 II 's
These also have support for many profiles but not sure about A2DP, but i 
believe it does.

And the one i use everyday.

My jawbone icon rogue.

I would be willing to send you the sony Ericson if it is helpful.

Original comment by Djoneslo...@gmail.com on 28 Jul 2010 at 8:28

[GoogleCodeExporter]

Hi, R3gis.3R
Has and of this been committed into the latest trunk ?
I couldn't really locate anything specific.

Original comment by Djoneslo...@gmail.com on 1 Aug 2010 at 7:17

[GoogleCodeExporter]

Be patient, first steps has been successfully done. On my nexus one (android 
2.2) I can now switch on/off bluetooth while in call. 
But to perform that, I need to refactor the way audio routes are established.
In fact, android can't re-route a audio track in streaming mode to bluetooth. 
So audio track has to be stopped and then re-run. This implies a lot of 
refactoring in my code. Besides in order to not break things for 2.1 and lower, 
wrapper class has to be done.

And so, as I don't want to commit things that don't work at all, (in order to 
not break work of Bob and Micheal), things are not committed yet. But soon I 
assure and in the same time a 0.00-12-07 with bluetooth SCO support for *Froyo 
only* (at least for now... maybe then I'll check if not possible from 1.5 to 
2.1) and improvements from Bob and Micheal.

Original comment by r3gis...@gmail.com on 1 Aug 2010 at 10:05

• Changed state: Started

[GoogleCodeExporter]

How much CPU usage does this take up, you mentioned your nexus one.

Are we going to end up "ceiling" on our lower end android phones ?

In theory if its a complete code re-write that needs to be done you could for 
the time being release a forked version with bluetooth supported hosted in 
another codebase ?

bSipSimple ?

Original comment by Djoneslo...@gmail.com on 2 Aug 2010 at 5:04

[GoogleCodeExporter]

????

1 - There is absolutely no impact on CPU! Why Bluetooth implementation could 
have an impact?

2 - Why do you want me to fork the project I started???? It makes no sens.

3 - CSipSimple build 0.00-12-07 is available for download : 
http://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-12-07.
apk
Be aware of the fact bluetooth is available only for android 2.2 and for 
bluetooth SCO devices. You'll need to force audio frequency to 8kHz (if changed 
from the settings) : not yet tested using 16kHz audio but SDK reference 
announce that bluetooth SCO stream only allow mono+8kHz.

Another point about this last version, Bluetooth don't automatically activate 
itself since detection of the presence of the device is not yet done. Todo 
later (seems not really simple to do sco api is poor).
Same thing with the Bluetooth take call button. I have a work around to manage 
it but it's not enough good to be integrated.

I'll see later for back-porting to 2.1 and lower. And then to A2DP bluetooth 
devices.

Original comment by r3gis...@gmail.com on 2 Aug 2010 at 6:01

[GoogleCodeExporter]

1 - This was a very bad misconception of me and im glad there is no impact on 
CPU ussage.

2 - I mentioned a fork because you had said you had to refactor your code.
Thought a split of the project would make things simple and keep users using a 
stable version.

3 - i'll check this out now and report all relevant info back.

Original comment by Djoneslo...@gmail.com on 2 Aug 2010 at 6:43

[GoogleCodeExporter]

R3gis  , could you give me an idea of what SIP provider and specific settings 
you are using ? I have tried the new bluetooth option and its not usable at the 
moment. The sound feed keeps fluctuating far to much to be able to carry on any 
conversation.

Could this be a limitation or difference of the chipset? I'm using the new 
android 2.2 released by htc this week on my mt3g ( 32b )
Which also i might add is one of the most popular phones made by HTC  eg: 
magic/saphire/onyx

Original comment by Djoneslo...@gmail.com on 2 Aug 2010 at 10:07

[GoogleCodeExporter]

Yes you're right, htc g2 (magic/mytouch) is too weak to support heavy codecs. 
For now all codecs are activated by default but once we will be able to do 
enough tests on many device csipsimple will automatically configure what codec 
is available on each device.

I also own a htc magic (still left in android 1.5 in order to test backward 
compatibility) and I make a lot of tests on it.
To make things work properly, I found out that forcing the use of PCMU or PCMA 
(by disabling all othre codecs in Option>Media>Codec & long press in each 
unwanted codec > Disable ); forcing 8kHz audio, disabling voice auto detection 
and disabling echo cancellation; make things working properly. 

The reason is that some codecs such as Speex for example consume a lot of CPU 
(for the codec topic, yes, CPU is a big deal).
Besides since builds I provide on the googlecode download section are 
debuggable and produce a lot of log. It also impact the performance on old 
devices.

Last point that can deeply impact performances is of course the network 
bandwidth.

For my tests on my HTC magic I use wifi, PCMU(or A)@8kHz without VAD and 
without echo cancellation.

Two question :
Is voice path (even if choppy) is well switched to your Bluetooth device?
I didn't know that htc released officialy froyo for G2 ! I though that last 
week it was an update for the HTC Desire. I'm really interested in their last 
update. Have you an url link for this update?

Original comment by r3gis...@gmail.com on 3 Aug 2010 at 6:56

[GoogleCodeExporter]

Thank you, i will try these settings immediately and see if they help.
As for the update, it was given out to a select pool of MT3G 1.2 and slide 
users.
HTC and Tmobile are actively sending out this update as of june 11th.
I'll try and package it up (pull the files using adb) and put them up somewhere.

I just got my device a few weeks ago and still getting used to it, however i 
have learned with allot of tweaking this thing can be just as fast as any 
nexus1 (minus the openGL LE stuff) .

Original comment by Djoneslo...@gmail.com on 3 Aug 2010 at 3:14

[GoogleCodeExporter]

:( this didn't really work out to well, ..still getting intermittent sound.
are there any other settings we can try ?

Original comment by Djoneslo...@gmail.com on 6 Aug 2010 at 1:34

[GoogleCodeExporter]

Mmmh maybe audio quality setting, change it to 3 if not already the case. 
Do you know what codec is in use when you are in call? (use the (i)nfo button 
to show information about current call).
I hope this is not a consequence of the Froyo update... on my device (remained 
in 1.5....) sound quality is pretty good on my tests. I probably should try 
with a cynanogen rom to see what is the impact of newer os version on the app.

Original comment by r3gis...@gmail.com on 6 Aug 2010 at 7:13

[GoogleCodeExporter]

r3gis.3R

First thank you for the great works in the last couple of weeks.
I've got to be subjective however, i'm really disappointed bluetooth is once 
again been given a back seat in development. I look at a LOT of non android 
devices with similar (if not the same) broadcom chipsets and the have more than 
made their bluetooth integration smooth and seamless. Which is not to say we 
can't get there.

It almost feels like being caught in a innovative paradox.

Its my esteemed hope bluetooth can be given a front seat in development with 
not just cSip but with other mainstream beta/alpha apps as well.

BEST
David

Original comment by Djoneslo...@gmail.com on 19 Aug 2010 at 6:20

[GoogleCodeExporter]

To your last question .

I've tried all the available codecs with the same intermittent audio issues on 
each.
RC3 of cyanogen is now available as well as a light version of gapps now.
Thank you very much for your help and time.

Original comment by Djoneslo...@gmail.com on 19 Aug 2010 at 6:25

[GoogleCodeExporter]

r3gis,

I've asked the trillian developers if they would use the cSip code in the new 
trillian android application, if they pick it up then maybe they could lend a 
hand with coding a seamless bluetooth backend.

Original comment by Djoneslo...@gmail.com on 20 Aug 2010 at 2:17

[GoogleCodeExporter]

I'm currently playing with my htc magic (now on Froyo Cyanogen 6) and 
bluetooth. Be aware of the fact on nexus one Froyo it is absolutely functional. 
And I'm not sure that cyanogen ROM well support bluetooth for third party 
applicaiton. But well, I'll try to see if something is possible.

As for Trillian developper... CSipSimple code is under GPLv3. As trillian is 
not opensource (as far as I know), legaly, they must not include parts of my 
code or derivated work of my code (unless they change their licence to a gplv3 
compatible one). 
But... I can bear it if they redistribute what they change and provide the 
community something more reliable.
If they want to contact me directly maybe we could work together.

Original comment by r3gis...@gmail.com on 20 Aug 2010 at 2:29

[GoogleCodeExporter]

After tests of cyanogen 6.0 RC3 : 
It is absolutely unstable ! (I don't blame Cyanogen for that because his work 
is still really impressive ... but as for BT and wifi .... really instable !)
Wifi connection goes away for some unknown reason, audio becomes choppy when 
trying to use bluetooth.

*Besides* and mainly : the standard phone application doesn't support 
bluetooth!!!
How do you want me to support Bluetooth if even the standard app doesn't 
support BT??? It clearly appear that the ROM doesn't support Bluetooth (as far 
as I can say SCO bluetooth) well.
So no way to have it functional on Cyanogen rom 6.0 for now ! And I can't do 
anything for that.... For the nexus one and htc desire on Froyo, things works 
well with CSipSimple.

Original comment by r3gis...@gmail.com on 20 Aug 2010 at 2:56

[GoogleCodeExporter]

Thanks r3gis, ill let them know.
I've also been able to secure a relationship with sipsorcery founders, to see 
if there is a way to setup SIP backend baselining and stress testing per 
individual sip provider (server side) . However that task is far more 
painstaking then it sounds.

Original comment by Djoneslo...@gmail.com on 20 Aug 2010 at 2:57

[GoogleCodeExporter]

For sipsorcery founders, interesting point let me know your progress about this 
point.

Original comment by r3gis...@gmail.com on 20 Aug 2010 at 3:02

[GoogleCodeExporter]

I'm sorry but i dont know what you mean.
The standard phone application on my Sapphire works without any issues.
Could it be your headset ? It seems you have a older run of the mill one.

Not to sound snobby, but i'm using one of the most advanced bluetooth headsets 
ever created. (the icon)
I haven't gotten a chance to try my jabra or Motorola headsets with RC3 or RC2 
yet.

I'll try and get some more information with regards to all of this and see what 
i can digg up. To the best of my knowledge Froyo and eclair both have full 
supported voice gateway support for the standard phone app.

Original comment by Djoneslo...@gmail.com on 23 Aug 2010 at 3:15

[GoogleCodeExporter]

Your handset probably support a2dp (that' I don't support yet). The one with 
which I try is a SCO handset (a jabra). And Cyanogen 6.0 RC3 doesn't support 
SCO handset at all... 

Besides, only Froyo provide an API for managing SCO BT handsets. It was 
supported since Cupcake version but only in the phone application (they use 
private API that a standard application dev should not use). For bluetooth 
a2dp, I have no device to test on. There is some method available on the 
android API that should manage that from 1.5 or 1.6 but if it behaves like 
bluetooth sco things will be more complicated.
Besides as cyanogen is not stable with bluetooth connections, I fear that even 
if I support BT a2dp, it will not solve your problem. 

Original comment by r3gis...@gmail.com on 23 Aug 2010 at 6:21

[GoogleCodeExporter]

Just for information (for those with *nexus one* and crash when handset is 
disconnected)
http://code.google.com/p/android/issues/detail?id=9503
Reporter is the owner of the sipdroid project.
I added a comment, and after investigation :
* I have a workaround for csipsimple (will be in -12-24) the backside is that 
you'll ear some blank sound in the headset even once disconnected - but at 
least it will not "reboot" (in fact it restart only some services but you get 
the boot screen) once headset or BT is disconnected + by default for now 
deactivate BT, user must click to activate it if he want.
* I'll probably commit something on the android project to fix the issue 
definitely on the android side (if android devs doesn't take my comment into 
account... commit process in android is faster - I've already contributed a 
minor update for the music app and took about 2 weeks to be validated).

Original comment by r3gis...@gmail.com on 27 Aug 2010 at 6:38

[GoogleCodeExporter]

I dont think it has anything to do with A2DP (stereo bluetooth), i did some 
(but rather quick) testing with a2dp turned off in the bluetooth connection 
settings and audio was still working as usual. I'll try another headset soon 
(one without a2dp support) to be certain.

Original comment by Djoneslo...@gmail.com on 29 Aug 2010 at 8:20

[GoogleCodeExporter]

Indeed, only SCO Bluetooth. (My comment was just for reference)
Besides, for now I only test with SCO.

Original comment by r3gis...@gmail.com on 29 Aug 2010 at 10:48

[GoogleCodeExporter]

Issue 177 has been merged into this issue.

Original comment by r3gis...@gmail.com on 29 Aug 2010 at 10:55

[GoogleCodeExporter]

Well for now i have found a bearable alternative.
It seems linphone found a workaround inside the bluetooth stacks to get 
bluetooth bearably working on older devices. They are using some kind of odd 
service hacks. The main thing i noticed with their app is> that it doesn't do 
any debugging or logging or anything fancy at all. It simply connects and runs. 
 It must chew through battery life like a monster however. I also noticed it 
keeps a constant connection and does some weird things with pulseaudio in the 
background.

So for the time being the only option we (D/S users) have is.

Linphone + Lite rom + a decent headset + a good wifi connection (2.5/3 Bars) + 
pcmu or pcma or other lite 8khz codec + pbxes sip optimization .
This will let you call the office in a pinch and let them know you're going to 
be late. I wouldn't use it to make intimate calls however, you would without a 
doubt come across looking like a jerk.

I wish i could report back better news.  Even with my own tinkering around in 
the source i haven't been able to scrub the intermittent audio issues.

We either need a super lite codec or tighter bond between the bluetooth stack 
and the headset. Which would be up to google to fix in AOSP

Original comment by Djoneslo...@gmail.com on 29 Aug 2010 at 11:19

[GoogleCodeExporter]

I would also recommend disabling the carrier radio using the following service 
code inside the default dialer app.

*#*#INFO#*#*

> Phone information > (Scroll down to the end) > turn off radio.

Thats all for now, i'll try and find out what LP does differently and inside 
the stacks, and will report back when i find out more. Have a beautiful week!

David

Original comment by Djoneslo...@gmail.com on 29 Aug 2010 at 11:24

[GoogleCodeExporter]

Good news.
Linphone has probably not commit their changes yet (I follow by far their 
changes to see if they solve this kind of annoying audio issues - as I follow 
the sipdroid devs).

So if they have something, there is chances other opensource solutions will 
have it soon ;).

Original comment by r3gis...@gmail.com on 29 Aug 2010 at 11:57

[GoogleCodeExporter]

Issue 220 has been merged into this issue.

Original comment by r3gis...@gmail.com on 20 Sep 2010 at 11:04

[GoogleCodeExporter]

Quick update : about comment 33 it seems to be fixed in android 2.2.1 !

Original comment by r3gis...@gmail.com on 28 Sep 2010 at 8:56

[GoogleCodeExporter]

Issue 435 has been merged into this issue.

Original comment by r3gis...@gmail.com on 1 Dec 2010 at 7:57

[GoogleCodeExporter]

Issue 460 has been merged into this issue.

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

[GoogleCodeExporter]

I'm running into a similar problem here trying to do this with a dect/bluetooth 
handset (at&t 92278) can can't get csipsimple to ring to the bluetooth...  I'm 
running csipsimple 0.00-16 r578 on android 2.2.1 kernel 2.6.32.0 (darkslide ROM 
on DroidX).

If I call in to the cell phone the dect handset rings, but if i dial the 
csipsimple extension it shows ringing on the phone but that's not passed to the 
bluetooth fine.

If anybody has any hints that would be great.

Original comment by mpic...@ezuce.com on 27 Jan 2011 at 5:46

[GoogleCodeExporter]

Issue 748 has been merged into this issue.

Original comment by r3gis...@gmail.com on 25 Feb 2011 at 10:28

[GoogleCodeExporter]

Latests dev releases includes automatic switch to BT SCO. Also use 
automatically 8kHz if using BT device.

Should at least configure it the best way it could. However there is probably 
still some things that could be improved. (For example I'm not sure about audio 
mode that should be used in the audio api for having it working with all 
devices and all headsets).

Original comment by r3gis...@gmail.com on 27 Feb 2011 at 7:27

• Changed title: Bluetooth support

[GoogleCodeExporter]

Sorry to bump this old issue r3gis (what's your noob friendly name ? :D) .. On 
my modest Samsung Galaxy Mini, I am able to hear the voice on the other end in 
an outgoing call on my modest bluetooth headset with A2DP but they are not able 
to hear my voice. It works however if I use the phone's built in dialer (thus 
bypassing SIP) . My phone is on Froyo .. Kernel is 2.6.32.9 .. Csipsimple 
version is r615 .. Let me know if I could help you more in this regard. I tried 
Linphone 1.1.4 and it works (ppl can hear my creepy voice) but the quality is 
poor and I really dont feel at home using that software ...

And btw a big hearty thanks to the developers connected to this wonderful piece 
of software. 

Original comment by beyond.h...@gmail.com on 3 May 2011 at 4:49

[GoogleCodeExporter]

Nightly build may help. See the wiki page about how to install nightly.

At least nightly will configure the app properly so that frequency will be 
compatible with bluetooth headset and will automatically turn it on when 
communication is established.

However keep in mind that bluetooth is available a clean way on the android os 
for third party apps only after 2.2.1. Before this version all we can get is 
some hackful thing that will almost every time result in a very bad audio 
quality.

Original comment by r3gis...@gmail.com on 3 May 2011 at 6:59

[GoogleCodeExporter]

Hmmm .. Installed nightly but no joy .. The interface looks quite polished 
though .. Kernel 2.6.32.9 means Android 2.2.2 is it not ?
Nevertheless, I can still use my other headset to make calls while the 
developers work on integrating the features .. Thanks for the response though 
.. :)

Original comment by beyond.h...@gmail.com on 4 May 2011 at 10:05

[GoogleCodeExporter]

I'm running the latest nightly build (r830), but, after all this time, the 
bluetooth mic handling is still pretty useless. Everything I speak sounds 
incredibly distorted to the other party. The blueotooth speaker (what I hear) 
is fine, though. I'm running Froyo (kernel 2.6.32.9) on my Motorola Defy. 
Please, r3gis, try to fix this already old issue for good. Nevertheless, I 
there seems to be no problems with the Android bluetooth stack, because the 
same bluetooth headset works flawlessly on normal phone calls.

Original comment by casou...@gmail.com on 6 May 2011 at 4:31