967901 - [Flame] Front Camera does not update the preview mode after taking one picture.

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Vendcom, defect)

Description

[John Hammink]

Flame
build from February 1 (that came with the device)
(Note - not possible to get software version nor logcat from device as the device currently doesn't boot past splash screen:  see 967890 - [Flame] Device doesn't boot past splash screen ).  

Previously, the device booted.

STR:
Press the camera button.

Expected:  Camera is invoked, with preview.

Actual: Camera is invoked, but crashes occasionally.   When it is invoked without crashing, there is no preview.

Comment 1

[John Hammink]

Version info:

    Gaia      e3d9cd2464a7acb95174abaff992a6b1167f6fd0
    Gecko     93c3441d3075a9fb54223c9396e519b7997ca0e5
    BuildID   20140128131230
    Version   28.0a2
    ro.build.version.incremental=35
    ro.build.date=Tue Jan 28 12:53:28 CST 2014

Comment 2

[yixiang wu]

 When you press the camera button, it enter the front camera firstly. Because the front camera can't work. so crash happened. You can press the top right corner button to enter the rear camera when it is in the front camera. The rear camera is work and preview normally.

Comment 3

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Yixiang -

May I know when you can fix the front camera?

Thanks

Vance

Comment 4

[yixiang wu]

No problem.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

The back camera does seem to work fine.  It's the front camera that has an issue with preview after taking one picture.

Comment 6

[David Flanagan [:djf]]

Does the camera app default to the selfie camera on this device?  

At the gecko level, the cameras just have numbers 0 and 1.  We default to camera 0. On all other devices, this is the rear camera.

If this is a critical bug for MWC we can probably workaround this in Gaia with a build time configuration that specifies which camera number to use by default.

Comment 7

[Jason Smith [:jsmith]]

Vendor issues don't block the release, so clearing the nom.

Comment 8

[Tony Zhao]

This issue should be already fixed on SW version v107 which release on Feb. 20.
Please verify on this version.

Comment 9

[Al Tsai [:atsai]]

Tested w/ SW version v107. it's fixed