iOS 6 Do Not Disturb Feature Failing To Automatically Turn Off For Some On New Year’s Day
Apple’s ‘Do Not Disturb’ feature may be one of the smaller functionality enhancements of iOS 6, but it has definitely proved to be really popular amongst the masses. The privacy based addition allows users to give themselves some peace of mind by disabling incoming notifications and phone calls and set filters accordingly. It seems that a number of users will be getting a lot more peace and quiet than they bargained for this New Year’s morning, due to an intermittent bug that prevents Do Not Disturb from disabling itself at the specified time.
A number of iPhone users have taken to online forums to report that the iOS 6 only feature is remaining active this morning, even though the scheduled time for it to turn itself off has elapsed. One of the great things about Do Not Disturb is that it actually comes with a small set of configurable options which allows the user to specify when the feature should become active and when it should turn itself off. It would appear that the change in year on the device timing system is causing the feature to remain active, but only for a small set of users.
This isn’t the first time Apple has experienced some iOS related issues at the turn of a new year. Last year saw a large set of iPhone users experiencing difficulties with the alarm functionality on the device, leaving them unable to rise and shine via their usual methods. That issue was solved with a quickly thrown together update to iOS, but it remains to be seen whether or not this reported Do Not Disturb bug will last beyond the first day of the year and whether or not any action will be taken on Apple’s part.
On a personal note, I have my Do Not Disturb scheduled to come on at 22:00 every evening and disable itself at 08:00 the following morning, with no overnight or functionality issues at this end as the new year came in. The forum posts also suggests that a lot of users have experienced no issues whatsoever, leaving us to believe that could be an isolated issue. Time will tell if Apple need to get involved.