Date & Time Issues after Sonoma Update / Rapid Battery Drain

Question

Date & Time Issues after Sonoma Update / Rapid Battery Drain

🕰️ **Experiencing Time Problems on Intel-Based Macs After Sonoma Upgrade?** 🕰️

Hello Mac users!

🙋‍♂️ Have you noticed any time-related issues on your Intel-based Macs after upgrading to Sonoma? 🆕 Some of us are encountering a peculiar problem where our Macs can't seem to keep their date and time settings in check. It's a bit frustrating! 🤨

🧰 To address this issue, some users have been running the command `sudo sntp -sS pool.ntp.org` to reset their time settings, but it's only providing a temporary fix. 😓

🤔 One user suggests trying out the default time source, **time.apple.com**, to see if that resolves the issue. Have you experimented with this? Did it work for you? Share your experiences!

🔄 For a few users, it's not just a minor time discrepancy; their Macs are jumping months and even years, as pointed out by another user. 😱 This can lead to scheduling and data integrity problems!

🕒 Another user mentions using **pool.ntp.org**, similar to the initial solution. However, the problem still lingers, raising questions about the root cause.

🤷‍♂️ One user wonders if setting the time and date automatically, as some users do, might be a contributing factor to this mysterious issue.

🙅‍♂️ Despite trying various solutions, one user confirms they are still experiencing the same problem. Is there anyone who's managed to find a solution to this issue?

🤞 A user adds that they've faced the same problem using **time.apple.com** on both 14.1 and 14.2. They also mention experiencing the issue on an M2 Mac, suggesting it's not exclusive to Intel-based Macs.

💡 Another user speculates whether the rapid battery drain issue associated with Sonoma could be connected to the time problem. Is there a hidden link between these two issues?

📞 Taking proactive steps, one user opens a support case with Apple to seek answers. We eagerly await their response to unravel this time-related mystery.

📣 A user encourages everyone to follow the lead of the user who opened the support case and report this issue to Apple. The more reports they receive, the faster we might see a resolution to this perplexing time problem.

Time is of the essence, and it's evident that this issue is affecting many users. Let's collaborate to find a solution and ensure our Macs keep accurate time once again! ⌛🖥️💬 #MacTimeIssues #SonomaBugs

Posted on Nov 8, 2023 7:45 AM

Reply

Answer 1

paka1

Level 1

12 points

Nov 27, 2023 8:35 PM in response to PirateLooks40

This is terrible. Time switched by years (2001), usually now returning back to Nov 16. I tried multiple workarounds with no success including switching time servers. The only bit that seems to work is to turn off auto sync and set the time manually via `sudo sntp -sS pool.ntp.org` or apple time server. Then after reboot time holds. It took me two days including wrongly issued `cron` jobs before I even noticed the time was off(!).

Reply

Answer 2

Dec 9, 2023 7:07 AM in response to benbabs

The previous command "sudo sntp -sS time.apple.com" didn't work permanently. Later, I discovered that this alternative solution is permanent solution :

Disable "Set Time and Date Automatically" from the system settings.
Run the following command in the terminal: sudo mv /var/db/timed/com.apple.timed.plist ~/Desktop ; sudo reboot
After rebooting, re-enable "Set Time and Date Automatically."

Reply

Answer 3

Dec 5, 2023 6:13 AM in response to PirateLooks40

I am experiencing the same issue where the my mbp' date continuously sets back by 3 months. The only workaround I've found is to run the following command in the terminal: sudo sntp -sS time.apple.com and then disabling the 'Set time and date automatically' option in the system settings.

Reply

Answer 4

Nov 13, 2023 3:18 AM in response to PirateLooks40

We find it by deleting the “localtime” shortcut file and rebooting it. You can find it in /etc/ directory. There is a chance it may fix it permanently

Reply