Database Develop

[Q] Google wallet tap to pay not working

Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?

Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app

I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.

Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone

Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.

I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app

I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.

A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.

om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.

Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.

Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay

My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).

After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.

kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.

henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?

kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.

My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)

Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk

After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.

Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!

Smart Lock Trusted Places not working as intended

I've noticed something odd the last few days.
I tend to use Smart Lock to have my phone unlocked while I'm at home and that tend to work decently. Sometimes it doesn't unlock if the phone can't get a good enough locations but overall it's been doing it's job.
These last few days I've noticed something odd however.
The phone doesn't lock. At all. Wherever I am. Kind of annoying.
Sure, there are other ways to solve this, but still. It's a built in function and it'd be nice if it was working as intended.
Running stock 7.1.1, feb's OTA without root so I'm not quite sure what would be the culprit behind this. I'm running beta versions of Google Maps though so that could be it. Maybe something broke in the latest update.
Has anyone else noticed this behavior?

I've seen the same thing recently. My setup sounds similar - stock 7.1.1 from February, not rooted, locked bootloader. I have Smart Lock set to stay unlocked at home but locked everywhere else. I'm at work right now where it should be locked but it's opening on a swipe up without prompting for my pin.
I suspect that this has something to do with a new version of Google Play Services or something getting pushed in the background.
I rebooted my phone and the issue went away. Now prompted for my pin every time I swipe up on the lockscreen.

Yep -both my wife's Pixel and mine fail to use trusted places and devices correctly (we don't use the other smart locks). Started after the Play Services 10.2.98 update on the 10th Feb.
Both trusts seem to only check on phone start, e.g. if restarting at a trusted place the phone remains unlocked when you leave that location.
I've sent feedback and reported it to Pixel support who seemed completely uninterested.

Cheers guys. It's not just me then.

I have the same problem. Trusted places is not recognizing the location. I'm on stock 7 with October security patch. Trusted device though works, Bluetooth in my Jeep.
Sent from my Nexus 6 using XDA Free mobile app

I have an update.
Here is the short version. Trusted places is working again. On Friday I received my first OTA security update. I'm now on NBD92D. After installing the patch there was no change until Sunday when there was a pop up explaining how trusted places functions. Since then it's functioning correctly.
Sent from my Nexus 6 using XDA Free mobile app

I'm on N6F26U and I just noticed this today. It's supposed to stay unlocked at home and when connected to the BT transmitter in the vehicle, but it was unlocked at the DMV today. Definitely not trusted.

Same problem here... Smart unlock bluetooth will not list any devices, at all. Period. Can't peer, can't use. Latest version. Thanks Google!

EMUI 10 / Android 10, problem with Google Pay

Anyone else experienced problem with Google Pay after update?
It worked extremely well for me up until the update, then all of the sudden it doesn't work any more.
I checked the settings inside Google Pay, but all seems well. Card is registered and everything.
When holding my phone up to the terminal there is no reaction from the phone at all.
What can I do to fix this?

I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!

Gfhoihoi72 said:
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Click to expand...
Click to collapse
Thanks! Looking forward to your feedback if this works or not.

TordFuglstad said:
Thanks! Looking forward to your feedback if this works or not.
Click to expand...
Click to collapse
Nope... Unfortunately not. Maybe I'll just downgrade to Android 9 and wait until a new patch for Android 10 comes out where they fix this.

No problems here, working as before

EnormoDerClown said:
No problems here, working as before
Click to expand...
Click to collapse
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.

Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though

giosal said:
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
Click to expand...
Click to collapse
True, that changed the way apps can use your IMEI and this was the way most banking apps verified your phone. But my banking app should be compatible with Android 10 and it is working for some people but not for others.

Gfhoihoi72 said:
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Click to expand...
Click to collapse
10.0.0.168. "normal" update. Not a member of the beta or anything, just normal OTA. Working exactly as on Android 9. Also tested/used with different cards/institutes in google pay. Working like a charm

Same problem here, Google Pay worked perfectly in 9.1. Now, with 10.0.0.173 there's no response when near terminal. No error messages anywhere. NFC works fine, e.g. ReadID to read the NFC chip in my passport.

The same here, but I have a mate 20 pro. After the update to Android 10 I can no longer pay with Google pay.
From Germany

Updated yesterday and works fine for me in UK

So i better stop an update i am asked to update to 173 and stay on my 168 It is working for sure on 168 for me. Used it quite often

I solved the problem on my P30 Pro. I was using a "twin SIM" card from Ice (service provider). When I switched sim cards to my main SIM, Google pay works as before. The twin SIM worked fine with Android 9. I think the problem is that the twin SIM does not have the real phone number, but some long code that the phone system somehow recognizes, but causes issues in some scenarios e.g. iMessage on iPhone which cannot verify it. That's why I had the twin SIM in my P30 Pro.
EDIT: The iMessage problem is caused by the fact that only the main SIM receives "class 0" or flash SMSs, used for iMessage's verification.

I'm having the issue with my UK region VOG-L29 that's running .173. I rarely use Google pay, so I'm not sure if it was working before the upgrade. Google Pay works fine on my Fossil Wear OS watch that's tethered to the phone. NFC also seems to work fine when connecting my camera to the phone.

Have also the problem of nfc payments (with gpay and postfinance app) not working after updating to Android 10. Full reset didn't help currently on version 10.0. 0.173 and still not working.
Huawei support doesn't know anything about this and said I should wait for app updates and/or emui update.not very helpful...
Uninstalling gpay and deleting the cards linked to it and setup everything from scratch didn't help either. Nfc hardware seems to work as I can trigger my bt connection with my nfc enabled headset.
Hopefully Huawei sorts this out quickly as it is very annoying since I used nfc payment almost every day on emui 9.1

Any solution for this problem? I also used the ohone to pay and the point is that it is a big inconvenience that there is no solution

Waiting for Huawei to fix the damn bug in their next update (hopefully). Downgrading or resetting and so on is a pain when the affected phone is your daily driver.

Been using GPay already multiple times with 10.0.173.
No problems here in germany.
Regards

Same here!
Updated yesterday to EMUI 10 and realized today that I could'nt pay at the terminal. Bad situation without credit cards
Seems like NFC does not work at all. When I try to read my credit cards with NFC Tools, there is no reaction from phone as before.

gPay not workin

I've added PayPal and my Creditcard, both are not working but worked fine on my Pixel 2 XL.
It says: "phone moved too fast" but even if I lay it down on the terminal and not even touched it, the error appears.
Someone can relate? Any advice?

Nope, mine is super sensitive

I have a similar experience. Transferred my three cards from Pixel 4 XL and all of them refuse to authorise a payment on the Pixel 5, despite setting up with no issue. Three issuers (Amex/Nationwide/John Lewis Partnership) and I've tried at least 6 vendors. Just get the "That didn't work" message. Something odd is going on.

darkinformer said:
I have a similar experience. Transferred my three cards from Pixel 4 XL and all of them refuse to authorise a payment on the Pixel 5, despite setting up with no issue. Three issuers (Amex/Nationwide/John Lewis Partnership) and I've tried at least 6 vendors. Just get the "That didn't work" message. Something odd is going on.
Click to expand...
Click to collapse
Update: Have undertaken a full factory reset today and rebuilt the phone without copying across anything from my previous device via cable. Can confirm Google Pay is now functioning correctly.

mine is not working but I dont want to factory reset the device

Same - worked fine on my 2XL, none of my cards (from 2 different banks) working on the 5, just comes up with the "that didn't work - try another card" error, so obviously NFC is fine. Have removed the cards and re-added but no luck so far. Next up is to roll back on Play Services (currently on beta) and see if that works. Don't particularly fancy a reset!

I also had the descibed issues when trying to pay in a store today. Had to resort to my VISA card instead. Got a "transaction failed" error, and the terminal prompted me to insert the card instead. Funny.. hopefully this is just a software issue that can be fixed.
At first I thought it was caused by my root, but I do pass SafetyNet just fine (on basic attestation).

MattSkeet said:
mine is not working but I dont want to factory reset the device
Click to expand...
Click to collapse
Maxr1998 said:
I also had the descibed issues when trying to pay in a store today. Had to resort to my VISA card instead. Got a "transaction failed" error, and the terminal prompted me to insert the card instead. Funny.. hopefully this is just a software issue that can be fixed.
At first I thought it was caused by my root, but I do pass SafetyNet just fine (on basic attestation).
Click to expand...
Click to collapse
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!

Did you unsubscribed from beta or just installed?

alastor2004 said:
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!
Click to expand...
Click to collapse
Yeah, doing the clear cache and data is probably the first thing I'd try. That has fixed several issues for me over the years on several different apps.

Hi all, hi @alastor2004,
Would you mind to share which "stable" version of Google Pay Services you are on NOW after downgrade?
alastor2004 said:
Mine now seems to work after rolling back to the non-beta Google Play Services - I did this through the Play Store.
I wouldn't be too surprised if it might have just been clearing Play Services cache/data (which I assume also happened when I rolled back) so maybe try that first!
Click to expand...
Click to collapse
My setup of the device was from scratch so I don't think it's a matter of restauration of some backup but I was in the Play Services beta program. I opted out but didn't get any notification about application downgrading back to stable release. My current version of Play Services is v. 20.39.15 (150400-335085612).
Thanks.
L.

GP not working on the P5 is a known issue. Sometimes factory reset works and sometimes not. An update will be coming soon according to Google.

bobby janow said:
An update will be coming soon according to Google.
Click to expand...
Click to collapse
Do you have a source for this information?

ademmer said:
Do you have a source for this information?
Click to expand...
Click to collapse
Here's one: https://www.androidpolice.com/2020/...ecting-phones-from-google-oneplus-and-others/
And another: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/

bobby janow said:
Here's one: https://www.androidpolice.com/2020/...ecting-phones-from-google-oneplus-and-others/
And another: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/
Click to expand...
Click to collapse
Sure, but I didn't mean a source for the issue (which I am facing myself) but a source that Google is working on a near fix.

ademmer said:
Sure, but I didn't mean a source for the issue (which I am facing myself) but a source that Google is working on a near fix.
Click to expand...
Click to collapse
Bottom of the 9-5 link
Lots of stuff on Reddit too.

bobby janow said:
Bottom of the 9-5 link
Lots of stuff on Reddit too.
Click to expand...
Click to collapse
I do not quite get it. I asked for a proof that Google is already working on the issue. The 9-5 link you provided sais on bottom: "We have reached out to Google for a comment on the issues that some are facing, and will update should we receive an official response."
Means: No official response from Google yet and no confirmation that anyone is already working on a fix. Or am I mistaken?

ademmer said:
I do not quite get it. I asked for a proof that Google is already working on the issue. The 9-5 link you provided sais on bottom: "We have reached out to Google for a comment on the issues that some are facing, and will update should we receive an official response."
Means: No official response from Google yet and no confirmation that anyone is already working on a fix. Or am I mistaken?
Click to expand...
Click to collapse
I was just trying to help you get started. Figure it out yourself.

I had the issue but i removed my card and re-added. its been ok so far

bobby janow said:
I was just trying to help you get started. Figure it out yourself.
Click to expand...
Click to collapse
Wholly jabber Jaws Batman, The peep was only asking for the correct info.
Sent from my Pixel 3a XL using Tapatalk

Banking NCF stopped working with MIUI 12.0.3

I updated from 12.0.2 to 12.0.3 of MIUI recently and I now cannot pay by NFC with my banking app. My banking app doesn't use Google Pay and I don't have or want Google Pay so I can't try that.
I have checked that "Use HCE" wallet is set. Is there anythign I can do to get things working again?

Does no one have any suggestions on this at all?

@ludditefornow can you elaborate a bit what do you mean by "cannot pay by NFC" - what exactly happens when you place your phone near the terminal: is there any reaction (message) from the banking app or no reaction at all? Did you try to pay with the banking app open? Did you try disabling and re-enabling contactless payments in your banking app? In MIUI settings just below the option where you select "Use HCE" there's another option to select application for contactless payments - maybe the upgrade reset it to "Google Pay"?
I also have MIUI Global 12.0.3 (upgraded from 11.something) but didn't try paying by phone yet.

Thanks for the response. I have always paid with the banking app open. And have never had an issue.
Since 12.0.30 I have had two reactions from the 'pay wave' NFC payment terminals. Either they state that they can't read and throw up an error. or simply do nothing.
I have tried to disable and reenable contactless payments and no difference.
I have confirmed that Google Pay is not the default and that my banking app is. I have also confirmed that my banking app has NFC permissions.
I really have no idea. But I appreciate your reply.

For me (Global version) it's still working fine.

Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.

Robbo.5000 said:
Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.
Click to expand...
Click to collapse
Thanks,
three different NFC checking apps return positive to NFC and HCE. There is no Android Beam and as far as I recall there never has been.
Updates always OTA. And the current ROM is global as is my phone.
I've completely uninstalled the app and reinstalled it and then added the card again. I will check it today and see the result.
Thanks for the assistance all.

Yesterday I paid successfully with my phone (as I mentioned - MIUI Global 12.0.3 upgraded from 11.something).

Interesting outcome (for me anyway).
After removing the credit card from the app and then deleting the app, I then reinstalled the app and added the card. This led to the NFC HCE function again working.
Another symptom that appeared at the same time on the update was that I could turn on airplane mode at the icon on the pull down draw on the home screen. I couldn't turn off the airplane mode in the same way. To turn off airplane mode I needed to do so with the slider in settings.
After HCE function started working again, my airplane mode on / off functionality came back as well.
I am just writing this here in case someone at sometime gets something similar and may have another option to try to repair it.