Comments on: palmOne Phone Link Application Updated

Strange, they don't specifically list the S/E T637, but they do the T630? 630 is identical except for color and GSM frequency as far as I know. T-mob=630 ... CingATT=637.

Anyway, I'll use the 630 for my T3, but I've noticed this more than once on things. I wonder if the 630 is older or more widespread, or if a real difference?

Pat Horne; www.churchoflivingfaith.com

Nope, did not work at all. Got "Missing netlib" error. Glad I did a backup first.

The T630 came prior to the T637 in Europe. It was a 900/1800/1900 phone and came in white. It was a big annoucement that SE did a black cased version for T-Mobile.

The T637 is a 850/1800/1900 phone that was released in the US for Cingular and ATT.

Well, the v710 has a crippled Bluetooth implementation, which I'm not even sure supports dialing from BT. Even if it does, the v710 was never a very big sales success, so I can't say it's surprising that P1 hasn't bothered to create a driver profile for it.

Not to mention the legal issues... with Verizon subscribers suing over the limited implementation, palmOne's legal dept. is bound to have said "stay clear"...

The V710's BT profile, albeit a crippled one, DOES support DUN & headset profiles. It's the OBEX (object exchange) profiles that are specifically disabled by VZW so you cannot use Mobile Phone Tools to move images, ringers, mp3s etc to & from the phone via BT. It also has trouble with several BT car kits but the recent firmware update did resolve some of the issues.

From what I hear, the upcoming v710 replacement (the e815) will have OBEX enabled but now DUN is disabled. I am sure it'll be hacked back into operation as some early reports said it was just a matter of some seem changes.

With a v710 and a Zire 72, we regularly connect to the I-net using a dial-up ISP. The dial-up networking connection works through the bluetooth "network service" set-up devices command without any problem. It's not a fast connection but it is more than suitable (for my use), for e-mail and casual web browsing -- weather and quick news while I'm on the road.

We used one of the other Motorola phone profiles when setting up the Bluetooth setup and it worked fine for ISP dial-up connections.

None of the other PDA Bluetooth dialing functions seem to work with the v710 on the Verizon network; it will not dial from "Quick Connect" or using Palm's manual "Dialer" software -- the v710 will dial out from the "Quick Connect" contact list and the called number will ring momentarily but immediately disconnect and the Bluetooth connection will drop.

As noted in a prior posting, "object exchange" is disabled in the v710 and we cannot send photos, contact lists, or other items to the phone from the PDA.

We haven't tried Bluetooth headsets so we can't comment on their utility, but as far as bluetooth dial up networking with the Zire 72, the v710 been a great success for our use.

(continued from above)

[b] ***CONCLUSION AFTER NEARLY 3 WEEKS WITH LD*** [/b]
Overall the LD's situation might be changing to "cautiously optimistic" IF P1 continues patching it. A nice midsummer combo of a $50 MSRP price drop, free PTunes Deluxe and a big ROM update would do wonders for the marketplace's response to the LD. For those who use only wi-fi or have a GSM cell and don't care too much about MP3 playback, a patched LD down the road might still be an attractive proposition. I still call it more of an Archos-style portable 4gb HD that happens to play back media & do PIM functions/apps more so than a media-centric PDA. It's ok for a one-off, "stay in the game" release but a proper PDA does not--and should not--have a fixed hard drive as standard equipment IMO. Until the Verizon BT issues are resolved, I am afraid I am still going to have to take a pass on the LD.

Sorry guys, I was trying to post some comments from a posting I in the PIC forums in regards to the LD's lack of compatability with the V710 being the BIG deal-breaker for me. I pasted the wrong section by accident.

In summary: The sad thing is that with the exact same settings on the same V710 phone and two LDs purchased 2.5 weeks apart, one LD got on the 'net just fine through Verizon DUN but the current ones refuses. I assume that P1 tweaked the BT stack of the 2nd production batch or there are minor incompatabilities between shipping units.

If P1 would JUST release a proper V710 or unsupported init string etc.!

Update:

Supposedly the new E810 Motorola on Verizon *DOES* work with the LifeDrive and all prior BT-enabled Palm devices....assuming you unofficially enable DUN support on the 815. I unfortunately cannot test this since I returned my LD lemons and am still mired in a 2 year contract on VZW and am stuck with my V710 for the next year...

So that leave the V710 & LifeDrive combo as the ONLY pair that doesn't work for DUN on Verizon.

Maybe it is a hardware issues, otherwise they would have done so. Unfortunately I have also been waiting for this too long...

Visit the link above, and do yourself a massive favour.

Ah yes, Mobile High Speed. Highly recommended auto configuration. Works like a charm, and support is very good if needed.

Do you mean the 6230 (since I've never heard of a Nokia 6320?) If so the Phone Link application from P1 supports it since the last update (the one fromer to this). You could still have chosen another Nokia phone from the list (like 6210i) and it worked even before, for me at least!

Yes - it should have read 6230. I am trying to use SMS and input on the T3 rather than the phone but it will not connect for me. If anyone has managed to do this can you let me know how?

Never tried with SMS, but the BT modem connection does work fine! Are you having troubles with it as well?

The BT modem connection works fine. It is only when I write a text message on the T3 screen and try to send it to the 6230 that it will not work. I used to do this all the time with my previous phone - a Siemens T68i and it worked perfectly.

Just tried it with the latest-1 drivers and indeed it doesn't seem to be working, I get a 16-digit pairing key request on the phone but after the pairing it still won't send.. Anyway I don't think I'm going to update after reading some of the comments! :/

There is a problem with the T3's Bluetooth stack (actually with all devices <= PalmOS 5.2) and the Nokia 6230. The Palm will always connect to the "SIM access profile" and not the "Serial rfcomm profile". The phone will disconnect from the network and no SMS function is possible. Neither Nokia nor PalmOne will fix this.

You can fix this by copying the Bluetooth serial driver (BtCommVdrc*.prc) from the T5 onto the T3. (I know it works, I make the phone drivers.)

Can anyone tell me where I can get my hands on the Bluetooth serial driver (BtCommVdrc*.prc) for the T5? I would love to be able to use the SMS on my T3.

I fell into this trap yesterday... and after ~12+ hours of rebuilding PC and Palm Tungsten T from backups, I'm not even going to think about trying to get the Palm talking to the 6230 with Bluetooth.

For a detailed coverage of the problem (including a link to where you can find the T5 BT driver), have a look at http://micke.hallendal.net/archives/2004/11/on_nokia_6230_a_1.html ...

Beware that you may still not get things to work. I have the latest Tungsten T update in my Palm, the latest firmware in the 6230, etc and I still have to re-install everything in the PC and the Palm and I'm no better off.

At least IR still works Ok between the Palm and the 6230.

I know that it works with the Tungsten T3. But for legal reasons I cannot send you the files. Maybe somebody else will.

I don't know if this patch can be done with the old Tungsten T. It has PalmOS 5.0, maybe it has different problems.

Note that you should turn Bluetooth off on the receiving device, as well as BT-Toggle or anything like that. You should copy the files from SD card into RAM, do not install them with Hotsync. Reset after install.

One more thing: Do NOT forget to install the resource file for your language. You must install at least two files on your T3.

IT'S WORKING. I finally have my T3 and Nokia 6230 "talking" to each other. I can surf the web and use Palm SMS. The long wait is over. I used the BT driver (BtCommVdrc*.prc)from the T5 and now I have a fully functional T3 again. Thanks to everyone for their comments.

polygott, where did you find the files? can you email them to me? I just bought a 6320 and it is driving me crazy that the dialer and other simple functions does not work.

May anyone be so kind an telling me where I can find the mentioned language resource file for the T3?
Only loading the BT driver does not work, as already described by AlexOfBorg.

tnick61,

I messed up my T3 so bad that in the connections manager I don't have the Bluetooth option anymore. Did a hard reset and solved the problem but in the midst of restoring my contacts and memo I deleted a whole bunch of categories so the contacts sat in unfiled.

Anyway, here is how I got it going. Don't remember the sequence I did it but it might not matter.

Copy the BtCommdrv file with FileZ after I deleted the "_T5"
Install the Phonelink update.
Install the Dialer software from the Palm website. (don't know if this is required but that is what I did)
Create new connection with Phonelink.
Go back to connection and select the new "Nokia 6230" change the driver to Standard GSM.
Enjoy your Dialer and SMS now.

Suddenly it felt it was not that hard.