1116397 - [Midori 2.0]Screen content will disappear for a moment when press power on if disabled lockscreen.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Homescreen, defect, P2)

Description

[sync-1]

FFOS 2.0
 Mozilla Build ID: 20141019000201
 
 
 DEFECT DESCRIPTION:
 After disable lockscreen, and then press power off and on, screen content will disappear for a moment.
 
  REPRODUCING PROCEDURES:
 1. disabled lockscreen in settings, go to idle screen;
 2. press power off, wait for some seconds;
 3. and then press power on, you will find in homescreen all the app icons are disappear for a moment. -> KO
 
 BTW: If you stay on settings app in root page, you can reproduce this issue too.
 
  EXPECTED BEHAVIOUR:
 After press power on, homescreen should display normal without delay display.
 
  For FT PR, Please list reference mobile's behavior:
 
 Note: On Flame 2.0, it will reproduce 100% when plugin with USB.

Comment 1

[Wesly Huang (EPM)]

qawanted for Flame on 2.0, 2.1, and 2.2 w/ same STR (no USB plugged) to see if there is some design issue here.

Comment 2

[Guoqiang.CHEN]

Dear Wesly,

It can be reproduce on Flame 2.0 & 2.2, without plug in usb wire.

Comment 3

[Brogan Zumwalt [Inactive]]

Issue DOES occur on Flame 2.0, Flame 2.1, and Flame 2.2

With lockscreen off, powering off screen (and waiting for a few seconds) causes homescreen icons to be momentarily missing on screen power on. This occurs whether or not USB cable is plugged into phone.

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20150105000200
Gaia: 3c9bb36d9ade1a0acd5e1d6cbb5057be7f5ad484
Gecko: 93f5c85a1d31
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20150105001204
Gaia: 73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko: 05dd053f1d90
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20150105010205
Gaia: c2bf20d23851d5fda9f8f0ef0267db5f49152376
Gecko: 636498d041b5
Version: 37.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 4

[Wesly Huang (EPM)]

[Blocking Requested - why for this release]:

though not function break but indeed impact UX, consider 2.0 timing nom. to 2.1 for triage, if already too late for 2.1 then suggest to go for 2.2 instead.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

How long is the "temporary?"  1 second?  2 seconds? 1 minute?

Comment 6

[Brogan Zumwalt [Inactive]]

Around 1 second on the current 3.0, it seems a bit faster than earlier builds/branches

http://youtu.be/gnRASMJshI0

Device: Flame 3.0
Build ID: 20150218002006
Gaia: 82f286f10a41aab84a0796c89fbefe67b179994b
Gecko: 9696d1c4b3ba
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 7

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Based on the information, I don't think it's a blocker for 2.1; possibly uplift for 2.2

Comment 8

[Gregor Wagner [:gwagner]]

Kevin, anything we can do here?

Comment 9

[Kevin Grandon :kgrandon]

I have a feeling that this depends on bug 1034001, but I am not 100% sure. Depending on that bug for now and doing a needinfo on Alive to confirm that.

Comment 10

[Stephany Wilkes]

Triage agrees with Naoki's comment #7 and is not blocking based on that.

Comment 11

[(inactive after 6/18) Alive Kuo [:alive]]

This is due to gecko cannot immediately redraw the content when the app changes from background to foreground. We have nothing to do here - unless we want to darken the screen until the app is fully drawn - but that will cause additional UX problem because the user will think the power button malfunctions.

Comment 12

[Kevin Grandon :kgrandon]

Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.