Nokia 6300 communication problems with syncml-obex-client

I am experiencing the same issue, as shown below. I am also attaching trace files.

[jas@speck libsyncml]$ syncml-obex-client -b 00:1e:a4:11:15:88 11  --slow-sync text/x-vcard  Contacts --identifier "PC Suite" --wbxml --dumpinfo
connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last 0, Next 1
Slowsyncing
Just received a new session with ID 1
Received the DevInf
Session 1 reported final. flushing
Received an transport error: Request not successfull: 68
Send the output below to the libsyncml developers

========================================
Man: Nokia
Mod: Nokia 6300
FirmwareVersion: V 05.50
14-08-07
RM-217
(c) N..
SoftwareVersion: V 05.50
14-08-07
RM-217
(c) N..
HardwareVersion: 1007

ReceiveLimit: 0
MaxObjSize: 0
Connection used: OBEX Client
Identifier: PC Suite

Databases:
DB Locations: Contacts
DB Type: text/x-vcard
DB Slow: 1

Bluetooth: Yes
Wbxml: Yes
SyncML Version: 1.1
SupportsNumberofChanges: Yes
SupportsLargeObjects: Yes

trace file (1 of 2)

trace file (2 of 2)

Also relevant: I am using opensync 0.35 - custom-compiled for my fedora 8 box, and am using libsyncml 0.4.5. I have also experimented with a variety of identifiers with the same result.

While using the Nokia PC Suite today, I made a discovery that seems consistent with the sync failure under opensync. Nokia PC Suite fails to sync the phone unless a user/password is present. Furthermore, when the sync fails under PC Suite, the feedback on the handset is identical to what I see when opensync fails. Thus, it seems as though user/password is mandatory for this phone.

I am attaching two USB capture logs. The first represents a failed sync when no user/password has been defined on either the phone or in PC Suite. The second is a successful sync using user/password of jas/adg. I told PC to only sync contacts - there was only a single test contact on both the phone and handset. Worked OK.

usb capture - failed sync

usb capture - successful sync

I'm happy to report that opensync just synced my evo contacts to the Nokia 6300 for the first time after many attempts. All I did was to add a username/password to the evo conf as shown in ticket #123.

NOTE: I am certain that I tried this repeatedly yesterday, and can only assume that opensync suddenly works because of my [first] use of PC Suite today - perhaps it brought the handset out of a previously bad state or similar?

The config used is:

[jas@speck group3]$ msynctool --showgroup eo 
Group: eo
Member 2: syncml-obex-client
        Configuration : <?xml version="1.0"?>
<config>
  <bluetooth_address>00:1e:a4:11:15:88</bluetooth_address>
  <bluetooth_channel>11</bluetooth_channel>
  <interface>0</interface>
  <!-- identifier>PC Suite</identifier -->
  <!-- identifier>Nokia PC Suite</identifier -->
  <!-- identifier>PC Suite Data Sync</identifier -->
  <identifier>PC Suite</identifier>
  <version>1</version>
  <wbxml>1</wbxml>
  <username>jas</username>
  <password>adg</password>
  <type>2</type>
  <usestringtable>0</usestringtable>
  <onlyreplace>0</onlyreplace>
  <onlyLocaltime>0</onlyLocaltime>
  <recvLimit>0</recvLimit>
  <maxObjSize>0</maxObjSize>
  <database>
     <name>Contacts</name>
     <objtype>contact</objtype>
     <objformat>vcard21</objformat>
  </database>
  <!--database>
     <name>Notes</name>
     <objtype>note</objtype>
     <objformat>vjournal</objformat>
  </database-->
</config>

Member 1: evo2-sync
        Configuration : <?xml version="1.0"?>
<config>
  <address_path>file:///home/jas/.evolution/addressbook/local/system</address_path>
  <calendar_path>default</calendar_path>
  <memos_path>default</memos_path>
  <tasks_path>default</tasks_path>
</config>

Nice catch!

Really wonder whats wrong with 6300 ...

Unfortunetly both usb log files look a bit truncate - usbsnoopy crashed while exporting? Do you still have the usbsnoppy native files?

Right. I tried the PC Suite thing earlier today, which I thought was working, but now I'm actually not sure anymore, read on.

After rebooting into Linux, I tried both using opensync and the syncml-obex-client utility, didn't get anything working (actually I wonder why it works for Jason if he got a username set...) both with or without authentication enabled.

Now I rebooted into Windows, PC Suite didn't work anymore. Using the explorer interface (which is, I suppose, not SyncML based, but part of the main PC Suite, not the sync subtool) did work fine. I made a backup of all data, did a reset of the phone using *#7780#, tried syncing again, no luck. Restored my backup, synced, no luck.

Then I decided to try the last thing I could think of: re-install firmware. Did so, tried syncing afterwards (with and without password set), and after restoring my data, all failed, both using USB and BT.

I'll attach a log of the failed BT sync.

The sync software log doesn't provide much info except this string: "PC Sync has encountered a problem and has terminated the synchronisation". If you search for it on the net, you'll see lots of people reported similar issues with different setups.

So, actually I'm wondering whether the first time I thought the sync succeeded it actually didn't, and I overlooked some warning message (as, even when sync fails, no popup dialog appears, it's just a string in some window).

USBSnoop log of failed BT search/connect/sync cycle

Some more info in case this helps with the troubleshooting.

Before use of username/password in my obex-client config suddenly worked, I was experiencing the followingn error message when doing a slow sync with msynctool:

contact sink of member 2 of type syncml-obex-client had an error: Auth required but not given

I'm still speculating about what made the sync suddenly work, and still think that PC Suite performed some sort of handset initialisation. Seeing ikke's post above, and how his handset is now not even operational under PC Suite, I'm wondering whether these handsets can fall into a state that generally precludes sync'ing.

Also, my firmware details (obtained using *#0000#) are:

Nokia 6300 V05.50 14-08-07 RM-217

Just to be clear, I found that for PC Suite to work, I needed to set a username/password on the handset under Connectivity->Data transfer->PC Synchronisation. Then, this needs to be matched in the PC Suite sync setup (and also in the msynctool obex config - I don't know whether it is possible to pass these creds to syncml-obex-client).

Re usb logs - I'm about to attach two more logs - raw and xml.

The use-case was the update of one contact from outlook to handset via PC Suite. I told PC Suite to update contacts only, and I think I have about 42 contacts in outlook now.

Hope this helps. This time, I've checked to confirm that the XML is good.

pc suite update of one contact (usblog)

pc suite update of one contact (xml)

I experience the same issue with the 6300. (Connection not working without credentials and "Auth required but not given" with username and password specified.)

I can post my log and trace files too, if this helps. I'm also very willing to try out patches. (I didn't get the latest svn version working though, even some test cases failed.)