Ultimate Question:
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
Background:
I've had Samsung Pay on my Gear S2 watch since it has been available, and it works better than I expected it to. It is obviously limited to NFC payment terminals, as the S2 has no Magnetic Secure Transmission device.
Enter the Gear S3, now with MST payment technology.
Linked it to my phone with zero issues entered my credit-card information, and was validated on Samsung Pay in less than ten minutes on the Gear S3.
At this point, my Gear S2 and the new Gear S3 are both enabled as payment devices using the same credit-card.
Take off the S3, put on the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S2 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
WTF? I go ahead and re-add the S2, call the bank, yadda yadda, and the S2 is back with my Visa enabled on it.
Yep. Now pick up the S3, and put down the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S3 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
100% reproducible.
I did this back-and-forth with the bank about 10 times last night, before someone there transferred me to the manager who asked if I could maybe spread out my token-requests over a few days.
Meanwhile my wife's S2 with Samsung Pay and the same card account is not affected by this at all - it seems that you're only allowed one Gear S watch at a time in which to have your Samsung Pay information stored, if they share a common phone. Authorize one, and as soon as you switch to the other it will de-authorize the card on that device. The bank assures me they are not doing this on their end.
My ultimate solution at this time is to have done a light-reset on my S2, powered it down, and put it on the charger until this can get straightened out. After doing that, I could get my card re-authorized on the S3 and it has been showing active for several hours now
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
I have a similar experience. Switch watch on the Gear manager app and all the Samsung Pay credit cards are deleted.
It appears that credit cards can be authorised on both phone and watch but not on two watches at the same time.
Thanks for confirming. I'd hoped this was just a configuration issue on my end.
Considering one of the stand-out features of the watch(es) is the Samsung Pay functionality, I'd say this sort of renders useless that cool auto-switch capability in the Gear Manager.
I had spent over an hour on the phone with Samsung Pay support, describing the problem, and was told I'd be getting a confirmation email with a case-number for the support issue. Several days later - with the email noticibly absent from my inbox - I called again to inquire.
No solution, no case-number, no notes on my account. No record I'd ever even called.
Nice.
Samsung Pay for Gear only supports 1 watch at a time
I had a similar issue, but I am using both S3 models. I was finally able to get someone at Samsung Pay support that new about the issue. He explained that the Samsung Pay Gear app registers as it's in device for mobile payments. That device can only have one watch associated with it. So as you register and use your second watch, the first watch is deregistered.
There was a workaround available in my case. Since I have a second Galaxy phone and my S3 Frontier is the at&t model with it's own connectivity. I was able to register my classic with my normal phone and my Frontier with my other phone. The frontier doesn't need the phone to be connected when I use it for transactions, since it has it's own connectivity. It's a bad workaround, but it has worked for the last month.
With MST transactions being a big selling point of the Gear S3, I count this as a complete fail on Samsung's part. I wanted both S3 for their different styles, but I am now looking at offloading one because the user experience is not seamless between the two.
I think Samsung never considered someone would have more than one watch each with Samsung Pay on it.
Sent from my SM-N930T using Tapatalk
beauzeaux said:
There was a workaround available in my case. Since I have a second Galaxy phone and my S3 Frontier is the at&t model with it's own connectivity. I was able to register my classic with my normal phone and my Frontier with my other phone. The frontier doesn't need the phone to be connected when I use it for transactions, since it has it's own connectivity. It's a bad workaround, but it has worked for the last month.
Click to expand...
Click to collapse
Doing a Samsung Pay transaction doesn't require connectivity. MST and NFC are hardware technologies. So both versions of the Frontier and the Classic models are S Pay capable.
Being able to pair a watch with 2 different phones is problematic. That would be the case with any Tizen or AW watch because it is a slave and master relationship. Which phones' contacts to use, which Facebook/Twitter account, which email, which messaging, etc. The solution is for watches to become independent- with standalone apps that pull directly from the servers (rather than going thru a phone). That is, essentially become a 1" smartphone.
Silly me, thinking that the new Gear manager's auto-switch capability would include preserving the Samsung Pay card registration on both watches.
It does not.
As a matter of fact, it disables the cards on both watches and will require you to re-authorize the cards on which ever watch you decide to use.
Yes, you're right. You can only activate credit card with one watch, not both. I've tested this very thoroughly and there's no way around this lim fact. What I've done is disable all connectivity on one watch and loaded the other one. I wear this one during the day and the other one at night. Best workaround I've found. Or you can add a second card on your second watch.
Sent from my MHA-L29 using Tapatalk
Samsung Pay doesn't work with two gear watches
I have two gear S3 watches, I can pair both to my S8 plus. The problem is setting up Samsung pay to use and work with two different Gear watches on the same phone, and use the same debit card. 1) both watches are to use the same debit cards. 2) One watch ("A") is active and linked to the phone. 3) setup the debit card on the phone for watch "A" using Samsung pay--all is fine to this point. On the watch SP works fine.
Now the problem: Turn off watch "A" and turn on watch "B", link "B" to the phone, proceed to setup SP. The first thing that happens is the previous working debit card is deleted and I,m prompted to re-setup the same debit card that was deleted. Now it's working for phone"B" just fine. Samsung Pay (SP) no longer works on phone "A" and will need to be setup again. Samsung Pay can't work with two gear S3 watches on the same phone. SP can only have one setup per phone, and each time you turn on a 2nd gear S3 watch, the exsisting SP setup is deleted. Why would anyone have a 2nd Gear S3 watch which will not be able to function correctly.
How does one setup two Gear S3 watches to work with Samsung Pay on the same phone? This is a MAJOR PROBLEM and needs to be addressed.
---------- Post added at 01:27 AM ---------- Previous post was at 01:07 AM ----------
The only way I could get Samsung pay to work on two watches was to first link watch "A" to the phone. Setup Samsung Pay (SP) on watch "A", adding two debit cards. Then turn off "Bluetooth" on the watch, so the watch does not link with the phone anymore. You might ask why have the 2nd watch at all if it's not linked to the phone, and that is the 64 dollar question I keep asking myself.
Turn off watch "A". Turn on watch "B",proceed to setup SP in the normal way (at this point all the debit cards used for watch "A" will have be deleted). Re-install the debit cards again (this madness---nuts). Now Samsung pay will work on both watches, but one watch no longer links to the phone--no incoming calls, no text messages, no email, but you have SP working.
Samsung are you listening...... This needs to get corrected....
jag5001 said:
Yes, you're right. You can only activate credit card with one watch, not both. I've tested this very thoroughly and there's no way around this lim fact. What I've done is disable all connectivity on one watch and loaded the other one. I wear this one during the day and the other one at night. Best workaround I've found. Or you can add a second card on your second watch.
Click to expand...
Click to collapse
If the problem is the same card can't be used on two different watches, the simplest solution is to have your bank issue a second card linked to the same account (ie. upload your spouse's card)
Hopeful that Samsung sends an update to allow this.
afblangley said:
If the problem is the same card can't be used on two different watches, the simplest solution is to have your bank issue a second card linked to the same account (ie. upload your spouse's card)
Click to expand...
Click to collapse
I've tried using my wife's card. It does not work, the same results only one Samsung account, per watch at the same time.
Same issue with me, S8 with both S3 Classic and Frontier. Its not that you can't have the same card on both watches, you can't have any cards active on both watches. Whatever cards registered on one watch are immediately deleted as soon as the phone connects to the other watch.
I also tried contacting Samsung Pay support on twitter. After a long back-and-forth they simply tell me to contact samsung support instead. Seems they are not aware of this issue. They told me they do not have two S3's on hand to try and replicate this problem.
I end up not using samsung pay at all as the hassle of adding even a single card every time I switch watches is too much hassle. This is a major bummer...
Just purchased my second S3 so I can have a nice watch for off duty and a beat up one for on duty use. I'm having the same problem. Researched and found this thread for info. At least now I can stop trying to get sp to work on both watches. Thanks for the info here. Major bummer for sp..
afh3 said:
Ultimate Question:
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
Background:
I've had Samsung Pay on my Gear S2 watch since it has been available, and it works better than I expected it to. It is obviously limited to NFC payment terminals, as the S2 has no Magnetic Secure Transmission device.
Enter the Gear S3, now with MST payment technology.
Linked it to my phone with zero issues entered my credit-card information, and was validated on Samsung Pay in less than ten minutes on the Gear S3.
At this point, my Gear S2 and the new Gear S3 are both enabled as payment devices using the same credit-card.
Take off the S3, put on the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S2 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
WTF? I go ahead and re-add the S2, call the bank, yadda yadda, and the S2 is back with my Visa enabled on it.
Yep. Now pick up the S3, and put down the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S3 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
100% reproducible.
I did this back-and-forth with the bank about 10 times last night, before someone there transferred me to the manager who asked if I could maybe spread out my token-requests over a few days.
Meanwhile my wife's S2 with Samsung Pay and the same card account is not affected by this at all - it seems that you're only allowed one Gear S watch at a time in which to have your Samsung Pay information stored, if they share a common phone. Authorize one, and as soon as you switch to the other it will de-authorize the card on that device. The bank assures me they are not doing this on their end.
My ultimate solution at this time is to have done a light-reset on my S2, powered it down, and put it on the charger until this can get straightened out. After doing that, I could get my card re-authorized on the S3 and it has been showing active for several hours now
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
Click to expand...
Click to collapse
I have the S3 Classic and want to purchase the S3 Frontier, so I was wondering the same and this is the response I received from Samsung support...
"Thank you for contacting us. We appreciate the opportunity to assist you.
I understand from your inquiry you want to use Samsung Pay on both your watches.
Kindly know that Samsung Pay can work on multiple devices independently, it does not deactivate or impact in other way the other Gear, as long as your bank allows you to have multiple cards issued for the same account.
Whenever you register a card in Samsung Pay, the bank issues a virtual card tied to your account. And it does that for each registration of Samsung Pay, even if it is the same account.
This is perfectly fine, that is how the application works, as long as the bank allows multiple registrations for the same bank account."
Please post if you were able to get both working, because I would love to purchase the S3 Frontier also.
Good luck.
I suppose as long as the card numbers are different on each device, then it could work as they state.
I can tell you what does not work - registering the same card (number) on more than one watch, and having those watches paired to the same phone.
I have a classic and a frontier and they both used to work with Samsung pay registered to the same phone, however since the latest gear updates they no longer work, can only have one tied to the account... I have a new issue as well, the Classic will no longer backup to the cloud... I've been in touch with support and they're basically useless to this point... Samsung has their head in their asses...
Just got the Galaxy Sport and already have the Galaxy Watch, now I use the GW mostly, but wanted to use the sport for when out and about training/riding/with kids, so want the Samsun Pay working on that too, but nope, doesn't matter if you use different cards (from different banks no less), as soon as Pay is setup on one watch it wipes the Pay setup from the other. No matter what.
Right pain in the bum!
the_ape said:
Just got the Galaxy Sport and already have the Galaxy Watch, now I use the GW mostly, but wanted to use the sport for when out and about training/riding/with kids, so want the Samsun Pay working on that too, but nope, doesn't matter if you use different cards (from different banks no less), as soon as Pay is setup on one watch it wipes the Pay setup from the other. No matter what.
Right pain in the bum!
Click to expand...
Click to collapse
Any new updates on this issue?
SiNJiN76 said:
Hopeful that Samsung sends an update to allow this.
Click to expand...
Click to collapse
Good luck with that, I'm still dealing with my Classic stuck in a Terms & Conditions loop going on a year, watch will NOT backup or restore properly to my account. My Frontier works perfectly but my Classic is fubared. This seems to all be tied with 1 watch per account if you ask me... How do I suspect this? It all happened when they switched to 1 watch for Samsung Pay per account.
Related
Hello,
I set up my gear s3 classic. Set up my Samsung pay on my axon 7 everything works up until the point I tried to pay with my watch. Selected my credit card and placed my watch near the magnetic reader and it didn't work for me. Tried it at Costco, target and teavana. Confused at why this isn't working. The instructions look so simple. Could anyone tell me what I am doing wrong?
You need to put it right where the card reader is located. I have noticed that it doesn't seem to work as well as the phone's MST does but it does work. Some readers don't work where I live either, Lowe's for example, but the majority of other places works just fine.
Does it happen instantly or it takes a few seconds for the terminal to register?
Works pretty much 99.9% of the time... you get better with practice...been using it on the S7 Edge for months
It can take a few seconds, and that's probably why they have it broadcast for 30 seconds as opposed to the phone only doing it for 15. I hold mine as close to the reader as possible and wait until the card reader responds.
Just tried it again and it didn't work getting frustrated as it should be easy from the videos
Once you put it into pay mode hold it right next to the swipe slot on most swipe pads, some pads actually have a touch spot. You should feel your watch vibrating and you can usually hear a beep from the pad when it recognizes the watch. When I use my debit card loaded on Samsung Pay, I sometimes get cued to put in my PIN and other times it just processes.
I have been in my local grocery store. It worked at the Starbucks inside the store, it worked at the self checkout, it did not work at the regular lane with a cashier. So, it is not always going to work in every store, or even at every type of checkout area.
Also sometimes the Samsung Pay app recognizes that I used Samsung Pay and it shows in my history. Sometimes Samsung Pay works, but I get no indication in my history that it worked. I have had about a 90% success rate with it working at different retailers.
keep trying with no luck my watch keeps counting down but no payment is made, could i have a faulty unit? or maybe i am not doing it right. should i be moving the watch by the terminal like i am swiping it? I did pay using nfc today which was pretty cool.
still no luck. timer counts down with no payment. feel like an idiot standing there.
How many places have you attempted to pay via MST? My go-to is MST since most card readers don't have NFC where I live. I know that when I start Samsung Pay that if I put it up to my ear I can hear it making noise internally. Try starting the app and telling it to pay and put it up to your ear to see if it makes noise, if it does then I would attempt the MST payment elsewhere.
Just tried it and I just hear the watch vibrating.
Attempt it at a different place and see if it happens to work. I have about 3 places locally to where I live that it doesn't work at all, and the rest work flawlessly. Also, try holding the watch face directly towards the middle of the swiper. Some places like gas pumps don't actually look for a card at all times and require a physical card inserted for it to start looking for the magnetic data. Could be possible in your situation.
I have an S3 classic - it worked when I first bought the watch - then for some odd reason, it stopped working. I can prove this because my wife's S3 Frontier works flawlessly RIGHT AFTER my 30 seconds of standing there with my S3 classic against the card reader stripe no matter far or near, up or down, it fails and I look like a complete idiot' but her s3 frontier just works instantly.
BUT if i got to a place that supports NFC payment, i can use the Gear S3 classic instantly and it works flawlessly - just the MST doesn't work.
Ultimate Question:
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
Background:
I've had Samsung Pay on my Gear S2 watch since it has been available, and it works better than I expected it to. It is obviously limited to NFC payment terminals, as the S2 has no Magnetic Secure Transmission device.
Enter the Gear S3, now with MST payment technology.
Linked it to my phone with zero issues entered my credit-card information, and was validated on Samsung Pay in less than ten minutes on the Gear S3.
At this point, my Gear S2 and the new Gear S3 are both enabled as payment devices using the same credit-card.
Take off the S3, put on the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S2 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
WTF? I go ahead and re-add the S2, call the bank, yadda yadda, and the S2 is back with my Visa enabled on it.
Yep. Now pick up the S3, and put down the S2. Allow a few seconds for the Gear Manager to switch to the new watch. Press and hold the Samsung Pay button on the S3 and note that it is telling me that the card has been removed from my device and asks me if I'd like to add one at this time.
100% reproducible.
I did this back-and-forth with the bank about 10 times last night, before someone there transferred me to the manager who asked if I could maybe spread out my token-requests over a few days.
Meanwhile my wife's S2 with Samsung Pay and the same card account is not affected by this at all - it seems that you're only allowed one Gear S watch at a time in which to have your Samsung Pay information stored, if they share a common phone. Authorize one, and as soon as you switch to the other it will de-authorize the card on that device. The bank assures me they are not doing this on their end.
My ultimate solution at this time is to have done a light-reset on my S2, powered it down, and put it on the charger until this can get straightened out. After doing that, I could get my card re-authorized on the S3 and it has been showing active for several hours now
Can anyone here say they've used two Samsung Gear S2/3 watches with the same phone, and been able to register both of them with the same Samsung Pay account and same bank credit-card account?
Hi All,
I'm in the US and just ordered a new S3 Frontier from Amazon. Pressing the back button twice did not open Samsung Pay, (it didn't do anything at all). It is not available in the new Samsung "Wearables" android app. I have an S8 running Android 8.0 and Samsung Pay works perfectly there.
I also noticed that when I connect a BT headset to the phone, no audio comes out, or it routes the audio to my phone's speakers. I have to disconnect the phone from the watch in order to use Spotify or hear music from my headset. Shouldn't I be able to have a BT headset connected to the watch, and then the watch connected to the phone? I can't get this scenario working so that I could answer a call on the headset, if it came through for example.
Also - any cool tips for a new S3 owner are welcome. I'm keep browsing the threads
Cheers
mark3eb said:
Hi All,
I'm in the US and just ordered a new S3 Frontier from Amazon. Pressing the back button twice did not open Samsung Pay, (it didn't do anything at all). It is not available in the new Samsung "Wearables" android app. I have an S8 running Android 8.0 and Samsung Pay works perfectly there.
I also noticed that when I connect a BT headset to the phone, no audio comes out, or it routes the audio to my phone's speakers. I have to disconnect the phone from the watch in order to use Spotify or hear music from my headset. Shouldn't I be able to have a BT headset connected to the watch, and then the watch connected to the phone? I can't get this scenario working so that I could answer a call on the headset, if it came through for example.
Also - any cool tips for a new S3 owner are welcome. I'm keep browsing the threads
Cheers
Click to expand...
Click to collapse
Did you order the US version of the Gear S3 or the international version? Also, you don't press the back button twice to activate Samsung Pay, you press and hold it.
Sorry, I meant holding the back button did nothing.
My Amazon order says US version in the description. However, I just tried to register the serial on Samsung.com and it can't find it. Wonder if Amazon sent me the wrong one?
Is there another way to check? If Samsung Pay doesn't work on this one, I guess I'll have to exchange it.
mark3eb said:
Sorry, I meant holding the back button did nothing.
My Amazon order says US version in the description. However, I just tried to register the serial on Samsung.com and it can't find it. Wonder if Amazon sent me the wrong one?
Is there another way to check? If Samsung Pay doesn't work on this one, I guess I'll have to exchange it.
Click to expand...
Click to collapse
Check the model number of your Gear S3 - the US version is: SM-R760NDAAXAR. And you could exchange it if it is not the US version that you ordered - but I would suggest you just try changing the CSC code first - see the thread on that, it's easy to do.
---------- Post added at 07:20 AM ---------- Previous post was at 07:14 AM ----------
mark3eb said:
Hi All,
I'm in the US and just ordered a new S3 Frontier from Amazon. Pressing the back button twice did not open Samsung Pay, (it didn't do anything at all). It is not available in the new Samsung "Wearables" android app. I have an S8 running Android 8.0 and Samsung Pay works perfectly there.
I also noticed that when I connect a BT headset to the phone, no audio comes out, or it routes the audio to my phone's speakers. I have to disconnect the phone from the watch in order to use Spotify or hear music from my headset. Shouldn't I be able to have a BT headset connected to the watch, and then the watch connected to the phone? I can't get this scenario working so that I could answer a call on the headset, if it came through for example.
Also - any cool tips for a new S3 owner are welcome. I'm keep browsing the threads
Cheers
Click to expand...
Click to collapse
Some instructions re: connecting a Bluetooth headset: https://support.t-mobile.com/docs/DOC-33520
Thanks for the input. When I dialed *#1234# the full model number appeared as: R760XXU2CRH1. I think that's the international version right? Are there are any main differences aside from S Pay? I thought the international one has no warranties or something as well. Perhaps a lower resale value as well?
FYI - I returned it to Amazon. It was the International version. I noticed that I could not register for the warranty on Samsung.com with the serial number.
When I received the real US version, I noticed some different packaging and a different charger. I now have Samsung Pay working
mark3eb said:
FYI - I returned it to Amazon. It was the International version. I noticed that I could not register for the warranty on Samsung.com with the serial number.
When I received the real US version, I noticed some different packaging and a different charger. I now have Samsung Pay working
Click to expand...
Click to collapse
Yea, most of the international versions of phones and wearables aren't covered by warranties if purchased in the US. Somewhere in small writing Amazon usually mentions that.
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Well... I tried Google pay at another shop and it worked fine when the screen turned off... So I'm down to Samsung Pay. Honestly, I don't have to have it with GPay working right now, but it's gonna bug the heck outta me not being able to update it.
Are your phones rooted?
inningsdefeat500 said:
Are your phones rooted?
Click to expand...
Click to collapse
No. I used to root every phone I had long ago, but I stopped doing that when I started using Google Pay and Samsung Pay. These days, I don't find a lot of reason to root anyway.
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Yeah I have the same issue with Google Pay. When I move my wrist to place it close to the card reader, a clock appears on top of the screen and prevents Google Pay from doing anything.. Really annoying.
I saw other people complaining about this as well on Reddit. Don't know what the solution is for now as I have already turned off the wrist gesture in the settings.
Hello, I tell you that I was able to make NFC payments work with the BBVA GO Apk in Argentina, I comment on why I think that in Latin America, it saved Chile, Brazil and Mexico, there is no application to use NFC Pay. If anyone is interested I can show them how I did. I cannot create a new thread as I am not reaching the level. Best regards Miguel.
I tried the 4 classic on my pixel 4 xl. It won’t finish setup. Tried three times. Took it back. Best Buy guy said there’s a software bug that prevents the Galaxy watch 4 classic from working on any non s22 or s21 phone.
What’s going on?
Wearables needs all it's many permissions or it will not load/work true even on a Samsung.
There's been an issue with the Pixels and Google even locked a thread about it on their own forum with no solution found.
Talk about sticking their head in the sand...
What does this mean? Basically you need an S21/22?
I run the app on the phone. It starts the setup and sits there about 50%. Then a notipops up saying you need to connect to the watch. It’s already connected. Tapping connect or cancel or whatever does nothing. The pop up just times out and goes away. The 50% set up or whatever the % is, it just stays there. Tried 3 x then returned the watch. The BB guy said it’s a software issue that no phones will work now with the current software unless the phone is the S21/22.
I don’t get it.
buggs1a said:
What does this mean? Basically you need an S21/22?
I run the app on the phone. It starts the setup and sits there about 50%. Then a notipops up saying you need to connect to the watch. It’s already connected. Tapping connect or cancel or whatever does nothing. The pop up just times out and goes away. The 50% set up or whatever the % is, it just stays there. Tried 3 x then returned the watch. The BB guy said it’s a software issue that no phones will work now with the current software unless the phone is the S21/22.
I don’t get it.
Click to expand...
Click to collapse
I don't know. Invariably Samsung will eventually fix the issues just don't hold your breath waiting for it.
As with most of the Samsung accessories it's optimized and integrated for the Samsung ecosystem. Even some Samsung users are having issues apparently.
The other side of this is sometimes you need to play with Samsung apps a bit. My Buds+ will run at first on the latest version of Wearables but eventually the audio screws up. Solution, install the older version which works, has a better UI and then Firewall block the the update UID for it so it doesn't auto update and self destruct
I make adjustments as needed... got a 2nd pair of Buds+ order, which shows you how rattled I am.
Wow lol. It’s been months and they haven’t fixed it. Insane. Could be on purpose too. Wanting to sell Galaxy phones. Hmm.
buggs1a said:
Wow lol. It’s been months and they haven’t fixed it. Insane. Could be on purpose too. Wanting to sell Galaxy phones. Hmm.
Click to expand...
Click to collapse
Well that could be Best Buys intent.
You give Samsung too much credit; this likely wasn't planned... which is why it happened
The original Buds were a mess when first released. It took a year worth of sequential firmware updates to dial them in.
There been reported problems with newer models as well I believe I saw as I was reading. Anymore I'll never preorder or be the first to buy their products or "test" their updates. Instead I buy when known to be good. It's always been hit or miss with Samsung to a greater or lesser degree. They are capable of producing exceptional products and bone rattling duds.
Best Buy intent? I was saying Samsung maybe did this on purpose.
Anyway.
buggs1a said:
Best Buy intent? I was saying Samsung maybe did this on purpose.
Anyway.
Click to expand...
Click to collapse
I have zero faith in Best Buy. They are a horror to deal with... they tried my patience for the last time 2 years ago.
buggs1a said:
I tried the 4 classic on my pixel 4 xl. It won’t finish setup. Tried three times. Took it back. Best Buy guy said there’s a software bug that prevents the Galaxy watch 4 classic from working on any non s22 or s21 phone.
What’s going on?
Click to expand...
Click to collapse
there is a software issue or something make watch 4 classic dont work on non samsung or even older samsung like s9 s10 that make you have trouble and think about upgrading the phone which personally im sure its on purpose by samsung you may be able to connect the phone doing factory reset but me and alot of people cant connect google account to the watch afterward which there is no fix till now ofc hoping the new upcoming wear os 3.5 and one ui 4.5 update will fix it but if not thats just it personally i was so intrested in s22 ultra and was thinking to buy it before this happened but if the update wont fix it i will never pay samsung in my life in any sort of way
omid_nr said:
there is a software issue or something make watch 4 classic dont work on non samsung or even older samsung like s9 s10 that make you have trouble and think about upgrading the phone which personally im sure its on purpose by samsung you may be able to connect the phone doing factory reset but me and alot of people cant connect google account to the watch afterward which there is no fix till now ofc hoping the new upcoming wear os 3.5 and one ui 4.5 update will fix it but if not thats just it personally i was so intrested in s22 ultra and was thinking to buy it before this happened but if the update wont fix it i will never pay samsung in my life in any sort of way
Click to expand...
Click to collapse
Factory reset is a waste of time; try a network reset instead!
Even with the Buds+ the getting them working takes some effort sometimes. The spen can be the same way.
If the Wearables app is screwed up, nothing may work. An older version may work but it requires some effort to load and keep from updating which would break it again.
Deliberate? No Samsung doesn't need to intentionally try to screw things up, it comes naturally Sammy's been dropping balls a lot lately.
I`ve been using my watch 4 classic with my 4XL without any issues since May before upgrading to my P6P. And after upgrading to my P6P I didn`t run into any issues. What I`ve experienced when setting up my watch 4 classic for the first time was that the samsung wearable app was switching screens after providing credentials for my g account and therefore was hiding the permissions quote and the wearable app was waiting for the authorisation to use the g account. Those sammy blue dots were circling around for many minutes. Happened to me twice. Using the back ´gesture let me grant the permissions needed and t he setup process just went through smoothly.
bluetigger68 said:
I`ve been using my watch 4 classic with my 4XL without any issues since May before upgrading to my P6P. And after upgrading to my P6P I didn`t run into any issues. What I`ve experienced when setting up my watch 4 classic for the first time was that the samsung wearable app was switching screens after providing credentials for my g account and therefore was hiding the permissions quote and the wearable app was waiting for the authorisation to use the g account. Those sammy blue dots were circling around for many minutes. Happened to me twice. Using the back ´gesture let me grant the permissions needed and t he setup process just went through smoothly.
Click to expand...
Click to collapse
The infamous circling blue dots make me cringed every time I see them now. Like some alien from Star Trek eyeballing you
Wearables will puke all over unless all permissions* are granted. Something I really hate about Wearables. Reminds me of the bixby spyware. Lol, don't worry Samsung servers are secure... until the next hack
*check that all permissions have been checked manually as it doesn't always happen during installation for whatever reasons.
Thanks all.
I had the S22+. No issue. But returned the watch and phone because the phone screen shuts off if I don’t touch it for a bit when playing games. Some games I play auto battle and takes awhile so no need to touch. So I returned them both yesterday.
buggs1a said:
Thanks all.
I had the S22+. No issue. But returned the watch and phone because the phone screen shuts off if I don’t touch it for a bit when playing games. Some games I play auto battle and takes awhile so no need to touch. So I returned them both yesterday.
Click to expand...
Click to collapse
Only 8gb of ram, max 256gb internal storage and no expandable storage, rounded display corners... yeah I'm not feeling it.
Good call.