[Kde-pim] Palm Treo 700p redux

[Adriaan de Groot]

On Friday 16 November 2007, Ryan Novosielski wrote:
> A couple of things about KPilot that confound me, and are reproducible.
> Now that I have a little more time and some decent equipment, it'd be
> nice to start helping out again.

Yay!

> I have a Treo 700p, and the Zire/T5/etc. workaround had worked pretty
> well for this particular device... two problems though:
>
> 1) After a sync, or an attempted sync, KPilotDaemon holds onto the USB
> port. This means that since my device is one that drops the USB
> connection when switching from sync mode to draw-power mode, it will
> lose ttyUSB1 (the one that it uses) and move to ttyUSB3 when it
> reconnects. Here's how it goes down:

The T5 workaround is supposed to handle just that: when a device keeps a /dev 
node around but doesn't actually hotsync through it. The idea is that KPilot 
*will* drop it again. The hotsync log you show below suggests that it isn't 
doing so. Ugh.

> 21:57:12 Trying to open device /dev/ttyUSB1...
> 21:57:23 Cannot accept Pilot (Success)
> 21:57:23 Could not open device: /dev/ttyUSB1 (will retry)
> 21:57:36 Cannot accept Pilot (No such process)
> 21:57:48 Cannot accept Pilot (No such process)
> 21:58:00 Cannot accept Pilot (No such process)
>
> ...and the progress bar is at 10%. At this point, any attempt to sync
> will fail since KPilot has ttyUSB1 open and the phone cannot use it.
>
> In fact, the only way to solve it appears to be to cause KPilot to hold
> open ttyUSB1 as I was describing, and let the phone return to the
> charging state. The phone will be using ttyUSB3. I then close and reopen
> KPilot, that tries to connect to ttyUSB1 and fails and says it will
> retry later because it's likely a USB device. Doing a HotSync then
> causes the device to drop its connection and go back to USB1, which then
> works. Doing this any other way causes KPilot to try to sync right away
> when the phone is just charging (and not going to exchange any data),
> which then gets in the way of a real sync.

If you have your OS configured right to do hotplug events, you can get it to 
point /dev/pilot to the correct USB device when the sync starts; I just don't 
know how to do it for anything beyond FreeBSD (some people have written 
suggestions on how to do it in SuSE, check the KPilot site).

Hope that helps a little with the connection problems, at least.


-- 
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20071116/c5bfb7d4/attachment.sig>
-------------- next part --------------
_______________________________________________
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/