iOS 6's 'Do Not Disturb' Not Shutting Off Automatically on New Year's Day

It just works.

No problems here on my iPhone and iPad.

Mine was scheduled from 3 am to 7 am but was still on long after 7...

OLDCODGER said:

What about just turning the "bleeping" thing off for the holidays, It won't kill you?

Click to expand...

Well some people use their phones for work and need to have personal time.


Mine was slated for 7am and it s turned off at 8am CST. Not the end of the world.

At least they didn't leave out the whole month of December like google did

Mine was scheduled to turn on at 1 am. Turn off at 4am... Of course it turned on. It's now 6:32 am and it hasn't shut off

TroyBoy30 said:

At least they didn't leave out the whole month of December like google did

Click to expand...

Wow....trolling for an argument?

..........

I had issues at first with 3rd party app alerts but recently it seems to be fine (or I'm sleeping through alerts lol). I only use it on occasion though. Does what I'd expect out of it....

I had one weird bug where, I restored my iPhone 5 (using the Restore All option from the Settings app) and the next day my alarm goes off, as it used to be set to before the restore.

Then it hit me -- HOW?

I opened the Clock app and sure enough -- NO ALARMS were present -- as it should be when a "full" restore from the Settings app is performed.

Scary, scary, iPhone ghost? But still -- it woke me up (and I even had to swipe it silent) that morning... which was a good thing.... friggin' freaky though.

Mine is still on, just noticed it now. Looks like Apple should hire a guy who's only job is to test year end/DST/time zone transitions.

Yup...

Had the same issue, no problem for me (ipad mini), but maybe a bit emberassing that apple can't handle a simple a simple date-change properly (this is not the first time)

Just like the prior rumor about failing alarm clocks in previous years, My iPhone came out of do not disturb phone like expected for New Years day without issue...

Both my alarm and DND (10pm to 7am) came out fine this morning.

MacMan1620 said:

It's nice to see all these trolls making a small issue look like the end of the world. Oh no!, "do not disturb" has ruined my New Years.

Click to expand...

Or maybe MacRumors is trying to invent a story that may be is not there just to post something before New Years Day.

Anyway, HNY.

codedbydesign said:

Every... ****ing... Year...

Click to expand...

My thought EXACTLY. How do they have an issue with something every single year??? Has no one at Apple ever dealt with a January 1st date on their equpiment.

This actually doesn't surprise me. I've started looking forward to a new mishap every year. Calendars, iCal, Clocks, scheduled events, etc. it has to be something.

If something doesn't happen to an Apple device on January 1st, my day isn't quite right. I've come to accept it. As absurd as it is, it's just become the new normal.

I turned it off (and back on) in my Notifications section, but turning it off the Do Not Disturb switch in Settings didn't do anything. Looks ok now, I guess. No need to reboot; just toggle.

Yep... This happened to me this morning (11pm - 5:30am).... Had to restart my phone, guess I could have just turned off the feature.
Hopefully the same thing won't happen tomorrow morning.

Bad Apple.

OLDCODGER said:

What about just turning the "bleeping" thing off for the holidays, It won't kill you?

Click to expand...

That's not the point.

And plenty of people work during the "holidays" or need to contact friends and family, so they need their devices.

My iPhone 5 shut off DND like normal, but my iPad 2 didn't. Some weird glitch. Just turn off DND, turn off the schedule, then turn the schedule back on,

I was too drunk at midnight to notice

IOS 'do not disturb' gate ....

Maybe I should check Apple Maps for locations of mountains that were once molehills.

haruhiko said:

Crap my DND is still on! It's 2:13pm already in HK.

Click to expand...

Many of my friends in several countries use DND and no one has reported issues so far. And neither me nor my flat mates have had issues.

Happened to me, not a big deal though, but still I always wonder what the bug is (as a developer I wish we had more details just to avoid making the same mistake one day).

Bathplug said:

The beginning of the end of the world as we know it. Hide yo wife, wide yo children!

Click to expand...

I wondered if the Mayans had bad handwriting and it really said Dec 31, not 21.

thejadedmonkey said:

This isn't daylight saving time, (which, isn't all that hard to do), it's a year. When you consider it's a flagship part of iOS 6, it's quite sloppy on Apple's part.

Click to expand...

All time/date calculations are done in one library/module usually.

No individual part of dealing with time is overly complex, but taken in it's whole, which is how we deal with such things, it is complex.

Again, it is quite silly, a little embarrassing even, but everyone struggles with this stuff.

Karl P