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

Issue 615354 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 615383
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 484781



Sign in to add a comment

bluetooth: Can't connect to device after restarting bluetoothd

Project Member Reported by fbeaufort@chromium.org, May 27 2016

Issue description

Version 52.0.2743.0 dev (64-bit)
Platform 8350.2.0 (Official Build) dev-channel link
Firmware Google_Link.2695.1.169

What steps will reproduce the problem?
(1) Go to https://googlechrome.github.io/samples/web-bluetooth/device-disconnect.html
(2) Enter nearby BLE device name, click "Scan" button
(3) Select device in BT chooser, click "Pair" button

What is the expected output?
Device should be connected

What do you see instead?
It is not.

Here are my logs:

[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(430)] requestDevice called with the following filters: 
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(432)] Name: 
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(433)] Name Prefix: PL
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(434)] Services:
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(435)] 	[
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(438)] 	]
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(441)] requestDevice called with the following optional services: 
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(568)] Populating 2 devices in chooser 12
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(571)] 	7C:35:FE:85:B5:7F
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(571)] 	6C:86:2A:7B:49:63
[7489:7489:0527/114718:VERBOSE1:bluetooth_adapter_bluez.cc(1251)] AddDiscoverySession
[7489:7489:0527/114718:VERBOSE1:bluetooth_adapter_bluez.cc(1547)] OnSetDiscoveryFilter
[7489:7489:0527/114718:VERBOSE1:bluetooth_adapter_bluez.cc(1432)] OnStartDiscovery
[7489:7489:0527/114718:VERBOSE1:bluetooth_adapter.cc(280)] BluetoothAdapter::OnStartDiscoverySession
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(593)] Started discovery session for 12
[7489:7489:0527/114718:VERBOSE1:bluetooth_adapter_bluez.cc(976)] Discovering changed: 1
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_CA_54_48_65_A6_45
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: CA:54:48:65:A6:45
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_AC_E6_4B_05_88_2D
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: AC:E6:4B:05:88:2D
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_67_ED_FC_BB_3C_6F
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: 67:ED:FC:BB:3C:6F
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_5A_E6_28_FE_D6_38
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: 5A:E6:28:FE:D6:38
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_FB_1F_30_C2_94_EA
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: FB:1F:30:C2:94:EA
[7489:7489:0527/114718:VERBOSE2:bluetooth_device_bluez.cc(637)] Gatt services have not been fully resolved for device /org/bluez/hci0/dev_C3_65_2E_68_4B_9E
[7489:7489:0527/114718:WARNING:arc_bluetooth_bridge.cc(683)] no Bluetooth instance available
[7489:7489:0527/114718:VERBOSE1:bluetooth_dispatcher_host.cc(363)] Adding device to all choosers: C3:65:2E:68:4B:9E
[7489:7489:0527/114720:VERBOSE1:bluetooth_allowed_devices_map.cc(47)] Adding a device to Map of Allowed Devices.
[7489:7489:0527/114720:VERBOSE1:bluetooth_allowed_devices_map.cc(62)] Device already in map of allowed devices.
[7489:7489:0527/114720:VERBOSE1:bluetooth_dispatcher_host.cc(713)] Device: PLAYBULB Candle
[7489:7489:0527/114720:VERBOSE1:bluetooth_dispatcher_host.cc(714)] UUIDs: 
[7489:7489:0527/114720:VERBOSE1:bluetooth_dispatcher_host.cc(723)] 	 Not Allowed: 0000ff02-0000-1000-8000-00805f9b34fb
[7489:7489:0527/114720:VERBOSE1:bluetooth_discovery_session.cc(45)] Stopping device discovery session.
[7489:7489:0527/114720:VERBOSE1:bluetooth_adapter_bluez.cc(1314)] RemoveDiscoverySession
[7489:7489:0527/114720:VERBOSE1:bluetooth_adapter_bluez.cc(1479)] OnStopDiscovery
[7489:7489:0527/114720:VERBOSE1:bluetooth_adapter_bluez.cc(976)] Discovering changed: 0

For info, I use BlueZ 5.39 with https://chromium.googlesource.com/chromiumos/third_party/bluez/+/2a2e7102cd86ec3c28cc2b7e003ba8deb07f4731 reverted as advised in  Issue 614903 .
 
Labels: -Pri-1 Pri-3
Summary: bluetooth: Can't connect to device after restarting bluetoothd (was: bluetooth: Can't connect to device)
I think I know how this happened but not sure why...

crosh> shell
chronos@localhost / $ sudo su
localhost / # stop bluetoothd
bluetoothd stop/waiting
localhost / # start bluetoothd
bluetoothd start/running, process 6799
localhost / # 

Why restarting bluetoothd prevents me to connect to device anymore?
Any idea?
Cc: de...@chromium.org mcchou@chromium.org
Components: -Blink>Bluetooth OS>Systems>Bluetooth
It looks like pairing agent needs to be turned on after restarting bluetoothd. I wonder if https://chromium.googlesource.com/chromiumos/third_party/bluez/+/e211b7c05fe6d4ac9535421317f893b249ea0083%5E%21/#F0 should also start pairing agent as well since it now remembers powered state.
According to a IRC discussion with BlueZ folks, pairing is not the issue there... still trying to understand what is going on. 

Comment 4 by ortuno@chromium.org, May 27 2016

Mergedinto: 615383
Status: Duplicate (was: Available)

Sign in to add a comment