At least you have to wipe data (no need to format) after flashing if your recovery supports decryption. Tested with crDroid 8.7 & 8.8 and ofox R11.1_1_3_A12 recovery
I didn't install magisk either. Safetynet also pass too.
I had this too, do you have face unlock enabled? Turning off face unlock stopped it for me, though I haven't actually paid for anything with it yet.
For those having issues on gpay or other wallets, just try clear cache from play and playservices. Should fix the problem.Dirty flash 20220816 over last update and can't get some payment app to work too. Me faceing issue with TrueMoney Wallet app.
And this is trouble me for a long time on this rom. When i'm double tap power to open camera. if i hold the phone that my hand cover proximity sensor (that happen often cause I have to held it horizontal for taking a picture), the pocket mode will kick in and auto lock my screen.
But anything than problem. This is fantastic update. It's make gcam double tap to open camera feel smoother. Not buggy when try to open picture on camera in lockscreen.
Appreciate the dev.
In my case dirty flash 3.6.2_12-RedmiK40-RedmiPOCOF3_v3.8.3_A12-alioth-skkk_4f7299ea + firmware 220.127.116.11 ( Global phone bought on banggood and used in europe ) + nikgapps 16082022 + magisk 25.2. Stuck on System boot logo ( Eye of Oziris ) and nothing happed in 20 minutes .... Can someone help ?
Don't know if the above is of any use @raystef66 ? Just something that I noticed on another thread.
So everyone has this issue using @Displax USNF-mod module on Poco f3 w/ Crdroid 8.9?... Interesting...
Did issue occur with an update, or just started occuring?
If no update its likely Google has strengthened prerequisites for deviceIntegrity on server end... Could be something peculiar to Crdriod Rom too... Eg. is selinux enforcing?... Some strange prop settings/manipulations?...
Could ask Poco f3 Crdroid maintainer about possible incompatibility... An integrated mod may be causing issues when running Magisk USNF mod, eg:
Perhaps it should look like this one(?):
or others linked from the issue below...
Could post info. here for @Displax / @kdrag0n:
*** Disclaimer I am not responsible for any damage you made to your device You have been warned