opensync-users

[Opensync-users] Nokia 6280, here we go...

[Meredydd L. <mer...@go...>]

Hello there,

Well, I've walked through the walkthroughs, scoured the archives, and
others seem to be getting their Nokia 6280s to sync perfectly happily.
No such luck here. I'm using the packages from Debian sid,
freshly-installed as of tonight.

In a nutshell:

$ syncml-obex-client --slow-sync text/x-vcalendar Calendar
--identifier "PC Suite" --wbxml -b 00:xx:yy:zz:ww:uu 11
connection with device succeeded
Received an transport error: Request not successfull: 68
$

If I specify "--version 1.2" (as opposed to 1.0 or 1.1), or drop the
"--wbxml", I get an error code of 67 rather than 68. recvLimit and
maxObjSize don't seem to be making a difference. The command used
above is reported as working, at least partially, here:
http://www.nabble.com/Nokia-6280-(evo2,-syncml-obex-client)-Link-error-t2142667.html

Full traces are attached.

Meredydd

Re: [Opensync-users] Nokia 6280, here we go...

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

Hi Meredydd,

I have the same phone.

On Sun, 2006-10-15 at 20:33 +0100, Meredydd Luff wrote:
> Hello there,
> 
> Well, I've walked through the walkthroughs, scoured the archives, and
> others seem to be getting their Nokia 6280s to sync perfectly happily.
> No such luck here. I'm using the packages from Debian sid,
> freshly-installed as of tonight.
> 
> In a nutshell:
> 
> $ syncml-obex-client --slow-sync text/x-vcalendar Calendar
> --identifier "PC Suite" --wbxml -b 00:xx:yy:zz:ww:uu 11
> connection with device succeeded
> Received an transport error: Request not successfull: 68
> $
> 

You will notice that at the same time that error is generated the phone
resets itself.  After reading up more online about this phone, I think a
mad a very bad choice.  Even with the most recent firmware it is
unreliable.  This phone is the windows 98 of 3G handset - looks nice,
sells well, yet buggy as hell.

Cheers

Dave

Re: [Opensync-users] Nokia 6280, here we go...

[Meredydd L. <mer...@go...>]

On 10/16/06, Dave Hall <dav...@sk...> wrote:
> > $ syncml-obex-client --slow-sync text/x-vcalendar Calendar
> > --identifier "PC Suite" --wbxml -b 00:xx:yy:zz:ww:uu 11
> > connection with device succeeded
> > Received an transport error: Request not successfull: 68
> > $
> >
>
> You will notice that at the same time that error is generated the phone
> resets itself.
Nope, my model doesn't even blink. That said, it must be noted that
these things typically have several firmware revisions, not to mention
operator customisations, so I wouldn't be at all surprised if we were
running different versions.

> After reading up more online about this phone, I think a
> mad a very bad choice.  Even with the most recent firmware it is
> unreliable.  This phone is the windows 98 of 3G handset - looks nice,
> sells well, yet buggy as hell.
Interesting. Unlike my last (a 7250, I believe), this one has yet to
crash on me once. It's my favourite Series 40 yet...

Oh, well. If nobody else has any suggestions, I fear I shall have to
resign myself to a broken phone on an 18-month contract...

Meredydd

Re: [Opensync-users] Nokia 6280, here we go...

[Juha T. <Juh...@ik...>]

On Monday 16 October 2006 13:22, Meredydd Luff wrote:
> Nope, my model doesn't even blink. That said, it must be noted that
> these things typically have several firmware revisions, not to mention
> operator customisations, so I wouldn't be at all surprised if we were
> running different versions.

Would it be possible to add some plugin to opensync to 
check if it has network connection and check some XML file
from opensync.org which contains the latest recommendations
for firmware version? 

I guess it would be somewhat privacy issue too, so it probably
would have to be behind some kind of switch.


Tuju

-- 
Ajatteleva ihminen tarvitsee unta.