As root, systemctl --user restart lipstick restored alarms and settings starts up (as nephros said)…
Still to warm this topic. From my exprience the alarm bug still exists on Sony Xperia 10 II with Tampella 5.0.0.55. Restarting the homescreen solves the problem temporarily.
Jolla C2 seems to behave correctly.
2 Likes
This bug exists on Xperia 10 III as well, running 5.0.0.62. I have not had problems before, but recently alarm has stopped working. Last week it failed 3/5 times and so far this week 3/3. Also restarting homescreen or the phone does not seem to help. To me it seems that phone goes to some deep sleep mode, often it does not react to power button but pressing volume button wakes the screen.
I had this today. 5.0.0.67 on 10 III.
1 Like
Happens to me very often on SFOS 5.0.0 (and prior) using the Xperia 10 II.
I already had to by me an alarm clock just because of this issue.
Usually I set three alarms. Sometimes a subset does not work, at other times all configured alarms fail to start. The behaviour is always the same: The alarm does not work and stays enabled in the clock app.
Just got this exact issue, despite never having experienced it before today (coincidentally after reading this thread). Xperia 10V 5.0.0.67 v4b
Had this issue once, about 5-6 years ago when my device completely froze.
From that moment on, I use my good old Nokia N8 as an alarm clock, which has NEVER failed since 2010! 
It even activates when the device turns off from low battery…
My old Xperia 10 / SFOS 4.5.0.25:
Set countdown alarm (Clock app) 1 hour.
Rebooted device after half an hour.
Another half hour later, exactly at the time, alarm sounded!
BTW is this specific to Clock alarms or also Calendar alarms?
I have never noticed this but then I use my N900 as an alarm clock (alarm goes off even when switched off).
Is it a problem with the sound server (not hearing the alarm) or with the app itself (not triggering the alarm)? Is there any more info on this, apart from people reporting the issue?
AFAICS there are several potential causes for an alarm not going off, or at least not alarming someone. (The following list is more or less from memory of several forum posts, not thoroughly researched.)
- RTC support: Depending on device/port, RTC wake-up may be supported or not. No support means no waking up of the device for an alarm (from “deep sleep” or power-off). This is what makes N9(00) users wonder what’s happening, as RTC wakeups work fine on those old devices. Affected XPeria devices probably listed here.
- ngfd hanging: certain sounds may cause ngfd to “hang”, i.e. be in limbo, running but not doing its job. If it crashed, that would cause systemd to restart it, but that is not happening. So alarm does go off, Clock plays it as it is supposed to, but there is no sound.
Restarting ngfd solves this. - pulseaudio hanging. Lots of people report solving sound issues by restarting the pulseaudio service. PA may or may not actually be the reason here, possibly restarting the service fixes some other issue (like 2. above), causing the impression PA is to blame.
- Clock app forgetting scheduled alarms. There’s two issues here:
a. Sometimes the clock app does not load its configuration after boot, causing all scheduled alarms to not work
b. clock app does not load its configuration, and triggers alarms, but fails to deliver any alarms to the (audio?) subsystem.
My observation is that both 4a and 4b happen with increased probability if device is booted from “act-dead” mode (charging mode), but it can happen with a regular boot as well.
It seems to be some kind of startup race condition.
Restarting both timed-qt5 and Lipstick resolves this. - Silent gesture. When the option to silence alarms and calls by turning the device display-down is enabled, alarms can be completely silent if the device is display-down at the moment an alarm goes off.
So, depending of which of the above applies, Calendar alarms may be affected, or not.
This Bug report should only be about Number 4, but as it’s tricky see through it all, people comment on the others in here as well.
3 Likes
At least most of the time when my xperia 10 II stays silent and screen off when the alarm should go off it actually goes off if I wake the phone myself. So for me it looks like a wakeup issue.
Thanks for the link. One of these days I should just read ALL of docs.sailfishos.org.
So RTC seems to be lacking for Xperia 10, Xperia XA2, Xperia X and Gemini PDA.
That’s curious, because my XA2 sporting an older version of Sailfish OS (4.3.0.12 Suomenlinna) has never failed alarming me up in the same use scenarios. I use it as my backup alarmer with a 100 percent success rate.
Actually I definitely also remember using my previous XA2 as an alarm clock.
Isn’t it only from power-off? Or do you mean to say they are one and the same by some technicality?
Personally, i haven’t expected alarms on powered off phones to work since the dumbphone days.
The thing I was thinking of is the two kinds of power off an Xperia10(i, ii, iii) can do. Regular shutdown via OS, and long-press of volume+power til it vibrates three times.
I don’t know the difference in detail, but one seems to be a “lighter” variant of “off” than the other.
That version is pre-mandatory encryption right?
Could explain it, as an encrypted device can’t boot far enough to read a user’s alarm preferences (or sound config) so even if RTC wakeup works it’s of little use.
Yes sir. The XA2 is an unencrypted installation. I bought the device and the SFOS license in February 2019, flashed it with then-current version of SFOS and ever since have only OTA updated it, up to version 4.3 when I switched to a newer device (10 II) as my daily driver. This alarm bug is the very reason why I never updated the XA2 after that, as to my best perception the alarm bug had not yet hit that version and I wanted to keep it that way.