View Single Post
Old 10-05-2016, 07:40 PM   #287
Alan_S
Evangelist
Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.Alan_S ought to be getting tired of karma fortunes by now.
 
Alan_S's Avatar
 
Posts: 446
Karma: 1084584
Join Date: Aug 2007
Location: Sisak, Croatia
Device: Kobo Aura H2O, Kobo Aura ONE
Quote:
Originally Posted by tshering View Post
Edit: In version 02, I improved the script for option 2. Asking the time server is now about 8 seconds quicker than in the old script. The script has still to wait 10 seconds before the hardware clock can be synchronised. Usually one would not synchronise the hardware clock at this point, but at the time of powering off. Maybe we should consider doing this.
I was thinking a bit on this.

As I understand, there is no problem with synchronizing hardware with system clock. It can be done whenever and how many times we want.

It looks to me that best solution would be to synchronize hardware clock with system clock as soon as we set system clock (just in case anything goes wrong later) and additionally to synchronize it also when we power off device, to maximize long term clock accuracy.

In this way we get best from both options. And it shouldn't be a problem, as we can synchronize hardware clock whenever we want.
Alan_S is offline   Reply With Quote