I have a very weird issue with enabling contactless payments with some of my cards.
I was able to add this Mastercard and enable contactless payments for this card when I first reinstalled my ROM (Pixel Experience). I then removed the card from GPay and try to add it again and it is failing when it tries to verify the details with the bank and I end up getting this error message to call the bank.
https://imgur.com/0Q0MFRG
The bank says they have reset everything and the card should be able to be readded again but still receive same error.
I also got a BRAND NEW Mastercard from another bank and it also fails with the above error.
Contacted Google support and they mention to get the bank to reset the tokens and the banks say its Googles fault.
The thing is I have a third VISA debit card which I can add and enable contactless payments no issues.
Anyone have similar issues or know how to fix?
I have no idea what happened, but it just started working again. I have no done anything on my end. Both my Mastercard's are now added and enabled for contactless payments. Maybe a mastercard thing?
Related
I purchased a Sprint Galaxy S3 off of eBay and I found out that the phone was still active.
I wanted to use the phone with Ting but I can’t because the previous owner did not deactivate this phone. I tried porting the phone number to Ting but I can’t because I need his account number and password from Sprint. I can’t get a new number because the device is currently active. I have tried contacting Sprint several times to get them to deactivate the phone and they refused every single time.
I have tried contacting the previous owner (his email address is in the phone) but my emails always return errors. So, his email address is currently in active. I really like this phone and I don’t want to give it up. I got this phone on August 6 and I was waiting for Sprint to deactivate it on the 25th (this information is in the phone) but instead of deactivating the phone, it is now showing current service from August 26 through September 25….
Why didn’t they deactivate this phone? Surely he isn’t still paying for it… He doesn’t even have the phone. Is there anyway to deactivate this phone? Is there anyway to force deactivation?
I have a problem with several local government-issued apps, that rely on identity information. In particular, transport ticketing and parking payments:
https://play.google.com/store/apps/details?id=lt.sisp.itero.ticket.client
https://play.google.com/store/apps/details?id=lt.sisp.itero.parking.client
The problem is, these apps are unable to identify me, and the services do not work. They operate on basis of telephone number and one of them (parking) even includes parking fees in to telephone invoice.
I have investigated this with the authorities and we came to conclusion that the problem is with my phone.
Even though Identity is listed in app Permissions, it is unavailable on Permission Manager list. I only can set permissions for location, sending MMS and making calls.
I do also use a mobile signature on second SIM card and it works very well (I had problems on Samsunf i9192 earlier).
Any thoughts? Do I have some kind of global privacy restrictions set?
Depends on the government. I know the US government has blocked Xiaomi and huwawi devices from working in official things like that.
So I bought my husband a cheap smart watch without knowing the first thing about them (first mistake), and I asked the seller if it could be used WITHOUT a sim card - just using Bluetooth to connect to the phone. They said yes it could so I bought it (apparently 2nd mistake lol).
Do any of you know - can it be used without a sim card and still access messaging and Facebook? He can make and receive calls fine but can't access Facebook or messaging at all. If he needs a sim card we'll probably just have to get rid of it because his phone service does not use sim cards (straight talk - non BYOD plan) so he would have to get a separate plan and phone number just to use the stupid thing. I mean he can always just use it for phone calls only but it seems kind of pointless if you don't have messaging.
Any advice would be appreciated
Thanks!
I submitted the post below to the AT&T Community hoping to get some answers. So far I gotten none. No one from AT&T support has been able to figure out how to re-provisione my watch 4 classic. I'm posting it here to see is someone has an idea of what could be happening. I think the issue is that no matter what they/we do the ICCID in the watch remains the same. (This ICCID is the original one installed scanning the UPC of an activation card that came with the watch) We have factory reset it and tried adding another eSIM, but the ICCID doesn't change. The current (unchangeable) ICCID has been flagged on their systems for some reason and it can not be reused. Has anyone experienced a similar issue... and if so how did you resolve it.
"My numbersync stopped working a couple weeks ago and after spending almost 3 hours on Saturday with an AT&T Phone Support rep... she ended up manually deactivating and tried re-activating the phone service for my watch. After entering all required activation codes manually (ICCID, IMEI... etc) on AT&T systems my "AT&T purchased" Galaxy Watch 4 Classic ended up with a "SIM not provisioned MM#2" error message. We tried factory resetting the watch 4 and restarting it multiple times, but the error would no go away. Long story short, she said that the only way to get it re-provisioned was for me to visit a AT&T store and get a new eSim card with a UPC with the Activation codes. Well, I went to the AT&T store in my neighborhood and spent 3 hour there. They tried a couple of new eSim cards and they could not get the watch to get activated. The store clerk called 2nd level tech support and the technician said that the only way that he could fix was if I got a new phone number. Reluctantly, I agreed, but that didn't work either. I still get the SIM not provisioned error. In the process to try to fix it, the battery of the watch ran out and they didn't have a compatible charger in the store. I plan to return to the store again tomorrow with my charger and my wife's Watch 4 which is working correctly with numbersync. The rep suggested that "maybe" the numbersync service was changed to require that it be used with the same phone number as my phone. This was never the case, I had a S3 Frontier for 3 years and upgraded to the Galaxy Watch 4 Classic for about 5 months and both had their own unique phone numbers that allowed the watches to make and receive phone calls independent of the Phone. Or work with numbersync when I turned it on. I could make phone calls to the watch phone number and make calls from it. Now it has been suggested that it needs to use the phone number from the phone to do so... Someone from AT&T with expertise in SIM provisioning for Galaxy watch 4 watches and numbersync... PLEASE!... get to the bottom of this issue."
tamanaco said:
I submitted the post below to the AT&T Community hoping to get some answers. So far I gotten none. No one from AT&T support has been able to figure out how to re-provisione my watch 4 classic. I'm posting it here to see is someone has an idea of what could be happening. I think the issue is that no matter what they/we do the ICCID in the watch remains the same. (This ICCID is the original one installed scanning the UPC of an activation card that came with the watch) We have factory reset it and tried adding another eSIM, but the ICCID doesn't change. The current (unchangeable) ICCID has been flagged on their systems for some reason and it can not be reused. Has anyone experienced a similar issue... and if so how did you resolve it.
"My numbersync stopped working a couple weeks ago and after spending almost 3 hours on Saturday with an AT&T Phone Support rep... she ended up manually deactivating and tried re-activating the phone service for my watch. After entering all required activation codes manually (ICCID, IMEI... etc) on AT&T systems my "AT&T purchased" Galaxy Watch 4 Classic ended up with a "SIM not provisioned MM#2" error message. We tried factory resetting the watch 4 and restarting it multiple times, but the error would no go away. Long story short, she said that the only way to get it re-provisioned was for me to visit a AT&T store and get a new eSim card with a UPC with the Activation codes. Well, I went to the AT&T store in my neighborhood and spent 3 hour there. They tried a couple of new eSim cards and they could not get the watch to get activated. The store clerk called 2nd level tech support and the technician said that the only way that he could fix was if I got a new phone number. Reluctantly, I agreed, but that didn't work either. I still get the SIM not provisioned error. In the process to try to fix it, the battery of the watch ran out and they didn't have a compatible charger in the store. I plan to return to the store again tomorrow with my charger and my wife's Watch 4 which is working correctly with numbersync. The rep suggested that "maybe" the numbersync service was changed to require that it be used with the same phone number as my phone. This was never the case, I had a S3 Frontier for 3 years and upgraded to the Galaxy Watch 4 Classic for about 5 months and both had their own unique phone numbers that allowed the watches to make and receive phone calls independent of the Phone. Or work with numbersync when I turned it on. I could make phone calls to the watch phone number and make calls from it. Now it has been suggested that it needs to use the phone number from the phone to do so... Someone from AT&T with expertise in SIM provisioning for Galaxy watch 4 watches and numbersync... PLEASE!... get to the bottom of this issue."
Click to expand...
Click to collapse
Your going to have to call tier 2 and have them remove all but the last number they tried to activate the watch with. Have them reprovision the last number and wait 24 hours. Then after 24 hours go to settings and try to activate mobile network and you should be good.Do not use the card to activate because with the newer watches don't use them.I hope this helps....
The issue with the "SIM not provisioned MM#2 " error was resolved. But my original issue with NumberSync remains. Below is the follow up that I posted in the AT&T Community.
"I spent about an hour or so in the AT&T store yesterday. Long story short... the issue was related to adding the ICCID to the watch using the Wearables app and selecting "New Plan". - Rep in the store kept factory resetting the watch and starting the activation process from scratch and selecting "Existing Plan" because as he said... we didn't want to add charges to my account.
The issue was solved by getting a new UPC in eSIM card and working along with a 2nd level tech support rep over the phone. Scanning the UPC code of a new eSIM card and making sure to select "Add to Watch" in the Wearable App as there are two options (One is for the phone) We had used this option before, but it would not overwrite the existing ICCID in the watch... reason being that we were selecting "Existing Plan!" This time we selected "New Plan!" with the new eSIM. The 2nd level support tech over the phone also made sure that the ICCID was active on their system before we added it to the watch via the Wearable app. SIM not provisioned error gone and the watch can make and receive calls.... BUT!
We could not get NumberSync to work no matter what we tried. We keep getting the following on the Wearable App when we try to activate it either from the watch or from the phone "Code: PD-GE-RsC-NullPointerException". Ended up opening a case number with the AT&T 2nd level rep related to this issue. If the issue doesn't resolve itself in the next 10 days I'm suppose to call back. "I" believe there's something wrong with the process that enables NumberSync on Watch 4 with Samsung S21 phones running Android 12 in the AT&T network. I always found that activation/deactivation of NumberSync to be a bit wonky. It sometimes deactivated itself for no apparent reason. I have hundreds of AT&T text messages saying... "You've suspended NumberSync for wearables...". Of course in 99% of those instances "I" had not suspended anything.
I have an AT&T Galaxy 4 Classic and a AT&T Samsung Galaxy S21+ running Android 12 Build G996USQU5BULJ and Wearable App version 2.2.47.21122061 with Galaxy Watch 4 Plugin version 2.2.11.21120251"
tamanaco said:
The issue with the "SIM not provisioned MM#2 " error was resolved. But my original issue with NumberSync remains. Below is the follow up that I posted in the AT&T Community.
"I spent about an hour or so in the AT&T store yesterday. Long story short... the issue was related to adding the ICCID to the watch using the Wearables app and selecting "New Plan". - Rep in the store kept factory resetting the watch and starting the activation process from scratch and selecting "Existing Plan" because as he said... we didn't want to add charges to my account.
The issue was solved by getting a new UPC in eSIM card and working along with a 2nd level tech support rep over the phone. Scanning the UPC code of a new eSIM card and making sure to select "Add to Watch" in the Wearable App as there are two options (One is for the phone) We had used this option before, but it would not overwrite the existing ICCID in the watch... reason being that we were selecting "Existing Plan!" This time we selected "New Plan!" with the new eSIM. The 2nd level support tech over the phone also made sure that the ICCID was active on their system before we added it to the watch via the Wearable app. SIM not provisioned error gone and the watch can make and receive calls.... BUT!
We could not get NumberSync to work no matter what we tried. We keep getting the following on the Wearable App when we try to activate it either from the watch or from the phone "Code: PD-GE-RsC-NullPointerException". Ended up opening a case number with the AT&T 2nd level rep related to this issue. If the issue doesn't resolve itself in the next 10 days I'm suppose to call back. "I" believe there's something wrong with the process that enables NumberSync on Watch 4 with Samsung S21 phones running Android 12 in the AT&T network. I always found that activation/deactivation of NumberSync to be a bit wonky. It sometimes deactivated itself for no apparent reason. I have hundreds of AT&T text messages saying... "You've suspended NumberSync for wearables...". Of course in 99% of those instances "I" had not suspended anything.
I have an AT&T Galaxy 4 Classic and a AT&T Samsung Galaxy S21+ running Android 12 Build G996USQU5BULJ and Wearable App version 2.2.47.21122061 with Galaxy Watch 4 Plugin version 2.2.11.21120251"
Click to expand...
Click to collapse
You may need to call samsung and make sure the watch is not black flagged. There was a batch of watches with known issues by samsung.
All the luck in the world to you to get through to Samsung. You should try to get this escalated quickly to the next level. I am making a bad joke here, but from my own experience you only get stuff done if you are at tier 4 or 5.
Apparently the error "Code: PD-GE-RsC-NullPointerException" with NumberSync was an issue on the AT&T network side. This morning without making any configuration changes to either my Watch 4 Classic or my S21+, I was able to re-enable NumberSync following the steps that start with getting an activation code.
I was wondering how many people have a Watch 4 Classic that they have successfully activated on any carrier. How many people are NOT able to activate the Watch 4 Classic?
I am one among the so many people who have not been able to activate the Galaxy Watch 4 classic on my service provider. I have spent hours and hours with Verizon reps, including tier 2 support, and they are not able to get it to activate via Wearable app. The Watch was also recently "repaired" by Samsung support (3 days ago) and still it will not activate.
1. Using QR code -- here I have to use the hidden menu to turn on QR code scanning -- I get the error "Code not valid or is already used". The Watch has been set up in both standalone (separate line) and number sharing mode.
2. Without QR code and directly querying the service provider I get error : Error 109: "Your service provider has not set up plan yet".
Now Verizon reps are ghosting me -- they just vanish -- after some time trying to fix the issue. I was with a rep last night trying to fix this who acknowledged that this was known issue and supposedly had fixed the issue for many other users. She almost swore she could fix my issue -- but of course not, and then she ghosted me. She quoted me internal messages from VZW implying the situation is known about internally and QR codes should not be used for these Watches. Whatever.
If anyone has any solutions it is greatly appreciated !!
Took At&t 7months to fix this issue on my daughter's watch. We tried Qr code did not work..numerous esim Sent through mail. The issue was that a rep entered something wrong when we purchased. Only solution for us was to have her cell number changed and we were then able to number sync
butchieboy said:
Took At&t 7months to fix this issue on my daughter's watch. We tried Qr code did not work..numerous esim Sent through mail. The issue was that a rep entered something wrong when we purchased. Only solution for us was to have her cell number changed and we were then able to number sync
Click to expand...
Click to collapse
Thanks for your reply!
Yes, it does seem that AT&T has finally gotten device-specific QR codes to work. But VZW seems unable to doit, even after two separate chats with their "Tier 2" chat. This is a simple matter of entering the wrong info while setting up the QR Code or the device account because without QR code I get an error "Your service provider has not set up a plan for the device". WTF?
Probably silly question. But have you made sure imei is correct on Verizons end? Make sure they have your watch in their system as wearable and not device. That was another issue we had.
butchieboy said:
Probably silly question. But have you made sure imei is correct on Verizons end? Make sure they have your watch in their system as wearable and not device. That was another issue we had.
Click to expand...
Click to collapse
Aha! Is there a difference between Wearable and device? I did not know that distinction existed.....
EDIT: This drew a blank out the Verizon rep. "It is a wactch so it is already a wearable"