1013644 - [Homescreen] Dock slips down so icons only partially shown

Status: RESOLVED FIXED

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

Description

[Marcia Knous [:marcia]]

Attachment: 2014-05-20-15-36-13.png

Open C, while running:

Gaia   8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348
SourceStamp cb9f34f73ebe
BuildID 20140520040203
Version 32.0a1

STR:
1. During smoketesting today, I was able to get the device in the state shown in the attached screenshot.

Pressing an icon in this state seems to restore the dock to its normal position.

Adding steps-wanted - will try to nail down a better set of STR.

Comment 1

[Cody Roesch [:croesch]]

I was able to track this bug down on the Flame 2.0

STR:
1. Enable Passcode lock on in settings -> Screen Lock
2. Launch an app such as Camera. (any app seems to work)
3. Tap the power button to lock the phone.
4. Launch the camera from the lock screen.
5. Hold the home button until you feel a vibration.
6. Tap the home button now to go to the lock screen
7. Enter the passcode to unlock the phone.
8. Notice the dock is now too low and being cut off.

Repro 5/5 100%
I've tried to narrow the steps down further but cannot seem to. I also don't know if this is exactly how marcia got this but mine is 100%


Environmental Variables
Device: Flame 2.0
Build ID: 20140520040203
Gecko: https://hg.mozilla.org/mozilla-central/rev/cb9f34f73ebe
Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348
Platform Version: 32.0a1
Firmware Version: v10F-3

Comment 2

[Cody Roesch [:croesch]]

Attachment: Flame 2.0.png

Comment 3

[Jason Smith [:jsmith]]

Check if this is reproducible on 1.4.

Comment 4

[Cody Roesch [:croesch]]

I was UNABLE to repro on Flame 1.4.

In 1.4, For step 8, instead of seeing the homes creen and the dock, the user is instead brought back into the camera app. Exiting the camera app manually at this point, the user does not get the dock problem.

Comment 6

[Jason Smith [:jsmith]]

STR feels unrealistic, so I don't think I'll nominate this.

Comment 7

[Frederik Braun [:freddy]]

I still get this (this is why I filed bug 1015095), but have no deterministic STR. But I would assume this is a common bug for people with a lock screen pin.

Comment 8

[Jason Smith [:jsmith]]

Sounds like there's more reduced STR here. Flagging steps-wanted to keep looking.

Comment 9

[Cody Roesch [:croesch]]

Ok I was able to narrow this down to half the amount of steps.

Flame 2.0 device
STR:
1. Open the camera app.
2. Hold down the home button until you feel a vibration then release before the card view appears.
3. Tap the power button to lock the phone
4. Tap the power button again and unlock the phone and the dock is now cut off.

Repro Rate 5/5

Comment 10

[Jason Smith [:jsmith]]

Can we get a video using the reduced STR in comment 9?

Comment 11

[Cody Roesch [:croesch]]

Here is the video of the reduced STR.

http://youtu.be/iH5UgMqLuh8

Comment 12

[Jason Smith [:jsmith]]

Can we keep digging for a realistic STR that a user could actually hit? Something like the lockscreen pin freddy is talking about above would be an example.

Comment 13

[Cody Roesch [:croesch]]

Ok, Lets try this again.

Was able to repro with the following steps on Flame 2.0

1. Lock the test device. (No Passcode needed)
2. Call the test device and wait for the incoming call to show up on the test device screen.
3. Cancel the call with the calling device and then swipe to unlock the test device.
4. Dock is cut off.

I also tried this with messages being sent or calendar events triggering but the bug did not happen with those events.

As a side note, if these steps although realistic, don't fulfill the requirements you are looking for, lets try to get some more information from the reporter or Freddy. So far I've provided several ways of getting this but still don't know if im even close to what others have done to get this bug.

Any additional info is welcome.

Environmental Variables
Device:  Flame 2.0
Build ID: 20140527040202
Gecko: https://hg.mozilla.org/mozilla-central/rev/cbe4f69c2e9c
Gaia: 6a391274cd436f8f0d1fad2db8c6b4805703259c
Platform Version: 32.0a1
Firmware Version: v10G-2

Comment 14

[Jason Smith [:jsmith]]

Ok - that sounds plausible for someone to hit.

Comment 15

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

B2g inbound Flame regression Window

Last working Environmental Variables:
Device: Flame
BuildID: 20140513113002
Gaia: c0604e76821a38e2c57263d3d30b462718e945d2
Gecko: 69708ec6ef87
Version: 32.0a1

First Broken Environmental Variables:
Device: Flame
BuildID: 20140513143003
Gaia: a13d42ab5240008e042d0c61bf9c9d05174e70e4
Gecko: 4bf31b954518
Version: 32.0a1

Last working gaia / First broken gecko - Does not occur
Gaia: c0604e76821a38e2c57263d3d30b462718e945d2
Gecko: 4bf31b954518

First broken gaia / Last working gecko - Issue occurs - Indicates a gaia issue
Gaia: a13d42ab5240008e042d0c61bf9c9d05174e70e4
Gecko: 69708ec6ef87

https://github.com/mozilla-b2g/gaia/compare/c0604e76821a38e2c57263d3d30b462718e945d2...a13d42ab5240008e042d0c61bf9c9d05174e70e4

Comment 16

[Jason Smith [:jsmith]]

Maybe bug 1003870?

Alive - What do you think?

Comment 17

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

Maybe https://bugzilla.mozilla.org/show_bug.cgi?id=1011071 helps..

Comment 18

[Jason Smith [:jsmith]]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #17)
> Maybe https://bugzilla.mozilla.org/show_bug.cgi?id=1011071 helps..

Ok - will retest after that bug lands.

Comment 19

[Jason Smith [:jsmith]]

QA Wanted to test this on June 1st trunk build or later.

Comment 21

[Cody Roesch [:croesch]]

On the latest Flame 2.0 Trunk build 6/02, I'm unable to reproduce this bug. Following the steps in comment 13, the dock does not get cut off (Repro 0/5). Even following the steps in comment 9, I'm unable to reproduce.

Environmental Variables
Device: Flame 2.0
Build ID: 20140602072051
Gecko: https://hg.mozilla.org/mozilla-central/rev/6a984e21c2ca
Gaia: 82679a5ce84d1b6bf388da6536d5682a3ad56de3
Platform Version: 32.0a1
Firmware Version: v10G-2

Comment 22

[Jason Smith [:jsmith]]

Closing as fixed by bug 1011071.