Comments on: palmOne Phone Link Application Updated
Article Comments
(31 comments)
The following comments are owned by whoever posted them. PalmInfocenter is not responsible for them in any way.
Please Login or register here to add your comments.
RE: They got my phone!
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
RE: They got my phone!
RE: They got my phone!
The T637 is a 850/1800/1900 phone that was released in the US for Cingular and ATT.
No v710 driver ..... AGAIN
The phone has been out for a YEAR.
The stupidity is absolutly amazing.
-R
RE: No v710 driver ..... AGAIN
RE: No v710 driver ..... AGAIN
RE: No v710 driver ..... AGAIN
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.
RE: No v710 driver ..... AGAIN
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.
RE: No v710 driver ..... AGAIN
[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.
RE: No v710 driver ..... AGAIN
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.!
RE: No v710 driver ..... AGAIN
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.
I think this broke my T3
Anybody else have a problem?
"Many men stumble across the truth, but most manage to pick themselves up
and continue as if nothing had happened."
- Winston Churchill
Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
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.)
RE: Still waiting for the driver for Nokia 6230 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
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.
RE: Still waiting for the driver for Nokia 6320 and my T3
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.
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6230 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
RE: Still waiting for the driver for Nokia 6320 and my T3
Only loading the BT driver does not work, as already described by AlexOfBorg.
RE: Still waiting for the driver for Nokia 6320 and my T3
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.
Latest Comments
- I got one -Tuckermaclain
- RE: Don't we have this already? -Tuckermaclain
- RE: Palm brand will return in 2018, with devices built by TCL -richf
- RE: Palm brand will return in 2018, with devices built by TCL -dmitrygr
- Palm phone on HDblog -palmato
- Palm PVG100 -hgoldner
- RE: Like Deja Vu -PacManFoo
- Like Deja Vu -T_W
They got my phone!
I might do a backup and give this a try to see if they got it right. Of course it mught be a moot point since Cingular broke my GSM dialup by turning off CSD in error. I'm still waiting for them to fix their mistake...