1120615 - [Alarm] Alarm not firing during the sleep mode

Status: RESOLVED DUPLICATE of bug 1163325

(Firefox OS Graveyard :: Gaia::Clock, defect)

Description

[Yeojin Chung [:YeojinC]]

Description:
The alarm does not fire when the phone is on the sleep mode. When the user presses the power button to wake up the phone, the alarm goes off.
   
Repro Steps:
1) Update a Flame device to BuildID: 20150112010228.
2) Set an alarm to fire.
3) Wait till the phone goes into the sleep mode.
  
Actual:
The alarm does not go off when the phone is on the sleep mode. The alarm goes off when the user presses the power button.
  
Expected: 
The alarm goes off at the right time while the phone is on the sleep mode.
  
Environmental Variables:
Device: Flame 2.2 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20150112010228
Gaia: f5e481d4caf9ffa561720a6fc9cf521a28bd8439
Gecko: bb8d6034f5f2
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a1 (2.2)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
  
Repro frequency: 4/12
See attached: video clip
http://youtu.be/HeHbBJBPdtI
(I was unable to get a logcat file due to low repro rate.)

Comment 1

[Yeojin Chung [:YeojinC]]

This issue does NOT reproduce on Flame 2.1.

Result: The alarm goes off during sleep mode properly.
Repro rate: 0/7

Environmental Variables:
Device: Flame 2.1
BuildID: 20150112001215
Gaia: 1975241ac29f723479e6c60b2bf74ebed54da91a
Gecko: 0863fe4b75c3
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 34.0 (2.1)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 2

[Yeojin Chung [:YeojinC]]

FYI, I had a SIM in my device. I was able to reproduce this issue with both internet connection on and off, and both Date & Time > Set Automatically on and off. The alarm would never go off until the user presses the power button, or goes off about 2 minutes later than the set time.

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

Nominating this 2.2? since the alarm will be used by a large number of end users and it must work properly.

We won't be able to get a reliable regression window here since the repro rate is so low.

Comment 4

[YouniS Bensalah [:younishd]]

I have reproduced this bug several times on master branch.

Device: ZTE Open C
BuildID: 20150113192509
Platform: 37.0a1

Comment 5

[Marcus Cavanaugh [:mcav]]

If anyone has success grabbing a logcat when this reproduces, we'll have a much better chance of tracking the root cause. I'll try to repro this today.

Comment 6

[Marcus Cavanaugh [:mcav]]

I attempted to reproduce this 10 times today, unsuccessfully, with varying situations:

- Clock app open, clock app closed
- Other apps running using memory (MemBuster app allocating lots of memory)
- Allowing the screen to timeout manually (per the YouTube video); manually shutting the screen off beforehand

Device: Flame
Build: Gaia master from last week; latest full-flash from last week
Repro frequency: 0/10

Comment 7

[Dylan Oliver [:doliver]]

Yeojin or Younis, can you try to reproduce and get a logcat to attach to this bug. At this time we have not been able to reproduce. 

Clearing nomination as it's not blockable at this time. Please renominate if you can get a log and we'll re-evaluate.

Comment 8

[Yeojin Chung [:YeojinC]]

I could still reproduce this bug. However, I was never able to reproduce this issue when the device was tethered, so I could not get a logcat after attempting multiple times.

Device: Flame 2.2 (Repro rate: 2/5)
BuildID: 20150201063054
Gaia: d6141fa3208f224393269e17c39d1fe53b7e6a05
Gecko: be206fa2fb60
Version: 37.0a2 (2.2) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 3.0 (Repro rate: 1/5)
Build ID: 20150202042034
Gaia: 4171327fce4803c52b2fae8071b114a70a3a68a7
Gecko: 3bf7ed413e87
Version: 38.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0

Comment 10

[Rhys Jones]

Attachment: logcat-2015-07-09-10-02-19.zip

Attaching a logcat I captured when my alarm failed to fire.

Alarm was set for 10am, but did not fire. Received a text message at 10:02am which woke the phone, alarm fired.

Using a Flame on 2.2, I think all the phone data is included in the logcat? If not happy to supply.

Comment 11

[Chuck Norris]

I got the same problem on my ZTE Open C.
Alarm doesn't fire up in sleep mode.
clock app opened or closed, the problem occurs.
Bug Frequency: every morning (grrr)

DEVICE: ZTE Open C
Build ID: 20150718125933
Platform: 37.0
SYSTEM VERSION: 2.2.0.0 prerelease

Comment 12

[omega_canta]

+1 here.

I have a Hamachi (Alcatel One Touch Fire).
I've been testing FFOS versions since last year. That means, a bunch of builds. This problem started with v2, and persists on V2.5 today. V1.x did not had this problem.

It seems to be something regarding the way the phone goes to "sleep" (i don't know the technical name, what happens when you press the power button once and the screen turns off).

Similar problem occur with the ringer (when somebody call me), sometimes it doesn't rings, and alert messages (like the ones when you receive an SMS message). All this while the phone is in sleep mode, and all this since v2.


Had to buy an alarm clock because of this bug :(

If anybody can post a link explaining how to do it, i'll be happy to try to get a log from the phone during the problem.