-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFC not working on Xiaomi 12 Pro MIUI 14 #242
Comments
Hmm, I have no idea what might be causing this. BCR's Magisk module doesn't do anything more than installing it as a system app (it doesn't modify other apps or components). BCR doesn't even run in the background until a phone call begins. |
I guess there my be some conflict in my Magisk. |
To fully remove everything, all you have to do is clear BCR's data in Android's Settings before removing the module. BCR doesn't put files anywhere else (besides your recordings directory). |
No luck :( Don't know why NFC still not working when BCR is enabled in Magisk. |
Does it only happen if BCR is enabled in Magisk or does NFC break whenever any module is enabled? |
Thanks for your help. My other modules are Shamiko and Universal SafetyNet Fix. NFC works regardless of whether they are enabled or disabled. |
If you're able to grab the full logcat immediately after a reboot (once with BCR and once without), I can try to take a look, but I don't really have any more ideas. |
Magisk currently has a known issue where its mirror mount points do not work correctly with overlayfs. Files from the overlayfs lowerdirs may no longer be accessible. On MIUI, this is a problem because /system/etc/permissions is an overlayfs mount and one of the lowerdirs is /product/pango/system/etc/permissions. One file underneath that path is com.nxp.nfc.nq.xml, which if missing, breaks NFC. Fixes: #242 Fixes: #246 Signed-off-by: Andrew Gunnerson <[email protected]>
After upgrading to MIUI 14, the NFC crash on boot and NFC is not working. I can only use NFC after disabling BCR in Magisk followed by a reboot.
here is the error trace:
Appreciate if anyone can help with this. Thanks
The text was updated successfully, but these errors were encountered: