Bluetooth discovery fails to stop |
|||||||||||
Issue descriptionversion: 64.0.3282.79 / 10176.41.0 What steps will reproduce the problem? (1) open shell and type "btmon -w btsnoop.log" (2) On chrome UI, tap on the system tray in bottom right corner, and then tap on Bluetooth. It will show devices found. Let it discover for a few seconds, say, 5 ~ 10 seconds. (3) Tap on elsewhere on chrome so that the Bluetooth device window disappear. (4) Check btmon to see whether it keeps finding devices. (In my test, discovery is not stopped.) (5) Tap on the system tray in bottom right corner again. Do not tap into Bluetooth menu this time. (6) Check btmon and see if discovery is stopped this time What is the expected result? The discovery should stop once we exit from the bluetooth sub-menu What happens instead? The bluetooth discovery doesnot stop Please use labels and text to provide additional information. Seen the issue om M-64 Eve,Caroline, Chell and peppy
,
Jan 11 2018
As i test on M-65 10295.0.0 ,I don't see the issue happening on this build
,
Jan 11 2018
Yes, I tested caroline-release/R65-10297.0.0 too today. The problem has been fixed on ToT. Let's close this issue. Pramod, thanks for testing it!
,
Jan 25 2018
Does seeing a continuous stream of messages like the following count as "bluetooth discovery"? If so, then I see this even on 10337.0.0 (tested on Soraka). The bluetooth setting wiondow is not displayed, but these messages are seen on btmon. Note that this is a problem because this might cause failure to suspend if a BT mouse is connected (as the bluetooth is then considered a wakeup source).
> HCI Event: LE Meta Event (0x3e) plen 43 [hci0] 22.745783
LE Advertising Report (0x02)
Num reports: 1
Event type: Non connectable undirected - ADV_NONCONN_IND (0x03)
Address type: Random (0x01)
Address: 2C:59:61:8E:3E:19 (Non-Resolvable)
Data length: 31
Company: Microsoft (6)
Data: 010920008388de13fffddb42d4026632095d3c1cd3551634ddf35a
RSSI: -72 dBm (0xb8)
> HCI Event: LE Meta Event (0x3e) plen 27 [hci0] 22.770913
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: 04:52:C7:0D:26:E3 (OUI 04-52-C7)
Data length: 15
Flags: 0x1a
LE General Discoverable Mode
Simultaneous LE and BR/EDR (Controller)
Simultaneous LE and BR/EDR (Host)
16-bit Service UUIDs (complete): 1 entry
Bose Corporation (0xfebe)
Company: SGL Italia S.r.l. (784)
Data: 400c0350
RSSI: -77 dBm (0xb3)
> HCI Event: LE Meta Event (0x3e) plen 25 [hci0] 22.796786
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: CA:04:C5:63:1F:AE (Static)
Data length: 13
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Google (0xfef4)
Name (short): gBV3
RSSI: -83 dBm (0xad)
> HCI Event: LE Meta Event (0x3e) plen 43 [hci0] 22.845796
LE Advertising Report (0x02)
Num reports: 1
Event type: Non connectable undirected - ADV_NONCONN_IND (0x03)
Address type: Random (0x01)
Address: 2C:59:61:8E:3E:19 (Non-Resolvable)
Data length: 31
Company: Microsoft (6)
Data: 010920008388de13fffddb42d4026632095d3c1cd3551634ddf35a
RSSI: -65 dBm (0xbf)
,
Jan 25 2018
,
Jan 25 2018
,
Jan 26 2018
Issue 805797 has been merged into this issue.
,
Jan 26 2018
,
Jan 29 2018
Hi rajatja@, could you describe how you reproduced the issue? Is it always reproducible? It would be helpful if you could attach /var/log/messages next time you see the issue again, and even better with the btmon log. Thanks!
,
Jan 29 2018
Has the root cause been identified? Need to triage / prioritize given RBS status for M64.
,
Jan 29 2018
Being on the settings page only makes us scan, not advertise. However, we do advertise at many other times due to the better together features. These reports are of advertising. If you do see 'scanning' continue after closing the settings page, then please do re-open this bug, otherwise it seems that this has been fixed.
,
Jan 29 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-65; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-65 label, otherwise remove Merge-TBD label. Thanks.
,
Jan 30 2018
Hi Rajat, I just tested 10337.0.0 on Coral and did not find the problem that you described. If you still observed the problem, please let us know the steps that you reproduce it. Thanks!
,
Feb 6 2018
Issue 809310 has been merged into this issue.
,
Mar 23 2018
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by rjahagir@chromium.org
, Jan 11 2018Owner: r...@chromium.org
Status: Assigned (was: Untriaged)