pro1x issues

[SkewedZeppelin]

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 #340 (comment)

[SkewedZeppelin]

@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: Remote hardware attestation #46 (reply in thread)

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]

@goshuberto just to clarify you're having 3 issues?

Actually 4; thank you very much for your attention. The 4th is the inability to use SeedVault in secondary profiles, but this is an LOS upstream problem (reported here: https://gitlab.com/LineageOS/issues/android/-/issues/7747)

• 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

Will do asap, eta. by next weekend.
I don't suspect fingerprint hardware blobs are missing, but any of the TEE/SEE trusty-kernel-2-kernel components.
The enrollment fails immediately, even before any 'scan' attempt happens.

• some wifi channels unavailable

  • do you have a sim in your unit?

Yes, I tried two different SIMs from countries allowing channel 1-13.
If the basestation uses channel 12 or 13, DOS can't find/join the BSSID.
Other channels work fine/reliably.

I'm quiet sure I joined with LOS installed (same device) successfully on channel 12/13, even before inserting any SIM. But would need to verify (which is a hassle because I can't restore 2ndary profiles). At least with a SIM of a german carrier inserted I can join on LOS without problems, even after removing it.

• 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: Remote hardware attestation #46 (reply in thread)

besides an issue tracker.

except an issue tracker is the best place for documenting such issues

I need to learn more android internals to help tracking this issue.
The boot loader of my fxtec wasn't locked from factory, so at least it wasn't me who 'unlocked' it...
But I missed running the KeyAttestation test app before flashing DOS/LOS :-(
Will do a factory-stock-reflash using EDL as time permits and try to get the device back into a state passing the key attestation test. And see what happens from there after flashing [DL]OS.

XMPP successfull

it is in moderated mode due to on-going network wide spam, you can post your username and I'll approve you

Oh, ic. unfortunate 'conversations' doesn't tell me "moderated", but a just a general error...
Thanks for approving huberto (be3.ovh)!

[goshuberto]

Thanks for your ongoing effort in rebasing DOS onto LOS21. Read about experimental builds in your news section.
I'd be very happy to test on pro1x. I have 2 devices in 'spare' state - this allows me to compare. No build env here, not much time an even less bionic/Java skills, so can only play the tester role. - Focus: FP-reader issue, 2ndary-user Seedvault support (recent upstream fix has landet allowing 2ndary profiles to selet seedvault as backup priveder at least), TEE/SEE support, working international 802.11xxx support.
Best regards,
Huberto

P.S. I still couldn't manage to get 'conversations' working - Certificate error... No use for XMPP here otherwise so wonś spend time on that... Hope my donation arrived in full, Liberapy split it into monthly remits as far as Iḿ aware - and took a good share of the 100 bucks... Discontinued the Liberapay donation, too many surprises

[SkewedZeppelin]

Thank you for the donation.

Hopefully these issues will be fixed along with the rebase, otherwise I'm out of options.

[goshuberto]

I can confirm that the fingerprint reader worked without any issues ever since I installed LineageOS 21 on my pro1x - Augst 24 build I afair.
The hotspots using channels above 11 also were accessable with LineageOS 21, when DivestOS wasn't able to even scan the BSSID (like mentioned, it's a regulatory mismatch to my estimation).
And with build 20241216 I can confirm that 5265fbf082694a19a4baccb811505a18810d2d94 (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/380205) solved the problem that SeedVault wasn't available as backup provider in secondary profiles. Works now, which is a ultimate must-have in my opinion.
Is there any way for me to get an experimental build for the pro1x?

Thanks!