#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

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.

Labels: -Type-Defect Type-Task
Owner: r3gis.3R
Status: Accepted

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

HI.

i could send you a spare headset if that would help

[Anonymous]

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

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

Thanks !

[Anonymous]

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

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!

[Anonymous]

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

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 :(

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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.

Status: Started

[Anonymous]

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

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 ?

[Anonymous]

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

????

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

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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?

[Anonymous]

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

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

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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

[Anonymous]

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

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.

[Anonymous]

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

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.