OK, so I ventured off into the world of Skype recently. Here's the first thing I learned: Bluetooth headsets on Windows XP SP2 suck.
But all is not lost. I finally cracked the code on my particular combination.
What I'm using:
Motorola HS820 Bluetooth Headset
Cyber-Blue Bluetooth EDR v2.0 Dongle
I first tried using it with the included software which comes on a little mini-CD with virtually no identification. It just says Bluetooth and V2.0 on the CD. No company name identification, no nothing. You can see that CD and the dongle over to the right.
The software on the CD sort of worked but not really. It worked backwards with Skype. When you connected the headset and it was ready to talk, upon dialing a Skype call it would disconnect. How annoying!
Then I tried switching to Microsoft's Bluetooth drivers. What a crock that was. That was when I learned that in their infinite wisdom, Microsoft does not support the headset profile in their Bluetooth drivers. How sucky is that?
Cyber-Blue's website was useless. They're an OEM and this unit is just their generic house model that's sold cheap. (What was I expecting from a $9 purchase at Geeks.com?) They don't have any supporting files or anything on their site.
So, then I figured I'd check out the software provider's website - Windigo Systems. Linked from their homepage is a Support page. On that page they provide "Blue Manager 3.1c". Well that would be great except for the fact that what I had on the CD that came w/ the dongle was 3.2b and I certainly wasn't going to chance using even older software.
Off to the Google I went again. I found few references to Blue Manager software. The only thing I found was another OEM who was offering Blue Manager 3.3 if you used a form to request it - problem being that you had to own one of their devices and report it's serial number to get the software. Stinkie.
Back to Windigo I go. This time I noticed they had a support email address listed. "What the heck" I figured. At least I'll have spent $9 and tried. To my amazement I got an email back in about 4 hours with a link to Blue Manager version 3.4d. Now why didn't they have that linked to their support page to begin with!?! Oh well. At least they were nice enough to email me back (in broken English, so I assume they're staffed with native Asian speakers so they can work w/ their Chinese and southeast Asian manufacturing partners).
For some reason I was unable to download anything from their website w/o getting a notice from my unzip program that there was a CRC error and the file was corrupt. Poey. But I was able to download it to my office PC (thanks to Logmein) and FTP it to myself w/o problem. I still have no clue why I wasn't able to download it over my Sprint/Embarq DSL connection. No matter, I had the software now. There was no stopping me. Or so I thought.
I begin to run the software. It wants to uninstall all the old software. Kaboom. BSOD! Yep, a nice blue screen of death. So I unplug the USB dongle and reboot. The second time I ran the software it wanted to uninstall the old software, so I let it try again. No BSOD that time. Oh, but it required the obligatory reboot before it could finish. I let it reboot then started the installer again (manually b/c it wasn't smart enough to start itself back up). Now the real install begins. It gets 3/4 of the way through the install and it tells me it can't finish without my Bluetooth dongle being plugged in. So I plug it in. Windows installs it again from scratch as if it were a new piece of hardware. Kaboom. BSOD AGAIN! Bollucks!
Ok, so I reboot with the dongle attached this time. Windows seems happy when it comes back up. I have the nice Microsoft Bluetooth icon in the system tray. I start the Blue Manager 3.4d installer again. I am asked by the software if I want to install the COM port for VoIP and data or for VoIP only. Since I don't have a Bluetooth capable phone yet, I go with VoIP only. The installer chugs along. It gets all the way through this time and the Microsoft Bluetooth icon disappears. That's the signal that Blue Manager has taken over control. Oh but wait... the software needs to reboot my computer again.
So... here were are 5 reboots later - 2 of which were planned. The software appears to have successfully installed that last time. I am able to start Blue Manager for Skype. Joy, it's a 2 step process to start Blue Manager so you can use your headset. Instead of automatically starting when Windows does - there's not even an option for that - you have to start Blue Manager for Skype and THEN start Blue Manager 4.3d so you can actually use the headset. Annoying but livable.
I put my Motorola HS820 into pairing mode (how stupid were the Motorola engineers for putting every single function on this thing except volume - and I bet they tried that in development! - under the control of the single button!). If you don't master counting your button hold time, you're destined for failure. Then I started the discovery process in Blue Manager by hitting Refresh. After entering the pairing password - "0000" - they paired. Yippie.
Now for the real test. Can I make a Skype call. It took a little fiddling b/c the new Blue Manager 3.4d software did not automatically set the headset as the audio device in Skype. To do that, in Skype go to Tools -> Options and set Windigo Audio BT device as the default for your incoming and outgoing audio. Once that was done, I was able to just hit the button on the Motorola HS820 and Blue Manager kept a connection open to the headset. It even kept the connection open after I hung up the Skype call.
All is not perfect in this arrangement. I can't use the button on the headset to answer or disconnect a Skype call like you can on a cell phone. You have to acknowledge the call using the keyboard and mouse as always. And if you forget to connect the headset by pressing the button before you answer the call neither party can hear anything.
The good news is that battery life for the Motorola HS820 is about 6 hours of talk time. So it's possible to just connect the headset while you're sitting at the PC and leave it connected. That also helps with knowing when calls are coming in. Unless you set the Skype option to "Ring PC speaker on incoming call" you won't hear anything to let you know a call is coming in if you'd forgotten to "connect" your headset or if the Bluetooth connection dropped (in cases like when you left the PC to go to the bathroom w/o taking the headset off).
Hopefully Skype will get a clue and help these headset folks or Microsoft get a grip on Bluetooth headsets. They way the work now is manageable. But most definitely not optimal.