Database Info

Wallet - Won't actually pay.

I've got Google Wallet installed, and cards activated, but I can't seem to make it actually pay...
A couple of trips to the local McDonalds - waking up my phone and waving it over the red sensor part of their card reader does nothing... unlocking or having wallet open at the time doesn't help either.
What am I doing wrong?
Sent from my SCH-I535 using xda app-developers app

Does your phone beep to let you know the nfc receiver has picked up an rfid signal?
Sent from my SCH-I535 using xda app-developers app

Did you have the NFC box check under settings more settings. It allows information to be sent between NFC device which is necessary.
Sent from my SPH-L710 using Tapatalk 2

No response at all from my phone or the terminal. Might as well have been waving my hand over it.
Does the phone need a physical "bump" instead of a wave to do its thing? I would expect this to work much the same as my proximity company ID badge.
NFC is turned on. SBeam is off (does that matter?)
Sent from my SCH-I535 using xda app-developers app

I always touch my phone back to the spot on the card reader. Do you have a case on your phone? There is only like a half inch of play before the phone is too far away. Try it again by tapping the phone.
Sent from my SCH-I535 using xda app-developers app

yeah. i get embarrass too if wallet doesnt work. how embarrassing!
but they have nfc soda vending machines in Atlantis hotel casino in reno! i tried it there with wallet on my nexus without the embarrassment and it works!
https://www.youtube.com/watch?v=OEwHMk4qFTs

"waving it over the red sensor part"
You dont know what your doing if you "waved" it. You must hold it up to the scanner for it to recognize. Also, if you have a case, it takes longer to pick up because the case adds thickness which reduces the bandwidth NFC can utilize due to a weaker signal.
Experiences: 8 successful payments. 1 failed (Walgreens isnt there yet)

There is no red sensor where I used it. 7-11 and cumbys. It's the grey part above the debit/credit card scanner that has the nfc symbol....Walgreen's failed for me also the manager said they just recently installed.
Sent from my SCH-I535 using xda premium

I've had the same exact problem as the OP. I tried mine at a local gas station where a friend works so I didn't look like a complete dunderhead and I tried it on 6 separate occasions and tried installing it several different times/ways and could never get it to work. They have the EZ Pay NFC reader above the credit card machine and every time I tried it it would not work no matter if I tapped it, took it out of the TPU case, got the cashier to hit credit, opened and unlocked the app. Nothing. It just simply refused to work. Maybe I'm just an idiot though, I just assume the EZ Pay NFC card reader would read my NFC chip in my phone. Maybe it won't. I am just at a loss. I just reset the app and went to my backup nandroid and left it along after all the attempts because I was so embarrassed.

i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol

Try without a case.I had no comm using NFC due to my case blocking the signal somehow. took it off and now it works every time.
Sent from my galaxy nexus using xda app-developers app

digitalsynner85 said:
i've only used it once thus far, i was worried it wouldn't work right since i never used NFC payments before so i had no idea how to do it......it took about 15 secs for GW to open up from a locked status on my phone then about another 20 secs for it to recognize the nfc scanner and to process a payment to mcdonalds, not bad, i had my card out in preparation though lol
Click to expand...
Click to collapse
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....

shangrila500 said:
I had thought that maybe it would take a bit for GW to notice the NFC reader but i left it there for a full 5 minutes at one point, I was running my mouth, and it never pulled up GW nor recognized the NFC reader. Also this was with the phone off. Another thing I found funny about it was that it the app would not pull up as Ready to Use until I had let it set up my Play Store credit card they have on file. I dont know if the OP is having the same exact problem as I am but it sounds exactly the same. I have also tested my NFC with my girlfriends GS3 to see if maybe I recieved a bad battery or maybe my phone was somehow faulty but it pulled the fileshare using S-Beam off without a hitch so.....
Click to expand...
Click to collapse
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.

digitalsynner85 said:
My phone wasn't off, just locked. If the phone's off then the nfc reader is supposed to be off too. I found that just quickly opening GW right before touching it to the reader makes it happen almost instantly. At least for me already.
Beamed via NFC through the local store to the internet from my SGS3.
Click to expand...
Click to collapse
Sorry about the misunderstanding. When I said off o meant my screen was locked. My phone just edited that part out. I have tried it like you did also, by opening the app right before touching it to the reader. Still doesn't work. It may just be an issue with my phone. No matter how I try to use it to pay it won't work...

i've had no issues having my nfc chip being scanned but i have yet to complete a purchase successfully. i'm going to chalk it up to the terminals not being configured correctly... my other nfc functions work fine.

Some dont work for some odd reasons because the storemanager/higher ups dont know what it is so they might have disabled it for what ever reason.
I know Walgreens has scanners but does not work JUST yet, they are partners of the whole NFC movement thing.
Stores that have worked for me are.
Chevron, 7-11 ( had to tilt there scanner up), McDonalds, BJ's (like walmart), Vending Machines.
Doesnt work: Walgreens, Some Random gas station out of town
I find that if you see a LED blinking or on thats connected to the scanner, the scanner works, but if it doesnt scan right away its the case's fault or not placing it.
Source: I like to consider myself a Wallet expert haha, my thread is over in Developer Section to get wallet as well. Also all my purchases have been used using a Otterbox Defender, and take about 3-5 seconds to complete the transaction.

mine failed as well at a jack in the box drive thru. looked like a fool. haha
i took my case off, opened the app, clicked the lock in the corner, entered my pin, and held it up against the reader for a good few seconds but nothing happened. nfc was on. their reader had like 4 spots for lights and the first one was on with a solid green light so not sure, hopefully it was their reader. will try again at a 7-11 if I can get over the embarassment

LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem

NeoMagus said:
LOL at you guys thinking your case is giving you a problem, most likely you are not putting the battery (where the NFC is) up to the correct part of the terminal (your phone should chime or make a noise when its recognized, just like when Android Beam comes up),
or just plain out the terminal doesn't work (not your phone), a mcdonalds and wendys in my area they have them but nothing happens and one mcd across town works perfectly fine. Just depends on the vendor.
I have the Otterbox Defender on both my S3 and Galaxy Nexus, and haven't had a problem or delay yet as long as their terminal is working correctly, and they are pretty thick cases. As long as you line it up right and they work shouldn't be a problem
Click to expand...
Click to collapse
Well said and 100% accurate. I bet the problems people are facing are user error or the terminal just doesnt work.

I've used mine on about three different occasions and it worked perfectly. But what's funny, I was in a local vzw store buying something. They have what looks like the press pass set up, tried to use it and it wouldn't go through. The girl checking me out was surprised and had no idea that you could even do that. Anyway, my point is that even though the card reader looks like it will work, if they don't have it set up it won't. Vzw's looks just like the ones at McDonald's.

Gear S2 Reactivation Lock

I was walking around best buy and they didn't have any new Gear S2, but they did have an open box one in mint condition, and it was $40 off. I took it home and I'm trying to pair to my S6. The issue I am having is that it says the reactivation lock doesn't match my samsung account. Is there anyway around this or am I screwed and have to head back to best buy tomorrow?
Thanks Guys!
Error message:
"The Samsung account you are signed in to does not match the Samsung account that was used to turn on Reactivation lock. Tap SETTINGS to sign out, then sign in to the correct account."

I have the exact same story and problem. Just got off the phone with Samsung and unless I can get the previous owners samsung account info to sign in and turn off the activation lock it's a paper weight. Heading back to best buy tomorrow

i had the same issue, went back to bestbuy and exchanged it for another one, tested it before i paid for it to make sure the other owner wasnt another dumbass

Xspidman said:
i had the same issue, went back to bestbuy and exchanged it for another one, tested it before i paid for it to make sure the other owner wasnt another dumbass
Click to expand...
Click to collapse
Well at least we know the reactivation lock works. I guess that will discourage people from trying to steal them. Best Buy should know better than to try and sell them in that state. But then again they are brand new so there's a learning curve for everyone.

yeah but it doesnt make sense that i showed samsung my receipt and everything and they had no way to remove it

If the person the returns the device does not log out of their Samsung account or NOT check the 'reactivation lock' then it will never be able to connect to a device again.

Here it is.

just left a Bestbuy with two gear S2's. One had the reactivation lock, other didn't.
Employee's had no clue the watch could lock itself down.

CTBob said:
Well at least we know the reactivation lock works. I guess that will discourage people from trying to steal them. Best Buy should know better than to try and sell them in that state. But then again they are brand new so there's a learning curve for everyone.
Click to expand...
Click to collapse
crazy talk said:
just left a Bestbuy with two gear S2's. One had the reactivation lock, other didn't.
Employee's had no clue the watch could lock itself down.
Click to expand...
Click to collapse
yup i lucked out on the second one, it was the only one left

If someone gets the watch from a retailer like Amazon, will this problem likely occur?

crea78 said:
If someone gets the watch from a retailer like Amazon, will this problem likely occur?
Click to expand...
Click to collapse
you'll never have this problem with new units. But there is a very strong chance that any used S2 will have this problem since it's enabled by default when you set the watch up.
I don't think anyone knows if Amazon has procedures in place to actually verify the used watches coming back to them have this lock turned on or not.

crazy talk said:
you'll never have this problem with new units. But there is a very strong chance that any used S2 will have this problem since it's enabled by default when you set the watch up.
I don't think anyone knows if Amazon has procedures in place to actually verify the used watches coming back to them have this lock turned on or not.
Click to expand...
Click to collapse
I don't think mine was enabled by default. I just skipped this step.

Same thing happened to me. Went back to best buy at another location close to home and they said theres nothing they can do so I have to go BACK to the original store 45 min away.... pain in the ass...

TheANSwer118 said:
Same thing happened to me. Went back to best buy at another location close to home and they said theres nothing they can do so I have to go BACK to the original store 45 min away.... pain in the ass...
Click to expand...
Click to collapse
Picked up an open box S2 at the local Best Buy. The Samsung specialist guys said they were aware of the Reactivation Lock issue and that they had instructions now on how to disable it. The head Samsung Rep said he checked the 2 open box units that he had seen since last Friday and that neither had the reactivation lock enabled. They let me pair the watch at their display area, and it worked fine.
So if you go for an open box unit pair it up in the store in case you need to work around the reactivation lock.

crazy talk said:
you'll never have this problem with new units. But there is a very strong chance that any used S2 will have this problem since it's enabled by default when you set the watch up.
I don't think anyone knows if Amazon has procedures in place to actually verify the used watches coming back to them have this lock turned on or not.
Click to expand...
Click to collapse
I can verify that Amazon does not have a procedure in place to deal with the Activation Lock issue. just got my watch today and now I am going to have to deal with Amazon on either sending the watch back or getting it deactivated.
Disappointed,
Fred

Same issue with Amazon used program, I can't activate the device.

So how do you deactivate the lock if returning

obsydian said:
So how do you deactivate the lock if returning
Click to expand...
Click to collapse
I think there are two ways
Log on to your Samsung account (not sure how) and deactivate it from there.
Reset the watch and repair it with your phone and I think there is a choice to deactivate the lock from during that process.
Hope that helps,
Fred

Found it, oddly you goto Find my device in Gear Manager, then the next menu gives you the option to turn it on or off.
Recall i had this problem when i sold my S5 a whileback, had to go and log in, then log out of the account.

Even Amazon had no idea about this because its exactly what happened to me. I let their customer service team and fulfillment team know that they need to look for this because there is nothing more disappointing than getting your new device and having to send it right back because the previous owner was an idiot.

How to pay with gear S3 MST?

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.

Question Google Pay locks the entire watch

Just received GWatch 4. Installed Gpay, and it requires a lock code. I get that, but, it locks the entire watch. When I used Samsung Pay, it only locked the app. Why doesn't Gpay have similar behavior?

Similar issue for me, except I am using Samsung Pay and it locks the whole watch. On my previous Galaxy Watch it worked fine and I only had to unlock to make a payment. Does anyone know why or how to prevent it?

EdzGNote7 said:
Just received GWatch 4. Installed Gpay, and it requires a lock code. I get that, but, it locks the entire watch. When I used Samsung Pay, it only locked the app. Why doesn't Gpay have similar behavior?
Click to expand...
Click to collapse
Yes, OK, but the pin is only required if you remove the watch from your wrist. As long as you wear it it will not request a pin, at least not on my watch.

This is one of the differences between Tizen and Wear. I have a Ticwatch Pro 3 GPS and this is the default security for Wear OS. If you want GPay you have to have a lock in place and on Wear it's to lock the device when not on your wrist. I also have a Galaxy Watch 3, and as we all know that to use Samsung Pay only the app needs to be locked by PIN. Although this watch looks like Samsung there are still some basic things that are absolutely Wear OS...

thanito said:
Yes, OK, but the pin is only required if you remove the watch from your wrist. As long as you wear it it will not request a pin, at least not on my watch.
Click to expand...
Click to collapse
Nope mine sometimes locks even when it's still on my wrist. Not all the time, but maybe about 30-40% of times I try to look at it.

stuartbruce said:
Nope mine sometimes locks even when it's still on my wrist. Not all the time, but maybe about 30-40% of times I try to look at it.
Click to expand...
Click to collapse
Strange, maybe the watch thinks that you took it off? I have GPay installed and only have to unlock the watch when I take it off.

stuartbruce said:
Nope mine sometimes locks even when it's still on my wrist. Not all the time, but maybe about 30-40% of times I try to look at it.
Click to expand...
Click to collapse
Is the watch snug on your wrist? If you wear it loose the watch might think you removed at some point.

Mine asks for PIN every time I look at my watch.

if im not mistaken, the reason the entire watch locks is because if the watch is awake, it will automatically use gpay if its set to default without actually having to open gpay, just like your phone

Coming from GW3, only needed pin for Sampay!
Now GW4 classic asks for pin every time I do anything but look at the time!!
If this watch is so ****ing sophisticated, with all these sensors, why the **** do I have to strangle my wrist for it to know I'm wearing it?! And even when I tighten it, it's hit or miss!

Drukan said:
Coming from GW3, only needed pin for Sampay!
Now GW4 classic asks for pin every time I do anything but look at the time!!
If this watch is so ****ing sophisticated, with all these sensors, why the **** do I have to strangle my wrist for it to know I'm wearing it?! And even when I tighten it, it's hit or miss!
Click to expand...
Click to collapse
THIS is exactly what's happening to me!!!! And someone on Twitter says not the case?
https://twitter.com/i/web/status/1438398410369949698

I had this issue of Gpay locking my watch every time the screen turns off, but it only happened once and a single reboot solved it for me.

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.

Drukan said:
Coming from GW3, only needed pin for Sampay!
Now GW4 classic asks for pin every time I do anything but look at the time!!
If this watch is so ****ing sophisticated, with all these sensors, why the **** do I have to strangle my wrist for it to know I'm wearing it?! And even when I tighten it, it's hit or miss!
Click to expand...
Click to collapse
Same issue with Spay. Would be great if someone can find a way to turn off that screenlock with NFC payment apps

BabeShaq said:
I had this issue of Gpay locking my watch every time the screen turns off, but it only happened once and a single reboot solved it for me.
Click to expand...
Click to collapse
resolved means- don't you need to unlock screen when you are not wearing it???

EdzGNote7 said:
Just received GWatch 4. Installed Gpay, and it requires a lock code. I get that, but, it locks the entire watch. When I used Samsung Pay, it only locked the app. Why doesn't Gpay have similar behavior?
Click to expand...
Click to collapse
GPay did the same thing for me. I had to put the created pin in every single time I tried to do anything on my watch. Didn't matter if it was on my wrist or not. I just went into the watch settings a removed the pin. Now it doesn't ask for it

V3N0M_90 said:
GPay did the same thing for me. I had to put the created pin in every single time I tried to do anything on my watch. Didn't matter if it was on my wrist or not. I just went into the watch settings a removed the pin. Now it doesn't ask for it
Click to expand...
Click to collapse
But if you removed the PIN, then you must have lost Gpay right?

Yeah this is doing my head in.. Got the watch a couple days ago. Want to use GPay but you need a pin. OK cool.... but its asking for that pin EVERY time i want to do something on my watch.... its infuriating.
Anyone got a solution?

only when i take and put it back do i need a pin...
go to settings /security
photo shows what i have

Just wonderful. I've used SPay for years on many different phones. Now that MST is gone using NFC on a watch factored into me buying a Watch 4. I installed SPay on the watch and needed to put in the PIN every time I left the main watch screen. I was hoping GPay was different, but apparently not. I am not going to be forever punching in a PIN. Who has time for that? Why even have such an unusable app installed? Put the PIN in before using the app ONLY! Just like on a phone. Samsung this is a lose for you. Technology is marching backwards by being less usable.

Question Galaxy watch 4 classic not work on non Samsung

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.