I get the impression that we agree that essential issues have not been resolved. That is precisely why there is a discussion here at the meta level about which thread can be marked as resolved and which remain unresolved.
I apologize, I don’t want to yell at you. What solution do you propose so that users can be warned about the update and those affected who were not warned in time can be helped?
2 Likes
@yvmuell Thank you for moderating the topic. I was also considering creating a new topic specifically for announcements regarding a new A15 version. This discussion is also linked in several news posts, which is probably why so many people are participating. However, as you pointed out: all was said here. I and probably many other people just want to receive news about a new update so a new topic for that would be welcome. Thoughts?
2 Likes
I really understand you want answers, still a new topic will not speed up anything. FP staff is “participating” here in this topic, so any announcement/update will be made here or in the official Software Update topic announcing the fix.
3 Likes
we user here cant do anything more to warn anybody in my eyes. Also the update is out several weeks and I ´guess people updated already, so in my eyes any warnings are already too late.
I really dont see the issue with the solution flag, because with this all important info is visible directly in the first post, so anyone wanting to read about issues before updating can easily find it and is warned.
2 Likes
It is not about speeding up things, but to declutter the inbox of people that are waiting for the update. This topic is a mess and frustrated or lost users are frequently post about other concerns.
I created Waiting for update of FP5.VT28.C.042 . Please do not post anything other than news there.
1 Like
Hi everyone,
Thanks for your patience while we continue to address the booting issue some of you have faced after updating to Android 15.
The problem is linked to a faulty fingerprint sensor. During the staged rollout, we closely monitored reports and confirmed that the real underlying issue was hardware-related. Because of this, we have now put a dedicated processes in place:
Faster identification: our Customer Support agents are trained to recognize this case quickly.
Chatbot support: our website chatbot now collects the necessary information, including address, to speed up the repair process.
Advanced replacements: we’ve also introduced an advanced replacement process for anyone whose device is affected, so they don’t have to wait for a full repair cycle.
In parallel, we have been working with our partner T2M on a software fix. We need to ensure that there are no unintended impacts, so this is taking some time. We will keep you updated on the progress and ability to release a fix.
This way, we’re addressing both the immediate impact (through faster repair and replacement processes) and the longer-term solution (through the software update).
I will post on the forum as soon as I know more.
Thanks for your understanding 
Sarah
9 Likes
At the moment, we can not share an ETA for this but I will make sure to inform you when we have news to share. Our team is currently working hard to fix this.
Please note that for each future software updates, I will post an official post in the forum with all the relevant information.
Thanks for your patience and for being part of this community!
8 Likes
How long does the repair take, where should the phone be sent, and is there a cost?
This is good news to hear. The frustration is this being a phone most of us all bought to last a long time and not replace to already have an issue which means this phone instead of lasting 6+ years, is being replaced after 2.
Has the design/hardware defect been identified and resolved in these new units or can we expect to experience the same issue in a few years again?
1 Like
Hi David,
Restarting 7-8 times in quick succession worked great for me the first time. After 2 days, my battery was empty and the phone shut down. After that, restarting 7-8 times in quick succession no longer worked.
I just kept restarting the phone quickly until it worked. That was definitely more than 20 restarts.
1 Like
Hi all, my phone is facing the same issue. Yesterday it just turned off on its own and is now no longer booting even after resetting for several consecutive times…
If your device already started once under android 15, the “recovery” boot under android 14 will no longer work.
Only if the sensor get working again, even just during the boot sequence, your phone will succeed booting on android (15).
Hello. I have the “fingerprint issue” (I did not know it had one, never used it).
Initially, rebooting multiple times worked. However, I performed the recent (a few days ago) update and did not reboot. Yesterday, I more or less accidentally rebooted and now I am stuck. Does it fall back to the broken A15 because of the recent A15 update?
New support tool for speeding up RMA:
1 Like
Same issue here. Fingerprint sensor stopped working in 08.2025. Current update 09.2025 bricked my phone. Rebooting 7-8 times does not work. Awesome -.-
As others mentioned prior. I bought a FP5 to have a phone that lasts. Broken parts within the first 2 years is annoying. I expect a robust phone, not premium features.
2 Likes
This depends on your specific case. Please reach out to our customer support team
Our team is working hard to create phones that are made to last. Sorry to read about the issue you have experienced and thank you for being a Fairphone community member
1 Like
I have three questions about this Android 15 / fingerprint sensor issue:
-
Is Android 15 still being rolled out over-the-air to Fairphone OS users who haven’t installed it yet?
(Asking on behalf of friends with FP5s running the stock OS.) -
To determine whether the fingerprint sensor is faulty in a way that would trigger this issue, is it sufficient to see whether fingerprint options are available in the settings menus at all (as described e.g. here)? It’s not necessary to try to add a fingerprint (if you have never used the fingerprint sensor and don’t intend to)?
-
Is it expected that Android-15-based /e/OS might also be affected by the same issue?
I realise that /e/OS is not developed by fairphone.com; but I bought my FP5 with /e/OS preinstalled from fairphone.com, and I understand that /e/OS inherits some components (‘firmware’?) from fairphone.com, and the developers that fairphone.com has working on the issue might already know whether the root cause is entirely within those shared components.
(I already tried asking a couple of times on the /e/OS forum, but no response yet.)
Please ask thi the e/OS developer, however I guess the answer is no.
Yes
Well to be sure I would check both. However no guarentee anyone can give you…