Clock problems with New Year

Discussion in 'iPod touch' started by aethelbert, Dec 31, 2007.

  1. aethelbert macrumors 601

    Joined:
    Jun 1, 2007
    Location:
    Chicago, IL, USA
    #1
    Is anyone else having problems with their clocks (both local and international) showing incorrect dates after the crossover to 2008? My clocks for Munich and Singaport both show the correct time, but the date of 12 July 2031.

    edit: same problem on the iPhone as well, also seen on iPhone forum.
     
  2. WildPalms macrumors 6502a

    WildPalms

    Joined:
    Jan 4, 2006
    Location:
    Honolulu, HI
    #2
    Wait until you enter the new year, then take a look at the clocks. I'm assuming you're referring to widget clocks?
     
  3. aethelbert thread starter macrumors 601

    Joined:
    Jun 1, 2007
    Location:
    Chicago, IL, USA
    #3
    Yes, I am referring to the World Clock section of the clock widget. I don't see how going to 2008 would fix clocks that went all the way to 2031, but ok...
     
  4. shiggys macrumors newbie

    Joined:
    Dec 31, 2007
    #4
    World Clock

    I see the same thing on the iTouch - Taipei is showing 07/12/31. We'll see what happens to my local time after New Years (I assume the same). Didn't they figure this out @ Y2K???





     
  5. Texas04 macrumors 6502a

    Texas04

    Joined:
    Jul 2, 2005
    Location:
    Texas
    #5
    Everywhere where "New Years" has passed is showing the correct time of day, but places like LA where it is 11:22pm and Honolulu where it is 9:22pm, they are showing 08/01/01???? all the other clocks in the world clock are showing "today"
     
  6. iJawn108 macrumors 65816

    iJawn108

    Joined:
    Apr 15, 2006
  7. Daveway macrumors 68040

    Daveway

    Joined:
    Jul 10, 2004
    Location:
    New Orleans / Lafayette, La
    #7
    Places where its not 2008 show up as being 2001. However my clock rolled over just fine to 2008, ie my recent calls etc show up as 1/1/08.

    So unix problem, no. The only future unix clock problem isn't until 2038.
     

Share This Page