The old DST was not static in dates either - it was always the first Sunday in April to the Last Sunday in October. Now it is the Second Sunday in March to the First Sunday in November . . .

That's right, but it was that way for a long long long time.

This new change to DST was just a knee jerk reaction to an issue the US government thought they had, in reality it means nothing, other then a lot of headaches.

It's been proven in study after study that DST changes do not save any money, yet that was the impetus they used to shove this change through, it was a dumb move in 2005 when they approved it, a dumb move in 2007 when they implemented it, and 2 years later its' still dumb.

So, to fix this for 2009, you can change this timezone.ini file to read: (for Easter Standard Time, for instance)

 

timezone = "GMT-5 Eastern US", 300, -60, 0, 0, 3, 0, 2, 1, 0, 0, 0, 0, 11, 0, 1, 1, 0, 0, 0

 

I researched this while at work and haven't been out to my car to test yet, but that's the only way the CSV line/string format makes sense.

Tried this, didn't seem to work...

Im having the same problem! time does not stay changed when i set it to not auto correct.

I would think this is worth voicing to Pioneer, if for nothing else than to get a few emails in their support inbox. They can't ignore them if everyone who has this problem complains (hopefully).

There was a known issue with iGo 8, as far as the timezones getting set incorrectly when the automatic timezone setting was selected. It was supposed to be fixed in the R1 patch Nav N Go released in August. Nav N Go also released R1 patch 2 in December, hopefully Pioneer includes this one in their 3.0 release (if it really is coming). Not sure if patch 2 also included timezone fixes.

XDA dev post on the topic

EDIT: Just checked my iPaq 310 (same iGo version, 2007.7 maps, same Titan CPU), it has the same issue with timezones. So Pioneer and other integrators probably used a common SDK with the same bug.

I have called the tech support multiple times. It seems too many poeple have been calling them, all I have been getting is a busy signal everytime I call, they must have turned the phones off

Same issue for me. I think I'll have to bug Pioneer so my gf will shut up about it, or wait until November, whichever comes first.

I am curious, if it is a patch issue. Wont the unit adjust to DST on the date it thinks it is going to change? So in couple of weeks it should be fixed right?

Dave

I am curious, if it is a patch issue. Wont the unit adjust to DST on the date it thinks it is going to change? So in couple of weeks it should be fixed right?

 

Dave

exactly what will happen

Isn't there a clock somewhere on your dash or on your wrist?

Contacted Tech Support...

Thank you for contacting Pioneer Electronics, Inc.

I'm sorry for the clock issues. We have reported this to the engineers and they are investigating the issue.

Please make sure you have registered your unit, you will be notified of any update.

 

Thank You,

 

Pioneer Support Group

I don't mind the time being wrong, it's just that when I put in a destination and it gives me an ETA I have to do the math... Annoying that's all...

In the meantime, one option is to apply the sys.txt workaround that used to be in the iGo FAQ, then use test mode to set the timezone and time from within the WinCE control panel.

In sys.txt:

[timezone]
sync_os_timezone=0
reset_os_timezone=0

Assuming that the WinCE 5.0 image already has the DST issue patched you can boot into test mode, update sys.txt, apply your timezone and correct time via Control Panel, remove SD card and then cycle ACC. I think a reset would likely clear the setting...

Simply amazing. When satellites are launched they have to purposely set the clock wrong due to time dilation (see of Einstein's Theory of Special Relativity). Apparently by not doing so the GPS would be useless.

Yet, they can't get the DST thing down

I - too - found that the unit was resetting back to auto (and the wrong time) every time I restarted it, after trying to manually set the time.

I just told the unit I was in the wrong timezone (Atlantic time instead of EST) and it works just fine. I have a feeling that some time in April its going to be an hour fast instead, but at that point I'll switch it back.

Not a big enough deal to worry about.

I - too - found that the unit was resetting back to auto (and the wrong time) every time I restarted it, after trying to manually set the time.

 

I just told the unit I was in the wrong timezone (Atlantic time instead of EST) and it works just fine. I have a feeling that some time in April its going to be an hour fast instead, but at that point I'll switch it back.

 

Not a big enough deal to worry about.

True, it is not an issue that turns the unit into a brick, but it is something that should have been caught already. When the DST time changed many systems had similar issues - but two years later it is common knowledge that it must be addressed when programming.

The fact is someone dropped the ball who should not have.

yea i noticed that this morning

So, does anyone have a fix for this problem other than switching to East Atlantic time zone?

guys, check your unit now, mine just updated like 30mins ago,

wow, same here, it was updated today.

That's just off the wall since it's not DST change week in either the old or new schema.

mine updated too... works correct.

Yeah I think it must have corrected Yesterday, Saturday March 14th, sometime because mine was reading correctly last night.

Mine also has correct time now.

I wonder if they accidently programmed the wrong date.

Since I down loaded the 3.0 my clock is one hour fast. If I take it off of auto time zone I can change it back to Pacific standard time and it is correct for awhile but then jumps ahead an hour. If the auto time change is on I can not change anything. What a pain. Will have to wait until Mon. to call tech support.