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

Issue 771335 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Discovery session cannot detect advertisements

Project Member Reported by khorimoto@chromium.org, Oct 3 2017

Issue description

We've seen this issue a few times. After starting up the CrOS device, we can detect nearby tether devices. At some point, something happens which prevents scans results from showing up.
 
Cc: khorimoto@chromium.org
rkc@ to provide logs.
I left my device scanning overnight, and when I got back, it was no longer detecting any Bluetooth devices. I opened up the Bluetooth settings, and no devices were there, even BR/EDR devices.

Logs were too big to attach to the bug (since I left the scan on overnight, the logs are very long). I uploaded them to Google Drive:

https://drive.google.com/a/google.com/file/d/0B6tDJkhYQT1FM0ZvRzZ3Q0NsMHM/view?usp=sharing

Comment 3 by mcchou@chromium.org, Oct 12 2017

b/67719578 is open and assigned to Intel.
Is this tracked by the b/ bug and should we close this?

We are planning to build a R62 stable RC the evening of the 19th, so we would need to have all fixes merged back to 62 in ~24 hours. 

Comment 5 by r...@chromium.org, Oct 18 2017

Status: WontFix (was: Assigned)
This is tracked by buganizer, closing.

Sign in to add a comment