@wgarcia Thanks for the info! I am sure there is someone else out there looking as well.

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...