New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 755242 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Bluetooth Speaker will show as connected but not seen in audio devices list

Project Member Reported by pbath...@chromium.org, Aug 14 2017

Issue description

Chrome Version:9765.28.0 (Official Build) dev-channel 

What steps will reproduce the problem?
(1)Pair and connect to BT speaker ( Two Sigma)
(2)Try to play any music

What is the expected result?

The music should play from BT speaker

What happens instead?

The BT speaker shows as connected but it is not seen in the audio devices list and music is played from on board speakers

Please use labels and text to provide additional information.

I am able to connect the same speaker with Iphone 6s and Nexus 6p with me and play music through the speaker
 
Screenshot 2017-08-14 at 11.39.59 AM.png
262 KB View Download
BTspeaker.txt
742 KB View Download
debug-logs_20170814-114058.tgz
80.5 KB Download
Cc: pbath...@chromium.org kobbad@chromium.org
Cc: wuchengli@chromium.org
Owner: wuchengli@chromium.org
Status: Assigned (was: Untriaged)
@pbathini, is this still happening? 
@wuchengli, can you take a look at this? 
Owner: pbath...@chromium.org
Re #0: 9765.28.0 is M61 and the device is Kevin.

9765.28.0 is built on Aug 13. It's too old. pbathini@ Please help verify the tot of M61. Thanks.
Owner: wuchengli@chromium.org
I can reproduce the issue on 63.0.3239.11/ 10032.7.0 build .

The Bluetooth speaker i am using is "Two Sigma" BT speaker.
I'll take a look.

Re #5: pbathini@ next time please still attach the feedback report or generate_logs logs. Thanks.
In log in #0:

2017-08-14T18:40:36.527551+00:00 ERR cras_server[2762]: Connection watch timeout.

https://cs.corp.google.com/chromeos_public/src/third_party/adhd/cras/src/server/cras_bt_device.c?type=cs&q=bt_device_conn_watch_cb+package:%5Echromeos_public$&l=619

The profile was not ready before timeout.
I tried bob M62 9897.0.0 with Bose AE SoundLink. I could not reproduce the issue.
I tried kevin M59 9460.57.0 with Bose AE SoundLink. I could not reproduce the issue.
Owner: mcchou@chromium.org
I think we need to get bluetoothd log since bluetoothd handles connection and profiles.

To enable the log, add --debug to

/usr/bin/start_bluetoothd.sh like this:

exec /sbin/minijail0 -u bluetooth -g bluetooth -G \
  -c 3500 -n -- \
  /usr/libexec/bluetooth/bluetoothd ${BLUETOOTH_DAEMON_OPTION} --nodetach \
  ${config_file_param} --debug

Then there will be bluetoothd logs in /var/log/messages.

Could Miao please take a look since it is model specific, plus, it seems that bluetoothd can not connect the profile ?

Thanks!
I tried kevin M63 10032.7.0 with Bose AE SoundLink. I could not reproduce the issue. This is probably specific to this Two Sigma speaker.
Cc: josephsih@chromium.org
Re #10  -- PFA the /var/log/messages and also generate_logs with the bluetoothd logs.

Re #11 -- Yes, it seems specific to Two sigma speaker.
messages.txt
340 KB View Download
debug-logs_20171024-160751.tgz
187 KB Download

Sign in to add a comment