1144185 - [Lockscreen] Lockscreen turns itself on after device fades to black after reaching timeout limit when charging phone

Status: RESOLVED WONTFIX

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

Description

[Joshua Mitchell (Inactive)]

Attachment: logcat_20150317_0858.txt

Description:
When the device hits the alloted time for timeout it will fade to black and should stay black. Currently, the device is inconsistently turning the screen back on to show the lockscreen immediately after fading to black.

This could be related to bug 1116368

Repro Steps:
1) Update a Flame to 20150317010203
2) Plug device in so it is charging
3) Allow the device to timeout

Actual:
screen turns back on for 9-15 second lockscreen timeout

Expected:
Device will stay on blackscreen after timeout limit reached

Environmental Variables:
Device: Flame Master
Build ID: 20150317010203
Gaia: 4868c56c0a3b7a1e51d55b24457e44a7709ea1ae
Gecko: 436686833af0
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 39.0a1 (Master)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0


Repro frequency: 10/20 (for 3.0)
See attached: logcat

Comment 1

[Joshua Mitchell (Inactive)]

This also reproduces on 2.2 (repro rate - 5/20) and 2.1 (10/10) 

Please ignore the "This could be related to bug 1116368" statement in comment 0, as that can no longer be true since it is not present prior to 2.2 

Device: Flame 2.2 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150317002504
Gaia: d0e09d5e6367e558824f9cbf691da99cedf63037
Gecko: 793d61bb0bd4
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 37.0 (Master)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Device: Flame 2.1 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150316001204
Gaia: 90f4ca618048b608c8e663d3e1d84781cfa719a8
Gecko: 65e67896e813
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 34.0 (2.1)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

------------------------------------------------------------------------------------
This issue does NOT reproduce on 2.0 

Device: Flame 2.0 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150316000201
Gaia: 896803174633fc6acd3fd105f81c349b8e9b9633
Gecko: 2fc0c40fd074
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 32.0 (2.0)
Firmware Version: v18D-1

Comment 2

[Peter Bylenga [:PBylenga]]

NI on component owner for nomination decision and assignment.

Comment 3

[Gerry Chang [:gchang]]

Not sure if this is caused by unstable power source.

Comment 4

[Gerry Chang [:gchang]]

Can you also attach a video link?

Comment 5

[Joshua Mitchell (Inactive)]

QA-Wanted: please get a video, thanks

Comment 6

[Yeojin Chung [:YeojinC]]

Here's the link to the video: 
https://youtu.be/epJw-AmTbvA

Note:
I was able to reproduce this issue only when the device is being charged via a computer. I was never able to reproduce when the device is plugged into the power source directly from a wall outlet.

Device: Flame Master (KK, 319mb, full flash)
Build ID: 20150319010201
Gaia: c39e15f631de80c69467fda0d4ea0bcda9e194ca
Gecko: cf1060d8ce9f
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 39.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0

Comment 7

[BMO Automation]

Firefox OS is not being worked on