I use the built-in clock/alarm to wake me up and it has been going off an hour late lately - ever since the 4.0 update. On the screen it will read "Alarm 6:15" and the actual time (both in reality AND on the Touch itself) will read 7:15. I've checked all the time zone stuff and it did it again today. Anyone else had this problem?
Adding my voice to the crowd. The iOS4 update seems to be giving me a lot of trouble. Battery life has gone down dramatically. The alarm didn't work for a while until I deleted it and added it again in the menu, and now it seems to be going off an hour early.
Alarms are naturally important to a lot of people. I don't know what could be so complex about it that it isn't easily fixable. Please patch quickly.
I live in northwest Indiana and have never had this problem, either with my original iPhone or with my new iPhone 4. But I always set my time to "Chicago" if I have to pick a city, because we're just an hour away from it & on the same (central) time zone.
I'll add that this part of Indiana has been on the central time zone (including daylight savings time) for as long as I've lived here... which started in 1987... So this issue probably wouldn't affect me, anyway.
I set my time zone to NY and after a day or two it seems to be working. I think I remember doing this before and it somehow reverted to the old "1 hour off" trick... I almost think it has something to do with one's current location even though the time zone is set by the user. More food for thought for iPod/iPhone users trying to get to work on time. I wish Apple understood if I lose my job, I can't afford more i-stuff!!
Yeah, looks like my timezone somehow was changed to East Coast/Indiana or something like that instead of New York. After I changed it back, it worked correctly.
It's still a bit bizarre since the time read correctly, but for some reason, the alarm went off an hour early than configured.
My touch woke me up 1 hour early today (3:30 vs. 4:30) Time was correctly reading 3:30 and weekday alarm was set to 430. And as noted in this string my battery has dramatically decreased... it is always on the charger now. I thought the battery was bad... not sure that is the issue after reading this string.
I have been considering upgrading to an iPhone but it was my FREE Samsung Solstice that I was able to rely on... It appears that the alarm problem is over a week old. Apple …Where is the patch?
Same problem here and I'm in London. It started when our clocks went back this weekend - my alarm went off an hour late this morning. Good job I woke up at the right time anyway.
Apple seems to have messed up this OS update - it's also created a lot of issues with ActiveSync and Exchange.
I'm in northern Indiana (USA) and we're on Eastern DST. I've since switched my time zone to "New York City" and it has been working fine. Problem is, now I've no excuse for being late to work...
My brother set his alarm this morning to get up for work, and it didn't go off, then when he got on the bus, an hour later it went off, he decided to play about with his ipod touch in many ways. He tried syncing his ipod with his computer to change the time settings, and he also turned it off + back on again.
Then he was changing the alarm settings and he turned of repeat, this then made the alarm go off at the right time than either an hour earlier or an hour later.
Same problem: Started 3 days ago, my alarm began sounding one hour EARLY on the iPOD Touch 2nd Gen 8gb.
At first, I thought it had to do with the fact that, up until a few years ago, DST ended on the last Saturday of October. It now ends on the first Saturday of November.
After reading these posts, I see that this problem has been going on for people for some time, so that theory of DST goes out the window for me.
For MONTHS I've had my alarm set to repeat every day, at 7 a.m. and now it sounds at 6 a.m. (one hour early) ...
I contacted Apple last night, and was told that I should do a complete restore, which I did while the tech stayed on the line with me.
I agree with the other posters: when it is set to sound off EVERY DAY, the problem is persists.
When it is set for one day only, it is fine.
I decided to try another test:
I set the alarm to go off on WEEKDAYS ONLY. This works.
(I know this doesn't help those who want to have it go off every day, as I'd like to have it, but, at least it seems that for those who work Monday - Friday and want to use this alarm to get up, as long as Saturday and Sunday are not included, it works. )
I do hope Apple will solve this one with the next update:)
My alarm started going off an hour early on 11/1/10. I have always had my alarms set for "everyday" but when I changed them to show a single day or "weekdays" it goes off at the correct time. I'm hoping that with the time change next weekend all will be fixed.
I'm hoping the same thing about the time change. I really do think that because up until a few years ago, the clocks rolled back the last Saturday in October.
October 31 is the first day I had the problem...so it really could be DST related.
Wouldn't that be great?
My friend always has hers set for weekdays only, and didn't experience the problem and we tested hers today, set it for an hour and 2 minutes later and it off 2 minutes later... :P
here's hoping it's DST and we don't have to wait for the next update.
For now, I just have weekdays, and a separate alarm for Saturday and another one for Sunday.
I am also having this problem and I live in Norfolk, VA. Just started happening on November 4, 2010 and at first I thought I was just losing my mind (which may be the case but is not germane to this issue). Anyhow, it happened again this morning and now it is annoying.
I ran a test to see if the alarm would go off if marked for Mon-Fri (instead of every day) and it worked as it should.
Yes, it seems that the problem lies with the EVERY DAY setting, but if you set it for WEEKDAYS, the problem is not there.
I set a Weekdays setting, plus a Saturday setting and a Sunday setting.
Hopefully the next update will fix it, as it seems this problem started with the latest update and people started having the problem in September or August.
