Traditional Apple screw-up makes iPhone users late again this year
by Alan Friedman / Mar 10, 2019, 9:33 AM
Here we go again. This morning at 2 am, Daylight Savings Time (DST) returned to most of the U.S. That means clocks were moved ahead an hour allowing it to stay light outside later in the day. It also means that once again, Apple iPhone users will be late to any appointments they might have scheduled for today. While most devices (like televisions, computers, smartwatches and Android phones) automatically adjust for the time change, for some reason it has become a tradition for the iPhone and iOS to screw it up.
were pushed back an hour instead of being moved ahead an hour, which could have made some iOS users up to two hours late. That same year, when iPhone users asked Siri when Daylight Savings Time was scheduled to start, the virtual assistant replied with the wrong date.Yes, the iPhone is supposed to adjust the time automatically. But this morning, one iPhone owner who set his alarm for 7:30am nearly overslept because his iPhone did not automatically adjust the clock for DST. This has also been the experience of several iPhone owners today. All oOf course, it could have been worse. Back in 2012 the clocks on iOS devices
There is a simple solution for iOS users who need to get up at a specific time on the day when DST begins or ends. Set two alarms, one assuming that the iPhone will change the clock automatically, and the other assuming that it won't. If your iPhone or iPad has not adjusted for the time change, you can set the clock manually. On iOS 12 go to Settings > General > Date & Time. Tap the the Set Automatically toggle to turn it off. Type in the correct time or scroll to select the correct time.
As we pointed out already, Android users don't need to worry about the time change. As for iOS users, once they manually adjust their clocks they will be okay until 2 am Sunday, November 3rd. That is when DST comes to an end for 2019.
Posts: 736; Member since: May 17, 2017
I didn’t know this was a thing. I’ve never noticed it!
posted on Mar 10, 2019, 9:54 AM 3
Posts: 30783; Member since: Feb 05, 2011
Got me twice bro, but not recently.
posted on Mar 10, 2019, 10:53 AM 1
Posts: 6445; Member since: Jul 11, 2012
This is way too funny!! Seriously...have you been under a rock for the last few years??
posted on Mar 10, 2019, 2:07 PM 3
Posts: 736; Member since: May 17, 2017
I will explain, again. I have not, until recently, used my phone as an alarm, especially on a Sunday. This glitch would likely escaped my notice. Also, I have not always used an iPhone. I guess I just missed all the stories about it. Life, you know...
posted on Mar 11, 2019, 7:44 AM 2
Posts: 2996; Member since: Dec 14, 2017
Just because you never noticed it doesn't mean that it never happened.
posted on Mar 11, 2019, 12:15 AM 1
Posts: 120; Member since: Jul 17, 2017
Instead of fixing damn bug I need to set two alarms hell yeah, my 15$ desk watch can adjust DST and alarm, but 1k $ phone can’t awesome :D
posted on Mar 10, 2019, 10:03 AM 14
Posts: 88; Member since: Mar 05, 2019
My iPhone XS automatically adjusted the time but even if it didn't for some users it didn't change its worth of over 1k
posted on Mar 10, 2019, 2:19 PM 2
Posts: 6349; Member since: Dec 02, 2011
I think Apple controls the EU, because the Parliament will be passing a law banning the 2 changes of the hours. Goddam that TimApple...
posted on Mar 10, 2019, 10:07 AM 0
Posts: 1152; Member since: Sep 04, 2015
Meanwhile your beloved Apple after years, still can't get it right.
posted on Mar 10, 2019, 10:25 AM 14
Seriously?! Is this what this site has become? Literally turning into BGR. Nothing but clickbait headlines. You make an entire article based on one persons complaint. Hey “journalists” before writing this, did you: • confirm that the user had automatic date and time enabled? • was in a location that observes DST. (Was he traveling?) Millions upon millions of iOS users woke up this morning with no issues, but you found one unverified claim and you decide to run an entire clickbait article about it? And for those that are curious, they do the same damn thing with android. This site has become the new BGR and rather then giving honest reviews, insightful opinions and breaking news in the phone industry, you’ve begun scraping company forums or Reddit for any unverified, one-off claims that you can find and then run a clickbait article about. So frustrating because this site used to be so much better. It used to be so much more. I’ve been here for years and just now made an account for this comment. I hope that you reconsider your clickbait tactics as it has caused great harm to BGR and I fear you’re going the same way.
posted on Mar 10, 2019, 10:39 AM 2
Posts: 570; Member since: Mar 21, 2012
For your information, I did check with those affected since some were friends and family. So this was actually a situation that affected people close to me that I know personally. And for the record, if you read the article I said that this happened to several iPhone users, more than just one. Regards, Alan
posted on Mar 10, 2019, 11:04 AM 12
“But this morning, one iPhone owner who set his alarm for 7:30am nearly overslept because his iPhone did not automatically adjust the clock for DST. This has also been the experience of several iPhone owners today. Of course, it could have been worse.” For your information, you provide no sources, you provide no facts and you provide to confirmation that the users settings were enabled and set up properly. Your next sentence brings up something that happened 7 years ago, which is a lifetime in tech. You guys can do so much better. You have done so much better before. This article is far below the standards that this site used to have.
posted on Mar 10, 2019, 11:36 AM 1
Posts: 1556; Member since: Aug 15, 2011
Get an android you won’t have this problem
posted on Mar 10, 2019, 12:50 PM 13
Send a warning to post author
Send a warning to Selected user.
The user has 0 warnings currently.
Next warning will result in ban!
Ban user and delete all posts
Message to PhoneArena moderator (optional):