Is there a way to check which apps have this requirement? One of the multi-factor apps that I need for my work only supports fingerprint access; if that stops working I’ll be forced to get a new phone.
I only know 3 people with FPs who would buy so I would image the cost would not warrant the ‘few’ buys
The “Fairphone community way” of doing this is to create a wiki and have people report their findings.
I’ve just prepared such a topic with the findings from the beta group:
Seconded. I would (kinda) happily upgrade the fingerprint reader if it restored the functionality present on Android 11
Not only fingerprint, BT also makes now problems.
How can I roll back zu Android 12?
Welcome to the community forum.
There was no official Android 12, the Fairphone OS upgrade went from Android 11 to 13.
Manual installation is still available for Android 11 (as well as 10 or 9) …
@Marta_Artigas Does FP consider the possibility of writing your own firmware for the sensor that would raise its trustowrthiness? Or is the reason Google doesn’t trust it somewhere in the hardware and thus not fixable on the current hardware?
With users having the option to stick to Android 11, will you keep sending security updates for that version as well?
Welcome to the community forum.
If the last years with prior Android versions are any indication, security update support for base Android 11 will end somewhen in early 2024.
Might be enough to bridge the time to the Fairphone 5 probably, but whether Fairphone have the resources to service 2 Android versions simultaneously, I don’t know.
(I don’t use the fingerprint sensor at all … and even if I would, I’m not using Fairphone OS, on custom ROMs not bound to Google certification the fingerprint sensor continues to be accepted as before. Banking Apps might not like custom ROMs, though. Tough call then.)
This is not true.
I have to use an app for authentication when logging in to certain webservices. It is only possible to use this app using my fingerprint and not by a pin or password.
This is a real problem for me and i dont have the time to backup all data on my device, so i can also not easily go back to version 11 without losing data…
Would you mind adding it in the wiki below once you reach the basic “trust level” to be allowed to edit wiki posts?
Is there no option with the app in question to reset, not use a fingerprint and use a code etc.
What app is this you are using?
No it is not possible, it requires a fingerprint sensor to work.
The app is called “Digitales Amt” and is used to access services related to the government. This also includes financial services from the government which makes it super annoying that it does not work…
it’s also used for digital signatures that i use very often.
This means, that this information will be better communicated to the user. That’s good. But it is not a solution to the problem.
Will there be any solution at all? Maybe by rolling out a different firmware to the fingerprint reader? Or a user-selectable switch to accept not-so-safe fingerprint readers for all apps?
Or anything else?
Any information about that would be helpful and end speculations.
Thank you very much!
Before people start downgrading by themselves … can anyone can say if the anti-rollback mechanism that bricked some FP4s now affects the FP3/FP3+ on Android 13, too?
hmh I am not sure but I suppose this firmware for that fingerprint reader is closed-source and not openly available source code. So fairphone might not have any rights to release modified firmware.
But regardless of that:
Since these security measures are implemented by Google, I can’t imagine how Fairphone could get around these security decisions without loosing Google certification and thus all Google-related things like GPS (Googl Play Services) and GMS (Google Mobile Services).
I use the LineageOS fork iodéOS and so far all my banking apps are working flawlessly even with fingerprint and Magisk Root activated.
But that might depend on every specifiv app, of course.
I agree, that’s what I am thinking, too. But still: We are just users, speculating. Would be nice to have an official statement, how Fairphone will continue with this issue.
In the end it is as simple as that: We need a solution.
It would be helpful to nonetheless quickly release the manual install file for Android 13 (perhaps with a link to this topic here for a warning) … https://support.fairphone.com/hc/en-us/articles/360048050332.
Since a number of users have upgraded already and are experiencing other issues apart from the fingerprint sensor situation, a manual install from scratch could be used to determine whether certain issues are really due to the Fairphone OS version itself or rather due to the in-place upgrading process.
for those wondering about custom ROM