Tag Info

Hot answers tagged

2

There's an option in /etc/bluetooth/audio.conf called autoconnect=truewhich is hashed out. I found enabling this option by removing the # and got things connecting properly with my bluetooth headset


1

Long time I was looking solution and finally helped me that link: http://ubuntuforums.org/showthread.php?t=2246613 Ubuntu 14.04 Audio sink problem to Logitech Wireless Adapter Hello, jcmoriaud. I had this problem recently as I bought a bluetooth speaker and attempted to connect to it with my laptop. It kept giving me "Connection Failed: Stream ...


1

Ubuntu 13.10 uses bluez 4.98, 14.04 and 14.10 uses 4.101 Both versions were compiled with the same option (--localstatedir=/var) I'm using 14.04 and the files are there and if I remove or add a device the /var/lib/bluetooth/(myadapteraddress)/linkkeys file is updated accordingly. I made a test on a 14.10 system, I added a BT device and the ...


1

Unlike MPD in system wide mode PulseAudio is running in userspace. This means, all pulseaudio settings including Bluetooth discovery and providing a Bluetooth audio sink is done from a user session. The MPD daemon, when running system wide, is unable to access Pulse Audio devices running in a user session. As it is in theory possible to run Pulse Audio in ...


1

On Linux, lightblue internally uses the PyBluez library, which doesn't currently allow a socket to opened on a specific HCI device. PyBluez internally uses the Linux bluetooth sockets functionality, so it depends on whether that allows sockets to be created for a specific HCI device. My guess is that it doesn't, else this functionality would have been ...


1

If you don't have a hardware switch to turn it on, I feel that the only solution is via Windows because sometimes hardware deactivated in Windows does not appear on other OS. In my case I had to install Windows 7 on new created partition (10 GB), install all neccesery drivers for Bluetooth and turn it on there. Then reboot to Ubuntu to check if the ...


1

The issue you are facing is due to a bug in older versions of the Linux kernel, < 3.15. The bug report can be found here. To solve the problem, enter the following commands - cd /lib/modules/$(uname -r)/kernel/drivers/bluetooth/ cp ath3k.ko ath3k.ko.orig cp btusb.ko btusb.ko.orig sed -e 's/\xf3\x0c\x05\x30/\xf3\x0c\x05\xe0/g' ...


1

Try with the below command and install the bluetooth genome again and then check whether you are able to connect to the bluetooth device, sudo apt-get install bluetooth blueman bluez-hcidump bluewho python-bluez bluez-tools Hope this helps.


1

Support for Atheros AR5BBU22 is in the Kernel since 3.6.15 but additionally the proprietary firmware has to be installed on the system for bluetooth to work. It is available in the package linux-firmware (on ubuntu; resp. firmware-atheros on debian, non-free).



Only top voted, non community-wiki answers of a minimum length are eligible