813112 - [ftu] First-time-usage screen is painful when the user must enter a pin code

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia, defect, P1)

Description

[Julien Wajsberg [:julienw]]

* have a new shiny phone (for example, after make reset-gaia)
* have a sim card with a sim code
* boot the phone

-> you get the pin code window (but not the same than the one we have from gaia after this) but in the same time you have the lock screen. This makes it very painful to enter the pin code as we kind of never get the keyboard.

This may be a regression with the new lock screen ?

Comment 1

[Borja Salguero [:borjasalguero]]

Now there is no 'lockscreen' when FTU is starting.... Could you check it again?

Comment 2

[Julien Wajsberg [:julienw]]

Attachment: video of the lock screen with the pin code

Comment 3

[Julien Wajsberg [:julienw]]

Attachment: photo of the device

Comment 4

[Julien Wajsberg [:julienw]]

I uploaded 2 artifacts that exhibit the problem (current gaia + gecko + b2g)

Comment 5

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

(In reply to Borja Salguero [:borjasalguero] from comment #1)
> Now there is no 'lockscreen' when FTU is starting.... Could you check it
> again?

Confirmed. You remove the ftuStarting class after the app window is opened, so the lockscreen appears. The z-index of lockscreen is higher than the keyboard. Sad I don't find this.

Comment 6

[Borja Salguero [:borjasalguero]]

[:alive] [:julienw] Let me check with latest build because it's working for me with my old build (before new lockscreen)... :( Im afraid that something changes with the new lockscreen. I will come back this evening with some updates.

Comment 7

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

There is still another issue, the lockscreen is still there during FTU running so the screen timeout is very soon if the user don't touches the screen after 5~7 seconds. That's bad UX.

Comment 8

[Julien Wajsberg [:julienw]]

:alive> yep that's very painful as well, I was considering opening another bug for that.

Comment 9

[Tim Taubert [:ttaubert] (inactive)]

It would be also nice to ensure that the screen isn't locked after the user finished the FTU process. I'd just expect the phone to be ready then.

Comment 10

[Borja Salguero [:borjasalguero]]

[:alive] [:julienw] Im gonna fix this bug and Im gonna include the 'numeric' keyboard instead QWERTY one. Let me check if changing the screen time-out is easy and I will add it to this PR. Thanks!

[:ttaubert] Let me check with UX, because I dont know if they want this behaviour.

Comment 11

[Borja Salguero [:borjasalguero]]

Attachment: PR

NOTE: If blocking-basecamp+ is set, just land it for now.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
User impact if declined: 
Testing completed: 
Risk to taking this patch (and alternatives if risky):

Comment 12

[Francisco Jordano [:arcturus] [:francisco]]

:alive +1, is there any bug filled for that?

Here we should fix the problem regarding the PIN, and open a new one for the screen timeout.

Thanks!

Comment 13

[Francisco Jordano [:arcturus] [:francisco]]

(In reply to Francisco Jordano [:arcturus] from comment #12)
> :alive +1, is there any bug filled for that?
> 
> Here we should fix the problem regarding the PIN, and open a new one for the
> screen timeout.

w00t! just discovered this -> Bug 813541

Thanks again!

> 
> Thanks!

Comment 14

[Borja Salguero [:borjasalguero]]

Thanks [:arcturus] !

Comment 15

[Josh Carpenter [:jcarpenter]]

(In reply to Tim Taubert [:ttaubert] from comment #9)
> It would be also nice to ensure that the screen isn't locked after the user
> finished the FTU process. I'd just expect the phone to be ready then.

Agreed. Conclusion of FTE should take user straight into Home screen, not require they unlock the device.

Comment 16

[mdaniloff]

Verified Fixed in Unagi build #20121231070201