Permanent Daylight Saving Time: How to Fix Clock and App Issues on Every Device

If the U.S. moves to permanent daylight saving time — or if your state or country has already stopped the clock change — your devices may not adjust automatically. Here's exactly what to fix, device by device, so your alarms, calendar events, and app notifications stay accurate.

Quick Fix First: Do This in 60 Seconds

1. Go to your device's Date & Time settings.
2. Turn Set Automatically OFF, wait 5 seconds, then turn it back ON.
3. Reboot the device.

This forces your device to re-sync with the network time server and pull the updated time zone rules. If this doesn't resolve it, follow the device-specific steps below.

iPhone and iPad

Fix 1: Force a Time Zone Rule Update

1. Open Settings → General → Date & Time.
2. Toggle Set Automatically off, then back on.
3. Under Time Zone, confirm your city is listed correctly — not a nearby city that may have different DST rules.

Fix 2: Update iOS

Apple pushes DST rule changes through iOS updates. If your clock is wrong after a permanent DST change, go to Settings → General → Software Update and install any pending update.

Fix 3: Fix Calendar Events That Shifted

Existing calendar events created before a DST rule change may shift by 1 hour. To correct them: open the event in Calendar, tap Edit, and manually adjust the time. For recurring events, choose Edit All Future Events.

Android

Fix 1: Resync Network Time

1. Go to Settings → General Management → Date and Time (Samsung) or Settings → System → Date & Time (stock Android).
2. Disable Automatic date and time, wait 10 seconds, re-enable it.
3. Reboot.

Fix 2: Update Google Play System Updates

Android distributes time zone database updates through Google Play system updates, not OS updates. Go to Settings → Security → Google Play system update and check for pending updates — this is the most common fix when Android clocks show the wrong hour after a DST policy change.

Fix 3: Samsung-Specific Fix

On Samsung devices, also check Settings → General Management → Date and Time → Time Zone. If it shows a generic zone like "GMT-5" instead of a named city zone, tap it and select the correct named zone (e.g., "Chicago" for Central Time). Named zones receive rule updates automatically; offset-only zones do not.

Windows PC

Fix 1: Install the Time Zone Update

1. Open Settings → Windows Update → Check for Updates.
2. Install all pending updates — Microsoft distributes DST rule changes as cumulative updates.
3. Reboot after installing.

Fix 2: Manual Time Zone Adjustment (Temporary)

If the update isn't available yet and your clock is off by exactly 1 hour:

1. Right-click the clock in the taskbar → Adjust date/time.
2. Turn off Set time zone automatically.
3. Manually select the correct offset for your region.

Note: Switch back to automatic once the Windows update is installed.

Mac

Fix 1: Update macOS

Apple bundles time zone rule updates into macOS point releases. Go to System Settings → General → Software Update and install any available update.

Fix 2: Reset Time Zone Detection

1. Go to System Settings → General → Date & Time.
2. Unlock the padlock with your admin password.
3. Turn off Set time zone automatically using current location, wait 5 seconds, re-enable it.

Google Calendar and Outlook

Google Calendar

• Go to calendar.google.com → Settings (gear icon) → General → Time zone.
• If your time zone shows an incorrect UTC offset, switch to a different zone and switch back — this forces a refresh.
• For events that shifted: Google automatically adjusts event times when time zone rules change, but events created with a fixed UTC offset (not a named zone) won't update. Check those manually.

Outlook (Desktop)

1. Go to File → Options → Calendar → Time zones.
2. Confirm the current time zone matches your actual location.
3. If meetings look shifted, go to File → Office Account → Update Options → Update Now to pull the latest Office patches, which include time zone rule fixes.

Smart Home Devices (Alexa, Google Home)

• Amazon Echo: Open the Alexa app → Devices → Echo & Alexa → [Your Device] → Time Zone. Re-select your time zone even if it looks correct — this re-registers it with Amazon's servers.
• Google Nest/Home: Open the Google Home app → tap your device → Settings → Device Information → Time Zone. Reselect your zone.
• Smart plugs and schedules: Automations with hard-coded times (e.g., "turn on at 7:00 PM") do not auto-adjust. Edit each schedule manually after a DST rule change.

Prevention: Make Sure You Never Get Burned Again

• Always use named time zones (e.g., "America/Chicago"), not UTC offsets (e.g., "GMT-6") — named zones receive automatic rule updates.
• Keep automatic updates on for all devices — DST rule changes arrive as system-level patches.
• Audit recurring calendar events after any DST change — check the first occurrence of each recurring event to confirm the time is still correct.
• Set a reminder for the first Monday after any announced DST policy change to verify alarms and scheduled automations.

Bottom Line

Permanent daylight saving time sounds simpler than the biannual clock change — but the transition period creates real device headaches. The root cause is almost always an outdated time zone database. Update your OS, resync network time, and verify named zones are selected rather than raw UTC offsets. Five minutes now saves you from a missed meeting or a misfired alarm later.

Which device gave you the most trouble? Drop it in the comments — we'll add a targeted fix.