Closed Bug 811194 Opened 12 years ago Closed 12 years ago

Alarm doesn’t ring on time if the phone is allowed to suspend

Categories

(Firefox OS Graveyard :: General, defect, P1)

Product:
Firefox OS Graveyard
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 804702

People

(Reporter: timdream, Assigned: iliu)

Details

(Keywords: regression)

Yesterday, I set an alarm for 3 hrs and turn off the screen w/o killing clock app. The alarm doesn't ring on time; the alarm call screen only show up when I turn on the screen manually 8 hours ago. It is likely that fixes in bug 796255 is not complete. Adding qawanted to verify if there is still a problem on the latest trunk.
After discussing with Tim, we found out the alarm did fire actually! However, users weren't aware of that and missed to close/snooze it. When turning on the screen later, users will still see the ringing page (already popped up on time) which shows the current system time. Bug 804702 has already addressed this issue: we shouldn't hook up the displaying alarm time on ringing page to the current system time; otherwise, it would make users confused.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
blocking-basecamp: + → ---
should by fixed according to bug 804702 remove qawanted
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.