I've ordered this headset, and we'll get logs from it if we can repro.

I have tried connecting the Bose Soundlink 2 headphones to Toshiba CB35-B3340 Chromebook (Swanky) . The UI of the Chromebook shows the headphones as connected but we don't see them under the audio devices list.

Deleted: log-121216-104424.tar.gz 788 KB

log-121216-104424.tar.gz 788 KB Download

Deleted: Screenshot 2016-12-12 at 10.42.43 AM.png 75.0 KB

	Screenshot 2016-12-12 at 10.42.43 AM.png 75.0 KB View Download

Deleted: bose.txt 707 KB

bose.txt 707 KB View Download

Miao, could you look at this? This is likely a BT issue again.

They work fine on my Samus with the following build -
Version 55.0.2883.76 beta (64-bit)
Platform 8872.65.0 (Official Build) beta-channel samus
ARC Version 3532895
Firmware Google_Samus.6300.174.0

Maybe its device specific.

The headphones work on 8872.65.0 (Official Build) beta-channel swanky.

But It doesn't work samus 56.0.2924.26 / 9000.26.0 build.

Same behavior as in #4 is seen.Swanky also had M-56 build in #4.

This seems to be a regression between M-55 and M-56

Miao: could you take a look at this since it looks reproducible according to #8 ?

I don't see suspicious log from debug log in #4, and there's no change in CRAS related to BT audio from R55 to R56. Maybe you can try put R55 bluetoothd onto R56 and see it makes difference?

Yes, I will take a look at this. We see some issues filed recently for Bose headphones.

Miao discussed with me about the correlation of this issue and chrome-os-partner 61751 "External BT speaker was paired, but the external speaker is not shown as an audio output source" today. It was suspected that this issue may not be device specific. 

I do not have the Bose Soundlink 2 headphones. I use "UE MINI BOOM" to test on Samus R56-9000.26.0 (referring to comment#8) but cannot reproduce the issue. The bt speaker does show up in audio device list after pairing and connection.

Hence, the issue looks like being related with the particular device, Bose Soundlink 2 headphones, only.

Mirroring https://code.google.com/p/chrome-os-partner/issues/detail?id=61751#c9:
I tried to pair and connect Bose AE2 SoundLink supporting A2DP and HFP/HSP with the following settings. Note that this is a BlueZ issue but not a platform-specific issue.

Platfrom: Samus
Build:    samus-release/R56-9000.52.0

Platfrom: Samus
Build: samus-release/R55-8872.73.0

With R55 image, samus connected to the headphone in BT setting and the headphone showed up on the list of audio devices. 
With R56 image, samus connected to the headphone in BT setting but didn't show up on the list of audio devices.

Logs:
R55_meesgaes_bt.txt: Bluetooth-related logs from /var/log/messages
R55_hcidump.log:     output of hcidump command
R56_meesgaes_bt.txt: Bluetooth-related logs from /var/log/messages
R56_hcidump.log:     output of hcidump command

Observation:
The attached logs includes my findings where I used "@@" as prefixes. In the logs of R55, samus paired and connected to the headphone via BR/EDR, and classic profiles, A2DP AVRCP AVDTP HSP/HFP, were connected afterwards. However, in the log of R56, samus paired and connected to the headphone via LE, so none of the classic profiles was connected with several retries, and that's why cras saw a sequence of D-Bus errors (org.bluez.Error.InProgress).

This is a dual-mode device issue in BlueZ where rkc@ landed a temp fix in R55. However, we need a proper fix for R56.  crbug.com/636078  is re-opened for this issue.

Deleted: R55_hcidump.log 1.2 MB

R55_hcidump.log 1.2 MB View Download

Deleted: R55_messages_bt.txt 127 KB

R55_messages_bt.txt 127 KB View Download

Deleted: R56_hcidump.log 24.6 KB

R56_hcidump.log 24.6 KB View Download

Deleted: R56_messages_bt.txt 142 KB

R56_messages_bt.txt 142 KB View Download

Verified on 9000.76.0 build