Z-Push Zimbra Backend (Push Email, Contacts, Appointments & Tasks)

[slite]

Im not sure but this might be a DST problem. Just created an appointment somewhere in Winter and it seems to sync right. I'll investigage further when i get home from work.

[lytledd]

I2. Force close of Calendar when i want to choose visible calendars. This only happens when i have a corporate calendar added (Cyanogen 7.0.3 on Desire Z)

On the Android phones, there are issues with the supplied calendar being buggy. The only way I'm able to get it work (At least for a week) was to clear the calendar storage and re-sync. You can do this by:

Menu
Settings
Applications
Manage Applications
All Tab
Scroll down to Calendar Storage
Force Stop
Clear Data.

This was under Android 2.3.2, over the weekend Sprint pushed out 2.3.3, I'll see if it fixes this issue.

Doug

[slite]

On the Android phones, there are issues with the supplied calendar being buggy. The only way I'm able to get it work (At least for a week) was to clear the calendar storage and re-sync.
Doug

Yea thanks, i already got down to that, but for me this doesn't fix it, when i first enter the calendars dialog after clearing it is empty as the calendar app fills its storage again. I quit and reopen the dialog some times, first the google accounts appear, but as soon as the zimbra account shows up (i see it for like a second) the calendar crashes again.

But thanks anyway, highly appreciated

[liverpoolfcfan]

Q1. Is there some sync window for calendar entrys? Seems like everthing that lies back or in the future some ammount of days isnt synced to my phone. Is there any way to change this?

Yes. every phone handles it differently. Most allow you to choose - most common for non-android is 2weeks in the past, and all future.

I1. Wrong timezone....

I2. Force close of Calendar when i want to choose visible calendars. This only happens when i have a corporate calendar added (Cyanogen 7.0.3 on Desire Z)

There may well be an issue in there but my experience with android thus far has proven that Calendar is the weakest part of the system. All the code seems to have been designed for google sync, and then modified to try to make it work with ActiveSync. On top of that you are running a custom rom - I have used Samsung Galaxy S for 4-5 months and have never had a calendar force close. I have seen many issues with it - but never application crashes. The worst issue I have is with 2.3.3 the calendar keeps synching every minute. It does not seem to wait for pings as it should. I have to turn off auto-sync of the calendar, and only sync it after sending, or accepting an appointment.

Can you please reproduce the issue with a Windows Mobile phone or a Nokia MailForExchange phone.

[slite]

Yes. every phone handles it differently. Most allow you to choose - most common for non-android is 2weeks in the past, and all future.

Hmm, interresting, didn't ever notice this with the google calendars, maybe they implemented them in a different way. Thx ^^

Can you please reproduce the issue with a Windows Mobile phone or a Nokia MailForExchange phone.

Hope i will find some time in my holiday next week to further explore and investigate, i will report back as soon as i know anything.

Thanks for your time and work

[liverpoolfcfan]

Hmm, interresting, didn't ever notice this with the google calendars, maybe they implemented them in a different way. Thx ^^

On the Samsung running 2.3.3 the setting is in

Settings-->Accounts and sync-->[Exchange account]-->Account settings-->Period to sync Calendar

I can't recall what it was on Froyo (or if it was even adjustable)

[lytledd]

The worst issue I have is with 2.3.3 the calendar keeps synching every minute. It does not seem to wait for pings as it should.

I've seen this as well, but I don't think it's a 2.3.3 issue.

My Sprint EVO was upgraded to 2.3.3 over the weekend and it still syncs every 5 minutes. The 2nd Android phone (I don't know what version it's running) syncs every 5 seconds and the 1 IPhone4 that is setup also syncs every 5 seconds.

Doug

[liverpoolfcfan]

The 2nd Android phone (I don't know what version it's running) syncs every 5 seconds and the 1 IPhone4 that is setup also syncs every 5 seconds.

You mean it starts a new logon, and issues a sync command for that folder evrry few seconds? Or it includes the folder in the normal ping cycle that runs every 5 seconds, and checks for updates?

[lytledd]

Or it includes the folder in the normal ping cycle that runs every 5 seconds, and checks for updates?

I would say the latter of the 2 statements, snippet of the log below:

06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:03 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Send SyncRequest
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Found 0 message changes                                                                
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Initializing message diff engine                                                       
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] 1 messages in state                                                                    
06/07/11 07:45:08 [8697] [drwhite@fakedomain.com] Found 0 message changes                                                                
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Initializing message diff engine                                                       
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] 1 messages in state                                                                    
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Send SyncRequest                                                                       
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Found 0 message changes                                                                
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Initializing message diff engine                                                       
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] 1 messages in state                                                                    
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Found 0 message changes                                                                
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Initializing message diff engine                                                       
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Found 0 message changes
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Initializing message diff engine
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] 1 messages in state
06/07/11 07:45:13 [8697] [drwhite@fakedomain.com] Found 0 message changes

Doug

[liverpoolfcfan]

I would say the latter of the 2 statements, snippet of the log below:

Yes - those are normal, and that is how z-push works under the covers. It looks for changes to the monitored folders every 5 seconds.

You can lessen the noise in the log file by commenting out 3 of the 4 lines in diffbackend.php - function Config - as I did here. Just add // at the front of the line and your initials to remind you that you made the change. The results conveyed by those lines are mileading in any case when you use the AlterPing sync method, as zimbra.php does.


// VJS debugLog("Initializing message diff engine");

// VJS debugLog(count($this->_syncstate) . " messages in state");

// VJS debugLog("Found " . count($this->_changes) . " message changes");