F3 losing time

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • turty
    Newbie
    • Aug 2013
    • 5

    #1

    F3 losing time

    hi all I am finding that my f3 box cant keep the right time on the clock it runs slower than it should do ie after 2 hrs its 5 mins behind real time which is a pain if I go away for a week and set timers is there a fix or do I have to just put up with it.....
  • DW190
    DK Veteran
    • May 2012
    • 1263

    #2
    Originally posted by turty
    hi all I am finding that my f3 box cant keep the right time on the clock it runs slower than it should do ie after 2 hrs its 5 mins behind real time which is a pain if I go away for a week and set timers is there a fix or do I have to just put up with it.....
    If you go into Local Time Settings and set to:

    United Kingdom
    By Region

    The time should then be picked up from the satellite.

    Comment

    • fatbob46
      Member
      • Jul 2013
      • 66

      #3
      Originally posted by turty
      hi all I am finding that my f3 box cant keep the right time on the clock it runs slower than it should do ie after 2 hrs its 5 mins behind real time which is a pain if I go away for a week and set timers is there a fix or do I have to just put up with it.....
      They all do that on standby, apparently it's a firmware problem.

      Comment

      • Hadron
        V.I.P. Member
        • Nov 2012
        • 2102

        #4
        Originally posted by turty
        hi all I am finding that my f3 box cant keep the right time on the clock it runs slower than it should do ie after 2 hrs its 5 mins behind real time which is a pain if I go away for a week and set timers is there a fix or do I have to just put up with it.....
        That is realy bad timekeeping.

        I find that mine loses about 3 minutes when switched to standby overnight (around 8 - 12 hours), but 5 minutes over 2 hours!!!

        Comment

        • turty
          Newbie
          • Aug 2013
          • 5

          #5
          Thanks guys sorry it was 5 mins over 12 hrs didn't check my post didn't should have been 12hrs not 2 . I see its a firmware prob and nothing I have done wrong

          Comment

          Working...