iPhone Alarms Hit By New Year's Bug
An anonymous reader writes "Non-recurring iPhone alarms stopped working on January 1 for devices running iOS 4.02, 4.1, and 4.2.1. Apparently, it will fix itself by January 3, and the current workaround is to set the alarm to repeat. My girlfriend wasn't impressed, sleeping in, and I wasn't either, having to race her to work!"
I don't understand why you use a phone as an alarm clock. For one it depends on a single power supply, or you have to charge it overnight next to your bed. Second, it uses software prone to bugs. I use a normal alarm clock on 220V, with a backup battery. It invariably goes of in time...
The only time I use my phone as an alarm clock is when I'm on vacation/business trip and even then, hotels have waking services
However, to be frank: These kind of bugs are unacceptable. If this were Microsoft, everyone would be laughing and scolding, but since it's Apple I'm sure we'll get excuses....
Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
First poster's alarms must not be working.
first post
My girlfriend wasn't impressed, sleeping in, and I wasn't either, having to race her to work!
Shall I call you a waaaambulance?
If you want news from today, you have to come back tomorrow.
Uh oh, I see Apple bashing coming. Defend yourselves
Thank you for posting this very interesting story. I am utterly fascinated at this, at alarm clocks failing to work. I look forward to reading the commentary on this breaking news piece.
Day light saving errors, new year errors, do they just have crappy coders at apple?
Apple can't quite seem to get that alarm working right. This isn't the first time. My Android based phone hasn't had any issues with the alarm, but since I work from home it's not as much of an issue.
See, this is why you need to convince your girlfriend to get into the habit of morning sex. There is no alarm clock more reliable than the human wang and as an added bonus there is no snooze button either :P
Monstar L
Thinking back to the Zune clock bug error, that one affected only a single model because the bug was in the interface between a particular brand and model of RTC hardware and the kernel.
Is this a similar error, confined to a driver issue with one platform's RTC, or is it an error in logic somewhere higher up the stack, and thus going to occur on all iDevices of a given firmware level?
Mine didn't go off to get me up for work. Fortunately I woke up only 10 minutes after it was supposed to go off. Apple released a comment saying they were unaware of any reason this could happen, but as the article above said it should resolve by Monday.
Chewbacon
The Bible is like Wikipedia: written by a bunch of people and verifiable by questionable sources.
This is like the third slashdot reported instance of a Y2K style timing bug and the last was in 2010 when 9++ = kaboom lol. It's unbelievable that people still leave glitches like this in their software. Is time really that hard to calculate and program around? People still can't program their software mere months out from a year rollover to be able to handle it?
Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
OMG, it is self aware, has introspection and can self improve? Now I know what all the Apple fans love it so much.
thegodmovie.com - watch it
This just isn't a plausible claim. As if "anonymous reader" has a girlfriend. Now I've heard everything.
... and then they built the supercollider.
Very few millions of people 20 years ago were downloading shareware. Cellphones, on the other hand, have an explosion with millions of Apps being marketted, and it's now cool and mainstream to pay cash for programs from sources who barely know how to code. Our world is being overrun again by easy-money coders who never passed a CS101 course or never got a full programming education. They are likely people programming in Visual Basic made obsolete by the new niche we call the Apps world. 7 years ago the New York Times said only 10-20% of IT workers in the US had a Bachelor's degree in Computer Science (4 year studies.)
The rest just wing it; never mind that not every CS degree makes you a programmer. Some untrained people are good, but from the rest we have buggy code like these alarms; nobody tests their products well because updates are "easy."
Last year, IIRC, there was a problem with Playstations (or PSP's or some MS hardware product) with the change of date for the New Year. As GOOD programmers get older, none of the fresh programmers care to learn how to avoid the old mistakes, probably because of details in my above rant. These bugs could have happened to wipe their phone data too, and the day we start seeing that is when people will realize that Apps are just like shareware code. Then, they'll return to ignoring things from untrusted or unproven sources.
It just works.
The point is that the iOS time routines are unreliable. You need a redundant clock/alarm that doesn't run on iOS.
I bought my girlfriend an iPhone, and the damn thing seems to set off the alarm at random times.
However, when I look at that thing, my Nokia N95 looks like crap in comparison. I'm no Apple fanboy, but I am really impressed with that thing.
Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
Don't be surprised that this keeps happening. Writing reliable software as mundane as the clock routines just isn't going to impress anyone. Everyone assumes that the existing, broken & untested date time routines works fine. We all know what happens when you make an assumption...
Really? Is that what really happened?
"What kind of music do pirates listen to?" -Paul Maud'dib
"Yeeeaaarrrrr n' Bee!!" -Stilgar, Leader of Sietch Tabr
"...My girlfriend wasn't impressed, sleeping in, and I wasn't either, having to race her to work!"
So for once in your life, you have an iron-clad excuse as to why you were late to work (posted on Slashdot, confirmed by vendor), and you're bitching?
That is sad, when you really think about it. Sad.
We've gotta nap for that!
"You're holding it wrong".
Llike with building services do _not_ trust any single device not to fail.
Instead use any two different type wake-up devices whenever it's important to get up at certain time. If it isn't that important then any single device will do the job usually.
Though last year they failed to charge the battery for some reason.
and the 2nd being Sunday, I am actually surprised how many people have crappy jobs that hey had to get up for on the weekends.
I read Slashdot for the headlines, because the headlines, unlike the articles, are usually original and never duplicated
If you want a reliable alarm clock, have kids
"the alarm will not ring if the power is out at the time of the alarm."
Mine does. It's an irritating high-pitched beeping, but it still goes off. Maybe you just have a crappy alarm clock.
just that.
There was enough time to fix this an several other updates were pushed out since this happened last,
so i'm not impressed by the job Apple does here.
- Hubert
until i read read this i wasn't know about my iphone alarm as i never used it.
Yes... alarm clocks usually have a single alarm time and don't work well for multiple people - I want to keep napping if my wife's alarm rings first and vice versa !!! :)
how to win the lottery
Unfortunately I am getting this vibe more and more from Apple's latest offering. Their earlier iPhone was great, and their new iPhone's glassy facade gives me a woody every time I see it. But there seems to be one critical problem after another with this one.
Are they the new Microsoft? Is this the Vista of the iPhones?
Apple make good phones. Their other stuff I don't really care about.
The fact my expensive new phone can't even manage to keep the time, twice this fucking year now (last one was when daylight savings came into effect), is really irritating to me. Last time I checked, clocks were pretty important. Alarms are also important. The alarm stays on but doesn't trigger. I don't even understand how this could happen on something as basic as a year change.
We're way past Y2K to be having this kind of crap happen.
Oh, and I do work one of the aforementioned 'shit jobs' that requires me to be at work by 8am on a Sunday morning (this marks the second time my phones made me late now). Guess I should buy a $10 alarm clock that can actually keep the time better than my $800+ phone.
I'm certain that the Macy's display case was deeply impacted by your "girlfriend's" tardiness.
.
.
BTW: Buying your plastic GF an iPhone is really over-the-top geekiness.
If only Apple had access to some sort of communication device to alert its users that there was a problem...
Seriously, a non-functioning alarm is a pretty serious problem, why no alert from AT&T?
And no friggin' daylight savings.
I like the fact that in the summer, the dawn doesn't start to break at 4 in the morning. Or that it gets dark later than during the spring/fall/winter.
Mit der Dummheit kämpfen Götter selbst vergebens
What?
How the heck does Dr. Seuss get modded troll?!?!
"City hall" in German is "Rathaus" Kinda explains a few things......
"It doesn't work, but it sure looks sexy"
Sucker. Never buy Gen A.
Original iPhone was Gen A.
iPhone 3G was Gen A.
iPhone 3GS was Gen B.
iPhone 4 is Gen A.
In short, wait for the next one.
I used cell as alarm mainly because of power outages, but really the idea of having fewer gadgets doing more work makes sense to me.
The one time I invested in a batt backup alarm, I wasn't smart enough to put it on surge protector, and lightening whacked the whole thing. (My fault, not alarm/batt backup.)
But my cell alarm's never failed me yet.
(Then again, it's not apple.)
Apple didn't think it was important-you shouldn't either.
Clearly, if you paid for an Apple product, you are used to being told what to think.
"It's wonderful." It just works - sometimes.
"There aren't any security issues." Once Apple gets around to patching them 2 yrs later.
"It isn't overpriced, it is high quality hardware" After you pay $1800 for a $750 laptop.
The fact that they can't seem to get clocks and alarms correct just shows how bad their development and QA teams are. This is simple stuff folks. Testing boundary conditions is a fairly well known thing. You test end of year, leap year and time changes too. At least other companies do, even if Apple doesn't.
Someone needs to get fired over this. Actually - 5 people need to be fired.
1) the guy that wrote the code
2) the guy who reviewed the code
3) the guy who's testing missed these trivial errors in the code
4) The boss of the developers
5) The boss of the QA team
If this were FLOSS software, the fix would have been released a few hours later on the first day of the problem.
Nice job Apple. Making something trivial look really hard.
BTW, I do not like Apple, if you couldn't tell.
Their earlier iPhone was great, and their new iPhone's glassy facade gives me a woody every time I see it. But there seems to be one critical problem after another with this one.
Personally I think it's mostly the media having a field day blowing things out of proportion. I have the new iPhone, both my sisters have one, my brother-in-law has one and none of us have had anywhere near the problems that are being reported in the media. Sure, there's been a few minor glitches here and there but nearly EVERY device has those. We certainly haven't experienced any problems that were major enough to stop us from using the iPhone or consider switching to another device.
Sapere aude!
This is why, when I have something important, like a airplane flight, I always make sure to set multiple alarms. I mean on different devices. I usually use the iPhone for my alarms, but on important cases I add at least my old mechanical wind-up alarm clock. No power or battery or software requirements still makes that the most reliable, if you have something like an airplane flight or job interview.
RogerWilco the Adventurous Janitor
I bought my girlfriend an iPhone, and the damn thing seems to set off the alarm at random times.
Well then why don't you just tell her not to?
My android phone alarm didn't go off this morning either... then I see articles about the iphone alarm bugs... any other android users have issues today?
Actually, dawn breaks even earlier at times. With DST even.
Mit der Dummheit kämpfen Götter selbst vergebens
"It doesn't work, but it sure looks sexy"
Sounds like my wife.
Good thing I'm still on version 1.02, my one-time alarm yesterday morning worked fine.
Does the one hour really make a difference for you?
Like anything important in life, it's good to build in some redundancy. In this case, have two alarm clocks!
Sure it does if it starts to dawn at 4 in the morning. Or 3:30.
If you are supposed to get up at 7 or even 8, that is the difference between being half asleep for the last two hours of sleeping and being already wide awake an hour before you need to get up.
And if your daily rituals depend on being at a certain place at 8 or 9 (and not earlier) and staying there until 16 or 17 (and maybe later) - that hour of sleep MAY be somewhat important to you.
Mit der Dummheit kämpfen Götter selbst vergebens
The WoW authentication servers broke at about the same time, maybe the Horde has Android and were awake and ready, but the Alliance were still asleep! Or maybe the same guy who wrote the alarm code, wrote the code for the authentication daemon.
I don't care what alarm you use...just get your ass to work.
this is what the fanboi's keep telling me but i just don't see it.
I've never been able to completely convert to relying on my phone for time. It works great for scheduling, task management, and reminders, but I've been hard pressed to use it as a watch or alarm clock where clocks and watches are available.
I have 2 clocks in my bedroom. One is a big analog clock on the wall because it looks nice and is big so easily readable from wherever in the room (even the hall). I also have an alarm clock next to my bed that has an alarm type I've never seen in any other alarm clock (crescendo alarm, starts quiet then gets loud, works great with snooze when you don't want a blasting alarm waking the whole damn house). If I want to know the time at home, chances are I'm looking for a wall clock first. Even when I'm at a computer, I look at the wall clock mounted on the wall in front of me.
I use to wear a watch all the time, but now I don't. Pretty much the only thing my phone has replaced in terms of being a time reference is my watch when I'm not near anything readily visible.
As for my phone being great for reminders, it is not my primary system for providing reminders. My schedules, tasks, etc, are synchronized with all of my computers. Not only will my phone alert me, but depending on the type of reminder and the importance, I'll get a popup on my computer, email, and/or text message. This is something that is important enough to me that I can't allow for a single point of failure. Of course, this can require a small amount of extra work and people these days are so lazy that it's not worth it to them to exert that extra effort to make sure it works.
With all that said, my Android phone has not failed me to date. Sure, it's had problems, I'm not saying it's better than iOS because iOS does have some advantages. However, it has never failed me, personally, and that experience will keep me loyal to Android.
I thought it only happens twice a year.
You have to adjust your wardrobe more times a year than that - and that doesn't get you more sleep time. And better too, as it gets you more "dark time" in the morning during half a year.
And me... well... me, I like sleepin'...
Mit der Dummheit kämpfen Götter selbst vergebens
This part of the problem with the fact software companies aren't held responsible for any fuck up they make. There is no incentive at all to test properly or even code properly.
It's not as if companies like Microsoft and Apple are poor and can't afford the best. They just don't want it and there is no benefit in doing it right the first time. They can push out something broken and no one really cares so they can patch it when they feel like it.
Software companies get away with a lot more than producers of physical products. I think that needs to change.
It does in the northern latitudes of the US, anyway. Just as we start to lose our evening daylight hours in the fall, along comes the DST change to rob yet another hour of usable light.
It's not the stupidest damn thing ever, but it's gotta be in the top 100, somewhere.
Unless the submitter is a lesbian I call shenanigans.
By the 365th day Steve had finished the work he had been doing; so on the seventh day he rested from all his work. Then Steve blessed the 366th day and made it holy, because on it he rested from all the work of creating that he had done.
Starbucks, Harbuckle of Breath.
The 27" monitor has a spec sheet and lists the system requirements necessary - just like any other computer monitor from any other manufacturer.
But don't you find it strange that the only line of monitors which a manufacturer sells does not have any connectivity options for sub-2 year old (and certainly not cheap) laptops that the SAME manufacturer made?
A bug is a bug, that's not an issue. All devices have bugs, but when bugs appear in both fundamental and basic functions then it starts wreaking of crap quality control.
As some people have pointed out testing cases for timing applications including the end of the year is programming QA 101. I would just chuckle if this was the first time this has happened. But this is the second time a major bug has screwed around iPhone users in the alarm application. It stuffed up daylight savings time too, which makes me think if they didn't review the code then, what's going to happen on Feb 29th? The question is will they actually review the entire code this time or just patch this flaw.
Also alarms not going off in a device which the company is actively pushing at businesses isn't a minor annoyance either. Neither is calls dropping out when the iPhone is held with the left hand.
This isn't Apple bashing, this is observation and other companies aren't immune to this either. In fact I would rate the Android bug of sending SMSes to the wrong recipient more critical than an alarm problem, but then I don't rely on an alarm anyway. I set it every night but always seem to wake before it goes off.
One mans minor annoyance is another's showstopper. I'm buying a Galaxy S next week (decision predates this iPhone issue so don't think this bug had any bearing on it, but I also didn't change my mind when I read about the sms bug). I know plenty of people who would consider that a showstopper.
Gee - your four year old phone looks crap in comparison to the latest iphone. Who'd have thought it?
That's because the N95 is crap. A network unlocked iphone is over triple the price of a network unlocked N95.
Just as we start to lose our evening daylight hours in the fall, along comes the DST change to rob yet another hour of usable light.
One... THAT is not the DST. That is the "regular time" you are complaining about.
Two... If the DST was kept on the whole year round, the sun wouldn't rise 'till 8 or 9 in the morning in December-January.
And the night would keep on falling earlier and earlier anyway, all the way until the winter solstice when the day would start getting longer again - not that you would really notice the change until mid-February.
A fine thing that would be for the working people. Seeing sunlight only on weekends during most of the winter.
Mit der Dummheit kämpfen Götter selbst vergebens
As some people have pointed out testing cases for timing applications including the end of the year is programming QA 101. I would just chuckle if this was the first time this has happened. But this is the second time a major bug has screwed around iPhone users in the alarm application. It stuffed up daylight savings time too, which makes me think if they didn't review the code then, what's going to happen on Feb 29th? The question is will they actually review the entire code this time or just patch this flaw.
As a programmer I can tell you that date and time calculations are among the most tricky ones that you have to do. It's so easy to get wrong with leap times (days, minutes, seconds, fractions of a second), time zones, local time adjustments, changing rules on how dates and times are calculated, various calendars, and so on. It's very easy for a tricky bug to get coded into the algorithms and to have it suddenly show up without much time to correct it.
Not that bugs, especially core ones in date and time functions, are acceptable. You do everything you can do to test the code and ferret them out. It's just one of those areas that bugs are likely since so many tricky rules are involved. I'm sure that Apple will try to locate the code that causes this bug and correct it. Hopefully that will be the end of the problems.
I agree that the Android SMS bug is also a bad flaw in a major function of a cell phone. Again, I'm sure that Android developers will do their best to correct it.
The fact is that modern computing devices are extremely complicated systems with tons of interacting components, many different developers, and plenty of potential for unintended side effects. You take your chances when you use such devices and it's up to each person to decide if they can live with any issues that pop up or if they want to take the chance on a different device. I've had a decent enough experience with the iOS devices that I can live with the bugs that have popped up so far, I don't think that it has that much higher or lower of a rate of bugs than similar devices by other developers.
Sapere aude!
As an embedded systems programmer I can tell you that date and time calculations are amongst the most well documented and easy to implement things I have done. I find programming a microcontroller to send a packet over a network far more difficult simply due to the fact that we have been using electronics for timekeeping since the transistor was invented. I would agree with you if we were in the late 80s but this is 2010, and a bug like this would be inexcusable.
Ultimately though this is beside the point. The phone never had a problem keeping time. The bugs were in the calendar / alarm apps which didn't come to terms with the fact that time may change slightly, and not with the underlying timekeeping code. Also of note is that iOS 3 wasn't affected. It sounds more like a lack of project cohesion between teams than anything. Especially the daylight savings issue a while back where recurring alarms would compensate for daylight savings despite the operating system already doing just that.
> then it starts wreaking of crap quality control.
And you're reeking havoc on the English language, moron.
I've heard about this new invention, it lets you continue sleeping even when it is light outside, I think it is called curtains or something.
For the third day in a row it hasn't worked. What a piece of shit.
I have a variety of times set as non-repeating alarms in both phones, and I turn those alarms on as needed each night before going to sleep. There are few alarm clocks that come with a more irritating sound than the iPhone's "Alarm" sound, so this works for me. Until this year.
On Jan 1, 2 and 3, the iPhone 3G worked as expected, but the iPhone 4 did not go off at all, even this morning, despite Apple's claim that the bug would fix itself. Out of curiosity, I created two new alarms, one repeating and the other not repeating, on the iPhone 4, and they both went off as expected. It seems you have to actually delete any alarms created before Jan 1 and recreate them if you want them to work.
I had an amusing moment on Sunday at 9:00 sitting in my office with my boss when one of my employees called and said he just woke up and had no idea why his alarm didn't wake him up:
My boss, who also has an iPhone, but apparently uses his 5-year-old son as an alarm clock, just stared at me. I'm sure the same scene will play out today because the bug did not really fix itself. Even though I have a device that's not affected and I understand what's going on, this is still going to impact me because other people around me don't... and some of them were told by me that it would "fix itself" this morning. <SARCASM>This totally undermines my credibility... the next time someone is missing money from their paycheck and I tell them it will "fix itself," they're not going to believe me!</SARCASM>
That and the earplugs so you don't hear the birds chirping in the morning - and you don't have to get up at all as you won't hear the alarm in time to get to work anyway.
The planet and most of living things on it don't give a fuck about OUR way of measuring time.
Daylight Saving Time is US adapting to our ecosystem in order to get more out of the deal - not the other way around.
Mit der Dummheit kämpfen Götter selbst vergebens
As an embedded systems programmer I can tell you that date and time calculations are amongst the most well documented and easy to implement things I have done.
You really don't have a clue about what you're talking about, do you? Yes, dealing with absolute time is trivial. Those of us who have to deal with human time don't have that luxury. The people keep changing it around, they add and remove randomly sized chunks of time on a whim and give extremely short notice, shuffle around when (or if) daylight saving times or other stupid shit like that happens, etc, etc.
The bug is still inexcusable because it should've been caught in testing, but anyone who has ever dealt with dates instead of tick-tock of seconds somewhere deep in a microprocessor that just needs to be internally consistent can tell you that these things are NOT easy to implement.
The phone never had a problem keeping time. The bugs were in the calendar / alarm apps which didn't come to terms with the fact that time may change slightly, and not with the underlying timekeeping code.
Well, the proper way to handle this is to use NSDate and NSCalendar along with the Event Kit Framework. If you use these classes then they should handle all of the time changes for you, rolling your own code to do this is definitely not a good idea because there are so many issues with time changes and calendar idiosyncrasies.
Basically it comes down to either the apps in question are doing the calculations on their own and there are errors in those calculations or the frameworks themselves have these bugs. I think it's likely that the bugs are in the frameworks because Apple is usually pretty good about using the proper frameworks rather than taking shortcuts.
By the way, here's an excellent write-up of some of the issues as well as examples of how to do these calculations in an iOS app.
Sapere aude!
I have had various mobile phones since about 1999 that have replaced my wristwatch alarm clock and PDA - the next model will probably replace the tv. However, I do have the more reliable http://www.amazon.co.uk/Doctor-Dalek-Talking-Alarm-Clock/dp/B000F44POS (sadly for all Dalek fans, apparently not currently available.) which wakes me up every morning at 6 am with threats of imminent extermination.
Even if the Nokia has run out of juice the Dalek does its job. Turns off after ten minutes or so ( at least I think it does, it must threaten the neighbours every morning when we are on holiday cos, I always forget to turn off the alarm!).
There is of course no real way to defeat the Daleks.
Apart from stairs.
Posts, MyBio or Sig, may contain satire, sarcasm, bolded nouns be sardonic or even witty & be Church of SD
Apparently, it will fix itself by January 3
Apparently not.
Required reading for internet skeptics
Would switching ios to open source have caught this bug earlier? This bug is a huge one, since it is a critical system which is required to be 100% reliable with consequences affecting users on important things such as aeroplane trips. In my case I was lucky enough that my parents also set an alarm on their reliable alarm clock, I was wondering why mine didnt go off, but then again I remembered this bug occuring during day light savings time which was now meant to be fixed(i guess only for daylight savings not new years-lol). Obviously their TDD was lacking in this area. Being that Apple only makes money off their hardware, at least thats what they tell us. What is the crime in giving their platform to the community so that their hardware will feature the most reliable software due to communities involvement and bug fixing? I'm not very familiar with how much of android is actually open source but i suspect apple could be benefiting from a similar strategy.