Thanks for bringing this up. There might be some calibration settings in the flame that needs to be adjusted. I think that's on the gonk level. Looks like we do have a bug on the exposure : bug 1056956
I asked the TAM to have the vendor look at the bug to see if they could fix it. Regards, Naoki On May 11, 2015, at 6:56 AM, Jonas Witmer <[email protected]> wrote: > I already noticed this issue in winter using the 188 image. I got some > picture from last summer, using the 123 image, and they are fine. > > Am 11.05.15 um 15:30 schrieb Andrew Osmond: >> We don't do anything differently on Open C vs Flame, and accept most of the >> defaults from the camera service/driver, so I believe most differences would >> be due to the hardware. I can't say I've used the Open C to compare though >> since I started with a Flame :). I will see about flashing the one I >> inherited and do a camera parameter comparison to make sure was nothing >> changed by the vendor. >> >> However in Aaron's case, it sounds like you have noticed a similar >> regression on the *same* device? Do you have rough window on when this >> happened? If you still have the photos (and proper timestamps), can you look >> up the last good / first bad taken photo dates? I would say it is more >> likely to be the base image, if only because we don't really tweak most of >> the camera parameters related to picture quality (except capture resolution). >> >> Thanks, >> >> >> Andrew >> >> On Mon, May 11, 2015 at 9:00 AM, Aaron Cajes (Mozilla PH) >> <[email protected]> wrote: >> This happened to me on my flame, too. Same nightly base image + Master build. >> >> And i thought my flame's camera was broken. Because photos before my current >> base image was great. >> >> — >> Sent from my Android Cherry Mobile phone >> >> >> On Mon, May 11, 2015 at 8:22 PM, Wilson Page <[email protected]> wrote: >> Pretty sure this is a hardware limitation. +aosmand to provide more info on >> this. >> >> W I L S O N P A G E >> >> Front-end Developer >> Firefox OS (Gaia) >> London Office >> >> Twitter: @wilsonpage >> IRC: wilsonpage >> >> On Mon, May 11, 2015 at 12:59 PM, Panos Astithas <[email protected]> wrote: >> The camera on my Flame (18D, nightly) can't seem to handle normal daylight >> conditions, at least of the kind we get here in Greece. Pictures I take in >> broad daylight are always overexposed and ugly as hell. On a cloudy day I >> can get decent pictures, so I'm wondering if that is a limitation of the >> hardware or a driver issue. Using HDR during the day generally tends to make >> things worse. >> >> My Open C (2.2) doesn't have that problem at all (just an atrociously low >> sensor resolution). I always get better pictures during the day from the 2MP >> Open C than the 5MP Flame. >> >> Has anyone else seen this? >> >> Thanks, >> Panos >> >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> >> >> >> >> >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
