[BUG] Clock time changes by itself

Thank you for your answer. Indeed, the issues might be different. I noticed the mention of hours, but I posted here as it seemed related.

Since I left the automatic update on, the clock seems to stay accurate. Without the option, I had to periodically adjust the time with a few minutes. Is there any debugging I can do to help more on this issue? I am wondering if it could be related in any way to periodic restarts I also have, as others reported. Maybe the internal clock fails from time to time? or doesn't update during crashes?

I don't know deeply the area so I have no idea about further debugging... Maybe @pekka-vuorela can shed some light.

Ok. Thanks. Until now, keeping Automatic Update set, the clock stayed on time. So, the problem is only when it runs by itself.

Clock drift is something more or less common in electronic devices, that is why we have mechanisms to fix it. Though it should not be _that_ bad.

It is indeed possible that the cellular network does not support time information (NITZ, see [1]).

@ilievdh: could you provide answers to the questions below to help us find out what's going on in your device:

• Do you have an active sim card in your Jolla?
• Do you have an internet connection set up (either mobile networking or WLAN)?
• Do you have automatic time update enabled?
• Is your time zone displayed correctly in the Settings app?
• What is the output to the terminal command "rpm -q timed-qt5 connman" ?
• What is the output to the terminal command "cat .timed/settings.data" ?

[1] http://en.wikipedia.org/wiki/NITZ#Carriers_supporting_NITZ

active sim - yes internet - both cellular data + wlan automatic time updated is off Timezone in Settings is correct "[root@Jolla ~]# rpm -q timed-qt5 connman timed-qt5-2.92-1.14.1.armv7hl connman-1.24+git48.1-1.5.1.armv7hl"

[root@Jolla ~]# cat .timed/settings.data cat: .timed/settings.data: No such file or directory [root@Jolla ~]# cat /home/nemo/.timed/settings.data cellular_zone = { value = "Europe/Sofia" }, format_24 = 1, local_cellular = 0, manual_offset = { value = 7200 }, manual_zone = { value = "Europe/Sofia" }, time_nitz = 0

I've added my timezone in /opt/alien/system/build.prop and on the next day there was a bigger offset on my clock from the real time. Then I've supposed that the timezone is calculated twice in the Alien Dalvik's VM. I've set "persist.sys.timezone=Etc/UTC" in /opt/alien/system/build.prop and since then I haven't have the issue with the clock anymore.