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

Issue 811465 link

Starred by 2 users

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

Kevin:BT headphone disconnects as we pair and connect a BLE mouse

Project Member Reported by pbath...@chromium.org, Feb 12 2018

Issue description

Chrome Version: 10323.30.0 / 65.0.3325.65

What steps will reproduce the problem?
(1)Pair and connect Bose QC35 headphones to Chromebook (kevin) and mobile device ( Iphone 7)
(2)Listen to music from chromebook
(3)Now connect a BLE mouse ( Microsoft designer mouse ) to chromebook

What is the expected result?
The mouse should connect and function fine

What happens instead?
As soon as we connect the mouse the Bose QC35 headphones is disconnected from the chromebook. After sometime the headphone re-connects itself but no audio is heard.

Please use labels and text to provide additional information.

This doesn't happen if we connect a HID mouse


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
bt_messages
425 KB View Download
user_chrome.log
328 KB View Download
ui.LATEST
3.1 KB Download
messages
799 KB View Download
dmesg.log
63.9 KB View Download
chrome
63.8 KB View Download
btnsoop.log
1.0 MB View Download
Labels: -Pri-2 Pri-1
Labels: -OS-Linux OS-Chrome
Issue seen on bob device also.

As mentioned in #0 , this happens only when we have the QC35 headphones connected to a phone and chromebook
Hi #1,

it seems like the cras request release right after the mouse connected:

1/ mouse connected:
2018-02-12T13:47:10.404463-08:00 DEBUG bluetoothd[3037]: profiles/input/hog-lib.c:report_map_read_cb() HoG created uHID device
...
2018-02-12T13:47:10.409907-08:00 INFO kernel: [  117.321106] hid-generic 0005:045E:0805.0003: input,hidraw1: BLUETOOTH HID v1.00 Mouse [Designer Mouse] on 18:67:B0:00:E2:73

2/ cras request release:
2018-02-12T13:48:56.556693-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:transport_set_state() State changed /org/bluez/hci0/dev_04_52_C7_C7_9D_1A/fd0: TRANSPORT_STATE_ACTIVE -> TRANSPORT_STATE_SUSPENDING <--- /* Release in progress */
...
2018-02-12T13:48:56.556767-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_request_create() Request created: method=Release id=4
2018-02-12T13:48:56.556780-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_owner_add() Owner :1.25 Request Release <--- :1.25 is cras

3/ media disconnected:
2018-02-12T13:48:56.566726-08:00 DEBUG bluetoothd[3037]: src/service.c:change_state() 0xf242108: device 04:52:C7:C7:9D:1A profile a2dp-sink state changed: connected -> disconnecting (0)
...
2018-02-12T13:48:59.364613-08:00 DEBUG bluetoothd[3037]: src/adapter.c:dev_disconnected() Device 04:52:C7:C7:9D:1A disconnected, reason 2 <--- MGMT_DEV_DISCONN_LOCAL_HOST
2018-02-12T13:48:59.365741-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_request_reply() Request Release Reply Success
2018-02-12T13:48:59.365810-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_owner_remove() Owner :1.25 Request Release



so maybe we can enable more cras logs to check:
add "--syslog_mask 7" to the end of /usr/share/cros/init/cras.sh
oops, that release request would supposed to suspend the transport(a2dp) by sending AVDTP_SUSPEND request.

but somehow the bluz started disconnecting the device, and then break the AVDTP_SUSPEND request:

normally:
2018-02-24T15:14:34.381657+08:00 DEBUG bluetoothd[2173]: profiles/audio/transpor
t.c:media_owner_add() Owner :1.43 Request Release <---- request release, send AVDTP_SUSPEND
2018-02-24T15:14:34.642877+08:00 DEBUG bluetoothd[2173]: profiles/audio/avdtp.c:
session_cb() <--- avdtp got cmd
2018-02-24T15:14:34.643047+08:00 DEBUG bluetoothd[2173]: profiles/audio/avdtp.c:
avdtp_parse_resp() SUSPEND request succeeded <--- finish AVDTP_SUSPEND request



but now:
2018-02-12T13:48:56.556780-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_owner_add() Owner :1.25 Request Release
2018-02-12T13:48:56.556810-08:00 DEBUG bluetoothd[3037]: src/service.c:change_state() 0xf2423d8: device 04:52:C7:C7:9D:1A profile avrcp-controller state changed: connected -> disconnecting (0) <--- start disconnecting
...
2018-02-12T13:48:59.365676-08:00 ERR bluetoothd[3037]: No reply to Suspend request <--- suspend request dropped
2018-02-12T13:48:59.365741-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_request_reply() Request Release Reply Success
2018-02-12T13:48:59.365810-08:00 DEBUG bluetoothd[3037]: profiles/audio/transport.c:media_owner_remove() Owner :1.25 Request Release


still not sure why disconnect...

Comment 5 by mcchou@chromium.org, Apr 19 2018

Labels: -Pri-1 -M-65 M-68 Pri-2
Owner: mcchou@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment