View Single Post
Old 10-01-2016, 07:27 PM   #267
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.
Why we wouldn't synchronize hardware clock immediately?

When I set time, it is correct time. It should be reflected with hardware clock also. I had problems with clock being late 3 minutes, I first noticed this after crash. This can also happen to other people, having crash, need to forcefully reset device or something similar.

In such case clock wouldn't be synchronized and therefore not correct.

From my point of view, I want clock as soon as possible to run correctly.
Alan_S is offline   Reply With Quote