FP Open OS: Clock resets after reboot

FP Open OS (and probably FP OS too) is indeed based on CodeAurora AOSP sources, :wink:. These are the official Qualcomm repos for OEMs with Android sources optimized and preconfigured for Qualcomm boards.

So, thanks to your useful link we now know that writing with hwclock doesn’t have to work on any Snapdragon board, and the bug is localized in the Android’s userspace service that should keep track of the delta between RTC and network time, :wink:


That leaves the obvious answer: When will we get a fix ? I am still waiting for version 16.07 - now probably 16.08. It looks to me as if they released the 1.5.1 FP OS, dropped the hammer and went on holiday.

Here’s a another clock-bug-victim. It’s one of those many really annoying bugs on my FP2 with latest OSOS.

And I’ve just made another observation:

Just having a mobile data connection isn’t enough to get the clock set after reboot. I really need to find a WIFI-Hotspot to connect - and (most interesting) it doesn’t matter if that WIFI-spot has internet connection or not.

So I made this WIFI-AP based on a raspberry pi with no realtime clock or internet connection or anything (basically with random time set), but connecting to that AP is enough to get correct time on my FP2. This is beyond logic…

edit: Another observation:

When using a captive-portal WIFI I wasn’t able to get time set at all. But it was in a foreign country with data roaming disabled so that might be linked somehow.

Once a mobile connection is established it can take a long time until the clock is updated. In the case of Wifi this happens faster. You can speed it up if you go to setup date/time-auto date/time and disable + enable again this setting. Then the clock will usually be updated immediately.


i have the same reboot date problem - travel in the past for free but i can not use the FP2 like that

Looking for a solution

Now with 16.07 being released without this being fixed can we have an update when this will be sorted ? And maybe a suggestion to the devs: I cannot see any purpose in keeping the RTC read only other than avoiding it ticking over before the 19th. January 2038 (the end of the Unix epoch). If this cannot be fixed in the system because its complicated, could you then please just rtc_write_enable=true in the next version - this will give even programs like TWRP that boot independently from the main system the proper time ?
Thanks a lot.


Hi. Interesting fact: my clock doesn’t reset to January 1st 1970 every time but the day changes everyday; January 2nd 1970 the second day after installation, then January 3rd 1970 the third day. I’ve only had my phone three days now, so I don’t know if it goes on… Never took the battery out since the installation though, wonder if it would start all over again!

It goes on. Even if you take the battery out. Regard from. The 18th January 1970!

Let’s hope this bug is fixed before the '80s! :smiley:


First reboot during the night! Result: as I haven’t heard my phone reboot and as I haven’t unlocked the sim card, the alarm clock did not ring… I don’t have many reboots, but this one was at a bad timing!
I will try not to set the time and date automatically for a while.


Same issue here! As I’m for working reasons sometimes in areas without wifi or network coverage I also experienced the alarm clock not working due to the clock reset after reboot. Disabling the automatic time settings didn’t worked for me, as the time was after reboot again in 1970 though I set the time manually before. Did I do something wrong? Is there a way to keep a manual set time after reboot?
And is it really true that, after I switch off my phone for the night a set alarm clock won’t wake me up (like FP1 did flawless)? Due to the mentioned reasons above I HAVE to save battery, so switching the phone of makes sense to me, but waking up on time for a job would also be more than helpful! :slight_smile:

Please note that switching off the phone and switching on again uses more power than a night in airplane mode - so it’s recommended to use airplane mode instead of switching off.


Same for me. I haven’t had another reboot during the night, so I just hope for the best!

Hi! I found a workaround for when I have important meetings: turn on wifi! The clock syncs directly with wifi, even if you don’t unlock the sim. I tried last night: turned on wifi, manual reboot, no sim-unlock, and the alarm clock woke me up.
Wouldn’t do it every day though, wifi drains the battery.
Edit: I’m writing about the alarm clock issue, many of you already had mentioned wifi of course!

1 Like

Reported on github as: https://github.com/Kwamecorp/Fairphone/issues/36

I don’t think anyone is actively maintaining that github. Reporting bugs here on the forum is sufficient.

Just noted the FP1 tags for that repository. Seems you were right.

thank you for your help paul. maybe this hint should be added to the batteries guide also as former FP1 user were used to turn off their phone automatically by FP1s system feature. And it has the benefit of a correct wake up too… :slight_smile:

Like most smart phones the FP2 cannot wake up for giving an alarm, because it has no hardware clock. So not only in regard to safe battery it makes sense to keep it on (I.e. In flight mode), but also for the alarm clock to work.

1 Like

This does not help a person like myself who does not want to have a microwave transmitter sitting by the bedside.