Open mymike00 opened 5 years ago
Oh, I just saw that in the indicator the time ia 8:00 and in the clock app it's 7:00, so probably it's a bug of the clock app...
The same problem is on Nexus 5 RC Build 2018-W50
Wow, nice that someone confirm this. I thought I'm the only one with this issue... also, I remember that this probably happens when I set the alarm at 7 am and after some weeks I switch it off (the alarm repeats every working day). then when I turn it on again it goes off at 8am instead of 7
Same problem for me on N5 RC 2018-W48 a few days ago
Confirm again: Happens for me on stable as well as on RC. When turning off and on the alarm for the first time an hour is added to it.
It happened to me on E5 RC 2018-W50 when editing an existing alarm, not always though.
Hmm it might be some kind of timezone offset calculation issue @mymike00 what is your time zone?
UTC+1 so yes, it's possible, since the offset of the alarm is one hour...
could it be associated with this error?
@Gabriele69 Does te restart also fixed the alarm time?
@Gabriele69 Does te restart also fixed the alarm time?
No. Unfortunately I realized this morning, when the alarm clock rang 1 hour late! The clock correctly marks the time (and coincides with what is indicated in the upper bar and in the circle on the Home). The alarm clock was set at 7.15 am, but turned on at 8.15 am!
I still think that this is an internal setting problem related to UTC (between Italy and the UK there is, in fact, one hour difference). But I do not know how to intervene to solve it (if not, trivially, setting the alarm at 6.15am!)
The only thing I see is that the clock did not automatically determine the location via GPS. I would not want it to depend on this and that the alarm - in the absence of location indication - will default to UTC
I don't know exactly how to reproduce this, but it's the second time I have and alarm set on the 7:00. the alarm goes off at 8:00 instead. if I have a look at the clock app I can see the alarm is set on the 7:00, when I tried to change the time the time picker had a small glitch, as the displayed value (7:00) was not the actually saved time. idk, but maybe it's just my device that recently is showing up some strange bugs... #979