Open Flohack74 opened 7 years ago
From @ernesst on October 7, 2017 2:0
The fixed might be this : https://git.launchpad.net/~ci-train-bot/repowerd/+git/repowerd-ubuntu-vivid-2276/commit/?h=repowerd-ubuntu-vivid-2276&id=6143d6a2d90df981d97de556fbe392e8ef617820
From @torchedesc on October 13, 2017 13:40
Did you select a day? I thought I had thrown same issue, but my alarm never went off because I didn't select a day.
From @dark-eye on October 13, 2017 16:16
@torchedesc @ernesst If the issue is that you didn't select a day it might be a clock-app issue as the date of the next alarm date is determined there and not selecting a day should set the alarm to be a single shot to by fired on the selected time next occurrence.
If it`s reproducible please open an issue on the clock-app.
Thanks,
From @wayneoutthere on October 17, 2017 16:39
This link doesn't work above: https://git.launchpad.net/~ci-train-bot/repowerd/+git/repowerd-ubuntu-vivid-2276/commit/?h=repowerd-ubuntu-vivid-2276&id=6143d6a2d90df981d97de556fbe392e8ef617820
From @wayneoutthere on October 17, 2017 16:58
hey everyone... I might have figured out the bug here. I tried all of the above but it didn't work (well, I couldn't get the link above) and it seems that as long as I wipe out the default word 'alarm' in the field where you give the alarm a name, and replace it with anything else, then when i press save everything works. >However, if i leave 'Alarm' in the label field then the alarm doesn't save and... no surprise, doesn't wake me up. Hope this helps.
From @ernesst on October 20, 2017 16:43
I can confirm after a week of test the device wakes up properly when all the days are selected.
Can we move the bug to clock-app ?
From @wayneoutthere on October 20, 2017 20:43
I'm fine with that. Move it wherever you want but it seems there are two things to test: the days selected and the default name in the alarm label field,.
Hey @ernesst,
After creating an alarm with no selected days does it appear in the alarm list? does the estimated time for the alarm correct?
Thanks,
Yes it appears in the alarm list and give the estimated time.
Hey @ernesst, I can seem to recreate it on my device (Meizu pro 5) i assume this is a device specific issue (as the tag say it is :)) I'll have to ask the community to help here and narrow down the cause of this issue.
If anyone can recreate this issue it and find the cause please create a PR of the fix.
From @ernesst on October 7, 2017 1:43
A legacy bug, that seems still present on ubports image.
Please see https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526 for more information
Copied from original issue: ubports/ubuntu-touch#288