We all knew this already, as it is documented in this report. As well, I strongly consense this is a kernel issue.
However, I am bound by Ubuntu Kernel Team and Ubuntu Bug Control policy to ensure the minimum requirement information is provided here, in order to mark this Triaged. Once marked, as per UKT/UBC policy, a report is in the official state where any Ubuntu Community/Kernel.org developer could begin working on this. :)
>"Mainline does nothing to resolve the issues."
Just to be clear, which mainline kernel did you test specifically?
Benjamin Kerensa, thank you for providing the lsusb output and testing the mainline kernel.
+ Just to clarify https:/ /bugs.launchpad .net/ubuntu/ +source/ pulseaudio/ +bug/972063/ comments/ 12 :
Bus 002 Device 010: ID 0b0e:090c GN Netcom
This is also an example of a bluetooth device intended to connect strictly via a BT connection with your BT laptop?
+ Regarding https:/ /bugs.launchpad .net/ubuntu/ +source/ pulseaudio/ +bug/972063/ comments/ 53 :
Bus 001 Device 003: ID 1bcf:2980 Sunplus Innovation Technology Inc.
Bus 002 Device 003: ID 8086:0189 Intel Corp.
Did both of these device IDs pop up when you plugged your BT in?
+ Regarding https:/ /bugs.launchpad .net/ubuntu/ +source/ pulseaudio/ +bug/972063/ comments/ 54 : Developers there seems to be a strong consensus that this is Kernel related."
>"Notably extensive testing of this hardware has already been conducted by myself and also various Canonical Engineers/
We all knew this already, as it is documented in this report. As well, I strongly consense this is a kernel issue.
However, I am bound by Ubuntu Kernel Team and Ubuntu Bug Control policy to ensure the minimum requirement information is provided here, in order to mark this Triaged. Once marked, as per UKT/UBC policy, a report is in the official state where any Ubuntu Community/ Kernel. org developer could begin working on this. :)
>"Mainline does nothing to resolve the issues."
Just to be clear, which mainline kernel did you test specifically?