[Touch-packages] [Bug 1710941] Re: Bluetooth stopped working after update
Thanks Daniel. Rolling back to kernel 4.4.0-87-generic #110-Ubuntu SMP seemed to fix the problem. Upgrading to 4.4.0-91 also seemed to cause other problems: My system started overheating, eventually slowed to a crawl (i.e., over a matter of minutes after each reboot slowed to the point of being unresponsive), and I saw 4 instances (one for each core, I presume) of kidle_interrupt, which I had never seen before. I notice that 4.4.0-91 is no longer showing up as an update in the repos for 16.04. For what it's worth, I also downgraded libgd3 to version 2.1.1-4build2, as it also upgraded around the same time as my recent kernel updates (-87 and -89, but I don't think I ever rebooted into -89). -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 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:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 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/1710941/+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
[Touch-packages] [Bug 1710941] [NEW] Bluetooth stopped working after update
Public bug reported: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 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:6896 acl:46 sco:0 events:294 errors:0 TX bytes:4254 acl:32 sco:0 commands:156 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1710941 Title: Bluetooth stopped working after update Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to Bose Soundlink II have been fine for years. Applied a few new updates in the last day or two --- system was generally up to date, I don't often wait more than a week or so --- and now I can no longer connect. Removed the device and re-paired just fine, although the speaker did not connect as it usually does after the pairing (i.e., it stayed in pairing mode). Messages in syslog: Aug 15 20:32:07 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:07 n1 bluetoothd[1075]: GLib: Source ID 276 was not found when attempting to remove it Aug 15 20:32:11 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:32:42 n1 bluetoothd[1075]: GLib: Source ID 287 was not found when attempting to remove it Aug 15 20:32:46 n1 bluetoothd[1075]: connect error: Connection refused (111) Aug 15 20:33:07 n1 bluetoothd[1075]: connect error: Host is down (112) Aug 15 20:33:07 n1 bluetoothd[1075]: GLib: Source ID 305 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76 Uname: Linux 4.4.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 15 20:34:34 2017 InstallationDate: Installed on 2015-12-26 (597 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterestingModules: rfcomm bnep btusb bluetooth ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2017-02-28 (168 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:bv
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
@Daniel van Vugt (vanvugt): Thanks for your assistance! I am not Mary Sherman, and I'm continuing to experience this problem, even with the PPA and after rebooting. I didn't subscribe to this bug, I didn't even know about it. I report bug 1691556 and you marked it a duplicate of this one. As I have already requested, kindly re-open my bug 1691556, as I don't believe I can re-open it myself. Finally, I'd like to see this fixed in 16.04. It's LTS, and that's important to me (and a lot of users). If that means I have to help with backport, I'm happy to do so. In addition, if I can be helpful with debugging, I'd be happy to do so, and have tried. It's just not clear to me at this point how to get better / more detailed debugging info. What I did try per https://wiki.ubuntu.com/DebuggingBluetooth didn't reveal anything helpful. For me, I believe the key issue is figuring out the "Device or resource busy" error (as I've mentioned here and in my original bug report). -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M.
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
The problem appears to be with setting up the input sink, which I couldn't care less about. If any knows of a way for bluez / pulseaudio to force a device to just connect as an output-only device (e.g., normal bluetooth speaker), I think I'd be fine, as I have no problems with numerous other bluetooth speakers. If not, I think for me the key is to figure out why the input sink cannot be established due to the "device or resource busy" message. If I could figure out how to a detailed debug / strace of bluetoothd when it tries to establish the input sink, that'd be most helpful. I've tried before w/o finding anything helpful. For me, I think the issue is not with pulseaudio but truly with bluez. Given this, I'd like to request that my bug 1691556 be re-opened and unmarked as a duplicate. From my perspective, no evidence or explanation has been given for why my report was marked as a duplicate as this one. The errors I've been continually reporting are different than those reported by others, and the fixes that seem to work for others do not work for me. For the record, here are the pulseaudio and bluez packages I presently have installed on my Ubuntu 16.04.02 LTS 64-bit on an Intel NUC i5 (NUC5i5RYH): ``` morse@n1 intel-nuc-i5-n1> dpkg -l bluez* pulsea* Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ NameVersion Architektur Beschreibung +++-===---=== ii bluez 5.37-0ubuntu5 amd64Bluetooth tools and daemons un bluez-alsa (keine Beschreibung vorhanden) un bluez-audio (keine Beschreibung vorhanden) ii bluez-cups 5.37-0ubuntu5 amd64Bluetooth printer driver for CUPS un bluez-gnome (keine Beschreibung vorhanden) un bluez-input (keine Beschreibung vorhanden) un bluez-network (keine Beschreibung vorhanden) ii bluez-obexd 5.37-0ubuntu5 amd64bluez obex daemon un bluez-serial (keine Beschreibung vorhanden) un bluez-utils (keine Beschreibung vorhanden) ii pulseaudio 1:8.0-0ubuntu3.3~xenial1 amd64PulseAudio sound server un pulseaudio-esound-compat (keine Beschreibung vorhanden) ii pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3~xenial1 amd64Bluetooth module for PulseAudio sound server ii pulseaudio-module-gconf 1:8.0-0ubuntu3.3~xenial1 amd64GConf module for PulseAudio sound server ii pulseaudio-module-x11 1:8.0-0ubuntu3.3~xenial1 amd64X11 module for PulseAudio sound server ii pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3~xenial1 amd64Zeroconf module for PulseAudio sound server ii pulseaudio-utils1:8.0-0ubuntu3.3~xenial1 amd64Command line tools for the PulseAudio sound server ``` -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Ver
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
@hife and @Mary Sherman (spot9019): Thanks for the speedy replies! @hife: Thanks for describing your workaround in greater detail. I've already tried the a2dp.py script, it doesn't fix the problem for me. I just downloaded again the latest version and tried again, no joy: ``` morse@n1 ~> ./a2dp.py Connection MADE Selecting device: 1. 0C:47:C9:0A:F6:F8 Amazon Tap-364 2. 00:0C:8A:58:F6:CA Bose SoundLink Mobile speaker II 3. 28:FD:80:00:86:85 Earin L 4. 50:F5:DA:A6:3F:EA Echo-JS6 Select device[1]: 4 Device MAC: 50:F5:DA:A6:3F:EA Device ID: bluez_card.50_F5_DA_A6_3F_EA Sink: bluez_sink.50_F5_DA_A6_3F_EA Updating default sink to bluez_sink.50_F5_DA_A6_3F_EA Setting the off profile Disconnecting the device. Connecting again. Cannot find `bluez_card.50_F5_DA_A6_3F_EA` using `pactl list cards short`. Retrying 4 more times Cannot find `bluez_card.50_F5_DA_A6_3F_EA` using `pactl list cards short`. Retrying 3 more times Cannot find `bluez_card.50_F5_DA_A6_3F_EA` using `pactl list cards short`. Retrying 2 more times Cannot find `bluez_card.50_F5_DA_A6_3F_EA` using `pactl list cards short`. Retrying 1 more times Device ID: bluez_card.50_F5_DA_A6_3F_EA Setting the a2dp profile Updating default sink to bluez_sink.50_F5_DA_A6_3F_EA Ignoring: Command: pacmd list-sink-inputs | grep "index:" failed with status: 1 stderr: Exiting bluetoothctl "Enjoy" the HiFi stereo music :) morse@n1 ~> pacmd list-sink-inputs 0 sink input(s) available. ``` When I run this a2dp.py script and get the output above, the following are posted in syslog: ``` Jun 3 13:10:19 n1 acpid: input device has been disconnected, fd 22 Jun 3 13:10:24 n1 bluetoothd[929]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy Jun 3 13:10:24 n1 kernel: [124613.035699] input: 50:F5:DA:A6:3F:EA as /devices/virtual/input/input26 Jun 3 13:10:27 n1 bluetoothd[929]: /org/bluez/hci0/dev_50_F5_DA_A6_3F_EA/fd14: fd(22) ready ``` When I run "pactl list sinks", I see sinks #0 and #1 as the built-in headphone jack, and then the Amazon Echo as sink #15 in a suspended state: ``` Sink #15 State: SUSPENDED Name: bluez_sink.50_F5_DA_A6_3F_EA Description: Echo-JS6 Driver: module-bluez5-device.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 49 Mute: Nein Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 Base Volume: 65536 / 100% / 0,00 dB Monitor Source: bluez_sink.50_F5_DA_A6_3F_EA.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE DECIBEL_VOLUME LATENCY Properties: bluetooth.protocol = "a2dp_sink" device.description = "Echo-JS6" device.string = "50:F5:DA:A6:3F:EA" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "speaker" bluez.path = "/org/bluez/hci0/dev_50_F5_DA_A6_3F_EA" bluez.class = "0x0c0414" bluez.alias = "Echo-JS6" device.icon_name = "audio-speakers-bluetooth" Profile: speaker-output: Lautsprecher (priority: 0) Aktive Profile: speaker-output Formate: pcm ``` -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified t
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
@hife and @Mary Sherman (spot9019): You both indicate that the latest pulse-testing ppa fixes the problem for you. Can you both indicate whether you are running Unity as the desktop or KDE or perhaps some other? I still have suspicions that there may be a permissions issue that is specific to Unity (which is the desktop I use and for which the fix does NOT work, at least for me). Thanks. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To b
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
I must unfortunately report that that the recently reported fix does not work for me. Ubuntu 16.04 LTS connecting to Amazon Echo. Pulseaudio 1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from ppa:ubuntu-audio-dev/pulse-testing as of today. The problem appears to result in the same conditions as I have comment on in bug 1691556 and discussed at askubuntu.com https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo- via-bluetooth Here are the syslog entries from testing today after installing the latest from pulseaudio-testing: Jun 1 10:24:23 n1 bluetoothd[1031]: a2dp-source profile connect failed for 50:F5:DA:A6:3F:EA: Device or resource busy Jun 1 10:24:23 n1 kernel: [ 423.337550] input: 50:F5:DA:A6:3F:EA as /devices/virtual/input/input22 Jun 1 10:24:26 n1 bluetoothd[1031]: /org/bluez/hci0/dev_50_F5_DA_A6_3F_EA/fd1: fd(23) ready Jun 1 10:25:26 n1 pulseaudio[5001]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Jun 1 10:25:41 n1 kernel: [ 500.946349] perf interrupt took too long (5021 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 Jun 1 10:25:28 n1 pulseaudio[5001]: message repeated 5 times: [ [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No Pu
[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
Additionally, this issue also appeared along the line with Ubuntu+KDE and apparently was easily resolved, as described in ubuntuforums.org, [link](https://ubuntuforums.org/showthread.php?t=2318966). Quoting another ubuntuforums.org post (also KDE), [link](https://askubuntu.com/questions/763539/bluetooth-speaker-no- sound-in-ubuntu-16-04), "So far, it seems that things only go wrong when I try to connect in A2DP mode. Until there is a real fix/workaround, I am going to try to remember to always switch to HSP/HSF mode before powering off or disconnecting the speaker.". So, perhaps in the short-term for Ubuntu+Unity a similar workaround could be found, if this is indeed the correct diagnosis, and in the longer-term figure out why connecting in A2DP mode fails (for both KDE and Unity). -- 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: New 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
[Touch-packages] [Bug 1691556] Re: Can't send audio to Amazon Echo via Bluetooth
I should also note that on the askubuntu.com site, I speculate that it may just be some permission issue deep down somewhere, and why. ** Description changed: - Pairing and coupling to Amazon Echo works, but sound is heard. + 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 + 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 ** Description changed: 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 + 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.han
[Touch-packages] [Bug 1691556] [NEW] Can't send audio to Amazon Echo via Bluetooth
Public bug reported: 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 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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: New 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