Closed
Bug 861971
Opened 12 years ago
Closed 11 years ago
Alarm clock not reliable
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect, P1)
Tracking
(blocking-b2g:-)
RESOLVED
FIXED
blocking-b2g | - |
People
(Reporter: dpalomino, Unassigned)
Details
(Whiteboard: khepera_43782, IOT, Spain, Ikura)
Buildid "20130321070205", device: ikura
gecko commit: b5183c99228bdc5be33340e359efd1b4f0859e92
gaia commit: 577d13088ebdbd353d13910d3317e713a140415b
Alarm clock seems not to be working fine. Sometimes the alarm is reproduced at very different time than the time really configured.
Example:
- Alarm set up at 7.20h
- Alarm rings at 21.47h (??)
P1, nominated tef? Adding cert dep.
Updated•12 years ago
|
Whiteboard: khepera_43782 → khepera_43782, IOT, Spain, Ikura
Comment 1•12 years ago
|
||
Hi David,
The ringing time is really strange. I have not seem that before. Could you please use latest build version for the issue? We just found out a DST issue(Bug 849785) affect alarm.
OS: Windows 7 → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Comment 2•12 years ago
|
||
Please renominate if this reproduces.
blocking-b2g: tef? → -
Flags: needinfo?(dpv)
Reporter | ||
Comment 3•12 years ago
|
||
Hi,
We have no logs about this, but the issue really occurred. I think we cannot do anything more until logs were collected, but it there is any known issue or suspect what's the root cause for this, please let us know.
Thanks!
David
Flags: needinfo?(dpv)
Comment 4•12 years ago
|
||
It often happens to me too, FWIW. I don't get such extreme delays as in comment 0, but less than 10' is common (probably less than 5').
Comment 5•12 years ago
|
||
See https://bugzilla.mozilla.org/show_bug.cgi?id=860884#c9 btw. I think this might be a gecko bug potentially.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Comment 6•12 years ago
|
||
We are getting a lot of reports that alarms are not reliable on a Keon.
http://forum.geeksphone.com/index.php?topic=4796.0 (Spanish)
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 7•12 years ago
|
||
Recently, we just fixed Bug 866366, which might work for this issue.
Comment 8•12 years ago
|
||
(In reply to Gene Lian [:gene] from comment #7)
> Recently, we just fixed Bug 866366, which might work for this issue.
Btw, it just landed TODAY onto b2g18/b2g18_v1_0_1 and it works well on the Buri (Hamachi). I would appreciate if someone can help verify if it's also working on ikura (no one in Taipei office have that device for now).
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
I have the same issue on ZTE Open C with:
Version: 1.3.0.0
20141011095656 / release-zte
Git commit 2014-10-11 01:19:27
This is the current french official release for ZTE Open C. (FFOS_FR_ZTE_OPENCV1.0.0B03)
Alarm rang this morning at 4:12 am, when Alarm clock was set at 7:30 am (and Flight mode on).
It happens quite often.
You need to log in
before you can comment on or make changes to this bug.
Description
•