|
|
If you're going to go through with this, you have to change the requirement for headset usage. The SD cards DO NOT support the headset profile - that is, the hardware in the SD Card does not, and will never, be able to communicate with a headset. They only support "Dial-up Networking, Fax, Serial Port, LAN via PPP, General Access, Service Discovery, Generic Object Exchange, Object Push, File Transfer" - in other words, only the Serial profiles, and none of the audio profiles (e.g. Headset, Handsfree, audio, etc). This means that the cards can not even be shoehorned into talking to headsets. Bluetooth synching is the best you can hope for.
I'm a computer science graduate student, and have been tinkering with Bluetooth on my my phone since I got a Kyocera 6035 three years ago, and have continued with my Treo 300, and now with my 600. Getting synching to work, can be done, but it won't be great - you can't expect the sort of user experience you would from a device with BT integrated.
I have made a lot of progress tinkering here and there on the problem, but nothing I wanted to share since it was far from complete. But given the significant excitement around getting this to work at all, I figured I'd share my project plans here and now, and wish someone with a lot more time than me luck.
There is precedent getting Bluetooth to work on a PalmOS device that did not include it originally using TDK's Blue5 by way of the handheld's serial port. Here are two intrepid solutions: using a Palm IIIc (sorry, in German) and a HandEra 330.
Given these solutions, my experimentation and design protocol looks as follows:
1. get power to the Blue5 - it needs 3.3v, so I was just going to attach it to 3 AAs and see if it'll power up.
2. get power to the Treo's serial port. As anyone who's tried getting GPS to work with their Treo knows, Handspring used a TTL signaling serial cable, powered by the host computer's serial port in place of a true RS-232 port on their products. This means that the small chip in a Treo's serial cable needs to be powered externally. Searching these forums, as well as other PDA-centric forums will reveal a wealth of information on this subject, and therefore I won't post all my notes here.
3. Experiment with TDK's drivers and software originally designed for PalmOS 3.5 and for a device with a true RS-232 port to see if they will work with the treo without modification.
4. If they will not, I had one other tack to try. Namely, to use a PalmV with the Blue5, to establish a pairing between the Blue5 and a Bluetooth enabled computer. Then, attaching it to the Treo, I would see if the pairing held and I could synch.
5. if all of this worked, I was planning on stripping a Treo battery expansion pack to fit the blue5 and it's power source inside and give me an enclosed Bluetooth expansion pack.
I intend to continue to tinker with this when I have time, and only to satisfy my curiosity. If TreoCentral intends to continue to support the pursuit of a Bluetooth driver for the Treo, I suggest it be amended to no longer include the headset requirement. Then, if anyone wishes to pursue that reward, you might get there sooner with my experimental protocol above. However, do so at your own risk - you could easily destroy your Treo, the Blue5, and possibly be injured if you are not careful with the power source should you short the Treo's battery.
best,
Conrad
|
|
|
Posting Permissions
Originally Posted by fmertz
Check out the 
