[Magisk] pndwal:
and I felt you only want to answer some questions as I had to ask more than once... 🙃

But you hadn't clarified... maybe in your mind...

Since you're still not letting go of assumptions I'll explain further, despite it being a circular argument... 😝

If you check Google Pay discussion thread you'll see many members had USNF + added a mismatched fingerprint (globally applied) using MHPC long before @Displax's USNF mod w/ (partial) Play Integrity fix (which does the same thing but targets gms) even existed (and @Displax was watching these developments in that thread), and that many continue to use this setup... You DID NOT state you had @ Displax (targeted) mod EVEN WHEN ASKED, and as you said you used MHPC in conjunction with USNF it appeared that you were likely passing deviceIntegrity verdict this way, like many others... - Not sure how more clear I could be than that...

I already covered why I wasn't sure you actually had L1 at that point since you never stated that plainly and you only said "Netflix is ok" (many users consider Netflix works fine w/ SD having never had L1 compatible hardware anyway)... Further, you didn't state how you were seeing "it goes to L3 with bad quality streams" despite my asking. (Thinking: 'perhaps you see L3 somewhere (where?) but never actually had L1 since streaming didn't even work w/o liboemcrypto-disabler mod')...

Well that's not really the purpose of the mod...

Actually the mod simply masks liboemcrypto.so library, and L3 is just a consequence...

Apps can use liboemcrypto.so for decrypting both SD and HD streams, but the library is required for HD... Apps can fall back to other libraries where liboemcrypto.so doesn't exist but HD streaming will fail as will L1 security check...

It seems that affected apps are not allowing liboemcrypto.so use for ANY streaming and root detection (or possibly even detection that existing hardware for TEE decryption exists and should be used... Could be using model / other props with their own model whitelist too...) seems to be the likely reason to me... Ie. it's likely that these apps are simply restricting their use to SD decoding with older libraries (as liboemcrypto.so is primarily designed to decrypt HD content in secure TEE OS) rather than preventing apps from working on devices w/o hardware TEE...

Netflix does this too BTW, but relies wholly on Widevine certification since v5.0, making their approach much simpler...

Those helping here often have information you aren't aware of and are looking at issues from a different angle... Which is really why you ask here in the first place...

Helpers shouldn't have to explain every reason for requesting information when analysing an issue; It's very helpful when members simply provide details of setup initially and further details as requested...

Others are trying to think outside the box on your behalf... Let them!...

... I think you mean Play Integrity deviceIntegrity here(?)

It's dangerous to assume anything when diagnosing issues on other's devices... This is actually a case in point: You CAN pass PI deviceIntegrity w/o Displax mod (as I've stated before)... You may not have tried/achieved that, but many do...

All best on your quest... Hope something here was helpful... PW