Hey, we are aware of this issue and hope to be able to work on a solution soon.
All persons in the team who use FP Open have the same issue…
I can’t say if the fix will come in 17.01 or 17.02, because we have some other stuff that needs to be done first.
Sorry to keep you waiting!
Many Thanks for the solution. I have successfully quickfixed the problem without using the closed source app Clock_Offset_Fix_2.2.apk like you mentioned in your later post https://forum.fairphone.com/t/fp-open-os-clock-resets-after-reboot/17635/70.
Here is my short description for building the two necessary scripts manually as alternative to the second point of your description:
#!/system/bin/sh
expr `date +%s` - `cat /sys/class/rtc/rtc0/since_epoch` >> /data/media/rtc_offset
chmod 644 /data/media/rtc_offset
#!/system/bin/sh
[[ -f /data/media/rtc_offset ]] && /system/bin/toolbox date -s $(expr `cat /data/media/rtc_offset` + `cat /sys/class/rtc/rtc0/since_epoch` | awk ’ {print strftime("%Y%m%d.%H%M%S",$1)} ’ ) && exit 0
P.S.: Nice to hear that the bug will be fixed soon.
A post was merged into an existing topic: FP2 - Change date “your fairphone since” lockscreen
2 posts were merged into an existing topic: FP2 - Change date “your fairphone since” lockscreen
This bug should be solved in todays update of Fairphone Open.
Cool, looking forward to that. 
(As of now, it isn’t out yet, is it? The updater doesn’t display that release and I can’t see it on https://code.fairphone.com/projects/fp-osos/user/fairphone-open-source-os-downloads.html either.)
For the technically inclined 
(and as diverse approaches have been discussed in this thread), can you give some insight on how this was fixed? (Maybe with a link to the relevant source changes.) That’d be much appreciated.
I’ll ask the devs. If it is not to much work, I am sure they will post it here. But it might be a while because they are really, seriously very busy at the moment.
No hurry, I’m just curious.
I confirm that. For me this issue is fixed since FP Open OS 17.01.
Thanks a lot!
Clock is still bugged.
22.02.2017
Updated the phone to security patch 05.01.2017
23.02.2017, 09:22
Turned off wifi
Turned off cell data
Turned off phone
Took out battery
Wait 5 seconds
Put battery back in
Start phone
Boot successful
aaaand:
@%&#!
EDIT 23.02.2017 09:57
Turn off wifi
Turn off cell data
Reboot without taking out the battery
It works!
Learning: Clock forgets time if you take out the phone battery and cannot get it from the cell network. Clock requires an internet connection to set itself automatically."
My first phone was an Ericsson SH-888, from 1998, I believe. It was able to set its clock just by network radio.
Douwe, what does all this mean?
CVE-2014-9420, CVE-2015-3288, CVE-2016-3911, CVE-2016-6710, CVE-2016-7042, CVE-2016-8422, CVE-2016-8444, CVE-2016-8450, CVE-2016-8452, CVE-2016-8458, CVE-2016-9754, CVE-2017-0381, CVE-2017-0382, CVE-2017-0384, CVE-2017-0385, CVE-2017-0386, CVE-2017-0387, CVE-2017-0390, CVE-2017-0392, CVE-2017-0393, CVE-2017-0394, CVE-2017-0395, CVE-2017-0396, CVE-2017-0397, CVE-2017-0398, CVE-2017-0399, CVE-2017-0400, CVE-2017-0402, CVE-2017-0403, CVE-2017-0404
This is a list of security fixes.
I also can confirm that the clock bug is fixed since 17.01. Thanks to the devs.
Please can devs inform us technically which solution finally works?
It’s fixed for me now on 17.02. I skipped 17.01 because my FP2 was headless and lying in my furniture.
I guess they fixed the certificate/permissions issue I looked into some time ago. The app package was one of the Qualcomm’s blobs, so they might had to contact them (as blobs are closed-source). I don’t know.
Clock bug fixed for me too 
14.03.2017 13:46
Turn off wifi
Turn off cell data
Take out battery
Wait 15 Seconds
Put battery back in
Start phone
Boot successful
Time stays correct!
Thank you devs!
