Post by Yousuf Khan Post by Yousuf Khan Post by Yousuf Khan
Been trying to get a BT speaker to work on my laptop for a while. I
BT receiver plugged into a USB port,
I hope you mean a BT transmitter?!
Really?!? That's what you're going to start with?
Post by Yousuf Khan
Don't you have any directions with the USB device? Like a driver CD
or a web site to go to for the download of drivers if needed?
No, these things don't come with any such things as they're supposed to
work straight out of the box. And for the most part, it did do that with
At this point, we don't know what speakers are involved here.
The speaker would have no way to enter a PIN, and perhaps
a single button both enables pairing, or clears the memory
of previous associations.
In the old days, you might have used a pin of 0000 or something.
The speaker should have A2DP, and may have aptX (better
quality, proprietary). Bluetooth stacks vary as to what
profiles they support, and I don't know where aptX gets
supported exactly. I can't imagine a speaker being "only
aptX", as the user would have a lot of trouble using it.
Maybe you could use Linux BlueZ to check out the speaker
from the PC side, just for fun. It won't really tell
you anything. But BlueZ does have the odd debug utility,
so it may be able to give you more background info
about what is happen, than the "buttery smooth but
useless" Windows approach. When my attempts to set up
a Piconet in Win10 were stymied at every step, I began
to realize just how poor the stack, and the planning was.
Wireshark seems to have an hci option on Linux, but I don't
know if anything exists for Windows. Wireshark also claims
to have dissectors for various stacks, so you should have
a way to label the packets when they arrive.
Linux had some other utility that would dump info
about the current Bluetooth state, but I can't remember
the name of it.
Sometimes articles like this, reveal "hardware state"
issues that may also apply to Windows. For example,
there is a command here, to tell your device to
drop an existing pairing (so that, presumably, Linux
could pair to that MAC address instead). But that would
not change what Windows remembers about BT devices.
And here, some people try to get at the keys on
the Windows registry. So something in here, will
show the pairing activity that has already gone on.
I take it the quantity on the end, is a unique MAC address.
The MAC used when networking on BT. The value might be
a representation of a 128 bit quantity.
"HERE IS THE FIX:
Remove the device from your PC (Devices and Printers)
click on Add a Device and set your bluetooth to pairing mode
when your device shows up in the list DO NOT HIT NEXT just yet
Instead right click and go to Properties and select ALL the
options for the services and after it install everything
it will work for you.
Also, please don't forget to change your default sound device
in Control Panel and Sound.
So apparently something in Add a Device, is going to show
profile options ? Like A2DP or aptX ?