Software update: FP5.UT2E.B.078.20241105

Hi everyone,

New software update based on Android 14 for Fairphone 5 users.

Software Version: FP5.UT2E.B.078.20241105

Resolved issues

  • Implementation for French Parental Control
  • Fixed an issue causing failures connecting to the B2B Zero Touch Portal
  • Fixed an issue that was causing the Automatic network selection not to work correctly under certain circumstances.
  • Fixed an issue that was causing some user interface components to not scale properly when the text size was changed.
  • Fixed an issue that was causing the apps icons to be partially cut off when searching in the app drawer.

Other improvements

  • Security patch level: 5th of October, 2024
9 Likes

not yet available for me on fairphone 5, but glad to see issues getting resolved :+1:

1 Like

Same here, neither on FP4 nor FP5. Let’s keep an eye on the clock, I vaguely remember a recent occasion when an update got available at 18:00 sharp.


UPDATE :clock6: 18:00 Amsterdam time:

8 Likes

I got it too, nice. So it’s 18:00 for releases to be available.

FP5 update size is 541MB according to the android updater app

Please dont mix Devices, I will split now into 2 topics

For the FP4 see here

4 Likes

I’ve just installed the update, as it showed up about a day ago. It was installed without errors. It asked for a reboot, as expected. Now my Fairphone 5 is showing the blue Start screen with the Text “FAIRPHONE Change is in your hands”. It stays and is not going away. I’ve waited for several hours.

I’ve restarted the phone by pressing the power button. But after a restart, it stays on the blue screen. A removal of the Battery does not help.

I am able to boot into the recovery menu.
When trying to boot into safe mode, the phone powers off.

I’ve found the support article about sideloading. I am technical experienced and able to do that. But I can’t find a Fairphone OS .zip to download. Here I can’t find the mentioned “./sideload_update.command”

I don’t want to lose the data on the phone. So a Factory Reset would be my last option. What can/should I do to get it back to start properly?

1 Like

In worst case you need to do a factory reset from recovery. However first try to boot into to system several more times

1 Like

@Ioiana_Luncheon Every update is welcome - but very disappointing, that there is still no support for third-party passkey providers (i.e. the new credential manager is not activated, but the old and deprecated Google sign-in is still used), which should have come with Android 14.

1 Like

I restarted plenty of times. Is there a possibility to install the update via the recovery console from sd card or adb sideloading?

No, not that I’m aware of, last time I checked support page this option was not available

Did you report that to support?

Yes. Twice. - First directly in July/August (after the Android 14 release for the FP5) and now end of October again, since Microsoft plans to support third-party passkey providers on Windows 11 more broadly and the FIDO alliance develops the credential exchange protocols, which allows for exporting and importing passkeys between providers (not released yet). So the whole passkey train is on it’s way - and we don’t have a fully functional Android 14 on the FP5 (but the old and deprecated password manager component instead of the new credential manager). :neutral_face:

PS: Here is a list of all the technical advantages of the new credential manager: Migrate from legacy Google Sign-In to Credential Manager and AuthorizationClient  |  Identity  |  Android Developers

3 Likes

At Youfone here. the update went smoothly.

1 Like

My fingerprint disappeared after the update and I had to add it again. Other than that no issues so far.

1 Like

When will an update address the faulty screen brightness issue. I read about this fault in reviews of the phone before i bought it. It is still an issue.

2 Likes

I’ve created a support ticket at the Fairphone support for my issue.

Hi everyone,

I’m experiencing an issue with my Fairphone 5 while trying to install a system update (Android 14). The update download always crashes or freezes at the same point, regardless of my efforts to fix it. Here’s a detailed explanation of the problem and what I’ve tried so far:

The Problem:

The system update starts downloading, but it consistently stalls or crashes at the same percentage of progress.

The device is connected to a stable Wi-Fi network, and the battery is sufficiently charged or plugged into a charger during the process.

I’ve recently purchased the Fairphone 5 (only a few weeks old), and there’s plenty of available storage space.

What I’ve Tried:

  1. Couldn’t find the Updater App:

I couldn’t locate a dedicated “Updater” app or similar on my device to clear its cache. If this app exists, I’d appreciate help in identifying it.

  1. Cleared Cache/Data of Other Apps:

I cleared the cache for other related apps like:

Google Play Store

Google Play Services

  1. Restarted the Device:

Performed multiple restarts, but the issue persists.

  1. Wi-Fi and Power Conditions:

I ensured I was on a stable Wi-Fi network. I also tried restarting the router.

  1. Manually Triggered the Update:

Attempted to manually check for the update under Settings → System → System Update, but the crash always happens at the same point.

My Questions:

Is this a known issue with the current software version for the Fairphone 5?

Could this be caused by a corrupted update package? If so, how can I force the device to download a fresh copy?

Are there any other troubleshooting steps I should try?

I’d greatly appreciate any help, as this is preventing me from updating my device. Thank you in advance for your support!

Best regards,
[Your Name]

Can you please define the exact Version you are trying to install?

There have been issues, not sure it was fixed with the Oct patch or Nov. You can check in developer settings if auto updates are enabled

Hi Yvonne,

Thanks for getting back to me! The update I’m trying to install is FP5.UT2E.B.078. Auto Update is enabled, and I’m in Developer Mode. Interestingly, Auto Update helped resolve a similar issue with the previous update (.72) after I had struggled with it for a while.

Cheers
Thomas