I know I've been absent from the forums for a while. However, upon updating my Latitude D820 to Windows 7 I have discovered that my 350 Bluetooth card does not function properly. My HTC Touch Pro can sync fine with the laptop via Bluetooth, however neither my mouse nor keyboard wish to function normally. I have tried everything I can think of to get this thing to work to no avail.

If anyone has any info on how they got theirs to work with keyboards and mice I'm all ears. If you have the 350 and was thinking about upgrading to Win7 DON'T at least until Dell gets off their lazy butts and releases some freaking drivers.

just after I removed 7 from my XPS, too, you are slow on the pickup for me to solve it

anyway, just use the Vista drivers. the BT driver architecture hasnt changed (aside from adding audio to the universal support)

Yeah Conda, I had been using the Vista drivers, but after the 5th time installing them it finally took. I was too friggin tired at that point to come back and update. It just wasn't easy on my D820 for some reason. I think it just has something to do with the way the Bluetooth hooks into the D820.

Well, I spoke too soon. Damn thing stopped working again and I've spent a few hours today trying to get it working again. I'll set my Dell BT mouse to pairing mode, pair it with the system but the mouse never exits pairing mode.

Hello,

I had the same problem with my M1730. This is the driver I downloaded from Dell and it worked perfect for my 350 Bluetooth card.
DELL_WIRELESS-370-BLUETOOTH-_A02-1_R235898.exe

Thanks for the tip Metalman, but for whatever reason that driver stalls at the "Wireless Switch" prompt. I'll switch the Bluetooth on and off several times and nothing.

It's weird because it's JUST the keyboard and mouse that don't seem to work. My Cell phone can link up fine, though I haven't tried my Canon ip90 yet.

Sorry to hear that Evil. With my M1730 this driver works better with win7 then when I was using vista with the Dell drivers.
Keyboard and mouse is about the same, but my Motorola HT820 works much better with these divers. With Win7 Microsoft drivers I had to first turn on my headset then start my computer for Bluetooth to see my headset. Now I can start my headset any time and Windows will see it.

I have recently moved from XP Pro to Windows 7 on my Dell M65 laptop. The upgrade adviser gave a green check mark for the Dell Wireless 350 Bluetooth module.

Noted under XP Pro, the module performed flawlessly.

After installation of 7, the default Microsoft driver did not allow it to function correctly, so on advise from Dell technical chat, I installed the Vista driver from dell.

It works - kind of. Erratic is the term best used for describing what's happening.

The day of installing the vista driver - my BT mouse would connect, then after going idle would lose the connection, and I would have to manually add the mouse again. Later that night, I could not make the laptop recognize the mouse at all. After giving up for the night, I shut down.

Today, was different - the module would disappear from the device manager list and reappear, (the blue indicator light blinking on and off accordingly, and the unplug/plug-in device sound played) sometimes in cycles, the mouse would reconnect on its own and all is good until the module would disappear off the device manager list again then reappear.... and reconnect the mouse on its own.

On advise from Dell technical chat, I shut down and removed the trim piece above the keyboard and unplugged the module, plugged it back in and made sure the tiny cable was firmly in place. After powering up, I still got a few "disappear/reappear" cycles, now it is stable.

It's been running for two hours now with the bluetooth behaving normally.

I am assuming Win 7 does not 100% like the vista driver for this bluetooth module.

Since the module is falling off the device list and then reappearing and functioning normally until the next time it drops off, I think maybe it could be the tiny connection cable, or even the module itself going wacko. - but I think not since only two days ago it was flawless under XP Pro - so I think the chances of the cable or module going bad during windows 7 installation are slim -- but still a possibility.

Also - to rule out the mouse, I connected my cellphone and the same thing as the mouse experiences.

Anyone have any ideas?

How can a bunch of 350 module owners ask Dell to release a driver for Windows 7? I understand the module is aging, hell, my M65 is now four years old.

which driver are you using? I'm using R226750 (under x64) and haven't had any problems with it myself

I am using R142181. That was the only one listed for my service tag for Vista 32-bit for the 350 module.

The R226750 driver you mention is for a much newer 370 mini card.

I dont even think I could try to use that driver because the hardware is so different between the 350 and the 370.

yeah it's for a 370, but works fine for the 350, thats what I have as well (well, 355). I think it was some information I found in the Dell forums that suggested that one in particular originally. the stack itself is a generic stack, and will pretty much work with any Broadcom-based Bluetooth device (which the Dell Bluetooth modules are).

works great for me. I'm on the 3rd time installing 7 (first for the launch party thing, then I took it back off because I was going to use that license for another machine, then I bought an upgrade for my XPS, and then just last week I got a new hard drive so did a clean install of 7 again), worked great for me every time.

Oh wow, I will give that one a try and report back!

Edit: 10 minutes later.....
There must be a difference between the 350 cards and anything newer (like your 355) because the R226750 driver stalls at the 'wireless switch' screen. I flipped my switch off then on and Win7 went ahead and installed the default microsoft driver while the Dell driver screen just sat there. Same as the other guy experienced above with a different 370 driver.

I will go back to the R142181 driver, as it 'settled down' and hasn't been acting up.