Since January, the clock in my CRV keeps starting up showing it’s 2:58, Jan 2.
Honda says it should self-correct this August.
I’m on tenterhooks.
What I found says that the time will correct on August 17, but the date will remain incorrect.
BTW, the service bulletin says the clock won’t properly adjust when the time changes for daylight saving time so we’ll have to do that manually.
I wouldn’t trust a car where the electrical engineers can’t get a clock to work right.
I dunno nuttin’ 'bout Honda clocks.
But–if you happened to own a 2003 Hyundai—well…I can’t skip over this wonderful opportunity! Here’s a link to a long thread about a Doper with a sorta similar problem…
A fun read.
I miss my old Santa Fe.
By the way, I don’t know if I ever mentioned the fate of that vehicle… I replaced it with a Hyundai Sonata in 2017, so I was letting my stepdaughter drive the Santa Fe. She in turn was letting her boyfriend drive it, even though I repeatedly told her I didn’t want him driving it. He was at a bar drinking and playing pool at 10 in the morning after dropping her off at work, and got in an accident when he left the bar (to go to another bar) and passed out while pulling out of the parking lot. The Santa Fe was totalled. Oh well I got a good 15 years or more out of it.
According to my Honda, it is still 2:58 on Jan 1. 
Software engineers. And clocks are ridiculously hard to get right. Just a complete rat’s nest of exceptions and special cases. Ideally, people should be using well-vetted time libraries, but that’s not always possible when you’ve been given a 10-cent microcontroller to work with.
Have you considered the possibility that the car is right, and it’s the world that’s wrong?
There’s no snow on the ground. That means it must be July or maybe August.
Depends on where you live. Our Southern Hemisphere counterparts would be saying “There’s no snow on the ground. That means it must be January or maybe February”. 
@Gorsnak knows where I live. 
I was thinking just put a GPS receiver in the car and it should be ridiculously easy. Then I read that the GPS is the problem.
Climate change advancing faster than we thought!
OK, so the week counter rolled over after 1024 weeks, and thinks it’s 2002, but why will it fix itself after another 32(ish) weeks? 32 is 100000 in binary, but 1024 is 10000000000, so the number going from 10000000000 (or I guess the string of 1’s that’s a value one less than that) back down to 0 at the initial rollover, then back up to 100000 doesn’t strike me as particularly special? Like why not 1000, or 1000000?
GPS isn’t the problem. Programmers who didn’t learn a goddamn thing from Y2K are the problem.
What’s Y2K, grandpa? 
The nothingburger before 9/11. Go back to watching TikTok.
So the answer to the question in the topic title is yes, sort of. I got in my 2010 Honda Fit this morning and the clock showed the correct time, though not adjusted for Daylight Saving Time. I can live with that and now I can get rid of the cheap clock I stuck to the dashboard as a replacement.
Mine too! It was Jan 1, 7:54 when I started the car.
Since we don’t do the DST thing, it was the right time.
As you note, the clock has the wrong date; it thinks it’s January 1, 2003. I can live with that and not having the time adjust for DST.