synce-hal and WM2003

[Adam Williamson]

Okay, so as promised, I gave synce-hal a shot :)

It seems to work great to pick up the device and start hal-dccm with
absolutely no messing about - great. synce-trayicon sees the device.

However, I seem to be stuck on partnerships.

I can't use create_partnership.py - I guess that's only for WM5/6 style
partnerships. So I use synce-matchmaker. This seems to create a
partnership fine:

[***@lenovo adamw]$ synce-matchmaker status
Current partner index: 1
Partner 1 id: 0x5c4caac8
Partner 1 name: "lenovo"

but sync-engine isn't having any of it. I run sync-engine and see:

2008-06-02 17:26:44,057 INFO engine.partnerships.Partnerships : ReadDevicePartnerships: Deleting dangling registry entry: (1, 1548528328L)
2008-06-02 17:26:44,069 DEBUG engine.partnerships.Partnerships : AttemptToBind: No valid host bindings found for any device partnership
2008-06-02 17:26:44,070 DEBUG engine.partnerships.Partnerships : AttemptToBind: setting current partnership to None
2008-06-02 17:26:44,074 DEBUG engine.syncengine.kernel : OnConnect: No valid partnership bindings are available, please create one (org.synce.SyncEngine.Error.NoBoundPartnership: )
2008-06-02 17:26:44,075 DEBUG syncengine : installing signal handlers

and now my partnership's disappeared! :

[***@lenovo adamw]$ synce-matchmaker status
Current partner index: 0

What's going on here, then?

I haven't verified that it'd work with my WM6.1 test device yet, but I
suspect it will - I'll check that out. I'll also check if the opensync
synce plugin works with synce-hal, but I suspect it won't.

[Adam Williamson]

Post by Adam Williamson
I'll also check if the opensync
synce plugin works with synce-hal, but I suspect it won't.

Hey, what do you know, it does.

So, the good news: synce-hal plus opensync's synce plugin = WM2003
synchronization heaven, it basically just works. No footling around
required. The bad news, synce's opensync plugin doesn't work. But hey,
we can live with that.

[Mark Ellis]

Post by Adam Williamson
Okay, so as promised, I gave synce-hal a shot :)
It seems to work great to pick up the device and start hal-dccm with
absolutely no messing about - great. synce-trayicon sees the device.
However, I seem to be stuck on partnerships.
I can't use create_partnership.py - I guess that's only for WM5/6 style
partnerships. So I use synce-matchmaker. This seems to create a

Correct.

Post by Adam Williamson
Current partner index: 1
Partner 1 id: 0x5c4caac8
Partner 1 name: "lenovo"
2008-06-02 17:26:44,057 INFO engine.partnerships.Partnerships : ReadDevicePartnerships: Deleting dangling registry entry: (1, 1548528328L)
2008-06-02 17:26:44,069 DEBUG engine.partnerships.Partnerships : AttemptToBind: No valid host bindings found for any device partnership
2008-06-02 17:26:44,070 DEBUG engine.partnerships.Partnerships : AttemptToBind: setting current partnership to None
2008-06-02 17:26:44,074 DEBUG engine.syncengine.kernel : OnConnect: No valid partnership bindings are available, please create one (org.synce.SyncEngine.Error.NoBoundPartnership: )
2008-06-02 17:26:44,075 DEBUG syncengine : installing signal handlers
Current partner index: 0
What's going on here, then?
I haven't verified that it'd work with my WM6.1 test device yet, but I
suspect it will - I'll check that out. I'll also check if the opensync
synce plugin works with synce-hal, but I suspect it won't.
--
adamw

Nothing to do with hal, sync-engine is currently for WM5/6 only. Use the
old multisync and the synce plugin for it, or apparently the synce
plugin supplied by opensync (not the one with sync-engine) will work.

Mark

[Adam Williamson]

Post by Mark Ellis
Nothing to do with hal, sync-engine is currently for WM5/6 only. Use the
old multisync and the synce plugin for it, or apparently the synce
plugin supplied by opensync (not the one with sync-engine) will work.

Yeah, as I discovered. It would be better to have all devices covered by
one plugin, though, really.

[Adam Williamson]

Post by Adam Williamson

Post by Mark Ellis
Nothing to do with hal, sync-engine is currently for WM5/6 only. Use the
old multisync and the synce plugin for it, or apparently the synce
plugin supplied by opensync (not the one with sync-engine) will work.

Yeah, as I discovered. It would be better to have all devices covered by
one plugin, though, really.

I noticed something funny with syncing using the OpenSync plugin,
libopensync-plugin-synce .

Its default configuration sets a file synchronization location (\My
Documents ). If I run KitchenSync and create a partnership with
libopensync-plugin-synce and the Evolution plugin, it seems to actually
try and 'synchronize' files - it scans everything in \My Documents after
doing all the contacts and tasks - and then basically fails because the
Evolution plugin has no idea what to do with the files...heh. I've
'fixed' this for now by setting a nonsense directory as the default file
sync location for the plugin, but did anyone else see this? Anyone think
of a better fix?