[Camera] Viewfinder may appear white/black; taking pictures is normal

NEW
Unassigned

Status

Firefox OS
Gaia::Camera
3 years ago
2 years ago

People

(Reporter: oliverthor, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(tracking-b2g:backlog, b2g-master affected)

Details

(Whiteboard: [2.5-Daily-Testing], [Spark], URL)

Attachments

(3 attachments)

(Reporter)

Description

3 years ago
Created attachment 8634816 [details]
logcat_20150716_0753.txt

Description:
When the user tries to take a picture from the camera app, they may observe on the camera open to a black-or-white screened viewfinder. All buttons are visible, however the screen does not display what the camera is viewing. Taking a picture via the shutter button, the user will observe a detailed preview image appear in the bottom left hand corner, and tapping the preview will bring the user to preview with actual pictures. Returning to viewfinder at this step will restore the viewfinder's screen to reflect the camera's actual view.
App was opened from homescreen, minimal other apps in use: observed during sanity tests, messages and dialer may have been open/used.

Repro Steps:
1) Update a Flame to 20150715160204
2) Do stuff
3) Open the Camera app
4) Observe viewfinder/screen
5) Take a picture
6) Observe preview, tap preview to view fullsize images


Actual:
Viewfinder may appear as a full white or black screen; taking pictures works as expected with what the camera actually sees

Expected:
Viewfinder/screen displays what the camera sees


Environmental Variables:
-------------------------------
only observed device:

Device: Flame 2.5
Build ID: 20150715160204
Gaia: b9968cdc4a1dee49848fed6159a59c378cea062d
Gecko: 49683d4e9ebd
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
--------------------------------


Repro frequency: 3/20 (only seen 3 times: 2 black screens, one white)
See attached: 
logcat x 2
video- https://youtu.be/Y1jizThn6ZM
(Reporter)

Comment 1

3 years ago
Created attachment 8634817 [details]
logcat_camera.txt
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
No-Jun have you seen this issue on Flame?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(npark)
Hmm, I can't repro this on my device with today's nightly, either on 319 or 512.  But this does sound a bit similiar with https://bugzilla.mozilla.org/show_bug.cgi?id=1183279, which I'll close now since I can't repro it.
Flags: needinfo?(npark)
Created attachment 8636297 [details]
dmesg

I was able to reproduce the bug 4 times on the reported build, and 1 time on today's build during the 3 hours of attempting to repro. Unfortunately I was NOT able to narrow down an STR. The repro rate is extremely low and SEEMS random to me.

A few notes:
- I was able to repro the bug with or without USB cable plugged in
- I was able to repro the bug with Geolocation app permission setting of Camera set to 'Share'
- I've taken pictures/recorded videos in Camera app
- Don't think it's a prerequisite to utilize Phone and Messages app, but I did open Phone app at some point.
- Settings app was utilized. I toggled Geolocation and NFC toggles.

I could continue to try but it feels like I'm getting nowhere in finding a consistent repro. Not sure if it's helpful but I've attached dmesg logs when bug happened.
Flags: needinfo?(ktucker)
I also was not able to nail down solid repro steps for this bug, but I was able to reproduce it about 12 out of about 65 attempts.  
What I noticed was that the issue reproduces when the camera has been off long enough (30+ seconds seems enough) that it must be reinitialized (a circular loading icon) when the app is opened.  This issue seems to be that it doesn't initialize and just shows a Black (common) or White (rare) screen with the focus reticle visible immediately (no loading icon).

For a short time I thought that putting the phone in landscape mode increased the reproduction rate (reproduced 4 times in a row) but then it no longer reproduced so that angle is a bust.

Leaving the tag so someone else can try.

Environmental Variables:
Device: Flame 2.5
BuildID: 20150716121625
Gaia: 77bc0d940bde2a5d2d4dfadfcccc6d8d77456d36
Gecko: 8d262d1d0ae5
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 42.0a1 (2.5) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
I was unable to reproduce this issue at a consistent rate on a later build (7/28). The Camera app opened to a black screen 3/35 attempts.  I had various apps running prior to opening Camera.  Locking/unlocking the screen seemed to not affect the repro rate at all.  Taking comment 5 into consideration, I waited about 30 seconds between opening and closing the Camera.      

Device: Flame 2.5 (shallow flash)
BuildID: 20150728175845
Gaia: 21256d7665f972255d198f8af81a8df4bd0e0fc4
Gecko: 2ee9895e032c
Version: 42.0a1 (2.5) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Requesting removal of steps-wanted tag as I am the third tester to find better STR.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: steps-wanted
[Blocking Requested - why for this release]:

Due to low repro rate, marking it as b2g-backlog until a reliable STR is found.
blocking-b2g: --- → 2.5?
[Tracking Requested - why for this release]:
Per comment 7
blocking-b2g: 2.5? → ---
tracking-b2g: --- → backlog
Duplicate of this bug: 1180729
Flags: needinfo?(aosmond)
I have been unable to reproduce.

However since you are able to take pictures, that means the camera hardware is active and working. The only known broken functionality is the viewfinder, which sounds similar to bug 1202967 where the audio gets muted and the viewfinder stops playing. Flame doesn't have a hardware button like aries so that reproduction path is out, but it may have the same root cause.
Flags: needinfo?(aosmond)
See Also: → bug 1202967
You need to log in before you can comment on or make changes to this bug.