-----Original Message----- From: Yves-Alexis Perez [mailto:corsac@debian.org] Sent: Sunday, December 27, 2009 6:51 PM To: Chen, Congwu Subject: Re: [SyncEvolution] SyncEvolution in Fremantle On 23/12/2009 09:05, Chen, Congwu wrote: > Firstly, > You may set up the log level a little large since I have not see more detailed logging. > (should be in peers/delirium/config.ini:loglevel, I think set it to 5 is enough). Ok, I've set it to 6, just in case. > > Secondly, the error is a little mysterious from my point. What I can guess is during the > second send from SyncEvolution to the phone, the underlying transport failed unexpectedly, > it's not the phone reset the connection but perhaps is it sends back some illegal data. Maybe > we will finally need to resolve to openobex debug message for help. I've attached the new log. The error seems to be: [2009-12-27 11:45:50.868] ObexTransprotAgent: Underlying transport error [2009-12-27 11:45:50.868] Aborted with unexpected result (20015) –[2009-12-27 11:45:50.868] 'SessionAbort' - Aborting Session, Status=408, ProblemSource=LOCAL [--][++] [->end] [2009-12-27 11:45:50.868] WARNING: Aborting Session with Reason Status 408 (LOCAL problem) *** [2009-12-27 11:45:50.868] --------------- Ignoring all commands in this message (after 0 sec. request processing, 0 sec. total) with Status 514 (0=none) from here on –[2009-12-27 11:45:50.868] End of 'SessionAbort' [->top] > > Is there anything visible on the phone during the sync process? Is there any manual on how > to configure the phone correctly to sync with a SyncML server over Bluetooth? Nothing is displayed on the phone. I'm not sure I can get debug logs on the device but I'm not sure anything is sent on radio. Regards (and merry Christmas), -- Yves-Alexis