Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

EngraVeer, thanks for checking on the network time sync. I guess I am going to leave well enough alone, although it does bother me not to have a basic option like time sync working. If I make any attempts to get DST calendar entries working with time sync, I'll post results here, but after all of the hassle getting to this point now, I doubt it is worth it :-)

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

so if 'time sync' is disabled, will the phone not change time when crossing time zones?

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

Another post on this very topic that may help is here:
http://forum.ppcgeeks.com/showthread.php?t=101460

Regarding "time sync" in phone setup... I ALWAYS turn it off 1st thing on any new ROM, it seems to be an old fix for a very old problem of hyperactive active sync... although it helps, active sync still autostarts way too often. I think I'll nickname it "hyperactive sync". ha! a-d-d sync, Ritalin sync..

My take? DST (Daylight Savings Time) issues based on the change a couple years ago & perhaps in addition, the issue in SP2 of XP.. a combo of both & when the patches were applied (calendar events already set).

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

I have the VZW Touch Pro 2 with the official WM 6.5 upgrade, presumably this would have any of the available DST or Time Zone Data Update tools already applied, right? Well I have the same problem of the repeating appointments I have made show up fine on my PC's Outlook calendar but are an hour earlier on the phone. If I edit the phone appointment the correct time is shown, there is nothing to change but when it displays, it shows one hour early!! No idea what to do with this. How can Microsoft still not know how to handle DST after all these years of making WinMo OS's???

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

Also even if I turn off the auto time synching feature it still resets the time and time zone on its own. I travel a lot and on my Touch Pro 1 I always left the time zone as Central, my home zone and manually fudged the time not allowing syncing. That way I could enter future appointments in whatever wrist time I'd be at when they came up. Since the time syncs now regardless of how I set the phone settings I can't do that so I had to adapt to inputing the times so they'd be right when the phone adjusted. It shoudn't have to be this hard. Indiciative of Microsofts luke warm committment to Windows Mobile all these years.

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

No argument - this is a pretty major failure, although I'm not sure if it's entirely a Microsoft/Win Mobile thing or something to do with how the time gets synced over the network, since this seems to be a major component of the problem.

Have you implemented the specific chain of instructions above? I suspect it will fix the problem. I wouldn't assume that WM 6.5 has the fix just because it's more recent, and would go ahead and apply KB975353 regardless. Remember the reset after each stage, and keep Automatic Time Sync with the network disabled.

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

Well, I thought I'd be able to abandon this thread, but no...

I was just checking my calendar again, having done nothing more with the DST issue, had left the Automatic Network Time Sync disabled, but my appointments are once again showing an hour early!!!! ](*,) ](*,) ](*,) ](*,)

I guess I'll try resetting to GMT and back again, but this is just so stinking ridiculous that I can't believe it.

unitmonster - is your Calendar still showing the correct times?

One minor consolation - my Holidays are at least staying on the correct dates. Whoop-de-doo! :???:

ETA: I went into CDMA settings, switched Time Zone back to London/GMT, clicked OK, didn't reset, and switched it back to Eastern. Each time it indicated it would change appointments to the new time zone, and it took a little bit to do it each time.

After this (again, no reset), the Calendar again showed the correct times.

So somehow this is still getting screwed up by something, even when Auto Network Time Sync is disabled, so that may not be the triggering cause, or at least not the only triggering cause.

Still a bunch of garbage...

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

DLC, my appts and all day events have stayed correct ever since "solving" my problem. However, from what you described today, it leads me to believe it is just a matter of time before things get screwed up again. Ugh!

You mentioned that you did not soft reset after you corrected the problem today. I am curious if the changes will hold for you after a hard reset.

This issue is ridiculous. This is just simple math. Between dates X and Y, move appts 1 hour ahead. How could this not be a simple fix, and why the heck is it only affecting some people???

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

Well it has survived 1 reset, and had previously survived 2-3 days of daily resets. I wonder if there is a registry setting or two that controls this behavior and some odd combination of events causes it to get reset to the prior values. I've seen this happen to a "Lock Level" registry key which gets changed on my TP2 from time to time for no good reason.

I'm tempted to post a poll to see how common this problem is or isn't.

Re: Calendar appointments off 1 hr. -- this is absolutely driving me to drink!
 

So far everything has been holding-up OK for me after applying those fixes earlier in the thread. After DLC's post though, I'm waiting for the other shoe to drop :-(

As I've said countless times and have agreed with everyone here... why does it seem an easier proposition to colonize Mars than to solve this friggin' DST problem??!!! And why are only a handful of us pulling our hair out over this? One thing's for certain... if it was a "widespread" problem (a la 2016 text messaging bug), it would've been fixed yesterday -- check that -- the day before yesterday!