SkewedZeppelin
commented
1 month ago @goshuberto just to clarify you're having 3 issues?
- fingerprint reader not working
- no fingerprint blobs are removed, it may be an issue with the fp hal being incompatible with some other change
- can you perhaps try the log steps and see if any of them mention fingerprint or biometrics:
- adb logcat -b all -d | grep -i -e dlopen -e "cannot link"
- adb logcat -b all -d | grep -i -e hardened_malloc -e "fatal allocator error"
- adb logcat -b all -d | grep -i audit
- some wifi channels unavailable
- no wifi related blobs are removed, but I've heard reports of similar channel issues. I've tried to see about adding a manual override but it seems there is no good way to do that.
- do you have a sim in your unit?
- attestation unavailable
- this could potentially be a deeper issue and why fp reader doesn't work or it could actually be this other unrelated issue in which case after unlock that attestation becomes impossible: https://github.com/Divested-Mobile/DivestOS-Build/discussions/46#discussioncomment-2263154
besides an issue tracker.
except an issue tracker is the best place for documenting such issues
XMPP successfull
it is in moderated mode due to on-going network wide spam, you can post your username and I'll approve you
goshuberto
Hi! I'm still new to DOS and tried to get in contact (by donating via LiberaPay, which doesn't allow to attach an telegram :-( Nor was my attempt to join via XMPP successfull, likewise my post in the XDA Forum for the pro1x device). Please remove non-working contact options, it's wasting a lot of time).
Back to topic: At lease for me the root cause is a wrong country code (for the 2.4GHz spectrum). Usually at least a european SIM should advertise the correct bandplan allowing to use channels beyond 11 - which works on LOS. But DOS can't join/see base stations transmitting beyond channel 11 (somehow e.g. Android-Hotspot selects channel 12 for no good reason - surrounding bssids use 1/5/9/13 pattern (only obsolete 802.11b had 22MHz spectrum per channel, we can use 4x 20MHz wide channels in europe with the 1/5/9/13 pattern)! The bad habit of using 1/6/11 pattern is commonly known by other vendors, but completely ignoring the environment and transmitting copmpletely out of pattern is a poor jamming feature of android).
To me, this looks like a deblobbing fallout... Just a guess!
Offtopic again: Likewise the problem with the finger print reader on my QX1050. It's working fine in LOS, while rollout fails on DOS. Even worse, it looks like the TEE keystore isn't available on DOS on my QX1050/bengal/662 from a very brief look, without inspecting any code (besides flying through deblobber.sh). Unfortunately I don't have any android dev env here, nor much time or other junctions to AOSP - I'm happy consumer of GOS out-of box on my pixels.
Anohter severe issue for me is that the Android Key Attestation Test App (https://github.com/vvb2060/KeyAttestation) fails on my QX1050. Im not an expert regarding StrongBox/TEE attestation, nor on bengal/Qualcom at all... But currently I must assume that keys can't be stored in a secure way on DOS, which seems to be the root cause for the failing FingerPrint roullout.
I'd highly appreciate if we can somehow find a way to get in contct besides an issue tracker. I also highly appreciate your DOS work!
Originally posted by @goshuberto in https://github.com/Divested-Mobile/DivestOS-Build/issues/340#issuecomment-2410402661