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

Issue 905374 link

Starred by 1 user
Status: Assigned
Owner:
█ shijinabraham@chromium.org
Last visit > 30 days ago
Cc:
josephsih@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Delay in stopping discovery

Project Member Reported by shijinabraham@chromium.org, Nov 14 

OS: CrOS 11151.29.0

What steps will reproduce the problem?
Run test_discover_device test via bluetooth_AdapterPairing.mouse autotest.

What is the expected result?
After calling stop_discovery the "Discovering" adapter property should turn False quickly.

What happens instead?
It take >30 seconds (sometime >90 seconds) for to the property to change. This is seen on some devices such as Sabin and Nocturne.

Comment 1 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.
►

Sign in to add a comment