Ever since about January 15th, I've been unable to user Google Pay on my Watch 4. It gives the error "Your phone can't make contactless payments as it doesn't meet software standards. Very odd, as GPay still works flawlessly on my S21+ (Stock AT&T, not rooted, no unlocked bootloader). Used to work perfectly until my last transaction on January 15th. I've tried uninstalling and reinstalling GPay on both my phone and my watch, but no luck. At least I can still use Samsung Pay on the watch, but one of the main reasons I go the watch was for Gpay.
Anyone else experience this?
Hurricane Andrew said:
Ever since about January 15th, I've been unable to user Google Pay on my Watch 4. It gives the error "Your phone can't make contactless payments as it doesn't meet software standards. Very odd, as GPay still works flawlessly on my S21+ (Stock AT&T, not rooted, no unlocked bootloader). Used to work perfectly until my last transaction on January 15th. I've tried uninstalling and reinstalling GPay on both my phone and my watch, but no luck. At least I can still use Samsung Pay on the watch, but one of the main reasons I go the watch was for Gpay.
Anyone else experience this?
Click to expand...
Click to collapse
Yes I've been having the same issue as well. My last transaction was Jan 22nd. I haven't been able to find a fix.
Seems the latest update has resolved the issue. Was finally able to use GPay yesterday at a local convenience store!
Related
I was jw how long it would be before we get a working version of wallet again since Google implemented a root checker. I remember that Google videos checked for root access but a work around was made. Could the same work around be made for wallet?
Sent from my Galaxy Nexus using Tapatalk
My wallet works fine with root?
I was just coming to post about this, here is my question:
Has anybody that is getting the "unsupported device" notification at the top of the Google Wallet home screen actually tried using Google Wallet yet? We're you successful?
As for a root workaround, OTA RootKeeper works just fine for me on other apps.. Google Video & Flixster. Problem is, Google Wallet isn't actually checking root, it's checking something else.. Maybe ROM version or kernel version?.
Sure it's prob a good idea Google warn that root+Wallet might not be the most secure. but is it "unsupported" as in, "if you can't get it working or if negative things happen because of root we are not responsible"? Or "unsupported" as in "if you try to use this on a rooted device we will not let you and you will look foolish at the store"? It's not very clear about that..
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
danger-rat said:
My wallet works fine with root?
Click to expand...
Click to collapse
Sure, in the past every bodies has, this is a new topic regarding the "unsupported device" yellow flag on the GW home screen. This will just appear magically as of yesterday. No update of GW is needed/required to get this "unsupported" tag, it has just mysteriously appeared with little to no explaination of what it means.
I'm still just having the "Prepaid is unavailable" error. I can't wait for something else to come and actually work. GW fails atm.
Just checked with Google CS. Unsupported means that it soon not work at all.
Sent from my Galaxy Nexus using Tapatalk
I get the unsupported device as well 4.0.4 rooted. I might try and go to 4.0.4 without root and see what happens (if it makes a difference)
peanut_butter said:
Just checked with Google CS. Unsupported means that it soon not work at all.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I also just spoke with GW CS, according to what I was told "unsupported" means if there is a glitch in the app causing it to not work correctly (pressing a button does not work and so on..), Google is not responsible for troubleshooting the app. Google Wallet should continue to function properly on rooted devices. Google currently has no plans of making Google Wallet unusable on rooted devices. If you lose your phone, you can still cancel/ retrieve your funds, in the words of the rep I spoke with "Your money is your money". so not sure who you spoke with or why you were told different than me, but according to the rep I just got off the phone with you are incorrect.
My 2 cents...
VZW just replaced my GN because I was having radio problems (they screwed me with a refurb .9 hardware, but that is another story...)
On my first GN I just sent back after a wipe, I was using both the officially supported Citi Mastercard and the Google Prepaid card.
When I got my replacement, I couldn't re-add my Citi Mastercard and my Google Prepaid card was showing the "free" $10 credit, but I actually had more than that amount as a pre-paid balance because I had added funds to it.
So, I called Google/Citi support and they had to do something on their end to allow me to add my Citi MasterCard back on the phone, because when I was trying to do it myself it kept giving me an error that my info was incorrect. So, Citi customer service was able to fix that and I now have my credit card registered.
However, I still can't add funds to the Google Pre-Paid card from either another credit card or a rebate gift card I have. I spoke to Google about that and they said that at this time, you cannot add funds to the pre-paid account because they are issuing an update for the wallet app by the end of this week.
Hope that helps someone else...
-Rob
robroy90 said:
However, I still can't add funds to the Google Pre-Paid card from either another credit card or a rebate gift card I have. I spoke to Google about that and they said that at this time, you cannot add funds to the pre-paid account because they are issuing an update for the wallet app by the end of this week.
Click to expand...
Click to collapse
I was able to add $20 to my Google Pre-Paid card a few hours ago. Several days ago I tried to use my VZW "referral" rebate card that VZW sent me and it wouldnt add the funds. I'm about to run down to the Walgreens now and try to make a purchase. I don't expect I will have any problems but if I do I will report them back here.
Got the email from google telling me that they have switched to Android pay and the link to download it via the play store. I get the message that my device is not compatible with it when I get to the play store. Pretty sure I am not the only one who is frustrated with this. Hoped it will get baked in when google bought softcard (ISIS). Tried side loading the apk, but i just get the message that it is unavailable when i try to open the app.:crying::crying::crying:
I actually called Google about it, asking specifically if it would work, even giving "Ross" the heads up that wallet tap to pay never did. He assured me it would, of course it doesn't, I replied to him letting him know. Will be interesting to see what he comes back with.
DesperateScorpion said:
Got the email from google telling me that they have switched to Android pay and the link to download it via the play store. I get the message that my device is not compatible with it when I get to the play store. Pretty sure I am not the only one who is frustrated with this. Hoped it will get baked in when google bought softcard (ISIS). Tried side loading the apk, but i just get the message that it is unavailable when i try to open the app.:crying::crying::crying:
Click to expand...
Click to collapse
It must be a T-Mobile thing. Sprint Note 3 has it: http://forum.xda-developers.com/note-3-sprint/general/android-pay-error-rooted-devices-t3204203
Were you rooted when you tried to install? For the initial install you must be unrooted. But showing incompatible on Play sounds like a carrier issue to me.
Did anyone ever get NFC working on their T-Mobile Note 3? I never could. Which sucks balls because I really want to do away with carrying so many pieces of plastic.
KennyG123 said:
It must be a T-Mobile thing. Sprint Note 3 has it: http://forum.xda-developers.com/note-3-sprint/general/android-pay-error-rooted-devices-t3204203
Were you rooted when you tried to install? For the initial install you must be unrooted. But showing incompatible on Play sounds like a carrier issue to me.
Click to expand...
Click to collapse
It might be carrier related. Tmobile, AT&T and Verizon were the backers for Softcard in the beginning. You had to have Softcard compatible sim cards to use the payment features of softcard. I dont have the same sim card anymore, not sure if that will make a difference.
Rooted or not, you dont have access to the app on the app store.
Any luck on this issue.?
I did call Google and they told me that since my phone was used with softcard it cannot be used with Apple Pay.
I thought Android Pay would supersede Softcard since Google bought the thing... I think someone should call T-Mobile as well and ask them how else can we make NFC payments with everything not functional.
Tmobil official word
I called T mobile and tech support said Note 3 ( and several others) are NOT compatible.
Tech is updating all the customer support cheet sheets so no one else has to go through this with them.
Somehow I just knew this Pay app fiasco (ISIS, etc) would end badly for us.. If the greedy corporate SOB's would have just gone with Google in the first place.. I hope they learned something
Is a class action in the cards for NOTE 3 owners ?? Any Lawyers out there ?
I installed Android Pay through the APK mirror APK, it installed perfectly with no errors and detected my NFC. I'm using the AT&T Note 3 (4.4.4 KitKat) ( N900a). I just need some place to test it now.
Keep us posted. Glad to see note 3 still kicking it.
Installed it on my note 3 tmobile bit I use cricket with it. Can't test it or anything as the rom I have from ages ago nfc won't turn on
futty said:
Installed it on my note 3 tmobile bit I use cricket with it. Can't test it or anything as the rom I have from ages ago nfc won't turn on
Click to expand...
Click to collapse
Android pay refuses to work if it detects that a device has been rooted. I switched back to the official Android 5.0 lollipop release for my Note 3 and Android pay works with no issues. I have added cards and successfully completed several purchases.
I did replace my battery last year, my current battery is an official Samsung battery manufactured in November 2015. Since some of the NFC hardware is in the battery this may have have helped my success with Android pay on my Galaxy Note 3
So I just tried to setup my Samsung Pay and it says this device is not compatible??!!
I have unlocked model on Sprint.
Just wondering if anyone else has similar issue to know it will self-resolve over time maybe or if something is funky here.
Very annoying as I used it a ton on my S7....
I have no issues using it on my unlocked S9.
bryanu said:
So I just tried to setup my Samsung Pay and it says this device is not compatible??!!
I have unlocked model on Sprint.
Just wondering if anyone else has similar issue to know it will self-resolve over time maybe or if something is funky here.
Very annoying as I used it a ton on my S7....
Click to expand...
Click to collapse
I have never used Samsung Pay but Google Pay is working fine on my S9 :good:
I set it all up and went to add my cards but all of them were incompatible. My banks prefer to use their own contactless payment methods or Google Pay.
bryanu said:
So I just tried to setup my Samsung Pay and it says this device is not compatible??!!
I have unlocked model on Sprint.
Just wondering if anyone else has similar issue to know it will self-resolve over time maybe or if something is funky here.
Very annoying as I used it a ton on my S7....
Click to expand...
Click to collapse
I"m having the same issue to. Anytime I try to use it, it says to update it. The samsung pay in the galaxy app store is updated. So uninstalling that one and installing the one from the play store says it's incompatible with my phone.
But, it sounds like Samsung is aware of the issue and will be updating the galaxy apps version soon
https://www.reddit.com/r/GalaxyS9/comments/848mxn/samsung_pay_incompatible/
https://www.reddit.com/r/GalaxyS9/comments/848mxn/samsung_pay_incompatible/dvpgqv7/
So I flashed my phone to the sprint FW and that one seems to work fine so must indeed be something with the US unlocked ones maybe on some providers or how it was updated etc.
I just tested mine and it works on the unlocked version.
For those that are working are you US based or intl?
I'm also wondering if it's app ver related, carrier related for unlocked or what lol.
I now have another issue with VM not working so am torn what FW I even want to run now lol. Downfall of early adopter I guess hah
Mine works fine with tmobile
Mine does not work. US unlocked snapdragon model. Keeps telling me to update app but there is not an update.
On T-Mobile US, and it works fine here. I didn't try it until after the day 1 update they pushed yesterday, so maybe that was the key?
bryanu said:
For those that are working are you US based or intl?
I'm also wondering if it's app ver related, carrier related for unlocked or what lol.
I now have another issue with VM not working so am torn what FW I even want to run now lol. Downfall of early adopter I guess hah
Click to expand...
Click to collapse
cdudeman said:
Mine does not work. US unlocked snapdragon model. Keeps telling me to update app but there is not an update.
Click to expand...
Click to collapse
I've been having the same issues on my USA unlocked S9+, but there's an update in the Galaxy app store today that finally gets me past that "need an update" screen. Go check!!
There is an update for Samsung pay that came out last night and now it works for me. I updated through the Galaxy app store.
When I use it my phone get stuck in wireless charging mode and to remove it igot reboot phone
I have the S8 Plus Hong Kong variant. Samsung Pay only worked for Hong Kong based banks. Uninstalled the app then installed the latest version on Play Store. Works fine now so Samsung did update the app. I'm pretty sure whoever you bank with needs to have a processing application which is compatible with Samsung Pay.
Hi every Samsung Pay user,
tl;dr: When I use Samsung Pay (France) on my S20+ 5G, it always fails the first time, I have to make the payment twice for it to work once.
I've got a S20+ 5G (G986B) in France, with CSC XEF/BOG. I've installed and configured Samsung Pay, as I did with my Note9 (same credit card). But nearly every time I try to pay with my S20+, the card machine recognizes the phone but refuses the payment the first time (the phone still thinks it was successful), and I have to try again right away for the payment to finally work.
This is quite frustrating as my Note9 (that I still own and use) always makes contactless payments right the first time. I know the NFC antenna isn't placed at the same spot for both phones, but each time I place the phone correctly depending on its NFC position. Also I'm using a Samsung Clear View case, so that souldn't be a problem either?
I may try Google Pay to see if it shows a similar problem, but for now I can't because I'm on OneUI 3 beta and I can't use GPay temporarily (this SPay issue was present on OneUI 2.5 too though).
Does anyone have the same issue, or some way to fix it? I still pay with my Note9 mainly because it works everytime. And I don't use my Watch that much because it doesn't work everywhere, and I often get my phone out for the fidelity cards anyway so, I may as well use it for payment too
Had exactly the same issue on 2.5, since moved back to google pay havent had that issue ever again
Hi, there's a reoccurring problem with eSIMs on Mint mobile. One of the Mint admins/executive team members posts service updates on Reddit and over the course of Nov-Dec posted that there were problems but eSIM was now working. Well it's not. I switched to eSIM and my physical SIM (pSIM) stopped working while the eSIM is non functional. I reached out to tech support and they told me the pSIM stopped working when I switched the eSIM and I would need a new pSIM. They told me they are having issues with Pixel 6 eSIM. The pSIM was mailed out to me and I'm still waiting. They tried to charge me for it! But they sent it free and expedited after I pointed out it was their fault for offering eSIM when they know about the issues. I am currently without service until the pSIM arrives, which hopefully will be tomorrow but with the snowstorm may not be until later. I'm also worried in case the snow storm causes internet outages as without a phone connection I would then have no way to contact the outer world.
A bunch of people have posted to say they managed to get their eSIM working on Mint mobile without doing anything special. My question is - Although this seems to be largely a carrier issue, is there anything anyone here can suggest to try and get my eSIM working? I've tried scanning the QR code and also entering in the details manually with the string: LPA:1$SM-DP+Address$activation code (with the values filled in). Is there a setting or different method anyone can suggest to try and get things working on my end? Executive support have reached out, but it's been 2 days since their last message. Thanks!
Hi, are you on the January update? No idea if that or a factory reset would help.
roirraW edor ehT said:
Hi, are you on the January update? No idea if that or a factory reset would help.
Click to expand...
Click to collapse
I was on Dec update, then updated to Jan and it still didn't work. I got it fixed in the end. I reordered a new eSIM and the second one worked. Apparently it's a bug on the Mint system and sometimes you need to download a few eSIMs before you get one which works. Annoying.