@Escain said in Any solution to get decent photos?: my picture with 12.6MP is usually between 2 and 3MB, but that could depends on the details on the image. I tried with a zoom and the image is indeed smaller at 2.8 Mb - as could be expected with a zoom done in software, there is less detail. I played a bit with the zoom (never used it before, for doing near distance photos I find much easier to actually get the phone nearer to the object) and it can indeed throw the focus off, but doing the video/still image switch fixed it. @Escain said in Any solution to get decent photos?: several hypothesis compression: my guess is not, 4.5 Mb for a jpeg image is not very aggressively compressed if at all. beautifying filter: there is nothing of the sort in the app code, as it is using QT controls it could be integrated in these controls, don't know. problems with zoom: this could be the more likely idea. Maybe you could give a try to the photo app in Waydroid. When faced with the focus problems, before finding the switch to video trick, I found that it focused properly immediately for near distance photos.

@gpatel-fr Thank you. I will follow that bug-report.

@Escain What android version did the phone come with? V14. I think that the issue was because I setup a fingerprint on Android before I installed UT. After several reboots and I don't know exactly what, it started working. Now, everything except GPS seems to work. Thank you for your help

@Futura Most of the time, yes. But I am still on Focal.

It is definitely some hardware-specific issue. I would not go as far as calling it a feature. Maybe because of low power, there is entered some specific bootmode and our halium-stage cannot handle that right or whatever. Though on a quick investigation in the FP3-android-device-source I could not see any obvious passage for this hypothetically case. Maybe someone could investigate differences in dmesg init logs or journalctl with and without low battery. I don't see other possibilities to find the root cause for this behavior. Besides that, that issue is very low priority on my list. It exists from the very beginning and I know how to avoid it, what makes me not putting too much energy into solving it.

@mario-ch said in Feedback FP3+ after 3 months: As a non-programmer, it is still difficult for me/us to understand that all non-smartphones, no matter how cheaply produced, have no problems with Bluetooth connections in car hands-free systems. Sorry, but that is simply not true! I have seen plenty of issues with all kinds of phones from very cheap to very expensive! Having Bluetooth issues with some random device they are beeing connected to seems almost normal : From headsets/earphones to cars and PC's/laptops! Bluetooth itself as a protocol is simply a mess and can easily have a lot of issues if you are unlucky...