adding fingerprint ID does not respond
-
When checking dmesg, there are some messages:
init: Control message: could not find 'android.hardware.biometrics.fingerprint@2.1::IBiometricFingerprint/default' for ctl.interface_start from pid: 37 (/system/bin/hwservicemanager)
-
@sonohgong
Same for me, and probably it is a hardware fault. Never worked for me ( devel and RC and stable ).
Never tried on Android -
I could reinstall Android 11 and test if the fingerprint sensor works, but I'lld like to be more sure that it could be a hardware problem before spending time on that.
Is there any way to diagnose this further from within UT?
-
@sonohgong I'm not aware any other ways to debug this in UT. It's a good practice to check functionalities on Android before flashing UT
Hopefully, you can sort this out. Maybe there's a manual flashing instructions and try that? -
@sonohgong
There is sensorsstatus app in openstore for this kind of purposes but sadly it doesn't support fingerprint sensor for now...https://open-store.io/app/sensorsstatus.chrisclime
Maybe the time to add and enhancement issue ^^
-
I installed Android and tried fingerprint sensor with both 11 and 12. It all works, so it's definitely not a hardware issue.
Since I need this I'm back on Android, it seems UT isn't for me yet
-
@sonohgong ah interesting. But why it works for most users then ?
I should try too Android again and go back to UT afterward to see -
@sonohgong
Confirmed, i've installed Android 11, setup a fingerprint there, was ok.
Then installed UT and i can set up a FP now -
Same problem. Latest version of focal.
Fairphone 4 6g version.
-
Hello,
I can confirm that the fingerprint reader of a fairphone 4 does not work when using it for the very first time under UBPorts.
What I did is:- I reverted to Android 11 and registered a fingerprint successfully,
- I re-installed ubports and was able to register several fingerprints successfully.
My guess is that the finger print reader requires a firmware upload of some sort, at least once, that the android driver provides but the ubports one does not.
I tried to open a ticket for this but gitlab is asking for a bank card to register new users… so I won't.
Could someone with a gitlab account be kind enough to submit the bug please ?
Cheers,
-
@Papa-Emeritux I actually have recent experiences on this on both my Fairphone 4 and 5. I encountered this issue on my Fairphone 5 when I first flashed UT. However my experience went a bit differently. I had registered fingerprints on Android and I flashed UT over Android 14. So I thought that was the reason. I reflashed Android 11 then reflashed UT and fingerprint started to work. Note that I didn't register a fingerprint on Android 11, at least that's what I remember.
Now, just 2 days ago, I flashed UT on my new Fairphone 4 and again, I had registered fingerprints and also experimented on flashing UT over Android 13. It actually didn't even boot this time so I reflashed Android 11 then reflashed UT again and fingerprint just worked. This time I'm 100% sure I didn't register a fingerprint in Android 11.
So my conclusion is that the most likely step that fixes this is reflashing Android via Fairphone's official script. Perhaps it does something that resets the fingerprint or something.
-
@kugiigi said in adding fingerprint ID does not respond:
Interesting, thanks a lot for sharing.So my conclusion is that the most likely step that fixes this is reflashing Android via Fairphone's official script. Perhaps it does something that resets the fingerprint or something.
Could it be the Android 11 image provided by fairphone ?
In any case, it would mean that something is persisting from Android (on the disk?) through the UBPorts installation process.
Mystery…
