fake-hwclock implementation #1886
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I noticed that when the camera boots, it starts with the firmware compilation time.
This causes problems when the device is not connected to the internet. When recording videos to a file, the system time is always the same at boot, which results in new recordings being concatenated into the same file instead of creating separate files.
Currently, the time is set in
S30customizer
from/etc/os-release
. I added a script that restores the system time from a saved timestamp file on boot and updates this file periodically. This ensures that the time at boot is set to the last known time the camera was powered on, although the restored time might be outdated.Personally, I don’t like the name
fake-hwclock
, but it’s called that on Debian systems, including Raspberry Pi. I would have preferred something likesw-rtc
instead.