(This image is a screenshot of the original, as the original was too large to upload.)
As far as I can tell this is random (ish), when it happens, it happens continually, at least for several minutes. It only happens on “std” setting, not on “hdr” or the others, but switching back to “std” stilll causes this error.
The image above was taken yesterday, I have about 10 other similar ones. It also happen the day before. But today I can not get it to reproduce the problem.
I have already had lots of issues with the open camera provided by /e/, such as green tinted hdr pictures or random crashes.
What may sound strange but actually works is just to use the original open camera app which may be found on f-droid and source forge (for those interested it’s here). Since i have used this method, i’ve never had problems. It’s the exact same software with a different UI.
I am still getting the problem, but perhaps more info can help diagnose a solution. I ma also willing to test/debug the camera app.
I have found that once the problem (i.e. the selfie camera), quitting the app and then restarting it does fix it, and therefore, it is not a problem with the current settings (i.e. resetting as above) but with something that occurs after using it.
I regularly switch between the different modes when using the camera, so perhaps a reset of some kind is needed between mode switch - I am obviously guessing.
I have also installed the original camera via fdroid. However, that has a problem with the wide-angle camera so is not useable either (it is always far to dark).
I didn’t say specifically, but assumed the new phone would be running the latest versions.
For completeness:
/e/ vesion : 2.8-t-20250219470165-official-FP5
fairphone : e_FP5-user 13 TQ3A.230901.001 eng.root.20250219.200752
I’ve just turned on the Faerphone camera and it looks awesome. What is the reason it is n;t on by default? Does it have security/tracking/open source issues?
My guess would include the concepts that Fairphone developed their own camera … there was demand for /e/OS to include the software … but there is quite a strong feeling that /e/OS should look very much the same on all devices especially in the official builds.
I guess the current situation is some sort of compromise. My guess is that it is not hidden in this way for any sort of security reason, if that were the case I would expect some clear indication as the user chose to open it.