How to configure Bluetooth Headset in windows XP?

Introduction:
If you are the owner of a Bluetooth headset, you will be glad to know that besides using it with your cellular phone, you can also use it together with your Windows XP PC. However, you may have attempted to pair up the headset with your PC only to find out that the built-in Bluetooth stack in Windows XP Service Pack 2 does not support the headset.
In this article I am going to show you the steps to prepare your PC so that it can work with your Bluetooth headset. I will be using the Billionton USB Bluetooth adapter as well as the Motorola HS820 Bluetooth headset (see Image 1)

Image 1. The Billionton USB Bluetooth adapter and the Motorola HS820 Bluetooth headset
What Are Bluetooth Profiles?
To be successful as a consumer technology, Bluetooth needs to be widely supported by vendors. Interoperability--the ability of different devices (from different manufacturers) to work with one another--is the key factor in securing this broad support.
Version 1.1 of the Bluetooth specification (the current version is 2.0, but most devices are still based on Bluetooth 1.1 and 1.2) has 13 profiles. A profile is a description of a particular functionality, and Bluetooth device manufacturers use these profiles as a guide. With this approach, vendors can be sure that their devices will work with current and future Bluetooth products. Let's take a closer look at the 13 profiles defined in Bluetooth 1.1:
Generic Access Profile (GAP)--Defines how two Bluetooth devices discover and establish communications between each other. The GAP is the "mother" of all profiles, as it defines the modes and procedures that all the other profiles use.
Service Discovery Application Profile (SDAP)--Allows Bluetooth devices to query the services available on other Bluetooth devices.
Cordless Telephony Profile (CTP)--Defines how a Bluetooth device can be used as a cordless phone.
Intercom Profile--Defines how two Bluetooth-enabled phones can connect with each other directly without the use of the public telephone network.
Serial Port Profile--Defines how two Bluetooth devices can communicate with each other by using virtual serial ports. Using this profile, Bluetooth communication can be treated as just another serial communication.
Headset Profile--Defines how a headset can communicate with a Bluetooth device.
Dial-Up Networking Profile--Defines how a Bluetooth device can connect to a Bluetooth-enabled modem or mobile phone.
Fax Profile--Defines how a Bluetooth device can connect to a Bluetooth-enabled fax device, such as a fax machine or a fax-enabled mobile phone like the Sony Ericsson T68i.
LAN Access Profile--Defines how a Bluetooth-enabled device can connect to a network using PPP (Point-to-Point Protocol).
Generic Object Exchange Profile (GOEP)--Defines a set of protocols that applications use for exchanging objects.
Object Push Profile--Used together with the GOEP to send and receive objects, primarily for exchanging electronic business cards.
File Transfer Profile--Used together with the GOEP to transfer files between two Bluetooth devices.
Synchronization Profile--Used together with GOEP to synchronize calendar and address information between two Bluetooth devices, such as a laptop and cell phone.
For other profiles in the newer Bluetooth specifications, refer to the Wikipedia Bluetooth entry.(en.wikipedia.org/wiki/Bluetooth#Bluetooth_profiles)
What is a Bluetooth Stack?
A Bluetooth stack is an application installed on your computer that interacts with your Bluetooth devices. Two Bluetooth stacks are widely in use today:

·         The Microsoft Bluetooth stack, which comes with Windows XP Service Pack 2

·         The Widcomm Bluetooth stack

Most Bluetooth adapters use the Widcomm Bluetooth stack driver. Widcomm (acquired by Broadcom, http://www.broadcom.com) licenses its software to most Bluetooth manufacturers. Consequently, the installation, configuration, and use of different Bluetooth devices on Windows have a nearly identical look and feel.
The problem with the Bluetooth stack built into Windows XP SP 2 is that it has limited support for profiles. In particular, it does not support the Headset profile required to connect with Bluetooth headsets, and hence your Bluetooth headsets will not be able to work with your Windows XP PC.
To overcome the limitations in the Windows Bluetooth stack, you can install the Widcomm Bluetooth stack drivers from the manufacturer of your Bluetooth device. You can download the latest drivers and support software from the adapter vendor's web site. Because each vendor customizes the Widcomm software slightly, you should not use drivers from a vendor other than the one that manufactured your Bluetooth adapters.
Updating the Bluetooth Stack on Your Windows XP Computer
Overriding the default Bluetooth stack in Windows XP SP2 requires some work on your part. The Widcomm Bluetooth driver is not WHQL-certified, and Windows XP uses the Microsoft Bluetooth stack by default (which is WHQL-certified). When you try to install the Widcomm driver, you will get an error message preventing you from proceeding with the installation.
To override the Microsoft Bluetooth stack, perform the following steps:
Go to Start -> Settings -> Control Panel -> System. In the Hardware tab, click on Device Manager (see Image 2).

 
Image 2. Invoking the Device Manager
Under the Bluetooth Radios item in the Device Manager dialog, you should see the Generic Bluetooth Radio and Microsoft Bluetooth Enumerator items (see Image 3). Right-click on the Generic Bluetooth Radio item and select Update Driver. 

Image 3. Updating the default Bluetooth driver
You will be prompted to connect to Windows Update to search for software. Select "No, not this time" and click on Next (see Image 4)

Image 4. Searching for software drivers
In the next dialog, select "Install from a list or specific location (Advanced)." Click on Next (see Image 5). 

Image 5. Installing the driver
In the next dialog, select "Don't search. I will choose the driver to install" and click on Next (see Image 6).

Image 6. Manually choosing the driver to install
In the next dialog, click on Have Disk (see Image 7).

Image 7. Manually choosing the driver to install
Click on the Browse button (see Image 8) to locate the folder containing the Bluetooth software from your manufacturer. In my case, my Bluetooth adapter is from Billionton. 

Image 8. Specifying the location of the drivers
You will notice that the model of the Bluetooth device (in my case it is "CSR USB Bluetooth Device") is now displayed in the Model list box (see Image 9). Click on Next.

Image 9. Installing the new drivers
The installation of the new drivers should now be started. When it is done, you should see the new Bluetooth device in the Device Manager window (see Image 10).

  
 











 





Image 10. The newly installed Bluetooth device
Installing the Bluetooth Software
Once you have successfully updated the Bluetooth stack, you need to install the Bluetooth software (see Image 11). The Bluetooth software can be downloaded from your vendor's web site (or found in the installation CD that comes with the Bluetooth adapter/device).

Image 11. Installing the Bluetooth software
Strangely, after installing the Bluetooth software, my Bluetooth stack reverted to the old Microsoft Bluetooth stack. To get back the updated Widcomm driver, repeat the steps described in the section "Updating the Bluetooth Stack on your Windows XP computer," which should bring back the newly installed Widcomm driver.
Once the Bluetooth software is installed, you should be able to find the My Bluetooth Places icon on your desktop (see Image 12).

Image 12. The My Bluetooth Places icon on the desktop
A wizard will also appear to bring you through a series of steps to configure Bluetooth support on your PC.
Turn on Discoverable mode for your Bluetooth headset and click on the Search Again button to search for the Bluetooth headset (if it has not already been found). When it is found, click on the headset (in my case it is HS820) and click on Next (see Image 13).

Image 13. Configuring the Bluetooth headset
You will be asked for a PIN code in order to pair your computer with the headset. Normally the PIN is 0000, but this is dependent on your device; check your documentation. Enter the PIN and click on Initiate Pairing (see Image 14)

Image 14. Pairing the Bluetooth headset with your PC
The profiles (services) that the Bluetooth headset supports will now be shown (see Image 15). Check the Headset service and click on Next. 

Image 15. Profiles supported by the Bluetooth headset
You should now see the icon for the headset in My Bluetooth Places (see Image 16). Double-click on the icon to connect the headset to your computer. The icon will be changed when the headset is connected.

Image 16. The headset icon in My Bluetooth Places
What Profiles Are Supported?
To view the profiles your device supports, you can right-click on the Bluetooth icon located in the system tray (see Image 17) and select Advanced Configuration.

Image 17. Viewing configuration information of your Bluetooth device
The Local Services tab will show the profiles your device supports (see Image 18).

Image 18. Viewing the profiles your device supports
Configuring Windows to Use the Bluetooth Headset as an Audio Device
Now that the Bluetooth headset is connected to your computer, you need to configure Windows to use it as your audio output and voice input device.
Go to Control Panel -> Sounds and Audio Devices, and in the Audio tab select the Bluetooth Audio item for both the Sound playback and Sound Recording section (see Image 19).
 

Image 19. Configuring Bluetooth Audio for audio
In the Voice tab, select the Bluetooth Audio item for both the Voice playback and Voice recording sections (see Image 20).

Image 20. Configuring Bluetooth Audio for voice
Clicking on the "Test hardware" button does not seem to recognize the existence of the microphone on the headset; however, the computer does redirect the sound output to the headset.
To verify that the headset is indeed working, use MSN Messenger. (I used version 7.0.) Click on Tools -> Audio/Video Tuning Wizard, and set both the Microsoft and Speakers to use the Bluetooth Audio (see Image 21). Click on Next, and you will be able to test the speaker.

Image 21. Using MSN Messenger to test the headset
You will also be able to speak into the microphone. If you can see the color of the indicator changes (see Image 22), your headset is working properly.

 
Image 22. Testing the microphone
Congratulations! You have now set up the Bluetooth headset.

 

12 Basic PC Troubleshooting Questions.

PC Troubleshooting:

 

1. Has the system ever worked properly?

•   Is the system just out of the box or has anyone worked on it?
•  Did this function ever work before?
•  Are the phone lines correctly connected to the modem?
•  Is the phone line connected through a surge protector?
•  Has the modem ever dialed out or detected a dial tone?

Right out of the box issues could point to shipping, assembly or an incorrect image download.  Components or cables may have shaken loose during shipping.  Look for indicators of proper functionality (e.g. o/s loading correctly), or failure (e.g. beep codes) of components.

 2. Has anything changed?

• When did the issue begin?
• Has this been a recurring problem?
• Did this happen today, last week?
• Has anyone added or removed any hardware or software?
• How long has the client been receiving this error?

If the error has been appearing for a long time, the client may have made his own attempts to troubleshoot the issue.  Ask what steps the client has already taken and what he may have done to try to fix it.  The client may have moved the system, loosened something, or missed something while setting up the system at a new location.  Relating the start time to the purchase date, changes to hardware/software and other factors affecting the PC, you may be able to narrow the possible causes of the issue.  

3. When did the system start doing this?

• Was anything downloaded off the Internet?
• Was the system completely shut down and restarted?
• Was e-mail sent or received?
• What was running previous to shutting down?
• Did the system lockup?
• What was the last thing the client did to the system?

This may provide an idea of what has happened to the system.  The client may have terminated a program incorrectly or shut down the system before exiting Windows.

 4. Was anything changed?

• Does the system seem to take longer to boot, to connect, to display a picture?
• Was the machine moved?
• Is the system suddenly in VGA mode?
• Could the sound be muted somewhere?
• Are any of the standard computer noises missing or different?

Changing desktop settings, default printer, resolution, screen savers can affect performance. The abnormal sounds that system makes may indicate where the issue lies.

5. Have you added any hardware or software?

• Is there an external device hooded to the machine (fax, answering machine, surge protector, scanner)?
• Does the user have call waiting, voice mail, caller recognition?
• Where any applications added or files zipped or unzipped?
• Has the client added any hardware/software to the system?

Check configuration; third party hardware/software manufacturers; check Device Manager in Windows – conflicts often occur after adding hardware; try removing recent additions to the system; software additions can cause driver issues, change system files and boot files, or update files causing new issues.

6. Did anyone else have access to this system?

• If so, who used it last?
• Are they available for questions?
• Were any of the system settings changed?

 Do not assume that nothing has changed just because the client has not changed anything.

7. Where is this happening? In one program or more than one?

• Does it happen in Dos, Windows or both?
• What o/s is the client using?
• If the problem is software, is a DOS or Windows application?
• Has the problem software been deleted (or uninstalled) and re-installed?

Get specific – different o/s need different troubleshooting steps and tools.  Take a close look at related programs.  Problems in several programs may indicate an operating system issue or a hardware issue, as opposed to an application error.  Problems in only one program may point to reinstalling that program.

8. Is there an error message?  If so what is it EXACTLY?

• When does the error message appear?
• Are there error messages associated with the attempted use of the program?

Error messages, which sound similar, may point to entirely different problems.  Write down the error message – word for word – and the details when the client receives it.  Enter the exact message into the tools.  There may be a quick solution: If the error is generated by a Microsoft program, check TechNet for the error.  If the error is generated by third party – redirect client to the manufacturer.

9. Does it happen every time or just sometimes?

• Does the same action always bring about the same results?
• If this has occurred before, is it after the initial boot?
• What is the timing of the failure?

Look for commonalities.  They can point to the root cause.  If the issue is constant, you may be able to recreate it and collect more info.  Chances are it may be a hardware setting somewhere or a hardware issue.  If the issue occurs only shortly after the system is turned on or only after the system has been on for an hour, the system may have a heat-related problem.  If the issue happens in only one application, chances are the issue is software related.  Random issues generally are hardware related.

10. Is everything else working properly?

• Have there been problems with other apps/hardware.

 A client may not realize that seemingly unrelated issues may be caused by the same problem.

11. Is the system on a network or attached to another system?

•  Network server may be down, breaking a connection to a needed program or file.
• Try booting without the network, unless the computer is a network server. If it helps narrow the cause. 
• Clients are sometimes unaware of the role of the server or another connected computer plays in certain applications.

12. Are there environmental concerns affecting the system?

• How long is the phone cord (6 feet)?
• Is the system close to any heavy electrical machinery?
• Is the system close to an electrical transformer or high-tension power lines?
• Has there been an electrical storm through the area recently?

Electric motors, florescent lights, fish tanks, power stations, broadcast towers, heavy-duty power lines construction equipment or construction in progress can cause issues with computer systems.  Damaged wall sockets, surge protectors that have taken a hit, or a blown circuit fuse in the house affect the amount of electricity flowing to the computer.