FP Open OS: Clock resets after reboot

M_Dammer · November 4, 2016, 6:29pm

Just to add that while travelling in Germany I was able to test the workaround under a different timezone and I can confirm that it works. The phone loads the correct time and timezone when rebooting it with WiFi off and in aeroplane mode. I have edited the text of the workaround accordingly.

z3ntu · November 17, 2016, 7:08am

I found two threads which are about the same thing. So apparently the problem is existant only in CAF trees…
http://www.96boards.org/forums/topic/cant-set-rtc-time-on-dragon-board/#gsc.tab=0

http://forum.xda-developers.com/showpost.php?p=62329019&postcount=3

Roboe · November 19, 2016, 3:56pm

Eureka! I think I just found the fix for the clock bug! Not a workaround anymore,

I found this BOARD_USES_QC_TIME_SERVICES := true build var, and added it to the BoardConfig.mk of the latest FP Open codebase. This should enable exactly the services we’ve discussed above Qcom devices have, but FP2 lacks for some reason.

I ran a nightly build, but it failed because of key issues on Ubuntu 16.04. I had to install Ubuntu 14.04 and a new build has been running for a few hours now.

When it finish, I’ll test if the clock works once and for all! Then I’ll probably push the patch to the FP Gerrit instance.

Edit: For future reference, it seems to require the libtime_genoff.so blob. Not a problem with the FP2, we already have that shipped,

Roboe · November 20, 2016, 9:34am

It didn’t work, . The build var is probably CyanogenMod-only. But in the search of how to enable time_daemon on Qcom CAF builds, I found an open source implementation from the guys of Sony Xperia Dev that could be useful for other ROMs:

JaTobias · November 22, 2016, 7:29pm

+1

Very annoying bug, a fix would be much appreciated.

Roboe · November 25, 2016, 9:01am

Ok, I’ve pushed the investigation forward. time_daemon and TimeService.apk are included in the build, as well as calling time_daemon restore on the init.qcom.rc (boot process). So, why are they not working?

I took a look at the system apps list and, surprise, TimeService (com.qualcomm.timeservice) is not installed. WTF! But it is on the system! Check it, /system/app/TimeService/TimeService.apk!

So I tried to debug by installing it manually. I opened Termux, and ran:

$ su
# pm install /system/app/TimeService/TimeService.apk
pkg: /system/app/TimeService/TimeService.apk
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]

¡Ahá! There’s the problem. A permission/signing key issue. But I cannot investigate further because, as you now, closed source code is not reviewable (I can’t see what the AndroidManifest.xml says, ). All this Qcom time thingies are part of the FP2 blobs.

PD: there’s useful Android permissions information at /data/system/packages.xml, FYI. Time info seems to be saved on a binary file at /data/time/ats_13

Smojo · January 5, 2017, 1:31pm

@Roboe any news about this?

I don’t won’t to follow the workaround with the non open spource app as well.

But the issue is there and I think it very annoying (especially while setting up a phone).
E.g.

certificate issue with e-MailI-providers and K9-Mail (any possibility to tell K9 to wait a bit before trying to get new mails the first time after reboot)
I would like to go on using my Pebble (/“Fibit”) Smartwatch (as long as it still works ) but the watch switch to factory mode because of this issue after each reboot.

For me it feels like that it takes about half a minut until the time is corrected.

Roboe · January 5, 2017, 1:45pm

DAVdroid failing because of invalid certificates is a common issue, too.

Nope, not any news. Eight months later, the bug is still unfixed. FP Open is a second-class citizen, from what we have seen.

Until your phone goes online and checks the time. If you never get online, then your phone is stuck at 1970.

Douwe · January 10, 2017, 3:40pm

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!

Antimailer · January 10, 2017, 5:32pm

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:

Alternative replacement of second point (“Open the “Clock Offset Fix” app …”):
create createoffset.sh:
#!/system/bin/sh expr `date +%s` - `cat /sys/class/rtc/rtc0/since_epoch` >> /data/media/rtc_offset chmod 644 /data/media/rtc_offset
copy to /sdcard1/<whatever_folder_you want>/TWRP/createoffset.sh
execute /sdcard1/<whatever_folder_you want>/createoffset.sh only one time (and every time after Hard Reset or Battery Removal)
create userinit.sh:
#!/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
copy to /data/local/userinit.sh
chmod 755 /data/local/userinit.sh
chgrp root /data/local/userinit.sh

P.S.: Nice to hear that the bug will be fixed soon.

paulakreuzer · February 9, 2017, 7:31pm

A post was merged into an existing topic: FP2 - Change date “your fairphone since” lockscreen

paulakreuzer · February 9, 2017, 7:30pm

2 posts were merged into an existing topic: FP2 - Change date “your fairphone since” lockscreen

Douwe · February 21, 2017, 12:29pm

This bug should be solved in todays update of Fairphone Open.

das_g · February 21, 2017, 1:08pm

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.

Douwe · February 21, 2017, 1:11pm

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.

das_g · February 21, 2017, 1:14pm

No hurry, I’m just curious.

Douwe · February 21, 2017, 3:27pm

It is out now
https://code.fairphone.com/contentx/2017-02-21_fairphone-open-17.01_release.html

maba007 · February 23, 2017, 6:54am

I confirm that. For me this issue is fixed since FP Open OS 17.01.
Thanks a lot!

technorati · February 23, 2017, 8:46am

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.

technorati · February 23, 2017, 8:13pm

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