@gpatel-fr said:
@PhAndersson said:
the Pixel is able to get its time from the traditional GSM network
My memory is a bit dim on the subject and it's all hearsay anyway, however I remember I was said otherwise.
After investigating the issue further (see below), I believe you're right. I just assumed it would be possible because my old Nokia N900 running Maemo used to do it (silly me ).
It could be that the Pixel is able to save clock and this ability was lost on more recent phones.
Yes and no... Looking inside 'journal' on the Pixel, I found the following:
Jun 07 22:05:10 hatshepsut systemd[1]: Starting Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices...
Jun 08 08:18:54 hatshepsut systemd[1]: Finished Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices.
Meaning that RTC support seems to be linked to the Qualcomm chipset. The Quintus starts the same service, but as it uses the MediaTek Dimensity 7050 chipset, I guess retrieving the HW clock just (silently) fails.
Further down in 'journal' on the Quintus, I see the following entry that seems to confirm it:
May 21 14:28:02 ubuntu-phablet systemd-timesyncd[1401]: System clock time unset or jumped backwards, restored from recorded timestamp: Thu 2026-05-21 14:28:02 CEST
What I don't understand is that you said you had the same problem on your FP5, even though that one does have a Qualcomm chipset (a more recent one than the Pixel, obviously).
@PhAndersson said:
use your phone as alarm clock when you travel
not sure it's a huge priority - there is an obvious workaround: do not stop your phone during the night.
Right, yes, I agree -- probably not a huge priority. Still, it bothers me because it also means my log timestamps are untrustworthy most of the time, as are the time-related EXIF data fields of my pictures, etc. Accurate timekeeping on anything computer-like is one of the fundamentals in my book
So I guess I'll report it to Volla nonetheless and see where it leads...
