Closed Bug 1137013 Opened 10 years ago Closed 10 years ago

[Camera] Volume buttons in Camera preview cause app to become unresponsive when returning to Camera

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-master verified)

VERIFIED FIXED
2.2 S7 (6mar)
Tracking Status
b2g-master --- verified

People

(Reporter: bzumwalt, Assigned: wilsonpage)

References

()

Details

(Whiteboard: [3.0-Daily-Testing])

Attachments

(3 files, 1 obsolete file)

Attached file Logcat
Description: When user takes a picture in the Camera app, opening preview by tapping icon in bottom left, then pressing volume up or down on the volume rocker causes camera app to become unresponsive when user presses back button. Taking picture when on viewfinder screen in camera app by pressing volume rocker works as intended. Repro Steps: 1) Update a Flame to 20150225010244 2) Launch camera app 3) Take picture and tap preview icon 4) When viewing preview press up or down on volume rocker 5) Tap back button Actual: Camera is unresponsive when returning from image preview after using volume rocker. Expected: Camera does not become unresponsive. Environmental Variables: Device: Flame 3.0 Build ID: 20150225010244 Gaia: f6bfd854fe4746f21bc006eac145365e85f98808 Gecko: 0a8b3b67715a Gonk: e7c90613521145db090dd24147afd5ceb5703190 Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0 Repro frequency: 3/3, 100% See attached: Youtube video clip & logcat Youtube link: http://youtu.be/bFuPFpp2GmI
Unable to test in Flame 2.2 as the volume rocker camera feature is not present in build.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Flags: needinfo?(wilsonpage)
We need to make sure that the .capture() call is ignored when the preview-gallery is open.
Flags: needinfo?(wilsonpage)
Assignee: nobody → wilsonpage
Attached file pull-request (master)
Attachment #8569819 - Flags: review?(lissyx+mozillians)
Attachment #8569819 - Flags: review?(jdarcangelo)
Comment on attachment 8569819 [details] [review] pull-request (master) I'm not a peer for this, but that does the job.
Attachment #8569819 - Flags: review?(lissyx+mozillians) → feedback+
Comment on attachment 8569819 [details] [review] pull-request (master) LGTM
Attachment #8569819 - Flags: review?(jdarcangelo) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Please request Gaia v2.2 approval on this patch when you get a chance.
Flags: needinfo?(wilsonpage)
Target Milestone: --- → 2.2 S7 (6mar)
This issue is verified fixed on the latest Nightly Flame 3.0 build. Actual Results: The camera app is still responsive after returning from preview. Environmental Variables: Device: Flame 3.0 KK (Full Flash) (319 MB) BuildID: 20150312010235 Gaia: 0c4e8b0b330757e261b031b7e7f326ef419c9808 Gecko: 5334d2bead3e Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: verifyme
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #8) > Please request Gaia v2.2 approval on this patch when you get a chance. The bug this patch fixes does not exist in v2.2 as we haven't uplifted the volume-key capture feature.
Flags: needinfo?(wilsonpage)
This blocks a blocker. Wilson, please request Gaia v2.2 on this when you get a chance.
Blocks: 1135789
blocking-b2g: --- → 2.2?
Flags: needinfo?(wilsonpage)
blocking-b2g: 2.2? → 2.2+
Attachment #8569818 - Attachment is obsolete: true
Comment on attachment 8582369 [details] [review] [gaia] wilsonpage:1137013-v2.2 > mozilla-b2g:v2.2 [Approval Request Comment] [Bug caused by] (feature/regressing bug #): [User impact] if declined: Volume rocker will toggle volume and not capture [Testing completed]: [Risk to taking this patch] (and alternatives if risky): New feature, moderate risk. [String changes made]: None
Flags: needinfo?(wilsonpage)
Attachment #8582369 - Flags: approval-gaia-v2.2?
Blocks: 1137918
Attachment #8582369 - Flags: approval-gaia-v2.2? → approval-gaia-v2.2+
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #14) > v2.2: > https://github.com/mozilla-b2g/gaia/commit/ > 7f1dab89dcd6ecaff2d62c031481b64b100386bf I don't think this should have been landed as it depends on bug 1133965. Also QA think this may be too risky to uplift features at this stage. I think we should backout. Apologies if I haven't pressed the right buttons. I'm not clear how patches with dependencies should be uplifted.
No longer blocks: 1133965
Depends on: 1133965
Ryan can you back the v2.2 patch out please?
Flags: needinfo?(ryanvm)
The approval request should have been cleared if you changed your mind about uplifting. Or a NO_UPLIFT on the whiteboard if you weren't sure yet. v2.2: https://github.com/mozilla-b2g/gaia/commit/cf9c885e882cee2452be36154fafe24c039b8518
Flags: needinfo?(ryanvm)
Attachment #8582369 - Flags: approval-gaia-v2.2+
Also, blocking 2.2+ status should probably be revisited.
Flags: needinfo?(bbajaj)
blocking-b2g: 2.2+ → ---
Flags: needinfo?(bbajaj)
Per comment 9 & comment 17, clear "verifyme" keyword.
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: