Hi,
Thank you for the reply. I've been slammed the past week, but finally
got a chance to test this out.
I followed the directions for connecting via USB (previously I was using
Bluetooth), gave my user privileges via udev, and am seeing the
following (Phone reports: System Error):
$ syncml-obex-client -u 0 --identifier "PC Suite" --sync text/x-vcalendar Calendar --wbxml
connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 201, Last , Next 20080501T201634Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an reply to our Alert
Session 1 reported final. flushing
Session 1 has ended
However, when I run this, the phone does not report any error, yet:
$ msynctool --sync evo_n95
Synchronizing group "evo_n95"
The previous synchronization was unclean. Slow-syncing
event sink of member 1 of type evo2-sync just connected
event sink of member 2 of type syncml-obex-client just connected
contact sink of member 2 of type syncml-obex-client just connected
Main sink of member 2 of type syncml-obex-client had an error: Link Error: 0x0
contact sink of member 1 of type evo2-sync just connected
Main sink of member 1 of type evo2-sync just connected
The sync failed: At least one objenit hat problems while connecting. Aborting
Main sink of member 2 of type syncml-obex-client just disconnected
event sink of member 2 of type syncml-obex-client just disconnected
contact sink of member 2 of type syncml-obex-client just disconnected
event sink of member 1 of type evo2-sync just disconnected
contact sink of member 1 of type evo2-sync just disconnected
Main sink of member 1 of type evo2-sync just disconnected
All clients have disconnected
ERROR: At least one objenit hat problems while connecting. Aborting
I've changed the n95 config to:
<?xml version="1.0"?>
<config>
<!-- sets the connection type to use. -->
<!-- please note that actually OBEX over network is not supported -->
<!-- 1 means obex over serial cable -->
<!-- 2 means obex over bluetooth -->
<!-- 3 means obex over IRDA -->
<!-- 4 means obex over network -->
<!-- 5 means obex over usb -->
<type>5</type>
<!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected.
`hciconfig scan` to search bluetooth devices. -->
<bluetooth_address>00:xx:xx:xx:xx:xx</bluetooth_address>
<!-- (Only for bluetooth) The bluetooth channel to use.
`sdptool browse $MAC` to search for the correct channel -->
<bluetooth_channel>10</bluetooth_channel>
<!-- (Only for USB) The usb interface number of the SYNCML-SYNC target. use syncml-obex-client -u (you will need access to the USB raw device) to find it. -->
<interface>0</interface>
<!-- The string that the plugin will use to identify itself. Some devices need a special string here. -->
<identifier>PC Suite</identifier>
<!-- The syncml version to use: 0 for 1.0, 1 for 1.1 and 2 for 1.2 -->
<version>1</version>
<!-- if the plugin should use wbxml -->
<wbxml>1</wbxml>
<!-- The username to use. Leave empty to not require a username -->
<username></username>
<!-- the password for the username -->
<password></password>
<!-- If wbxml is enabled, defines wether the wbxml should use string tables -->
<usestringtable>1</usestringtable>
<!-- Never send ADD command, but send REPLACE (not needed normally) -->
<onlyreplace>0</onlyreplace>
<!-- Workaround around for mobile phones which only use local timestamps and _no_ UTC timestamps! -->
<onlyLocaltime>0</onlyLocaltime>
<!-- Sets the maximum allowed size in bytes of incoming messages (some device need this option set). Example: 10000 -->
<recvLimit>0</recvLimit>
<maxObjSize>0</maxObjSize>
<!-- XXX: Currently you need to write this by your own.
Later it's planned to create such entries on the fly during
the discovery() call. Example database field:
<database>
<name>Contacts</name>
<objtype>contact</objtype>
<objformat>vcard21</objformat>
</database>
-->
<database>
<name>Contacts</name>
<objtype>contact</objtype>
<objformat>vcard21</objformat>
</database>
<database>
<name>Calendar</name>
<objtype>event</objtype>
<objformat>vevent20</objformat>
</database>
</config>
On Sat, 2008-04-26 at 10:17 +0200, Daniel Gollub wrote:
> On Saturday 26 April 2008 00:37:18 xyon wrote:
> > When trying to sync my n95 with the CLI msynctool, I get timeout errors.
> >
> > Once msynctool is started, the phone immediately reports "Connecting".
> > After some time (long pause noted below in msynctool output), the phone
> > reports "Sending Calendar 5 of 5", and msynctool reports a disconnect
> > (shown below).
> >
> > I've attached the hex hcidump and included below all pertinent
> > information I could think of.
>
> Could you try first try the syncml-obex-client command line tool? To check if
> this is a libsyncml or OpenSync issue...
>
>
>
http://libsyncml.opensync.org/wiki/obex-guide#Troubleshooting>
> Thanks for testing!
>
> best regards,
> Daniel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone> _______________________________________________
> Opensync-devel mailing list
>
Opensync-devel@...
>
https://lists.sourceforge.net/lists/listinfo/opensync-devel--
Steven McCoy
Infrastructure Design / Systems Engineer
IndigoRobot Services
EMail -
Steven@...
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel