*: detecting abrupt disconnections in Linux#420
Closed
sorayaormazabalmayo wants to merge 10 commits intotinygo-org:releasefrom
Closed
*: detecting abrupt disconnections in Linux#420sorayaormazabalmayo wants to merge 10 commits intotinygo-org:releasefrom
sorayaormazabalmayo wants to merge 10 commits intotinygo-org:releasefrom
Conversation
This PR registers a `ConnectionStatusChanged` WinRT event handler on `BluetoothLEDevice` to detect abrupt disconnections. The handler resolves the current connection state and forwards it to `a.connectHandler`. The event token and handler are stored to allow proper unregistration during device teardown.
notifications by passing in nil as the callback argument
…inygo-org#389) * linux: Add Write method to write characteristic value with response * Use short hand error check * Remove named returns
* linux: support removing service * windows: support removing service * sd+hci: stub removing service method
Unexpose the representation of the UUID data and unexport the Bytes method. Also document the byte ordering of binary marshaling and provide an exported binary round-tripper for UUID data.
Signed-off-by: deadprogram <ron@hybridgroup.com>
…go-org#410) * fix: Windows characteristic ordering in DiscoverCharacteristics The characteristics will now appear on the expected order * range over filterUUIDs
This PR implements persistent D-Bus signal monitoring at the adapter level to detect abrupt disconnections. The `connectHandler` callback was not being invoked when Bluetooth devices disconnected abruptly (e.g., device powered off, out of range, battery died) on Linux. It only worked for planned disconnections via `Device.Disconnect()`. This created an inconsistency with the Darwin implementation, which correctly detects all disconnections through CoreBluetooth's `DidDisconnectPeripheral` delegate method.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implements persistent D-Bus signal monitoring at the adapter level to detect abrupt disconnections. The
connectHandlercallback was not being invoked when Bluetooth devices disconnected abruptly (e.g., device powered off, out of range, battery died) on Linux. It only worked for planned disconnections viaDevice.Disconnect(). This created an inconsistency with the Darwin implementation, which correctly detects all disconnections through CoreBluetooth'sDidDisconnectPeripheraldelegate method.