Originally Posted by Didgeridoohan
Are you absolutely sure that the stock ROM doesn't have a fingerprint prop? What happens if you run:
getprop | grep fingerprint
As I've said before, as far as I know the cts profile only looks at ro.build.fingerprint. I did not think that basic integrity would be affected by prop values. What have you found by experimenting with the thumbprint? Do you mean that you only pass basic integrity if you alter the thumbprint props? What happens if you disable your module, do you fail both cts profile and basic integrity? So many questions, I know, but I'm a curious fella...
Also, like I said prevously, pretty much all of the "dangerous props" you're altering are already taken care of by MagiskHide. No need to do it again...
Lastly, if you're going to be providing the updated USNF module, could you at least alter it to not replace Magisk's Busybox? It's just a matter of removing the cp commands...
without the thumbprint, it fails both checks. with thumbprint it passes basicintegrity. i feel like there might still be ro.build.fingerprint but im really not excited about reflashing it to get one value.
as it stands now,
ro.build.fingerprint is resetting to the lineage one when i delete it.
ro.vendor.build.fingerprint and ro.buildimage.build.fingerprint are gone
ro.vendor.build.thumbprint and ro.buildimage.build.thumbprint are both the stock ones from my phone
passing basic but not cts, as expected for for lineage fingerprint.
tried deleting ro.build.fingerprint with ro.build.thumbprint and it readded fingerprint.
i tried setting ro.build.fingerprint to the stock thumbprint value and it gave the same results
i have no idea why i didnt get rid of all the duplicates while i was getting rid of everything else. next version i guess
planning to get rid of the usnf file all together soon as long as no one is saying my other one exploded their phone.