Has anyone else seen this kind of notification callback failure? Using the built-in adapter, I do not see the notify callback problem. This machine is running Windows 10 Version 2004.
Device Manager shows it as "Intel (R) Wireless Bluetooth (R)".
The adapter is an Intel Dual Band Wireless-AC 3160 mini-card. (Works) I also have a Windows desktop machine with built-in Bluetooth. But on Version 2004, and also recent Windows Insider Preview builds, I see the notify callback problem. This dongle works fine on a Windows 10 Version 1909 laptop just fine. In Windows it shows up in Device Manager as "Generic Bluetooth Radio". (Fails) I have a generic Bluetooth 4.0 USB dongle, which identifies via USB as VID/PID 0a12/0001, "Cambridge Silicon Radio, Ltd", "Bluetooth Dongle (HCI mode)". I am testing with two different adapters:
#USE GENERIC BLUETOOTH RADIO WINDOWS 10 REGISTRATION#
I've instrumented the callback registration code in dotnet/client.py, and it seems to be doing what it it's supposed to. Yet I have also seen it mysteriously start working after removing and replacing the adapter (but not all the time). Cycling Bluetooth on and off in Windows Settings doesn't help. When the failure happens, no notify callbacks happen at all. It seems to be related to which version of Windows 10 I'm using, and which Bluetooth adapter. I have been having trouble with notify callbacks not happening sometimes.
BlueZ version ( bluetoothctl -v) in case of Linux:.Operating System: Windows 10 Version 2004 and also Windows Insider Preview builds.
0 kommentar(er)
