NFC not working properly - Xiaomi Poco X3 NFC Questions & Answers

I cant get NFC to work properly. My phone is able to read cards and tags in NFC mode but it doesnt emit anything. E.g. google pay is not working.
I have ArrowOS 11 with latest MIUI firmware.
I tried with my wifes NFC phone and my Poco can register signal from her phone but not the other way around.
Im thinking firmware issues or something with ArrowOS?
Any ideas?

I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.

I was able to get mine to work yesterday using an apple 12 as reciever.
The signal is insanely weak, i literally had to use a precise angle at a certain spot on the iphone to get a registration.
There is no way to get a card terminal to register anything this NFC emits. Seems it has to be closer than a few millimeters apart to get any registration.
Which is strange because i can scan tags/cards that are a few cm away without issue..
Im thinking this is a hardware issue

ndb055 said:
I've got a similar issue, I can't get NFC payments to work. Also using Arrow OS 11 (latest release) with the newest miui firmware. Tried to root my phone with Magisk 24 to see if this works but until now without any success. Any help would be great.
Click to expand...
Click to collapse
Install Magisk 23, hide the Magisk app (it will get a different icon and a different package name), hide Magisk from Google Play, Google Pay and your banking apps, install GPay SQLite Fix v2.6 from here:
Releases · stylemessiah/GPay-SQLite-Fix
A magisk module that ONCE allowed Google Pay to work on rooted phones - stylemessiah/GPay-SQLite-Fix
github.com

Related

Magisk Rooted + Barclays App, can't use fingerprint authentication

OnePlus 7 , OOS 10.0.7 GM57BA
- rooted with Magisk
- busybox installed
- NO Xposed!!
- magisk package name changed
- magisk Hide enabled in settings
- safetyNet passed
- packages hidden: Barclays and com.anfroid.phone
Issue: cannot set up fingerprint authentication in Barclays app. It works well in any other apps. When following the procedure, the app throws an error T0009 and the message "Error during fingerprint authentication/registration"
I contacted the Barclays team, they don't seem to have the error in their errors list. Possibly to be forwarded from the system?
I also tried to hidein magisk the fingerprint authentication services com.qualcomm.qti.biometrics.fingerprint.service
Maybe I didn't hide all services involved in fingerprint authentication? What else should I try to hide from root?
I'm looking for suggestions.
Hi,
i've got the same issue for ages (with my previous OP6 too) and it's the same with the BA Amex app.
I think it's just an issue of these apps with our OP7 phone?
Have you ever been able to make it work with the phone un-rooted?
bay12 said:
Hi,
i've got the same issue for ages (with my previous OP6 too) and it's the same with the BA Amex app.
I think it's just an issue of these apps with our OP7 phone?
Have you ever been able to make it work with the phone un-rooted?
Click to expand...
Click to collapse
Yes, my wife's phone (also OP) was never rooted and it worked just fine. OP5T, then OP7 and now OP8. And yes, the OP7 Which is mine now,was hers before.
On the default phone configuration it seems to be working just fine.
derei said:
Yes, my wife's phone (also OP) was never rooted and it worked just fine. OP5T, then OP7 and now OP8. And yes, the OP7 Which is mine now,was hers before.
On the default phone configuration it seems to be working just fine.
Click to expand...
Click to collapse
oh interesting! i don't think i've ever tried to used these apps with an unrooted phone.
Please let me know if you manage to solve this issue
Same problem forever with Barclays and OP6
I have the same issue with my OP8T, rooted with patched Magisk image, MagiskHide, but otherwise stock OS. I'm also unable to get any useful information out of Barclays.
This worked fine on my OP3T so it seems to be something with the newer phones.
Hello guys,
I have the same issue with my OP8P, magisk hide,safety net passed. I have another banking app which is working perfect but this for some reason it is not working
I've just had my S9+ replaced on insurance. However I've had to have the phone replaced again as the first replacement they sent had an issue with the touchscreen.
My original phone worked fine with fingerprint authentication in banking apps.
The first replacement I rooted with Magisk and both my banking apps worked OK, but the newest replacement doesn't work with either banking app and just errors when trying to enable fingerprint authentication.
All phones were running the same Alexis ROM, same configuration with Magisk and same kernel.
Really weird.

Worth to install LineageOS 16.0 on T5 ?

Hi,
Those who installed LineageOS on T5, could you please share your experience ?
I noted from few comments on this forum:
5GHz Wifi is not working but 2.4 GHz is working fine
disable HW overlays in the dev options to remove blur
disable AudioFX to correct sound
Is there any other prooblem ? What about bluetooth, camera, GPS, gapps ?
Any feedback will be appreciated
I'm the one who said it didn't work on 5GHz wifi, it is working.
I had to wait several minutes until my AP appeared, once I connected for the first time it did not give me any problem.
Also something like this happened when starting LineageOS for the first time, it did not connect neither in 2.4 nor in 5 but waiting it worked.
After disabling AudioFX I installed Eqfy Equalizer which works fine.
The camera app is not working, a white line appears in the middle of the screen and there are no photo options or anything.
Since I don't use it to take photos, I have not tried more but I suppose that with some other camera app it should work.
Not tested bluetooth or GPS for now.
On the other hand, the tablet works more fluidly and you have more free space.
In the absence of trying more things, for now I'm sticking with LineageOS.
Thanks for your feedback.
I have flashed LienageOS 16, and have patched RAMDISK.IMG to install Magisk.
It looks OK, I like it so far. There are only two issues:
* Camera is not working
* I have only 2,4Ghz WiFi (which btw is working fine), but I do not see 5,0 GHz network in my list
GPS, bluetooth, sound, image,...everything seems working OK, but I didn't check in details.
Despite those two issues I will stay with LineageOS. I prefer it one hundred times over EMUI. And for camera, which btw is not very important to me neither, I will probably find a fix one day.
From time to time your 5GHz AP may appear, you can connect but then it disappears again.
Yesterday I checked, I thought it was connected in 5GHz but no, the connection was in 2.4
I confirm that the Wifi in 5GHz does not work.
borja113 said:
Thanks for your feedback.
I have flashed LienageOS 16, and have patched RAMDISK.IMG to install Magisk.
It looks OK, I like it so far. There are only two issues:
* Camera is not working
* I have only 2,4Ghz WiFi (which btw is working fine), but I do not see 5,0 GHz network in my list
GPS, bluetooth, sound, image,...everything seems working OK, but I didn't check in details.
Despite those two issues I will stay with LineageOS. I prefer it one hundred times over EMUI. And for camera, which btw is not very important to me neither, I will probably find a fix one day.
Click to expand...
Click to collapse
I have sorted it out.
For WiFi, I changed the channel on my router, put it at 44, and now the 5,0 Ghz Wifi is visible and I can connect.
For camera, I have found a Gcam which works OK, it is "GC_4.1.006.126161292-41003513.apk", easy to find on XDA.
So now I have LineageOS fully working. For the time being everything is fast and stable.
Kgonla said:
From time to time your 5GHz AP may appear, you can connect but then it disappears again.
Yesterday I checked, I thought it was connected in 5GHz but no, the connection was in 2.4
I confirm that the Wifi in 5GHz does not work.
Click to expand...
Click to collapse
I thik it is related to router. On my router, in settings, the choice of channel was set to automatic, I put it to 44 and it is visible, and the connection is fast and stable. For some reason the tablet doesn't see higher frequencies.
borja113 said:
I thik it is related to router. On my router, in settings, the choice of channel was set to automatic, I put it to 44 and it is visible, and the connection is fast and stable. For some reason the tablet doesn't see higher frequencies.
Click to expand...
Click to collapse
I'm going to take a look to Gcam, I've tested a couple of cam apps but not working.
Now I'm using channel 56 but previously I tested other channels, maybe the day it worked I was using a lower one, will test too.
Thanks a lot.
borja113 said:
I have sorted it out.
For WiFi, I changed the channel on my router, put it at 44, and now the 5,0 Ghz Wifi is visible and I can connect.
For camera, I have found a Gcam which works OK, it is "GC_4.1.006.126161292-41003513.apk", easy to find on XDA.
So now I have LineageOS fully working. For the time being everything is fast and stable.
Click to expand...
Click to collapse
Hello again, I have changed the channel to 44 and for now it works fine.
The Gcam is not working for me, It tells me that it cannot find the camera and closes.
Kgonla said:
Hello again, I have changed the channel to 44 and for now it works fine.
The Gcam is not working for me, It tells me that it cannot find the camera and closes.
Click to expand...
Click to collapse
Hello. If this can be of any help: the Gcam which I installed, I found it on this thread:
https://forum.xda-developers.com/huawei-p20/themes/google-camera-huawei-p20-kirin-devices-t3882198
It is : Google Camera v4.1.006.126161292, in the first post, section OTHER AVAILABLE APKs.
Maybe we’re not using the same version.
After flashing LineageOS, I found that I had two cameras : HwCamera2.apk 8.0.0.200 which I think is Huawei camera, and Camera2.apk 2.0.002. First one was crashing immediately, the second one didn’t work with a white line in the middle. Now I have first one disabled, second one is still there but useless. And third one is the one above which is OK.
Has anyone had any luck with Netflix?
I tried LineageOS yesterday and was unable to install Netflix from the play store, likely because it said I was uncertified. I was however able to download and side load Netflix, which initially appeared to resolve the issue, however any attempt to play content resulted in a 5.10 error. From what I can tell, this appears to be something to do with DRM, however the few potential solutions I've found using Magisk didn't help resolve the situation, and I've ended up reverting to Emui
Aside from Netflix, I didn't come across any other issues while testing. Unfortunately for me, Netflix was the main reason for getting this tablet in the first place, my old 3rd Gen iPad would have been more than adequate for my needs other wise
In order to get Netflix work, I installed one older versions found on apkmirror. I picked up randomly 6.21.0. I installed also liboemcrypto_disabler (even though I do not know if it was necessary), and in addition of that it is hidden in Magisk. It is working, I do not know how to check the quality, but I guess it is 720p.
Why TWRP needed why not to flash directly from stock recovery...
If you want to install LineageOS, the TWRP is not needed. You flash LineageOS via fastbot. In fact, it is better not to mess with TWRP, officially it is not supported by OpenKirin ROM's.
I also thought so but it's ok I have LineageOS installed with OpenCamera everythink seems to be working fine even LTE is there 16.1 version available ?
and also where can I get stock recovery if I need it, is it available for download anywhere ? or after LineageOS instalation it also installs stock recovery ?
If you want go to stock recovery again, On OpenKirin site there are comprehensive guides, under section Support, about where to find stock EMUI firmware, and how to extract and flash stock recovery image.
I do not think that LineageOS will install stock recovery, if you had TWRP before LineageOS installation, most likely it is still there. You may check it yourself : Vol Down + Power on boot.
I've just tried LineageOS build 6 on my AGS2-W09 and the camera seems to work ok now.
Had to install OpenCamera and set the all permissions, clear storage for this app and on the next run it can finally save the aquired photo.
The 5Ghz WiFi works with no problems (my router selected channel n.60)
As for audio: there is a glitch when device is booting, might want to not wear headphones during a reboot ☺
Haven't tried disabling AudioFX or installing Viper4Android as I am rolling back to stock firmware.
Netflix:
I think I konw why Netflix is not working: I have no IMEI with this OS.
UPDATE: IMEI should not matter on this device as it has no network.
I had tried the Netflix 6.21.0 version mentioned here and it gives me the same "Device failure occurred 501.-1006" error.
Then I've installed Kodi with a Netflix addon and it gives me: "It was not possible to get data from Widevine CryptoSession. Your system is not Widevine certified".
It is pretty clear that the LineageOS 16 build 6 (lineage-16.0-20201019-emui8-gapps.img) has no Widewine libraries installed.
Other than this the OS is very responsive, unfortunately I have to rollback because of this.
I am using this tablet for Netflix and prime on stock emui.
I really want to upgrade to custom ROM but no polished ROM anywhere!
guys how you have managed to pull boot.img from the device?
can anyone guide me through?
I have successfully managed to flash LineageOS latest build on MediaPad T5
kamilmirza said:
guys how you have managed to pull boot.img from the device?
can anyone guide me through?
I have successfully managed to flash LineageOS latest build on MediaPad T5
Click to expand...
Click to collapse
Can you share the entire installation process.
Thanks
bluestar778 said:
Can you share the entire installation process.
Thanks
Click to expand...
Click to collapse
For LineageOS 16 --> https://forum.xda-developers.com/t/twrp-lineageos-16-installed-in-t5.4161857/
For Latest build (LOS18.1) --> https://forum.xda-developers.com/t/...ation-guide-for-mediapad-t5-ags2-xxx.4291431/

LineageOS questions

Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.
Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.

Question [SOLVED] Gpay NFC not working on AOSP custom ROMs

On my Poco X3 pro global, Gpay doesn't work with NFC payments when using AOSP custom ROMs A12.1, instead it works flawlessly in the same conditions with any fastboot or recovery MIUI roms.
I tried with or without magisk (obviously with safety net always passing and certified device on play store and google pay app, hiding play store, play services and google pay with zygisk), I tried deleting all data in play store, play services and gpay and trying again.
I tried with different custom aosp roms and gapps packages but nothing changed, when i try to pay the POS retrives an error and the transaction fails (nothing pops up on the phone).
The NFC chip works perfectly so it's not a hardware problem (I also said it works perfectly on MIUI).
I've got 13.0.4 firmware on.
Any ideas? Thanks to everyone who will answer
Gpay NFC payments worked for me on every ROM i tried, but i never rooted or modified them in any way (no mods, custom kernel etc) so that might be an answer.
The solution to this problem can be found to this link! Just swap your SIMs (or remove one and swap the other one), reboot your phone and you're good to go!
NFC doesn't working (unique mysterious problem)
Good day! Poco X3 Pro 8/256 does not want to pay for NFC in any way. What is the problem? When paying, any terminal beeps 2 times and issues an "equipment error". I studied a lot of information on XDA/4PDA, I didn't find anything similar to my...
forum.xda-developers.com

Question Google Wallet on MIUI 14?

Anyone got Google Wallet with NFC working on MIUI 14? I previously had it working on MIUI 13 but not since I upgraded.
Ok solved my own problem. In case anyone might be interested, my problem was that one of the Magisk modules (i.e. AndroPlus's Google Assistant module) was "disabling" my NFC. Once I turned off that module, it all worked again.
Hello i can't paying with m'y phone because my phone IS rooted
issa033 said:
Hello i can't paying with m'y phone because my phone IS rooted
Click to expand...
Click to collapse
Since your phone is rooted it should be no problems. Make sure you have the magisk module "universal safety net fix" and don't use AndroPlus's Google Assistant magisk module. It should work, if not then disable all other modules and see if it works. If it does, then its one of the modules causing the problem. That was the issue with mine.
FYI in case anyone is interested, I have a Mix fold 2, MIUI 14, unrooted, and I finally worked out how to get Google Pay/wallet working on it without rooting.
Instead of adding the card from the Google Pay app which would give me an error every single time, I went into my internet banking app on the fold 2 and started digging through my banking app settings. In those settings, I found a "cards" section, and, 'lo and behold, there beside my regular card was a little G pay icon. After clicking the icon, my banking app downloaded google pay onto the fold for me, sent me confirmation code by text and this time, NO ERRORS! It all went smoothly. I have used my phone to pay 4 times today and it's working like a charm.
I'm in Australia, using National Australia Bank.
I'm so thrilled, as it's been a couple of years since I rooted anything, and I didn't want to do it on something as nice or expensive as the fold (not for some time yet anyway).
bunnigrrl said:
FYI in case anyone is interested, I have a Mix fold 2, MIUI 14, unrooted, and I finally worked out how to get Google Pay/wallet working on it without rooting.
Instead of adding the card from the Google Pay app which would give me an error every single time, I went into my internet banking app on the fold 2 and started digging through my banking app settings. In those settings, I found a "cards" section, and, 'lo and behold, there beside my regular card was a little G pay icon. After clicking the icon, my banking app downloaded google pay onto the fold for me, sent me confirmation code by text and this time, NO ERRORS! It all went smoothly. I have used my phone to pay 4 times today and it's working like a charm.
I'm in Australia, using National Australia Bank.
I'm so thrilled, as it's been a couple of years since I rooted anything, and I didn't want to do it on something as nice or expensive as the fold (not for some time yet anyway).
Click to expand...
Click to collapse
Wohooo!!! Just discovered another Aussie Mix Fold 2 user!!! Yeah! Our numbers are growing ;-P
Anyone have wallet working it complains about root even though I have magisk hide + safety net fix. miui 13

Categories

Resources