nokia n95 timeouts

[xyon]

Hi everyone,

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.



Packages/versions:

bluez-hcidump 1.41-1
bluez-libs 3.27-1
bluez-utils 3.27-2
evolution 2.12.3-2
evolution-data-server 1.12.3-1
gnome-bluetooth 0.11.0-1.1
kdebluetooth 1.0_beta8-2
libopensync 0.36-1
libopensync-plugin-evolution2 0.36-4
libopensync-plugin-syncml 0.36-3
libopensync-plugin-vformat 0.36-1



hcidump command:

# hcidump -i hci0 -x -w hci.dump
HCI sniffer - Bluetooth packet analyzer ver 1.41
device: hci0 snap_len: 1028 filter: 0x0



msynctool command/output:

$ 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
contact sink of member 1 of type evo2-sync just connected
Main sink of member 1 of type evo2-sync just connected
Main sink of member 2 of type syncml-obex-client just connected
All clients connected or error
event sink of member 1 of type evo2-sync just sent all changes
Main sink of member 2 of type syncml-obex-client just sent all changes
Received an entry pas-id-4810983F00000003 from member 1 (evo2-sync).
Changetype ADDED
Received an entry pas-id-480E984A00000017 from member 1 (evo2-sync).
Changetype ADDED
Received an entry pas-id-4810983B00000002 from member 1 (evo2-sync).
Changetype ADDED
Received an entry pas-id-4810979C00000000 from member 1 (evo2-sync).
Changetype ADDED
contact sink of member 1 of type evo2-sync just sent all changes
Main sink of member 1 of type evo2-sync just sent all changes

**** There is a long pause here ****

event sink of member 2 of type syncml-obex-client had an error: Timeout.
contact sink of member 2 of type syncml-obex-client had an error:
Timeout.
The sync failed: At least one object engine failed while getting
changes. Aborting
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




Configurations:

Member1 (evo2-sync):

<?xml version="1.0"?>
<config>
  <address_path>default</address_path>
  <calendar_path>default</calendar_path>
</config>


Member2 (Nokia n95 (Europe, non-8GB)):

<?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>2</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>



-------------------------------------------------------------------------
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

[Daniel Gollub]

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

[xyon]

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

[xyon]

Did some more research with the syncml-obex-client, and started using
bluetooth. I also created a new empty addressbook and empty calendar in
Evolution, and set them to default.



This seems to work (got "Sync Complete" on the n95):

$ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vcard
Contacts --identifier "PC Suite" --useStringTable --wbxml --version
"1.1"

connection with device succeeded
Just received a new session with ID 1
Session 1 reported final. flushing
Session 1 has ended




This appears to hang the connect, similarly to what the phone does
during msynctool:

$ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vevent
Calendar --identifier "PC Suite" --useStringTable --wbxml --version
"1.1"

connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 201, Last , Next
20080501T204634Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing


Is there a different format or something I should be using with the n95?


On Thu, 2008-05-01 at 16:26 -0400, xyon wrote:

> 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

-------------------------------------------------------------------------
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

[xyon]

I apologize for the multiple messages, especially to Daniel who's
getting these in his inbox (terribly sorry).

I've found some more info that might be helpful:

$ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vcard
Contacts --identifier "PC Suite" --useStringTable --wbxml --version
"1.1"
connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last , Next
20080501T205617Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an reply to our Alert
Going to receive 83 changes

*** Here it lists all the vcards for the contacts, w00t! ***

Session 1 reported final. flushing
Received an reply to our Sync: 200
Session 1 reported final. flushing
Session 1 has ended



So Contacts look golden. Calendar appears to be what's hanging things up
(even if I disable calendar in the sync profile on the phone, it still
hangs. I've also deleted all calendar entries from the phone):

$ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vevent
Calendar --identifier "PC Suite" --useStringTable --wbxml --version
"1.1"
connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 201, Last , Next
20080501T210946Z
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing

*** Console does not report any more, phone reports "Connecting..." and
after a long delay: "Operation Timeout".***


On Thu, 2008-05-01 at 16:51 -0400, xyon wrote:

> Did some more research with the syncml-obex-client, and started using
> bluetooth. I also created a new empty addressbook and empty calendar in
> Evolution, and set them to default.
>
>
>
> This seems to work (got "Sync Complete" on the n95):
>
> $ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vcard
> Contacts --identifier "PC Suite" --useStringTable --wbxml --version
> "1.1"
>
> connection with device succeeded
> Just received a new session with ID 1
> Session 1 reported final. flushing
> Session 1 has ended
>
>
>
>
> This appears to hang the connect, similarly to what the phone does
> during msynctool:
>
> $ syncml-obex-client -b 00:xx:xx:xx:xx:xx 10 --sync text/x-vevent
> Calendar --identifier "PC Suite" --useStringTable --wbxml --version
> "1.1"
>
> connection with device succeeded
> Received an Alert for the DS Server at Calendar: Type: 201, Last , Next
> 20080501T204634Z
> Just received a new session with ID 1
> Received the DevInf
> Session 1 reported final. flushing
>
>
> Is there a different format or something I should be using with the n95?
>
>
> On Thu, 2008-05-01 at 16:26 -0400, xyon wrote:
> > 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
>
>
> -------------------------------------------------------------------------
> 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

-------------------------------------------------------------------------
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

[xyon]

Still trying to sort this issue out, but I think I may have run into an
msynctool problem, now, instead of phone/libsyncml:

I can use syncml-obex-client to grab vcards from Contacts on the phone.
With calendar disabled in the "PC Suite" profile on the phone, I can get
a successful completion with syncml-obex-client (and "sync complete" on
phone) when syncing vevent. But when I try to sync with msynctool, I get
the original results (appears to hang). I even disabled the event
objtype in msyntool's profile for evo/n95, but with the same results.

I see there is "conversion config: VCARD_EXTENSION=Evolution" for each
of the contact formats in evo's member (vcard30 and vcard21), however
there is no conversion config for the event formats in evo's member
(vevent20), nor are there any conversion configs for the n95's member
(vevent10). Since the n95 and evo use different types of vevents (20 and
10 respectively), shouldn't there be some sort of conversion config to
translate between them? Can I set this manually?


-------------------------------------------------------------------------
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

[xyon]

Got it working. Thanks to Jc2k in IRC.

I dropped back to opensync 0.22, and libsyncml 0.4.5, all worked out of
the box.

Thanks again, Jc2k for pointing out the version problem.


On Mon, 2008-05-05 at 11:13 -0400, xyon wrote:

> Still trying to sort this issue out, but I think I may have run into an
> msynctool problem, now, instead of phone/libsyncml:
>
> I can use syncml-obex-client to grab vcards from Contacts on the phone.
> With calendar disabled in the "PC Suite" profile on the phone, I can get
> a successful completion with syncml-obex-client (and "sync complete" on
> phone) when syncing vevent. But when I try to sync with msynctool, I get
> the original results (appears to hang). I even disabled the event
> objtype in msyntool's profile for evo/n95, but with the same results.
>
> I see there is "conversion config: VCARD_EXTENSION=Evolution" for each
> of the contact formats in evo's member (vcard30 and vcard21), however
> there is no conversion config for the event formats in evo's member
> (vevent20), nor are there any conversion configs for the n95's member
> (vevent10). Since the n95 and evo use different types of vevents (20 and
> 10 respectively), shouldn't there be some sort of conversion config to
> translate between them? Can I set this manually?
>
>
> -------------------------------------------------------------------------
> 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

-------------------------------------------------------------------------
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