#51 Bluetooth support

[Anonymous]

Originally created by: Djonas2...@gmail.com
Originally owned by: r3gis...@gmail.com

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.

[Anonymous]

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

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.

[Anonymous]

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

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.

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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.

[Anonymous]

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

Just for information (for those with *nexus one* and crash when handset is disconnected)
https://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).

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

Issue 177 has been merged into this issue.

[Anonymous]

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

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

[Anonymous]

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

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

[Anonymous]

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

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

[Anonymous]

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

Issue 220 has been merged into this issue.

[Anonymous]

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

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

[Anonymous]

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

Issue 435 has been merged into this issue.

[Anonymous]

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

Issue 460 has been merged into this issue.

[Anonymous]

Originally posted by: mpic...@ezuce.com

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.

[Anonymous]

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

Issue 748 has been merged into this issue.

[Anonymous]

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

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

Summary: Bluetooth support

[Anonymous]

Originally posted by: beyond.h...@gmail.com

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.

[Anonymous]

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

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.

[Anonymous]

Originally posted by: beyond.h...@gmail.com

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

[Anonymous]

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

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.

[Anonymous]

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

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.