Update went smoothly - with a strange side effect:
My system language was changed from German (first) and English (second) to “Und - Not available as system language”, which set the actual language to default English.
After having re-added German as first language and English as second language everything is back to (my) normal. (“Und” can be removed via the three dots in the top right corner.)
Can anybody confirm this bug?
I ran the update last night, checking it now it still looks fine, without adjusting it:
Edit: Bit different from your setting, just realized.
Besides, also no issues running the update.
Hello, update went smoothly here.
No changes to language settings to report.
2 posts were merged into an existing topic: FP Security Updates need to be more frequent
Yes, update went withouth issues here, too.
Again disappointing, though, as Fairphone has still not managed to bring Always On Display back after they successfully solved the display issue about it. When are we going to be able to use AOD again??
I’m still waiting for the update to become available 
I also had a strange language change anomaly after this update. Got an extra language in SwiftKey keyboard app: Abuan (the first available language listed there).
Anyone else still waiting for the update? It’s been more than a week since it got released to the public.
Hi @Ioiana_Luncheon, maybe you can tell more about this update? All my colleagues also don’t have this latest update available. We’re still running the February update and we’re nearing May. It would be nice to at least be able to install the available update.
As far as I remember its not the first time you get updates delayed and we know this is in general provider specific and the provider can also be the culprit. So did you contact you provider as well?
I asked my provider before, they said they don’t have the ability to manage/hold updates.
I think it’s a process Fairphone controls. Like during Christmas when something in that build/test pipeline wasn’t working well and after some complaints they had a look, fixed the checks and updates became available.
It’s better to ask then to guess what’s going on I think. I also don’t know of other Android phones that have this issue.
We have examples were indeed it was the provider causing delays due to delayed internal tests. Btw which provider are we talking about?
Beside this is anecdotal evidence I dont think its relevant
Internal test on the FP side? Or really on the telecom provider’s side? Because I’m not sure anymore which one it is. Especially since this issue isn’t that visible with other brands. And since my provider replied before they don’t have control over the update process.
But I can ask them again. I’ll probably get a reply sooner from them then from FP anyway.
I’m using one of the largest telecom provider in The Netherlands. So even though it’s indeed me once again complaining about this here, there are many more people hit by this delay.
Hi UPPERCASE,
AFAIR you are on D1 Telekom Germany like me, I’ve got this update on the first day it got published.
That’s not a Dutch telecom provider. It doesn’t really matter which one I use. Fairphone should release the update in a consistent way for everyone or be more transparent about it. Then people don’t have to guess or bother them with this.
No update here by the way 
For sure it matters which provider you use, else no one can check for reasons and provide answers. And again also the provider has to do their job and test to ensure updates work properly in their network.
No it doesn’t matter. Do you really want everyone to contact Fairphone each time this happens? That doesn’t scale well and FP cannot use that extra load. They should aim for a consistent release and provide a list of providers that are delayed, if any. An ETA would be great as well.
Thanks for the info! In the past FP was able to solve issues in the test pipeline as well. So my guess is that the tests are running in the FP infra. While the test themselves are provided by the provider probably.
Fairphone already doesn’t perform well with their update schedule, these delays make it even worse. The update is available, but still not for everyone. This issue is less visible with other Android devices, I don’t even know if it happens there at all. There is room for improvement.
Just as a ref: I got FP5.UT2L.B.107.20250218 (released on march 10th) on my fp5 on Proximus I think around april 8th
Nice! But now we’re both waiting for the next update that was already released 