-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Unable to scan on windows 10 tablet: "no such interface supported" #364
Comments
What's the build version of that windows 10 release? |
Version: 1809 |
🤔 Perhaps this is why it fails for me. According to this microsoft doc The AllowExtendedAdvertisements property was introduced in version 2004, my tablet is on 1809. I'm assuming that's what's being set here in the crate? Probably not worth it to fix in the crate, but if you have advice or a workaround I'd appreciate it 😅 |
Update: I removed that line in my fork and I'm able to scan. |
Huh, interesting. I wonder if we can do some sort of existence check around that. |
Yeah up to you if you want to support a 6 year old version of windows. ¯_(ツ)_/¯ |
I've got the same error when testing on Windows 10 LTSC 2019, which is supported by Microsoft until 2029 (longer than LTSC 2021). Version 1809, 17763.5936. Would you please describe OS version requirements in the documentation before fixing this issue? "btleplug is a Bluetooth Low Energy (BLE) central module library for Rust. It currently supports Windows 10, macOS (and possibly iOS) and Linux (BlueZ)." Does it support only Windows 10 2004 and later, but not Windows 11? |
Workaround in my app: in https://github.com/wuwbobo2021/rtl8762c-ble-uart/blob/main/host-term/README.md Another interesting problem: when bluetooth is disabled on Windows 10, the adapter is still available in And I don't know how to get the ATT_MTU value of the connection (maybe not an issue of |
Describe the bug
When calling
adapter.start_scan().await
I get this error: Error { code: HRESULT(0x800004002), message "no such interface supported" }It only happens on the windows 10 tablet that I'm targeting other windows devices work.
Expected behavior
I expect it to start scanning like it does on every other device I test.
Actual behavior
The error above.
Additional context
The device is a faytech "10.1 Ruggedized Tablet PC"
It runs Windows 10 enterprise LTSC.
Could it be the fact that it's an LTSC tablet that's is simply so out of date that it wont work with the
windows
crate?Might be out of scope for this crate but I'm not sure how to trouble shoot this. 🤔
I made it panic so I could give you a stack trace.
The text was updated successfully, but these errors were encountered: