Release of bluez-gnome-1.1

This release brings back most applications that have been omitted from the previous release.


The bluetooth-sendto application has been ported over to the new API and the bluetooth-wizard application is now installed by default.

The support for GNOME VFS based file browsing is currently not integrated. That might follow in one of the next releases.

Release of bluez-gnome-1.0

This is the first release supporting the BlueZ 4.x D-Bus API. The support for the old API has been removed. This brings a lot of internal changes with it and thus the major version number has been increased.


Despite the fact that this version is called 1.0 it has some drawbacks. The only two applications currently ported to the new API are bluetooth-applet and bluetooth-properties. So if you are looking for file transfer support, this is the wrong release for you.

This release can be used with hcid -x from bluez-utils-3.36 or with bluetoothd from the latest bluez-4.x release. When using hcid make sure to enable the experimental support via the -x switch, because otherwise only the 3.x API will be present.

The next step is to get all the dialogs for Simple Pairing support in place. This should include support for the bluetooth-wizard and after that we will port the missing applications to the new API.

BlueZ and PulseAudio

It seems Joao Paulo have been pretty busy lately working on GSoC project: bluetooth audio support for PulseAudio, and here is a preview of his work:

As you can see PulseAudio are now able to handle Bluetooth audio devices (A2DP and HSP). There are still some missing features that we want to add, a proper wizard on BlueZ to pair/connect those devices and some bugs which we should take care before releasing the code so don’t expect it to work flawless.

To test it run:

pulseaudio -L “module-bt-device name=<name> addr=xx:xx:xx:xx:xx:xx profile=<a2dp,hsp> rate=<8000-48000> channels=<1,2>”

kudos to Joao Paulo and Lennart

SCO over USB support

The new btusb driver gets finally SCO over USB support. This allows the usage of mono headsets for VoIP calls.


Qualification FUD

It seems that commercial stack manufactures like to spread FUD (Fear, uncertainty and doubt) about BlueZ and its qualification status. Trying to eliminate the open source competition by telling customers that BlueZ can’t be qualified is just plain bad business practice and these companies are lying to you.

The truth is that BlueZ has been qualified according to the Bluetooth PRD 2.0 (and later) and has been used successful in products. The most prominent example is the Nokia N810 Internet tablet. It is based on the Maemo platform which includes BlueZ as one of its core components. If you don’t believe me, check the official qualification record by yourself.

To help qualifying BlueZ based products we split the qualification into components for the host stack (GAP, L2CAP, RFCOMM and SDP) and profile stack. Companies like Nokia, ACCESS, TomTom and others have sponsored the qualification of BlueZ components that can be re-used by others.

Current known qualification records can be found at the BlueZ qualification page and it is expected that are more products out there are using BlueZ and have successfully passed the Bluetooth qualification.

If there exist any questions when it comes to BlueZ qualification, feel free to mail me. You find my email address in the source code.

Release of libgdbus-0.2

This version switches to gtk-doc for API documentation instead of Doxygen. It allows an easier and a lot cleaner way for creating and publishing documentation.


Release of libgdbus-0.1

The libgdbus is a helper library to make it easier for system daemons using GLib to integrate with D-Bus. It provides convenient functions for registering interfaces, signals and properties and handles all the introspection details. It also provides a simple API to listen NameOwnerChanged or any other signals without getting into D-Bus low-level details.


Release of bluez-4.1

Unfortunately the 4.0 release was more like a brown paper bag release. It didn’t include the compat/sdp.h header file and thus building some of the legacy applications became impossible. To make it easier for the package maintainers to perform the transition from 3.x, here comes a new release that fixes it.


This release also includes two patches that should have been already included in the 3.x series, but for some reasons slipped through the net. They should improve the A2DP performance when using ALSA and allow PAN/BNEP to pass qualification testing.