Wow, if only Motorola had said that on the box. Wouldn't have wasted my time with it. Not only is it extremely uncomfortable, it's also flawed. Oh good!

Is there any way to make this work with the 355 Module?

I'm using an MX1000 and I'm hoping this will fix a couple of problems:

a) The mouse randomly disconnects while gaming, and it's very involved getting it to reconnect.

b) It behaves very strangely following a system standby with the Dell drivers.

Im currently using the Widdcom drivers with the 355 and it works great with my jabra bt620s (a2dp and headset), Logitech mouse (not sure which model), and my motorola phone v551. Try that stack and see how it works!

While installing the Widcomm software I get this message during the "Installing Bluetooth Kernel..." phase:

No Bluetooth device was detected. Please make sure that your Bluetooth device is plugged in properly and click 'OK' to continue installation. Click 'Cancel' to continue installation without the Bluetooth device.

So I click Cancel and it detects a COM port and a Communications Port and a couple Audio things, but nothing that would indicate that I could connect my mouse. What's my next move?

Also, although I can't get to that step yet, I don't have the Logitech dongle. Is that going to be a crippling problem in trying to use my MX1000?

Update: There's now a Bluetooth icon in my tray again, but upon Right Click it says "Bluetooth Device not found." Also, there is an unknown BCM2045 in the device manager.

Go to http://mikestein49.com/Files/ and right click/save the jabra.iso (scan it if you want but its legit). Mount the iso and install that driver. That should work. If not, I duno.

You didn't say it, but do you know about pairing a bluetooth mouse?

Right-click on the bluetooth icon and put it into search mode AND then press-and-hold the pairing button on the bottom of the mouse - hold the button in until the software registers it.

wwing, thanks for the effort, but during the installation I get the error:

"Please insert the disk: 1"

There must be some protection on that disk or something.

Just to clarify, the 355 Dell download uses Widcomm software, but it still uses the Broadcom driver. That's what this thread is about, right? Using an actual Widcomm driver, and not just Widcomm software?

I figured it out how to use 4.20.01(T) with my Dell Bluetooth 350.

1. Download the 4.20.01(T) bluetooth stack from http://aps.toshiba-tro.de/bluetooth/...s&download=3ww
2. Run the installer. Tell it to ignore the Windows driver warnings. After a while, it will tell you to press Fn+F2 to turn on the Bluetooth card. Even if your wireless functions are on, it will keep prompting you. So go ahead and cancel out of the installation.
3. Reboot
4. Go to your device manager (right click on My Computer->Properties, select the Hardware tab, press Device Manager). (Or Start menu->Run->devmgmt.msc)
5. In the Universal Serial Bus Controllers list there should be one that is marked by a yellow warning triangle. Double click it. It'll say that the device driver isn't installed. Keep this window open for a bit, you'll need it later.
5.9 Backup C:\WINDOWS\inf\tosrfusb.inf in case you mess it up in the next step. Not that it'll do you much good now anyway.
6. Edit C:\WINDOWS\inf\tosrfusb.inf in Notepad or equiv. Where it says Rfusb_DellDevice (%TosrfUsb.DeviceDesc87%=Rfusb_DellDevice, USB\VID_413C&PID_8120) replace that with "%TosrfUsb.DeviceDesc87%=TosrfUsb_Device, USB\VID_413C&PID_8103". (no quotes) Find all instances of "8120" and replace them with "8103".
7. Save the file.
8. You might need to trash tosrfusb.pnf. Maybe.
9. Go back to that device window you opened earlier. Click the Install Driver button. Let it search automatically. It'll find two matches. Pick the second one ("Dell Bluetooth USB adapter").
10. There might be some other associated "fake" devices that the Toshiba stack will ask you install after installing the driver. Let it install them. Hopefully things work. If you don't have a blue antenna icon in your systray, you might need to reboot.

Moo.

So far no Joy

Absolutely,couldn't agree more,BT has been an enormous waste of my life.
The sooner this technology is replaced,the better.

I'm confused. I thought the TM350 used a CSR chip and a Toshiba stack, while the new TM350 uses a Broadcom chip and a Widcomm stack. Since the 355 module dumps the 350's problematic Toshiba stack in favor of Widcomm, the TM355 seems to be a big step forward as far as this thread is concerned (assuming the 355 is available from Dell spare parts). Or am I missing something?

With the 355 module, what u need to do is first install the dell bluetooth drivers. Once they are installed, reboot the box, but don't click on the bt icon that comes up. This will install the dell widcomm stack, which is not what u want.

Instead, go ahead and install the newer widcomm software over that. The broadcom drivers will be installed already and the new widcomm sw will then recognize the bt module. Make sure to run the patcher on the new widcomm stack as well.

I found the dell widcomm stack very laggy with my logitech bt mouse. The new versions are much better.

The anycom widcomm stack works very well for me and seems to be very new. It also uses the broadcom bcm2045 chip.

http://www.anycom.com/products/bluet...36&tab=support

A Few things I want to say. This thread has been extremely helpful, for the most part in getting WIDCOMM drivers, I hate the new TOSHIBI drivers. I have a 9100 upgraded from a 300 to a 350 module.
---
I initially had the problem where I could not get setpoint to work with my my module, but after doing many installs and uninstalls of drivers, I eventually got it working. I think what did it is after I installed the modded WIDOMM drivers I downloaded and installed Setpoint 2.6, which allowed me to connect and pair my devices with setpoint (don't pair the equipment with windows because then they won't pair with setpoint). I then configured my mouse and keyboard and upgraded to the Setpoint 3.10. It works very well.
---
Now I have one slight problem with the Blue[tooth] Light. Yes, I can not turn mine off either; it's even stays on solid in Stand-by... I have no disable option on the icon in my tray. Some say to press FN+F2. That may work, but it will also turn off my WLAN connection.
Does anyone have any input on how to get everything set up in a way that I can get a disable option on the tray icon?
---
Lastly, has anyone tried that WIDCOMM 5.1.0.2100 that 'bugmenot' mentioned above? I would, but I'm just glad I have my Logitech equipment working as it's supposed to right now.

Here's how it appears so far since I got my 350 and MX5000.
Turning off my keyboard for about 9 hours a day doing a lot of typing and some gaming, the keyboard battery level is still on "good" and hasn't changed.
Using my mouse moderately to moderately-high and leaving it on all of the time, the battery lasted a week.
My Dell350 drivers also lasted a week....
...I left my computer on all night, everything was working fine, I woke up this morning and nothing worked. My Truemobile350 drivers were nowhere to be found in device manager. It just randomly shat itself, and when I restarted the blue light didn't even come on.
To keep it short, it was a driver problem and the only WIDOMM driver I've found on this thread that works is the one listed at the very start of it with the license patcher.

After wasting 4 hours of my Saturday that I'd have wasted anyways I can assure you these things from my trials.
1) The Anycom driver listed above does not contain drivers for the 350 card.

2) You MUST have the Logitech bluetooth dongle plugged in while installing setpoint or the program will not give you option to connect your devices. (Note to you people pairing your device with Windows, you can only use the keyboard functionality and won't be able to use the LCD features or customize buttons)

3) Aslo, after you get your 350 bluetooth card working again, you may have to reinstall Setpoint again, but that may not be the same for everybody.