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.

Sign up for GitHub

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

Jump to bottom

Bluetooth discovery gets stuck on Widcomm stack #8

Open

GoogleCodeExporter opened this issue Aug 29, 2015 · 0 comments

Labels

auto-migrated Default-branch OpSys-Windows Priority-High Type-Defect

GoogleCodeExporter commented Aug 29, 2015

Sometimes the function WIDCOMMBluetooth::doDiscovery() never returns due to 
the OnDiscoveryComplete() callback function never being called once the 
discovery is complete. This seems to be a problem with the Widcomm stack, but 
needs to be tested and confirmed.

Original issue reported on code.google.com by erik.nor...@gmail.com on 17 Sep 2009 at 12:52

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-High Type-Defect auto-migrated Default-branch OpSys-Windows labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment