Reply
Thread Tools
Posts: 306 | Thanked: 106 times | Joined on Feb 2010
#1
Dear all,

Has anybody managed to sync addressbook using opensync via bluetooth?

syncml is responding with an error as below

Code:
 syncml-obex-client -b xx:xx:xx:xx:xx:xx 25 --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" --dumpinfo
Received an transport error: Link Error: 0x0
Received an transport error: Unable to get answer
Received an transport error: Link Error: 0x0
Didnt receive the devinf though it was requested
Is there any other syncing solution? I have opensync-0.22 sync beautifully with kontact with N95.
Thanks
 
Posts: 3 | Thanked: 1 time | Joined on May 2010
#2
Hi,

I experience the same problem, but have some findings that may (or may not?) help.

According to http://www.opensync.org/wiki/trunk/syncing/syncml :
1) Restart your bluetooth service.
2) Make sure the screen is not locked on the N900.

These advises do not matter for me, but anyway...

What I have found:
3) Setting the version to 1.0 with "--version 1.0" seems to help.

4) Case matters! It should be Calendar (not calendar), Notes (not notes) and Contacts (not contacts).

The closest to success I get is this:
Code:
$ syncml-obex-client -b xx:xx:xx:xx:xx:xx 25 --version 1.0 --wbxml --identifier "PC Suite" --dumpinfo --slow-sync text/x-vcalendar Calendar --slow-sync text/plain Notes --slow-sync text/x-vcard Contacts
connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 200, Last 0, Next 1273419067
Slowsyncing
Received an Alert for the DS Server at Contacts: Type: 200, Last 0, Next 1273419067
Slowsyncing
Received an Alert for the DS Server at Notes: Type: 200, Last 0, Next 1273419067
Slowsyncing
Just received a new session with ID 1273419067
Received the DevInf
Session 1273419067 reported final. flushing
Received an transport error: Link Error: 0x0
Send the output below to the libsyncml developers

========================================
Man: Nokia
Mod: N900
FirmwareVersion: (null)
SoftwareVersion: 210.34.75
HardwareVersion: (null)

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

Databases:
DB Locations: Calendar
DB Type: text/x-vcalendar
DB Slow: 1

DB Locations: Notes
DB Type: text/plain
DB Slow: 1

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

Bluetooth: Yes
Wbxml: Yes
SyncML Version: 1.1
SupportsNumberofChanges: Yes
SupportsLargeObjects: Yes
5) Some general advises on the net are to limit the number of changes with --recvLimit and to set the --maxObjSize. I have tried both, but neither seem to matter.

Any suggestions are welcome!

libsyncml: 0.4.6
libopensync: 0.22
Distro: Fedora 12
 

The Following User Says Thank You to sgb For This Useful Post:
Posts: 306 | Thanked: 106 times | Joined on Feb 2010
#3
Thanks for your findings. Unfortunately i received the same error even with "--version 1.0". The libraries i have are:

libsyncml-0.4.6
libopensync-0.22
Distro: Gentoo x64
 
Posts: 3 | Thanked: 1 time | Joined on May 2010
#4
Seems like the "restart service" tip above has some substance after all. After leaving my laptop for dinner and returning again I got the exact same error as you.

Restarting the service did not help though, but restarting the bluetooth chip itself got me back to the "almost there" report above:

Code:
# hciconfig hci0 down
# hciconfig hci0 up
# hciconfig hci0
hci0:   Type: USB
        BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 1021:5 SCO MTU: 64:1
        UP RUNNING PSCAN ISCAN 
        RX bytes:87051 acl:737 sco:0 events:1371 errors:0
        TX bytes:44157 acl:704 sco:0 commands:584 errors:0
This behaviour seems to be some kind of power saving "feature".
 
Posts: 3 | Thanked: 1 time | Joined on May 2010
#5
An alternative, more persistent, way for me to reliably repeat my half-way-there results seems to be to load the btusb module with the reset parameter.

Test it with:
Code:
# hciconfig hci0 down
# rmmod btusb
# modprobe btusb reset=1
# hciconfig hci0 up
If this helps make it persistent with the following line in /etc/modprobe.d/options.conf or similar file:

Code:
options btusb reset=1
I have also tried to sync via USB and get the exact same behavior...

First find a SYNCML-SYNC interface:
Code:
# syncml-obex-client -u
Found 4 USB OBEX interfaces
Interface 0:
        Manufacturer: Nokia
        Product: N900 (PC-Suite Mode)
        Interface description: PC Suite Services
Interface 1:
        Manufacturer: Nokia
        Product: N900 (PC-Suite Mode)
        Interface description: SYNCML-SYNC
Interface 2:
        Manufacturer: Nokia
        Product: N900 (PC-Suite Mode)
        Interface description: PC Suite Services
Interface 3:
        Manufacturer: Nokia
        Product: N900 (PC-Suite Mode)
        Interface description: SYNCML-SYNC
Use '-u interface_number' to connect
Then try to sync via that interface (-u 1):
Code:
# syncml-obex-client -u 1 --identifier "PC Suite" --slow-sync text/x-vcard Contacts --slow-sync text/x-vcalendar Calendar --slow-sync text/plain Notes --wbxml --version 1.0 --dumpinfo
connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 200, Last 0, Next 1273577047
Slowsyncing
Received an Alert for the DS Server at Contacts: Type: 200, Last 0, Next 1273577047
Slowsyncing
Received an Alert for the DS Server at Notes: Type: 200, Last 0, Next 1273577047
Slowsyncing
Just received a new session with ID 1273577047
Received the DevInf
Session 1273577047 reported final. flushing
Received an transport error: Link Error: 0x0
Send the output below to the libsyncml developers

========================================
Man: Nokia
Mod: N900
FirmwareVersion: (null)
SoftwareVersion: 210.34.75
HardwareVersion: (null)

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

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

DB Locations: Calendar
DB Type: text/x-vcalendar
DB Slow: 1

DB Locations: Notes
DB Type: text/plain
DB Slow: 1

Bluetooth: Unknown
Wbxml: Yes
SyncML Version: 1.1
SupportsNumberofChanges: Yes
SupportsLargeObjects: Yes
For USB access you need to be root though, and obviously a cable. That is why I would prefer to sync over Bluetooth if possible.

Anyone got this working??
 
Posts: 306 | Thanked: 106 times | Joined on Feb 2010
#6
Bumping this to check if anybody has made any progress to get opensync working with N900.
__________________
------------------------------------------------------------------
Voice choppy on sip calls
Please vote for bug number 10388
 
Posts: 112 | Thanked: 26 times | Joined on Sep 2009
#7
Does syncing the calendar work?
 
Posts: 25 | Thanked: 6 times | Joined on Aug 2010
#8
I spent a few hours I won't get back, too. Looks to me like it's not gonna work with current versions of software.

The lamest of workarounds for now, at least it's something, is getting the unoficcial MoreFunctionsForAddressBook extension for Thunderbird. On the N900, export all your contacts as vcard 3.0's. Now in the Thunderbird Contacts, use Tools > MoreFunctionsForAddressBook to import them all at once.

People are working on getting Thunderbird to synchronize with Ubuntu One for Ubuntu 11.10. Until then, you can use the unofficial Hedera Contact Sync extension. But it's so alpha and new, I haven't got a clue why it works on one and not on the other.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 21:28.