03-02-2025 06:38 PM
New S25 Ultra, and I can't figure this out. Added a card to Google Wallet. It says it's setup correctly, everything is ticked, NFC on, Wallet is default, etc. however when I go to pay, nothing happens. Only when I open Google Wallet does it spring to life and work. It's not a verification issue, just nothing happens at all, as if the phone hasn't registered a card reader is present.
Tried uninstalling and reinstalling and all that, but not something I can easily test, as I have to go and buy another coffee every time but it still fails to respond when waving it over a card reader. Any suggestions?
17-02-2025 03:50 AM
I was able to make it work on my side. I initially registered both fingerprint and face unlock on the phone. Removing face unlock allowed me to fix the problem.
Prior to that fix I noticed that when I opened Google wallet, it would always ask me to verify myself even tho the phone was already unlocked. If it doesn't ask you to verify yourself after removing face unlock the problem should be fixed I think.
17-02-2025 09:34 AM - last edited 17-02-2025 09:34 AM
Thanks for the reply but it's not a verification issue with me. I don't use face unlock, and I'm getting no response when trying to pay, not a verification failure.
Opening wallet from the quick tile however seems to work, though no idea why that's different to opening from the home screen, and I shouldn't have to open the app at all anyway.
Hopefully the next update will help, whenever that arrives.
09-03-2025 11:20 PM
None of the suggestions has worked for me yet. I have tried adjusting battery optimization, etc etc but still randomly it does not work. It's frustrating to pay so much for a phone that can't do this basic functionality.
10-03-2025 07:57 PM
13-03-2025 11:00 AM
Same issue with S25 (basic, non ultra). It's software bug, we need to wait.
13-03-2025 11:03 AM
Probably help to report to Google and Samsung as waiting wont matter if they don't see it as a problem affecting many people.
14-03-2025 10:52 PM
I'm having the same issue and was surprised to find out so many people are reporting this over here and on reddit for over a month now without any help from Samsung. It's a disappointment to say the least..
17-03-2025 12:41 PM
I reported this bug to Samsung and they replied that the problem would be fixed in the next update. We'll se.
17-03-2025 01:58 PM
That's what the last clueless call handler told me before the last update, and I waited, and it didn't help.
18-03-2025 11:29 AM - last edited 21-03-2025 07:28 AM
there is nothing else we can do but wait.