[System] When launching camera from lock screen, previous FG application is shown for some time and then camera is opened

NEW
Unassigned

Status

Firefox OS
Gaia::System::Window Mgmt
3 years ago
3 years ago

People

(Reporter: Sharaf, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

Details

(Whiteboard: [LibGLA, TD-72462, WW, B] interaction-design)

(Reporter)

Description

3 years ago
STR

1) Enabel screen lock in settings
2) Open any application like messenger, Calendar etc
3) Lock the screen by pressing sleep button
4) From lock screen launch the camera app by sliding to camera icon

Actual Result:
The previous FG application is displayed for some time, and then camera app is launched

Expected result:
Camera app should be opened directly without showing previous app.
(Reporter)

Updated

3 years ago
Whiteboard: [LibGLA, TD-72462, WW, B]
(Reporter)

Comment 1

3 years ago
Hi alive,

It seems the issue happens because lockscreen is waiting for repaint whenever unlocked.
When launching camera, cant we just skip this?
Please provide your opinion.

ni? to alive
Flags: needinfo?(alive)
We may do something, but this seems a polish.
Component: Gaia::System::Lockscreen → Gaia::System::Window Mgmt
Flags: needinfo?(alive)
Hmm, on my flame the repaint doesn't occur but the camera transition is still from right to left.
Maybe this is the most strange part.
(Reporter)

Comment 4

3 years ago
as per discussion in IRC need UX input on this.

ni? UX team
Flags: needinfo?(firefoxos-ux-bugzilla)

Comment 5

3 years ago
Flagging Tif on camera.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(tshakespeare)
So firstly, I'm on my flame following the STR I don't see the previous foreground application (e.g. Music) before seeing the camera. However, like Alive, I do see the weird slide transition which appears to be similar to doing an edge gesture when the device is unlocked.

I also happened to notice, as I misread the STR at first, that when there is a passcode enabled and you tap on the camera icon from the lock screen, the camera app just appears (i.e. there is no weird slide transition). 

The two scenarios (passcode enabled or disabled) should be the same and we should not see the transition as in the passcode disabled state.

If there is a situation where a previous foreground app is being briefly displayed before showing camera (as indicated in the STR), the same is still true - we should not be seeing other UI before seeing the camera.

Not only does showing another app or the transition, however brief, increase the delay of using the camera app (which is our primary use case of putting the shortcut on the lock screen), there could be any number of private things (calendar appointments, text messages, etc) that a user would not want others to see before the camera is shown - regardless if it is passcode protected or not.

Whatever the case is, app UI or weird transition, the camera shortcut from the lockscreen should behave consistently in both passcode and no passcode situations and the camera should immediately come up with no other apps or transitions shown. This is not a matter of polish but is a usability issue.

Thanks guys!
Flags: needinfo?(tshakespeare)
Whiteboard: [LibGLA, TD-72462, WW, B] → [LibGLA, TD-72462, WW, B] interaction-design

Comment 7

3 years ago
hi james dolphin has this issue too . I can reproduce it on dolphin.
Flags: needinfo?(james.zhang)
Flags: needinfo?(james.zhang)
status-b2g-v1.4: --- → affected
This may require LockScreen & System to put the current app to background, and then launch the camera app (so that the app would launch as there is only the homescreen). Or to delay LockScreen unlocking until the transition is done in background (we can cease the animation to let the switching faster). IMO these two ways can keep the current path works well, and only require relevantly few modifications. However, Alive may know the issue better than me.
See Also: → bug 1068393

Comment 9

3 years ago
This issue currently repros on Flame 2.1 (319mb/full flash) and Flame 2.2 (319mb/full flash) 

Actual results: Previous app is briefly displayed when launching the camera from the lockscreen. 

Video clip: http://youtu.be/qVfKsdaVr7k

Device: Flame 2.1
BuildID: 20141201001201
Gaia: ccb49abe412c978a4045f0c75abff534372716c4
Gecko: 18fb67530b22
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
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
BuildID: 20141201040205
Gaia: 39214fb22c203e8849aaa1c27b773eeb73212921
Gecko: 08be3008650f
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 37.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Status: UNCONFIRMED → NEW
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
Ever confirmed: true
Flags: needinfo?(pbylenga)
QAWanted for branch checks.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: qawanted

Updated

3 years ago
QA Contact: ddixon
Branch Check

Issue DOES occur in Flame 2.2, 2.1, 2.0 (shallow flash, eng. build, 319 MB memory)

Actual Results: Previous app is shown when user accesses Camera at lockscreen. 

Device: Flame 2.2
BuildID: 20141202025557
Gaia: 725685831f5336cf007e36d9a812aad689604695
Gecko: 22ad8a162cf3
Version: 37.0a1 (2.2)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
----------------------------------------------
Device: Flame 2.1
BuildID: 20141202061559
Gaia: a684b82a19dd1939ca6e75e60a6203327b333c2a
Gecko: a7f6a3cc59bc
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.0
BuildID: 20141202035701
Gaia: 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko: 29222e215db8
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
status-b2g-v2.0: --- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: ddixon
You need to log in before you can comment on or make changes to this bug.