Search Archive

F900BT Time Error

By Red Zinger · Aug 20, 2010in Problems/Troubleshooting💬 3 posts👁️ 875 views
Posted Aug 20, 2010 · 00:51 UTC#1

I had an issue with the time on the map being correct, but the time on the audio screens was incorrect (wrong time zone 3 hrs off). I called Pioneer tech support a few weeks ago. They said update firmware. I did, but it didn't fix the problem. I called again recently. Now they say it is a known issue in states that have multiple time zones when auto-correct is turned on. Apparently there is a software bug and the fix is bundled in the 2010 map update which is $120. I can't believe I have to pay to patch their software bug! :x

 

Anyway, I installed the map update a few minutes ago. Now the map and audio screens read the same time - but it's the WRONG time! I am in the part of IN in CST but it thinks I am in EST. Since I am less than an hour from the other time zone, I really want to have auto correct on so it will change as I cross zones.

 

Does anyone here have any ideas other than turning off auto-correct? Is it just another bug that Pioneer will have to patch? (and hopefully not charge $$)

Posted Aug 20, 2010 · 14:57 UTC#2

Red, check out this post on a similar timezone bug us folks in Oregon had for the longest time. Turns out there is a small percentage of the state in MST, so their bug set the entire state of OR to Boise, Idaho time (WTF?!). Sounds like the 2010 maps still have the bug in their data.zip's tzinfo.bin. :( If they don't have 2 timezones for Indiana in tzinfo.bin, maybe you can patch yours to add it (see the Florida example in the post)...

Posted Aug 20, 2010 · 22:32 UTC#3

Thanks FourG. I don't feel comfortable modding my software. Besides, it looks like I could only change the time zone of the whole state. I am in a little corner that is different from the rest of Indiana. If I did that it still wouldn't change when I crossed the time-zone borders. It would be easier to turn off auto-correct, then turn it back on when I travel east or south.

 

I just called Pioneer again. This guy said that there is no record of this problem (with Indiana) in the system despite the fact that this is my 4th call regarding this issue! He gave me a case number and sent it off to the engineers. Now I guess I just have to wait until they find enough other bugs to make distributing a patch worthwhile.