FAIRPHONE 3 and 3+ A13 - Fingerprint sensor update

I don’t think this was managed properly at all. It is clear that a lot of people will have internet banking etc. on their phone. So this will hit a LOT (most?) users badly. As a software engineer myself I can recommend a better way for a software release which is used by a lot of users.

  1. try with a small user base ‘friends and family’
  2. larger user base of alpha testers
  3. even larger user base of beta testers
  4. general rollout.

If there are issues raised by the alpha/beta testers (as was the case here) there MUST be an easy automated rollback procedure which does not involve data loss or configuration loss.


It won’t be ‘solved’ in the next months, if at all.


This is an absolute disaster indeed.

To all of you who followed this story like me since the beginning, how do you feel about knowing that new people arrive on this topic everyday, because they just updated, then noticed that their stuff didn’t work anymore, and just learned that they’re sh*t out of luck?

I feel absolutely disgusted. And just thinking that they regret doing the update and that they’d just like to downgrade, but they can’t without wiping the whole phone (and wasting hours doing it for the non tech-savvy…)

We NEED to do something about it. To anyone here having any relation with FP employees, make them read this topic so they’ll hopefully STOP the bleeding and cancel this update. You CANNOT expect people to read the changelog about some disappearing feature!! :rage::sob:


I think there were other very serious issues with the A13 upgrade. Videos don’t pay properly and the only solution appears to be to take the battery out and reboot. But I won’t write anything here I give up - very disappointing. As far as I can see there was no urgency to do the A13 upgrade at all I only did it because I was prompted.

1 Like

Then could you please apply to Google, get employed there and fix this in Android? A lot of people worldwide would be thankful.
Or contribute this for free to the Android base, it’s Open Source.

You are a software engineer?


3 posts were merged into an existing topic: FP3+: Issues with Android 13 update

@AnotherElk your comments are not helpful. Sure I’m a software engineer but I paid money for the phone and expect a properly managed test and release process not a new hobby. Blaming google is not the way either or are you seriously saying that every other A13 phone is also broken?


I seem to be one of the lucky unlucky ones here.
I have the issue with the Austrian government app. I was unlucky that my release notes did not include the warning about the feature. And I have the weird SIM PIN issue.
Sadly I am really limited in my choices because I want a phone with removeable battery.
I think my plan is to wait for a month or so and then do a rollback to A11. Nothing of value should be lost. Alternatively I could switch to Lineage and try out to circumvent the root checks in my banking apps and in the government app.
But I have to say the rest of the update works really well for me. The phone seems faster. The battery seems to last longer. Most of the other stuff I use regularly works fine. Even the keyboard seems to be more pleasant to use.
As I said I am lucky.
I might be disappointed in FP and their decision and the lack of communication.
But I might be also a bit frustrated given that they announced a week ago that they would support FP3 till the beginning of 2026. Which would be awesome, except the thing we are all talking about.

Before Elk asks, I am not a software engineer. I am a software tester. :slight_smile:
I did not know that they have open calls for testers. I might even answer the call the next time it comes around. Thanks for sharing that information.


Ahh… That’s why it doesnt work any more with some apps… Good to know. Even when it is a bit late for it…
May I ask if NFC is influenced by this too?
Is there already a workaround for this issues?

As you can see from the citing I was commenting on the rollback part.
Android doesn’t have this.


This is what makes me the most angry. I’ve read the notice about the fingerprint scanner out of sheer luck, because it was at the end of the update notice, grouped with “extra stuff”, about 50 messages ago, people have kept coming to complain here about the lack of communication and today I still got another notification about the update with still no mention of this issue. At this point, I just assume it’s done on purpose, to show the number of updated phones with total disregard of how many people are going to lose access to extremely important apps. And it does a good damage to my opinion of the company (my willingness to buy another FP has gone out of the window earlier this week).


I have exactly the same issue. So, I can’t use the fingerprint sensor even for unlocking my FP3+.

Have you been able to resolve the issue somehow?

1 Like

Unlocking works fine and a lot of “low” security apps work fine as well.
Linked to this thread is a lsit of all known apps which do not work as before.


I really, really hope that this is a path leading to a solution for the issue. Would be nice to get a statement from FP regarding the viability of this approach.

1 Like

Hello everyone, thanks for all the messages. I would like to add to this discussion a bit from our side. I’m Miquel Ballester co-founder and Head of Product of Management and together with the Software Longevity team we work on our software updates.

Let’s start with a quick summary for new readers:

Since the update to Android 13 for Fairphone 3(+), the fingerprint sensor at the back of the device can no longer be used to log into certain apps with higher security requirements, such as some banking and government apps. This is because of updated security requirements for Android 13, which has lowered our sensor’s security certification from Class 3 to Class 2. This is very common as phones become older. After all, software upgrades will always align with the latest tech available in the market. However, there is no need for alarm. A Class 2 certification is still quite strong and will allow your fingerprint sensor to work normally for a multitude of apps. For apps that require a higher security certification for the fingerprint sensor, you can still access them through a PIN or passcode.

We want to again sincerely apologise for the oversight on our part in communicating this issue before. As we said already, we were aware of this issue before starting the roll-out of the latest update, but failed to include it in the release notes the first time.

These are the actions we have taken to minimize the effects:

  1. Once we realized this, we stopped the rollout of the update on the 11th of July. Only 10% had got the update until then.
  2. We updated the release notes and published them again.
  3. We resumed the rollout on the 17th of July

Noticing this is not enough information, on 28th of July:

  1. We are updating the notification that users see before they accept the download to warn them about this regression.
  2. We are updating the release notes to provide clearer communications on the regression for people downloading the software update.

One thing to keep in mind is that although biometrics (fingerprint) are more convenient, they are potentially less secure. It’s never as safe as logging in with a strong password, which is an option that remains available for nearly all apps. This is documented in the official documentation of Android, please see here. Android states that:

“in the tiered authentication model, pins, patterns and passwords are primary authentication and they provide the highest level of security. Biometrics are the second tier of authentication and offer security and more convenience”.

Despite the previous statement, some apps only use biometric authentication to login.

The apps that lost access with the fingerprint sensor are exactly those with the highest security requirements (like banking apps), here’s a list of all the apps and their status for fingerprint support (thanks Ingo and to everyone who updated the list). We are sad to lose this convenience feature on those apps, but it is the right thing to do to keep these accounts as secure as possible. You can still access your accounts via login methods that are more secure than using your fingerprint, like passwords.

Every iteration of fingerprint sensors and chipsets makes progress and offers higher and higher levels of security. In our Fairphone 4, we could implement a newer, even more, secure version of fingerprint sensors and chipsets with higher standards of security. This is why we can still offer to log in via the fingerprint sensor on those apps with the Fairphone 4.

While this development is not something we are happy about, please do understand we are trying our very best to future-proof our phones as best as possible. Like the later software updates for Fairphone 2, this is the first upgrade we’ve completed without the support of the chipset provider and that comes with its own set of teething problems. With our unique approach to software, we are challenging the industry every day, going way beyond what our other brands and partners are doing.

This way of challenging the industry standard comes with risks and regressions that are sometimes beyond our control. Sometimes, like on this occasion, we reach a hard limit that isn’t resolvable from the technical side. Despite this major regression in Android 13 for Fairphone 3, our users get much more from us than they would get from any comparable device on the market of similar hardware and age, as we are already offering software updates since its launch in 2019.

Having said that, we would like to profusely apologize once again for not communicating this clearly in the release notes. We should have been more proactive in letting you know about this development and it is something we will be more actively concerned with in the future.

I hope this answers your questions. And thanks all for being so engaged in the conversation.


In case it helps, here we include as well some FAQs:

What exactly is causing the issue with the fingerprint sensor?

Due to updated test requirements, Fairphone 3’s fingerprint sensor is now certified at a lower security standard, according to Android’s security requirements. We cannot get an updated firmware from the fingerprint sensor supplier, in order to increase the level again. Android biometrics security requirements are continuously increasing to stay aligned with latest research in the field, for example on reproducing someone else’s fingerprint to log into their device and apps.

Could Fairphone have prevented this?

We could have written the explanation proactively for the end users.
We are also having conversations with all our software and hardware suppliers to get their support for a longer time for our more recent products. On Fairphone 3, unfortunately, the manufacturer declined to offer us long-term commitment for firmware support.

Why wasn’t this issue included in the release notes?

We were aware of this issue before beginning the roll-out of the latest update, but failed to include it in the release notes. This is a major oversight and should not have happened. We realize that we need to be more proactive about how to communicate and present known issues/regressions and potential workarounds before releasing updates to the public.

That said, this only affects apps with higher security requirements, like banking apps. In general, you can keep using the fingerprint sensor normally.

If Fairphone was aware of this, why did you choose to release the update, anyways?

Some workarounds could be put in place, see the section “What do do for the affected users?”. This is not convenient for the users using the fingerprint sensor with some apps, but they can still use those apps, unlocking them via PIN/password. In this case, we prioritize continuing software support despite losing this feature.

If the fingerprint sensor is certified as “weak”, does this mean it is not safe to use / wasn’t safe to use before the Android update?

Android security requirements changed with Android 13, which require changes in the firmware of the fingerprint sensor. Because of the lack of this firmware update, the fingerprint sensor could not be qualified “Strong” anymore and “Strong” could be a prerequisite for some apps to use it, like the banking apps. Weak is one of the categories of the Android Compatibility Definition Document (CDD) which evaluates the security of a biometric implementation. The Biometric Class “weak” (called class 2) now is considered “secure” but not secured as the Strong level, see the Android specification (the table below describes each class for new Android devices). Biometric security is classified using the results from the architectural security and spoofability tests. A biometric implementation can be classified as either Class 3 (formerly Strong), Class 2, (formerly Weak), or Class 1 (formerly Convenience).

Will I no longer be able to access my banking app / other apps that I usually use the biometric login for?

All apps that offer biometric login also offer the option to login using your password or pin code. This issue, therefore, does not mean you will not be able to access your apps at all.

(When) will you fix this? Is there a workaround?

Fix not, workaround yes: Affected apps can still be unlocked via PIN/password, which is by default configured as a fallback option in any context that makes use of the fingerprint sensor.

(How) can I go back to Android 11 to get the functionality of the fingerprint sensor back?

Going back to Android 11 will not solve this issue: Android 11 will eventually run out of security support. Apps with high-security requirements won’t work anymore at that point – these will be more or less the same apps that require strong fingerprint security. As a temporary workaround, it is, however, possible to go back to Android 11. Please see https://support.fairphone.com/hc/en-us/articles/360048050332 for instructions on how to manually install older Android versions.

Will the fingerprint sensor on the Fairphone 4 stop working as well, once the Fairphone 4 receives the Android 13 update?

No, as the fingerprint manufacturer for the Fairphone 4 didn’t drop the support. We’re also already preparing now to avoid similar situations for Fairphone 4 as much as possible.

I use another alternative operating system on my Fairphone 3/3+. Will this issue affect me as well?

Yes. Alternative operating systems all use the same fingerprint firmware as our official software, since there is no alternative or open source firmware available for Fairphone 3’s sensor. Therefore, in terms of fingerprint detection and spoofing security (reproducing someone else’s fingerprint), other systems will be as secure as our official one.


The “Digitales Amt” app, which is necessary for citizens in Austria, works exclusively biometrically. It is necessary in order to submit applications and communicate with authorities. Therefore, the phone is now worthless. You admit that your supplier did not inform you in time. This is your legal issue. So what to do? Throw away the sustainable Fairphone? As a result of the violation of the duty to warn, better find a solution or at least make an offer.


So you feel any possible commitment oft your supplier to provide an Firmware Update once?

Hey there,

As we explained in the post, that app does not follow the recommendations of Google. By only allowing to use biometrics, it is closing the door to other more safe ways of logging in, like a password. I hope you will continue to enjoy you phone for other uses for a long time. We will keep providing software updates, beyond any other brand in the industry. Thanks


We have been trying for months now. Unfortunately, one of the bottlenecks in the industry, as component manufacturers are not used to provide long term commitments. Sometimes our drive for longevity wins, but sometimes it doesn’t. I hope for your continued support, thanks for engaging in the conversation.


If you are referring to whether LineageOS, for example, now also classifies the fingerprint sensor as Class 2: No, it doesn’t. LineageOS has reverted the commit that would implement this security check: