Free dell bluetooth support software for pda

This is a free utility which permits FASTCODE Bluetooth Applications, such as 1st Bluetooth Mouse, to interact with PC
System requirements:
- Windows , Bluetooth , .NET Framework 2.0

Want to listen to your music stored on your 2125, 3125 or Motorola Q, but dont want to carry around a corded headset? If youve got a BlueTooth headset, then youre in luck! With this program, just start it up, and all of the sounds from your system will be rerouted from the internal speaker to your BlueTooth headset!
System requirements:
- Windows Mobile 5.0 Smartphone

Control your NXT robot using Bluetooth and your PalmOS device! Works with buttons and controls motors A & C. FWD, REV, L, R, revolve. More to come!!!
System requirements:
- Palm: Tungsten T|3
- 4KB

Medieval Bluetooth File Transfer (OBEX FTP) for J2ME 1.00 has come as an effective program with which you can utilize your cell phone to browse, explore and manage files of any Bluetooth ready device (File Transfer Profile (FTP) OBEX)! Download, upload, explore, edit, create, delete and rename files and folders on your phone, PDA, palm, notebook, PC, photo viewer, music player and so on; using an easy, fast and intuitive user-interface (GUI).

Transfer or delete many files and entire folders at once, with a single keypress, using the multiple selection feature. Explore hidden files, or make your personal data private and/or read-only, using the attributes editor (local filesystem only). Cut, copy and paste files and folder across filesystems. Save your favorite devices in the bookmark list, to speed-up the connection procedure.

Major Features:

1. Works on almost all phone models with MIDP 2.0 and CLDC 1.1 support, using a single JAR file
2. Easy to use, fast and straightforward user-interface (GUI), powered by Medieval GUI system
3. Shortcut keys improves user usability and speed-up your GUI experience
4. Unique fullscreen mode, to remove top/bottom bars and enlarge working area
5. Cool and intuitive menu system to execute extended functionality
6. Multiple files and folders selection, to transfer/delete many items at once
7. Select all, Select none and invert selection options available
8. Navigate on both local and remote filesystem using a single keypress
9. Download/upload items from/to any device with OBEX FTP support (almost on all phone models
10. Ability to cut/copy and paste files between devices and/or to manage local filesystem
11. Edit file or folder attributes to enable or disable READ, WRITE and HIDDEN status flags
12. Open and view the content of some files using the internal viewer (local filesystem only)
13. Get files and folders informations on both local and remote devices
14. Create new folders on both local and remote filesystem
15. Signed with both VeriSign and Thawte certificates
16. Multi-language user interface.

Support Log is a Palm application to record details of problems and solutions.
Designed mainly for people who provide out of hours support and need a convenient tool to record their efforts.
It will allow you to record information such as time and date, severity, trouble ticket number, description of the problem and any resolution and more.
Main features:
- - Records Date, Time, Problem and Solution.
- - Records Standby, Serverity and Trouble Ticket.
- - Usual edit features - Cut and Paste etc.
- - Delete ALL facility.
- - Export All logs to comma separated format.
System requirements:
- Palm OS v3.5

Getdeblu is a freeware utility that permits you to receive files into the expansion card through Bluetooth, IrDA or HotSync.
You can specify the default application, the HotSync directory and the Destination directory.
System requirements:
- Palm OS v4.0.

A basic database to keep track of child support payments and that part of my Navy Retirement pay that my ex gets with running totals.
System requirements:
- HanDBase v.2.7x or greater

An application for updating SDP records on Series 60, specifically for making Bluetooth File Exchange on OS X usable with Series 60. Licensed under GPL.

OBEX File Transfer on Series 60, with Bluetooth File Exchange on OS X

This only conserns Series 60 2nd edition (and probably 1st edition, too), 3rd edition and Series 80 work as they should.

Overview

Ever since starting to use Series 60 phones with OS X, Ive been annoyed by the fact that Bluetooth File Exchange cant browse them. The only way of transferring files between them is by using OBEX push, that is, by sending individual files (which then on the phone end up in the inbox).

This is bearable, but sometimes youd want to send a bigger file straight to the memory card which doesnt even fit into the main memory of the phone.

I dont know about any OBEX FTP client for Series 60 either (is there any?), otherwise that would be a feasible workaround.

Initially, it seemed to me that Series 60 didnt work at all with Bluetooth File Exchange, since it only showed an empty folder. After quite some time, though, I figured out that it actually works, but not as one would hope. Uploading files works, and then the uploaded files are stored into the inbox. And in that case, the files which are in the inbox, uploaded using OBEX FTP earlier, are visible. But not files sent using OBEX push, and of course nothing outside of the inbox.

I had only tried using obexftp (which uses openobex) on Linux using USB earlier, and knew that that one works as I want to. Much later, when I tried using obexftp with Bluetooth, I found the same situation if one doesnt manually specify a specific RFCOMM channel. Using the wonderful tools in BlueZ (more specifically, sdptool), I could view a dump of all SDP (service discovery protocol) records on the phone, and suddenly everything made sense.

The phone advertises quite a few different services, among them a standard OBEX FTP service and OBEX PC Suite services. The RFCOMM channel one had to specify in order to make obexftp work was the PC Suite channel.

In other words, Series 60 advertises two services which speak the OBEX FTP protocol, one very crippled advertised with the ordinary OBEX FTP service UUID and one full-fledged service with a PC Suite-specific UUID.

One cant expect Bluetooth File Exchange to look for the non-standard PC Suite service UUID, and I dont know of any other OBEX FTP application for OS X. But theres still another (quite hackish) solution: make the phone advertise the PC Suite service using the OBEX service UUID.

Ideally, the hack would consist of a simple application on the phone, which investigates the local SDP database and makes the necessary modifications. Unfortunately, the SDP APIs on Symbian dont seem to provide any way of reading whats in the database, and the APIs for reading SDP records from other devices dont seem to be able to connect to the local SDP server. In other words, the investigation of the SDP database must be done on some other device.

Solution

Note, I take no responsibility whatsover for the effects of using these tools. They work for me, at least.

SdpBrowser

SdpBrowser is a tool for OS X, which more or less does the same as sdptool in BlueZ - its capable of listing all the SDP record data on a remote device. (Bluetooth Explorer in the Xcode Developer Tools does more or less the same, but only for the local SDP database.) This can be useful when developing Bluetooth applications for some other device than the local mac.

Since SdpBrowser is made specifically for this need, it also can try to parse out the necessary information from the SDP records.

SDP Editor

SDP Editor is a small tool for Series 60 for updating already existing SDP records on the phone. Enter a SDP record handle and a RFCOMM channel, and that record is updated to advertise the given channel.

The changes arent persistent, everything is back to normal after restarting the phone.

The APIs dont work too well if the given record handle doesnt already exist, on 6630 the SDP server crashes. Updating the wrong record makes some other service unusable. In all cases, restarting the phone should restore everything.

Usage

Using SdpBrowser, select Get PC Suite info in the Device menu, select the phone and click browse. If everything works as it should, it gives the SDP record handle of the OBEX FTP record and the RFCOMM channel of the PC Suite service.

Then start SDP Editor on the phone, choose Update channel in the menu, and enter the handle and RFCOMM channel given by SdpBrowser. Then, Bluetooth File Exchange should be able to browse the files on the phone.

The handle and channel shouldnt change as long as you dont install/remove any service on the phone, so in general youll only need to rerun the application on the phone with the last, working values.

If it doesnt give all the necessary information, you can try to read it manually from the raw SDP records. Select Browse in the Device menu, and select the phone. Look for a record with the text "OBEX File Transfer", and look for the number on the row starting with "0:" in this record (e.g. "0: 0x10006"). Thats the record handle (in hexadecimal). Also look for a record with the text "Nokia OBEX PC Suite Services". That record should have a row like "4: { { } }, { { }, { 0xc } }, { { } }". Here 0xc, that is 12, is the RFCOMM channel.

Further improvements

This already is quite an improvement to the original "functionalty" of the crippled OBEX FTP service. But e.g. the System-directory is hidden - if one would be able to directly transfer files there, the development process of Series 60 applications would get a big speedup. This directory is still accessible, if one is able to manually enter a directory to open. (Incidentally, obexftp does this.)

So, the final wish is a "Go to directory"-dialog for Bluetooth File Exchange, or obexftp working on OS X. (openobex can be compiled with USB support on OS X, but I havent gotten it to work... Perhaps Ill have to add support for OS X-bluetooth to it myself, sometime, if I have time and if noone else beats me to it.)