Closed
Bug 1116740
Opened 11 years ago
Closed 11 years ago
[Flame][Lockscreen]The screen still stays on Clock view when a minute after we reset stopwatch.
Categories
(Firefox OS Graveyard :: Gaia::Clock, defect)
Tracking
(b2g-v2.0 wontfix, b2g-v2.1 wontfix, b2g-v2.2 unaffected)
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | wontfix |
b2g-v2.1 | --- | wontfix |
b2g-v2.2 | --- | unaffected |
People
(Reporter: jihao, Unassigned)
Details
Attachments
(2 files)
[1.Description]:
[Flame][v2.1][Lock Screen]The screen still stays on Clock view after we reset stopwatch and wait a minutes.
Attachment: logcat_flame_1246.txt and Stay_on_clock.3gp
Occurrence time: 12:46
[2.Testing Steps]:
Set up: Set Screen timeout is 1 minute.(By Default)
1. Open Clock.
2. Set an alarm to start 1 min later.
3. Tap Stopwatch item.
4. Tap Start button to start timimg.
5. Tap the Stop button while the alarm rings.
6. Switch to Stopwatch item.
7. Tap Pause and tap Reset button.
8. Wait a minute.
[3.Expected Result]:
8. The screen should enter suspend mode.
[4.Actual Result]:
8. The screen still stays on Clock view.
[5.Reproduction build]:
Flame 2.1 build:
Gaia-Rev 73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ea426e47bfc4
Build-ID 20141230001256
Version 34.0
Flame 2.2 build:
Gaia-Rev 322ef5116a5827a30c9a3cd9b842449a9c66a5b3
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/67872ce17918
Build-ID 20141230010205
Version 37.0a1
[6.Reproduction Frequency]:
Always Recurrence,5/5
TCID: Free Test
Comment 2•11 years ago
|
||
Hi Alive, could you help with this, thanks.
v2.2 doesn't have this problem.
Flags: needinfo?(alive)
Comment 3•11 years ago
|
||
The stopwatch will request screen wake lock while it is running. This is a clock feature. Closing.
Also, in the video you only leave the device with 10~sec. ANY user action will enlarge the idle timing.
Status: NEW → RESOLVED
Closed: 11 years ago
Component: Gaia::System::Lockscreen → Gaia::Clock
Flags: needinfo?(alive)
Resolution: --- → INVALID
Comment 4•11 years ago
|
||
verified with v2.1 and v2.2 have different results, reopen this issue
following comment 0 steps, v2.1 will never screen timeout
Gaia-Rev b04a8cb7b2482e0a44e6702b48c42283a00b5b1e
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/99cea2c818f6
Build-ID 20150105161204
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150105.200839
FW-Date Mon Jan 5 20:08:48 EST 2015
Bootloader L1TC10011880
following comment 0 steps, v2.2 will never screen timeout after 1 minute
Gaia-Rev 4ceeff19086b2a2955f044ad923dcfa63a293de3
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/912036eeb024
Build-ID 20150105160215
Version 37.0a1
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20150105.192724
FW-Date Mon Jan 5 19:27:36 EST 2015
Bootloader L1TC10011880
ni Marcus, could you help with this, thanks.
v2.1 and v2.2 have different results.
Status: RESOLVED → REOPENED
Flags: needinfo?(marcuscavanaugh)
Resolution: INVALID → ---
Comment 5•11 years ago
|
||
Sorry for typo on v2.2 description
(In reply to Mike Lien[:mlien] from comment #4)
> verified with v2.1 and v2.2 have different results, reopen this issue
>
> following comment 0 steps, v2.1 will never screen timeout
> Gaia-Rev b04a8cb7b2482e0a44e6702b48c42283a00b5b1e
> Gecko-Rev
> https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/99cea2c818f6
> Build-ID 20150105161204
> Version 34.0
> Device-Name flame
> FW-Release 4.4.2
> FW-Incremental eng.cltbld.20150105.200839
> FW-Date Mon Jan 5 20:08:48 EST 2015
> Bootloader L1TC10011880
>
> following comment 0 steps, v2.2 will never screen timeout after 1 minute
it should be: v2.2 will screen timeout after 1 minute
> Gaia-Rev 4ceeff19086b2a2955f044ad923dcfa63a293de3
> Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/912036eeb024
> Build-ID 20150105160215
> Version 37.0a1
> Device-Name flame
> FW-Release 4.4.2
> FW-Incremental eng.cltbld.20150105.192724
> FW-Date Mon Jan 5 19:27:36 EST 2015
> Bootloader L1TC10011880
>
> ni Marcus, could you help with this, thanks.
> v2.1 and v2.2 have different results.
Comment 6•11 years ago
|
||
The expected behavior is that the screen times out if the timer is not running. (When the timer is running, the screen should stay awake.)
It sounds like you're saying that this is broken in v2.1, but works correctly in v2.2. Since we cannot uplift a fix to 2.1, there is nothing more we can do. Please reopen if I don't understand correctly.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Flags: needinfo?(marcuscavanaugh)
Resolution: --- → INVALID
Comment 7•11 years ago
|
||
I don't think this is INVALID since it indeed a bug with v2.1
ni Bhavana to comment if we don't fix this in v2.1
Status: RESOLVED → REOPENED
Flags: needinfo?(bbajaj)
Resolution: INVALID → ---
Hi Mike,
We executed the steps in Comment #0 on Flame 2.2 when timeout are respectively set as “1min”, “2min”, “5min” or “10min”, no abnormity appeared . And when executing the same operations on Flame 2.1, this issue can be reproduced.
Flame 2.1 build
Gaia-Rev b04a8cb7b2482e0a44e6702b48c42283a00b5b1e
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/99cea2c818f6
Build-ID 20150106001308
Version 34.0
-------------------------
Flame 2.2 build:
Gaia-Rev b77e0d56d197e0ee02d801a25c784130d888c9db
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/2a193b7f395c
Build-ID 20150106010234
Version 37.0a1
Flags: needinfo?(mlien)
Updated•11 years ago
|
Flags: needinfo?(mlien)
:ktucker, please verify this bug on master. Please also determine if the bug is a regression from 2.0 to 2.1.
Flags: needinfo?(ktucker)
Comment 10•11 years ago
|
||
This issue does NOT reproduce on Flame 2.2.
Result: The screen times out after 1 minute.
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Full Flash)
BuildID: 20150108010221
Gaia: d4dac29613076bdba3cb8adc217deadb08a2ac20
Gecko: 70de2960aa87
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
=========================================================
This issue DOES reproduce on Flame 2.0 and 188-1 Base Image (2.0).
Result: The screen does not time out after 1 minute.
Device: Flame 2.0 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20150108000200
Gaia: 31d6c9422cd0a8213df9f96019c9ab7168ec3ab3
Gecko: 7c7daab470fb
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
Flags: needinfo?(ychung) → needinfo?(ktucker)
Keywords: qawanted
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 11•11 years ago
|
||
Given QA's latest testing I don't think we need to block 2.1 on this so clearing the NI.
Flags: needinfo?(bbajaj)
Comment 12•11 years ago
|
||
refer to comment 10 and comment 11, mark as WONTFIX
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•