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.
@afiestas
found it bluedevil-monolithic is package that shows the icon.
also note that I had kded4 started just in case.
[...] ansluta. Att skicka filer från datorn gick däremot bra. Men så ikväll, efter att ha läst denna artikel, och tittat under Dependencies insåg jag vilket paket jag saknade: obexd-client. Fast det [...]
Hi,
This is looking good! I managed building and installing bluedevil but it looks like I haven’t installed it properly. Some symptoms:
1) I’m not sure if it is supposed to start automatically but it doesn’t (running bluedevil-monolithic, as pointed out by Cae, seems to do the job). (I’m on KDE 4.5.1)
2) kcmshell complains about missing modules “bluedeviladapters”, “kcm_bluedeviladapters”, “kcmbluedeviladapters”, “bluedevildevices”, and more like that. Running “locate” reports .so files in /usr/local/lib/kde4/ and .desktop files in /usr/local/share/kde4/services/.
3) Browsing bluetooth:/ in konqueror or dolphin says the protocol is not authorised/invalid (just like it would if I typed totallyrandomstring:/).
4) If I select my phone in the menu (just under “Known devices”) and select “Browse device” it just shows a blank dolphin window. Copy-pasting the address (obexftp://something/) into another window triggers that the invalid protocol error again.
5) My phone sees my computer, and Send file from my computer to my phone works, but attempting to send something from my phone to my computer just says “connection failed” on my phone. But this one might be an error at the bluez level, correct?
What I did:
I did a git clone of bluedevil and libbluedevil, then cmake and make install for both, that all completed without errors. I removed kbluetooth, thinking that might create conflicts, and rebooted. I then ran bluedevil-wizard to select my phone, and that appeared to work fine.
Any ideas?
hi, i’m using your program and i have to say that the work you’ve done is really good. I’m a native spanish speaker, but i know a bit of english, so i can help translating.
I’ve tried this on Kubuntu beta, and this is impressive leap to future. However, I’ve a slight issue. I have Nokia BH-604 headset which supports both a2dp and headset profiles. It seems that when I pick the headset device as preferred in kde multimedia settings and try to play music, the headset profile is being used. Are there are any workarounds, or things I can check?
Exactly the same issue here with a BCK-08. This result to a very poor music quality.
BTW, Many thanks for this software!
Will be fixed in the next version (1.1), which in theory will be released a few weeks after 1.0 (we’re in feature freeze now).
Thanks for the reporting! and please use http://bugs.kde.org so we do not forget to implement it.
Seems that you miss to set the right prefix for your environment, CMAKE ../ -DCMAKE_INSTALL_DIR=/usr for exmaple, try it and then if you still have problems report them to http://bugs.kde.org
Thanks.
HOLY CRAP, Well done! This app and the libs are great! Clear to use and reachable through system settings. Thank you for this!
It depends on the device, but if it doesn’t have a way to introduce the pin you should just wait.
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?
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
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.
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!
If you use pulseaudio you can switch between profiles with a tool such pavucontrol.
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
Please, can you fill bugs/wishes at http://bugs.kde.org ? that is the only way we can keep track of them.
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
BlueDevil not found my bluetooth adapter: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Please, fill a bug at bugs.kde.org so we can track the problem down.
Thanks.
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
I’m quite sure that’s not possible with BlueZ (the current Linux Bluetooth Stack) :/
There are planes for implement suport of audio devices (auriculars, micros, etc) like Blueman?
Thankyou
What exactly do you mean? we already support headsets and micros (build in those headsets)
[...] en 3 proyectos: Kamoso: Una aplicación para divertirse tomando fotos y videos desde una webcam. BlueDevil: Integración de la tecnología Bluetooth en KDE. Solid: Una subcomunidad dentro de KDE, enfocada [...]
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
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
[...] current series distributed by Eric (4.6.3) added the bluedevil bluetooth stack which works nicely. Make sure to read Eric’s notes about the release as they have much more [...]
@afiestas
Done, thanks.
[...] bluedevil of course – the new KDE bluetooth stack which is based on the BlueZ libraries already present [...]
[...] bluedevil was added – not a dependency as such, but rather additional functionality for your KDE [...]
[...] as “KDE extragear”, compared to Slackware’s own version of KDE: I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the [...]
[...] three useful new applications, compared to Slackware’s own version of KDE: I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the [...]
[...] three useful new applications, compared to Slackware’s own version of KDE: I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the [...]
[...] the KDE core set. They are new, compared to Slackware’s own version of KDE. I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the [...]
[...] the KDE core set. They are new, compared to Slackware’s own version of KDE. I already added bluedevil to my 4.6.5 package-set. Bluedevil is the new KDE bluetooth stack with a nice GUI, based on the [...]