Closed
Bug 1082433
Opened 10 years ago
Closed 10 years ago
[B2G2.0][Alarm] alarm rings after some delay (3-10Sec) after power on the device
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1086598
People
(Reporter: srinivasvemula.mtech, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
Steps to reproduce:
1. Tap [Clock] icon on Home screen.
2. Tap [Add alarm] icon at the upper right of the screen.
3. Tap [Time] to set alarm time.
4. Set the alarm time the time when 2 minutes after now.
5. Tap [Done].
6. Power off the phone.
7. Power on the phone.
9. Wait for the set alarm ring.
Actual results:
The alarm rings about 10 seconds later than the set alarm time.
Expected results:
The alarm should ring at the set time
Reporter | ||
Comment 1•10 years ago
|
||
Issue is not reproducing when clock app is running.
OS: All → Gonk (Firefox OS)
Hardware: All → ARM
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(selin)
Flags: needinfo?(nhirata.bugzilla)
Flags: needinfo?(fabrice)
Reporter | ||
Updated•10 years ago
|
Summary: [B2G2.0][Alarm] alarm rings after some delay (3-12 Sec) after power on the device → [B2G2.0][Alarm] alarm rings after some delay (3-10Sec) after power on the devic
Reporter | ||
Updated•10 years ago
|
Summary: [B2G2.0][Alarm] alarm rings after some delay (3-10Sec) after power on the devic → [B2G2.0][Alarm] alarm rings after some delay (3-10Sec) after power on the device
Updated•10 years ago
|
Flags: needinfo?(fabrice)
Updated•10 years ago
|
Flags: needinfo?(selin)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(iliu)
Flags: needinfo?(epang)
Flags: needinfo?(ejchen)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(m)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(shchen)
Updated•10 years ago
|
Flags: needinfo?(shchen)
Updated•10 years ago
|
Flags: needinfo?(ejchen)
Updated•10 years ago
|
Flags: needinfo?(iliu)
Comment 2•10 years ago
|
||
Thanks for pointing this problem but please don't spam us ...
Although this may be clock app's bug, but to be honest, apps all rely on API exposed by Gecko (Gonk) and this may take time to find out the root cause, so this may not related to Gaia.
You have to attach your device info with clean steps first and make sure this bug can be reproduced on specific devices / versions. For this, you may need to set "qawanted" keyword for this bug to ask for QA's help.
After that, with enough knowledge, we can dig deeper about this problem. Hope this clarifies something for you. Right now, I would remove all ni? here and please think twice to ni? us the right people only after things are clear.
By the way, I mainly work on Settings app instead of Clock app ... =_="
Flags: needinfo?(nhirata.bugzilla)
Flags: needinfo?(m)
Flags: needinfo?(epang)
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(m)
Reporter | ||
Comment 3•10 years ago
|
||
This issue reproduces not only first time after power on, but also whenever clock app is not running.This delay is occurring with registration process to open the application and to set the message handler callback.
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(m)
Resolution: --- → DUPLICATE
Comment 5•10 years ago
|
||
Hi Marcus, Could you please kindly update on this bug ?
Thank you very much !
Flags: needinfo?(m)
You need to log in
before you can comment on or make changes to this bug.
Description
•