- Jul 23, 2005
- 684
- 0
- 76
what is a bluetooth dongle that you guys use that comes with drivers and software that work with vista
First, this isn't for my phone. . . this is a headset I'm using for my computer. So I hope that clears your admonishment of "goofy" headsets. Yes I do own a mono bluetooth headset I use for my phone but found it inconvenient. I'd rather pay complete attention to the road than have a head set on. If its that important, I'll pull over and answer it.
I digress. The headset I'm using, are for my computer. Original purpose was to get rid of my wired headset that I either trip over, get tangled up in, etc. A better link: http://www.newegg.com/Product/...x?Item=N82E16875982001
So with that out of the way. . .
I did manage to get my headset working. It was vista's fault. Vista has a built in bluetooth stack that is pre-"gimped". It only allows file transfer, mouse, and keyboard. It is not OEM. I am running vista ultimate x64. Widcomm has a set of drivers (heavily modified by users) that will work with virtually any set of dongle/headset/peripheral. There is some need to tweak and patch the drivers to get full functionality. Sound quality isn't that great for what I felt is a bit much for a set of good headphones, but I'm pretty sure its a driver issue. Until Motorola comes out with branded dongle that has native Vista support (currently all of them are on xp only). I'll stick to my el cheapo stick for now.
Here's the Patcher http://www.dev-hack.com/pafile...ndex.php?act=view&id=3
Here's the Drivers http://www.dev-hack.com/pafile...ndex.php?act=view&id=2
Not to keep harping, but I'm pretty sure Vista RTM has a stripped down version of their stack. Prior to the new driver installation, the headset is recognized, and profiled correctly as a headset. But when you connect to the device it asks for a driver. . . which is odd. Why do you think there are so many thirdparty bluetooth stacks running around, namely anycom, toshiba, and bluesoliel? The widcomm drivers contain the missing audio and headset profiles that (vista was missing) needed for the device to connect. Thats why it works. I've never fiddled with XP's native stack. They may very well be more "complete" but as I see it Vista's stack is gimped. I even went to test it to try to find out if you were right, at a friends computer, also running vista ultimate. He uses a blue tooth keyboard and mouse. I plug my blue tooth dongle, paired the two using Vista's stack, viola, and keyboard connected and so did the mouse - but no headset. I agree you definitely have to make sure the hardware id is accounted for, and I eventually had to do that using the patcher program. But . . . that was only used so that the new widcomm driver could see it. The original vista stacker could already see the dongle and the headset.
