opensync-users — The place to get help for the OpenSync project

Re: [Opensync-users] irmc-sync always tries to add all entries

[Christopher S. <ope...@ch...>]

Hi Stefan,

Am Sonntag, 30. Juli 2006 17:39 schrieb Stefan Wolf:
> Hi,
>
> Since my SE K600i doesnt work properly with syncml (the error is
> "wrong initial Node: Type"), I now tried irmc-sync. I tried to sync
> my cell phone with the file plugin. The first time, everything goes
> fine:
> msynctool --sync irmcfile
> Synchronizing group "irmcfile"
> Member 2 of type file-sync just connected
> Member 1 of type irmc-sync just connected
> All clients connected or error
> Member 2 of type file-sync just sent all changes
> Received a entry 00020000002C with data of size 4 from member 1.
> Changetype ADDED
> Received a entry 000200000026 with data of size 4 from member 1.
> Changetype ADDED
> .
> .
> .
> Member 2 of type file-sync committed all changes.
> All clients have written
> Member 2 of type file-sync just disconnected
> Member 1 of type irmc-sync just disconnected
> All clients have disconnected
> The sync was successful
>
> But when I run it again, he report every contact as a conflict!
>
> msynctool --sync irmcfile
> Synchronizing group "irmcfile"
> Member 2 of type file-sync just connected
> Member 1 of type irmc-sync just connected
> All clients connected or error
> Received a entry 000200000001 with data of size 24 from member 2.
> Changetype ADDED
> Received a entry 000200000002 with data of size 24 from member 2.
> Changetype ADDED
>
> [...]
> Any suggestions?

Can you please try to reproduce this and create trace files for 
debugging? Have a look at http://www.opensync.org/wiki/tracing for more 
information. I think that there is a X-* attribute on your phone which 
cause these conflicts.

Regards,

	Christopher

Re: [Opensync-users] irmc-sync always tries to add all entries

[Xin Z. <xi...@gm...>]

在 2006-07-30日的 17:39 +0200，Stefan Wolf写道：
> The sync was successful
> 
> But when I run it again, he report every contact as a conflict!
> 
It's a known problem as far as I know.
> 
> Any suggestions?
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________ Opensync-users mailing list Ope...@li... https://lists.sourceforge.net/lists/listinfo/opensync-users

[Opensync-users] irmc-sync always tries to add all entries

[Stefan W. <wo...@fs...>]

Hi,

Since my SE K600i doesnt work properly with syncml (the error is "wrong=20
initial Node: Type"), I now tried irmc-sync. I tried to sync my cell phone=
=20
with the file plugin. The first time, everything goes fine:
msynctool --sync irmcfile
Synchronizing group "irmcfile"
Member 2 of type file-sync just connected
Member 1 of type irmc-sync just connected
All clients connected or error
Member 2 of type file-sync just sent all changes
Received a entry 00020000002C with data of size 4 from member 1. Changetype=
=20
ADDED
Received a entry 000200000026 with data of size 4 from member 1. Changetype=
=20
ADDED
=2E
=2E
=2E
Member 2 of type file-sync committed all changes.
All clients have written
Member 2 of type file-sync just disconnected
Member 1 of type irmc-sync just disconnected
All clients have disconnected
The sync was successful

But when I run it again, he report every contact as a conflict!

msynctool --sync irmcfile
Synchronizing group "irmcfile"
Member 2 of type file-sync just connected
Member 1 of type irmc-sync just connected
All clients connected or error
Received a entry 000200000001 with data of size 24 from member 2. Changetyp=
e=20
ADDED
Received a entry 000200000002 with data of size 24 from member 2. Changetyp=
e=20
ADDED
=2E
=2E
=2E
Member 2 of type file-sync just sent all changes
Received a entry 00020000002C with data of size 4 from member 1. Changetype=
=20
ADDED
Received a entry 000200000026 with data of size 4 from member 1. Changetype=
=20
ADDED
=2E
=2E
=2E
Member 1 of type irmc-sync just sent all changes
All clients sent changes or error
Conflict for Mapping 0x808c890:
Entry 1:
UID: 00020000002C
=46ile: 00020000002C
Size: 115

Entry 2:
UID: 00020000002C
<?xml version=3D"1.0"?>
<contact>
  <Name>
    <LastName>ADAC Operator</LastName>
  </Name>
  <Telephone>
    <Content>+4917922411</Content>
    <Type>HOME</Type>
  </Telephone>
  <FormattedName>
    <Content>ADAC Operator</Content>
  </FormattedName>
</contact>


Which entry do you want to use? [1-9] To select a side, [D]uplicate, [I]gno=
re,=20
Keep [N]ewer:

Any suggestions?
=2D-=20
  Stefan Wolf <wo...@fs...>

Re: [Opensync-users] Some success with Nokia6680 SyncML via Bluetooth

[Daniel P. <da...@ri...>]

Daniel Gollub <dg...@su...> writes:
> On Wednesday 26 July 2006 11:50, Daniel Pittman wrote:
>> The specific errors I hit are:
>>
>> All conflicts have been reported
>> Error writing entry libkcal-256941553.509 to member 1: content type was not
>> configured Mapping Write Error: content type was not configured
> There seems to be a problem of detecting/setting the object type (todo or 
> event) of the synced entry from the cellphone. That is the reason why the 
> kdepim-sync plugin is not able to write this entry. (The file-sync plugin 
> should be able to write this "unknown" object type...) 
>
> So i guess it is a problem of the syncml plugin or maybe of libsyncml.
>>
>> (Member 1 is the SyncML client connected to the Nokia 6680)
>>
>>
>> Also:
>>
>> The sync failed: Unable to write one or more objects
>> Error synchronizing: Unable to write one or more objects
>> Pipe closed! Exiting.
>> Pipe closed! Exiting.
>> QFile::writeBlock: Write operation not permitted
>>
>> The final error looks like something has failed to write out data as
>> expected.
>>
>>
> Can you try to reproduce this and create trace files for more debugging 
> information. http://www.opensync.org/wiki/tracing

Hrm.  Small problem: that includes all the contact details for people in
my phone, some of which I can't make available to the general public.

Is there any easy way to address that issue without rendering the trace
files completely useless?


Also, on a not-unrelated note, is there any easy way to reset the sync
group without needing to delete and recreate it?  In testing this I had
OpenSync duplicate a bunch of calendar data, which is a minor PITA.

> Also interesting would be the information in which format the vcal or
> vtodo is stored. Use the --dumpinfo paramter of the syncml-obex-client
> if you use the syncml obex connection.

I hope these are the right details, as follows.  I have included the
summary from the Contact stuff, and a subset of the objects reported
with the Calendar data.  Let me know if you need more and I will send it
directly.

Regards,
        Daniel

daniel@enki:~$ syncml-obex-client -b 00:12:62:B4:57:5C 11 --identifier "PC Suite" --version 1.1 --wbxml --dumpinfo --sync 'text/x-vcard' Contacts
connection with device succeeded

[...]

========================================
Man: NOKIA
Mod: 6680
FirmwareVersion: (null)
SoftwareVersion: 4.04.07
HardwareVersion: (null)

ReceiveLimit: 0
MaxObjSize: 0
Connection used: Obex
Identifier: PC Suite

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

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


daniel@enki:~$ syncml-obex-client -b 00:12:62:B4:57:5C 11 --identifier "PC Suite" --version 1.1 --wbxml --dumpinfo --sync 'text/x-vcalendar' Calendar
connection with device succeeded
Received an Alert for the DS Server at Calendar: Type: 200, Last 20060726T094241Z, Next 20060730T140127Z
Just received a new session with ID 17
Going to request the devinf
Session 17 reported final. flushing
Received an reply to our Alert
Going to receive 4 changes
Received the DevInf
Session 17 reported final. flushing
Received a added entry 125 of size 281 and type text/x-vcalendar
                Data: BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VTODO
UID:125
SUMMARY:SWOT analysis
DUE:20060803T000000
X-EPOCTODOLIST:To-do list
STATUS:NEEDS ACTION
X-EPOCAGENDAENTRYTYPE:TODO
CLASS:PUBLIC
DCREATED:20060727T000000
LAST-MODIFIED:20060727T103000
PRIORITY:2
END:VTODO
END:VCALENDAR

Received a added entry 126 of size 292 and type text/x-vcalendar
                Data: BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
UID:126
SUMMARY:Farmers market
DTSTART:20060805T080000
DTEND:20060805T123000
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PRIVATE
DCREATED:20060730T000000
LAST-MODIFIED:20060730T023100
PRIORITY:0
STATUS:NEEDS ACTION
END:VEVENT
END:VCALENDAR

[...]

Received an reply to our Sync: 200
Session 17 reported final. flushing
Session 17 has ended
Send the output below to the libsyncml developers

========================================
Man: NOKIA
Mod: 6680
FirmwareVersion: (null)
SoftwareVersion: 4.04.07
HardwareVersion: (null)

ReceiveLimit: 0
MaxObjSize: 0
Connection used: Obex
Identifier: PC Suite

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

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

-- 
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707        email: co...@di...
                 http://digital-infrastructure.com.au/

Re: [Opensync-users] SonyEricsson K750i Irmc-Sync <-> KDEPIM works .... for the most part

[Christopher S. <ope...@ch...>]

Hi Achim,

Am Samstag, 29. Juli 2006 21:06 schrieb Achim Spangler:
> Hi,
>
> I reported some weeks ago on still existing problems with German
> Umlauts, Resetting mobile phone and bad sync conflicts.
> [...]
> PLEASE PLEASE DEAR developers check the attachement and derive
> decision plans to let opensync ignore in future those differences.

Thanks a lot for your feedback. I'll have a look at it tomorror.

Best regards

	Christopher

[Opensync-users] SonyEricsson K750i Irmc-Sync <-> KDEPIM works .... for the most part

[Achim S. <Ach...@mn...>]

Hi,

I reported some weeks ago on still existing problems with German Umlauts, 
Resetting mobile phone and bad sync conflicts.

At first the technical details:
1) Kubuntu Dapper with fresh updated system
2) Opensync packages for UbuntuDapper which are build from a member of this
   list - BIG BIG THANKS!!!!
3) SonyEricsson K750i with Firmware version R1N035
   --> probably quite old, but last time I checked O2 hadn't released newer
       version
   (so I would have to let a service shop upgrade my firmware to a non-branded
    newer version, or not?)
4) KDE 3.5.3 (as updated from the semi-offical KDE Kubuntu Repo)


At first I was a irritated, as my mobile was STILL resetted with the new 
merged irmc-sync plugin. But some evaluation revealed, that the sync-group 
CACHE had some VERY VERY BAD DATA CACHED in my $HOME/.opensync/ SO THAT MY 
MOBILE PHONE WAS CRASHED BY SOME RUBBISH FROM OLDER TRIES!!!!
==>
1) The OpenSync programs shouldn't cause problems, when the current
   version of both sides don't contain any reference to broken cached
   entries (in my case it was probably a event at date, where neiter
   my mobile phone nor KDEPIM listed an event!!)
2) there should be a call parameter option to multisync to clear any
   cached data for a sync group.
   At least I had to create a complete new group, to get a fresh start.

OK - after I had created a new syncgroup, had cleared the complete mobile 
phone contact list (after backing it up) and had initially filtered 
everything but contacts OUT, I got my first successfull sync!!! Yippie

I was also able to successfully sync later with all parts including notes, 
calendar ..

Here some comments which I fill with debug information in the anonymized 
attachement.
1) It would be very fine, when debug messages on broken utf8 encoding would
   list also the affected words (or line), so that I have a chance to search
   KDEPIM and my mobile for those illegal data.
   EVEN BETTER:
   msynctool would immediately stop at thos positions, and would allow the
             user to define a corrected text

2) There are still several <tag> types for events and contacts, which are
   differing between KDEPIM and irmc-sync/K750i, so that the user gets lots
   of erroneous conflict reports.
   I attache several conflict reports, where I replaced all personal data I
   was aware of


PLEASE PLEASE DEAR developers check the attachement and derive decision plans 
to let opensync ignore in future those differences.

Thanks,
Achim

Re: [Opensync-users] Problem with make of opensync

[Daniel G. <dg...@su...>]

On Saturday 22 July 2006 08:40, John Najarian wrote:
> =A0 =A0I run Fedora 5 and tried building opensync-0.14.
> When I ran 'autoreconf -sfi' I got the following

Don't build the version 0.14. The current stable release of OpenSync is 0.1=
8.
The source tarballs of the opensync package got renamed since version 0.15=
=20
from opensync to libopensync. ("opensync" =3D=3D libopensync).

best regards,
Daniel

Re: [Opensync-users] Some success with Nokia6680 SyncML via Bluetooth

[Daniel G. <dg...@su...>]

On Wednesday 26 July 2006 11:50, Daniel Pittman wrote:
> The specific errors I hit are:
>
> All conflicts have been reported
> Error writing entry libkcal-256941553.509 to member 1: content type was not
> configured Mapping Write Error: content type was not configured
There seems to be a problem of detecting/setting the object type (todo or 
event) of the synced entry from the cellphone. That is the reason why the 
kdepim-sync plugin is not able to write this entry. (The file-sync plugin 
should be able to write this "unknown" object type...) 

So i guess it is a problem of the syncml plugin or maybe of libsyncml.

>
> (Member 1 is the SyncML client connected to the Nokia 6680)
>
>
> Also:
>
> The sync failed: Unable to write one or more objects
> Error synchronizing: Unable to write one or more objects
> Pipe closed! Exiting.
> Pipe closed! Exiting.
> QFile::writeBlock: Write operation not permitted
>
> The final error looks like something has failed to write out data as
> expected.
>
>
Can you try to reproduce this and create trace files for more debugging 
information. http://www.opensync.org/wiki/tracing
Also interesting would be the information in which format the vcal or vtodo is 
stored. Use the --dumpinfo paramter of the syncml-obex-client if you use the 
syncml obex connection.

best regards,
Daniel

[Opensync-users] Some success with Nokia6680 SyncML via Bluetooth

[Daniel P. <da...@ri...>]

G'day.  Using the Ubuntu packages kindly provided by Matthias Jahn I
have been somewhat successful in getting a sync between my Nokia 6680
and my Linux system.

Thank you *very* much for this -- this is a great step forward, and I am
looking forward to things polishing off; it is great to see the progress
that OpenSync is making.

A sync between the phone and a file target runs smoothly, but trynig to
sync KDE-PIM seems to have problems.

Having checked the bug tracker, it looks like the KDE-PIM, or possibly
SyncML, side of things isn't working right at the moment.

The specific errors I hit are:

All conflicts have been reported
Error writing entry libkcal-256941553.509 to member 1: content type was not configured
Mapping Write Error: content type was not configured

(Member 1 is the SyncML client connected to the Nokia 6680)


Also:

The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects
Pipe closed! Exiting.
Pipe closed! Exiting.
QFile::writeBlock: Write operation not permitted

The final error looks like something has failed to write out data as
expected.


So, is this expected - are the KDE and SyncML plugins currently
incompatible, or is this something else?

Regards,
        Daniel
-- 
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707        email: co...@di...
                 http://digital-infrastructure.com.au/

Re: [Opensync-users] new cell phone

[<bu...@gm...>]

Hi, 

Dnia 26-07-2006, śro o godzinie 15:58 +0200, Daniel Gollub napisał(a):

> Can you try to reproduce this with the irmc-development branch? Also with 
> enabled OSYNC_TRACE to get more detailed information. 

I have seen a lot of development and tested irmc development branch
several weeks ago - more less with the same results as before. I decided
it was a work in progress needing more time, but I will do more testing
including OSYNC_TRACE this weekend. I already created a ticket on
encoding including part of the trace several months ago
(http://www.opensync.org/ticket/155). Is it better to send new traces to
the list or use the ticket system?


> > - tasks and calendar entries are messed up
> > - I don't know if it possible to sync notes (evolution 2.6 features
> > memos module)
> should work with the irmc-sync plugin.
Do you know how to set up config files to include notes? As for tasks
and events I'll try to check it again. They always synced well for the
first sync and broke with updates (resulting in double entries etc.). 


-- 
Regards
Rafał Próchniak

[Opensync-users] Any new Release?

[Daniel E. <es...@gm...>]

Have you consider to release a new version of Opensync?

If the proyect release new versions regulary the potencial testers
could have a try and send bugs reports and patchs.

--=20
Trabajar, la mejor arma para tu superaci=F3n
"de grano en grano, se hace la arena" (R) (entr=E1mite, pero para los
cuates: LIBRE)

Re: [Opensync-users] still problems syncing with syncml-http-server and p900

[Maciek B. <ma...@bo...>]

I can confirm, I have got a very similar behaviour. I have tried with the 
addressbook and not calendar. At the end of the data, the synchronization 
hangs. I still don't know why, however.

Your config seems fine.

./Maciek

On Thursday 27 July 2006 22:59, Olivier Smeesters wrote:
> Hi,
>
> I upgraded my packages from Matthias' repository and tried again the
> P900 sync. It went a little further but still did not complete.
> It seems the PDA sent all its calendar entries. Opensync answered with a
> lot of commands(?) and then... nothing happened anymore.
>
> Here are the packages:
> libopensync-plugin-evolution2          0.18+svn20060606-dapper1
> libopensync-plugin-file                0.18+svn20060606-dapper1
> libopensync-plugin-palm                0.18+svn20060606-1.1
> libopensync-plugin-syncml              0.18+svn20060614-dapper1
> libopensync0                           0.18.1+svn20060725-dapper1
> libsoup2.2-8                           2.2.93-0ubuntu1
> libsyncml-utils                        0.4.0+svn20060706-dapper2
> libsyncml0                             0.4.0+svn20060706-dapper2
> multisync-cli                          0.18+svn20060621-dapper1
> multisync-gui                          0.18+svn20060629-3
> opensyncutils                          0.18.1+svn20060725-dapper1
>
> Is there anything I can do to make it go to the end ?
>
> (I've the logs & network capture but they don't fit on the mailing
> list.)
>
> By the way, is this a correct configuration for the P900 ?
> <config>
>   <username>olivier</username><password>1234</password>
>   <url>/</url><port>5079</port>
>   <usestringtable>0</usestringtable>
>   <onlyreplace>0</onlyreplace><recvLimit>0</recvLimit>
>   <maxObjSize>0</maxObjSize>
>   <contact_db>addressbook</contact_db>
>   <calendar_db>calendar</calendar_db>
>   <note_db>notes</note_db>
> </config>
>
> My P900 is configured with
> - server: http://169.254.1.65:5079
> - username: olivier
> - password: 1234
> - protocol: HTTP (no connection authentication)
>
> Thanks,
>
>
> Olivier
>

Re: [Opensync-users] new cell phone

[Daniel G. <dg...@su...>]

On Sunday 23 July 2006 19:11, Rafa=C5=82 Pr=C3=B3chniak wrote:
> 2. Irmc in general promises to work (at least transfers contacts
> properly to Evolution), but:
> - Polish characters (it may also break other languages) are lost when
> syncing phone back from Evolution
Can you try to reproduce this with the irmc-development branch? Also with=20
enabled OSYNC_TRACE to get more detailed information.=20

((
export OSYNC_TRACE=3D/tmp/osync_trace;
mkdir /tmp/osync_trace;
msynctool ---sync *yourgroup*
))

In the trace log files are information stored about the used encoding which=
=20
should help to fix your encoding problems.

Christopher has done many work to fix encoding problems.

> - tasks and calendar entries are messed up
> - I don't know if it possible to sync notes (evolution 2.6 features
> memos module)
should work with the irmc-sync plugin.

>
> Perhaps with proper amount of trial and error it is possible to get it
> working, but I don't really have time to test it (it involves manual
> editing of config files and manual removal of broken contacts from the
> phone). I decided to give up and next time get a device with better (out
> of the box?) support...
The irmc-sync config for the S65 via Bluetooth should look like this:

<connectionmedium>bluetooth</connectionmedium>
<btunit>FF:FF:FF:FF:FF:FF</btunid>
<btchannel>5</btchannel>

>
> If you're interested in Siemens (R.I.P.), you might take a look at 75
> series - S75 and SL75 (and maybe others) come with linux support (XMPM -
> phone manager for linux), which relies on opensync. I haven't tested
> those, XMPM can't recognize S65. There is a better chance to make them
> work, especially with syncml though.
>
> Siemens phones have at least one advantage - easy access to phone memory
> (via FUSE and SieFS) via irda, cable or bluetooth.
so far as i know siefs works also with obex like the irmc-sync plugin.

best regards,
Daniel

Re: [Opensync-users] still problems syncing with syncml-http-server and p900

[Olivier S. <ol...@sm...>]

Hi,

I upgraded my packages from Matthias' repository and tried again the
P900 sync. It went a little further but still did not complete.
It seems the PDA sent all its calendar entries. Opensync answered with a
lot of commands(?) and then... nothing happened anymore.

Here are the packages:
libopensync-plugin-evolution2          0.18+svn20060606-dapper1
libopensync-plugin-file                0.18+svn20060606-dapper1
libopensync-plugin-palm                0.18+svn20060606-1.1
libopensync-plugin-syncml              0.18+svn20060614-dapper1
libopensync0                           0.18.1+svn20060725-dapper1
libsoup2.2-8                           2.2.93-0ubuntu1
libsyncml-utils                        0.4.0+svn20060706-dapper2
libsyncml0                             0.4.0+svn20060706-dapper2
multisync-cli                          0.18+svn20060621-dapper1
multisync-gui                          0.18+svn20060629-3
opensyncutils                          0.18.1+svn20060725-dapper1

Is there anything I can do to make it go to the end ?

(I've the logs & network capture but they don't fit on the mailing
list.)

By the way, is this a correct configuration for the P900 ?
<config>
  <username>olivier</username><password>1234</password>
  <url>/</url><port>5079</port>
  <usestringtable>0</usestringtable>
  <onlyreplace>0</onlyreplace><recvLimit>0</recvLimit>
  <maxObjSize>0</maxObjSize>
  <contact_db>addressbook</contact_db>
  <calendar_db>calendar</calendar_db>
  <note_db>notes</note_db>
</config>

My P900 is configured with 
- server: http://169.254.1.65:5079
- username: olivier
- password: 1234
- protocol: HTTP (no connection authentication)

Thanks,


Olivier

Re: [Opensync-users] libopensync-plugin-synce compile errors on fc5?

[Tako S. <qui...@pa...>]

 > Hi,

>  
> Noticed a while back someone having problems compiling
> libopensync-plugin-synce, but not much info beyond 'works for me' :^)
> 
> Not really interested in rolling my own RPMs, simple compile from source
> would make me smile :)
> 
> Copied below is output fail and also relevant(?) info from log.  Any
> suggestions welcome.  (Suspect this is something fairly simple I'm missing?)
> 
> Regards,
> Morgan.

I have the same problem and it seems related to the "mimedir" library somehow.

Removing it from the configure script makes it go a lot further but fails in the end of course.

Cheers,
-Tako

Re: [Opensync-users] =?iso-8859-1?q?still_problems_syncing_with=09syn?= =?iso-8859-1?q?cml-http-server_and_p800?=

[matthias j. <jah...@fr...>]

Am Montag, 24. Juli 2006 10:50 schrieben Sie:
> On Thu, 2006-07-20 at 12:02 -0700,
> As for the P900 opensync connection, I'm blocked in the same position as
> you are (connection blocked after a first exchange of messages). I sent
> a message on the mailing list, no answer.=20

maybe you read the false .... it was topic on opensync-devel ;-)

if you are using debian or ubuntu ... than you could try my repro at :
http://www.in.fh-merseburg.de/~jahn/

there i have included a patch from =20
Maciek Borowka <ma...@bo...> that should help with Sony Ericsson P90=
0=20
or Sony Ericsson P910.


> I tried to contact Armin Bauer  (as stated on the SyncML page of the
> opensync doc) but no answer either.=20

Armin is currently busy  with his study at university ....

> If you find something, I would be very happy to hear about it.

Matthias

Re: [Opensync-users] =?iso-8859-1?q?still_problems_syncing_with=09syn?= =?iso-8859-1?q?cml-http-server_and_p800?=

[Maciek B. <ma...@bo...>]

On Monday 24 July 2006 10:50, Olivier Smeesters wrote:
> In case nobody else told you, the problem is that you PDA is using the
> mrouter protocol (as it's called). It's trying to resolve
> wsockhost.mrouter through the DNS server advertised in the PPP
> connection. If you don't put such a DNS in place, it will not work.

The simplest solution is to:
1. Forget about bind
2. Add "169.254.1.68 wsockhost.mrouter" to /etc/hosts
3. Install and lauch dnsmasq package

dnsmasq is much simpler than bind, uses /etc/hosts and by default automaticaly 
detects all interfaces.

> As for the P900 opensync connection, I'm blocked in the same position as
> you are (connection blocked after a first exchange of messages). I sent
> a message on the mailing list, no answer. 
> (as stated on the SyncML page of the opensync doc) but no answer either.
> If you find something, I would be very happy to hear about it.

You'll find your happiness here:
<http://sourceforge.net/mailarchive/forum.php?thread_id=26641219&forum_id=44498>
(there are still problems, later during the sync, however)

./Maciek

Re: [Opensync-users] still problems syncing with syncml-http-server and p800

[Olivier S. <Ol...@Sm...>]

On Thu, 2006-07-20 at 12:02 -0700,
ope...@li... wrote:
> Message: 6
> Date: Thu, 20 Jul 2006 14:22:39 +0200
> From: Ciro Scognamiglio <mo...@ol...>
> Subject: Re: [Opensync-users] still problems syncing with
>         syncml-http-server and p800
> To: ope...@li...

Hi,

> BTW I am also having problems having the ppp connection up for more
> than
> 2min... I am using gnubox...but this is another topic...

In case nobody else told you, the problem is that you PDA is using the
mrouter protocol (as it's called). It's trying to resolve
wsockhost.mrouter through the DNS server advertised in the PPP
connection. If you don't put such a DNS in place, it will not work.

This is true for any communication channel of the P800/P900, infrared,
bluetooth and USB (as they all get to a PPP connection).

See http://www.alfonsomartone.itb.it/hcpcpi.html for a workable
solution.

I don't remember if it is explained there but there is catch in the
setup of the DNS server. In short, you want to put a small DNS server on
your PC that will answer this query. But BIND (the name server daemon)
will only bind to the interfaces that exists when it starts. As your PPP
connection is (most probably) not yet there, you would need to restart
it. Another way is to set the DNS server entry in ppp as the IP address
of a fixed ethernet adapter. As its a fixed adapter, it will be present
when BIND starts and as its on the PPP server, it will be accessible
from the P900.

As for the P900 opensync connection, I'm blocked in the same position as
you are (connection blocked after a first exchange of messages). I sent
a message on the mailing list, no answer. I tried to contact Armin Bauer
(as stated on the SyncML page of the opensync doc) but no answer either.
If you find something, I would be very happy to hear about it.

Best regards,


O Smeesters

Re: [Opensync-users] new cell phone

[<bu...@gm...>]

Dnia 22-07-2006, sob o godzinie 10:31 +0200, Florian Preinstorfer
napisał(a):
> hello everybody,
> Sorry for contacting the list , but i want to buy a new cell phone and
> in that case i want synchronize it with my linux box. 
> has anybody of you experience with one of those devices?
> 
> Siemens S65

I've been struggling to get S65 to sync properly with both multisync and
opensync. My experiences - they're not perfectly representative:

1. I haven't tested syncml (at least not after it got support for <1.2).
I'm not even sure if s65 supports syncml over bluetooth or usb (http is
supported). I want to test it, but I don't have enough time...

2. Irmc in general promises to work (at least transfers contacts
properly to Evolution), but:
- Polish characters (it may also break other languages) are lost when
syncing phone back from Evolution
- tasks and calendar entries are messed up 
- I don't know if it possible to sync notes (evolution 2.6 features
memos module)

Perhaps with proper amount of trial and error it is possible to get it
working, but I don't really have time to test it (it involves manual
editing of config files and manual removal of broken contacts from the
phone). I decided to give up and next time get a device with better (out
of the box?) support... 

If you're interested in Siemens (R.I.P.), you might take a look at 75
series - S75 and SL75 (and maybe others) come with linux support (XMPM -
phone manager for linux), which relies on opensync. I haven't tested
those, XMPM can't recognize S65. There is a better chance to make them
work, especially with syncml though. 

Siemens phones have at least one advantage - easy access to phone memory
(via FUSE and SieFS) via irda, cable or bluetooth. 

I hope this helps.

Cheers,
Rafał Próchniak

Re: [Opensync-users] new cell phone

[daniel f. <dan...@gm...>]

hi flo,

here is such list: http://www.opensync.org/wiki/DeviceCompatibilityList=20
feel free to test your phone and post your results :-)

best regards,
daniel

Am Samstag, den 22.07.2006, 10:31 +0200 schrieb Florian Preinstorfer:
> hello everybody,
> Sorry for contacting the list , but i want to buy a new cell phone and
> in that case i want synchronize it with my linux box.=20
> has anybody of you experience with one of those devices?
>=20
> Siemens S65
> Motorola L6
> Sagem my300x
>=20
> I couldn't find any of those devices in the Hardware Compatiblity
List.
>=20
> maybe you can send me your experiences?
>=20
> thanks in advance,
> flo
>=20
>=20
>=20
>
-------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to
share your
> opinions on IT & business topics through brief surveys -- and earn
cash
>
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

[Opensync-users] new cell phone

[Florian P. <Flo...@gm...>]

hello everybody,
Sorry for contacting the list , but i want to buy a new cell phone and
in that case i want synchronize it with my linux box. 
has anybody of you experience with one of those devices?

Siemens S65
Motorola L6
Sagem my300x

I couldn't find any of those devices in the Hardware Compatiblity List.

maybe you can send me your experiences?

thanks in advance,
flo

[Opensync-users] Problem with make of opensync

[John N. <jna...@ya...>]

Hello,

   I run Fedora 5 and tried building opensync-0.14. 
When I ran 'autoreconf -sfi' I got the following

autoreconf -sfi
acinclude.m4:5: warning: underquoted definition of
AM_PATH_CHECK
  run info '(automake)Extending aclocal'
  or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
acinclude.m4:5: warning: underquoted definition of
AM_PATH_CHECK
  run info '(automake)Extending aclocal'
  or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
[root@localhost opensync-0.14]# automake

So I ran 'automake' which completed with nothinhg and
then ran './configre' and got the following:
[root@localhost opensync-0.14]# ./configure
checking for a BSD-compatible install...
/usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name...
a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler...
yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none
needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none
required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler...
(cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached)
none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler...
(cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached)
none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output...
/bin/sed
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object
files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries...
pass_all
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler...
yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... f95
checking whether we are using the GNU Fortran 77
compiler... yes
checking whether f95 accepts -g... yes
checking the maximum length of command line
arguments... 32768
checking command to parse /usr/bin/nm -B output from
gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag  works... yes
checking if gcc supports -fno-rtti -fno-exceptions...
no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports
shared libraries... yes
checking whether -lc should be explicitly linked in...
no
checking dynamic linker characteristics... GNU/Linux
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for f95 option to produce PIC... -fPIC
checking if f95 PIC flag -fPIC works... yes
checking if f95 supports -c -o file.o... yes
checking whether the f95 linker (/usr/bin/ld) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux
ld.so
checking how to hardcode library paths into
programs... immediate
checking whether stripping libraries is possible...
yes
checking for bison... bison -y
checking for pkg-config... /usr/bin/pkg-config
checking for libxml-2.0... yes
checking XML_CFLAGS... -I/usr/include/libxml2
checking XML_LIBS... -lxml2 -lpthread -lz -lm
checking check.h usability... no
checking check.h presence... no
checking for check.h... no
configure: Checking to see if we can build Python
bindings
checking for a Python interpreter with version >=
2.2... python
checking for python... /usr/bin/python
checking for python version... 2.4
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.4/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.4/site-packages
checking for pyrexc... no
checking for headers required to compile python
extensions... found
configure: WARNING: Couldn't find either Pyrex or the
Python headers, not building Python bindings
checking for glib-2.0 gmodule-2.0 gobject-2.0
gthread-2.0 sqlite3... yes
checking PACKAGE_CFLAGS... -pthread
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
checking PACKAGE_LIBS... -Wl,--export-dynamic -pthread
-lgmodule-2.0 -ldl -lgobject-2.0 -lgthread-2.0
-lglib-2.0 -lsqlite3
configure: creating ./config.status
config.status: creating Makefile
config.status: creating opensync/Makefile
config.status: creating tools/Makefile
config.status: creating tests/Makefile
config.status: creating formats/Makefile
config.status: creating formats/vformats-xml/Makefile
config.status: creating osengine/Makefile
config.status: creating opensync-1.0.pc
config.status: creating opensync-1.0-uninstalled.pc
config.status: creating osengine-1.0.pc
config.status: creating osengine-1.0-uninstalled.pc
config.status: creating Doxyfile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

========================================
  Pythong Bindings:       Disabled
  Unit Tests:             Disabled
  Debug messages:         Enabled
  Tracing:                Enabled
  Profiling:              Disabled
  Sync Engine:            Enabled
  Tools:                  Enabled

Now build opensync and install it.
Afterwards go into the plugins directory
and build the plugins you need.
========================================

Now I ran 'make' and got the following:
[root@localhost opensync-0.14]# make
cd . && /bin/sh
/home/Johnnyboy/OpenSync/opensync-0.14/missing --run
autoheader
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make  all-recursive
make[1]: Entering directory
`/home/Johnnyboy/OpenSync/opensync-0.14'
Making all in opensync
make[2]: Entering directory
`/home/Johnnyboy/OpenSync/opensync-0.14/opensync'
if /bin/sh ../libtool --tag=CC --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I.. -pthread
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   
 -Wall -I/usr/include/libxml2   -Werror 
-DOPENSYNC_PLUGINDIR=\"/usr/local/lib/opensync/plugins\"
-DOPENSYNC_CONFIGDIR=\"/usr/local/share/opensync/defaults\"
-DOPENSYNC_FORMATSDIR=\"/usr/local/lib/opensync/formats\"
-g -O2 -MT opensync_env.lo -MD -MP -MF
".deps/opensync_env.Tpo" -c -o opensync_env.lo
opensync_env.c; \
then mv -f ".deps/opensync_env.Tpo"
".deps/opensync_env.Plo"; else rm -f
".deps/opensync_env.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -pthread
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-Wall -I/usr/include/libxml2 -Werror
-DOPENSYNC_PLUGINDIR=\"/usr/local/lib/opensync/plugins\"
-DOPENSYNC_CONFIGDIR=\"/usr/local/share/opensync/defaults\"
-DOPENSYNC_FORMATSDIR=\"/usr/local/lib/opensync/formats\"
-g -O2 -MT opensync_env.lo -MD -MP -MF
.deps/opensync_env.Tpo -c opensync_env.c  -fPIC -DPIC
-o .libs/opensync_env.o
cc1: warnings being treated as errors
opensync_env.c: In function 'osync_file_read':
opensync_env.c:706: warning: pointer targets in
passing argument 3 of 'g_io_channel_read_to_end'
differ in signedness
make[2]: *** [opensync_env.lo] Error 1
make[2]: Leaving directory
`/home/Johnnyboy/OpenSync/opensync-0.14/opensync'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/Johnnyboy/OpenSync/opensync-0.14'
make: *** [all] Error 2

Any help would be appreciated.

Thanks,

John


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Opensync-users] msynctool --wait working again on trunk

[Eduardo P. H. <eha...@ra...>]

Hi,

(if you are not using the recent code from the trunk on the svn
repository, where the ipc-branch code was recently merged, you
don't need to worry about this message)

(Anyway, if you are not using the current code from svn trunk yet but
are interested in helping to test it, your help would be very welcome :)

The most annoying bug (for people using syncml-http-server plugin) in the
recently-merged IPC code was just fixed. 'msynctool --wait' wasn't working
in the new code yet, because sync alerts weren't being handled by
osplugin.

I've just added the code for this on svn trunk. It is working when using
file-sync and the sync alert generated by monitoring the directory.
Unfortunately I couldn't test it using syncml-http-server, right now,
but it is supposed to work with syncml-http-server and other plugins
that support sync alerts.

Please let me know (preferably through the bug reporting on
www.opensync.org, but you can mail me if you like) if you still have
any problems with the new code.

Regards,

-- 
Eduardo

Re: [Opensync-users] still problems syncing with syncml-http-server and p800

[matthias j. <jah...@fr...>]

Am Donnerstag, 20. Juli 2006 14:22 schrieb Ciro Scognamiglio:
> matthias jahn wrote:
> >> what am I doing wrong?
> >
> > well have you tried to you wbxml?
> > syncml-http-server --port 8080 --sync \
> > text/x-vcard  /home/moray/p800 --multi --wbxml
>
> --wbxml seems not to be supported as options on the syncml-http-server I
> am using... (i.e. 0.4.0+svn20060706)

well ... i should read manpages to ;-)
<<<<
 Note that you dont have to set wbxml explicitly. libsyncml detects the=20
incoming packets and sets wbxml automatically if needed.
>>>>

you could try --slow-sync ... but i don=B4t  think it will work ...

you should definite open a bug ticket at http://libsyncml.opensync.org for =
it.
And append the tracefiles you get (export SYNCML_TRACE=3D/path/to/log/dir)
see syncml-http-server manpage..

> > Also what version did you use ?
>
> I am using the ubuntu dapper packages from
> http://www.in.fh-merseburg.de/~jahn/
>
> version ~0.18+svn20060614 ATM.

libopensync0 0.18+svn20060710-dapper1.2 ?

That is current svn ..... so the sync with msynctool  and syncml-http-serve=
r=20
will currently not work for you ..   (and me to ... ;-( )


> > Why don=B4t you try irmc with your device?
> >  ... as far as i know your device should support it...
> >
> > (look at http://www.opensync.org/attachment/ticket/244/irmc-sync.conf
> > for a example config over bluetooth ...
> > )
>
> That would have solved a lot of problems :(
> no, IrMC is not supported either on the p800 and the p900 devices.
> The only sync method supported is syncml over http.

sad .... i thought you are a happy one with irmc ...

> BTW I am also having problems having the ppp connection up for more than
> 2min... I am using gnubox...but this is another topic...

i am using gnubox to .... so maybe i could help you with this=20


Matthias
________

Debian, Ubuntu  SVN OpenSync Repro at:
        http://www.in.fh-merseburg.de/~jahn/

Re: [Opensync-users] still problems syncing with syncml-http-server and p800

[Ciro S. <mo...@ol...>]

matthias jahn wrote:

>> what am I doing wrong?
>=20
> well have you tried to you wbxml?=20
> syncml-http-server --port 8080 --sync \=20
> text/x-vcard  /home/moray/p800 --multi --wbxml
>=20

--wbxml seems not to be supported as options on the syncml-http-server I
am using... (i.e. 0.4.0+svn20060706)

> Also what version did you use ?=20

I am using the ubuntu dapper packages from
http://www.in.fh-merseburg.de/~jahn/

version ~0.18+svn20060614 ATM.

> If you use current svn ... the --wait command is currently broken .... =
;-(
>=20
> Why don=B4t you try irmc with your device?
>  ... as far as i know your device should support it...
>=20
> (look at http://www.opensync.org/attachment/ticket/244/irmc-sync.conf
> for a example config over bluetooth ...
> )
>=20

That would have solved a lot of problems :(
no, IrMC is not supported either on the p800 and the p900 devices.
The only sync method supported is syncml over http.

BTW I am also having problems having the ppp connection up for more than
2min... I am using gnubox...but this is another topic...

C.