2 ms·

> WIDCOMM bluetooth stack Oh that brings memories. Fun fact, Bluetooth is still shit in Windows 10. A ham friend bought a TP-Link UB500 bluetooth stick to con

> WIDCOMM bluetooth stack Oh that brings memories. Fun fact, Bluetooth is still shit in Windows 10. A ham friend bought a TP-Link UB500 bluetooth stick to connect to some bluetooth-to-serial adapter for one of his radio... Windows recognized it, but refused to connect to the serial adapter. Only after installing dedicated drivers for the BT stick [1], it worked. It's mind-boggling that Windows still doesn't ship with a fully functioning native Bluetooth stack. Everything Bluetooth should be standardized for decades now. [1] https://www.tp-link.com/de/support/download/ub500/v1/ https://www.tp-link.com/de/support/download/ub500/v1/

vel0city 2y ago
From what I've experienced, any Intel WiFi/BT adapter/BT stack just works out of the box on Windows. Any random USB adapter has a massive amount of variability. There's just so many different chipsets out there with tons of odd quirks.
- evoke4908 2y ago
  If all you're doing is pairing headphones, sure. Developing anything at all against the windows Bluetooth stack is abject misery. It's fundamentally broken. Many API calls are not implemented or just don't work. Several just return wrong data. Core features of Bluetooth like custom advertising data are simply not exposed in any way. My favorite: if your program is listening for devices in the background, the windows Bluetooth pairing menu breaks. Specifically the devices you're listening for will never show up about 50% of the time. If they do, it's likely that pairing will fail with no indication or reason. Additionally, windows 10 does not support simultaneous audio sink and source. You absolutely cannot ever have your phone stream audio to your computer and then the computer pipe it back out to your BT headphones. I'm not sure if windows actually supports audio sink at all apart from HFP (phone call audio). Windows 7 supported this. All linuxes also have had this for over a decade. At work, Microsoft forcibly updated one of our testing machines to W11, and there was nothing at all I could do to make it see our BT device. They are completely bog standard SPP serial devices using BT classic/EDR. Both of which have been a standard part of the BT spec since before W10 was even considered. Windows' Bluetooth stack is an atrocity and an embarrassment. It's outrageously broken and incomplete. It is hands down, no contest the single worst Bluetooth implementation of any OS since windows 7. When linux has better Bluetooth than you, you've really fucked up.
- mschuster91 2y ago
  Unfortunately, that doesn't hold true for anything no longer "under support" from them, and even the "last known supported" driver version wouldn't like to be installed (the MSI errored due to some "blacklisting"), hence the need to buy the TP-Link in the first place. Intel has gone down the drain just as well, I used to recommend their wifi/bt chips a long time, but not any more.
toast0 2y ago
Bluetooth support is so bad, people started making mice that use wifi rather than Bluetooth. I don't know if that's still a thing, but it was around 2012.

vel0city 2y ago

From what I've experienced, any Intel WiFi/BT adapter/BT stack just works out of the box on Windows. Any random USB adapter has a massive amount of variability. There's just so many different chipsets out there with tons of odd quirks.

evoke4908 2y ago
If all you're doing is pairing headphones, sure. Developing anything at all against the windows Bluetooth stack is abject misery. It's fundamentally broken. Many API calls are not implemented or just don't work. Several just return wrong data. Core features of Bluetooth like custom advertising data are simply not exposed in any way. My favorite: if your program is listening for devices in the background, the windows Bluetooth pairing menu breaks. Specifically the devices you're listening for will never show up about 50% of the time. If they do, it's likely that pairing will fail with no indication or reason. Additionally, windows 10 does not support simultaneous audio sink and source. You absolutely cannot ever have your phone stream audio to your computer and then the computer pipe it back out to your BT headphones. I'm not sure if windows actually supports audio sink at all apart from HFP (phone call audio). Windows 7 supported this. All linuxes also have had this for over a decade. At work, Microsoft forcibly updated one of our testing machines to W11, and there was nothing at all I could do to make it see our BT device. They are completely bog standard SPP serial devices using BT classic/EDR. Both of which have been a standard part of the BT spec since before W10 was even considered. Windows' Bluetooth stack is an atrocity and an embarrassment. It's outrageously broken and incomplete. It is hands down, no contest the single worst Bluetooth implementation of any OS since windows 7. When linux has better Bluetooth than you, you've really fucked up.
mschuster91 2y ago
Unfortunately, that doesn't hold true for anything no longer "under support" from them, and even the "last known supported" driver version wouldn't like to be installed (the MSI errored due to some "blacklisting"), hence the need to buy the TP-Link in the first place. Intel has gone down the drain just as well, I used to recommend their wifi/bt chips a long time, but not any more.

toast0 2y ago

Bluetooth support is so bad, people started making mice that use wifi rather than Bluetooth. I don't know if that's still a thing, but it was around 2012.