Drive Accord Honda Forums banner
61 - 80 of 118 Posts

·
Registered
Joined
·
1 Posts
Just noticed today my clock jumped ahead and hour and when I go to clock adjustment to change it, it doesnt change after i adjust the time. Tried turning the auto timezone and auto dst off and on made no difference. I drive a 2011 exl coupe with navi. Anyone else have the same thing happen?
Yes, experiencing same thing, can't seem to change it.

.
 

·
Registered
Joined
·
5,266 Posts

·
Registered
Joined
·
1 Posts
Just noticed today my clock jumped ahead and hour and when I go to clock adjustment to change it, it doesnt change after i adjust the time. Tried turning the auto timezone and auto dst off and on made no difference. I drive a 2011 exl coupe with navi. Anyone else have the same thing happen?
2009 Honda Accord started the new year one hour ahead Dealer disconnected battery to no avail even made it worse Now wrong hour and minute. today has Code error 1 then becomes error 2 on the time screen navigation still works
Radio stopped working
Wrong time on display is annoying
Have appointment with dealer next week

Vehicle Automotive design Bumper Motor vehicle Audio equipment


Bad start to 2022: radio stopped working, displays wrong time, displays “error 2”
Anyone experiencing similar problems ?
 

·
Registered
Joined
·
1 Posts
Just noticed today my clock jumped ahead and hour and when I go to clock adjustment to change it, it doesnt change after i adjust the time. Tried turning the auto timezone and auto dst off and on made no difference. I drive a 2011 exl coupe with navi. Anyone else have the same thing happen?
I have the same issue. I wondered if I just didn't look at the clock since the time change.
 

·
Registered
Joined
·
626 Posts
Can anyone verify whether this is just an issue with Honda vehicles? Could this be a clock/date problem with the GPS satellites? If so, then all Nav systems from all car manufacturers are affected.

I asked because a buddy of mine has a Lexus ES-350 and he has the same GPS clock problem that started this year (2022). He also has a 2009 Ridgeline, and of course, has the same clock/date issues we are having.

BTW, I first noticed the problem on my 2011 Ridgeline GPS clock. Checked my 2010 and 2018 Accords, and yep ... the GPS clocks are stubbornly stuck at Jan 1, 2002.

CORRECTON: My 2018 Accord is now showing the correct date and time. I have the Touring trim, but don't know if that makes a difference.

I've since checked my 2011 Ridgeline and 2010 Accord and those still have the wrong date and time.
 

·
Registered
Joined
·
3 Posts
The GPS satellites are correct (otherwise, we would all be having serious issues, such as aircraft, etc). The actual GPS date in my Accord is now showing May 27, 2002, which makes sense since it was reading May 19, 2002 on the 2nd. GPS time is correct, but the clock is an hour ahead, since the system thinks it is May, so should be on Daylight Saving Time (it is still keeping perfect time, just on DST). The Calendar in the unit does think it is Jan 1, 2002 (not that I ever use it). It wouldn't surprise me if other makes are having similar issues.

To get to the hidden detailed GPS info (at least on my 2011 Accord), press and hold, in order, Menu - Map - Cancel (such that all three are being pressed at same time). Hold for about 5 seconds, and a diagnostic screen will appear. Select the "individual tests", and then select "GPS Information"

Rick Brodzinsky
 

·
Registered
Joined
·
1 Posts
Just noticed today my clock jumped ahead and hour and when I go to clock adjustment to change it, it doesnt change after i adjust the time. Tried turning the auto timezone and auto dst off and on made no difference. I drive a 2011 exl coupe with navi. Anyone else have the same thing happen?
Same here. I contacted American Honda and they wanted to charge me $1 to tell me the issue.
 

·
Registered
Joined
·
2 Posts
It sounds like there might be two issues. Some reports indicate the clock reset to May 2002; others January 2002.

If it reset to May 2002, this almost certainly indicates a GPS Epoch issue. While the date doesn't align with the GPS Epoch, the observed offset from the current date is -1024 weeks, the length of a GPS Epoch. This suggests that Honda programmed it with a 143 week offset so that:

GPS week 143 = May 19, 2002
GPS week 1023 = March 31, 2019
GPS week 0 = April 7, 2019
GPS week 142 = December 26, 2021

So this particular issue could affect any Honda nav system between 2003 model year and 2012 model year after which the system was rewritten.

Honda says it will autocorrect in August. I don't buy that. The time will appear to be correct when we enter Daylight Saving Time (2nd week of March in the US) but will then recur with the clock displaying an hour behind in August when the system thinks it will have moved to standard time.

For the systems that reverted to January 2002, that's likely a separate bug. I don't have an answer for that, except that maybe it's a Y2K22 bug similar to Microsoft Exchange, and because the integer can't begin with ‘22...’ it's somehow dropping the leading 2 and rendering it as ‘02...’ but I haven't done the math to see if that makes any sense.
 

·
Registered
Joined
·
626 Posts
I read on this CR-V post that the date on some NAV systems is stored in a 32 bit word in this format:

YYMMDDHHMM

The value is stored as a signed integer, and thus the 32nd bit is not used. The largest integer is therefore 2^31 which equals 2,147,483,648. If it was an unsigned integer the largest number would be 4,294,967,296.

This means that Dec 31, 2021 would be stored as 211231HHMM and therefore within the signed integer range. However, Jan 1, 2022 would be 220101HHMM and exceeds 2^31, and thus is misread as 020101HHMM (Jan 1, 2002). The use of an unsigned integer was corrected at some point on later NAV systems as @JJohnson mentions above.

I don't know if what I read was true. But, this makes sense to me since my 2010 Accord and 2011 Ridgeline computes the GPS date/time incorrectly (Jan 1, 2002), yet my 2018 Accord is calculating the proper date/time.

BTW, even using an unsigned 32 bit word the problem would appear again in the year 2043.
 
  • Like
Reactions: Saaavy

·
Registered
Joined
·
1 Posts
Just noticed the same problem with the clock in my 2011 accord jumping ahead an hour. How can we get the word out for Honda to fix it? I tried like many to rest the time and no go. So annoying!!! Also how does one tell what generation?
 

·
Registered
Joined
·
61 Posts
It sounds like there might be two issues. Some reports indicate the clock reset to May 2002; others January 2002.

If it reset to May 2002, this almost certainly indicates a GPS Epoch issue. While the date doesn't align with the GPS Epoch, the observed offset from the current date is -1024 weeks, the length of a GPS Epoch. This suggests that Honda programmed it with a 143 week offset so that:

GPS week 143 = May 19, 2002
GPS week 1023 = March 31, 2019
GPS week 0 = April 7, 2019
GPS week 142 = December 26, 2021

So this particular issue could affect any Honda nav system between 2003 model year and 2012 model year after which the system was rewritten.

Honda says it will autocorrect in August. I don't buy that. The time will appear to be correct when we enter Daylight Saving Time (2nd week of March in the US) but will then recur with the clock displaying an hour behind in August when the system thinks it will have moved to standard time.

For the systems that reverted to January 2002, that's likely a separate bug. I don't have an answer for that, except that maybe it's a Y2K22 bug similar to Microsoft Exchange, and because the integer can't begin with ‘22...’ it's somehow dropping the leading 2 and rendering it as ‘02...’ but I haven't done the math to see if that makes any sense.
The exact nature of the issue depends on the vehicle. On the accord the only place the current date is found normally is in the calendar app, at least I have yet to find the date listed on any other screen. My car, the calendar app claims the current date is Jan 1 2002(it is stuck there). The time in the navi unit is stuck at 12:00 and does not move. The time displayed on the small screen below the nav screen is the correct time. Others say the time displayed on the small screen is incorrect. Apparently in some other Honda's the time is simply stuck at 12 or 1 but I believe these vehicles only have one screen displaying time. This would indicate that, in the Accord, there are 2 separate units tracking time. There would have to be for the nav screen and the radio screen to display two different times.

I think the issue is basically what you described. The firmware in GPS devices typically don't use the GPS epoch date, they hard code the start typically based on the firmware date, so the roll over within the device could happen anywhere in the 1024 week cycle. Basically what you described is what happened.
Beyond that, what I think is going on is there are other modules and a lot of software involved in the navigation unit and something is not happy that the date is now May 2002. Perhaps it is before the firmware date of some other module or creating some kind of date check issue in the software.

As for the August "autocorrect", it is possible the rollover date isn't in 2002 and through some bug or programming oversight there are some weeks in the 1024 week cycle that are hard coded to 2002 and once we are out of that range everything will work normally again.
What I think is more likely, I believe it is the week of August 14th(may have the date wrong but it will be in August regardless) will correspond to Jan 2003 in the nav system. This will correct whatever it is that is failing due to the date and allow the clock to be manually set, but the date will most likely still be incorrect.


I read on this CR-V post that the date on some NAV systems is stored in a 32 bit word in this format:

YYMMDDHHMM

The value is stored as a signed integer, and thus the 32nd bit is not used. The largest integer is therefore 2^31 which equals 2,147,483,648. If it was an unsigned integer the largest number would be 4,294,967,296.

This means that Dec 31, 2021 would be stored as 211231HHMM and therefore within the signed integer range. However, Jan 1, 2022 would be 220101HHMM and exceeds 2^31, and thus is misread as 020101HHMM (Jan 1, 2002). The use of an unsigned integer was corrected at some point on later NAV systems as @JJohnson mentions above.

I don't know if what I read was true. But, this makes sense to me since my 2010 Accord and 2011 Ridgeline computes the GPS date/time incorrectly (Jan 1, 2002), yet my 2018 Accord is calculating the proper date/time.

BTW, even using an unsigned 32 bit word the problem would appear again in the year 2043.
No. This is a complete BS theory created by a few arm chair experts that read a couple articles about Microsoft's woes with their Exchange software and think they have a clue what they are talking about. Any system, designed with the purpose of tracking time does not store date and time in this way. Even MS's issue had very little to do with the actual date. The issue was the version string of the signature file used by the anti-malware engine. The signature file version string is stored as a 32bit signed integer and MS made the choice to version the files as YYMMDDXXXX (likely for simplicity). They pushed out an update, which updated the signature file to version 2201010001 and because the value was stored as a 32b signed integer, it crashed the AV engine. MS released a fix to change the signature version to 211233XXXX.

While there are a few methods to track time, by far the most common is epoch based, time unit passed since epoch date, this time is then used by software to calculate the date. GPS uses an epoch system to track time and any device that is getting time from the GPS will undoubtedly also use epoch time.
 

·
Registered
Joined
·
1 Posts
I appreciated finding this thread today. I was very confused why my 2012 Accord EX-L w/ Navi is doing this as it's usually dead-on accurate with time changes. I've read the same experience with other models as well. Can anyone confirm if getting an updated map DVD (I still have the original 2011 disc) actually fixes this bug? I don't want to spend money on something I wouldn't normally buy if it won't repair the issue.
I have the same issue on my 2012 EXL coupe
 

·
Registered
Joined
·
626 Posts
@2012 Accord HFP, Thanks for that explanation and rebuttal.

At this point, I (we) don't know what actually caused this date/time failure. I still like my explanation even though it's BS. That's because it made me feel good about a broken clock (LOL).

In any event, as long as my 2018 Accord date/time is correct,along with my phone, computer and watch, I'll just suffer with my 2010 and 2011 until a fix happens.

Cheers.
 

·
Registered
Joined
·
1 Posts
Seems like there is a bug in the navigation system, the clocks on my 2010 Accord and many other Honda models have advanced by one hour today (2022-JAN-02).

CRV: Clock Fault (Year 2022)

Pilot: 2011 EX-L w/NAV Clock Issue

Ridgeline: handsfreelink and navi problems

Just like the owners in those posts, I also tried manually set the time, but it jumps right back to 12:00 on the Navigation UI after I hit "DONE", and the smaller clock on the radio is nolonger in sync with the navigation system.

And also the GPS status on the navigation is not stable (keep going from no fix (No GPS symbol on map) -> 2d fix (a dimond shape next to the word GPS) -> 3d fix (a box next to the word GPS) -> no fix) even tho I am driving in a low density zone with good visibiliy to the sky.

I wish Honda would release a fix.

View attachment 536911
The clock on the Navigation UI is stuck at 1200. And the clock on the radio is one hour ahead.

View attachment 536910
And today's date became 2002 Jan 1 in the Calendar
How did you get to the calendar? I can’t figure out how to get to it on mine!
 

·
Registered
Joined
·
1 Posts
I appreciated finding this thread today. I was very confused why my 2012 Accord EX-L w/ Navi is doing this as it's usually dead-on accurate with time changes. I've read the same experience with other models as well. Can anyone confirm if getting an updated map DVD (I still have the original 2011 disc) actually fixes this bug? I don't want to spend money on something I wouldn't normally buy if it won't repair the issue.
I have a brand new dvd update disc and I am having the same clock issues. The dvd isn’t the issue
 

·
Registered
Joined
·
1 Posts
Good evening guys,
First time here and I am also experiencing the same issue with 2012 Honda Accord EX-L

I’ve also heard from a buddy that Honda is currently in process of making a fix for the Y2K bug it currently has. He’s saying August minimum.
 
61 - 80 of 118 Posts
Top