Phone Clock Wrong? How to Fix Time Drift on iPhone & Android

Your phone shows a time that's minutes — or a full hour — off, and you notice it right before a meeting or a clock-in. In almost every case this isn't a hardware fault: it's automatic time syncing that's stopped working, or a timezone that's set wrong. This guide walks through the exact fix for iPhone, iPad, and Android, then covers what to check if the basic fix doesn't work.

The short version: toggle automatic time off and back on

Phones are designed to keep correct time continuously from your carrier network or internet time servers. If the clock is wrong, either that sync has stopped, or the timezone detection is wrong. Start with these three:

• iPhone / iPad: Settings > General > Date & Time > turn on Set Automatically (if it's already on, turn it off, wait a few seconds, then back on)
• Android: Settings > System > Date & time > turn on Set time automatically (same off/on trick if it's already on)
• Both platforms: toggle Airplane Mode on for about 10 seconds, then off — reconnecting can force a fresh time sync. Restarting the device also helps, especially after a timezone database update.

Diagnose by how far off the clock is

The size of the drift tells you what to check first.

Minutes off usually points to sync; a clean one-hour gap usually points to timezone/daylight-saving rather than the time itself.

Fix it on iPhone or iPad

1. Reset automatic Date & Time

Open Settings > General > Date & Time and turn on Set Automatically. If it's already on, turn it off, wait a few seconds, and switch it back on. Make sure the device has an internet connection and is running an up-to-date iOS/iPadOS version before trying this.

2. Check the time zone

Turning off Set Automatically reveals a Time Zone field you can set by city — choose the correct one for where you are. It's common for a city set manually while traveling to get left behind; switch back to Set Automatically once you're home.

3. Check Location Services

Timezone detection can rely on Location Services in some cases, so leaving it on for at least Date & Time-related use makes automatic detection more reliable.

Fix it on Android

Go to Settings > System > Date & time and turn on Set time automatically (toggle it off and back on if it's already enabled). Do the same for Set time zone automatically if your device separates the two options. As with iPhone, an active internet connection and Location Services help the timezone detect correctly, and a restart after any of these changes can help the new setting take effect.

Still wrong after resetting automatic time?

Devices where the basic reset doesn't help usually share one thing: the path that delivers correct time is blocked somewhere. Check for these:

• No SIM, or a data-only SIM: without a voice-carrier connection, the device can't get a network time signal, so correction stops whenever it's off Wi-Fi. Connect to home Wi-Fi and reset automatic time there.
• After the battery has died completely: the internal clock can reset and be badly off right after the device restarts. It usually self-corrects once it reconnects to a network.
• Older devices past their support window: timezone rule updates (e.g., daylight-saving changes in a given country) stop arriving, so automatic detection can be wrong even when it's "working." Setting the timezone manually is the practical workaround.
• Custom ROMs or rooted devices: time-sync behavior can differ from stock Android, and this is hard to fix reliably outside of reverting to stock.
• A company-managed device (MDM): a work profile can grey out Date & Time settings entirely. This isn't a bug — contact your IT department instead of trying to work around it.

If it's a computer's clock that's wrong rather than a phone's, the cause and fix are different — Windows and Mac both have their own automatic time-sync setting under system Date & Time settings, and the same "toggle it off and back on" trick usually works there too.

Why a wrong clock causes bigger problems than it looks

A few minutes of drift isn't just cosmetic — it quietly breaks anything that depends on exact time.

Two-factor authentication codes get rejected

Authenticator apps generate their 6-digit codes using TOTP, which calculates the code from the current time. RFC 6238, the TOTP specification, defines a 30-second time step and recommends that verifiers allow some tolerance for clock drift between client and server — but that tolerance is set by each service, so a badly wrong device clock can still get every code rejected. If your password is correct but 2FA keeps failing, check the clock first.

Time clock, booking, and ticketing apps

Many time-clock apps rely on server time rather than the device's display, but a wrong on-screen clock still causes confusion about what was actually recorded. Restaurant reservations and ticket on-sales that rely on your device's clock can also make you appear late — or miss the exact drop time — if it's off.

Certificate errors and app login failures

HTTPS certificates are only valid for a specific date range, so a device clock that's badly wrong can make a site's certificate look invalid and block the connection. Some apps failing to log in, or a browser suddenly showing security warnings, can be a clock problem rather than an app problem.

Using an old phone as a desk clock

An old phone or tablet propped up and charging, with the screen filling with the time, makes a genuinely useful desk clock. Mihata's free Focus Clock turns any browser into a full-screen digital clock, with no install and no account.

One honest caveat: a browser clock displays whatever time the device's own OS reports — it doesn't pull time from a radio signal or time server of its own. If the phone's clock is drifting, the browser clock will show the same wrong time. Fix the automatic time setting first using the steps above, then set up your desk clock.

Frequently asked questions

How do I manually set the exact time on my phone?

On iPhone, go to Settings > General > Date & Time and turn off Set Automatically to enter the time zone and time manually. On Android, turn off Set time automatically under Settings > System > Date & time. Manual settings drift again over time as the internal clock's small error accumulates, so switching back to automatic once the underlying issue is fixed is the better long-term option.

Why is my phone exactly one hour off?

This usually points to the timezone rather than the time itself — often a daylight-saving-observing zone selected instead of your actual one. Check Time Zone on iPhone or the automatic timezone toggle on Android and confirm it matches where you actually are.

Date & Time settings are greyed out and I can't change them.

This happens when a Screen Time passcode is set, or when a company-issued device has a management profile (MDM) restricting the setting. On a work device, don't remove the profile yourself — contact your IT department.

Is a rejected 2FA code caused by clock drift?

It can be. Authenticator codes are calculated from the current time using TOTP, so a device clock that's significantly off will produce codes the server rejects. RFC 6238 sets the time step at 30 seconds and lets each service decide how much drift to tolerate. Reset automatic time first, then try again.

Does the clock stay accurate on a device with no SIM card?

Yes, as long as it's connected to Wi-Fi — it can still reach an internet time server. Correction pauses while it's offline, though, so a device used offline for long stretches can drift. Keeping Location Services on also helps timezone detection stay accurate.

If clock drift keeps causing login or attendance problems across your team's devices, it's often a sign that device management is worth a closer look. Mihata helps small and mid-size businesses with practical IT and AI support — happy to talk through what's actually needed for your setup.