1226766 - After dismissing an alarm on the lockscreen, the display does not turn off after 10 seconds.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)

Description

[Martin Shuman [:Marty]]

Attachment: logcat_alarm-timeout.txt

Description:
If the user receives an alarm at the lockscreen, after dismissing it (Stop or Snooze), the display will not turn off after 10 seconds, as it is supposed to at the lockscreen.  Instead, the display will shut off according to the Screen Time-out configuration in Settings > Display.  This time-out is set to 1 minute by default, but can be configured to 2, 5, 10 minutes or Never.  This issue can increase battery drain.

Repro Steps:
1) Update a Aries to 20151120132248
2) Set an alarm to go off in one minute. Lock the device.
3) Wait for the alarm to trigger. Tap either Stop or Snooze
4) Do not touch the screen. Wait for the display to turn off.

Actual:
The screen takes a full minute to turn off after dismissing the alarm.

Expected:
The screen takes only 10 seconds to turn off.

Environmental Variables:
Device: Aries 2.6
Build ID: 20151120132248
Gaia: 94a821b49f4dca3f9321cd80e13c44c4a6696952
Gecko: ec628289d8b4ed310463a0729c3e60a7798dfcac
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 45.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0

Repro frequency: 8/8
See attached: Video (URL), Logcat

Comment 1

[Martin Shuman [:Marty]]

This issue DOES occur on the latest Flame 2.6 Nightly and 2.5 OTA builds.
The screen takes a full minute to turn off after dismissing the alarm.

Environmental Variables:
Device: Flame 2.6
BuildID: 20151120030231
Gaia: 94a821b49f4dca3f9321cd80e13c44c4a6696952
Gecko: 3835b568092ae3b71adc931d24928670ad7141a7
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 45.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0

Environmental Variables:
Device: Flame 2.5 OTA
BuildID: 20151120073427
Gaia: b7f130c36588e308784cd1b7c8a28585c9819076
Gecko: 589a9b96c5bc632bcc336d0543442983cc1f61dd
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0a2 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

***************************************

This issue does NOT occur on the latest Flame 2.2 build.
The screen takes only 10 seconds to turn off.

Environmental Variables:
Device: Flame 2.2
BuildID: 20151120032503
Gaia: 885647d92208fb67574ced44004ab2f29d23cb45
Gecko: 462d8e9208ea
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 2

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

I don't think this is a blocker but let's get a window here.

Comment 3

[John Thomas [:Johnt]]

Caused by changes made in Bug 1094759 

B2G Inbound Regression Window

Last Working
Environmental Variables:
Device: Flame 2.5
BuildID: 20150604012244
Gaia: e0fbadeb78a96137f071d9be7a47ef9fe882d17f
Gecko: 64ce149fabf1
Version: 41.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

First Broken
Environmental Variables:
Device: Flame 2.5
BuildID: 20150604020845
Gaia: c1ef854924f18357832ddcf98dc6c42391d5599e
Gecko: 4f7e7631e277
Version: 41.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Last Working gaia / First Broken gecko - This issue does NOT occur with broken Gecko
Gaia: e0fbadeb78a96137f071d9be7a47ef9fe882d17f
Gecko: 4f7e7631e277

Last Working gecko / First Broken gaia - This issue DOES occur with broken Gaia
Gecko: 64ce149fabf1
Gaia: c1ef854924f18357832ddcf98dc6c42391d5599e

Gaia Pushlog:
https://github.com/mozilla-b2g/gaia/compare/e0fbadeb78a96137f071d9be7a47ef9fe882d17f...c1ef854924f18357832ddcf98dc6c42391d5599e

Comment 4

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

Gregor would you know who would look at this now that Alive is inactive?  Seems to have been caused by the changes for bug 1094759.

Comment 5

[Gregor Wagner [:gwagner]]

Greg, can you take a look?

Comment 6

[Greg Weng [:snowmantw][:gweng][:λ]]

I guess it's not a LockScreen issue because it looks like a ScreenManager timout mistake. Will try to find out the root cause but don't know who knows ScreenManager better.

Comment 7

[Greg Weng [:snowmantw][:gweng][:λ]]

Project status changed.

Comment 8

[BMO Automation]

Firefox OS is not being worked on