Closed Bug 1017873 Opened 10 years ago Closed 6 years ago

[B2G][Settings]Screen Timeout set to 1 minute doesn't activate for at least nine seconds after 1 minute

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(b2g-v1.4 affected, b2g-v2.0 affected)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected

People

(Reporter: mclemmons, Unassigned)

References

(
URL
)

Details

(Whiteboard: [2.0-flame-test-run-1]) 

User opens Settings App and Select "Display" option found under the Personalization section. Select Screen Timeout and choose 1 minute. Timing the timeout extends beyond 1 minute. The screen dims around the 1 minute mark but the timeout doesn't occur until roughly 1 minute 9 second mark. 

Prerequisites:
1. Have a stopwatch nearby

Repro Steps:
1) Update a Flame to BuildID: 20140529040201
2) Tap Settings App, select display option and choose screen timeout to 1 minute
3) Observe device screen while a stopwatch has been activated

Actual:
Screen timeout occurs at approximately 1 minute nine seconds – screen dims at around 1:01 but device screen goes black at 1:09.

Expected:
Timeout occurs close to or at 1 minute mark consistently


Notes:
Repro frequency: (5/5, 100%)
Link to failed test case: None 
See attached: video clip = https://www.youtube.com/watch?v=XnixEFDWbwY

2.0 Environmental Variables:
Device: Flame 2.0 MOZ
BuildID: 20140529040201
Gaia: 4142df90c71abdc1e3a87cd37dff1a22d5e38b34
Gecko: 1e712b724d17
Version: 32.0a1
Firmware Version: v10G-2
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
This issue reproduces on Flame 1.4, Buri 1.4, OpenC 1.4, and Buri 1.3 following the STR from Comment 0. On each device/build, the timeout didn't occur until roughly the 1:09 to 1:10 mark. 

1.4F Environmental Variables:
Device: Flame 1.4F
BuildID: 20140529000204
Gaia: 7bc1c15c67661a0b8e35f18f15a9d03d1d2cfcd5
Gecko: 2181cac4d0fc
Version: 30.0
Firmware Version: v10G-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140529000204
Gaia: 7bc1c15c67661a0b8e35f18f15a9d03d1d2cfcd5
Gecko: 2181cac4d0fc
Version: 30.0
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

1.4 Environmental Variables:
Device: OPENC 1.4
BuildID: 20140529000204
Gaia: 7bc1c15c67661a0b8e35f18f15a9d03d1d2cfcd5
Gecko: 2181cac4d0fc
Version: 30.0
Firmware Version: US-Ebay P821A10v1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140529024024
Gaia: 5bd226b03a2d63dfe9df204f7c0afb9984e8fd42
Gecko: 42ef074f380f
Version: 28.0
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.