[Kde-pim] Reason why the 700p doesn't sync...

[Ryan Novosielski]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello folks... I am attempting to sync my Palm Treo 700p. I had a 650
which was great in every way (save EVDO and NVRAM), but when the boss
bought me a cell, I opted for a Treo 700p.

Well, the thing won't reliably sync by USB and it has finally occurred
to me why. The 700p, when plugged in, draws power and alerts the PC to
its presence. The problem, however, is if one opens kpilot, kpilot
notices the open port and doesn't hold off like it apparently normally
would before attempting to open a USB port (Pilot device /dev/ttyUSB1
does not exist -- probably it is a USB device and will appear during a
HotSync).

The upshot of this is the following behavior:

1. Device is plugged, /dev/ttyUSB0 and /dev/ttyUSB1 appear.
2. kpilot notices this and says (Device link ready.)
3. You push HotSync
4. Device goes from draw power mode to communicate mode (I have no idea
how this thing works, this is just how it looks to me), does not use
/dev/ttyUSB0 and /dev/ttyUSB1 (because they are in use?) and instead
starts attempting to connect on /dev/ttyUSB2 and /dev/ttyUSB3.
5. kpilot notices this and says "Cannot listen on Pilot socket
(Input/output error)", as a result of its previous "Device link ready."
condition going away.

The same thing happens with pilot-xfer. The only way to make this work
is to make sure the device is already syncing by the time it causes a
device to appear on the PC. This is tricky, however, because it doesn't
seem like you have an unlimited amount of time to get the PC properly
connected after pushing HotSync on the device -- it only appears to work
for the first few seconds.

Anyway, it appears as if this is the problem. Now, how on earth can we
go forward from here? Does this description make sense to anyone? Here's
an example with pilot-xfer:

BAD:
1. Connect device. (/dev/ttyUSB0-1 created)
2. Run pilot-xfer (listens to /dev/ttyUSB1)
3. Hit HotSync (/dev/ttyUSB0-1 go away, /dev/ttyUSB2-3 appear)
4. Eventual failure

GOOD:
1. Connect device. (/dev/ttyUSB0-1 created)
2. Hit HotSync (/dev/ttyUSB0-1 are destroyed and then re-created)
3. Run pilot-xfer (listens and connects on /dev/ttyUSB1)
4. Success

Thanks for reading this far and hopefully it was helpful.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF339Fmb+gadEcsb4RAq89AJ0ZFJ1rupx3AQ+5RZRxik3pljzbEQCeIhDg
4MT1gwkZ5++tC+H7AiBBa2g=
=ELOU
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/