Slashdot Mirror
iPhone Wants To Hang On To the Old Year
pdclarry writes "Users of the iPhone have noticed that it is showing December 31, 2007, even where it is already the new year. There have been a number of reports confirming the problem: Bug in Clock, Problem with New Year: My Clock — shows wrong year, Worldclock went wrong for "tomorrow" items."
Here it's already 2008 and where new year's have not arrived the iPhone's clock application is showing 01/08/01, doesn't make sense at all.
Hope they fix it soon although it's purely aesthetic.
May the source be with you!
That's a pretty egregious bug. One would think that somebody should have caught it in testing.
On the other hand, the clock is set by the phone network, correct? (I don't own an iPhone but my non-iPhone does this, so I feel like this is a safe assumption.) If that's the case, maybe the code to read the year part of the network time has a bug.
I wonder if this means that the 1.1.3 firmware is going to come out sooner, or be delayed. A invalid date could potentially break a lot of functionality.
Doesn't the phone get the date and time from the AT&T network?
I just checked my iPhone, and the world clock says New Delhi is 2007/12/31, rather than 2008/01/01. The regular calendar that handles appointments is unaffected since all my appointments are showing up in 2008 correctly.
I assume that this surprise (not bug) in the world clock is because the iPhone is so cool that we will no longer be advancing years beyond the year 2007. 2007 will be henceforth referred to the "year of our iPhone". Changing from our current B.C./A.D. system to this now A.i.P. calendar system is the real news.
Happy Year 1 A.i.P. everyone!
Insert simplistic political, ideological, or personal proselytization here.
Its designed only to last until the end of 2007.
Now that it is 2008, you need to buy a new one.
Reality has a liberal bias
So this is how they're planning to make people upgrade to a better...
Err wait, Bad Steve Jobs! You're supposed to force a _hardware_ upgrade, not a _firmware_ upgrade!
--sf
Oh god - Y2K was real all along - we just got the wrong year! How could we have been so blind?!
Head for the hills - save yourselves!
The iPhone uses an ARM CPU for its processor. I did a Google search on any DateTime-related problems, and found two of interest, one of which was solved by disabling code optimizations. Someone with more experience should look into this idea.
http://readlist.com/lists/lists.ximian.com/mono-list/1/5148.html
http://bugs.freepascal.org/view.php?id=9080
Life is irony, and nothing ever goes as planned.
And they said I was crazy for stockpiling all that food!
SJW: Someone who has run out of real oppression, and has to fake it.
The iPhone is sooo 2007! Apparently. ;-)
I guess that we now know for sure 1 of the features of the new firmware 1.1.3.
Compatibility with 2008 !
I'm a little disappointed. No one seems to be considering the possibility that the OTHER clocks are wrong, and the iPhone (er, I mean, and iPhone) is right?
I mean, come on, which is more likely, that some central time authority everyone is syncing to had a glitch, or that an Apple product was in some way imperfect?
Think about it.
Apology to Ubuntu forum.
Since I don't own an iPhone, and I didn't RTFA (much), I gotta ask...
Is it getting its time from AT&T's network? If so, is this really Apple's fault?
I've had similar problems on more than one occasion with a regular cell phone showing daylight savings time wrong, or radio stations broadcasting RDS with the time wrong, and the downstream device dutifully sets itself to whatever it gets over the air.
Other than this text, there is no discernible information contained in this sig.
It would certainly open whole new avenues of scientific research if it turned out that something like a cesium clock can suddenly have such a disparity from it's regular exponentially fractional precision. I would really like to read some of the doctoral papers that would suddenly arrise in an attempt to understand and explain the occurance.
Like this problem has never been solved before...
What kind of incompetents write this software? It is not even that you have to solve this for yourself. Just take a day to research solutions. And then test it. Hint: The tests should include new year, end of February in a leap year. Run this for the next 100 years or so (simulated, of course) and avoid embarassment.
Seriouly, those responsible shoud be fired with a perfomance review that prevents them from ever writing software for others again.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Oh wait, it's only 830. nm.
Well, it seemed to be ok, until I go into the clock application and all the dates read 08/01/01.
System settings say 1 January 2008, so I assume it's a display error. At least it rolled over into 2008 though which is what I thought the main article said was the problem. Odd really, as you'd expect such as basic issue to be caught in testing.
It's also on the iPod touch, which isn't getting its time from the network (I'd be very surprised if it could). Reykjavik and zones to the east all show 31 Dec 2007 instead of the customary "Tomorrow" for those presently past-midnight WorldClock choices. All the way, that is, until Pago-Pago, Samoa, across the date line, where it is showing Today. Wellington, New Zealand is the same time modulo 24 hours, only Tomorrow, er, 31 Dec 2007 iTouch(iPod) Central Standard Time. :)
I have a little nslu2 I have debian installed on. It runs a ARM processor.
I just check it's time Both date and hwclock are reporting wrong. I have it's clock set to utc.
Interesting bug, I will set the clock tomorrow to see if it happens again.
Lord Steve will just declare Dates to be irrelevant and the herds of his fanbo...I mean devotees will march in lockstep.
As mentioned above, the problem also occurs on the iPod Touch under the Clock icon function.
Oh, and for those with Mac OS/X, the fifth generation of the iCal application still totally misses the Gregorian conversion that occurred in September 1572.
For those with Unix, type "cal 1572" into a shell and then "man cal" for an explanation.
Parent is Myminicity spam. Publish IP, track down in meatspace, burn down house, buttrape mother. Wipe hands on pants, repeat.
I work at Apple, and I entered a bug report. I suspect the problem is merely a display error in World Clock, but, since it is affecting many people, I asked my manager to ensure the right people are notified quickly.
The problem does not seem to affect date displays outside of World Clock. For example, if you go into General settings, then Date & Time, turn off "Set Automatically," set the date to January 1, 2008, and then look at some recent calls in the phone, you will see they have correct dates. At least for me. If somebody observes otherwise, please let me know, and I will add it to the bug report.
I'm in Atlanta (EST). I just threw up a couple of World Clocks (hadn't bothered with that prior to this), one for Denver, one for Honolulu. Both display the dates as "08/01/01" (nevermind it's still 12/31/07 in both time zones).
"People" using "unnecessary" quotes should be "shot".
Its fine on my Iphone!! listen_to_slashdot
Switched from Dec 07 to Jan 08 exactly on time.
Hmmm. All my Windows Mobile devices have seemed to figure out that it's 2008..... It could be because I have an autographed picture of Bill Gates watching over my computer (no seriously). muahahaha -1 troll me! Happy new year from your pal Bill Gates!
I checked mine (and my wife's) at about 1AM on Jan 1... they both rolled over just fine. Sounds like our SEP field is working just fine.
Help save the critically endangered Blue Iguana
Your 2 year contract only expires when the iPhone says it does.
Maybe the iPhone is right, and India's still in 2007?
you forgot the hang, drown, quarter and keel-haul bits...
MP3 Search Engine
You know, the ones where September 1993 continued through February 9, 2005.
I had a Tandy 102 for taking notes in law school. It actually decremented the year in 1988 . . .
hawk
I'm running Leopard, and the dock icon for iCal is still displaying Dec 31 for me, even though it is almost Jan 2 here.
While iCal is running it displays the right date, but reverts to Dec 31 as soon as iCal is quit.
Feel free to call me crazy on this one, but has it been considered such an obvious error was intentionally left in place to "encourage" iPhone users to update their firmware once the next release is issued? No matter how cool it may seem to show off your 3rd party apps running on your jailbroken iPhone, it's unlikely anyone who bothered to jailbrake their iPhone will want to show it off with a screwed up date/time setting they can't correct by themselves.
Of course, if Apple does finally release a "true" iPhone SDK that has no nasty surprises packaged in with it, such a tactic would simply be silly and pointless. On the other hand, if the SDK comes at the price of paid commissions to Apple, eliminating the competition early on might not be such a bad idea...
8==8 Bones 8==8
I have no iPhone, but my 5G iPod with Video is keeping perfect track of time and date. Does that mean it's Linux?
I live in Norway and use Telenor as my carrier on my iPhone with 1.1.1 firmware... It shows all the dates correct. Shame on AT&T?