Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

iPhone Wants To Hang On To the Old Year

timothy posted more than 6 years ago | from the 223*3*3 dept.

Bug 104

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."

cancel ×

104 comments

Sorry! There are no comments related to the filter you selected.

They have good reason too.... (-1, Troll)

Anonymous Coward | more than 6 years ago | (#21870962)

Re:They have good reason too.... (2, Funny)

Anonymous Coward | more than 6 years ago | (#21872176)

Parent is Myminicity spam. Publish IP, track down in meatspace, burn down house, buttrape mother. Wipe hands on pants, repeat.

Re:They have good reason too.... (1)

jacquesm (154384) | more than 6 years ago | (#21873708)

you forgot the hang, drown, quarter and keel-haul bits...

So silly bug (1)

LynXmaN (4317) | more than 6 years ago | (#21870966)

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.

Re:So silly bug (1)

karnal (22275) | more than 6 years ago | (#21871048)

Maybe it's converting to MM/YY/DD.

Re:So silly bug (1)

rednip (186217) | more than 6 years ago | (#21871154)

Maybe it's converting to MM/YY/DD.
Nope, just checked, my iPhone is showing "07/12/31" for those cities for whom the new year has arrived. No big deal, I don't use the world clock anyways, I even had to add a couple of cities to it just to check the bug. Personally, I'm much more concerned over the lack of stereo bluetooth.

Re:So silly bug (-1, Troll)

Anonymous Coward | more than 6 years ago | (#21871426)

I would be more concerned at being the kind of cheerless idiot that buys one of these things. Still, thats just me.

Re:So silly bug (1, Interesting)

Anonymous Coward | more than 6 years ago | (#21871064)

When the local year rolls over to 2008 it corrects itself.

So it is a limited bug.

Re:So silly bug (1)

ewanm89 (1052822) | more than 6 years ago | (#21873644)

That will repeat every new year. Not so limited... (darn, that wrecks using modpoints on this thread)

Re:So silly bug (1)

Actually, I do RTFA (1058596) | more than 6 years ago | (#21885820)

Slashdot responses...

Apple messes up dates in the world clock: Hope they fix it soon although it's purely aesthetic.

Microsoft messes up dates in the world clock: Haha, id10ts in Redmond - or - Oh no, the security implications are huge - or - If this was F/OSS someone would have noticed the bad date code and patched it.

Google messes up dates in the world clock: Huh, I thought India was 16 hours behind me, but they must be in some crazy timezone that isn't what I expected.

Communication bug with GSM network? (1)

Baricom (763970) | more than 6 years ago | (#21870978)

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.

Re:Communication bug with GSM network? (1)

Guido del Confuso (80037) | more than 6 years ago | (#21871234)

It's not really an invalid date problem, but an incorrect conversion problem. If it's like every other Unix system (and there's no reason to believe it's not) the date and time are stored internally as an integer and converted on the fly to whatever format is required for display. However, when comparing two dates, the unconverted date (possibly plus or minus any adjustments for time zones) is used.

Re:Communication bug with GSM network? (0)

Anonymous Coward | more than 6 years ago | (#21871364)

This also happens on the iPod touch. So it's not a GSM issue.

Re:Communication bug with GSM network? (1)

Reaperducer (871695) | more than 6 years ago | (#21871500)

Like the others, my phone's World Clock function is showing 07/12/31 in Hong Kong and London.

And I guess this is a feature, not a bug, but it shows that the date in my current time zone is "Today." Well, that's not all that helpful if I don't know what today's date is, is it?

Re:Communication bug with GSM network? (1)

wdr1 (31310) | more than 6 years ago | (#21872634)

The general time/date/etc. is correct. It seems to manifest in "world clocks" only (at least for me).

Re:Communication bug with GSM network? (-1, Troll)

ILuvRamen (1026668) | more than 6 years ago | (#21872708)

wasn't everyone "supposed" to have caught the Y2K glitch too? Everyone was like "oh gee, it'll never have to go past 2 digits or roll over to 00." So I guess Apple thought they were safe from the Y2.008K bug. What a bunch of morons. Maybe they should have spent less time on those annoying ads (especially that stupid music!!!) and actually made sure the programming was less retarded.

Re:Communication bug with GSM network? (4, Funny)

ribond (149811) | more than 6 years ago | (#21875034)

That's a pretty egregious bug. One would think that somebody should have caught it in testing.


They're expecting you to buy a new ipod/iphone/iWhatever each year. Why should the date change? That's the 2007 model!

Isn't it an AT&T issue? (0)

Anonymous Coward | more than 6 years ago | (#21870980)

Doesn't the phone get the date and time from the AT&T network?

Re:Isn't it an AT&T issue? (1)

hedwards (940851) | more than 6 years ago | (#21871278)

Probably, my razr does and I'm on the AT&T network, so it should. If I am not mistaken that applies to any GSM phone on the market, regardless of network.

But it is worth noting that AT&T hasn't hit 2008 yet, so if it's getting its date and time from that network, it shouldn't say anything other than 12/31/2007. Or some arrangement of that.

It could also be that Apple has the auto update feature turned off for some reason as well.

Confirmed! (5, Funny)

sg3000 (87992) | more than 6 years ago | (#21870984)

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. [wikipedia.org] system to this now A.i.P. calendar system is the real news.

Happy Year 1 A.i.P. everyone!

Re:Confirmed! (5, Funny)

secolactico (519805) | more than 6 years ago | (#21871074)

Happy Year 1 A.i.P. everyone!

Wait... shouldn't it be 2 A.i.P.? I mean, since the year formerly known as 2007 is now 1 A.i.P. not 0 A.i.P. right?

I can already hear the discussions 100 years from now as to when does the next century really start...

Re:Confirmed! (4, Funny)

Ambiguous Coward (205751) | more than 6 years ago | (#21871272)

I'm not so sure...I mean, A.i.P. stands for *After* iPhone, right? So 2007 was *during* the coming of the iPhone. It's sort of like counting from negative to positive. We say ..., -2, -1, 0, 1, 2, ..., rather than ..., -2, -1, 1, 2, ...

This way, 2007 is simply the central point from which you count outwards. Anything prior is negative (clearly, since there was no iPhone...how could anything be *positive* in such a state? It's a wonder we survived those dark ages) and anything after is positive (because we have the iPhone! The time of enlightenment has arrived!)

At least with the iPhone, we're much more likely to witness a second coming...and a third, fourth, fifth, and so on, ad nauseam. Go Apple! :P

-G

Re:Confirmed! (1)

Faylone (880739) | more than 6 years ago | (#21871572)

Well, some [pvponline.com] claim the iPhone IS the second coming of Christ.

Re:Confirmed! (2, Informative)

tverbeek (457094) | more than 6 years ago | (#21871598)

A.i.P. stands for *After* iPhone, right?
No. Just like "A.D." doesn't stand for "After Death" (as I was told in elementary school).

The "A." stands for "Anno", Latin for "Year". "A.iP." stands for "Year of Our iPhone".

Re:Confirmed! (1)

Ambiguous Coward (205751) | more than 6 years ago | (#21871828)

Ah. I was victim of the same educational offense. It never made sense to me, anyhow, since it would imply a missing gap of 20-30 years, since Before Christ would be before he was born, and After Death would be some time later. Anyhow, I still stand by my reasoning that yes, there *is* a year zero. Otherwise, the math just don't add up none. :P

-G

Re:Confirmed! (3, Funny)

Anomolous Cowturd (190524) | more than 6 years ago | (#21872836)

Programmers everywhere are dreading the unpredictable "second coming bug".

Re:Confirmed! (1)

mce (509) | more than 6 years ago | (#21873572)

Math-wise there is a year 0 only if your reference point lasts a year. But the birth of Christ didn't take a year, just a few hours (or a single second if you consider that we generally say that someone was born on YYYMMDD at hh:mm, irrespective of labour). Therefore, in Christian/western historical counting there is no - and has never been - a year 0. Year 1 AD starts at the moment of his birth (being the first year after his birth), Year -1 AD stops at that very same momment (being the last year before it). As long as you know this and take it into account, the math works all fine.

Note that I'm not saying he was ever really born, let alone on the date we historically claim. But that's irrelevant to how counting has been done since over 200 years.

Re:Confirmed! (3, Funny)

aussie_a (778472) | more than 6 years ago | (#21872276)

At least with the iPhone, we're much more likely to witness a second coming...and a third, fourth, fifth, and so on, ad nauseam.
I didn't know the iPhone's vibration function was so strong!

Re:Confirmed! (5, Funny)

The One and Only (691315) | more than 6 years ago | (#21872816)

There are two kinds of people in the world: (1) Those who start their arrays from 1 and (1) Those who start their arrays from 0.

Re:Confirmed! (1)

Kreigaffe (765218) | more than 6 years ago | (#21873278)

i'm trying very hard to throw points at you...

let me know when it starts working.

Re:Confirmed! (1)

The_reformant (777653) | more than 6 years ago | (#21875290)

There are two kinds of people in the world: (1) Those who start their arrays from 1 and (1) Those who start their arrays from 0.
You forgot ("table") Those who use associative arrays

Re:Confirmed! (0)

Anonymous Coward | more than 6 years ago | (#21877696)

Should have been "there are 10 kinds of people" :P

Re:Confirmed! (0)

Anonymous Coward | more than 6 years ago | (#21871548)

I guess the phone just obeys Apple HQ date

Re:Confirmed! (1)

mattwarden (699984) | more than 6 years ago | (#21872730)

Unfortunately the iPhone uses 1 digit to store the year in order to save space.

Time to brush off your Usenet calendars... (1)

argent (18001) | more than 6 years ago | (#21874182)

You know, the ones where September 1993 continued through February 9, 2005.

Not a bug (5, Funny)

CokeBear (16811) | more than 6 years ago | (#21870992)

Its designed only to last until the end of 2007.
Now that it is 2008, you need to buy a new one.

Re:Not a bug (0, Offtopic)

sykopomp (1133507) | more than 6 years ago | (#21871022)

I lol'd

Sorry, already used up all my mod points.

Re:Not a bug (0)

Anonymous Coward | more than 6 years ago | (#21871106)

I know you're joking, but seriously, don't give Apple or AT&T any ideas.

Re:Not a bug (0)

Anonymous Coward | more than 6 years ago | (#21871392)

But I signed up for the 2-year plan! Wait, is this that Megahertz Myth thing?

Re:Not a bug (1)

Kreigaffe (765218) | more than 6 years ago | (#21873280)

the 2 year plan just means you pre-emptively agree to buy iPhone 2.0 next year (this year), and don't need any further agreement. the plan is still there, yes, but your old outdated iPhone is no longer trendy or stylish and must be replaced.

Re:Not a bug (1)

Carewolf (581105) | more than 6 years ago | (#21871840)

Sad, but true

Planned Obsolecense (0)

Anonymous Coward | more than 6 years ago | (#21871024)

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

Y2K! (0)

Anonymous Coward | more than 6 years ago | (#21871032)

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!

DateTime issues with ARM CPU on other platforms (1, Interesting)

cwolfsheep (685385) | more than 6 years ago | (#21871044)

The iPhone uses an ARM CPU [wikipedia.org] 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 [readlist.com]
http://bugs.freepascal.org/view.php?id=9080 [freepascal.org]

Re:DateTime issues with ARM CPU on other platforms (2, Insightful)

geekboy642 (799087) | more than 6 years ago | (#21871536)

Those two issues with software/runtime libraries being ported are completely irrelevant to a bug in a display module of a clock built in native code. Don't trust the first Google link you get if you don't understand the topic.

Re:DateTime issues with ARM CPU on other platforms (0)

Anonymous Coward | more than 6 years ago | (#21871624)

But it's such easy-karma material! And it dilutes the waters via the usual "It's not Apple's fault - and when it is, it's a feature; we just can't begin to understand it!"-reality distortion thing.

Yeah, I know - Flamebait. Ah well.

Re:DateTime issues with ARM CPU on other platforms (1)

cwolfsheep (685385) | more than 6 years ago | (#21871784)

Well, that's what I wanted to know if there was a Y2K-ish issue on-hand, or a simple mess-up.

NSLU2 (1)

headbulb (534102) | more than 6 years ago | (#21871862)

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.

Re:NSLU2 (1)

Briareos (21163) | more than 6 years ago | (#21873680)

Both date and hwclock report the right date for me on my NSLU2 running Debian, so something must be majorly wrong on your end.

Also, even if hwclock were to report a bad time why should it concern the date command which just reports the kernel's idea of the current date and time which is keeping its own time? Nevermind getting updated regularly via ntp?

Not that I'd think that the ARM CPUs in the NSLU2 and the iPhone would have the same RTC hardware, since that's not part of the CPU. Also, dates are calculated using the ALU just like everything else, so there's no chance in hell there'd be a bug in it that would only affect dates and not all calculations...

np: Jürgen Paape - Fruity Loops #2 (Speicher CD3)

Re:NSLU2 (1)

headbulb (534102) | more than 6 years ago | (#21884898)

Yep. I should have mentioned that I am the one that had the date wrong.

So it's a day off. My bad.

Y2K finally hits!! (5, Funny)

elrous0 (869638) | more than 6 years ago | (#21871072)

And they said I was crazy for stockpiling all that food!

Re:Y2K finally hits!! (4, Funny)

rednip (186217) | more than 6 years ago | (#21871192)

Y2K finally hits!!...And they said I was crazy for stockpiling all that food!
If you need to have any more 8 year old food, my fridge is an excellent source.

Re:Y2K finally hits!! (1)

superash (1045796) | more than 6 years ago | (#21872894)

(looking at your sig) No wonder your cat is the boss now :P

Re:Y2K finally hits!! (1)

Daltin (1153533) | more than 6 years ago | (#21871288)

It's funny, this time, for Y2K-and-one-one-twenty-fifths, nobody expected anything!

Re:Y2K finally hits!! (1)

Threni (635302) | more than 6 years ago | (#21871436)

If Apple's bugfixing hasn't learnt anything from the problems with the iPod Classic, the next release will be out in about 3 weeks and cause more problems than it fixes.

Re:Y2K finally hits!! (1, Funny)

Jugalator (259273) | more than 6 years ago | (#21871814)

And they said I was crazy for stockpiling all that food!
Score: 4 Insightful? It's funny, but come on... Hmm, a call for more meta moderation, I guess. I'll be on my way there.

That must mean: (1, Funny)

fluch (126140) | more than 6 years ago | (#21871076)

The iPhone is sooo 2007! Apparently. ;-)

Unfortunately.. (-1, Redundant)

Colourspace (563895) | more than 6 years ago | (#21871156)

You all bought the 2007 model, but Steve will be happy to furnish you with a new 2008 model with a fully charged battery as of tomorrow. For $600. Happy new year!

1.1.3 (2, Interesting)

gutnor (872759) | more than 6 years ago | (#21871178)

I guess that we now know for sure 1 of the features of the new firmware 1.1.3.
Compatibility with 2008 !

Re:1.1.3 (1)

attemptedgoalie (634133) | more than 6 years ago | (#21871212)

1.1.3 is already in testing. Nobody uses the date on their phone anyway, so they'll just wait for 1.1.3.1. :-)

Re:1.1.3 (0)

djh101010 (656795) | more than 6 years ago | (#21871276)

If 1.1.3 adds just a fix for this, I'd skip it. I have a site, ipodtouchmods.com, which I'll post any deltas of the forthcoming 1.1.3 update to. I suspect it's just trivial BS and maybe a block to those of us who unjail our iPods/iPhones so we can add third party apps. No good reason to install 1.1.3 unless it adds some killer app (FLASH PLEASE). Even so, even with Flash, I'd probably wait for the unjail process to be solidified, or for the flash stuff to be backported to 1.1.1 or 1.1.2 by the mods community.

Re:1.1.3 (1)

attemptedgoalie (634133) | more than 6 years ago | (#21871408)

The stuff I've read says that 1.1.3 is going to be fairly substantial.

Supposedly you're going to be able to move icons on the iPhone's "desktop", set icons for favorite websites, etc.

But no, no Flash. Which makes no sense. For the people worried about battery life / CPU power, they could make Flash an opt-in setting.

Re:1.1.3 (1)

djh101010 (656795) | more than 6 years ago | (#21871462)

The stuff I've read says that 1.1.3 is going to be fairly substantial.

Supposedly you're going to be able to move icons on the iPhone's "desktop", set icons for favorite websites, etc.
Ah, as I can more or less do today with "smbprefs" and "customize".

But no, no Flash. Which makes no sense. For the people worried about battery life / CPU power, they could make Flash an opt-in setting.
No flash, no upgrade, far as I'm concerned. Custom icons were solved months ago by the hacker community. Same with moving icons around on the screen. If that's all they've got for 1.1.3, I'll wait for Flash. Got a source for that info, by the way? I'd love to read it.

Re:1.1.3 (1)

jaredmauch (633928) | more than 6 years ago | (#21871468)

I for one hope flash never comes to the iPhone. I'm tired of reading everyone beg to have crappy battery life. I appreciate you saying it should be opt out but I suspect most other folks asking for it are not understanding the true impact of their wish on hardware rev 1.

Re:1.1.3 (1)

heinousjay (683506) | more than 6 years ago | (#21871982)

Does it somehow drain the battery when you aren't using it? I'll answer that for you - no, it doesn't. Quit bitching about useless stuff.

Re:1.1.3 (0)

Anonymous Coward | more than 6 years ago | (#21878036)

I just don't see how flash will kill the battery faster than any other task using the CPU, ie. all of them. I'm sure they could have a checkbox to disable it for psychic paranoids such as yourself, but even if it does drain the battery (like every other program does) the benefit clearly outweighs that cost. Then again, it's not like you can just swap the battery when its flat (like every other phone ever made), so I guess your point has a little merit.

Re:1.1.3 (1)

djh101010 (656795) | more than 6 years ago | (#21879210)

Then again, it's not like you can just swap the battery when its flat (like every other phone ever made), so I guess your point has a little merit.

Odd, I was never able to find out how to swap out the battery on my Treo 600, which the iPhone replaced for me. I'm thinking that's because it couldn't be, what with there being no batter hatch. That said, there was probably a similar option as we have with the iPhone where I can send it to Apple for 50 or 60 bucks and get it swapped out, or third parties for significantly less. But, I understand, AC's like spreading FUD, or perhaps FUD-spreaders prefer to post as ACs. Either way, you're wrong.

Occam's Razor, people! (4, Funny)

UbuntuDupe (970646) | more than 6 years ago | (#21871194)

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.

That'd be impressive (1)

Virm (938584) | more than 6 years ago | (#21871296)

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.

Network time (1)

peektwice (726616) | more than 6 years ago | (#21871220)

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.

Re:Network time - it's also on the iPod touch (1)

mareksquonk (541185) | more than 6 years ago | (#21871772)

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. :)

The "difficult" clock algorithm... (1)

gweihir (88907) | more than 6 years ago | (#21871584)

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.

Re:The "difficult" clock algorithm... (0)

Anonymous Coward | more than 6 years ago | (#21872162)

As I read your post, a pretty white light formed around it, and I felt myself at one with all living things. You are love.

Hey, my phone says 12/31 too! (3, Funny)

rob1980 (941751) | more than 6 years ago | (#21871678)

Oh wait, it's only 830. nm.

iPod Touch screwed up also... (3, Informative)

Aphrika (756248) | more than 6 years ago | (#21871770)

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.

Re:iPod Touch screwed up also... (1)

NateTech (50881) | more than 6 years ago | (#21873630)

Ha. Hey guys, another newbie here thinks companies have time/budget/staff for this thing he calls "testing" again!

Didn't he get the memo? Only enough of this "testing" to be able to say it was done is ever accomplished anymore. Anything beyond that is a waste of resources that could be used getting the next crap-tacular product out the door.

Man I love Slashdot. Always good for a laugh.

Seen this before (1)

hawk (1151) | more than 6 years ago | (#21875622)

I had a Tandy 102 for taking notes in law school. It actually decremented the year in 1988 . . .

hawk

That's Ok... (0, Flamebait)

dreamchaser (49529) | more than 6 years ago | (#21871942)

Lord Steve will just declare Dates to be irrelevant and the herds of his fanbo...I mean devotees will march in lockstep.

Re:That's Ok... (0)

Anonymous Coward | more than 6 years ago | (#21884462)

Once again the moderation proves a point. Idiot zealots lol.

Apple needs a new calendar coder guy (1)

SystemFault (876435) | more than 6 years ago | (#21872000)

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.

Re:Apple needs a new calendar coder guy (1)

fluch (126140) | more than 6 years ago | (#21872046)

1752 is what you mean. 1752. ;-)

Re:Apple needs a new calendar coder guy (1)

Bill, Shooter of Bul (629286) | more than 6 years ago | (#21872266)

Yeah, but its even more confusing than that. 1582 is the date that one of the Popes( Greogory, hence Gregorian Calendar) decreed the calendars change. The protestant heathens refused as they didn't read about the time change in the bible, or int the wittings of martin Luther. So they kept the old Julian system until 1752. So there are dates that did exist in some countries that didn't in others, and there was a disagreement about the date between countries.

As per usual read the wiki Here [wikipedia.org]

After writing that I know see the ;) at the end of your comment. In which case, I have notified the athories and you soon expect the unexpectable inquisition hailing from the Iberian peninsula region.

Re:Apple needs a new calendar coder guy (0)

Anonymous Coward | more than 6 years ago | (#21872546)

My iPod touch has no problems, it shows the date/time correctly in every application. However, under clock since it says "local time" Today, that's not very much use. Calendar app is correct though, as is the splash screen upon re-awakning.

Bug report entered (3, Informative)

edp (171151) | more than 6 years ago | (#21872314)

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.

Same here (1)

Samurai Cat! (15315) | more than 6 years ago | (#21872324)

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).

Re:Same here (1)

curmudgeous (710771) | more than 6 years ago | (#21873640)

"...I just threw up a couple of World Clocks..."

Dude, I do NOT want to know what you were drinking last night.

It seems to work fine for me.. (1)

listen_to_blogs (1210278) | more than 6 years ago | (#21872504)

Its fine on my Iphone!! listen_to_slashdot [blogbard.com]

Not mine (1)

tgibbs (83782) | more than 6 years ago | (#21872576)

Switched from Dec 07 to Jan 08 exactly on time.

Re:Not mine (1)

pandrijeczko (588093) | more than 6 years ago | (#21872970)

Hmmm.... most other people would be breaking open champagne and kissing a loved one at midnight on New Years Eve.

But iPhone users are staring into their phones... I guess that says it all.

Re:Not mine (1)

tgibbs (83782) | more than 6 years ago | (#21875158)

Hmmm.... most other people would be breaking open champagne and kissing a loved one at midnight on New Years Eve.
But iPhone users are staring into their phones... I guess that says it all.


Actually, in the minutes before New Years Eve, most people are looking at their watch, waiting for the precise moment to crack open the champagne.

Like many iPhone owners, I no longer bother to carry a watch.

Not ours either, (1)

ErikTheRed (162431) | more than 6 years ago | (#21873004)

I checked mine (and my wife's) at about 1AM on Jan 1... they both rolled over just fine. Sounds like our SEP field [wikipedia.org] is working just fine.

What the...nobody spouting about their WM devices? (1)

Jaktar (975138) | more than 6 years ago | (#21872726)

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!

Read your contract (3, Funny)

DrXym (126579) | more than 6 years ago | (#21873380)

Your 2 year contract only expires when the iPhone says it does.

Re:Read your contract (1)

socz (1057222) | more than 6 years ago | (#21877898)

Your 2 year contract only expires when the iPhone says it does.


oh man, wouldn't that be something eh?? and then since apple is so trendy all the other phone carries will follow their lead and do the same. I may never get out of this contract now! arrrrrrrrg

Who's mistaking? (0)

raflmoe (758933) | more than 6 years ago | (#21873422)

Maybe the iPhone is right, and India's still in 2007?

Same problem in Leopard (1)

emm-tee (23371) | more than 6 years ago | (#21876958)

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.

Re:Same problem in Leopard (1)

osssmkatz (734824) | more than 6 years ago | (#21878836)

That's almost normal.. although early reports said it was "fixed" in Leopard. But on Tiger, the icon wouldn't update. (the actual image file). Pretty minor bug, unrelated to this problem, and if I do say so, I would rather not have my resources consumed with updating an image file.

Accidental error... or intentional? (1)

Bones3D_mac (324952) | more than 6 years ago | (#21880180)

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...

Oddly enough (1)

Swift2001 (874553) | more than 6 years ago | (#21883714)

I have no iPhone, but my 5G iPod with Video is keeping perfect track of time and date. Does that mean it's Linux?
Load More Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>