However, I have been experiencing this issue for a very long time over different types of laptops and headphones. Kind came across this thread due to the fact I am currently using TaoTronics SoundLiberty 79 as well. And while doing so deliberately throw normal Bluetooth users under the bus as collateral damage. The other scenario is that you're very aware of the problem and have taken a design decision to opt for some fancy functionality provided, outside standard specifications, by some device manufacturer. So, I would ask that you stop pretending that this is a unknown issue and solve it. And this is what is not working for various devices with the standard communication device driver. In this case I start to suspect that Microsoft developers are going past the standard "communication device" api's by some reason. The idea with typed devices that add hear to a specification, is that it is registered as an enabled device and works as one. "Hi all - have you confirmed that you're using Teams enabled devices?" This comes out very strange to me. Again, with the wide range of devices, it is not probable that there is nothing else but a teams problem. There is no chance that Microsoft is not aware of the problems. So base line is: With the wide range of devices and number of people that experience these problems. Only in this thread a vast number of users give evidence that a vide range of different devices from different manufacturer, that is working great for other purposes will just not co-operate with teams. But with teams there is a whole different story. However, that problem aside, most or every application will work fairly good including microsoft skype. As you state with the article most pc Bluetooth communication devices works bad with the pc because of the Bluetooth specification and the fact that the devices only host one chip. I have been using several Bluetooth devices with both my telephone and several laptops. No deflection intended" but it is hard trying to look past the ignorance.
0 kommentar(er)
