Skip to content

12:00AM is the worst before 30mins #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jxmked opened this issue Mar 29, 2025 · 0 comments
Open

12:00AM is the worst before 30mins #3

jxmked opened this issue Mar 29, 2025 · 0 comments
Labels
invalid This doesn't seem right

Comments

@jxmked
Copy link
Owner

jxmked commented Mar 29, 2025

Updating date every 12:00AM sometime fails depends on what time you turn on the device. It fails because... if the device seconds is ahead than RTC and the device time went 12:00AM meanwhile the RTC remains behind and the device went to sync the time. The device time went back to 11:59PM and the program prevent to sync the time with 30mins interval.

We have multiple solution and quick fix for this.
We can also sync the second but the device clock can be either faster and slower so this second might end up desync overtime.
We can also adjust/remove 30mins interval before the last time sync.
We can allow to sync within period of time.

@jxmked jxmked added the invalid This doesn't seem right label Mar 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant