I'm trying to use the latest bluez release, specifically 4.33.
Previously I was using a 3.x version that shipped with fedora.
I can't seem to find hcid in this new release. Has the name of the hcid daemon changed to something else ?
I also noticed that in version 4.x, libs and utils are no longer separate tarballs. Does anyone know if it's all in one tarball now which is bluez.4.xx.tar.gz.

Thanks..

-Carlos

BlueZ 3.x and 4.x are completely different code bases; they are basically different in every way.

There are no more individual daemons, everything is handled by bluetoothd. The configuration system is completely changed as well, so essentially nothing written for 3.x will work on 4.x.

On top of this, the documentation for 4.x is absolutely abysmal. Even the docs that ship with the source tarball are outdated and in some places just plain wrong.

Because of all of these changes and the poor documentation, there is very little software that will actually work with BlueZ 4.x at this point. It would be better to consider the 4.x branch a long-term project, as it simply isn't ready for full time use right now.

That being said, if for some reason you really want to try and use it, then yes everything is now bundled together. There aren't separate library and utility packages anymore.

1 members found this post helpful.

Thanks MS3FGX.

That really clarified things..
The only reason I was going to the 4.x code base is because I
couldn't get my headset to work with 3.x.
I was able to pair it up using hcitool cc 12:22:33:44:55, but after
a few seconds, the connection was lost. Subsequent pairing attempts resulted in "can't create connection. input/output error".
When I looked at hcidump everything looked fine..
Maybe I need to go back to 3.x and try it again.

Thanks again..

I have had a lot of trouble with headsets as well. I believe that headset support has been improved in the 4.x series, but since very little software supports it yet it doesn't help much...

If you are going to go back to 3.x, make sure you are using the latest version, which should be 3.36. You might also want to try connecting to a device other than a headset (if you have one, anyway) to verify that BlueZ in general is working properly.

I went back to 3.36 and for the most part I have it working.
I'm using skype to test it, but the only thing I hear when I play a test sound is white noise instead of proper sound.
Unfortunately I don't have another bluetooth device to test, but I'm pretty sure most of it is working now.

-Carlos