I had the same issue with Device or resource busy and the same problem when Alexa says that is connected to pc and no sound - but it's because your pc becomes bluetooth speaker for Echo, in that state pacmd list-cards shows: ... a2dp_source: Przechwytywanie o wysokiej dokładności (źródło A2DP) (priority 20, available: yes) a2dp_sink: Odtwarzanie o wysokiej dokładności (odpływ A2DP) (priority 40, available: no) off: Wyłączone (priority 0, available: yes) ...
Finally I got connected Echo as bluetooth speaker and it's working now after reboot too. Steps to get Echo working as bluetooth speaker that works for me: 1. Echo doesn't know anything about bluetooth connection - so first forget your device in Alexa App, and other devices. 2. Reinstall your pulseaudio-module-bluetooth: for fedora: sudo dnf reinstall pulseaudio-module-bluetooth 3. Uncomment MultiProfile in /etc/bluetooth/main.conf and set it to multiple. (not sure if it is nesesery) 4. If you made modifications do: sudo systemctl daemon-reload sudo service bluetooth restart 5. Check if A2DPSink and source is registred with sudo service bluetooth status 6. If not do: pacmd load-module module-bluetooth-discover 7. Reset adapter: sudo hciconfig hci0 reset 8.Check if adapter works good: (my class is 0x1c0104) hciconfig -a 9. Now unload pulseaudio modules: pacmd unload-module module-switch-on-connect pacmd unload-module module-switch-on-port-available Now open terminal and run bluetoothctl, and in bluetoothctl type: default-agent remove ECHO_MAC (if you have saved it before) Now tell to Echo "Alexa, bluetooth" and after "Searching" Echo should show in bluetoothctl so connect it: connect ECHO_MAC exit After that bluetoothctl should show that connects to echo and pairs it, then pacmd list-cards will show a2dp_sink available yes. After reboot when you want to connect, don't say anything to echo, just run bluetoothctl and connect echo. If after connect bluetoothctl doesn't show anything about pair and connect, you can try to manualy connect to a2dp_sink with: dbus-send --print-reply --system --dest=org.bluez /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX org.bluez.Device1.ConnectProfile string:0000110b-0000-1000-8000-00805f9b34f Replace XX with your echo MAC. Fedora 29, BlueZ 5.50. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1691556 Title: Can't send audio to Amazon Echo via Bluetooth Status in bluez package in Ubuntu: Confirmed Bug description: Pairing and coupling to Amazon Echo works, but no sound is heard. I believe the issue is related to the fact that Amazon Echo is paired as a handset (i.e., speaker + microphone) rather than just as a speaker. I believe the critical error is found in a dmesg line such as: Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy as I describe in the askubuntu.com discussion at: https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo- via-bluetooth I have clarified there my thinking and the steps I've taken thus far on this issue, which includes trying debug bluetooth per the Ubuntu wiki page which describes how to do so. This is probably an upstream issue, as Mike H-R has commented there that the problem also occurs on ArchLinux. I and a few others would like to get this resolved, and I am happy to help (I'm a software developer). However, at this point, I'm not sure how to proceed without some assistance. I suppose I could report it to Debain, but I've only ever used Debain vis a vis Ubuntu, so I thought it best to start here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 17 22:27:59 2017 InstallationDate: Installed on 2015-12-26 (507 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-504 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr: hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: DC:53:60:97:55:17 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0 TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
