Blue Tooth dongle not active after being power off

**Dwaine** · 06-11-2007, 01:47 PM

I looked at the device options. Only the built-in motherboard hubs have the power options. I did set off the power options on all hubs.

Same thing. After a power shutdown, the dongle is not active. The computer does see the bluetooth dongle, and the drivers are loaded. Just not active.

I just hate going to the trunk to pull and re-insert the bluetooth dongle to get it active again.

Any other suggestions? It's a waste of money to get another bluetooth dongle when this one does work, but is inactive after power shutdowns. I'm also worried if I buy a new dongle, I'll have the same problem.

Dwaine

**wywywywy** · 06-19-2007, 12:51 PM

Same problem here despite tried many things.

Will get a new Belkin one to try as they are two a penny on eBay nowadays.

**Dwaine** · 06-19-2007, 05:49 PM

Originally Posted by wywywywy

Same problem here despite tried many things.

Will get a new Belkin one to try as they are two a penny on eBay nowadays.

I wonder why some adapters have this issue as others don't.

**jonessc** · 06-19-2007, 06:27 PM

Originally Posted by Dwaine

I wonder why some adapters have this issue as others don't.

I tend to find different brands use different bluetooth stacks like Microsoft, Wildcomm and some brands like Toshiba use there own as well.

The Belkin use a stack that tends to be the most compatible especially if you plan on using Phone Control software like PHOCO to control your mobile phone via Bluetooth.

Althrough its a gamble buying one it will be a worthy investment plus they have a freephone helpline number that can offer setup advice (At least they do in the UK)

**wywywywy** · 06-20-2007, 03:22 AM

Originally Posted by Dwaine

I wonder why some adapters have this issue as others don't.

I found Belkin to be pretty good in general, as they almost always use good quality hardware components.

For example, not just Bluetooth dongles, but even things like USB hubs, they use chipsets that are many times more expensive just so that all USB ports can transfer at USB 2.0 speed at the same time instead of sharing the bandwidth like cheap hubs. I think you get the picture. They don't always tell their customers about these "attention to details" but in most cases their hardware is quality.

Sometimes their software is a bit weak but in this case since we all use Widcomm anyway so it doesn't make a difference in terms of software.

**wywywywy** · 06-30-2007, 06:50 PM

The Belkin arrived a few days ago.
Sorted the problem straight away!
Since then I've not had a single problem.

**Dwaine** · 08-01-2007, 04:38 AM

I have tried to figure out this problem without much success. The blue tooth adapter works fine if the carpc gets rebooted by myself. If the carpc power supply shuts the computer down, then the adapter needs to be reinserted.

I guess I should buy another usb adapter. I like the MSI one.

**isamu** · 08-06-2007, 05:36 AM

Having the EXACT same problem Dwaine. May have to ditch this Micro$oft Mouse dongle and go with the Belkin.

**Dwaine** · 09-07-2007, 11:26 PM

I bought the dlink bluetooth adapter. The issue has disappeared. Bluetooth is working great now.

Why do some adapters have this problem?

**Clintebb** · 10-09-2007, 11:57 PM

i would try devcon again.. i had the exact same issue, dev manager shows it there fine, but widcomm drivers say its disabled, unplugging it and pluging it back in again works fine. same as when i run devcon it fixes it too. i havent tried restarting a device via devcon but writing a script to make devcon disable the device then enable the device works great. have ou tried this? another thing to note is to make the script pause until the device is disabled otherwise it won't work.

heres the script i made using autohotkey, the stuff in brackets after each line should be deleted, i just added it here to say what each line does. the pause at the end can be made smaller or not there, trial and error will tell you. also you may need to change the code for the device, i used pid_200a as it was part of the pid of my device, and didnt interfere with any other devices. there is info around here for hwo to use devcon.. if you are like me just type devcon /? and work it out from there. i think i used something like devcon find *usb* and that listed all usb devices, and from there looked for something in their codes that was unique to the bluetooth adapter, the * on either side indicated "(any number of any characters)pid_200a(any number of any characters)

runwait devcon disable *pid_200a* (disables bluetooth adapter)
runwait devcon enable *pid_200a* (enables bluetooth adapter)
sleep, 10000 (pause for 10 seconds to give time for bluetooth software to load and enable the adapter before starting xport)
run c:\xport3\xport.exe

anyways if u need any more help just ask.