opensync-users

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Ashley J G. <agi...@pu...>]

>  You're right; sdptool indicates channel 7 for this phone.

Same with my SE k608i (Hi Jason!)
(first up, sorry for breaking the thread, just signed up to the list so 
pasting from the web archives)

>  I'm not brave enough to try the --wbxml flag, since my phone is behaving
>  exactly as reported in Dave Hall's post on the 20th July.
>  Recall in that case (same phone),  the phone refused to reboot 
>  after it shut itself down. 
>
>  Dave, if you're out there, did the phone come back to life in the end?
>  Did you try it again with updated firmware (or are you too scared of your
>  girlfriend ;P)?
>
>  Cheers,
>
>  Jason.

I saw the same behaviour as you - the phone switches itself off. I have tried 
with the --wbxml option, and there is no resulting smoke. The phone does not 
switch off, instead it sits there with the "synchronising" animation, and 
stays that way until I ctrl-C the syncml-obex-client process.

I have applied a patch that Daniel Gollub posted to the opensync-devel list
http://sourceforge.net/mailarchive/forum.php?thread_id=30478831&forum_id=44498
but it has not changed the behaviour. 

ie:

[me@here]$ syncml-obex-client -b *myphoneMAC* 7 --slow-sync text/x-vcard 
addressbook --wbxml --version 1.1

connection with device succeeded
Received an Alert for the DS Server at addressbook: Type: 201, Last 0, Next 37
Slowsyncing
Just received a new session with ID 1
Session 1 reported final. flushing
 *[ wait for as long as you like - nothing happens. I press Ctl-C ]*
[me@here]$

It gets to the "Session 1 reported final. flushing" bit pretty quickly, so it 
seems like the phone is immediately knocking back the process (or we think it 
is?).

What other information might I be able to provide to help fix this? Is anyone 
able to sync with their k608i by this or another method?

I am on an x86_64 box running FC5, so Jason I would be interested if it works 
for you on what I assume is a 32bit machine, when you try the wbxml option.

-- 
Regards,
	Ashley J Gittins
	web: 	http://www.purple.dropbear.id.au
	jabber: agi...@pu...

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Dave H. <sk...@ph...>]

Hi all

On Wed, 2006-09-20 at 01:56 +1000, Ashley J Gittins wrote:
> >  You're right; sdptool indicates channel 7 for this phone.
> 
> Same with my SE k608i (Hi Jason!)
> (first up, sorry for breaking the thread, just signed up to the list so 
> pasting from the web archives)
> 
> >  I'm not brave enough to try the --wbxml flag, since my phone is behaving
> >  exactly as reported in Dave Hall's post on the 20th July.
> >  Recall in that case (same phone),  the phone refused to reboot 
> >  after it shut itself down. 
> >
> >  Dave, if you're out there, did the phone come back to life in the end?
> >  Did you try it again with updated firmware (or are you too scared of your
> >  girlfriend ;P)?
> >

After the phone sat for a day with the battery out of it, it came good
again.  Sorry for not posting a follow up on it.

I have not tried sycing the phone again via syncml over bt.  I have
tried irmc over bt just recently and it dumps the entries to files.  I
am planning to swap my gf my nokia PoS 6280, for my old SE v600i and try
to sync it with evo.  I will post more info when I have time.

I hope this helps someone.

Cheers

Dave
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
e sk...@ph...
w phpgroupware.org
j sk...@gm...
sip 393...@fw...
       _            ____                    __        __             
 _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___ 
| '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
| |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
| .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
|_|         |_|                         |_|Web based collaboration platform

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Ashley J G. <agi...@pu...>]

On Wednesday 20 September 2006 12:50, Dave Hall wrote:
> I have not tried sycing the phone again via syncml over bt.  I have
> tried irmc over bt just recently and it dumps the entries to files.

Hi Dave,
	Any details on how you managed to sync using irmc? Whenever I try doing that 
I get the same sort of problem, the phone sits there with the synchronizing 
animation going, and the PC end thinks it's waiting for something from the 
phone. I have included a log below of the output. 

This is using multisynk with the IrmcSync Konnector, over bt, same result if 
the "Phone model" setting is set to "other" or to "Sony/Ericsson T68i". 

I end up having to kill multisynk as it seems it is blocking while waiting for 
the phone. All the log output below happens very quickly, it is at the last 
line with the sendRequest() at line 765 which just sits there.

I rebooted the phone between attempts too, as I have noticed in windows that 
if I have a botched sync attempt in linux the phone won't sync with windows 
until after a phone reboot.

If anyone can see where more detailed info would help diagnose the problem 
please yell out (and please feel free to trim the log output in replies).

-- 
Regards,
	Ashley J Gittins
	web: 	http://www.purple.dropbear.id.au
	jabber: agi...@pu...

QObexClient::connectClient()
QObexClient::sendRequest( ... )
QObexTransport::setBlocking( 1 )
QObexTransport::connected( ... )
QObexClient::transportConnected()
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 19
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 19 )
QObexTransport::writeBlock(): write( 18, ., 19 ) returns 19
QObexTransport::readyWrite(): written = 19
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): ConnectPacket
QObexTransport::readBlock( 4 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 4 )
QObexTransport::readBlock(): read( 18, ., 4 ) returns 4
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 9 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 9 )
QObexTransport::readBlock(): read( 18, ., 9 ) returns 9
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read dword header value
QObexTransport::readBlock( 4 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 4 )
QObexTransport::readBlock(): read( 18, ., 4 ) returns 4
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleConnectResponse( ... )
QObexClient::handleConnectResponse(): We want a directed connection
QObexClient::handleConnectResponse(): Using connection id 1
QObexClient::handleConnectResponse(): mConnected = true;
QObexClient::makeIdle()
Got Response Packet
   Success, final bit set
        Who
        ConnectionId
QObexClient::sendRequest() at line 765
QObexClient::get( ... )
QObexClient::sendRequest( ... )
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 55
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 55 )
QObexTransport::writeBlock(): write( 18, ., 55 ) returns 55
QObexTransport::readyWrite(): written = 55
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): NormalPacket
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 285 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 285 )
QObexTransport::readBlock(): read( 18, ., 285 ) returns 285
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleGetResponse( ... )
QObexClient::handleGetResponse() Success
Got Response Packet
   Success, final bit set
        BodyEnd
QObexClient::makeIdle()
QObexClient::sendRequest() at line 765
QObexClient::get( ... )
QObexClient::sendRequest( ... )
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 57
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 57 )
QObexTransport::writeBlock(): write( 18, ., 57 ) returns 57
QObexTransport::readyWrite(): written = 57
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): NormalPacket
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 133 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 133 )
QObexTransport::readBlock(): read( 18, ., 133 ) returns 133
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleGetResponse( ... )
QObexClient::handleGetResponse() Success
Got Response Packet
   Success, final bit set
        BodyEnd
QObexClient::makeIdle()
QObexClient::sendRequest() at line 765
QObexClient::get( ... )
QObexClient::sendRequest( ... )
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 57
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 57 )
QObexTransport::writeBlock(): write( 18, ., 57 ) returns 57
QObexTransport::readyWrite(): written = 57
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): NormalPacket
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 4 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 4 )
QObexTransport::readBlock(): read( 18, ., 4 ) returns 4
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleGetResponse( ... )
QObexClient::handleGetResponse() Success
Got Response Packet
   Success, final bit set
        BodyEnd
QObexClient::makeIdle()
QObexClient::sendRequest() at line 765
QObexClient::get( ... )
QObexClient::sendRequest( ... )
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 77
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 77 )
QObexTransport::writeBlock(): write( 18, ., 77 ) returns 77
QObexTransport::readyWrite(): written = 77
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): NormalPacket
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 228 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 228 )
QObexTransport::readBlock(): read( 18, ., 228 ) returns 228
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleGetResponse( ... )
QObexClient::handleGetResponse() Success
Got Response Packet
   Success, final bit set
        BodyEnd
QObexClient::makeIdle()
QObexClient::sendRequest() at line 765
QObexClient::get( ... )
QObexClient::sendRequest( ... )
QObexTransport::sendObject( const QObexObject& )
QObexTransport::sendObject() at 165, size = 77
QObexTransport::blocking()
QObexTransport::readyWrite()
QObexTransport::writeBlock( buf, 77 )
QObexTransport::writeBlock(): write( 18, ., 77 ) returns 77
QObexTransport::readyWrite(): written = 77
QObexClient::transportPacketWritten()
QObexTransport::selectModeChanged( 1, 0 )
QObexClient::transportSelectModeChanged( ... )
QObexTransport::blocking()
QObexClient::sendRequest(): transport()->blocking(): TRUE
QObexClient::sendRequest() at line 755
QObexTransport::doSelect()
QObexTransport::doSelect(): try to select
QObexTransport::doSelect(): infinite select
QObexTransport::doSelect(): select returns 1
QObexTransport::slotIOReady()
QObexTransport::readyRead()
QObexTransport::readyRead(): try to read core header.
QObexTransport::readBlock( 3 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 3 )
QObexTransport::readBlock(): read( 18, ., 3 ) returns 3
QObexTransport::readyRead(): Header seems to be complete
QObexTransport::readyRead(): try to read additional core header.
QObexTransport::readyRead(): NormalPacket
QObexTransport::readyRead(): Try to read header id
QObexTransport::readBlock( 1 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 1 )
QObexTransport::readBlock(): read( 18, ., 1 ) returns 1
QObexTransport::readyRead(): Try to read header length
QObexTransport::readBlock( 2 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 2 )
QObexTransport::readBlock(): read( 18, ., 2 ) returns 2
QObexTransport::readyRead(): Try to read header value
QObexTransport::readBlock( 205 )
QObexTransport::blocking()
QObexTransport::readBlock( buf, 205 )
QObexTransport::readBlock(): read( 18, ., 205 ) returns 205
QObexTransport::readyRead(): packet ready
QObexClient::transportPacketRecieved( obj )
QObexClient::transportPacketRecieved() at 616
QObexClient::transportPacketRecieved() at 623, response code = Success, final 
bit set
QObexClient::handleGetResponse( ... )
QObexClient::handleGetResponse() Success
Got Response Packet
   Success, final bit set
        BodyEnd
QObexClient::makeIdle()
QObexClient::sendRequest() at line 765

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

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

在 2006-09-20三的 15:09 +1000，Ashley J Gittins写道：
> Hi Dave,
> 	Any details on how you managed to sync using irmc? Whenever I try doing that 
> I get the same sort of problem, the phone sits there with the synchronizing 
> animation going, and the PC end thinks it's waiting for something from the 
> phone. I have included a log below of the output. 

This problem is identified and fixed by cstender. But you need a
terminal to get it: run  'msynctool --filter-objtype note' on terminal
to initiate the sync. Checkout the latest svn of irmc before doing that.

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Ashley J G. <agi...@pu...>]

On Wednesday 20 September 2006 22:06, Xin Zhen wrote:
> This problem is identified and fixed by cstender. But you need a
> terminal to get it: run  'msynctool --filter-objtype note' on terminal
> to initiate the sync. Checkout the latest svn of irmc before doing that.

Thanks Xin Zhen, I am in the process now of removing all my rpm's and building 
from a latest svn checkout, will let you know how I go, thanks.

By the way, does anyone know why the spec files were recently removed from the 
repository? Would have made it easier if I could keep my system cleaner by 
building and installing rpms instead of direct installs. Were there problems 
with maintaining them?

-- 
Regards,
	Ashley J Gittins
	web: 	http://www.purple.dropbear.id.au
	jabber: agi...@pu...

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Dave H. <dav...@sk...>]

Hi Ashley,

Sorry for lagging, I am a little snowed under atm.

On Wed, 2006-09-20 at 15:09 +1000, Ashley J Gittins wrote:
> On Wednesday 20 September 2006 12:50, Dave Hall wrote:
> > I have not tried sycing the phone again via syncml over bt.  I have
> > tried irmc over bt just recently and it dumps the entries to files.
> 
> Hi Dave,
> 	Any details on how you managed to sync using irmc? Whenever I try doing that 
> I get the same sort of problem, the phone sits there with the synchronizing 
> animation going, and the PC end thinks it's waiting for something from the 
> phone. I have included a log below of the output. 
> 
> This is using multisynk with the IrmcSync Konnector, over bt, same result if 
> the "Phone model" setting is set to "other" or to "Sony/Ericsson T68i". 

I just used the kitchensync-opensync deb using the following sources
deb http://www.in.fh-merseburg.de/~jahn/ dapper main
deb-src http://www.in.fh-merseburg.de/~jahn/ dapper main 

I prefer GNOME/GTK apps, but I actually found kitchensync a litle more
user friendly and it seems to guess things a little better.

I am still yet to try a full sync with evo, as I don't want to kill my
gf's phone :)

Cheers

Dave

Re: [Opensync-users] Tips for troubleshooting syncml connect with SE phone

[Ashley J G. <agi...@pu...>]

On Thursday 21 September 2006 22:41, Dave Hall wrote:
> I just used the kitchensync-opensync deb using the following sources
> deb http://www.in.fh-merseburg.de/~jahn/ dapper main
> deb-src http://www.in.fh-merseburg.de/~jahn/ dapper main

Thanks Dave. Turns out that the clue Xin Zhen gave me was enough to get things 
up and running.

After a fresh build out of the repository I have sync with the SE k608i 
working from the command line with opensync.

I set up a group with two members, a kdepim-sync member and an irmc-sync 
member, the latter configured as:

<config>
  <donttellsync>false</donttellsync>
  <connectmedium>bluetooth</connectmedium>
  <btunit>00:16:20:0E:61:2F</btunit>
  <btchannel>8</btchannel>
</config>

Then running:

msynctool --sync test --filter-objtype note 

successfully syncs the data between kontact and the k608i. It seems that the 
event based stuff (events, todo) keep re-syncing across even without making 
changes to them which makes the sync slow, so I am usually excluding those 
from the sync also using the filter-objtype option. 

My thanks to you, Xin Zhen and Jason for cluing me in along the way :-)

-- 
Regards,
	Ashley J Gittins
	web: 	http://www.purple.dropbear.id.au
	jabber: agi...@pu...