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

Issue 898335 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 898334
Owner:
Closed: Oct 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

[SecureChannel Bluetooth] Ignore DeviceChanged event right after device is disconnected

Project Member Reported by jlklein@chromium.org, Oct 23

Issue description

For context, see https://groups.google.com/a/google.com/d/topic/better-together-dev/nHWZg-7fme4/discussion.

We are currently trying to connect to a device right after the connection to it is lost, which will always fail and waste one of our retry attempts. It also seems like it may put Bluetooth in a weird state sometimes. According to Gio, we should:

"Once the device becomes disconnected, ignore the first DeviceChanged event. That event is being dispatched because the device disconnected, not because we received an advertisement. If the device is still around, we'll soon get another DeviceChanged event and we can connect then."
 
Mergedinto: 898334
Status: Duplicate (was: Assigned)

Sign in to add a comment