iPhone wrong time!

[Rik]

I wonder if it was 255 hours after the change?

[Simon]

Sorry, did I miss something?  Why would that be significant?

[Rik]

One byte... I'm just wondering if their time change programming could be out by 8 bits or 256 hours. That would possibly produce a change at 10 days and 12 hours after the correct time.

[pctech]

That'd be really taking the bit now wouldn't it 

[Rik]

Right between the teeth, Mitch.

[zappaDPJ]

I use one of these strange devices, I believe they are called alarm clocks. 

And so will my daughter, as from tomorrow

Indeed, and it's been right since then, till this afternoon. 

We think it might have lost the hour sometime yesterday, or the day before as it now.

[Simon]

In my case, it's three days and about ten hours fast, Zap, so I don't think it's the BST bug. 

[pctech]

Must be the time source then.

[Simon]

No, it's been documented on the Apple forums, from people in different time zones to me, so unless that's a coincidence, it looks like an iPhone bug. 

[Gary]

No, it's been documented on the Apple forums, from people in different time zones to me, so unless that's a coincidence, it looks like an iPhone bug. 

My alarm was an hour out here, the time is spot on though as thats updated by the carrier. If you turn auto update of time off the problem is mitigated until the release of 4.2 which is due very soon.

[zappaDPJ]

In my case, it's three days and about ten hours fast, Zap, so I don't think it's the BST bug. 

Perhaps it's down to the provider. AFAIK my phone has been correct in that respect, it certainly is now. I think in our case it's just the alarms are off.

[Technical Ben]

That's the curious thing, isn't it. The clocks changed 10 days ago.

I suppose it's programming. These things carry over at the worst of times. Perhaps the repeating alarms on a 7 or 10 day cycle. So it does not break until the cycle is restarted. (I'm thinking 3 days of one week plus 7 of the other. It only broke when a full week passed)

[pctech]

Although I'm on O2 I can't check but will ask one of my colleagues later who is also on O2 and has an iThing 4

[Simon]

I can't see how it can be the carrier, as other people, not on O2, have had the same issue, and wouldn't it affect all phones on O2?

[Gary]

Although I'm on O2 I can't check but will ask one of my colleagues later who is also on O2 and has an iThing 4

Its repeat alarms like weekly etc oddly ones for the weekends work ok all my daily ones that repeat every day work fine its just the one that wakes me up that was an hour out, so just dialled it back an hour till the fix come out, I have sim free iPhone on O2. The time is fine, no issue at all.

[pctech]

I really don't know Simon.

[Gary]

I can't see how it can be the carrier, as other people, not on O2, have had the same issue, and wouldn't it affect all phones on O2?

Not seen anyone I know with your issue Simon, its just the alarm that's affected them.  

[Simon]

More here:

http://discussions.apple.com/thread.jspa?threadID=2642957&start=0&tstart=0

[Rik]

Well, that seems firmly to point at hardware not network.

[Simon]

That said, I've just tried switching off 3G, and setting the clock to Auto. It's fine. I then switched back to 3G, and at the moment, it's still fine. Can't explain that one! I still don't see how it could have been the carrier, with people on different networks all over the world affected, but I suspect we'll never know.

[Rik]

I think it's got to be a phone bug and, depending on how the date and time are coded, it may have triggered at a particular value.

[Simon]

I agree, but there still seem to be too many variables for it to be as simple as that. 

[Rik]

I wonder if we'll ever know...

[Technical Ben]

I wonder if it was 255 hours after the change?

Oops. Missed that. Rik to the first post as ever.

[Rik]

I need them to lean on, Ben.