epg clock going nuts

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • latnl8rzdude
    Junior Member
    • Nov 2008
    • 24

    #1

    epg clock going nuts

    looked through posts and cant find this one, so its probably me doing something wrong

    I upgraded to 4.57e_E two days ago (which i got right 1st time ) and i've had a few green flickery screens followed by the box swithing off then on, in addition to this when I go into the epg the clock is flashing beween the corrent time and one hour out. I've messed about in the user settings until my face went blue and its still going my nut in. what am I doing wrong? should i upgade to the beta epg????
  • Shinzon
    Junior Member
    • Sep 2008
    • 28

    #2
    menu, user settings, time, turn summer time on

    Comment

    • latnl8rzdude
      Junior Member
      • Nov 2008
      • 24

      #3
      Originally posted by Shinzon
      menu, user settings, time, turn summer time on
      yep done that. clock on info screen reads correct. its only in epg, its flashing between the two times ie. correct time and 57mins ago..

      Comment

      • latnl8rzdude
        Junior Member
        • Nov 2008
        • 24

        #4
        is 4.57 less stable than previous releases? I'm getting several freezes a day since upgrading. I was wondering if others have experianced the same?

        Comment

        • Deni
          Newbie
          • Apr 2009
          • 1

          #5
          Star view updating time display

          to change the time on epg (star view 3) go to Time Setting and change Timezone to GMT + 01.00.

          Comment

          • latnl8rzdude
            Junior Member
            • Nov 2008
            • 24

            #6
            thanks all. did as u all said and clock kept flashing between two times so decided to live with it and left it alone... hey presto this morning its fine, who'd av thort eh? box still giving green freeze screen then power off and on again tho... not all the time so mabee its on its way out? still, its only been doing this since upgrading to 4.57...

            Comment

            Working...