i just purchased a motorola HS810 bluetooth headset and a USB bluetooth adapter for my laptop. i'm using softphones a lot and i want to be able to do my calls without wires. the usb adapter appears to be working fine. it's using the generic windows xp sp2 drivers and i can pair the headset with the computer. it shows up as a moto HS810 headset on the pc. no problemo. it's using com5 and com6 for in and out. but i can't actually get any signal in or out of it. i know i'm on the bleeding edge here. haven't been able to find any help on the microsoft or bluetooth or motorola sites. my guess from reading some windows CE forums is that i need windows to create an audio driver for this thing somehow - so it knows that there's a device to and from which it can route audio. for example, i have a logitech usb (wired) headset, and when i plug that in, it shows up as a new audio device that i can select in the "Sounds and Audio Devices Properties" from Control Panel. anybody fallen off this cliff already and care to share? grazie tante, doody.
Doody, my first thought would be that you need a Motorola driver. But, you've already checked out Motorloa's site and got nothing, you may want to Google your headset to see if anything comes up. Also, try this site full of device drivers: http://www.driversguide.com/. I also had a bluetooth issue earlier, but it wasn't an audio one. Early this year I tried to pair my bluetooth HP GPS receiver with my notebook PC equipped with a Targa bluetooth adaptor, so I could use MS Streets 2005. For some reason, my notebook couldn't link up with the GPS receiver, though the receiver works perfectly with my iPaq with built-in bluetooth. Didn't have the patience to figure out why, so I returned the Targa adaptor. Bluetooth works great with cell phones and PDAs, but I guess it still has ways to go on PCs. Good luck!
anybody have any additional thoughts on this? is there some generic windows "speaker/mic" device i can leverage and point at these two i/o com ports perhaps? has anybody here done this with a Windows CE/Mobile/PocketPC device and care to share how this final step works? tia, doody.
fyi/fwiw in case somebody else ends up in this morass. the problem is that with XP SP2, microsoft shoves its bluetooth driver at any bluetooth setup. this is fine unless you need to support a bluetooth profile that MS has decided (for whatever odd reasons) to not support - such as, drum roll, the headset profile. so like in the days of old (windows 3) where you had different TCP/IP stack vendors, there are currently multiple bluetooth stack providers. MS's solution works if you want to do the things MS supports. if you want to do something MS doesn't support, then you're stuck where i was. here're the gory details/instructions on how to make things work. the widcomm drivers seem to come with just about every bluetooth radio (including my generic compusa one). http://forum.skype.com/viewtopic.php?t=10822 doody.
