Clock time wrong after a crash / random shut down
asked 2014-10-10 03:52:26 +0300
Had this quite often when a crash / random shut down occured. Luckily crashes got rare after installing the "paper fix".
Unfortunately I had a crash short time after the 1.0.8.21 update. The clock time was off by nearly one hour after the crash what I didn't realised until next day when I missed an event in the morning :-(
The wrong clock time problem happened to me quit often also with previous crashes. Some times the clock was off by days.
My network provider doesn't support automatic time updates via GSM. And integrated NTP is not available.
Is a lithium cell connected to the CMOS clock? How could a crash or battery problem change the CMOS clock?
Same with mine. I once got mails from the future ("in 20 Stunden" in German, funny), so I think it's because a Jolla is a timeless piece of personal device, which can yesterday tell us what tomorrow happened. So, time is relative.
Robomike ( 2014-10-10 15:13:25 +0300 )editOk I saw this too after a crash my phone time was off by 4 minutes but luckily provider has clock sync support so it comes back.
copyninja ( 2014-10-14 12:05:55 +0300 )editClearly Jolla is the phone, The Doctor would use to call the TARDIS. =:o)
Back to topic: I never yet had this problem with mine thanks to the GSM network (Swisscom) supporting time updates.
Venty ( 2014-10-15 10:12:52 +0300 )editTime update is not an option for me. I use MEZ continously and never switch to DST and back, personal reasons. Due to synchronizing topics (OwnCloud etc.) I try to keep time zone the same on all devices. Network provider would sabotage me at this point. But I think it shouldn't be that hard to call a public ntp server during startup?
Robomike ( 2014-10-15 12:13:18 +0300 )editI've seen this as well today, the date was off by a week
kearnage ( 2014-10-19 00:46:26 +0300 )edit