Official Linux Bluetooth protocol stack
Archive for the ‘Release’ Category.
This release fixes a lot of minor issues found during the first day of testing at the UPF in Budapest. Big kudos to the Nokia Maemo team 
The biggest fix comes for an issue in our SDP server that was unable to match protocol UUIDs for the service search and service attribute search requests. This bug has been around since forever, but we finally found and fixed it.
This release ensures that mice and keyboards are automatically marked as trusted. It also adds support to bluetooth-sendto to use the new obex-client if available.
This release fixes an issue with the SCO server socket and an issue with uninitialized reply messages of some GetProperties methods that could have caused random crashes.
The issue with the SCO server socket caused some connection issues with headsets. If you still see these issues, please report them on the mailing list.
This release adds the obex-client application. It is a D-Bus enabled OBEX client daemon that allow easy integration of OBEX based Bluetooth profiles.
An example send-files (written in Python) demonstrates how easy it is to send files via Bluetooth and get status updates on the progress.
With this release the location of the binaries now depend on libexecdir setting given to configure. It will either default to /usr/libexec or can be overwritten to be /usr/lib/obex in some cases. Also the names of the D-Bus service files changed.
This is a point-release before the upcoming UnPlugFest in Budapest next week. It contains various updates to the handsfree support using the dummy hardware emulation.
Bastien and I talked about adding support for the kill switch subsystem to either the applet or the properties application and after Stefan was asking for the “off” option, I sat down and added support for power switches to the properties application.
The implementation uses HAL for triggering the kill switch, but to be quite honest, the support in HAL is just plain broken. It works, but that’s it!
HAL will not send out notifications when other applications change the status of your kill switch. Not to mention what happens when the system contains a physical kill switch. This means that the status indication of the kill switch option might not be correct. The lifetime of the properties application is normally pretty short and so it is acceptable (for now), but still far from perfect.
Also the all Bluetooth kill switches seems to have no real parents. This means there is no indication which device will be affected by the exported kill switch.
The latest bluez release adds more properties and signals that allow a lot of code simplification inside the user interface. This release makes heavily use of.
Please use the latest bluez release. Otherwise some functionality might fail.
In the previous release a bunch of signals were missing that the next version of bluez-gnome will make use of. Especially with the usage of the new Alias and Icon properties.