TiVo 3 Clock - wrong time

My Series3 clock is about 3 seconds off the auto-set time on my computer.

 

Mine was off some odd amount once. I think it corrected after I manually connected to Tivo.

 

I have two Series3s and they are almost never set to the same time. It's really annoying to see them on top of each other with different times on the display.

 

Ditto. Never understood why.

 

I saw the time wrong yesterday.. at somewhere around midnight, the S3 said it was 4:30-ish PM on SATURDAY. (found via view by channel -> and what day it was showing)

It had successfully recorded a show a few hours earlier, so I suspect Tivo's servers were off for a short period of time..?

 

Right now, my Tivo thinks it is Friday 9/21 @ 12:13pm -- too bad it is really Sat 9/22 4:13pm. It had just auto connected to the servers. I'll try a manual connect as soon as it finishes processing.

 

I've recently started to experience the same problem. I've tried the manual reconnection a few times, and changed the number that Tivo dials out to, but the problem comes back quickly (within an hour or so) and seems to get constantly worse as time goes on. I found this thread, but I don't see a resolution. Is anyone else still experiencing this problem?

 

I have 4 of the series 3 machines, and I occasionally see the external display time off by about 2.5 hours. Initiating another call fixes it.

As far as I can tell (I'm not certain) it still records at the proper time. It just seems to be the external display time that's off.

Except for the rare 2.5 hour off time display, all 4 external display times always match each other, and change together within a one or two second window.

 

Unfortunately, it's not recording correctly - it's basing the recording time on the displayed time.

 

Are you using dial-up or broadband? I've got broadband, and never ever seen a time/day issue.

 

Dial-up.

After reconnecting this morning around 10:30 AM, it's now up to 6 minutes fast.

 

Likewise.

 

I have broadband, and my S3 once thought the time was several hours later than it really was. The problem corrected itself within 24 hours.