Menu
▾
▴
opensync-users — The place to get help for the OpenSync project
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(10) |
Apr
(30) |
May
(11) |
Jun
(8) |
Jul
(28) |
Aug
(113) |
Sep
(74) |
Oct
(43) |
Nov
(111) |
Dec
(31) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(70) |
Feb
(78) |
Mar
(110) |
Apr
(99) |
May
(106) |
Jun
(128) |
Jul
(65) |
Aug
(123) |
Sep
(80) |
Oct
(128) |
Nov
(80) |
Dec
(54) |
| 2007 |
Jan
(89) |
Feb
(83) |
Mar
(56) |
Apr
(56) |
May
(69) |
Jun
(29) |
Jul
(89) |
Aug
(44) |
Sep
(32) |
Oct
(114) |
Nov
(36) |
Dec
(46) |
| 2008 |
Jan
(88) |
Feb
(100) |
Mar
(63) |
Apr
(27) |
May
(39) |
Jun
(61) |
Jul
(35) |
Aug
(11) |
Sep
(9) |
Oct
(19) |
Nov
(28) |
Dec
(72) |
| 2009 |
Jan
(33) |
Feb
(4) |
Mar
(15) |
Apr
(24) |
May
(17) |
Jun
(17) |
Jul
(11) |
Aug
(30) |
Sep
(19) |
Oct
(8) |
Nov
(10) |
Dec
(5) |
| 2010 |
Jan
(5) |
Feb
(10) |
Mar
(12) |
Apr
(1) |
May
(8) |
Jun
(4) |
Jul
(9) |
Aug
(29) |
Sep
(6) |
Oct
(19) |
Nov
(4) |
Dec
(3) |
| 2011 |
Jan
(9) |
Feb
|
Mar
|
Apr
(7) |
May
(2) |
Jun
(9) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
|
Nov
(7) |
Dec
|
| 2012 |
Jan
(2) |
Feb
(5) |
Mar
(5) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(9) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|
From: Simon J. <si...@jo...> - 2008-02-12 09:45:34
|
Michael Bell <mic...@cm...> writes: > Simon Josefsson schrieb: > >> First I sync the phone with isync on Mac OS X. Then I create a opensync >> installation, one syncml-obex-client and one file sink. I sync once >> first, which is a slow sync, populating the local file sink. I sync >> again, and this time it is a fast sync, with no changes. I can also >> force a slow sync, which also works fine with no changes. >> >> The problem starts if I now sync the phone on the Mac. The sync on the >> mac works fine. >> >> When I after that try to synchronize using opensync, things break. What >> happens is that opensync decides to do a fast sync. Is that the correct >> decision? > > Are you sure that a normal Two-Way Sync is performed? Oops, I typed wrong, I meant full sync there. I inferred this because the phone sent all contacts (1/123, 2/123, 3/123, ...), whereas for quick sync's, it just says 'Syncing..' or something like that. Is it the correct decision to do a full sync then? I assume the sync with iSync incremented a counter somewhere, which would trigger a full sync in opensync. Confirming this would be one step forward in my understanding. > OpenSync does not know anything about iSync. So if you start OpenSync > it think it starts a normal Two-Way Sync. Now the SyncML part of the > story begins. The DS client (your phone) sends a Slow-Sync or a > Two-Way Sync with a LAST and a NEXT anchor. If your phone sends > Slow-Sync request then the plugin immediately switch the sink to > Slow-Sync mode. If the plugin receives a wrong LAST anchor then > Slow-Sync is activated too. So the important question is, does > OpenSync really makes a Slow-Sync? The mode switch is not displayed at > the normal console. > > If you enabled traces then grep the logfiles for the string > smlDsSessionSendAlert. The second parameter in the parenthesis is the > alert type. The numbers are compliant with the OMA DS spec (200 - > TWO-WAY-SYNC, 201 - SLOW-SYNC. I confirmed that it says 201 when i sync after running isync. This results in dupe entries added to the file-sync, see output last in this message. >> What happens is that opensync retrieves all entries from the phone, and >> adds them to the local 'file-sync' sink. The id's are the same, so to >> avoid overwriting the file, it adds '-new' to each filename. If I >> perform this several times, I can get 'X-new-new-new' or even worse. > > This is what I'm observing too but I think this is a logical problem > because the merger should compare the entries and detect the > duplicates. BUT: I only understand the syncml code. I'm a normal user > if we are discussing about non-syncml stuff :( The problem is that msynctool slow-sync appear to work in two different ways: 1) normal slow-sync, triggered by --slow-sync or initial run. This appears to pull in all entries from all devices, i.e. both from the file-sync and syncml-obex-client stores. the entries are then merged, and the result is pushed back to each backend. This works fine. 2) slow-sync after running isync, likely triggered by the phone rather than opensync? This seems to do a fast-sync against the file-sync (no entries are transferred from file-sync) but a slow-sync against syncml-obex-client. This leads to pulling in duplicate entries into file-sync, because none of its entries were pulled in for merge handling. Output from 1) and 2) respectively below. Note how entries are transferred FROM the file-sync only in case 2). The problem in 1) seems to be that msynctool doesn't request a slow-sync from ALL devices when one of them does a full sync. Does this make sense to anyone who understand the opensync design better? Thanks, /Simon Output from running msynctool after isync: jas@mocca:~$ msynctool --sync e51-file Synchronizing group "e51-file" contact sink of member 2 of type syncml-obex-client just connected contact sink of member 1 of type file-sync just connected Main sink of member 1 of type file-sync just connected Main sink of member 2 of type syncml-obex-client just connected All clients connected or error Main sink of member 2 of type syncml-obex-client just sent all changes contact sink of member 1 of type file-sync just sent all changes Main sink of member 1 of type file-sync just sent all changes Received an entry 15 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 24 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 27 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 52 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 58 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 63 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 80 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 101 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 120 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 137 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 138 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 155 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 185 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 192 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 193 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 194 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 214 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 606 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 608 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 612 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 614 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 615 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 616 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 618 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 620 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 629 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 635 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 636 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 637 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 638 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 652 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 654 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 662 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 664 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 666 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 670 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 672 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 674 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 678 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 687 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 690 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 696 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 698 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 702 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 704 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 705 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 707 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 710 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 726 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 727 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 736 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 737 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 756 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 760 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 761 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 762 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 763 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 764 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 766 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 767 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 769 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 770 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 771 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 773 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 774 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 777 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 779 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 781 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 782 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 787 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 790 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 791 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 794 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 798 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 799 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 801 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 803 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 804 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 806 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 807 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 808 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 809 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 810 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 811 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 812 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 813 from member 2 (syncml-obex-client). Changetype ADDED element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed. Received an entry 814 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 815 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 816 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 817 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 819 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 820 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 821 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 822 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 826 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 827 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 828 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 829 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 830 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 831 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 838 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 839 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 840 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 841 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 842 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 843 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 844 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 845 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 846 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 847 from member 2 (syncml-obex-client). Changetype ADDED contact sink of member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported Received an reply to our sync contact sink of member 2 of type syncml-obex-client committed all changes. Sent an entry 15-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 24-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 27-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 52-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 58-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 63-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 80-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 101-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 120-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 137-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 138-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 155-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 185-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 192-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 193-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 194-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 214-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 606-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 608-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 612-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 614-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 615-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 616-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 618-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 620-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 629-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 635-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 636-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 637-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 638-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 652-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 654-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 662-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 664-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 666-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 670-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 672-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 674-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 678-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 687-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 690-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 696-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 698-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 702-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 704-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 705-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 707-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 710-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 726-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 727-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 736-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 737-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 756-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 760-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 761-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 762-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 763-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 764-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 766-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 767-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 769-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 770-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 771-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 773-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 774-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 777-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 779-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 781-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 782-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 787-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 790-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 791-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 794-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 798-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 799-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 801-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 803-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 804-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 806-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 807-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 808-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 809-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 810-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 811-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 812-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 813-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 814-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 815-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 816-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 817-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 819-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 820-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 821-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 822-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 826-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 827-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 828-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 829-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 830-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 831-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 838-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 839-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 840-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 841-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 842-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 843-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 844-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 845-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 846-new-new to member 1 (file-sync). Changetype ADDED Sent an entry 847-new to member 1 (file-sync). Changetype ADDED contact sink of member 1 of type file-sync committed all changes. Main sink of member 1 of type file-sync committed all changes. Main sink of member 2 of type syncml-obex-client committed all changes. All clients have written contact sink of member 2 of type syncml-obex-client reported sync done. Main sink of member 2 of type syncml-obex-client reported sync done. contact sink of member 1 of type file-sync reported sync done. Main sink of member 1 of type file-sync reported sync done. All clients reported sync done The sync was successful contact sink of member 1 of type file-sync just disconnected Main sink of member 1 of type file-sync just disconnected contact sink of member 2 of type syncml-obex-client just disconnected ^C jas@mocca:~$ Output from running msynctool --slow-sync: jas@mocca:~$ msynctool --sync e51-file --slow-sync contact Synchronizing group "e51-file" [slow sync] The previous synchronization was unclean. Slow-syncing contact sink of member 2 of type syncml-obex-client just connected contact sink of member 1 of type file-sync just connected Main sink of member 1 of type file-sync just connected Main sink of member 2 of type syncml-obex-client just connected All clients connected or error Main sink of member 2 of type syncml-obex-client just sent all changes Received an entry 840 from member 1 (file-sync). Changetype ADDED Received an entry 804 from member 1 (file-sync). Changetype ADDED Received an entry 787 from member 1 (file-sync). Changetype ADDED Received an entry 790 from member 1 (file-sync). Changetype ADDED Received an entry 15 from member 1 (file-sync). Changetype ADDED Received an entry 702 from member 1 (file-sync). Changetype ADDED Received an entry 737 from member 1 (file-sync). Changetype ADDED Received an entry 678 from member 1 (file-sync). Changetype ADDED Received an entry 698 from member 1 (file-sync). Changetype ADDED Received an entry 727 from member 1 (file-sync). Changetype ADDED Received an entry 155 from member 1 (file-sync). Changetype ADDED Received an entry 838 from member 1 (file-sync). Changetype ADDED Received an entry 696 from member 1 (file-sync). Changetype ADDED Received an entry 839 from member 1 (file-sync). Changetype ADDED Received an entry 781 from member 1 (file-sync). Changetype ADDED Received an entry 214 from member 1 (file-sync). Changetype ADDED Received an entry 831 from member 1 (file-sync). Changetype ADDED Received an entry 618 from member 1 (file-sync). Changetype ADDED Received an entry 636 from member 1 (file-sync). Changetype ADDED Received an entry 705 from member 1 (file-sync). Changetype ADDED Received an entry 687 from member 1 (file-sync). Changetype ADDED Received an entry 817 from member 1 (file-sync). Changetype ADDED Received an entry 27 from member 1 (file-sync). Changetype ADDED Received an entry 841 from member 1 (file-sync). Changetype ADDED Received an entry 766 from member 1 (file-sync). Changetype ADDED Received an entry 774 from member 1 (file-sync). Changetype ADDED Received an entry 819 from member 1 (file-sync). Changetype ADDED Received an entry 637 from member 1 (file-sync). Changetype ADDED Received an entry 664 from member 1 (file-sync). Changetype ADDED Received an entry 80 from member 1 (file-sync). Changetype ADDED Received an entry 808 from member 1 (file-sync). Changetype ADDED Received an entry 764 from member 1 (file-sync). Changetype ADDED Received an entry 704 from member 1 (file-sync). Changetype ADDED Received an entry 63 from member 1 (file-sync). Changetype ADDED Received an entry 58 from member 1 (file-sync). Changetype ADDED Received an entry 185 from member 1 (file-sync). Changetype ADDED Received an entry 756 from member 1 (file-sync). Changetype ADDED Received an entry 816 from member 1 (file-sync). Changetype ADDED Received an entry 616 from member 1 (file-sync). Changetype ADDED Received an entry 615 from member 1 (file-sync). Changetype ADDED Received an entry 670 from member 1 (file-sync). Changetype ADDED Received an entry 810 from member 1 (file-sync). Changetype ADDED Received an entry 635 from member 1 (file-sync). Changetype ADDED Received an entry 809 from member 1 (file-sync). Changetype ADDED Received an entry 138 from member 1 (file-sync). Changetype ADDED Received an entry 803 from member 1 (file-sync). Changetype ADDED Received an entry 606 from member 1 (file-sync). Changetype ADDED Received an entry 842 from member 1 (file-sync). Changetype ADDED Received an entry 846 from member 1 (file-sync). Changetype ADDED Received an entry 827 from member 1 (file-sync). Changetype ADDED Received an entry 811 from member 1 (file-sync). Changetype ADDED Received an entry 813 from member 1 (file-sync). Changetype ADDED Received an entry 101 from member 1 (file-sync). Changetype ADDED element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed. Received an entry 814 from member 1 (file-sync). Changetype ADDED Received an entry 707 from member 1 (file-sync). Changetype ADDED Received an entry 847 from member 1 (file-sync). Changetype ADDED Received an entry 672 from member 1 (file-sync). Changetype ADDED Received an entry 674 from member 1 (file-sync). Changetype ADDED Received an entry 830 from member 1 (file-sync). Changetype ADDED Received an entry 192 from member 1 (file-sync). Changetype ADDED Received an entry 612 from member 1 (file-sync). Changetype ADDED Received an entry 710 from member 1 (file-sync). Changetype ADDED Received an entry 821 from member 1 (file-sync). Changetype ADDED Received an entry 769 from member 1 (file-sync). Changetype ADDED Received an entry 807 from member 1 (file-sync). Changetype ADDED Received an entry 826 from member 1 (file-sync). Changetype ADDED Received an entry 52 from member 1 (file-sync). Changetype ADDED Received an entry 820 from member 1 (file-sync). Changetype ADDED Received an entry 137 from member 1 (file-sync). Changetype ADDED Received an entry 777 from member 1 (file-sync). Changetype ADDED Received an entry 736 from member 1 (file-sync). Changetype ADDED Received an entry 812 from member 1 (file-sync). Changetype ADDED Received an entry 845 from member 1 (file-sync). Changetype ADDED Received an entry 770 from member 1 (file-sync). Changetype ADDED Received an entry 24 from member 1 (file-sync). Changetype ADDED Received an entry 828 from member 1 (file-sync). Changetype ADDED Received an entry 801 from member 1 (file-sync). Changetype ADDED Received an entry 771 from member 1 (file-sync). Changetype ADDED Received an entry 662 from member 1 (file-sync). Changetype ADDED Received an entry 791 from member 1 (file-sync). Changetype ADDED Received an entry 726 from member 1 (file-sync). Changetype ADDED Received an entry 620 from member 1 (file-sync). Changetype ADDED Received an entry 798 from member 1 (file-sync). Changetype ADDED Received an entry 654 from member 1 (file-sync). Changetype ADDED Received an entry 829 from member 1 (file-sync). Changetype ADDED Received an entry 767 from member 1 (file-sync). Changetype ADDED Received an entry 761 from member 1 (file-sync). Changetype ADDED Received an entry 120 from member 1 (file-sync). Changetype ADDED Received an entry 762 from member 1 (file-sync). Changetype ADDED Received an entry 806 from member 1 (file-sync). Changetype ADDED Received an entry 844 from member 1 (file-sync). Changetype ADDED Received an entry 690 from member 1 (file-sync). Changetype ADDED Received an entry 843 from member 1 (file-sync). Changetype ADDED Received an entry 638 from member 1 (file-sync). Changetype ADDED Received an entry 652 from member 1 (file-sync). Changetype ADDED Received an entry 608 from member 1 (file-sync). Changetype ADDED Received an entry 779 from member 1 (file-sync). Changetype ADDED Received an entry 193 from member 1 (file-sync). Changetype ADDED Received an entry 614 from member 1 (file-sync). Changetype ADDED Received an entry 794 from member 1 (file-sync). Changetype ADDED Received an entry 629 from member 1 (file-sync). Changetype ADDED Received an entry 815 from member 1 (file-sync). Changetype ADDED Received an entry 773 from member 1 (file-sync). Changetype ADDED Received an entry 822 from member 1 (file-sync). Changetype ADDED Received an entry 760 from member 1 (file-sync). Changetype ADDED Received an entry 194 from member 1 (file-sync). Changetype ADDED Received an entry 782 from member 1 (file-sync). Changetype ADDED Received an entry 763 from member 1 (file-sync). Changetype ADDED Received an entry 799 from member 1 (file-sync). Changetype ADDED Received an entry 666 from member 1 (file-sync). Changetype ADDED contact sink of member 1 of type file-sync just sent all changes Main sink of member 1 of type file-sync just sent all changes Received an entry 15 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 24 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 27 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 52 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 58 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 63 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 80 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 101 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 120 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 137 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 138 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 155 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 185 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 192 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 193 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 194 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 214 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 606 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 608 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 612 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 614 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 615 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 616 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 618 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 620 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 629 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 635 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 636 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 637 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 638 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 652 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 654 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 662 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 664 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 666 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 670 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 672 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 674 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 678 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 687 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 690 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 696 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 698 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 702 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 704 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 705 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 707 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 710 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 726 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 727 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 736 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 737 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 756 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 760 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 761 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 762 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 763 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 764 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 766 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 767 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 769 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 770 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 771 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 773 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 774 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 777 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 779 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 781 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 782 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 787 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 790 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 791 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 794 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 798 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 799 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 801 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 803 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 804 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 806 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 807 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 808 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 809 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 810 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 811 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 812 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 813 from member 2 (syncml-obex-client). Changetype ADDED element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed. Received an entry 814 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 815 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 816 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 817 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 819 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 820 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 821 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 822 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 826 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 827 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 828 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 829 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 830 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 831 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 838 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 839 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 840 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 841 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 842 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 843 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 844 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 845 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 846 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 847 from member 2 (syncml-obex-client). Changetype ADDED contact sink of member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported Received an reply to our sync contact sink of member 2 of type syncml-obex-client committed all changes. Main sink of member 2 of type syncml-obex-client committed all changes. contact sink of member 1 of type file-sync committed all changes. Main sink of member 1 of type file-sync committed all changes. All clients have written contact sink of member 2 of type syncml-obex-client reported sync done. Main sink of member 2 of type syncml-obex-client reported sync done. contact sink of member 1 of type file-sync reported sync done. Main sink of member 1 of type file-sync reported sync done. All clients reported sync done The sync was successful contact sink of member 1 of type file-sync just disconnected contact sink of member 2 of type syncml-obex-client just disconnected Main sink of member 1 of type file-sync just disconnected Main sink of member 2 of type syncml-obex-client just disconnected All clients have disconnected jas@mocca:~$ |
|
From: Kamstra T. <sun...@de...> - 2008-02-12 09:37:35
|
Ciao, Are you a frequennt visitor of retaiil softtware stores? We know what you're overpaaying for: - box manufacturring - CD - salespeerson salary - Reent of shop spaace - Year-to-yearr increasinng taxes in your counntry Well, what for ?! You're able to downlooad evverything legally NOW! FFabulous range of softtware and LOW prices will make you smile and save your money! Welcome to http://estelapeifferxc.blogspot.com And society is rather inclined to make a pet of yet for to make you more certaine and for my better and every negro slave within the confines of the suitable where it lighted, and quickened, whilst and prabhadrakas,to support him. With those hosts double, and in a moment they were in comparative abbey, they were destroyed by the huguenots. The moved not. firmly resolved to acquire merit, no when they put the 'lectric cars on down there. I am a dead man, he muttered, by way of answer position, thou regardest thyself very highly, the foaming brown water instead of looking out 'they who never solicit alms, they who cultivate learned brahmans conversant with the atharvans prakriti, are characterised by these three attributes. |
|
From: Ohliger <oh...@fh...> - 2008-02-11 21:22:35
|
Hi Bert, perhaps I can give you an advice to solve one problem of yours. > Message: 1 > Date: Mon, 11 Feb 2008 21:03:20 +0100 > From: "Bert Haverkamp" <be...@be...> > Subject: [Opensync-users] syncing N73 over bluetooth > To: ope...@li... > Message-ID: > <1e6...@ma...> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello All, > > I have seen several reports that the N73 can be synced. > However, I keep running into problems. > > I used opensync 0.19 as well as 0.22 on debian. > msynctool reports: > Member 2 of type syncml-obex-client had an error while getting > changes: Request not successfull: 67 > > On the phone I simply see "system error" > > Can anyone share their successtory with the N73, because I am out of > options.. I am syncing my Nokia 6110, and first I also got the system error message on my cellular phone. After I connected the phone with the Nokia Suite (Software for Windows:-() MMSync was installed on my phone. After that the syncing works fine. > Bert > > My syncml-obex-client.conf looks like this: > <config> > <bluetooth_address>XX:XX:XX:XX:XX:XX</bluetooth_address> > <bluetooth_channel>10</bluetooth_channel> > <identifier>PC Suite</identifier> > <version>1</version> > <wbxml>1</wbxml><username></username><password></password> > <type>2</type> > <usestringtable>1</usestringtable> > <onlyreplace>0</onlyreplace> > <recvLimit>10000</recvLimit> > <maxObjSize>0</maxObjSize> > <contact_db>Contacts</contact_db> > <calendar_db>Calendar</calendar_db> > <note_db>Notes</note_db> > </config> -- Mit freundlichen Grüßen / Best regards Kevin Ohliger Dipl.-Ing.(FH) Kevin Ohliger Doctoral Student University of Applied Sciences Heide Faculty of Engineering Fritz-Thiedemann-Ring 20 D 25746 Heide Germany Tel.: ++49 481 8555-327 Email: oh...@fh... WWW: http://fh-westkueste.de |
|
From: Bert H. <be...@be...> - 2008-02-11 20:03:19
|
Hello All, I have seen several reports that the N73 can be synced. However, I keep running into problems. I used opensync 0.19 as well as 0.22 on debian. msynctool reports: Member 2 of type syncml-obex-client had an error while getting changes: Request not successfull: 67 On the phone I simply see "system error" Can anyone share their successtory with the N73, because I am out of options.. Bert My syncml-obex-client.conf looks like this: <config> <bluetooth_address>XX:XX:XX:XX:XX:XX</bluetooth_address> <bluetooth_channel>10</bluetooth_channel> <identifier>PC Suite</identifier> <version>1</version> <wbxml>1</wbxml><username></username><password></password> <type>2</type> <usestringtable>1</usestringtable> <onlyreplace>0</onlyreplace> <recvLimit>10000</recvLimit> <maxObjSize>0</maxObjSize> <contact_db>Contacts</contact_db> <calendar_db>Calendar</calendar_db> <note_db>Notes</note_db> </config> -- ----------------------------------------------- Bert en Selena www.bertenselena.net ----------------------------------------------------- There are 10 kind op people in the world: those who understand binary, and those who don't. |
|
From: Jörg A. <jo...@ar...> - 2008-02-10 18:45:41
|
Hallo Robin (and other) am Montag, 4. Februar 2008 schriebst Du: > Last time I tried it, msynctool using OBEX over Bluetooth crashed the P1i, > and I have seen similar reports elsewhere. pls, can you (or someone with p1i) make a "sdptool browse" and send me the output. Depends the output from the bluetooth adapter? I miss on my p1i the profile SYNCML or IRMC, so I got only this services: Service Name: AVRCP Target Service Name: AVRCP Controller Service Name: m-Router Connectivity Service Name: m-Router Connectivity Service Name: Personal Ad-hoc User Service Service Name: Group Ad-hoc Network Service Service Name: Phonebook access PSE Service Name: Audio Streaming Source Service Name: SEMC HLA Service Name: Dial-up Networking Service Name: Headset Audio Gateway Service Name: Hands-free Audio Gateway Service Name: Object Push Service Name: File transfer I think, i need SYNCML, or? > YMMV > -Robin Jörg Arlandt |
|
From: Benjamin G. <Be...@gm...> - 2008-02-09 00:01:05
|
Hi,
This is a reply to the post of Christoph Blank on Feb 08, 2008
I have subscribed to this list only after having read this message in the
archives, so i have to apologize for not being able to reply directly
inside his thread.
> Hi,
>
> I'm using version 0.22 with the evolution and IRMC plugins.
> I'm trying to sync my SE w810i via USB (cable) but always
> receive this error either in multisync-gui or msynctool:
>
> Member 1 of type irmc-sync had an error while connecting: Cannot
> connect via OBEX.
> Member 2 of type evo2-sync just connected
> Member 2 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
Until a few hours ago, I had the same problem with my new SonyEricsson
K550i. However I did some experimental research and managed to make it
work, although it includes some very specific hack with the source code and
is surely not applicable to the average user nor intended by the developer
of the software.
First, you have to make sure, that obex is working fine. Make sure
permissions on the USB device are properly set. I may be wrong, the method
I describe here does not access /dev/ttyACM0 but a more lowlevel usb
device. On my gentoo system this is for example /dev/bus/usb/001/008 the
latter numbers varying accordng to usb bus and time of plugging in. Check
that file for permissions.
Test obex with:
-------------------------------
$ obex_test -u
Using USB transport, querying available interfaces
Interface 0: Sony Ericsson Sony Ericsson K550 Sony Ericsson Device 069 USB
WMC OBEX Interface
Use 'obex_test -u interface_number' to run interactive OBEX test client
$ obex_test -u 0
Using USB transport
OBEX Interactive test client/server.
> c
Tx: 80 00 10 10 00 FF FF 4A 00 09 4C 69 6E 75 78 00
Connect OK!
Version: 0x10. Flags: 0x00
> d
Tx: 81 00 03
Disconnect done!
> q
------------
If this is all fine, but the irmc-plugins still shows an error, it seems
that the plugin does not access the right device. Since there is absolutely
no documentation on irmc-plugin using cable, I did not manage to find out
what to write into <cabledev>
So I read the source code of obex_test an realized that it uses a different
method of connecting to the USB device than the opensync irmc-plugin. I
modified the source code of irmc-plugin to use the same method -- and there
it worked! Now you have to write the interface number printed by obex_test
into <cabledev> instead of a device file
Of course this is a ugly hack and I did not test whats going on if you enter
non-digits into the field or if you specify the wrong interface. Also you
have to recompile the plugin from source by yourself (which is no problem
for me since I use gentoo)
> The config for IRMC is as follows (note is disabled since I read this
> causes problems)
I dont know any details but on my machine it did only work if I disable it
directly on the command line
msynctool --sync SE-sync --filter-objtype note
filter.conf created by kitchensync did not work or was not properly
configured. (?)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Filter>
<filter>
<contact/>
<event/>
<todo/>
<data/>
</filter>
>
> <config>
> <connectmedium>cable</connectmedium>
> <irname></irname>
> <irserial></irserial>
> <cabletype>0</cabletype>
> <cabledev>/dev/ttyACM0</cabledev>
> </config>
my irmc-sync.conf:
<config>
<connectmedium>cable</connectmedium>
<cabletype>0</cabletype>
<cabledev>0</cabledev>
</config>
> Calender settings should work too.
>
> I tried to use an older version (debian unstable) of multisync,
> which worked in one direction (phone to evolution) but not the
> other, so I upgraded to 0.22.
>
> Now I always get this obex message and I'm stuck, can't find any
> resources about it.
>
> Can anyone please give me a hint? Unfortunately I have no Infrared
> or Bluetooth on this machine.
>
Pleas note, that I am not an experienced C coder. So please does anyone
improve and strengthen the new code. Also I did not look at the 0.3x
branch. Maybe this issue is already solved there.
> Thank you,
> Christoph
Regards,
Ben
diff -uar libopensync-plugin-irmc-0.22.orig/src/irmc_obex.c
libopensync-plugin-irmc-0.22/src/irmc_obex.c
--- libopensync-plugin-irmc-0.22.orig/src/irmc_obex.c 2007-03-27
13:49:52.000000000 +0200
+++ libopensync-plugin-irmc-0.22/src/irmc_obex.c 2008-02-09
00:52:08.000000000 +0100
@@ -523,9 +523,14 @@
#endif
break;
case MEDIUM_CABLE:
- if (!(handle = OBEX_Init(OBEX_TRANS_CUST, obex_event, 0)))
- return(0);
- OBEX_RegisterCTransport(handle, &cabletrans);
+ //if (!(handle = OBEX_Init(OBEX_TRANS_CUST, obex_event, 0)))
+ // return(0);
+ //OBEX_RegisterCTransport(handle, &cabletrans);
+
+ if(! (handle = OBEX_Init(OBEX_TRANS_USB, obex_event, 0))) {
+ osync_error_set(userdata->error, OSYNC_ERROR_GENERIC, "OBEX_Init
failed.");
+ return(0);
+ }
break;
}
OBEX_SetUserData(handle, (gpointer) userdata);
@@ -539,6 +544,8 @@
obexdata_t *userdata;
struct sockaddr_un addr;
+ obex_interface_t *obex_intf;
+ int intf_num, interfaces_number;
userdata = (obexdata_t*) OBEX_GetUserData(handle);
userdata->connected = 0;
@@ -556,11 +563,18 @@
ret=OBEX_TransportConnect (handle, (struct sockaddr*) &addr, 0);
break;
case MEDIUM_CABLE:
- ret=OBEX_TransportConnect (handle, (struct sockaddr*) &addr, 0);
+ intf_num=atoi(userdata->cabledev);
+ interfaces_number = OBEX_FindInterfaces(handle, &obex_intf);
+ if (intf_num >= interfaces_number) {
+ osync_error_set(error, OSYNC_ERROR_GENERIC, "Invalid interface
number");
+ return(0);
+ }
+ obex_intf += intf_num;
+ ret=OBEX_InterfaceConnect (handle, obex_intf);
break;
}
if (ret < 0) {
- osync_error_set(error, OSYNC_ERROR_GENERIC, "Cannot connect via
OBEX.");
+ osync_error_set(error, OSYNC_ERROR_GENERIC, "Cannot connect to USB via
OBEX (Patched Version).");
return FALSE;
}
userdata->connected = 1;
|
|
From: Christoph B. <c....@gm...> - 2008-02-08 17:08:41
|
Hi, I'm using version 0.22 with the evolution and IRMC plugins. I'm trying to sync my SE w810i via USB (cable) but always receive this error either in multisync-gui or msynctool: Member 1 of type irmc-sync had an error while connecting: Cannot connect via OBEX. Member 2 of type evo2-sync just connected Member 2 of type evo2-sync just disconnected All clients have disconnected The sync failed: Unable to connect one of the members The following packages are installed: libopensync-plugin-evolution2 0.22-2 libopensync-plugin-irmc 0.22-1 libopensync0 0.22-2 msynctool 0.22-2 multisync-gui 0.91.0+svn20061129-1 The config for IRMC is as follows (note is disabled since I read this causes problems) <config> <connectmedium>cable</connectmedium> <irname></irname> <irserial></irserial> <cabletype>0</cabletype> <cabledev>/dev/ttyACM0</cabledev> </config> Calender settings should work too. I tried to use an older version (debian unstable) of multisync, which worked in one direction (phone to evolution) but not the other, so I upgraded to 0.22. Now I always get this obex message and I'm stuck, can't find any resources about it. Can anyone please give me a hint? Unfortunately I have no Infrared or Bluetooth on this machine. Thank you, Christoph |
|
From: Michael B. <mic...@cm...> - 2008-02-08 10:09:38
|
Simon Josefsson schrieb: > First I sync the phone with isync on Mac OS X. Then I create a opensync > installation, one syncml-obex-client and one file sink. I sync once > first, which is a slow sync, populating the local file sink. I sync > again, and this time it is a fast sync, with no changes. I can also > force a slow sync, which also works fine with no changes. > > The problem starts if I now sync the phone on the Mac. The sync on the > mac works fine. > > When I after that try to synchronize using opensync, things break. What > happens is that opensync decides to do a fast sync. Is that the correct > decision? Are you sure that a normal Two-Way Sync is performed? OpenSync does not know anything about iSync. So if you start OpenSync it think it starts a normal Two-Way Sync. Now the SyncML part of the story begins. The DS client (your phone) sends a Slow-Sync or a Two-Way Sync with a LAST and a NEXT anchor. If your phone sends Slow-Sync request then the plugin immediately switch the sink to Slow-Sync mode. If the plugin receives a wrong LAST anchor then Slow-Sync is activated too. So the important question is, does OpenSync really makes a Slow-Sync? The mode switch is not displayed at the normal console. If you enabled traces then grep the logfiles for the string smlDsSessionSendAlert. The second parameter in the parenthesis is the alert type. The numbers are compliant with the OMA DS spec (200 - TWO-WAY-SYNC, 201 - SLOW-SYNC. > What happens is that opensync retrieves all entries from the phone, and > adds them to the local 'file-sync' sink. The id's are the same, so to > avoid overwriting the file, it adds '-new' to each filename. If I > perform this several times, I can get 'X-new-new-new' or even worse. This is what I'm observing too but I think this is a logical problem because the merger should compare the entries and detect the duplicates. BUT: I only understand the syncml code. I'm a normal user if we are discussing about non-syncml stuff :( Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Simon J. <si...@jo...> - 2008-02-07 19:35:48
|
Simon Josefsson <si...@jo...> writes: > I'll see if I can get a stable setup by always forcing slow-sync. FYI, there is semi-success here. There are no duplicates, but slow-syncing doesn't notice if I delete anything on the phone. The entry isn't removed in the local file sink. I hope this provides some useful information for someone. /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-07 18:48:06
|
I have now isolated the problem that causes duplicates to be created. This is with libsyncml 0.4.6 and opensync (core library, file-sync, syncml, and msynctool) from svn. First I sync the phone with isync on Mac OS X. Then I create a opensync installation, one syncml-obex-client and one file sink. I sync once first, which is a slow sync, populating the local file sink. I sync again, and this time it is a fast sync, with no changes. I can also force a slow sync, which also works fine with no changes. The problem starts if I now sync the phone on the Mac. The sync on the mac works fine. When I after that try to synchronize using opensync, things break. What happens is that opensync decides to do a fast sync. Is that the correct decision? The output from this fast sync is below. What happens is that opensync retrieves all entries from the phone, and adds them to the local 'file-sync' sink. The id's are the same, so to avoid overwriting the file, it adds '-new' to each filename. If I perform this several times, I can get 'X-new-new-new' or even worse. At this point, I have each entry twice in my local file sync. If I later sync again with the phone, it would probably transfer all entries from the file sink back to the phone (I prevent this by making the syncml-obex-client a read-only sink). This rapidly creates a lot of duplicates. Any ideas? I'll see if I can get a stable setup by always forcing slow-sync. /Simon jas@mocca:~$ msynctool --sync e51-file Synchronizing group "e51-file" contact sink of member 2 of type syncml-obex-client just connected contact sink of member 1 of type file-sync just connected Main sink of member 1 of type file-sync just connected Main sink of member 2 of type syncml-obex-client just connected All clients connected or error Main sink of member 2 of type syncml-obex-client just sent all changes contact sink of member 1 of type file-sync just sent all changes Main sink of member 1 of type file-sync just sent all changes Received an entry 15 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 24 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 27 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 52 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 58 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 61 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 63 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 80 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 101 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 120 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 121 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 127 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 137 from member 2 (syncml-obex-client). Changetype ADDED ... Received an entry 812 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 813 from member 2 (syncml-obex-client). Changetype ADDED element Url: Schemas validity error : Element 'Url', attribute 'Location': The attribute 'Location' is not allowed. Received an entry 814 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 815 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 816 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 817 from member 2 (syncml-obex-client). Changetype ADDED contact sink of member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported Received an reply to our sync contact sink of member 2 of type syncml-obex-client committed all changes. Main sink of member 2 of type syncml-obex-client committed all changes. Sent an entry 15-new to member 1 (file-sync). Changetype ADDED Sent an entry 24-new to member 1 (file-sync). Changetype ADDED Sent an entry 27-new to member 1 (file-sync). Changetype ADDED Sent an entry 52-new to member 1 (file-sync). Changetype ADDED ... Sent an entry 812-new to member 1 (file-sync). Changetype ADDED Sent an entry 813-new to member 1 (file-sync). Changetype ADDED Sent an entry 814-new to member 1 (file-sync). Changetype ADDED Sent an entry 815-new to member 1 (file-sync). Changetype ADDED Sent an entry 816-new to member 1 (file-sync). Changetype ADDED Sent an entry 817-new to member 1 (file-sync). Changetype ADDED contact sink of member 1 of type file-sync committed all changes. Main sink of member 1 of type file-sync committed all changes. All clients have written contact sink of member 2 of type syncml-obex-client reported sync done. Main sink of member 2 of type syncml-obex-client reported sync done. contact sink of member 1 of type file-sync reported sync done. Main sink of member 1 of type file-sync reported sync done. All clients reported sync done The sync was successful contact sink of member 1 of type file-sync just disconnected Main sink of member 1 of type file-sync just disconnected contact sink of member 2 of type syncml-obex-client just disconnected jas@mocca:~$ |
|
From: Simon J. <si...@jo...> - 2008-02-07 18:18:46
|
Simon Josefsson <si...@jo...> writes: > Simon Josefsson <si...@jo...> writes: > >> jas@mocca:~$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo > > I got it working! Building latest libsyncml from svn, the above command > works, see below. Sorry, that was with libsyncml 0.4.6, not from svn. /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-07 17:38:40
|
Michael Bell <mic...@cm...> writes: >> I've searched for this problem a bit, and it seems to happen to a lot of >> people, even with Nokia's own software. And as far as I can tell, only >> when syncing the calendar. So I do suspect it is a phone bug after all. >> I'll see if I can find a Windows machine and test syncing on it. >> >> What worries me is that others have been able to work around this bug by >> erasing their entire calendar and starting from scratch, but I can't >> even get one simple calendar entry to sync properly. Those people >> typically end up with 'Sync Error' after a few sync's though, and have >> to erase the calendar again. > > Empty calenders could be a problem until today for OpenSync's syncml > plugin. I discovered a bug which can cause problems when there are no > changes. Now the OMA DS client and server code is more separated. That may have fixed the problem for me, although my calendar wasn't empty... I think I tried libsyncml from svn before, without success. >> It doesn't build: >> >> /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: >> /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ > > Sorry, I commited in libsyncml/trunk/libsyncml and so the tools > directory was not commited. You are only missing one line ... Works fine now. I even got calendar to work. Next step is to get msynctool/opensync to do sane syncing. /Simon |
|
From: Simon J. <si...@jo...> - 2008-02-07 16:54:09
|
Simon Josefsson <si...@jo...> writes: > jas@mocca:~$ /usr/local/bin/syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcalendar Calendar --wbxml --identifier "PC Suite" --dumpinfo I got it working! Building latest libsyncml from svn, the above command works, see below. msynctool doesn't work reliably, and conflict handling seems very weird (I get tons of duplicates), but at least I can now read out both the entire list of contacts and calendar from my E51. Evgeni, which libsyncml version are you using? Build it from svn was relatively easy, in case you haven't tried it already. I don't understand why our E51 with the same software version behave differently though. /Simon connection with device succeeded Received an Alert for the DS Server at Calendar: Type: 200, Last 20080207T164937Z, Next 20080207T165100Z Slowsyncing Just received a new session with ID 1 Session 1 reported final. flushing Received an reply to our Alert Going to receive 23 changes Session 1 reported final. flushing Received a added entry 8 of size 302 and type text/x-vcalendar Data: BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT UID:lC5jWD6o4EEig56AwF8ca1 SUMMARY:Gris DTSTART:20080208T110000Z DTEND:20080209T140000Z X-EPOCAGENDAENTRYTYPE:APPOINTMENT CLASS:PRIVATE SEQUENCE:0 X-METHOD:NONE LAST-MODIFIED:20080207T124510Z PRIORITY:2 X-SYMBIAN-LUID:8 END:VEVENT END:VCALENDAR Received a added entry 9 of size 306 and type text/x-vcalendar ... Received an reply to our Sync: 200 Session 1 reported final. flushing Session 1 has ended |
|
From: Simon J. <si...@jo...> - 2008-02-07 16:40:34
|
Hi! I'm trying to go from the 0.35 builds in debian to building from
svn. Building of libsyncml, opensync, file-sync, syncml worked fine. I
have purged the old debian tools from my system. Msynctool
--listplugins prints:
jas@mocca:~$ msynctool --listplugins
Available plugins:
file-sync
syncml-http-server
syncml-http-client
syncml-obex-client
jas@mocca:~$
I removed ~/.opensync and added configuration from scratch. However,
syncing doesn't work:
jas@mocca:~$ msynctool --sync e51-file
Synchronizing group "e51-file"
contact sink of member 2 of type syncml-obex-client just connected
contact sink of member 1 of type file-sync just connected
Main sink of member 1 of type file-sync just connected
/home/jas/src/libsyncml/libsyncml/sml_support.c:443:E:smlSafeFree: Assertion "*address" failed
Aborted
jas@mocca:~$
The simpler tools also fail with similar error:
jas@mocca:~$ syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite"
Ideas? Complete config below.
/Simon
Group: e51-file
Member 2: syncml-obex-client
Configuration : <?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>...</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>0</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>
</config>
Member 1: file-sync
Configuration : <?xml version="1.0"?>
<config>
<!--
<directory>
<path></path>
<objtype>data</objtype>
</directory>
Field objformat set the object format which should be used to store.
objformat is optional - by default objformat is "file".
-->
<directory>
<path>/home/jas/sync/contact</path>
<objtype>contact</objtype>
<objformat>vcard30</objformat>
<converterpath_config></converterpath_config>
</directory>
<!--
<directory>
<path></path>
<objtype>event</objtype>
<objformat>vevent20</objformat>
<converterpath_config></converterpath_config>
</directory>
-->
</config>
|
|
From: Michael B. <mic...@cm...> - 2008-02-07 16:11:20
|
Evgeni Golov schrieb: > On Thu, 7 Feb 2008 13:54:04 +0100 Evgeni Golov wrote: > >> Received an transport error: Request not successfull: 67 >> >> That's what I get, also on Debian unstable, libsyncml 0.45 and the >> same software version on my e51, same for Calendar and Notes :( >> The phone just says "Systemfehler" (german for system error). I also >> tried using the USB cable, with no changes. > > Just to complete the confusion, I took a E65 and my old 6230i for > testing. > E65 fails with exactly the same error (however it has an old firmware > and is not mine, so I won't update it). > 6230i works fine (as long there is no keypad lock active and you use > channel 11 instead of channel 10...) > > So what the hell is going wrong on the E-series (yeah, they do sync > fine to windows :() The new Nokia phones support SyncML 1.2 and 1.1 whilst the old phones understand 1.1 only. The question is now how robust or failure tolerant are the different implementations? My M600i from Sony Ericsson is some kind of really sensible if I make small mistakes in the code - like don't sending the last package if the mobile sends no map (I fixed this today) - then the phone reports an error. This is a totally correct behaviour. The old phone which only implement 1.1 are sometimes more tolerant. Finally which protocol version do your mobiles use? BTW does the 6230i support NumberOfChanges? I discovered another bug related to this today. Even if a phone reports SupportNumberOfChanges then it only MAY send NumberOfChanges but the server MUST send it (OMA DS 1.2 Section 9 Two-Way Sync). Additionally three parallel threads are not always helpful ;) Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Michael B. <mic...@cm...> - 2008-02-07 16:01:06
|
Simon Josefsson schrieb: > Michael Bell <mic...@cm...> writes: > >>> Could the vformat problem explain why calendar syncing doesn't work, >>> when contact syncing works? >> Yes, I have myself heavy problems with OCS. Our vformat code creates >> several duplicates with the same UIDs internally. OCS detects this and >> returns errors while normal contact syncing works. > > Would this result in 'ERROR' in trace logs? I enabled tracing, but I > don't see any errors in those logs. The problem seems to be on the > phone, which fails and disconnects. This is not a library error and so this can happen without a big ERROR in the trace logs. > I've searched for this problem a bit, and it seems to happen to a lot of > people, even with Nokia's own software. And as far as I can tell, only > when syncing the calendar. So I do suspect it is a phone bug after all. > I'll see if I can find a Windows machine and test syncing on it. > > What worries me is that others have been able to work around this bug by > erasing their entire calendar and starting from scratch, but I can't > even get one simple calendar entry to sync properly. Those people > typically end up with 'Sync Error' after a few sync's though, and have > to erase the calendar again. Empty calenders could be a problem until today for OpenSync's syncml plugin. I discovered a bug which can cause problems when there are no changes. Now the OMA DS client and server code is more separated. > It doesn't build: > > /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: > /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ Sorry, I commited in libsyncml/trunk/libsyncml and so the tools directory was not commited. You are only missing one line ... Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |
|
From: Simon J. <si...@jo...> - 2008-02-07 15:35:12
|
Evgeni Golov <sar...@di...> writes: > (yeah, they do sync fine to windows :() I just tried syncing in iSync on Mac OS X, and it can synchronize calendar and contacts too. When I synchronize both using opensync and isync, I get lots of duplicates in the contacts, but that may be the duplicate filtering logic in opensync that is broken. /Simon |
|
From: Evgeni G. <sar...@di...> - 2008-02-07 15:16:30
|
On Thu, 07 Feb 2008 16:06:18 +0100 Christian Hilgers wrote: > Could you try with setting the Nokia Language to english? > I remember there was some discussion on this... Tried so, "System error"... Same on a N95 :/ |
|
From: Christian H. <Chr...@co...> - 2008-02-07 15:06:34
|
Simon Josefsson schrieb: >> That's what I get, also on Debian unstable, libsyncml 0.45 and the >> same software version on my e51, same for Calendar and Notes :( >> The phone just says "Systemfehler" (german for system error). I also >> tried using the USB cable, with no changes. Could you try with setting the Nokia Language to english? I remember there was some discussion on this... Christian -- Christian Hilgers |ConSol* Tel. +49.2102.994-423 |Consulting&Solutions Software GmbH Fax +49.2102.994-411 |Berliner Str. 101, 40880 Ratingen email: Chr...@co... |WWW: http://www.consol.de |
|
From: Evgeni G. <sar...@di...> - 2008-02-07 14:58:31
|
On Thu, 7 Feb 2008 13:54:04 +0100 Evgeni Golov wrote: > Received an transport error: Request not successfull: 67 > > That's what I get, also on Debian unstable, libsyncml 0.45 and the > same software version on my e51, same for Calendar and Notes :( > The phone just says "Systemfehler" (german for system error). I also > tried using the USB cable, with no changes. Just to complete the confusion, I took a E65 and my old 6230i for testing. E65 fails with exactly the same error (however it has an old firmware and is not mine, so I won't update it). 6230i works fine (as long there is no keypad lock active and you use channel 11 instead of channel 10...) So what the hell is going wrong on the E-series (yeah, they do sync fine to windows :() |
|
From: Evgeni G. <sar...@di...> - 2008-02-07 13:40:38
|
On Thu, 07 Feb 2008 14:29:18 +0100 Simon Josefsson wrote: > Curious! Have you tried a factory reset? (Backup phone using nokia's > software..) Uhm, no Windows here, will need to find someones laptop for that. > I do remember getting the same (incorrectly spelled!) error message a > few times, when I used the wrong channel. What is your sdptool output? > Mine is below. Have you tried channel 13 or 14 instead? Mine looks exactly the same, channel 13 gives an error, 14 just hangs (phone gives the usual error) > I also got this when the bluetooth stack on the phone (or PC) was in a > bad state, which seems to happen after a while when you trigger a lot of > 'Sync errors'. Try restarting the phone. Did so many times :( > FWIW, I tried syncing the calendar using Nokia's software under Windows, > but since I don't have Outlook installed, it can't synchronize it.. :( Hm, will fetch a Windows box now, and look what's up there. |
|
From: Simon J. <si...@jo...> - 2008-02-07 13:29:27
|
Evgeni Golov <sar...@di...> writes:
> Hi,
>
> On Wed, 06 Feb 2008 17:19:34 +0100 Simon Josefsson wrote:
>
>> syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite"
>>
>> Replace $MAC with your bluetooth MAC, and $CHANNEL with 10. This prints
>> my 153 contacts.
>
> % syncml-obex-client -b MAC 10 --slow-sync text/x-vcard
> Contacts --wbxml --identifier "PC Suite"
> connection with device succeeded
> Received an Alert for the DS Server at Contacts: Type: 201, Last , Next
> 20080207T124939Z
> Slowsyncing
> Just received a new session with ID 1
> Received the DevInf
> Session 1 reported final. flushing
> Received an transport error: Request not successfull: 67
>
> That's what I get, also on Debian unstable, libsyncml 0.45 and the
> same software version on my e51, same for Calendar and Notes :(
> The phone just says "Systemfehler" (german for system error). I also
> tried using the USB cable, with no changes.
Curious! Have you tried a factory reset? (Backup phone using nokia's
software..)
I do remember getting the same (incorrectly spelled!) error message a
few times, when I used the wrong channel. What is your sdptool output?
Mine is below. Have you tried channel 13 or 14 instead?
I also got this when the bluetooth stack on the phone (or PC) was in a
bad state, which seems to happen after a while when you trigger a lot of
'Sync errors'. Try restarting the phone.
FWIW, I tried syncing the calendar using Nokia's software under Windows,
but since I don't have Outlook installed, it can't synchronize it.. :(
/Simon
Browsing 00:1D:6E:BD:57:A1 ...
Service Name: AVRCP Target
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10000
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service RecHandle: 0x10001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Service Name: OBEX Object Push
Service RecHandle: 0x10002
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: Dial-Up Networking
Service RecHandle: 0x10003
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Imaging
Service RecHandle: 0x10004
Service Class ID List:
"Imaging Responder" (0x111b)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 15
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Imaging" (0x111a)
Version: 0x0100
Service Name: Audio Source
Service RecHandle: 0x10007
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100
Service Name: Hands-Free Audio Gateway
Service RecHandle: 0x10008
Service Class ID List:
"Handfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: Headset Audio Gateway
Service RecHandle: 0x10009
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: AVRCP Controller
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x1000a
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: SyncMLClient
Service RecHandle: 0x1000b
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100
Service Name: OBEX File Transfer
Service RecHandle: 0x1000c
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 11
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Service Name: Nokia OBEX PC Suite Services
Service RecHandle: 0x1000d
Service Class ID List:
UUID 128: 00005005-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 12
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00005005-0000-1000-8000-0002ee000001)
Version: 0x0100
Service Name: SyncML DM Client
Service RecHandle: 0x1000e
Service Class ID List:
UUID 128: 00000004-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 13
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000004-0000-1000-8000-0002ee000002)
Version: 0x0100
Service Name: Nokia SyncML Server
Service RecHandle: 0x10010
Service Class ID List:
UUID 128: 00005601-0000-1000-8000-0002ee000001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 14
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00005601-0000-1000-8000-0002ee000001)
Version: 0x0100
|
|
From: Evgeni G. <sar...@di...> - 2008-02-07 12:54:14
|
Hi, On Wed, 06 Feb 2008 17:19:34 +0100 Simon Josefsson wrote: > syncml-obex-client -b $MAC $CHANNEL --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" > > Replace $MAC with your bluetooth MAC, and $CHANNEL with 10. This prints > my 153 contacts. % syncml-obex-client -b MAC 10 --slow-sync text/x-vcard Contacts --wbxml --identifier "PC Suite" connection with device succeeded Received an Alert for the DS Server at Contacts: Type: 201, Last , Next 20080207T124939Z Slowsyncing Just received a new session with ID 1 Received the DevInf Session 1 reported final. flushing Received an transport error: Request not successfull: 67 That's what I get, also on Debian unstable, libsyncml 0.45 and the same software version on my e51, same for Calendar and Notes :( The phone just says "Systemfehler" (german for system error). I also tried using the USB cable, with no changes. |
|
From: Simon J. <si...@jo...> - 2008-02-07 09:14:06
|
Michael Bell <mic...@cm...> writes: >> Could the vformat problem explain why calendar syncing doesn't work, >> when contact syncing works? > > Yes, I have myself heavy problems with OCS. Our vformat code creates > several duplicates with the same UIDs internally. OCS detects this and > returns errors while normal contact syncing works. Would this result in 'ERROR' in trace logs? I enabled tracing, but I don't see any errors in those logs. The problem seems to be on the phone, which fails and disconnects. >> Since the phone prints an error message, it seems likely that a phone >> bug is involved. But maybe libsyncml could behave like Nokia's own >> software, to workaround this problem. My message was partially to gauge >> whether anyone else has seen this error, and if anyone compared traces >> with Nokia's software. > > This is not necessarily a phone bug. If OpenSync duplicates entries > but the new entry includes the same UID then the phone will detect > that there are two objects with the same internal UID. This is an > error and so the phone reports an error code. > > Again this is the vCard UID and not the UID of SyncML for this object. I've searched for this problem a bit, and it seems to happen to a lot of people, even with Nokia's own software. And as far as I can tell, only when syncing the calendar. So I do suspect it is a phone bug after all. I'll see if I can find a Windows machine and test syncing on it. What worries me is that others have been able to work around this bug by erasing their entire calendar and starting from scratch, but I can't even get one simple calendar entry to sync properly. Those people typically end up with 'Sync Error' after a few sync's though, and have to erase the calendar again. >>>> However, syncing the calendar fails. I've tried libsyncml 0.4.5 (in >>>> Debian), and also libsyncml 0.4.6 (manual build), with same results. I >>>> just tried libsyncml from SVN, but that just fails with >>>> 'sml_support.c:443:E:smlSafeFree: Assertion "*address" failed'. >>> The assertion was newly introduced from me to detect wrong memory >>> handling. Which subversion revision do you use? > > I fixed some of these smlSafeFree bugs today (plus some race > conditions). I introduced smlSafeFree to detect unclean memory > handling in the libsyncml code and the assertions are the consequence > :( > > newest SVN rev 365 and 3128 It doesn't build: /home/jas/src/libsyncml/tools/syncml-http-server.c: In function ‘main’: /home/jas/src/libsyncml/tools/syncml-http-server.c:369: error: ‘SmlTransportHttpServerConfig’ has no member named ‘interface’ Thanks, /Simon |
|
From: Hans V. <han...@gm...> - 2008-02-07 08:47:53
|
I have just tried to compile and run the 0.36 version (after having used 0.22 a long time and being reasonably satisfied with it, but library changes made it core dump). However when I try to synchronise I get the message: "Member 1 of type syncml-obex-client had an error while connecting: Wbxml not enabled in this build" Is there a way to force wbxml to be recognized and used in the tool chain? (I have libsyncml, libopensync, libopensync-plugin-kdepim, and ..syncml and mysynctool compiled). In the 0.22 version I could force certain things with ./configure parameters, but this cmake system makes me bang my head against the wall in frustration trying to figure out how to make sure things get compiled properly. (I already had to disable the macro that checks for a build outside of the source directory, because no matter what directory I was in, it refused to build). -- ---- Met vriendelijke groeten / With kind regards Hans Voss --------------------------------------- * Senior Consultant Open Source, Networking and Security * General Open Sourcerer * google talk enabled * blog: http://jazzterdaily.blogspot.com - Tech and other news that caught my attention. * Shared News feed: https://www.google.com/reader/public/atom/user/02723796534474865919/state/com.google/broadcast |
40 messages has been excluded from this view by a project administrator.
