KDE-Bluetooth for KDE 4: first test release

kde-logo-official
One of the main 3rd party packages for KDE is the KDEBluetooth suite. It is the graphical interface to Bluetooth for KDE. The KDE 4 port was now released in a first test version.

Managing Bluetooth on Linux is actually pretty easy – bluez, the Open Source bluetooth stack is certified by the Bluetooth group itself and is therefore fully supported. However, bluez needs a GUI to be used by users. For KDE, KDEBluetooth delivered a well working solution for years.

With the release of KDE 4 the KDE 3.5 version of KDEBluetooth can of course be used, but a KDE 4 suite would be better integrated. The porting efforts took some time, but now the first version is there: KDEBluetooth4, version 0.1 (also see the project page at kde-apps.org).

While I currently have a KDE 4.1Beta running, that machine does not have bluetooth, so I can’t test it myself right now. However, the release notes on kde-apps.org list the features (and has screenshots), but also the yet missing points. And indeed almost all basic functions are already implemented:

  • Trayicon to manage all functions
  • Passkey and Authorization Agent to handle requests from remote devices
  • Bluetooth Adapter configuration
  • Bluetooth Device-Manager
  • Bluetooth Device Wizard, to add new Devices
  • KBlueLock, to lock your screen, when your mobile phone is out of scope
  • Send Files to remote devices (obex-data-server)

Quite nice for a first test release! However, currently the kio-browsing is still missing. Also, support for requesting capability information (for example if it is an audio device or a pointer device) are missing as well as support for audio devices. From my point of view the most hurting point is that there is currently an obex-data server missing so that files cannot be received. But that is only a matter of time.

In case you run a recent KDE 4svn version, give it a test! As usually the developers welcome any kind of (polite) feedback and of course any help development wise.

10 thoughts on “KDE-Bluetooth for KDE 4: first test release”

  1. It looks like kdebluetooth4 doesn’t use Solid for communicating with the hardware and is doing it instead directly with BlueZ.
    Is there any reason doing so? Doesn’t Solid provide all necessary features yet?
    Are there any plans going to use Solid for it? I’d love to see having the efforts brought together.

    Anyways, kdebluetooth is really great – going to try it now as it looks in KDE4 now.
    Thank you for porting it.

    Regards, Elias P.

  2. Nice, I already missed that.🙂

    But why not make it a part of the official KDE? (in kdenetwork?)

    Has someone asked the devs of kde bluetooth asked about this?

  3. Hi!

    One thing that likes me, but don’t know if is implemented, is the posibility to hide the tray icon when no bluetooh adapter is up. This way, when i press fn+f10 the thay icon appears, and when preesed again, it disappears.

    Just an idea.

    Bye!

  4. @Bernhard: this is probably an intermediate step, so they can get the functionality out to the users and then concentrate on splitting it into a Solid backend and a frontend using Solid.

    So basically working on the core problem first and doing nice KDE integration afterwards

  5. eliasp, if I get Kevin’s comment right it will in the end sit on top of solid… but I’m not sure right now.

    shiny, you are of course right – but an obey server would be cool as well😀

  6. @eliasp: kdebluetooth4 is not a port of kdebluetooth from KDE3. It is a complete rewrite and working on top of solid using its solid-bluez api. There is no direct bluez communication like it was in kdebluetooth3.

  7. Kdebluetooth4 does not work on Kbuntu. It’s documented in their bug tracker. As soon as bluetooth is supported as well as kppp then Kubuntu will be a viable option for mobile users.

  8. I tried it today after I noticed an update. I can now get kbluetooth to sync with my logitech bluetooth mouse without any problems.

    It disconnects without problems, and reconnects automatically (although I haven’t rebooted yet to test if the connection will persist – I’m sure it will.)

    This is a really welcome milestone for the kbluetooth guys who struggled with a lot of criticism for the last six months. Thanks guys for all of the hard work.

    I have three questions:
    1) How is the audio device development going? I would loveto use my bluetooth headphones;
    2) How will the system work for connecting to non input/non audio devices?

    J

Comments are closed.