Closed
Bug 1211032
Opened 9 years ago
Closed 7 years ago
When starting a video recording, the UI does not change immediately.
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect, P3)
Tracking
(blocking-b2g:-, b2g-v2.2 unaffected, b2g-master affected)
RESOLVED
WONTFIX
blocking-b2g | - |
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | unaffected |
b2g-master | --- | affected |
People
(Reporter: JMercado, Assigned: dmarcos)
References
()
Details
(Keywords: regression, Whiteboard: [2.5-Daily-Testing][polish] 2.6UXnom)
Attachments
(1 file)
535.70 KB,
text/plain
|
Details |
When starting a video recording, it can take up to 4 seconds before the camera UI will switch.
Repro Steps:
1) Update a Aries to 20151002111044
2) Open the Camera App
3) Switch to video recording
4) Press the record button
Actual:
The UI will sometimes take much longer to change to recording mode than normal.
Expected:
The UI changes quickly and starts recording.
Environmental Variables:
Device: Aries 2.5
BuildID: 20151002110438
Gaia: 9a682cb7bc8b7fde624a9b2b3c2d64415a08b04b
Gecko: 5f16c6c2b969f70e8da10ee34853246d593af412
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 44.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
Repro frequency: 3/12
See attached: video, logcat
Reporter | ||
Comment 1•9 years ago
|
||
This issue DOES reproduce on 2.5 Flame.
Actual Results: The Camera UI will not always change immediately when starting a video recording.
Environmental Variables:
Device: Flame 2.5
BuildID: 20151002030232
Gaia: 9a682cb7bc8b7fde624a9b2b3c2d64415a08b04b
Gecko: 5f16c6c2b969f70e8da10ee34853246d593af412
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
This issue does NOT occur on 2.2 Flame.
Actual Results: The Camera UI always switches immediately.
Environmental Variables:
Device: Flame 2.2
BuildID: 20151002032503
Gaia: 5dd95cfb9f1d6501ce0e34414596ef3dd9c2f583
Gecko: 2ab95b3d02a7
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → unaffected
Flags: needinfo?(ktucker)
Keywords: regression
Comment 2•9 years ago
|
||
[Blocking Requested - why for this release]:
Performance regression so in camera so nominating to block on this.
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(npark)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: sleedavid
Comment 3•9 years ago
|
||
There is no performance regression (to my knowledge). It can really take a few seconds for the camera driver/hardware to be ready sadly and always has (I see the same behaviour on a BB Z10). The reason this doesn't happen on 2.2 is because the display behaviour changed in bug 1192186.
On 2.2 the timer was shown as soon as the recording start was requested. It would take up to 4 seconds to start incrementing that timer. On master the timer is only shown when the recording has started (hence the up to 4 second delay in showing it) but always starts incrementing right away.
It is a simple change back on when to display the start is requested but it is a little deceiving. Maybe we could show it right away but put "--:--" in the timer box until it actually starts recording, to provide an indication to the user that it isn't actually recording yet...
Blocks: 1192186
Comment 4•9 years ago
|
||
Hmm, per Comment 3, so this bug is not a performance regression, but a sort of UI one. I'd think having a message that indicates the camera hardware is preparing to get ready would suffice. But the wait for the video camera does feel rather long in current setup.
Flags: needinfo?(npark)
Updated•9 years ago
|
QA Contact: sleedavid
Updated•9 years ago
|
QA Contact: jthomas
Comment 5•9 years ago
|
||
B2g Inbound Regression Window
Last Working
Environmental Variables:
Device: Flame 2.5
BuildID: 20150618203333
Gaia: ebe8099162234338dd95f8343651393b9de62dba
Gecko: 28876011e342
Version: 41.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
First Broken
Environmental Variables:
Device: Flame 2.5
BuildID: 20150619055343
Gaia: ebe8099162234338dd95f8343651393b9de62dba
Gecko: e3b6829af189
Version: 41.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Last Working gaia / First Broken gecko - This issue DOES occur with broken gecko.
Gaia: ebe8099162234338dd95f8343651393b9de62dba
Gecko: 28876011e342
Last Working gecko / First Broken gaia - This issue does NOT occur with broken gaia.
Gecko: e3b6829af189
Gaia: ebe8099162234338dd95f8343651393b9de62dba
B2g Inbound Pushlog:
http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=28876011e342&tochange=e3b6829af189
This issue is caused by Bug 1175656
Blocks: 1175656
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: regressionwindow-wanted
Reporter | ||
Comment 6•9 years ago
|
||
Andrew this issue seems to have been a fallout of a bug 1175656 instead. What are your thoughts?
Flags: needinfo?(jmercado) → needinfo?(aosmond)
Comment 7•9 years ago
|
||
Blocking for regression from 2.2
Diego,
Please take this and investigate. Andrew has a few other performance regressions on camera that needs to be looked at. Also please keep the bug updated with your progress.
Thanks
Hema
Assignee: nobody → dmarcos
Priority: -- → P3
Updated•9 years ago
|
blocking-b2g: 2.5? → 2.5+
Comment 8•9 years ago
|
||
Spoke to tif, adding ux folks for input (see comment 3). they will look into this in today's triage and comment
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 9•9 years ago
|
||
The regression should be fixed if at all possible. If it isn't possible, then we should be showing a spinner until the recording can start.
Thanks for pinging the UX team!
Flags: needinfo?(firefoxos-ux-bugzilla)
Comment 10•9 years ago
|
||
Removing from blocking release because of rate of reproducibility. However Diego will put in the simple spinner fix as suggested by ux team.
thanks
hema
blocking-b2g: 2.5+ → -
Whiteboard: [2.5-Daily-Testing] → [2.5-Daily-Testing][polish]
Updated•9 years ago
|
Whiteboard: [2.5-Daily-Testing][polish] → [2.5-Daily-Testing][polish] 2.6UXnom
Updated•9 years ago
|
Flags: needinfo?(aosmond)
Comment 11•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•