Home > KDE, Software Libre > BlueDevil, the new KDE bluetooth stack is here

BlueDevil, the new KDE bluetooth stack is here

We’re proud to announce the first release of BlueDevil, the new bluetooth stack for KDE SC.

Description:

BlueDevil is a set of components, which integrates bluetooth within the KDE SC, for example adding a system preference module (KCM), or allowing to browse the files in a cell phone from you favorite file browser.

The list of already implemented components is:

  • System preference module (KCM) to configure all the options regarding Bluetooth (also fully activate/deactivate it)
  • Integration with the KDE input/output system (KIO), which allows to discover and explore all bluetooth devices around from your favorite file browser
  • A wizard to pair your devices, and connect directly to the compatible services, such input (mouse, keybaord, Wiimote) and audio (headsets, phones)
  • Systray application integrated with the last KDE SC 4.5, from where all BlueDevil actions can be done (disconnect devices, send files, configure…)
  • Daemon to listen incoming petitions, for example to receive files, or to introduce a requested PIN.

Dependencies:

  • bluez (to get it working)
  • obex-data-server (for receiving files, and KIO’s)
  • obexd-client (for sending files)
  • KDE SC 4.4 or greater
  • PulseAudio, or a proper configured Alsa (with the bluetooth hook)

Errata:

  • When using kio_obexftp in dolphin on a KDE SC 4.4, some times it won’t load the content because more than one kio is launched at the same time and it is not supported by the backend (Tip: Disable the previews or use konqueror)
  • In KDE 4.5 SC, some times when a device is removed, the systray is not correctly updated (Seems to be a bug in QDBusMenu)
  • When trying to open a file from a bluetooth device, the progress gets stucked at 99%

Target Audience:

This release should be stable enough to be used by everybody, but we’re looking specially for advanced users with “compiling skills” so we can get quick feedback and fix as many bugs as possible. if you are Interested send an email to alex (at) ufocoders dot com.

Internationalization:

Currently BlueDevil is not ready to be translated (the strings are not final), and we’re looking for native English speakers who can help us with the strings, interested people send an email to alex {at) ufocoders.com

Special thanks to (in no particular order):

  • BlueZ developers and community for their help during the development (and patience)
  • David Faure for his help during the development and infinite patience talking about KIO’s
  • To ufocoders for sponsor half of the development

Obtaining the code:

To get the tag:

git clone git://gitorious.org/bluedevil/bluedevil.git; git checkout v1.0-rc1

In the next release we’ll provide the proper tarball.

Categories: KDE, Software Libre Tags:
  1. December 22nd, 2010 at 01:55 | #1

    It depends on the device, but if it doesn’t have a way to introduce the pin you should just wait.

  2. December 23rd, 2010 at 16:35 | #2

    Splendid! I just removed the old kbluetooth 0.4.2 program and emerged bluedevil on my Gentoo system and it integrated beautifully. My headset was paired within a few clicks (as it should be) and connected to alsa. Kudos!

    Now I need to figure out a way to easily switch my sound system output over to the new alsa device, any hints how I can do this from within KDE 4.5?

  3. Trian
    December 24th, 2010 at 13:14 | #3

    I’m trying to figure this one out, so any help will be appreciated.

    I’m trying to pair a Logitech V470 mouse to my opensuse/kde installation.
    I reach the “BlueDevil Remote Device Wizard”, where I do see my mouse, I select it and then I press “Next”. From there on, whichever option I may follow, I am presented with a number (0000 or whatever I may type in) and I’m supposed to “Introduce the following PIN in your device”.

    any help will be appreciated

  4. giaur
    December 26th, 2010 at 02:07 | #4

    Browsing devices still does not work. I’ve added bug report – it was very long ago… and I’m really tired – latest version, and still this feature sometimes works and sometimes not (nothing happens when I try to use it – empty window and no folders visible at all, after I logout and login to kde again, magically it starts to work… or not).

    I really have no idea what’s so difficult there and what’s the reason you can’t fix this, but – this is only what I use bluetooth for, so there is only one thing I can do – switch back to blueman and say, that blueman is rather unstable and not very useful for me. Sorry.

  5. John Suykerbuyk
    December 27th, 2010 at 16:31 | #5

    I’m using an Altec Backbeat 902 headset that supports Audio Sink, a two way headset service, and buttons (input service).

    Problem is, when I pair with the device via bluedevil, only the headset service connects (the high quality Audio Sink service does not appear to be visible).

    With the old KDE blue tooth tool chain, when pairing, it would default to the two way headset service, which I would then disconnect, and then reconnect with the high quality Audio Sink service.

    Is there anyway I can get bluedevil to ignore or skip over the headset service? I primarily only want to use the high quality Audio sink service.

    Are there any command line tools that can be used to diagnose or display the device topology?

    bluedevil-audio yields the following version info:
    Qt: 4.7.1
    KDE Development Platform: 4.5.90 (4.6 RC1)
    Bluetooth Audio Helper: 0.1

    Thanks!

  6. December 27th, 2010 at 16:56 | #6

    If you use pulseaudio you can switch between profiles with a tool such pavucontrol.

  7. promeneur
    January 26th, 2011 at 18:50 | #7

    i tested bluedevil 1.0.1
    Mandriva 2010.2 32 bit
    qt 4.7.1
    kde 4.5.5
    nokia 5800 xpress music

    1. browsing with dolphin
    - scanning through the folder tree ok
    - deleting a file ok
    - copy from/to my pc ok
    but
    -no preview
    this is a pb when i want to search and select a photo
    - when i quit dolphin
    i see the connection between my pc and my smartphone is not terminated
    then
    i must close the connection in my phone

    2. sending a file to my smartphone

    if my smartphone is hidden (but registered)
    strangely bluedevil discovers bluetooth devices instead of supplying to me the list of the registered device
    then
    i cannot choose my smartphone
    then
    i click on “suivant”
    then
    i see knotify turning and turning but no transfert

    i assume there is no connection

    if my smartphone is not hidden
    then
    i can choose it
    then
    i click on suivant
    then
    i see knotify turning and turning without any transfert.
    this time the progess bar indicate about 98 % transfert
    but in my phone i do not see any connection

    3. receiving a file

    i send a file with my smartphone but it can’t connect to my pc
    my smartphone says “connection failed”

    addendum
    receiving/sending a file works well with kbluetooth

  8. January 27th, 2011 at 18:43 | #8

    Please, can you fill bugs/wishes at http://bugs.kde.org ? that is the only way we can keep track of them.

  9. leslie88
    February 14th, 2011 at 22:40 | #9

    Hi!
    vlad@debian6kde:~$ lsusb
    Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 004: ID 13fe:1e00 Kingston Technology Company Inc.
    Bus 002 Device 003: ID 0457:0151 Silicon Integrated Systems Corp. Super Flash 1GB / GXT 64MB Flash Drive
    Bus 002 Device 002: ID 03eb:0902 Atmel Corp. 4-Port Hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 003: ID 0458:705e KYE Systems Corp. (Mouse Systems)
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    When I try “Configure adapters” :

    “No adapters found. Please connect one.”

    Debian 6.0 KDE

  10. April 15th, 2011 at 19:57 | #10

    BlueDevil not found my bluetooth adapter: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

  11. April 15th, 2011 at 22:31 | #11

    Please, fill a bug at bugs.kde.org so we can track the problem down.

    Thanks.

  12. André Vande Vonder
    April 25th, 2011 at 18:05 | #12

    Hello,

    I just finish to install KDE 4.6.2 under my Gentoo. BlueDevil are very very splendid but …..
    Where I will find information about ‘private’ device.
    I have some user’s on my system and thus all of them see a device of each other users !!
    For security and private usage (by user) where I set this ?

    Thanks

  13. April 27th, 2011 at 11:10 | #13

    I’m quite sure that’s not possible with BlueZ (the current Linux Bluetooth Stack) :/

  14. Deus mortus est
    April 28th, 2011 at 19:02 | #14

    There are planes for implement suport of audio devices (auriculars, micros, etc) like Blueman?

    Thankyou

  15. April 30th, 2011 at 22:32 | #15

    What exactly do you mean? we already support headsets and micros (build in those headsets)

  16. May 22nd, 2011 at 02:09 | #16

    Alex, hola!

    I recently got a new machine and am trying to get bluedevil working, but have not yet succeeded. Below are all the details.

    The bottom line is that the software installs, the menus function, the system recognizes the BT adapter, but the machine cannot find other devices, and other devices cannot find this computer.

    + The machine is HP TouchSmart tm2t-2200
    + The OS is openSUSE 11.4
    + The OS-installed version of BlueDevil was 1.02 (which didn’t work) but I have now added repositories and used YaST to install version 1.04-3.1.
    + This same Bluedevil version works just fine on my old machine with the same operating system, so it must be the difference in hardware?
    + YaST reports the hardware as
    Vendor: usb 0x148f “Ralink Technology, Corp.”

    Any ideas?

    Thanks in advance, kind regards.

    Saludos, Andy Lavarre
    ===================== Details =====================
    YaST reports:
    38: USB 00.0: 11500 Bluetooth Device
    [Created at usb.122]
    Unique ID: JPTW.tGttqvOhWG9
    Parent ID: FKGF.0j9+vWlqL56
    SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0
    SysFS BusID: 2-1.3:1.0
    Hardware Class: bluetooth
    Model: “Ralink Bluetooth Device”
    Hotplug: USB
    Vendor: usb 0x148f “Ralink Technology, Corp.”
    Device: usb 0×1000
    Revision: “52.76″
    Driver: “btusb”
    Driver Modules: “btusb”
    Speed: 12 Mbps
    Module Alias: “usb:v148Fp1000d5276dcE0dsc01dp01icE0isc01ip01″
    Driver Info #0:
    Driver Status: btusb is active
    Driver Activation Cmd: “modprobe btusb”
    Config Status: cfg=no, avail=yes, need=no, active=unknown
    Attached to: #36 (Hub)

    Bluedevil discovers it at MAC CC:52:AF:50:0D:FE

    We have it activated with modprobe btusb
    But configuring it fails with bluedevil.

    Installing the operating system on the new machine resulted in bluedevil 1.02-3.8.1 being installed. This version does not work.
    The older machine has bluedevil 1.04-3.1 installed. That version DOES work on that machine.

    I uninstalled bluedevil and searched around for repositories for the newer version. I was not able to install 1.04 because of dependency issues, but after rebooting and runnning yast2 sw_single I now found 1.04-3.1 available so I installed it. I also compared all the other bluedevil and bluez files between the two machines. I have the same files on both. But bluedevil does not work on the new machine although it does work on the old machine.

    After all of this and a fresh reboot dmesg reports:

    [ 62.418592] Bluetooth: L2CAP ver 2.15
    [ 62.418596] Bluetooth: L2CAP socket layer initialized
    [ 62.437051] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [ 62.437054] Bluetooth: BNEP filters: protocol multicast
    [ 62.542333] Bluetooth: SCO (Voice Link) ver 0.6
    [ 62.542336] Bluetooth: SCO socket layer initialized
    [ 63.295452] Bluetooth: RFCOMM TTY layer initialized
    [ 63.295458] Bluetooth: RFCOMM socket layer initialized
    [ 63.295460] Bluetooth: RFCOMM ver 1.11

  17. May 29th, 2011 at 17:52 | #17

    Hi, sorry for the late response,

    can you please report a bug at bugs.kde.org so we can track the problem? a blog is not the best place to put this :p

  18. June 7th, 2011 at 22:39 | #18

    @afiestas

    Done, thanks.

Comment pages
1 2 205
  1. July 28th, 2010 at 11:25 | #1
  2. July 29th, 2010 at 19:31 | #2
  3. July 31st, 2010 at 13:54 | #3
  4. July 31st, 2010 at 18:31 | #4
  5. August 1st, 2010 at 00:11 | #5
  6. August 7th, 2010 at 17:17 | #6
  7. August 10th, 2010 at 13:36 | #7
  8. August 17th, 2010 at 16:15 | #8
  9. September 6th, 2010 at 00:16 | #9
  10. May 2nd, 2011 at 00:03 | #10
  11. May 31st, 2011 at 15:02 | #11
  12. June 10th, 2011 at 16:52 | #12
  13. July 7th, 2011 at 17:12 | #13
  14. August 1st, 2011 at 20:01 | #14
  15. September 7th, 2011 at 22:22 | #15
  16. October 5th, 2011 at 23:46 | #16
  17. November 2nd, 2011 at 20:09 | #17
  18. December 8th, 2011 at 14:41 | #18