Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I connected my Philips SHB9000 bluetooth to my Windows 7 (64 bit) for the very first time, it worked well. I had to manually change the default playback device, but otherwise it worked.

Then, when I start up my computer from standby, it's nearly random when I can reconnect or not. My last option is to remove the bluetooth device and reconnect it. But now, even that doesn't work.

The sad thing is, this used to work better on Windows 7 beta.

Windows Update has a new driver which fails to install. Searching for this driver yields nothing. I thought all vendors had an official site for their drivers? Well, Philips seems to have none.

If there is no answer to this problem, my advice is to NOT buy this headset. It's good looking, the sound is nice, but what need do we have from that if we can't use the bloody device?

share|improve this question

migrated from Feb 7 '10 at 16:41

This question came from our site for professional and enthusiast programmers.

I had similar issues with my SHB9000 and windows 7 x64 and though they seem resolved now that I installed the latest ASUS Bluetooth drivers, I did notice some interesting things;

1) The ACER bluetooth drivers did install, but messed up everything. All the devices exposed by the headset were there all the time, even when the headset was off, and the sound defaulted to it all the time even if it was nowhere near the laptop. The drivers installed fine though, no conflicts.

2) The ASUS drivers, specific for the BT-253 chipset, worked fine, even though the ACER ones claimed to be a newer version (I had to manually uninstall both the software and all drivers).

3) Most importantly, while experimenting, I noticed that the headphones switch from the proper stereo protocol (A2DP) to the crappy wireless headset one (the mono sound, whatever the name is) whenever I activated the microphone in some way or another. Currently, the headset is present as both a playback and recording device in the audio settings, whenever it is turned on. The recording device is the default recording device when the headset is turned on. As soon as I turn on ANYTHING that captures microphone input (even the "Recording" tab in the "Sound" settings), it switches to mono sound in order to enable microphone input. If I DISABLE the wireless microphone, or switch the default to the built-in microphone, it goes back to proper stereo sound.

In short; if you're experiencing this, try disabling the wireless microphone in the sound settings, or set the default one to another microphone. As long as the microphone on the headset is not in use, it will use A2DP and the sound quality is fine.

share|improve this answer

I had the same problem, I have a sony vaio computer which only comes with the standard Microsoft drivers. I installed this one ->

reinstalled the shb9000 again, and worked

share|improve this answer
I wish I could tick off this as answered, but it's not. I installed the above drivers, and I think I traded one problem with another. Now my headset gets connected, but receives no sound. – Thomas Eyde Mar 22 '10 at 1:00
Update: My headset adds itself as two playback devices, one mono and one stereo. The mono one can be reconnected, but not the stereo. Which is the one I want. – Thomas Eyde Mar 23 '10 at 15:18

You must log in to answer this question.

protected by studiohack Apr 27 '11 at 1:09

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .