
New Member
•
11 Messages
AT&T NumberSync stopped working on my Galaxy Watch 4
I've been using my Galaxy Watch 4 with NumberSync enabled from my primary phone. It was working well until 2 days back, now I'm trying to make it work, but it keeps throwing an error. Logged into my AT&T account and confirmed my watch is not listed under Synced wearables. When I tried to reconfigure the NumberSync, it prompts for the code from my watch, and my watch AT&T NumberSync app throws an error with code PD-SD-N/A. No luck with support chats/calls. Anyone have similar issues recently? I did get a text confirmation saying that my NumberSync stopped working 2 days back, and that's when I realized it doesn't work. So, when AT&T have these services traced in the backend, it'd be good at least if they also stop charging us for the watch line for the time when NumberSync doesn't work.
s_thilkumar
New Member
•
11 Messages
2 years ago
@Lukeaj that's exactly the first thing the support in ATT says, it's something wrong with Samsung watch, contact Samsung support. I walked into a store where I know the manager, who activated my watch last time in a jiff. He tried his best and got dead end with the AT&T NumberSync app. He started looking into the forum, then I told him that it's a known issue. He agreed its a back end problem. That's the basic etiquette ATT should teach their support staff, being transparent. @ATTHelp why do we've to keep troubleshooting when the problem is in the backend? Just tell us that you're all working to resolve the issue and keep us posted. Seriously ATT should stop charging us for the watch line until this problem resolves.
0
ATTHelp
Community Support
•
225.4K Messages
2 years ago
Hey, lamontedwards! We see you're experiencing difficulties using NumberSync like other customers. We're here to help!
Let start off with some basic troubleshooting steps. You may have already tried them and that is fine, just let us know if they helped get you a step closer to resolving this. Please let us know which error codes you're receiving if there are any. Now, let's run your device through a troubleshooting diagnostics to help us discover why this error is occurring. There are great gems that you'll find helpful. Just pull up our AT&T Wireless support website and select Get suggestions. Then locate Services>Device pairing (NumberSync).
Also, remove NumberSync and set it back up: (If you can, uninstall the Galaxy Wearable app and download it again.)
Before you begin, make sure:
Set up NumberSync from the Galaxy Wear app:
Don't forget to check out additional tips provided in our Forums article labeled NumberSync Not Working - Fixes from the Community. Come back and visit!
Jonye, AT&T Community Specialist
0
0
ATTHelp
Community Support
•
225.4K Messages
2 years ago
Thank you for trying the troubleshooting @hollowel.
This is currently a known issue that our techs are working to resolve expeditiously. You can follow this thread for the latest updates regarding this situation. Thank you for reaching out to our AT&T Community.
Darais, AT&T Community Specialist
0
ATTHelp
Community Support
•
225.4K Messages
2 years ago
We're sorry for the inconvenience @DapperAdam.
This is currently a known issue that our techs are working to resolve expeditiously. You can follow this thread for the latest updates regarding this situation. Thank you for reaching out to our AT&T Community.
Darais, AT&T Community Specialist
0
0
s_thilkumar
New Member
•
11 Messages
2 years ago
Seems like the work is in progress. Tried the numbersync now, with wifi disconnected, using mobile network, opened the AT&T NumberSync, which opened up showing the connected watch, which didn't happen before. It always errored out. But, when selecting the watch, it shows the agreement, selected Agree, then it prompts for the code from watch. The watch is now erroring out with the same code as before SD-SDK-N/A. Hope this should gets resolved soon.
0
0
s_thilkumar
New Member
•
11 Messages
2 years ago
It just worked now. Completed the process, and watch is successfully syncd now. I did the whole process by disabling wifi on my phone, and using the mobile data, just fyi. Finally... 😂
0
0
Lukeaj
New Member
•
15 Messages
2 years ago
Congrats. Maybe it is getting better? My phone is asking for a code now. That is an improvement, but my watch still errors out.
0
0
Atlutd17
New Member
•
1 Message
2 years ago
I conquer with so many here. I called 3 days ago and got a case number with an escalation and a promise someone would contact me within 12-24 hours. Has that happened? Heck No! We should be given a credit for the entire $10. This is absolutley unacceptable to be told you would be contacted in 12-24 hours and now it is 3 days later. And I found out through the forum it was a backend problem while I was on the phone with tech for 30 minutes plus. Lack of transparency is not acceptable. I am outside my return window (October purchase). My cell bill, only cell is $400 a month and I have been with ATT since Cingular was bought out. I am sure Verizon would LOVE my business. Over $70k paid to ATT. Seriously fix it, credit, or cancel my service. And, quit telling people it's their watch or their fault for turning something off.
(edited)
0
0
earldav
Contributor
•
2 Messages
2 years ago
I resolved the problem myself because much like in the past when NumberSync issues were raised, the product owner(s) on the AT&T and/or Samsung side frequently forget to include the Phone APN in the firmware updates, so this knocks out the connectivity needed. For a Samsung Galaxy Watch 4, go to Settings > Connections > Mobile Networks > Access Point Names > Add. If you only see the APN for ATT Nxtgenphone, then add the Phone APN. It's only 2 fields, but you can see the complete profile on this BYOD settings page: https://www.att.com/support/article/wireless/KM1062162/ Also, because I wasn't sure if WiFi being on would interfere or not, I went ahead and turned it off and then also made sure Mobile Networks was Always On just until I got NumberSync successfully hooked back up. Hope this helps everybody else!
0
tracy8583
New Member
•
4 Messages
2 years ago
Was just able to use NumberSync and no error message! Looks like it has been fixed!
0