It works, but is wonky as hell - mostly depends on the combination of your BT adapter and the particular device you want to connect to. I'm using bluez infra plus blueman for 'frontend' - no DE for me (i3+assorted stuff). Audio routing via pulseaudio. I have Lenovo x220 here, and my experience so far is: • Bose SLIII - works well (would be very sad if it didn't) • H/K Onyx Studio - works well • Blaupunkt BT20 - wonky:) mostly because it presents itself as 4 devices Generally my impression is that if stuff exposes just the 'Audio Sink' interface it's fine.
For stuff like the Blaupunkt which is a Headset+Handsfree+Audio Sink+Serial Port it's basically 'turn everything off and on again until it works as it should'. Hope this is at least a bit useful:D • • • •.
I am able to make it work but every time I returned from suspend there is a possibility that it won't work anymore unless I remove all paired device, reboot several time my bluetooth device and play with blueman-manager long enough that I will stumble accross a combination of manipulation that would eventually make the sound working. The state of the bluetooth stack makes me think of WiFi back in 2008 before mac80211 appeared, it is random, device dependant and you don't really know what to expect.
The following are instructions for connecting a Bluetooth device for serial communication on Arch Linux using BlueZ 5.31. Prerequisites The following packages are required: • bluez: bluetoothd • bluez-utils: bluetoothctl, rfcomm Pair • Start daemon: systemctl start bluetooth • Pair using bluetoothctl: power on agent on scan on. Scan off pair • Create serial device: rfcomm bind 0 You should now have /dev/rfcomm0. Unpair • Remove serial device: rfcomm release 0 • Unpair using bluetoothctl: remove power off • Stop daemon: systemctl stop bluetooth Troubleshooting Check rfkill list to make sure that the Bluetooth device is not blocked.
This post is no more updated, please read my two new posts: Connect Bluetooth Headset To Raspberry Pi 3 (AD2P only) Connect Bluetooth Headset To Raspberry Pi. Sep 25, 2013. I seem to have gotten this working now. Bluetooth seems a bit finicky. I'm recapping my steps in full in case someone else finds it useful (though its pretty much what I tried initially). This is for Android JB (4.2.2) on a Nexus 4 and Arch Linux 3.6.7-1, with bluez 4.101 on Gnome 3.6 (w/ gnome-bluetooth).
Awesome guide! It helped me out just perfect. If I may add a few things for people reading it: • for me the bluetooth service was not enabled to start on boot, nor was the rfcomm module loaded. Surprisingly rfcomm bind. Command doesn't spit errors in that case - just exits and doesn't create the serial port. • Once you have paired a device it will be remembered by the core bluetooth module. So after reboot (host and peripheral) you don't have to do the bluetoothctl commands - just go to step 3 (rfcomm bind. Omnisphere Challenge Code Keygen Download No Virus. ) and when you open the serial port it will connect.