Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for BLE extended advertising on Windows #96

Open
SaltyLad opened this issue Nov 14, 2024 · 2 comments
Open

Support for BLE extended advertising on Windows #96

SaltyLad opened this issue Nov 14, 2024 · 2 comments

Comments

@SaltyLad
Copy link

Hello,

I've noticed that the Windows implementation of this plugin currently lacks support for BLE extended advertising. As a result, devices using extended advertising features, such as coded PHY, aren’t detected during scans.

This can be addressed by enabling BluetoothLEAdvertisementWatcher.AllowExtendedAdvertisements after the watcher is instantiated. I’d be happy to submit a pull request to make this change if you’re open to supporting this feature.

More details here

@rohitsangwan01
Copy link
Contributor

Hey, because there are multiple platforms involved, it would be great if we have some info about rest of the platforms as well, and then decide the Api behaviour

@SaltyLad
Copy link
Author

Hi,

Sorry for the delay in responding. I have tested the package on the Android platform. I can confirm devices using extended advertising features are discovered when scanning, no changes are required.

I unfortunately cannot test for Mac or iOS as I do not have Apple devices available.

I would suggest this setting be enabled by default on Windows without necessarily adding an API option. Legacy advertising devices could still be seen during scanning, and this would bring the Windows version in line with the Android version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants