I don't even know if it's an issue: when i try to use Google Pay in store (NFC) it returns with an error asking for my finger print(phone already unlocked), resulting in an error as well on the vendor side(machine). I have to put the finger print and google pay app asks to get closer again and after all of this, it works. I know that google pay is supposed to work without asking for finger print, just using the phone unlocked witch i did.
Do u people have to do that or it just works (without the extra authorization)?
PS: I did a deblot, but I already reinstalled all the Samsung pay and pass stuff even guessing that it didn't cause the issue.
Thanks in advance.
did you set it as default? i have a pass which i need to set google pay as default. otherwise i would only use samsung pay.
Sent from my SM-G975F using Tapatalk
jemfalor said:
did you set it as default? i have a pass which i need to set google pay as default. otherwise i would only use samsung pay.
Sent from my SM-G975F using Tapatalk
Click to expand...
Click to collapse
Yeah, its set as default. When you use google pay, even the phone already unlocked, it asks you to put the fingerprint?
uvitor said:
Yeah, its set as default. When you use google pay, even the phone already unlocked, it asks you to put the fingerprint?
Click to expand...
Click to collapse
never really use google pay for payment before, only passes. for passes, never request for fingerprint or anything.
i once installed an app somewhere in the internet and many times, it would ask for fingerprint. uninstalled it btw.
Sent from my SM-G975F using Tapatalk
Hi all!
I'm writing here to see if someone has any idea, it seems I'm not able to understand the reason.
I setup Google Pay on my OnePlus 5 and it was working perfectly, up until some days ago. Now when I put the phone close to the POS, nothing happens, even if I open the Google Pay app before placing the phone near the terminal.
I performed a factory reset of the phone, after that, Google Pay started working again, but then, after a few hours, it just stopped with the same exact behavior, meanwhile I had restored the backup of most of my apps.
I again performed a factory reset, Google Pay started working properly, then slowly started re-installing and re-configuring my apps, constantly testing if Google Pay was working (luckily I found out how to "test" if Google Pay is working without having to buy something*), everything was working properly, but then, apparently without reason, Google Pay stopped working again in the exact same way.
I pinpointed the problem down to Google Pay and not generically to NFC, because Android Beam and other NFC apps are working perfectly. I also tried an app from Visa that emulates a credit card for test purposes (Visa Mobile CDET), this app replaces Google Pay as Tap&Pay provider and when I test the NFC payment with that app set as default, it works, the test card is sent over to the receiving terminal. As soon as I change the default Tap&Pay to Google Pay, nothing happens anymore.
Some additional info: my OnePlus 5 has never been rooted, it is up to date with the latest firmware (OxygenOS 9.0.6). Google Pay is version: 2.90.250604638
Is anyone experiencing the same issue?
thanks a lot!
moebius83 said:
Hi all!
I'm writing here to see if someone has any idea, it seems I'm not able to understand the reason.
I setup Google Pay on my OnePlus 5 and it was working perfectly, up until some days ago. Now when I put the phone close to the POS, nothing happens, even if I open the Google Pay app before placing the phone near the terminal.
I performed a factory reset of the phone, after that, Google Pay started working again, but then, after a few hours, it just stopped with the same exact behavior, meanwhile I had restored the backup of most of my apps.
I again performed a factory reset, Google Pay started working properly, then slowly started re-installing and re-configuring my apps, constantly testing if Google Pay was working (luckily I found out how to "test" if Google Pay is working without having to buy something*), everything was working properly, but then, apparently without reason, Google Pay stopped working again in the exact same way.
I pinpointed the problem down to Google Pay and not generically to NFC, because Android Beam and other NFC apps are working perfectly. I also tried an app from Visa that emulates a credit card for test purposes (Visa Mobile CDET), this app replaces Google Pay as Tap&Pay provider and when I test the NFC payment with that app set as default, it works, the test card is sent over to the receiving terminal. As soon as I change the default Tap&Pay to Google Pay, nothing happens anymore.
Some additional info: my OnePlus 5 has never been rooted, it is up to date with the latest firmware (OxygenOS 9.0.6). Google Pay is version: 2.90.250604638
Is anyone experiencing the same issue?
thanks a lot!
Click to expand...
Click to collapse
Not directly, but maybe you get some ideas of those discussions for magisk/Google pay
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79016060
https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post79030908
spot on! thanks!
I never thought about Play Services, but that's the issue indeed.
The version I had installed was:
17.4.55 (100400-248795830)
May 21, 2019
arm64-v8a + armeabi-v7a
Android 9.0+
nodpi
Click to expand...
Click to collapse
I reverted to the previous one I found on apkmirror:
17.1.94 (100400-248977010)
May 21, 2019
arm64-v8a + armeabi-v7a
Android 9.0+
nodpi
Click to expand...
Click to collapse
and now Google Pay is working again.
I guess this means there was a bug introduced on the latest version or something like that, it's difficult to say without a changelog
At least this explains the random behavior, Play Services libraries are probably updated in background automatically.
thanks for the hint! Now I have to make sure Play Services libraries won't update automatically and I probably need to monitor new releases as I don't want to stick with an old version forever.
Opened a ticket on the google issue tracker: https://issuetracker.google.com/issues/135132389 please "star" it and add your comments, we need to understand if this is just a OnePlus issue.
Opened a ticket on OnePlus forum: https://forums.oneplus.com/threads/...-5-after-google-play-services-update.1053102/
Possible workaround, however not very straightforward and comfortable, but could be useful to troubleshoot:
- Install Visa Mobile CDET app: https://play.google.com/store/apps/details?id=com.visa.app.cdet&hl=en
- set it as default Tap&Pay app
- as "Use default" option, select "Except when another payment app is open"
- open Google Pay app and keep it in foreground
- pay with Google Pay
moebius83 said:
Opened a ticket on the google issue tracker: https://issuetracker.google.com/issues/135132389 please "star" it and add your comments, we need to understand if this is just a OnePlus issue.
Opened a ticket on OnePlus forum: https://forums.oneplus.com/threads/...-5-after-google-play-services-update.1053102/
Possible workaround, however not very straightforward and comfortable, but could be useful to troubleshoot:
- Install Visa Mobile CDET app: https://play.google.com/store/apps/details?id=com.visa.app.cdet&hl=en
- set it as default Tap&Pay app
- as "Use default" option, select "Except when another payment app is open"
- open Google Pay app and keep it in foreground
- pay with Google Pay
Click to expand...
Click to collapse
what is Visa Mobile CDET for? i've read the description on google play but i don't understand what it is supposed to do...
alessandro_xda said:
what is Visa Mobile CDET for? i've read the description on google play but i don't understand what it is supposed to do...
Click to expand...
Click to collapse
From what I understand, it emulates different types/technologies of contactless cards, so merchants can be sure their POSs are compatible with that type/technology of cards.
It should be "safe".
I tried the workaround, and I can confirm it works.
Now we just have to organize a meeting in Bologna, the issue seems to be here
andreacos92 said:
From what I understand, it emulates different types/technologies of contactless cards, so merchants can be sure their POSs are compatible with that type/technology of cards.
It should be "safe".
I tried the workaround, and I can confirm it works.
Now we just have to organize a meeting in Bologna, the issue seems to be here
Click to expand...
Click to collapse
Exactly, the app itself is not useful to us, but it lets you change Tap&Pay default to another app that is not Google Pay and this seems to be unlocking Google Pay for some reason.
I'm really starting to think that the issue is only in Bologna
moebius83 said:
Exactly, the app itself is not useful to us, but it lets you change Tap&Pay default to another app that is not Google Pay and this seems to be unlocking Google Pay for some reason.
I'm really starting to think that the issue is only in Bologna
Click to expand...
Click to collapse
maybe.
I've OOS 9.0.5, with franco kernel and latest magisk, and I've tried Gpay this week and it still work. /canada , visa.
oVeRdOsE. said:
maybe.
I've OOS 9.0.5, with franco kernel and latest magisk, and I've tried Gpay this week and it still work. /canada , visa.
Click to expand...
Click to collapse
Which Google Play Services and Google Pay version? Thanks
Hello everyone. Finally I found someone else with this problem! Since may/june 2019 I'm having this strange issue of Google Pay not working anymore. I've been in contact with Google and OnePlus, they reflashed OxygenOS but nothing solved the problem. Google Play Services is now updated to the version 19.4.20, but Google Pay and other NFC apps still don't work. The strange thing is that some NFC apps work properly, other do not work at all... Just like Google Pay. In the meantime, did someone found a stable solution? Thank you all.
Hello Frank!
the only workaround is the one described above, unfortunately, no solution is offered, but it seems it's some kind of compatibility issue with other nfc apps.
for example, andreacos92 realized that after a factory reset, Google pay works properly, but the moment he installed Muver (an Italian nfc app to use mobile bus tickets) and after the first reboot, Google pay stops working, even uninstall ing Muver will leave Google pay broken, the only solution is another factory reset.
any chance you're also using that app? Or perhaps another one using nfc?
if I flash magisk and things can I log into my starling banking app and view things like normal?
kevinireland11 said:
if I flash magisk and things can I log into my starling banking app and view things like normal?
Click to expand...
Click to collapse
as i know samsung pay will never work , dont know about bank app
Sent from my SM-N975F using Tapatalk
This depends on your Banking App, some of them still work but with a warning every time you start the App. Other ones won't work anymore, use your PC instead.
I agree with Phlipz91
Mine have been fine as long as they're hidden in Magisk
Hello,
I thought that I have covered all basic requirements, but for some reason Gpay doesn't work at my new Gen6.
Steps of activating it:
- Installed Gpay app
- Set up my Revolut card, which I also use at my mobile
- Have NFC & location on
Any ideas what maybe is the problem?
Wow, no one has got yet the Gen6 from here?
I have a Gen 6 and have been using GPay without issue. Just to start at the beginning, you are opening GPay on the watch before trying to tap, correct? I have the top user button set to open GPay, to make it easy to get to.
CSX321 said:
I have a Gen 6 and have been using GPay without issue. Just to start at the beginning, you are opening GPay on the watch before trying to tap, correct? I have the top user button set to open GPay, to make it easy to get to.
Click to expand...
Click to collapse
I found out that the problem is related to my geo, as gpay is not officially supported in my country although at my mobile it works pretty fine without any problems like at the Gen6.