[Fwd: Re: [Z-Push-dev] Nokia N900 and Z-push 1.3 RC]

[Thorsten Schnebeck]

Am Donnerstag, 29. April 2010 16:43:17 schrieb wp1133599-user:
> 
> Hi Sorry for not answering so long but I have been busy.
> 
> Out Front: I haven't been able to read the mailinglist regularly so please
> be patient if I repeat or missed something.
> 
> First : I can confirm Thorstens findings. I too always get an initial
> sync. Did you guys figure out the problem with this?
> Second: Compared to 0.3 I keep losing contact information on syncs ...
> which might be related to it being an initial sync and non of the data
> entered into the phone seems to reach the server.
> 
> Do you guys think it would be possible to find a date and time to get
> together in IRC or any other Instant Messenger to talk, maybe even VOIP. I
> would appreciate if Alain could tell me a little about his plans with the
> kolab connector and some information how it works. Since I would like to
> take on the task to create a better working Syncronization Application for
> the N900 which at least works with kolab. And I would like to know how
> Thorsten is doing with the N900.
> 
> Maybe you can include me in your private email conversation.
> 
> Thanks
> Alexander

Hi Alexander,

I would like to wait for PR1.2 (maybe in 2 weeks) on the N900 to have a stable basis when talking with the zpush devels.
So far I see no problems with the kolab backend but with zpush 1.3. You can use backend 0.4 without problems with z.push 1.2.3.
I would be nice I you can confirm this.

Bye

  Thorsten

> 
> Am Samstag, den 24.04.2010, 02:01 +0200 schrieb Thorsten Schnebeck
> <thorsten.schnebeck at gmx.net>:
> > Am Freitag 23 April 2010 23:45:17 schrieben Sie:
> >> hi Thorsten
> >> 
> >> see the attached message
> >> Alain,
> >>
> >>  Von: Sebastian Kummer <s.kummer at zarafaserver.com.br>
> >> > I would say it's related to the provisioning which was introduced in
> >> > 1.3.
> >> > I'm not sure if the N900 supports it as until today I had no device
> >> > "in hands" for testing.
> >> > 
> >> > Try enabling the loose-provisioning (z-push config). If that also
> does
> >> > not help, disable provisioning completely
> >> > (parameter provisioning).
> >> > 
> >> > Cheers,
> >> > Sebastian
> >> > 
> >> > PS. Any hints in the debug log?
> > 
> >> 
> >> Regards
> >> 
> > Hi Alain,
> > 
> > from the N900-MfE Wiki:
> >> Known issues
> >> Provisioning
> >> N900 is considered to be "non provisioning device" from Exchange server
> >> point of view. It basically means that it can
> >> not be managed from Exchange server - administrator can not wipe your
> >> device, request you to use autolock and so on.
> >> Basically, all the provisioning data received from the server is
> ignored
> >> and the server is informed that N900 MfE
> >> does not support this feature. Exchange administrator can configure the
> >> server in two ways - he/she can allow to use
> >> non-provisioning devices or disallow. In the second case N900 MfE will
> >> not work as server will reject the
> >> connection.
> > 
> > I used the new released z-push-1.3
> > 
> > first I test "loose_provisioning" -> does not work
> > Then I changed provisioning to false -> does not work
> > 
> > Then I update 1.2.3_RC to 1.2.3 -> works
> > 
> > Is not there another fundamental change between 1.2.x and 1.3:
> > For 1.2.x I have to patch diffbackend.php with this
> > 
> > +    function syncstate($state)
> > +    {
> > +        $this->_state=$state;
> > +    }
> > 
> > This was not necessary any longer when supporting 1.3 but something I
> > would call "syncstate" is exactly my problem with 1.3 as every sync
> behaves
> > like the first sync(?)
> > 
> > Bye
> > 
> >   Thorsten
> > 
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
> 
>