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

Issue 800998 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Bluetooth discovery fails to stop

Project Member Reported by pbath...@chromium.org, Jan 11 2018

Issue description

version: 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


 
Labels: M-64 M-65
Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
As i test on M-65 10295.0.0 ,I don't see the issue happening on this build
Status: WontFix (was: Assigned)
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!

Comment 4 by rajatja@google.com, Jan 25 2018

Labels: -Pri-2 Pri-1
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)

Comment 5 by rajatja@google.com, Jan 25 2018

Status: Assigned (was: WontFix)

Comment 6 by rajatja@google.com, Jan 25 2018

Labels: Proj-Soraka

Comment 7 by rajatja@google.com, Jan 26 2018

Cc: tbroch@chromium.org snanda@chromium.org ravisadineni@chromium.org bleung@chromium.org
 Issue 805797  has been merged into this issue.

Comment 8 by rajatja@google.com, Jan 26 2018

Labels: ReleaseBlock-Stable
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!
Has the root cause been identified?   Need to triage / prioritize given RBS status for M64.

Comment 11 by r...@chromium.org, Jan 29 2018

Status: Fixed (was: Assigned)
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.

Labels: Merge-TBD
[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.
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!
Cc: abodeti@google.com mkarkada@chromium.org derat@chromium.org ka...@chromium.org dhadd...@chromium.org
 Issue 809310  has been merged into this issue.
Project Member

Comment 15 by sheriffbot@chromium.org, Mar 23 2018

Labels: -Merge-TBD

Sign in to add a comment