I am having the same issue here.
Uninstalling and reinstalling the Gallery (click command) did not help.
Also, removing the cache rm -rf .cache/mediascanner-2.0/ .cache/lomiri-thumbnailer/ .cache/gstreamer*/* and rebooting did not help neither.

I did not tried to reinstall ubports with ubports installer, as this is my phone and I don't want to play too much with it.

@gandalf

Thanks your. So it's confirmed that this is not solely my battery.

I see no reports of this on Android FP3+, this might be either Linux or UT. Or maybe a mix with the firmware of FP3.

I confirm this issue on my FP3+, 100% times when I boot it under 10%.
Additionally, it's exactly 10%, so it seems either firmware or UT software. If it were hardware, I would expect this 10% to drift over years (with the battery getting old), or being slightly different on different devices.

My battery seems to work totally fine: I have usually 3+ days of autonomy, and the phone reacts perfectly up to the 0-1%.

I think that UT have a special start-up on low-battery causing the issue. The fact that the phone reacts differently at 9% or 11% is a strong indication that this is software and not hardware.

So I want to highlight that the phone works perfectly until dying at 0%.
The problem only appears when starting the phone below 10%.

Hi,

I am using a Fairphone 3+, with 2022-W47 4258, but I see this issue since several updates.

When my battery get under 10%, the "low battery" message shows.
I usually react to this either by :

1. connecting the device to a power source, or
2. by switching off my device, so I can make a last call in case of urgency.

It happens that if I start my device with still less than 10% of battery, it is not able to connect in any way:

• I can enable the wifi, but no wifi is detected
• Antena signal shows error, and I can't receive/send calls or SMS.

I usually wait until the battery level is ok, and then restart the device. This fixes the problem (until I start my device under 10% again).

Is this issue known?
Is there any configuration to fix it?
Is this related with Ubuntu-Touch in general or just with my FP3+?

@mario-ch said in Feedback FP3+ after 3 months:

Als Nicht-Programmierer ist es für mich/uns immer noch schwer zu verstehen, dass alle Nicht-Smartphones, egal wie billig sie produziert werden, keine Probleme mit Bluetooth-Verbindungen in Freisprechanlagen von Autos haben.

The problem is that most manufacturers (HW) don't care about Linux, so they don't implement any driver. Then, Linux kernel developers need to guess how that hardware work and create drivers, which arrive late. So you can have several years delay between a hardware being released, reported and solved.
When you buy a cheap HW, they created it, and they created the driver at the same time.

Back to the topic:
I wonder if the Android driver could be included somehow?

Ubuntu-touch status on FP3, after 3 months:

Hi community!
First of all, thank you for providing this great OS compatible with my FP3+ phone. I really enjoy it and I am happy to be far from the big-brother company

Mostly, all necessary is working:

1. I can call / receive calls
2. Basic access for browsing
3. Telegram messaging
4. OpenStore applications for most common scenarios.

What I really miss:

1. P0: Bluetooth support for calls. When driving, it's an absolute must. I also have "that" wonderful headset able to manage calls.
2. P1: Fingerprint: not a must, but still, very convenient.

Hopefully it helps

Kind regards
Adrian