REPRODUCIBILITY: Always
OS VERSION: 5.2.0.17
HARDWARE: Jolla Phone 2026
UI LANGUAGE: Portuguese (European)
REGRESSION: Unknown
DESCRIPTION:
The alarm picker, under some conditions, has inconsistent controls (the analog and the digital control), i.e. in my case (BST right now), the controls are off by one hour. (see image)
So to set alarms I have to make sure to take that into consideration.
Note that on the alarm list the hours are correct.
Yes, the only place that does not follow localtime (i.e. my timezone Europe/Lisbon) is that picker. Curiously tried with the timezone changed to Europe/Madrid and that one is fine.
Europe/Lisbon timezone is equal to UTC. But Portugal has summertime so today is UTC+1 (this w/o Azores). So it is hard to say the timezone is not correct when UTC is shown. So maybe in the definition of Europe/Lisbon the summertime is missing?
Is there a difference between the clock on the startscreen and the time picker in the alarm setting?
I know what is my timezone and its relation with both UTC and DST changes. Like I mentioned on the bug description that specific picker is the only instance on the entire SailfishOS interfaces (as far as I know) that show time that is incorrect. The clock on the start screen is correct, the clock on the Alarm landing pane is correct (i.e. where it shows existing alarms), the clock on the lock screen is correct, the clock on appsupport (i.e. the android container) is correct.
And if you look at the image it’s pretty obvious that while the “clock” hands show 9:00 (this is correct timezone+dst aware control), the digital display shows 10:00 which is incorrect.
I also initially missed the fact that the clock hands and the digital readout differ. (That’s hilariuos, except when you need your alarms to work, of course ).
Would you mind updating the bug report to stress this discrepancy? I think that would help developers understand and fix the issue.
Curious, changing it to anything else works fine, London (same timezone) and even Madeira (also the same timezone, and also in Portugal) work perfectly.
In case another confirmation is needed… I am in Lisbon timezone, and indeed: a new alarm is created correctly according to the analog clock, but the numerical value displayed in the picker is off by 1 hour.
Another portuguese user here, I confirm the bug is present in C2 (5.1.0.11) and in P2 (5.2.0.17). In Portugal, Lisbon the hour number is 1 hour higher than the analog clock, changing to UK, London it shows correct. Alarm sounds off at correct time.
).
