1181004 - [Flame][Window Management]Long press home button and hold during blue boot animation, then Task Manager overlay appears on lockscreen.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

Description

[Shally Li（leave from Mozilla）]

[1.Description]:
[Flame v2.2][Window Management]Long press Home button and hold during blue boot animation, then task manager overlay appears on lockscreen, and user can't unlock screen until restarting.

Found at: 21:04
Attach: logcat_2104.txt and Flame_v2.2.3gp.

[2.Testing Steps]: 
1. Restart device.
2. When blue friefox loading screen appears, immediatly (Important) long press the home button and hold.

[3.Expected Result]: 
2. The user is brought to the lockscreen without the task manager overlay.

[4.Actual Result]: 
2. The message "Your recent app windows show up here" appears over the lockscreen which results in device unavailability. 

[5.Reproduction build]: 
Device: Flame v2.2 (affected) 
Build ID               20150706002507
Gaia Revision          ea11f422b687a982f0a961c9aea7858066561707
Gaia Date              2015-07-02 23:37:50
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c0214b4c1ea0
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150706.035706
Firmware Date          Mon Jul  6 03:57:18 EDT 2015
Bootloader             L1TC000118D0

Device: Flame master (unaffected)
Build ID               20150706010204
Gaia Revision          dc6c18c0dea7af3c40bfff86c530fd877d899dc4
Gaia Date              2015-07-04 01:35:20
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/136c41fca853
Gecko Version          42.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150706.051656
Firmware Date          Mon Jul  6 05:17:08 EDT 2015
Bootloader             L1TC000118D0

Device: Nexus5 v2.2 (unaffected) 
Build ID               20150706002507
Gaia Revision          ea11f422b687a982f0a961c9aea7858066561707
Gaia Date              2015-07-02 23:37:50
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/c0214b4c1ea0
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150706.041056
Firmware Date          Mon Jul  6 04:11:15 EDT 2015
Bootloader             HHZ12f

Device: Nexus5 master (unaffected)
Build ID               20150706010204
Gaia Revision          dc6c18c0dea7af3c40bfff86c530fd877d899dc4
Gaia Date              2015-07-04 01:35:20
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/136c41fca853
Gecko Version          42.0a1
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150706.044857
Firmware Date          Mon Jul  6 04:49:16 EDT 2015
Bootloader             HHZ12f


[6.Reproduction Frequency]: 
occasionally Recurrence,7/10

[7.TCID]: 
Free Test

[8.Note]:
1.There is no HW-Home button on Nexus 5.
2.Flame master rate: 0/30.

Comment 1

[Shally Li（leave from Mozilla）]

Attachment: logcat_2104.txt

Comment 2

[Shally Li（leave from Mozilla）]

Attachment: Flame_v2.2.3gp

Comment 3

[Hermes Cheng (inactive after July 27, 2015)]

Sam, could you take a look?

Comment 4

[Sam Foster [:sfoster] (he/him)]

This was fixed once by a patch uplifted from master and verified on v2.2 in bug 1163169. Can we get a window to see where it regressed on v2.2 on Flame? Or was the original verification wrong and this was never actually fixed in v2.2?

Comment 5

[Shally Li（leave from Mozilla）]

Hi Sam,

    I know bug 1163169, its original repro rate is 10/10. After patch landed on 2.2, I verified it as pass (sorry for that it should be fail with a low frequency), but now, I find that I can repro this bug with a lower frequency (rate: 2/15) on the build I used to verify on bug 1163169 comment 22.  And I find that device will vibrate once after long pressing on home button, and then the bug may occurr. While on flame master build, device will not vibrate, so the bug can't be repro on flame master.

    With above information, I clear 'regressionwindow-wanted', because the patch on 1163169 did not fix the bug absolutely.

Comment 6

[Shally Li（leave from Mozilla）]

Attachment: Flame_v2.2_1.3gp

Hi Sam, 

    I think I can update a 100% repro STR that can apply for all cases(this bug and bug 1163169). The key STR should be the time that device vibrates, instead of firefox loading screen. 

The 100% repro STR:
  1. Restart device;
  2. Long press home button, when device vibrates for the first time(no matter where you are now, maybe the firefox loading screen, maybe the previous screen), loose your finger, and observe device after it restarts complestely.
  Note that: if you miss the opportunity of first vibration, you can't repro this bug.

Actual Result: 
  2. The message "Your recent app windows show up here" appears over the lockscreen which results in device unavailability. 


    The reason why I verified 1163169 as pass is that when I long press home button on firefox loading screen, the opportunity of first vibration is gone on: 20150527002504, which is the build I used to verify on bug 1163169 comment 22.
    However, I can repro this bug on firefox loading screen by using latest build since the first vibration opportunity happens on the loading screen.


Please see video: Flame_v2.2_1.3gp
In the video, the left device flashed build: 20150527002504, and you can see the vibration happened on the black screen whinch was previous firefox loading screen; the right device flashed latest build: 20150707162503, the vibration happened on the firefox loading screen.

Comment 7

[Sam Foster [:sfoster] (he/him)]

This is the kind of thing that bug 1094759 fixed - but that's a huge patch that is not useful for uplift/cherry-picking. We could probably find another way to head off this race condition - essentially avoiding responding to hold-home events until lockscreen and others have had a chances to initialize. It would be necessarily v2.2-specific. With that branch past code-freeze and this being something of an edge-case, I need to know what the priority is for a fix like that.

Comment 8

[Gregor Wagner [:gwagner]]

Josh, whats the status of 2.2? Do we only care about red-tai related bugs from now on?

Comment 9

[Josh Cheng [:josh]]

Hi Gregor, Sam, Shally and Hermes,
I do not think this is blocker and 2.2 already CCed. We only land security patches or critical regression after CCed and this one seems not any of above.

I do not think we need to take care of this unless this is requested by RedTai partner.
Please let me know if you have any concern. Thanks!