UsageConfig - apply saved NTP/DVB time sync setting on startup#4346
Merged
Conversation
timesync notifier was registered with initial_call=False, so saved configuration was not applied after Enigma2 startup until the user changed the setting manually.
Member
|
I suggest this should be reverted as this is not a solution. See forum When it is set to 'NTP' and there is no 'NTP' time known (yet) when enigma2 starts-up the time will be in 1970... so recordings/timers do not start. You need to 'fallback' to DVB time in these cases. When enigma2 does start-up and the 'system' already as an appropriate time I'm afraid adding the non initial check was a good idea. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
timesync notifier was registered with initial_call=False, so saved configuration was not applied after Enigma2 startup until the user changed the setting manually.