touch-packages team mailing list archive

[goliy <962082@xxxxxxxxxxxxxxxxxx>]

I confirm the bug is still here, HSP\HFP profile doesn't work
Tested with 2 bluetooth headsets

syslog says:
Jan 3 06:14:25 fitz123-laptop bluetoothd[745]: /org/bluez/745/hci0/dev_48_C1_AC_E0_2C_CF/fd0: fd(26) ready
Jan 3 06:14:25 fitz123-laptop rtkit-daemon[2277]: Successfully made thread 3043 of process 2262 (n/a) owned by '1000' RT at priority 5.
Jan 3 06:14:25 fitz123-laptop rtkit-daemon[2277]: Supervising 4 threads of 1 processes of 1 users.
Jan 3 06:14:25 fitz123-laptop bluetoothd[745]: Badly formated or unrecognized command: AT+XEVENT=USER-AGENT,COM.PLANTRONICS,PLT_Legend,115,34.06,1069b78391dca242aa1fc92c3794e7f6
Jan 3 06:14:25 fitz123-laptop bluetoothd[745]: Badly formated or unrecognized command: AT+BIA=0,0,0,1,1,1,0

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.10
Release:	14.10
Codename:	utopic

$ usb-devices
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=413c ProdID=8197 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=A4DB3020F62F
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

$ dmesg | grep Bluetooth
[ 14.799529] Bluetooth: Core ver 2.19
[ 14.799549] Bluetooth: HCI device and connection manager initialized
[ 14.799556] Bluetooth: HCI socket layer initialized
[ 14.799559] Bluetooth: L2CAP socket layer initialized
[ 14.799568] Bluetooth: SCO socket layer initialized
[ 14.803087] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.803091] Bluetooth: BNEP filters: protocol multicast
[ 14.803099] Bluetooth: BNEP socket layer initialized
[ 14.815372] Bluetooth: RFCOMM TTY layer initialized
[ 14.815382] Bluetooth: RFCOMM socket layer initialized
[ 14.815387] Bluetooth: RFCOMM ver 1.11

-- 
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/962082

Title:
  Profiles that require duplex audio like Head Set (HSP) and Hands Free
  (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips

Status in HWE Next Project:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This problem seems to occur on every device that uses  the BCM20702A0
  Bluetooth hardware.

  How to reproduce:

  (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0.
  (2) Activate the device.  Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device.  This creates SCO link and the plumbs the audio components.
  (3) Open the sound settings tool and select the bluetooth device under the "Input" and "Output" tabs.  Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right.  This is the item to select.

  Now, everything should be configured so that you can use your
  bluetooth device to hear and record audio.  Test this by:

  Testing Input:

  (1) In the sound settings tool, select the "Input" tab.
  (2) Make sure the "Input Volume" is not muted and the scale widget is not set to zero.
  (3) Make sounds into the headset mic -- you should see the "Input Level" bar raise.

  Testing Output:
  In the same program:
  (1) Select the "Hardware" tab.
  (2) In the box labeled "Choose a device to configure", select your bluetooth device.
  (3) A combobox should appear at the bottom of the window labeled "Settings for the selected device".  Choose "Telephony Duplex (HSP/HFP)".
  (4) Now click on the "Test Speakers" button to the right.
  (5) Run speaker test.  You should hear a sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions