I don’t endorse them, but for me it would be cheap enough to not worry about if it doesn’t help. I would test it if I could but my only interaction with Austria is ÖBB and of course your wonderful pastries and cakes.
As an self-employed IT-Security Expert with a Bachelor’s and a Master’s degree (in IT-Security) and more than 15 years of experience in the field, I am confident to assert that the claim of “biometric factors (fingerprint, face id) being less secure than knowledge based factors (pins, passwords, patterns)” is factually wrong.
Without wanting to become to technical, it depends on multiple factors, including the aforementioned quality of the sensors.
On another note: Maybe I have overread it, but would Android 12 also be affected from this issue?
PS: Maybe Fairphone should maintain lists of critical and important apps to test against to prevent this in the future.
I have been following the thread on the fingerprint sensor with interest. I use the fingerprint for many apps and find it very convenient. However, I tested all my banking and authentication apps before updating and found they all seem to work OK with a 6 digit pin code which is not a really big hassle. So I have decided to take the plunge and update to Android 13. I can live with this for the time being on my Fairphone 3 (which I’ve had for nearly 4 years). The phone is generally a bit slow for a lot of apps these days, so I think I’ll need to change it before too long, so this situation will only be temporary for me. I’ll wait for Fairphone 5 and consider that alongside others when I am ready to get a new phone.
Re various apps, I have tried all my banking apps (Co-operative, M&S, Smile, Nationwide, John Lewis Credit Card), which now require a pin instead of a fingerprint. Microsoft Autheticator still works with fingerprint. I also tried credit reference agency apps - Clearscore still works with fingeprint but Credit Karma and Experian now need a pin. I will add to the wiki when I get time.
I forgot to disable automatic updates in the developer options, because they where not activated on my phone. I’ve interrupted the update while downloading and switched it of in google play, But it was to late! During the night my FP3 did a reboot and woke up with A13. Now I am experiencing all the trouble mentioned in this topic.
Hello,
I would just like to clarify one point. The A13 update has a major impact on applications using the fingerprint reader.
Just to be sure, will there be a software patch provided by Fairphone or another company to fix it or the fingerprint reader of the Fairphone 3(+) is unusable and will never be compatible on A13?
In this case, if you want to be able to fully use the fingerprint reader, you would have to rollback to an earlier version of Android?
Finally, according to this thread from July 13th this update has been discontinued, so how could I have started the update yesterday, July 31st with this major issue ?
The update was only discontinued until a warning was placed in the release notes. As the problem comes from a degradation of safety class by Google and no support from the finger print sensors manufacturer, there will be most likely no update for this issue.
Thanks a lot, yesterday evening I already ordered a Fido2 token, one that was recommended by ID Austria. It should arrive at Thursday. If it works fine I might buy a second one, but now I first wanna test it.
I can understand that if you have no experience so far with a custom ROM. But what’s the risk if you really consider switching to a different device (which you still can do if the custom ROM does not meet your expectations).
There’s no guarantee. But most or all should work.
I too will go with a FIDO token.
But I will also get myself a cheap second phone for authentication purposes till everything is set up.
Also having a second phone as backup, if I start experimenting with Lineage is a good idea.
I will report back.
iodéOS also has a long list of apps that work/or don’t fully work with their operating system (which is also based on LineageOS) - I recommend to take a look there too:
