The pictures actually don't look too bad! What I see from the pictures is more of an environment lighting (sun shining really bright) issue versus the camera actually being defective.

If you insist that the device is the sole issue, I would suggest resetting the device and if that doesn't resolve the issue, you should contact your place of purchase.

Thanks!

It is quite awkward. Event my worst phone with a 0.3mpx doesn't do that on day light. Can't this be corrected by software?

Hi Luis,

Those pictures (especially the ones outside by sunlight) definitely look washed out and extremely bright. It seems as if the sensitivity in the camera is turned way too high!

I have a Flame device and the quality on my camera is very decent in daylight. Unfortunately, this may be a sign of a hardware issue. I would also advise contacting the place you purchased your device, as well as the manufacturer (T2M) for additional support.

In the meantime, there may be a couple of things you could try to troubleshoot this issue:

1. Take the back cover of the phone off.
2. Take the battery out.
3. Take the SIM card and microSD card out (if applicable).
4. Wait 10 seconds.
5. Put the SIM card and microSD card back in (if applicable).
6. Put the battery back in.
7. Put the back cover back on.
8. Turn the device on.
9. Check if the issue you were having is still present.

You may also attempt to do a full reset of the device.

Warning: Resetting your phone will delete all data stored on the device, including apps, calendar data, email accounts, and settings.

To reset the device, follow these instructions:

1. Open the Settings application.
2. Tap on the Device Information button.
3. Tap on the More Information button.
4. Tap on the Reset phone button.
5. Tap OK to reset your device.

Lastly, you can also attempt to flash a newer version of Firefox OS on your Flame device. You can find more information on how to update your device on the Mozilla Developer Network - Flame page.

We hope that this fixed the issue you were having. Please report back to us if this helped!

Thanks!!

- Ralph

Hello Ralph,

Thank you for your help. I'm already running the 2.0 from the stable branch. I have problems with the daily updates but that's a different problem.

I will try doing what you've said and if it doesn't work, I'll try updating to the 2.2 version. But if it is a kernel issue then I'll have to wait for an update in the base image.

I also need to know if it isn't an hardware problem.

There is definitely something wrong with the camera on v2.0

The two pictures below show the same location the first (good one) taken with v1.3 and the second one with v2.0. I think there is something wrong with the calibration, because I noticed that the v2.0 camera takes really good low light pictures. Something in the code seems to prevent it from adjusting to changing light conditions.

I just installed v2.0 which is the latest version available at the Flame Developer page. Why would resetting the phone make any difference?

Hi aliasbody and Michael,

Thank you for the additional examples and information about this issue. Unfortunately, I have been unable to reproduce it on my Flame device.

I am running a recently flashed device with the new KK-based v180 base image, listed here, and then flashing a v2.0 build on top of it.

I opened bug 1082829 so that our developers can investigate and track this issue.

My suggestion for resetting the device was just a general troubleshooting attempt. If there was an internal camera setting that somehow got messed up, my hopes were that resetting would bring those "brightness" settings back to normal.

Since version 2.0 has already passed the Code Complete phase, I would suggest attempting to reproduce this issue on versions 2.1 and 2.2. It is possible that this problem has already been resolved in the more recent releases.

In the meantime, to help isolate this problem, would you be able to reproduce this issue with the front+back cameras, as well as with the Flash turned to "On", "Auto", and "Off"?

Thank you again for the additional information, and for your help in the investigation and resolution of this camera problem.

- Ralph

So, if I understand correctly, you put on the 2.0 base OS and then flashed 2.0 again? How are those different. I only flashed the 2.0 base OS linked from the Flame web page. Where can I find the updated version 2.0? Or version 2.1, for that matter. Thanks.

When installing the 180 base image you have the base development image with all of the dev tools and apps and only the English Language. After that you need (it is not an obligation though), to install one of the updates using the shallow script by updating it to a nightly build (2.0, 2.1 or 2.2 knowing that the 2.0 is the 'stable' one).

You can find everything here : https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Updating_your_Flame_to_a_nightly_build

With the nightly versions you receive an update every day, but for me and for some users the updates don't work (because of the lack of space in the system partition), I've created a script for this which corrects the font problem (on some 2.1 and 2.2 installs) and removes 'unnecessary fonts' in order to provide enough space to OTA Updates.

Give it a try : https://bugzilla.mozilla.org/show_bug.cgi?id=1021839#c50

There's a comment here from a user who won an Open C (presumably with the default FFOS 1.3) claiming that his videos jumped from 352 x 288 to 720x480 when he installed android in place of FFOS on the same phone.

I also have an Open C with FFOS 1.3 and as far as I can see, there's nothing in the settings which could have been wrongly set to reduce the resolution and if android can capture video at much higher resolution with the same hardware, it seems that FFOS must be doing something wrong.

http://community.giffgaff.com/t5/Social-General-Discussion/I-ve-won-a-Firefox-phone/td-p/14483009/highlight/true/page/4