- Device: Volla Quintus (algiz) - Channel: stable + release candidate - Build: 24.04-1.3 + 24.04-2.0 beta ### Steps to reproduce - turn WiFi off - turn mobile data off - write down date/time as currently displayed on the phone - turn phone off - keep phone off for long enough that the clock lag will be noticeable (e.g. a couple of hours) - turn phone back on - system clock will resume at the time phone was turned off ### Expected behavior - reasonably accurate date/time value is expected to be kept based on RTC - at power on, elapsed time since shut-down is taken into account based on current value of RTC ### Actual behavior - system clock only synchronises when NTP servers are reachable - current value of system clock is not written to RTC, causing time not to be preserved across "power off" periods - `systemd-timesyncd` falls back to setting clock to value of a preserved file timestamp during boot (hence going back to the time the phone was turned off) ### Logfiles and additional information In 'journal', right after powering up the phone, I found the following entries (collected on June 8, 2026, with the phone running 24.04-1.3/stable): ``` Mar 24 14:46:00 ubuntu-phablet systemd[1]: Starting timekeeper.service - Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices... [...] (clock jumps from Mar. 24 to Jul. 17 right at the next event) Jul 17 17:26:09 ubuntu-phablet systemd[1]: Finished timekeeper.service - Timekeeper is a utility to keep/restore RTC offset for Qualcomm devices. [...] Jul 17 17:26:09 ubuntu-phablet systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization... [...] (clock jumps from Jul. 17 to May 21 right at the next event) 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 [...] May 21 14:28:02 ubuntu-phablet systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization. ``` So it looks like the 'Timekeeper' service still does something even though the Quintus is not based on the Qualcomm chipset (seeing as the clock gets adjusted, although improperly). This apparently causes 'systemd-timesyncd' to detect the clock as jumped backwards, in which case it resets the clock based on a timestamp -- that basically returns it to the the time the phone was last powered up. The same behaviour has been observed after upgrading to 24.04-2.0 beta/RC. According to this page: https://devices.ubuntu-touch.io/device/algiz/, the RTC is supposed to be supported by UT on the Quintus, but it doesn't appear to be the case.