Closed
Bug 1037969
Opened 11 years ago
Closed 11 years ago
Gaia Timer overcooked my bacon
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1037079
People
(Reporter: kats, Unassigned)
Details
The timer in the Gaia clock app doesn't seem to go off properly. I was using it (Flame device, local master build) to time bacon and after the timer reached 0 nothing happened. The screen was off at the time so I didn't notice but when I turned the screen back on and unlocked the device the timer was sitting at 0 with the "pause" and "cancel" buttons still there. The vibrate/sound settings were set to default and the timer volume was maxed out, so I expected either some sound or vibration.
Another time I tried using it (same STR) and when I unlocked the screen it showed 37 seconds on the clock, but it wasn't counting down any more. I think the timer time had actually elapsed but the display hadn't updated, so it was internally at 0 seconds but it still showed 37 seconds.
|
Reporter | |
Updated•11 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
|
||
Comment 2•11 years ago
|
||
Sadly, this is a recent system-level regression that causes mozAlarms to not fire properly.
Sorry about your bacon. :(
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
|
||
Updated•11 years ago
|
blocking-b2g: 2.1? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•