NotebookForums.com › Forums › Notebook Manufacturers › Dell Notebook Forums › Dell Home (Inspiron, XPS, Studio) › What's up with Dell's Bluetooth drivers?
New Posts  All Forums:Forum Nav:

What's up with Dell's Bluetooth drivers? - Page 10

post #181 of 266
d/l widcomm version 5.1.0.11 and copy the btwusb.inf into version 5.1.0.21, then once u go and install, it will recognize the dell 350.


Quote:
Originally Posted by Lobo_wolf14
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.
post #182 of 266

Unknown file location

[Exactly what directory does the files get transferred to? Unable to fine the svcpackfolder in the driver.


QUOTE=KAROLOYDI]I have the truemobile 350 on mine. With Microsoft drivers my mx5000 (Mx5000 keyboard+mx1000 mouse) desktop works but I can't access some of the advanced features. With widcom drivers I can acess all the advanced fatures as well, like customising buttons, etc. The widcomm are also better with my phone. With them I can see the memory stick as a drive through bluetooth and access all folders. With Microsoft I had to send files one by one.
Quick guide on MX1000
1. Update the Truemobile firmware to the latest version. To do this download the Dell Drivers. Extract them using winrar. Look inside for the 2KXP directory, and inside of that, the DFU directory. Run dfu.exe. It takes around 10 minutes.
2. Download Widcomm drivers
http://www.megaupload.com/?d=BJ0NDHW6
3. Mod Them so that they can work on the truemobile
http://www.megaupload.com/ru/?d=HKH6KNHJ
Copy all files from 'svcpack' in the Patch to 'svcpack' folder in the drivers. It will replace one file and also copy 4 more files.
4. Uninstall Toshiba Bluetooth Drivers from Add/Remove Programs (Only if you are using the dells default drivers. Otherwise go to next step 5)
Restart. I think Windows will go ahead and install the Microsoft drivers without asking you after restarting.
5. Remove the Microsoft bluetooth support by following these steps:
http://support.microsoft.com/default...b;en-us;889814
Restart
6. Click cancel when the new hardware found wizard appears. Go to Control Panel>Administrative Tools>Services. Right Click on Bluetooth Support Services, select properties and change it from Automatic to disabled. This will remove the Microsoft driver's Bluetooth icon from the control panel and tray.
Restart
7. Click cancel when the new hardware found wizard appears. Install the Widcomm Modded Drivers.
Restart
8. Plug in the Logitech Hub and install the mouse drivers.After that it will tell you it needs to restart.
If windows is only recognising your logitech bluetooth hub as a "Generic USB Hub" then press the red button on your receiver while plugging it in.
9. Remove the Logitech Hub after restart and connect the mouse using the truemobile.
Done
10.HOW TO REMOVE THE ANNOYING "MY BLUETOOTH PLACES" ICON FROM THE DESKTOP AND "MY COMPUTER" THAT DON'T WANT TO GO AWAY!
Open up the registry editor (Start> Run> regedit). Browse to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\Name Space\{6af09ec9-b429-11d4-a1fb-0090960218cb}
Delete it. If you are paranoid, choose to export it first (right-click> export), so you can add it back later if you need to.
Restart your computer for the changes to take effect.
11. How to remove the "My Bloototh Places" shortcut from "My computer"
Download TweakUI.
http://download.microsoft.com/downlo...ertoySetup.exe
Install it and run it. Go to "My Computer" (in TweakUI). Untick "My Bluetooth Places". Click Apply. I think you can remove the desktop icon too with this. But I couldn't test it cause I had already removed it.[/quote]
post #183 of 266
so the dell drivers are horrible
Any1 tried BlueSoleil from IVT Corporation ( www.bluesoleil.com )
post #184 of 266
Heres a link to a thread for the latest drivers (I wasnt sure if I could give a direct link to the drivers, so I just gave a link to the thread)

Widcomm 5.1.0.2100:
http://forum.gsmhosting.com/vbb/arch...33952-p-1.html

They will work only with the new truemobile 355 that has a broadcomm chip. Not with the truemobile 350 and 300. The latest widcomm that works with those is 5.1.0.1100. Heres a link to the thread for 5.1.0.1100 http://forum.gsmhosting.com/vbb/showthread.php?t=294359. The following instructions should also work for the 350 and 300 with the widcomm 5.1.0.1100


1.Uninstall the previous drivers.
2.Restart
3.When the new driver found wizzard appears select install automatically or cancel. It makes no difference (at least for me)
4.Install the new drivers
It will say "Bluetooth device not found. Press cancel and it will continue installing the drivers
5.After it finishes copy the licence patcher in the driver's folder (It should be in program files folder with the name "ANYCOM" or "Thinkpad" or "Widcomm", depending on which driver you have installed) and run the patcher. Select your card from the list and click save.
You might have to restart before the card starts to run properly.

If you have the MX5000 bluetooth and mouse and you cant customise the buttons then try this. Use the licence patcher to install the drivers with the logitech dongle. After you make sure everything runs fine (you might need to install the setpoint drivers again) use the licence patcher to install the trumobile card, remove the logitech dongle and connect the mouse and keyboard.


Troubleshooting:
Everything went wrong when I tried to install my new Truemobile 355. It probably wont be as bad for all of you, but I think I got all possible problems anyone could have with installing the drivers, so I am gonna share all my grief with you hoping it will help some of you.

1. When I put the new card in, it wouldnt appear anywhere. Not even in the BIOS. The reason was that in the BIOS there is a "BOOT POST" option. I had it set to minimal. Set it either to automatic or thorough.
2. After that when I tried to install the new drivers (Widcomm 5.1.0.1700) the trumobile 355 wouldnt appear on the list of the licence patcher. I went to the device manager, expanded the bluetooth (pressed the + sign), right clicked on the Truemobile 355 and selected "Update Driver". Then I showed the wizzard where the dell's drivers are (They should be somewhere in C:\DELL). It said that this driver is older than the one I currently have and asked me if I wanted to continue anyway. I said yes. Then ran the licence patcher and the truemobile 355 appeared on the list. I selected it and clicked save. Then went back to the device manager and updated the driver again. But this time I showed the wizzard to where the 5.1.0.1700 drivers were installed. And installed the latest driver again. This time it worked.
If you have the truemobile 350 or 300 you can try installing the widcomm 5.1.0.2100 and then update the driver and show the wizzard where the 5.1.0.1100 drivers are. Maybe it will work.
3. I tried to install a newer driver again (Widcomm 5.1.0.2100). The only problem was that this time it would install the wrong driver all the time. I dont remember the exact name, but it was some letter and numbers, something like BCM2 or something like that. It would still install the wrong driver after following the instructions in step 2.
I looked in Add remove programs. There was something installed there that was named "Windows Broadcom Bluetooth Drivers". I uninstalled that and then followed the instructions in step 2 and it worked.
Now I have the latest drivers, after struggling for 3 days.lol

4.About the problem with lag when using mouse, keyboard and headset at the same time.
I bought a logitech bluetooth 1.2 headset some time ago. My reasoning was that 1.2 bluetooth wouldnt take so much bandwidth and it would leave some bandwidth for the mouse and keyboard. I was completely wrong. What was happening was the opposite. The mouse will have to wait longer until the headset sends and receives the data. And this is the reason for the lag and the crackling sound on the headset.
I bought a new headset. Its really cool. I suggest it to everyone. Its Nokia BH-802 (BH-800, BH-801 and BH-803 are more or less the same). Its Bluetooth 2.0 EDR. And its really small. And it doesnt need the earloop to hold it (although it has one if you want it). So it doesnt hurt your ear.
The difference between the logitech one and this one is significant. It wont be perfect enough to play Battlefield 2 or counterstrike source, but if you want to use skype and do other things at the same time its perfect.
Another option I read about is use two different bluetooth hubs. And use the microsoft stack with your mouse and keyboard and the widcomm stack with the second bluetooth hub for the headset. My problem is that the microsoft stack wont recognise the truemobile 355 (but I think its cause I messed up the drivers too much. It might work for you). If anyone has succesfully installed the trumobile 355 with the microsoft stack please let me know.

Thats all folks! Hope it helps
post #185 of 266
Wow just updated to 2100 and all I have to say is what a royal pain in my a$$. Not a quick and easy job in the least. I had to use portions of instructions from 4 different forums and in the end had to make up some steps on my own. Maybe I'll put it all together in an easy tutorial so that it will be easier for others in the future. All I wanted was to be able to use my bluetooth headphones and now I can. I wonder why Dell didn't think to include that ability when they went to the 355 module and got ride of the 350 module which had a2dp support.
post #186 of 266
whats the newest BT drivers for the dell 350 card
right now i have the 5.0.1.802 drivers..
post #187 of 266
Quote:
Originally Posted by jamescardenas07
whats the newest BT drivers for the dell 350 card
right now i have the 5.0.1.802 drivers..
The last one for truemobile 300/350 is widcomm 5.1.0.1100.

I did it! No lag! I installed my trumobile 350 again. I am using the trumobile 350 with the microsoft stack and the logitech bluetooth hub with the widcomm 5.1.0.2100.

I can do everything now. But no customising of the mouse keys, and the keyboard lcd is not displying anything. Just the date, time and temperature.

I ll keep it this way. I like it. The lcd was taking too much battery.
post #188 of 266
I just tried installing the Widcomm stack for my Truemobile 350 and when all is said and done an I have run the patcher then reboot and right click on the BT icon it says "Can't find bluetooth device". Any ideas?
post #189 of 266
Right now I have the 355 Truemobile. I installed the Dell drivers, then patched the Anycomm drivers and installed that stack on top of the Dell. Right now in device manager it says under the device manager, the 355 is using driver version 5.0.1.2069 which is what comes with the Dell package, but then when I click on details it shows the 5.1.0.2100 that comes with the Anycomm and the Bluetooth Configuration utility shows 5.1.0.2100. So is this working properly and in line with what others have done? Thanks.
post #190 of 266
I've got the same problem. After installing Widcomm driver, my Truemobile 350 is not found too.
post #191 of 266
Need help desperately...

was running Dell TM350 module on my PWS M70 with the Toshiba stack. Have all this fancy Logitech bluetooth equipment that I could use as generic devices but not customize as Setpoint would not recognize any of it without a supported bluetooth stack (ie MS or Widcomm). So... I uninstalled the Toshiba, prevented the MS stack from self-installing, installed the patched Widcomm stack (1100 version). Everything works flawlessly as Setpoint now recognizes everything and allows for full customization.

Here's the rub...

I use my Moto Razr V3 (w/a T-Mo data plan) as a bluetooth GPRS modem quite often (I'm an architect on jobsites a lot with no web connection capability). Paired the phone and most-importantly, used it no prob for DUN with the Toshiba stack. Managed to pair my phone with this new Widcomm stack easily enough and can run OBEX file transfer, etc b/t phone and laptop, but when I try to connect for DUN, I get an "Error 692" reading and phone fails to connect to the web.

Anyone have a solution or ideas? I'm afraid I traded a more important function for a lesser one.

Added all the extra initialization commands, dialing rules, etc so is there something else I'm just missing? Or do you guys think there is some conflict with the stack and card?

Thx in advance.
post #192 of 266
I tried installing a 355 from scratch today. I gave up. I downloaded the 355 drivers from Dell website, and ran the install. It "autodetected" a bunch (and I mean a bunch) of bluetooth devices that I didn't even have--BT mouse, keyboard, modem, fax, Com port, HID something or another...

All I wanted was to use my V270 mouse. Everytime I double-clicked the blue BT symbol in my systray, I got a screen saying "Starting Bluetooth", and a few more devices would be "found", then the windows seems to hang.

After rebooting a few times, I got into control panel and ran BT devices. When I tried to have it detect the mouse, it tried for about 2 seconds and would never find it. BTW, I've setup dozens of V270 mice in the Dell 350 BT using the MS BT drivers, no problem.

Basically, I could never get that crappy software to work. Uninstalled (which it wouldn't allow until I removed the BT device) the Dell BT stack (WIDCOMM), and rebooted. Lo and behold, the MS Stack was there and instantly was able to detect and use my V270.

Why does it have to be sooooo difficult?
post #193 of 266
lancorp,
Now I'm not familiar with the 355, but with my 300 and 350 it's not installing all of those devices, just the services/ BT ports to allow you to connect those devices. Such as the BT serial connection was probably one of them, I don't know anyone who uses that one.
Now again just guessing, I'd have to say that it is hanging because both Microsoft and Widcomm are somehow both trying to manage the Bluetooth.. Is that even possible? Anyways try to make sure you unpair your devices from the Microsoft BT manager before you install the Widcomm Drivers. I had a problem where my computer wouldn't remove my mouse from the paired devices even when the mouse had been off, attempted to be unpaired, and drivers and chip removed and reinstalled (I forget how I fixed that one).
post #194 of 266
This question's for me.
Does anyone else out there have an Inspiron 9100 and installed the Dell BT350 chip? I did and ever since then I have not been able to access any kind of Mass Storage device through my USB2.0 hub, and my whole USB system seems to be pretty unstable. Does anyone else have this problem? Do you think the new chip is messing with things (350's were never actually recognized to work in the 9100's but calling Spare Parts say they are compatible), or should I just reformat... (I've reinstalled the driver waaay too many times for it to be just the BT driver prob)
post #195 of 266
I've been running the TM350 in my XPS (gen1) since 31 March 2005 with zero problems.
post #196 of 266
I just downloaded the drivers on post #1 (could not get the 5.1.0.1100 to work to save my life. The original older drivers have saved me much grief in trying to Activesync and Modem bluetooth to my new Cingular 8525 phone. THANK YOU!!!!!
post #197 of 266
Quote:
Originally Posted by KAROLOYDI
6. Click cancel when the new hardware found wizard appears. Go to Control Panel>Administrative Tools>Services. Right Click on Bluetooth Support Services, select properties and change it from Automatic to disabled. This will remove the Microsoft driver's Bluetooth icon from the control panel and tray.
Restart
If it just says Bluetooth Services in that menu should I still disable it?
post #198 of 266
I got the 1400 drivers from that CD of I think Page 12 to work with my 350 bluetooth. But the range is so bad that I think I get a usb Class 1 Bluetooth stick for decent quality. The range of the internal one is really only to synchronise your portable or for using your Sony portable as a mediastation remote. For skype or Sipcalls quality just sux.
post #199 of 266
who needs bluetooth anyway <_<
post #200 of 266
I can't get my 355 Bluetooth adapter to start the Headset service when my Motorola HS850 headset connects. It will start the Audio Gateway though...
New Posts  All Forums:Forum Nav:
  Return Home
NotebookForums.com › Forums › Notebook Manufacturers › Dell Notebook Forums › Dell Home (Inspiron, XPS, Studio) › What's up with Dell's Bluetooth drivers?