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

Issue 758312 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

When advertising or scanning fail to start up, we still use full timeout

Project Member Reported by khorimoto@chromium.org, Aug 23 2017

Issue description

We currently use a 10-second timeout for connecting to a host device (i.e., we start advertising/scanning, and if we don't get a response back in 10s, we try another host device).

However, starting up advertising/scanning is asynchronous. If it eventually fails to start up, we still wait the entire 10 seconds before giving up and trying another device, even though there is no actual way for the connection to occur since BLE failed.

We should give up that attempt and retry immediately instead of waiting 10s.
 
Status: WontFix (was: Available)
Since this bug was filed, we changed to retry any failed advertisements instead of just seeing one failure and stopping any attempts.

Sign in to add a comment