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!
Related
Ok guys, as i'm browsing, I keep seeing the same questions over and over gain in different threads talking about Google Wallet. I want to put everything out here in one thread. Keep in mind i'm in the US, I know our foreign friends will be different as Google is still working on getting it working outside the US. So this guide is for you US peeps.
1.) Yes, GW works fine on rooted devices. A banner will show that your device is unsupported, and a warning may appear during checkout...ignore this. The app still works just fine. The reason it says "Unsupported Device" is because when you are rooted, there is a security risk for GW (just like there's one for you device as a whole).
2.) GW will not appear on the Play Store from your device. However, if you go to the Play Store on your computer, it will be there.
3.) You have heard there was an update that allowed you add all major credit cards, but you can't see how to update it. You have two options:
~a.) My most recommended option. Go to the Play website using your computer. Click on 'My Android Apps'. Choose the Asus Nexus 7. Scroll through the installed apps until you find "Wallet." Click it. Click on 'INSTALLED' and it will offer to send the update to you. Send it to your N7, you may need to be on wi-fi, I'm not sure about that. Now you'll have the other options for credit cards.
~b.) IF IF IF IF IF and ONLY IF the first option does not work, you can use the hacked apk found here. Just follow the instructions. Now if you are outside of the US, there are instructions in that thread for getting GW to work outside of the US. If you have issues, post them there so the developer can work on it. It is his apk, so he needs to know of issues, not me.
4.) You have added your credit/debit card. When you use GW, it will actually use your virtual master card that goes through Google, which will then debit from your actual card. What does this mean? It means that if you get any kind of rewards for using your card at certain places, you may not get those rewards or only part of them, as your billing statement will show that it was a Google purchase.
5.) No. You do NOT have to have a data or internet connection to use GW.
So there you have it. And just point out the most frequently asked questions: no data/internet required, works on rooted devices regardless of the warnings you see, only shows up in the Play Store on your computer browser. There, those have been repeated twice, so you should not be asking anymore
That's awesome. I'd added a card online, deleted an old one, but the damned app on my N7 just showed a Citi card, and no option to update. I felt retarded... I'm glad this is finally set up. Thanks.
My N7 is rooted. I've installed the latest wallet and I've entered one of my credit cards. When I did that I got an email from google stating that my wallet was set up and ready to go. To test it I should open wallet and tap my card to authorize its use. It doesn't matter how much I tap, touch, or rub the card on the N7 it doesn't appear that it is reading my card.
Is it working properly? I'd kinda like to test it out before I actually take it in someplace and try to use it.
ba_hamilton said:
My N7 is rooted. I've installed the latest wallet and I've entered one of my credit cards. When I did that I got an email from google stating that my wallet was set up and ready to go. To test it I should open wallet and tap my card to authorize its use. It doesn't matter how much I tap, touch, or rub the card on the N7 it doesn't appear that it is reading my card.
Is it working properly? I'd kinda like to test it out before I actually take it in someplace and try to use it.
Click to expand...
Click to collapse
Is your card a paypass card? Never seen it ask to tap the card to the phone. Not sure why it would, frankly.
I was about to say the same thing. You can't tap just any ole card. Doesn't work that way. The card needs to have an RFID chip in it, or some sort of NFC chip. Someone correct me if i'm wrong.
Installed yesterday from the link that was posted and this is what I get.
Thoughts?
Sent from my Nexus 7 using Tapatalk 2
I am not rooted and I tried it at a Walgreens, but it didn't do anything. Can someone explain in elementary steps how it actually works when using it at a store? I just figured I had to have a data connection and that is why it didn't work, but this guide says otherwise.
Thanks for your help!
First, download the PayPass locator to find which stores near you actually have a console that is compatible with the device. Some Walgreens DO NOT have the mastercard paypass system. They have some other kind of technology. I tried at a walgreens by my place and felt foolish when the girl just looked at me weird.
You can use this at ALL McDonald's. Go there and order something. Turn your device on. Make sure NFC is enabled in the settings. You don't need to have wallet open already, but it would speed up the process. If you don't have it open, but with the phone screen turned on, rest the back of the device to the paypass surface. They need to be physically touching. You may need to move the device around just a bit. You will hear a ringing noise, and then google wallet will be active. It will ask you to type in your PIN and the press the device to the surface to complete the transaction. Sometimes you have to tell the person at the cash register that you are paying with credit. Once you tap it a second time to the surface of the paypass thing, it will say transaction complete.
NOW, sometimes it doesn't work 100% flawlessly. SOMETIMES you have to tap the device to the pad over and over again. Or move it around on top of the pad until it goes through. And sometimes, even tho it goes through on the end of the cash register, the device still tells you that the transaction may not have gone through. If the person smiles at you and gives you your receipt, it went through just fine. But the device will ask you to tap the paypass pad again. Just take the receipt and wink at the person if they are cute because they have never seen it before and they are probably blown away by it.
Oh, and even though people say that you don't need a data connection to use it, I have always been connected via wifi to my phone or the wifi at the restaurant when I use it.
One more question, I am getting annoyed by the "you need flash blah blah blah", so I am going to root.
In the past I thought I saw articles saying something about resetting google wallet before you root or it messes it up, but when I go into Wallet to reset it - I don't see that option.
Is this something that is still required? If so, what are the steps?
I was under the impression that you don't need a wi-fi connection to complete a transaction at a PayPass terminal. Has anyone used it successfully knowing there was no wi-fi connection?
Heaterz16 said:
One more question, I am getting annoyed by the "you need flash blah blah blah", so I am going to root.
In the past I thought I saw articles saying something about resetting google wallet before you root or it messes it up, but when I go into Wallet to reset it - I don't see that option.
Is this something that is still required? If so, what are the steps?
Click to expand...
Click to collapse
From Google wallet, go into the menu from the google wallet home screen. The three dots up in the right hand corner. Then settings. Then reset google wallet.
You do not need a wifi / data connection ! How many times does this need to be stated?!
Groid said:
I was under the impression that you don't need a wi-fi connection to complete a transaction at a PayPass terminal. Has anyone used it successfully knowing there was no wi-fi connection?
Click to expand...
Click to collapse
.....................really dude? Did you read the whole thing? I even said it twice. Let me quote myself:
5.) No. You do NOT have to have a data or internet connection to use GW.
So there you have it. And just to point out the most frequently asked questions: no data/internet required, works on rooted devices regardless of the warnings you see, only shows up in the Play Store on your computer browser. There, those have been repeated twice, so you should not be asking anymore
Click to expand...
Click to collapse
See? I put it in there twice. I'm not trying to be a jerk, I just have little patience for people who don't read and ask questions that were already answered. Hope the bluntness gets the point across so this doesn't happen in the future, that's all.
adamhlj said:
From Google wallet, go into the menu from the google wallet home screen. The three dots up in the right hand corner. Then settings. Then reset google wallet.
Click to expand...
Click to collapse
I can't believe I didn't see that until now, I tried that about 4 times using the menu button but it never had the settings option....before I realized I was within a card which didn't have that option. I had to hit the back button twice to get to the "homepage" of the app, then I saw the settings, reset option...
Thanks!
Thanks OP. Your method of updating the app worked flawlessly for me. Now I added another card. Can't wait to try this out.
Quick question: lets say I get a galaxy S3, it has Google wallet on it or I install it(I believe that device has nfc also, all I would have to do is sign in and data transfer KR copies to new device? Or will I have to set THST device up all over again ?
Here's an odd question:
Let's say you're at the end of your funds on your debit card, and you don't want to charge the whole amount on your (different)credit card. Is there a way to use Google Wallet to pay out the last of the debit card's funds, THEN cover the balance of the purchase with the credit card?
matrix0886 said:
~b.) IF IF IF IF IF and ONLY IF the first option does not work, you can use the hacked apk found here. Just follow the instructions. Now if you are outside of the US, there are instructions in that thread for getting GW to work outside of the US. If you have issues, post them there so the developer can work on it. It is his apk, so he needs to know of issues, not me.
Click to expand...
Click to collapse
I'm running Team EOS Rom build 19.
Nothing else would work for me, so I did this method.
I have tried installing it by just tapping the apk and I have also put the apk in /system/apps and set permissions. No matter how I do it, I always get this.
Any thoughts?
I can verify that this works when rooted on the stock ROM AND WITHOUT INTERNET CONNECTION. When I have used it on my Nexus 7, I have had the app open as it will ask you to put in your PIN number on the device.
Few things to make sure you have done before scanning. Make sure you have a card selected before hand WHICH DOES REQUIRE INTERNET CONNECTION. I have tried to scan my Nexus 7 and Galaxy S III without a card selected (although I'm not sure why the card was deselected) and neither would work.
When you scan the device at the NFC point of sale, make sure you center the "U" in "Nexus" on the back of your device over the scanning area (this is according to the instruction manual on the device). You can test this for yourself if you have another NFC capable device, using Android Beam. You will find that the scanning range of the NFC is very specific on both devices.
Sometimes, it will take a little bit of time for the device to be scanned and for the transaction to be completed. You will hear a sound from your device indicating that the NFC has been scanned, after which the Google Wallet app will pop up prompting you to put in your PIN or that the transaction has been completed, showing you a receipt.
matrix0886 said:
.....................really dude? Did you read the whole thing? I even said it twice. Let me quote myself:
See? I put it in there twice. I'm not trying to be a jerk, I just have little patience for people who don't read and ask questions that were already answered. Hope the bluntness gets the point across so this doesn't happen in the future, that's all.
Click to expand...
Click to collapse
I read the OP entirely and thought, hooray! In post 7 someone said his didn't work and questioned the data connection. Post 8 said he was successful and stated he had a wi-fi connection with his phone at the time. No one before my post had verified wi-fi or data was not needed except the OP. Trust, but verify. I just wanted one other person to say it worked.
Just curious if there was a way to reload the virtual card without having another credit/debit card added as an available card in GW? Is there a phone number or website where we could add funds, so the virtual card is the only card listed in GW?
Sent from my Nexus 7 using Tapatalk 2
Just like the title says anyone get it to work in running Clean ROM I get through the whole "add a card" process and then get the not compatible message
mines work. just updated about 2hrs ago. im just waiting to verify my cards
Where'd you get that from? The only option I see is to download the new "Google Wallet" alongside the current pre-installed one.
well yesterday it asked me to update so i updated and then when i launched google wallet it also asked me if i wanted to use google wallet or use the new android pay. i clicked android pay it downloaded it for me and launched at well and its working fine.
Well hell mined keeps telling me the same thing and I just updated right now too...
Well I stand corrected, checked yesterday was nothing even late night...this morning it updated. No errors, runs perfect but yet to try it to actually pay.
*Edit: Used it at Walgreens this morning. Had to hold it to the unit, scan my fingerprint, then remove and hold again. Worked.
Works for me. It imported my credit and loyalty cards from Wallet. I used it this morning and the only thing is it didn't automatically use my Panera loyalty card. But I'm not sure if that functionality is up and running yet.
Sent from my SM-G928V using Tapatalk
I'm having the same issue as you are and I'm rooted - not Rom'd. Did you find a solution?
Not sure if it's the same for rooted s6's as it was for rooted M8's, but if you disable SuperSU temporarily (SuperSU>Settings>Uncheck enable Superuser), then go in to android pay, it should activate. After that, just go back to SuperSU and recheck the enable superuser box.
wolfgrrl said:
I'm having the same issue as you are and I'm rooted - not Rom'd. Did you find a solution?
Click to expand...
Click to collapse
What he said ^ haha but i noticed that if i enable SU again the service won't work when i try to pay
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!
Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards
net4u said:
Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards
Click to expand...
Click to collapse
I also have the april security patch, but i could still do a payment yesterday with the NFC of the phone.
So no problem for me.
Yes, Google Pay stopped working for me in mid-April, *but* before I installed the April security patch so that wasn't the cause for me. I was hoping the April patch might fix it but no joy. I've been checking here to see if anyone else had the same problem but this is the first report I've seen.
It's very annoying as I'd got very used to using it... as you say other NFC things are fine.
I've done all the usual tricks of uninstalling, wiping caches, trying an earlier version (it seemed to stop working after the Google Pay update was installed that was released on the 15th, so I thought that might help), etc. etc. but no joy at all. It just doesn't trigger.
Same problem, suddenly NFC doesn't work anymore. Weird thing I discovered is that it might work at that moment when I press the power button to switch display off. ... Strange
Using Magisk with it? Rooted device?
Ah, ok, maybe i wasn't clear enough.
For me it still works, but i do NOT use Google Pay, i use the app from our bank for NFC payments.
I think that i have read some time ago about problems with Google Pay, so maybe that is the case.
I also found out some time ago, that i have to have the lockscreen on-screen, otherwise i cannot do a payment.
So unlocking the phone makes payments impossible and screen-off is also a no-go.
But i suppose you guys already knew that.
xsycox said:
Using Magisk with it? Rooted device?
Click to expand...
Click to collapse
Nope, pure stock (apart from most evenwell apps disabled for this user).
EDIT: Two threads about it now on the Nokia forum at https://community.phones.nokia.com/categories/nokia-7-plus
Fixed by uninstalling Google Pay
Just an FYI, I had my NFC issue resolved by uninstalling Google Pay. May help someone else.
I did not use Google Pay (since is not available in my country), but two tap and pay apps from two banks where I have accounts. Both have updates in april, and one of them tryied to became forced my default one without asking explicitly. But as I say: other NFC functions works: I can beam, I can read tags or cards.
I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.
Nexustb said:
I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.
Click to expand...
Click to collapse
No, I mean since is not available in my country yet, I haven't it on my phone.
....and fixed in the latest version of Google Pay, released last week
It may be related to this: https://nvd.nist.gov/vuln/detail/CVE-2019-2041 ?
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.