Thread: bluetooth woes

Here's some good news...

First, I found THE Handsfree spec. This describes in great detail how everything works. And, yes, we get access to the phonebook, as well as in-band ringtones
http://www.bluetooth.com/NR/rdonlyre...PEC_V10r00.pdf

Second, I made some progress on the re-written app this weekend. It's still in it's infancy, but it can accept as well as initiate connections to a phone (but doesn't do anything with that connection yet). Hopefully within the next few days I'll get the OK to release the utility classes I'm using, then I'll set up a Sourceforge CVS site.

Edit: The part about access to the phonebook and the in-band ringtones actually came from here: http://msdn2.microsoft.com/en-us/library/aa916242.aspx

Alex

I wish that I could help out with this, but I'm still a very newb C++ programmer. Bluetooth is about the last thing to hold me back from making a linux box for the car.

Hi!
So now a days i still lose my sco audio connection. Gentoocar said it was normal but is there any way to solve it? After reading part of the software i though that "houston we was connected " should appear.
The worst thing is that i make a phone call to my mobile phone a i get a Segmentation Fault and my sound system does not work any more.

About the coding audio after asking to Simon Vogl (author of the handsfree) i definitely agree with you to use S16_LE. I also asked about the pipe to the author and he replied "The missing pipe should raise an error but not cause any other trouble (you can replace it by ctrl=0 to set it to stdin it is used for controlling behavior only "

So basically we really do not have to worry about that.
Any suggestion what to do?

I hacked the handsfree.c code a little and stopped the sco audio connection from cutting out -- or sleeping. Unfortunately this caused a kernel oops.

After a reboot and another execution, the application never got to the code section I edited.

I may be wrong here, but it could be the case that different mobiles/cells output different integer codes for what status they are at (I assume this is GSM codes?) For instance, my Motorola Razr gives 6,3 for when the call is trying to connect, so I changed the if(which == 1 && what ==3) to 6 & 3.

After this, every outbound call I made was transmitted to the speakers. Regular Seg. faults occurred, and with me not being much of a C coder, I couldn't pin down exactly what went wrong. I'm guessing too much data is being sent to the buffer/sound card.

I've since realised that everyone on this thread and I have different goals - I was looking for the opposite thing! I wanted to have incoming calls via Skype/X-Ten/etc directed to my phone... i.e Use the actual handset as a headset. From what I've read so far, I don't think this is possible, unless the bluetooth stack on the phone has the headset profile... and I doubt that it does or it can be added easily.

For the guys making a go of this; I'd check out the source for either or both chan_bluetooth and chan_cellphone from the Asterisk. Both of these modules work very nicely. To speed up development, you could fork either if the licence permits.

I'll still check this thread and offer as much help as I can.

Best of luck.

Hmm, looks like my phone uses handsfree version 1.1 (0x0101), and headset version 1.0. And my bluetooth dongle uses handsfree version 1.1 as well.

So I guess I'll use the 1.0 spec. I'm not sure what has changed between the two but I assume 1.5 devices are backwards compatible. So far in my reading everything looks the same.

BTW my dongle is a Zonet, with a Broadcom "BCM92045DG Non-UHE" chipset.

Originally Posted by Zimans

BTW, AT+BRSF=127 is all my phone needs to feel a HF connection is established, good for just plugging random commands for testing.

Despite bluetooth being a standard, every phone behaves a little differently.

Ah, I tried that with my phone and the BRSF command alone didn't make it "connected", so I plugged in the rest of the commands from the spec ("AT+BRSF=0", "AT+CIND=?", "AT+CIND?", "AT+CMER=3,0,0,1") and that does the trick for me.

Looks like I have some more spec-reading and parser-writing ahead of me, but I feel like I'm making progress