Thread: Firmware 5.10.2
View Single Post
Old 01-30-2019, 09:04 PM   #55
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Sol Arkite View Post
I want to report that my clock changes periodically on my PW2. After I restored the device and started over on the updated 5.10.2 (I’m holding off from 5.10.2.1 til I hear more) I noticed after I was using koreader that the clock was again not of the correct hour or minute. Not at all sure if it related to using koreader or some other hack or perhaps just buggy firmware. On the bright side, after the restore and hotfix, my battery life and indexing are working great. I wish I knew if 5.10.2.1 if was a correction for this problem or some test to foil the jailbreak or whatever it is correcting.
P.S. I’m still using the KUAL kindlet in my Documents folder of my PW2 and it doesn’t seem to have any problems with that.
Linux employs two clocks.
A software clock and a hardware clock.
The software clock is what you see and if it was correct before the update, that still doesn't mean that the hardware clock was correct.
It could well be that only the software clock had been set (the "normal" thing done by user-land setting).
It takes a special, system level, command to set the hardware clock from the software clock.
If never done, then the hardware clock might be anything.


When you updated the device, you also restarted the Linux kernel.
As part of its start-up, "knowing" that the hardware clock was the master system reference, it set the software clock to that date/time.


And if the hardware clock had been wrong (but hidden from view) before the restart, how you could see the wrong setting because the restart made the visible, software, clock the same.


Ref: https://www.gnu.org/software/coreuti...tting-the-time


There are several ways that both clocks can be set to the correct and identical time.
My date/time KUAL extension is one of them - it corrects both clocks to match the International date/time server network.
See the documentation included with the KUAL extension.
knc1 is offline   Reply With Quote