Software Update: FP5.VT2F.C.065.20251016 📲

Discuss The Products
, ,
1

Dear Community,

Tonight a new software update for the Fairphone 5 will be rolling out.

Software Version Information:

  • Model: Fairphone 5 (FP5)

  • OS Version: Android 15

  • Software Version: FP5.VT2F.C.065.20251016

  • Build ID: FP5.VT2F.C.065

  • Security Patch Level: 5th of October, 2025

  • Update size (from previous MR): 30.67 MB (30665904 bytes)

Here is a list of the changes:

:hammer_and_wrench: Resolved issues: :hammer_and_wrench:

  • Fixed an issue that resulted in the Dynamic app icons not displaying the correct information for date and time.

  • Fixed an issue where fingerprint haptics were not functioning correctly.

  • Fixed an issue that was resulting in Quickstep (launcher) to quit when using the “Saving app pair” feature.

  • Fixed an issue that resulted in NFC not functioning correctly.

:sparkles: Other improvements: :sparkles:

  • Security patch level: 5th of October, 2025

You can find all Fairphone 5 release notes on our website: https://support.fairphone.com/hc/en-us/articles/18682800465169-Fairphone-5-Release-Notes.

To find more information about updates, please visit this page. You can also find our support article here.

  • Update went well :white_check_mark:
  • I’m having issues with this update :red_question_mark:
  • I’m not able to update :cross_mark:
0 voters
13 Likes
2

Thanks for the update.
Available at 18:00 sharp, no more delays on Deutsche Telekom network apparently.

With sounds and vibration deactivated, there is no vibration feedback from the fingerprint sensor anymore when unlocking (that’s the fingerprint haptics bullet point in the changelog I guess).

But Security Patch Level October 5th on November 17th? Oh come on Fairphone!

4 Likes
3

Installed cleanly on T-Mobile in the US.

4

for me its the same with vibration enabled. Do you have touch feedback enabled or disabled?

5

Touch feedback disabled.

Edit: True, that’s the setting to change it. If I activate touch feedback, it vibrates

6

I hate touch feedback on the screen thus I always have this disabled and think haptic feedback of the sensor still worked till now… so I actually hope its a bug and will be fixed.

5 Likes
7

I can confirm: Even with vibration alarm enabled (but no sound) the haptic feedback of the fingerprint sensor doesn’t work anymore. It worked for the last time before I turned to silent mode. When turning sound back on the haptic feedback didn’t come back.
What is the behavior to be expected? If that is known we can decide if this is okay (and we could wish for a new setting to fine-tune this) or a new bug.
Do I choose that the update went well (what it did so far) or that I have issues (because of the haptic feedback of the fingerprint sensor) now?

4 Likes
8

its at least so far reported as an issue in the beta group and I hope they will not come up to say “you must enable touch sensitivity” to make this work, its intended… on the FP4
btw it still works without this setting enabled.
btw2: I have no idea what the fix was for…

1 Like
9

My fingerprint completely stopped working after the last update. May of course be a hardware issue but still is no good sign for the reliability of Fairphone products.

2 Likes
10

A reboot fixed that for me.

2 Likes
11

Yes. The vibration at pressing the Power Button is finally stopped, when vibration is disabled in the settings. Thanks :grinning_face:

2 Likes
12

Lucky you. Had quite a lot of reboots since then. Including taking battery out and in again..

13

@Fairphone_CM, for at least PT2M after installation, I wasn’t able to enable 802.11 ac and/or ax: [1]

11-18 00:39:10.722 23957  4467 V WifiPickerTracker: Entry 1/4: [StandardWifiEntry][TNCAPD0390D][Disconnected / Disabled][Level:4][WPA/WPA2/WPA3][Standard:4][Saved]
11-18 00:39:12.917  1738   780 D LOWI-9.0.1.89.y: [LOWI-Scan] BSS 00:1e:42:**:**:30 (wlan0) ASSO: NO AddInfo: 0x0, TSF 0, 00:13:13.017, RSSI: -112, CPL: 127, AGE: 696,  SSID TNCAPD0390D, TSFDelta: 0x0, TXRate: 0
11-18 00:39:12.936  1793  2885 V WifiConfigManager: getSavedNetworkFromScanResult Found "TNCAPD0390D"WPA_PSK for TNCAPD0390D[[WPA2-PSK-CCMP-128][RSN-PSK+FT/PSK+PSK-SHA256+SAE+FT/SAE-CCMP-128][ESS][MFPC]]
11-18 00:39:12.953  1793  2885 D WifiNetworkSelector: Networks filtered out due to low signal strength: TNCAPD0390D:a0:b5:3c:d0:39:0d(2.4GHz)-85 / EE WiFi:7a:86:60:80:35:3c(5GHz)-85 / EE WiFi-X:7a:86:60:80:35:3d(5GHz)-85 / BT-C9CMM3:d4:86:60:80:35:3b(5GHz)-86 / 
11-18 00:39:12.955  1793  2885 D WifiNetworkSelector: Disabled configured networks:
11-18 00:39:12.955  1793  2885 D WifiNetworkSelector:   "TNCAPD0390D":27 reason=NETWORK_SELECTION_DISABLED_ASSOCIATION_REJECTION , count=3;

When that resolved, .*RegState also returned =0(IN_SERVICE), but I continue to observe “2147483647” returned as the value for every telephony.registry key. :person_shrugging:

  1. ↩︎
14

Where is the most important part of the update: Fix for the CVE-2025-48593? I’M JUST ASKING!

15

Same here. One day before this update, the fingerprint sensor stopped working, but was still visible in the settings. No more checks, I hoped for the update. However, with the update, the finger print disappeared from most settings, e.g. Device unlock with pin or face recognition only; no menu to add fingerprints. “Fingerprint unlock behavior“ remained switched on.
Rebooted many times, followed a recommendation from older discussions to deactivate “find my phone”, which is now the “find hub”, rebooted again. Still no fingerprint working.

1 Like
16

Almost 100% sure the update is not the cause. Get in contact with support

2 Likes
17

As for most important … do you have any other insight than what I saw cited over in the /e/OS forum? …

“You shouldn’t worry about this. As far as I can tell, phones are NOT vulnerable to CVE-2025-48593. The issue only affects Android devices that support acting as Bluetooth headphones / speakers, such as some smartwatches, smart glasses, and cars. In addition, an attacker has to get a victim to pair to the attacker before they can access the headset service. As long as you don’t accept the pairing request on your smartwatch/glasses/car, you should be fine.”

(GitHub - zhuowei/blueshrimp: Proof-of-concept for CVE-2025-48593)

5 Likes
18

Thanks for the assessment!

1 Like
19

Thanks for good news :clap:t3:

20

This is not exactly an issue, but I noticed a change in how vibration feedback works for the fingerprint sensor now.
It seemed to have stopped working, but it was off because I had vibration feedback from touch interactions turned off.

telegram-cloud-photo-size-4-5827911591930825606-y
telegram-cloud-photo-size-4-5827911591930825606-y580Ă—805 31.2 KB

I guess this makes sense, but I did not mind having vibration feedback always on for the fingerprint sensor, and off for touch screen interactions. Ideally it would be two separate settings.

6 Likes