| 29 Oct 2024 |
 oak 🏳️🌈♥️ | https://source.android.com/docs/security/features/authentication/fingerprint-hal | 00:54:36 |
 @samueldr:matrix.org | if you poke around in the different packages, you might see an activity related to fingerprint stuff | 00:54:43 |
 Atemu | Could grep for that permission string on the official android image hmm | 00:54:45 |
| oak 🏳️🌈♥️ | It's pretty well documentated | 00:54:52 |
| Atemu | s/permission/intent/ | 00:54:53 |
| @samueldr:matrix.org | also that intent could/can be scanned by software | 00:55:02 |
| @samueldr:matrix.org | https://github.com/SimonMarquis/Android-SecretCodes | 00:55:21 |
| @samueldr:matrix.org | (could) | 00:55:23 |
| Atemu | Right but we do want the OEM service in this case | 00:55:42 |
| Atemu | * Right but we do want the OEM service menu in this case | 00:55:46 |
| @samueldr:matrix.org | probably something like that if it exists | 00:56:01 |
| oak 🏳️🌈♥️ | If you look at the Fingerprint HIDL link I posted, it quite nicely shows what all are the compontents related to that | 00:56:03 |
| oak 🏳️🌈♥️ | fingerprintd is standard component provided by AOSP, but the FP vendor library is provided, well, by the vendor | 00:57:30 |
| Atemu | Thanks a bunch for the pointers so far though! I'll have a look at all of them tomorrow and try to figure out what and how my fingerprint reader broke. | 00:57:50 |
| @samueldr:matrix.org | Atemu: and that activity launcher app filters activities in packages too, so e.g. finger will find the fingerprint-related ones under settings | 00:57:56 |
| oak 🏳️🌈♥️ | I hope the issue is not inside the closed source binaries | 01:00:02 |
| Atemu | In reply to @samueldr:matrix.org
Atemu: and that activity launcher app filters activities in packages too, so e.g. finger will find the fingerprint-related ones under settings Yeah it didn't like that ^^' | 01:00:15 |
| oak 🏳️🌈♥️ | I wonder if the FP vendor library sources are available | 01:00:27 |
| @samueldr:matrix.org | oh, yeah, launching random activities might not work when they require params | 01:00:31 |
| Atemu | It's also not like the settings are at fault, this is almost certainly just the settings reacting to biometrics not working at a lower layer | 01:00:46 |
| @samueldr:matrix.org | yes, was about to say; it wasn't meant to imply that the settings page are to be looked at, but an example that it will filter "deeper" than package names | 01:01:23 |
| Atemu | In reply to @oak:universumi.fi
I hope the issue is not inside the closed source binaries Given that it also affects stock ROM... | 01:01:32 |
| @samueldr:matrix.org | it sure smells fishy | 01:01:54 |
| oak 🏳️🌈♥️ | It might be that the problematic code runs inside TEE | 01:02:03 |
| Atemu | Ohoh | 01:02:13 |
| Atemu | That could also be a state that I'd wipe by wiping userdata, huh | 01:02:32 |
| Atemu | Because android would presumably re-init TEE state when it's got a clean slate | 01:02:54 |
| oak 🏳️🌈♥️ | Yeah it probably resets the Keystore / Keymaster at least | 01:04:12 |
| oak 🏳️🌈♥️ | Fairphone has Qualcomm chip so they are probably running QSEE | 01:04:32 |
| @samueldr:matrix.org | that fairphone? (I forget which model is the latest) | 01:05:01 |
