[tNtKemp]

So, as I understand it, this radio and navigation system sets the date automatically through GPS signals. I can set the time through the setup menu. Here's my problem:

As of the last week or so, the display shows a January, 2002 date. The time displayed varies every time I start the car. If I go into Setup to adjust the time, it always displays 12:00 at the top. If I change it based on 12:00 it never comes up correct. I figured out that if I know exactly how many hours and minutes the actual time it displays under normal use is off by, I can make that change off of the 12:00 it displays, then it will display the right time under normal use... Until the next time I turn the car off, them on again. The date never corrects itself. Navigations seems to work fine still... So the GPS functionality seems to be there.

Any thoughts?

 

[André-Luc]

I have same problem have you found any way to fix it?

 

[shalgiva1974]

Same Problem. I thought it was my battery but no issue lights appear.

 

[Garrydhu]

Same Problem. I thought it was my battery but no issue lights appear.

Try and disconnect the 12 v for a while?

 

[GenGwen]

Same problem.. Hopefully an update will come quickly

 

[RAMITCHELL13]

So, as I understand it, this radio and navigation system sets the date automatically through GPS signals. I can set the time through the setup menu. Here's my problem:

As of the last week or so, the display shows a January, 2002 date. The time displayed varies every time I start the car. If I go into Setup to adjust the time, it always displays 12:00 at the top. If I change it based on 12:00 it never comes up correct. I figured out that if I know exactly how many hours and minutes the actual time it displays under normal use is off by, I can make that change off of the 12:00 it displays, then it will display the right time under normal use... Until the next time I turn the car off, them on again. The date never corrects itself. Navigations seems to work fine still... So the GPS functionality seems to be there.

Any thoughts?

I have the same problem. Tried downgrading the software from the most current version (2021) to the last version. But no luck -- same issue which started 00:00 01/01/2022!
Called the software vendor - they have been getting lots of calls about this issue from Honda, Nissan, and Acura owners.
They don't have an answer either...

 

[Bev]

Yes, I have the same issue. Thanks for the information!

 

[RAMITCHELL13]

I have the same problem. Tried downgrading the software from the most current version (2021) to the last version. But no luck -- same issue which started 00:00 01/01/2022!
Called the software vendor - they have been getting lots of calls about this issue from Honda, Nissan, and Acura owners.
They don't have an answer either...

Here's Honda's official response:

Good afternoon, Ron. We're sorry about that. We're aware of the issue our engineers are looking into it. They've advised its something to do with the navi's calendar and that it will resolve itself when the date rolls over into August but they're looking for a counter measure to correct it sooner.

August? Really?

 

[RAMITCHELL13]

If you are not the original owner, contact Honda and get your VIN updated so when they have a fix, they can notify you...I just did via "chat" with a nice guy at Honda Motors.

 

[mollyrose09]

I am having same issue here! Tried the software update but still off.

 

[Megand990]

Thank god I am not the only one with this issue. It’s driving me insane because how can you not look at your navigation system and it just screws you up all together. Hopefully there will be a fix soon, but I don’t think I could bare waiting for August to get it fixed. I was thinking about getting the update thinking that would help. Clearly that isn’t going to fix our problem, but I at least know that I don’t need to go spending $150 for the 2021 update.

 

[novemer]

Same problem with my 2012 Insight Facelift in Germany. You can manually set the clock but it wont get into the navigation system for calculating arrival times etc. and it will be gone after the next restart, so its a waste of time :/

 

[RAMITCHELL13]

Thank god I am not the only one with this issue. It’s driving me insane because how can you not look at your navigation system and it just screws you up all together. Hopefully there will be a fix soon, but I don’t think I could bare waiting for August to get it fixed. I was thinking about getting the update thinking that would help. Clearly that isn’t going to fix our problem, but I at least know that I don’t need to go spending $150 for the 2021 update.

Unfortunately, doing the upgrade does not fix the issue! I have the upgrade and saved the DVD from before doing the upgrade. I downgraded the Nav to the previous version, results were the same. Re-upgraded the Nav to the newest version and then contacted Honda Motors.
keep in mind Nissans are having the same issue.

 

[JackKieser]

This is a widespread issue with computer systems after 1/1/22; it's not just affecting Honda / other vehicle nav systems. Short answer to this problem is that it is VERY common in computer programming to store date information as what is called a long integer; it's a type of data structure. What "long integer" (or long int) means is that it's an object that's a number that can be all the way up to 2147483647; any number larger than that can't fit in the storage and gets messed up. Well, guess what the date value for 1/1/2022 is? It's larger than that number, meaning ANY COMPUTER SYSTEM that stores the date as a long int is now screwed. This affected EVERY SINGLE Microsoft Office program, for instance, because Microsoft programmed every Office program (Word, Excel, Powerpoint, Outlook, etc.) to store dates as a long int back during the Y2K "crisis": they just kind of forgot to check whether or not long int would be good enough for the future... and it's not.

So, I can tell what's happening even without looking at the Honda Nav code. Dates are being stored as a data type that can't handle the size of the date value for any date / time after 1/1/22, and it's rolling over to a smaller value that it can handle (that's the incredibly oversimplified version of it). And it's a problem that's affecting many computer systems of many types and many creators all around the world right now.

All the vendor has to do is update the source code to handle date and time with a larger data type, then push an update (or send update discs, whatever) to users for free. Problem solved. But, that could be expensive, so don't hold your breath.

 

[RAMITCHELL13]

This is a widespread issue with computer systems after 1/1/22; it's not just affecting Honda / other vehicle nav systems. Short answer to this problem is that it is VERY common in computer programming to store date information as what is called a long integer; it's a type of data structure. What "long integer" (or long int) means is that it's an object that's a number that can be all the way up to 2147483647; any number larger than that can't fit in the storage and gets messed up. Well, guess what the date value for 1/1/2022 is? It's larger than that number, meaning ANY COMPUTER SYSTEM that stores the date as a long int is now screwed. This affected EVERY SINGLE Microsoft Office program, for instance, because Microsoft programmed every Office program (Word, Excel, Powerpoint, Outlook, etc.) to store dates as a long int back during the Y2K "crisis": they just kind of forgot to check whether or not long int would be good enough for the future... and it's not.

So, I can tell what's happening even without looking at the Honda Nav code. Dates are being stored as a data type that can't handle the size of the date value for any date / time after 1/1/22, and it's rolling over to a smaller value that it can handle (that's the incredibly oversimplified version of it). And it's a problem that's affecting many computer systems of many types and many creators all around the world right now.

All the vendor has to do is update the source code to handle date and time with a larger data type, then push an update (or send update discs, whatever) to users for free. Problem solved. But, that could be expensive, so don't hold your breath.

I suspect you’re right on target. It did not make sense that the issue would resolve in August.
Most people wrote code where they stored the year as packed decimal usually just two bytes. Instead of 1999, it was just 99. When theyear rolled to 2000, you got 1900. Why, because the programmer would prefix the year with 19.
How do I know this, fifty plus years in Information Technology and yes I wrote my share of programs.

 

[dhrubajee]

Hi Guys
I am having the same issue since a couple of days when I had to jumpstart my car. Before everything was perfect and amazing, I forgot turn of the ceiling light for 3 days and battery was flat. I did jumpstart I had to use my sat nav code and everything seemed okay. Yesterday I saw the clock was showing the different time rather than the real time. I tried to set it up and I did set the time but again when I switched off the car and started again the time was again displaying the wrong.
I think Hondas should resolve the issue. If anyone from Honda know how to fix the problem please do let us know.
Thanks

 

[Scooter]

Hello all:
I am also having the same problem. Frustrating to see that it is always 4 o’clock when I start the car. I’ve tried the manual corrections, but they don’t update when you re-start the car. Happy new year, I guess.

 

[RAMITCHELL13]

I suspect you’re right on target. It did not make sense that the issue would resolve in August.
Most people wrote code where they stored the year as packed decimal usually just two bytes. Instead of 1999, it was just 99. When theyear rolled to 2000, you got 1900. Why, because the programmer would prefix the year with 19.
How do I know this, fifty plus years in Information Technology and yes I wrote my share of programs.

I did do some research and Microsoft Office 2019 does not have any issues nor does Windows Server 2016/2022 nor Windows 10/11!

 

[RAMITCHELL13]

Hello all:
I am also having the same problem. Frustrating to see that it is always 4 o’clock when I start the car. I’ve tried the manual corrections, but they don’t update when you re-start the car. Happy new year, I guess.

Ensure Honda Motors has your correct contact information - they are working on a fix and will let us know via the noraml USPS Mail etc...

 

[RAMITCHELL13]

Found an official statement regarding this issue:

The Situation:
Honda and Acura cars as old as 2004 and equipped with navigation are showing incorrect date and time settings. Date often shows January 1, 2002 (or another month and day in 2002) and time is stuck and cannot be adjusted.

The Cause:
Honda’s head unit receives a GPS signal for date and time including a number representing a week, coded in binary. These digits count from 0-1024 and rollover to 0 after the completion of week 1024. Honda’s head unit supplier did not code their head units to account for the rollover and, on January 1, 2022, reverted to a date and time 1024 weeks in the past.

The Solution:
Honda is aware of the issue and says it will self correct sometime in August.
This happened in the past, and Honda’s solution then was to mail out update discs. It took several months.
It’s not clear if Honda will produce update discs or allow for a self-correction.