| 2017-05-17 20:37:14 |
Doug Morse |
bug |
|
|
added bug |
| 2017-05-17 20:46:22 |
Doug Morse |
description |
Pairing and coupling to Amazon Echo works, but 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 bus
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 |
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 bus
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 |
|
| 2017-05-17 20:46:39 |
Doug Morse |
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 bus
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 |
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 |
|
| 2017-05-18 01:54:23 |
Daniel van Vugt |
marked as duplicate |
|
1582213 |
|
| 2017-06-06 03:57:09 |
Daniel van Vugt |
removed duplicate marker |
1582213 |
|
|
| 2017-06-06 03:59:34 |
Daniel van Vugt |
tags |
amd64 apport-bug xenial |
a2dp amd64 apport-bug xenial |
|
| 2017-06-18 00:55:11 |
Launchpad Janitor |
bluez (Ubuntu): status |
New |
Confirmed |
|
| 2017-07-12 21:54:12 |
Michael Mueller |
bug |
|
|
added subscriber Michael Mueller |
| 2017-08-16 19:59:13 |
Charles Inwald |
bug task added |
|
bluez |
|
| 2017-08-16 19:59:29 |
Charles Inwald |
bug task deleted |
bluez |
|
|
| 2017-09-14 00:11:20 |
Mark Tomich |
bug |
|
|
added subscriber Mark Tomich |
| 2018-02-08 21:02:06 |
Preston |
attachment added |
|
pavucontrol showing output levels https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5051465/+files/screenshot-2018-02-08-160123_871x277.png |
|
| 2018-09-21 07:01:06 |
Daniel van Vugt |
tags |
a2dp amd64 apport-bug xenial |
a2dp amd64 apport-bug bionic xenial |
|
| 2018-11-29 09:22:00 |
review |
attachment added |
|
bluetooth status - ubuntu and echo https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5217241/+files/bluetooth_echo.png |
|
| 2018-11-29 09:23:20 |
review |
attachment removed |
bluetooth status - ubuntu and echo https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5217241/+files/bluetooth_echo.png |
|
|
| 2018-11-29 09:34:56 |
review |
attachment added |
|
bluetooth status - ubuntu and echo https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+attachment/5217251/+files/bluetooth_echo2.png |
|
| 2020-04-15 22:51:00 |
Adam Skalicky |
bug |
|
|
added subscriber Adam Skalicky |
| 2020-06-23 11:00:52 |
pico.dev |
bug |
|
|
added subscriber pico.dev |
| 2021-09-28 03:28:53 |
Daniel van Vugt |
bug task added |
|
pulseaudio (Ubuntu) |
|
| 2021-09-28 03:28:59 |
Daniel van Vugt |
pulseaudio (Ubuntu): status |
New |
Confirmed |
|
| 2021-09-28 03:31:31 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
| 2021-11-07 17:58:50 |
Rodrigo |
bug |
|
|
added subscriber Rodrigo |
