Odd issues with native UT Alarm clock. [Solved]

Opolork

Hi.

I make an alarm and I need to have it 2 hours ahead to get the correct alarm time to show. e.g. to get a 6am alarm - I need to choose 8am.

Also, when I try to change the Alarm type - it's stuck on 'UBports' - I want the 'Alarm clock' sound - the changes never remain. Creating a new alarm entry solved this.

I wanted to try a test alarm and when I do - it says the alarm will go off in 1d and so many hours & minutes.

AppLee

@Opolork Hi, what channel are you on ?
IIRC on RC channel there is an issues with timezone so the clock displays your real time but the system still uses UTC.

I'm not home so I cannot check.

Opolork

@AppLee said in Odd issues with native UT Alarm clock.:

@Opolork Hi, what channel are you on ?
IIRC on RC channel there is an issues with timezone so the clock displays your real time but the system still uses UTC.

I'm not home so I cannot check.

Hi AppLee. My timezone is set to 'Cork (Ireland) UTC+2' and to 'Automatically'.

Lakotaubp

@Opolork That's the problem. You don't need the +2 they are currently the same.

Opolork

My alarm says it's 11 hours away even though I know it's 9 hours away.

Must I unselect auto and manually select my timezone? I hope not as that'd be unfortunate in other ways.

Lakotaubp

@Opolork mine is set to automatic. Try re entering your time zone home city in system settings, time and date.
Edit: Arenyou actually in Cork? What happens if you put in say Dublin.

Opolork

@Lakotaubp said in Odd issues with native UT Alarm clock.:

@Opolork mine is set to automatic. Try re entering your time zone home city in system settings, time and date.
Edit: Arenyou actually in Cork? What happens if you put in say Dublin.

Yes, I'm in Cork (City). I put in Dublin and it too says +2.

I just tried Belfast and it says "UTC+0".

I've decided to set it to Cork, Munster and set the time & date manually. I don't understand where the +2 hours are coming from. Ireland is on the same time as GMT & UTC.

The weird alarm countdown amount is correct again.

Lakotaubp

@Opolork Thats what I wanted to test. How far from where you are before it sorts itself out. Odd that it's ok time wise with Belfast though.

Giiba

There is a known issue for the clock app that causes alarm and timer issues related to timezone calculations. It is some sort of logic error. Setting the timezone to '+0' is a solution to the issues, but means manually setting the time.

Opolork

@Giiba Thank you.