This error remains unsolved, amazon echo cannot be paired, as an input and output device. It only works with one of the two
-- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
