I am pretty sure about that. The reason is that Google - as other software developers - always try to avoid regressions at any cost.
Beginning with a certain version of Android, Google required all devices to be encrypted. But this was just mandatory for new sold devices, not for updates of already existing devices.
The reason is simple: Older devices lacked the AES instruction set in the SOC; software encryption would make the devices slow and the battery drain a lot. Regression → Frustration → Problems for all involved parties.
Google requires a specific minimal kernel version for each version of Android. If it is a new sold device. If it is an upgrade of an already existing device, they are not too strict about it.
Reason: The kernel (or better: it’s modules) contain firmware BLOBS which are released by the component and SOC manufacturers for a specific kernel version.
Best example is the FP3: It is running exactly the same kernel version on Android 11 as on Android 13. Google is not forcing Fairphone to update the kernel, but still get the certification.
I am pretty sure, that Google has no problem with the fingerprint reader. It is an upgrade of an already existing device, not a device that hits market initially with Android 13.
So we don’t know why Fairphone disables the fingerprint reader for apps with higher security demand, as the new standards in Android 13 most likely are just valid for new sold devices, and not mandatory for updates.
There is no public issue tracker, no code repository or public road map where decision like that are discussed. Software development at Fairphone happens behind closed doors, and as I already mentioned before, I hope they will tell more about the backgrounds for this decision and the way they are going to solve that.
Once maybe to unlock the phone, and then once each time for maybe six apps.
Each app is checking for security not each other.
As mentioned people can use more than one finger, in fact even the same finger can provide a dozen or more prints. The sensor records some of the print as 256bit or more code and by slightly using a different part of the finger you get a different code.
So if you have problems with the sensor recognising your finger do multiple takes and some when wet etc.
[…] We have stopped the roll-out (at 10%) of the update, for now, to make sure the information for the end users is well-written and clear enough.
I am very sorry for all the people who are affected by the fingerprint sensor problem. I do not use this, so I have no problem with it. But I am frustrated that I can no longer update. When will the rollout start again?
Welcome to the forum.
Like you I don’t use it other than for unlocking the phone, which isn’t affected, however than can be no answer to your question as that depends upon unknow factors.
There are questions:
Has the rollout stopped to provide more info on the download, like a big RED WARNING, in which case it won’t be long but still, if it as ready to relates it would be done. If it’s not ready then we wait for notification and not query why as this just uses more resources of Fairphone
Then of course they could have found a or be looking for a way to enable it’s use which will take some time.
and of course they could be doing both.
However I think the last A11 update has the same security patch 5th June so there’s no worry there: Best check that as I update on the first day, so can’t check.
Also they may be sending it out with the new 5Th July update or even the 5th Aug, if they have to make any real changes, like a also a warning in the OS about the reduced function of the fingerprint sensor
There’s quite a few dislike as to how the GUI of A13 looks and works as well, so it isn’t that big a deal really.
hey amoun thank you for your response. I can understand your description well, however, it is not an answer to my question, and therefore it does not get me anywhere. It is important to say that your concerns are probably not my concerns. I most likely have a different perspective.
I have been waiting a long time for the update to Android 13 that I need. It was announced to distribute it in June. When it comes to adjusting the text in the changelog, this would be a short thing to do (as you write). That’s why I waited a few days now.
Because no date was communicated, I asked. I doubt that I am hindering Fairphone’s process because of this. This is simply my right as a user of such a device.
And whether Android 13 for FF3 is good or bad will be individual, so I ask you not to decide for me from your perspective. I would be thankful for that.