Is the difference the same when you shoot the photos from the same distance? (the first photo is taken from further away) Did the first photo use flash (Blitzlicht)? (the selfie cam has no real flash at all)
The problem is still there. It is no solution, that some apps will to some digital postprocessing with the picture. The problem still ist, that the Fairphone OS is not handling the imager settings correctly. Therefore the image is still too dark in many Apps.
This is pretty anoying, due many Apps needs to Frontcamera for identity verification and the too dark pictures can’t be used. There is still work to do and this isn’t acceptable at all, because the problem is know since many years and there is still no work in progress!
I’d like to think it is.
I guess every camera App including every stock camera App post-processes the pictures, that’s why enthusiasts are so eager to get RAW format pictures to get around any processing any App would do before they apply their own treatment to their images.
So, if an App post-processes badly, use an App that does it better.
At least this way you could make sure whether you are dealing with a hardware or a software fault.
Off course the protection foil was removed, I’m developer of such camera systems, so I’m pretty sure what I’m talking about.
When taking a picture, you have two possibilities to manipulate image parameters like brightness or contrast: you can post process the RAW data and you can change register settings of the imager.
Both is needed to get ideal results. But it seems that either the analog gain or the exposure time of the sensor can’t be set. And that is an App independent problem.
You can clearly see, that these Apps do some digital gain on the RAW data, which leads to a pretty high noise. When I have an App which is not processing with additional digital gain, and use a lot of light, I see a pretty clear picture with very low noise.
Therefore I’m definetly sure, that dynamic register settings are not performed well and this is what the Fairphone developers have to check. Since today, there is no feedback of the Fairphone developers, which is in my opinion pretty poor. The whole idea of the Fairphone is useless, when the device does not work well.
While I can understand frustration about unfixed bugs, this one was entered for Android 6.
I’m positively surprised there’s still developer activity in the Android 6 bugtracker.
Fairphone currently seem to have their hands full with Android 7, so I think your chances would be better with checking whether the problem persists in Android 7 and if so, with entering the issue again for Android 7.
Edit: I just saw somebody mentioned in the Android 6 issue that it persists in Android 7. That’s not as effective as entering it in the Android 7 bugtracker, I think.