Galaxy Watch LTE duplicate messages

Is it possible to pursue a solution with the DIGITS team as well? While connected to LTE, I'm getting messages on both my phone and watch (a good thing, as they are not being delayed in delivery) but messages don't synchronize as being read across devices. I'm thinking this involves DIGITS as the DIGITS app on an iPad and Win10 computer shows the same behavior.

We look forward to a solution to this problem!

I'll echo this. I have the watch and I have the same problem. Past the 14 days, what options are we given?

Great call out, @magenta6238774​! The Samsung team is also already working with the DIGITS team to determine if that's the underlying issue. Unfortunately, I do not have any updates at this time. They're currently going back and forth trying to find a permanent solution that also doesn't drain the Watch battery.

For those asking if there are any options to return the device outside of the buyer's remorse period - currently, we do not have any update to extend the buyer's remorse period for the Galaxy Watch. If that changes, I'll most definitely update this thread. I have passed the request along but cannot make any promises that the return period will be changed.

It's either a defect with the watch software or defect with T Mobile digits.  Either way we should be credited since it is not working as designed.  It's been two months. 

Just picked up a 46 and a 42 and immediately noticed the same issue. Additionally, group messages sometimes come in as separate messages from each sender. In some cases appearing in both the group thread and separately, other times in only one or the other. I'm assuming that happened when the watch switched between Bluetooth/LTE. An under 2 day battery life would be a dealbreaker for me too. Any update on this? I now have 6 days left to decide!

Hello, if there was an option to mark all missed incoming messages as read when the watch connects to LTE, that would be a great (but probably not final) step towards a solution. It seems like something that could be implemented in DIGITS or the watch messages app.

This problem has become more annoying as we enter the holiday season, as folks are comparing functionality between watches and carriers in their gift decisions. I'd love to be able to tell others that this increasingly-heard-about problem is solved for the LTE Galaxy watch on T-mobile.

@dupsla​, I'm so incredibly happy to read your update! Thank you for encouraging others to call in to get this resolved as we have zero account access on our end to make any changes. I'm very curious what they changed to cause it to work when we've had multiple teams working on this.

Hello everyone! I'm happy to report an additional example of progress. Following dupsla's urging, I called T-mobile support and eventually got connected to the DIGITS team. We did the following:

• Verify that my watch software was up to date. This was R815USQU1BRJ3, the release from mid/late October. I should note that after being on bluetooth connection with the phone again (yay!, as I had been doing LTE-only), the watch did update yesterday to R815USQU1BRJ6.
• Unregister then re-register the watch with DIGITS. This is more than de-associating and then reassociating the watch with the phone number in DIGITS.

With those changes, I can go back to bluetooth connection between phone and watch with messages synchronizing, while not getting duplicates when switching to LTE. So far so good for two days, which did include a watch software update. I will indeed follow up if things stop working.

I don't think this is ready to be considered solved, as the steps taken for my watch are similar but different enough from what it sounds like worked for dupsla. Also, it took a good deal of discussion to get from the general support to the DIGITS team; this might of course vary between callers and who is on both ends, but it would be good to make this issue more findable to the support teams. Until a clear, reproducible path to making this work is demonstrated, I would suggest this not be considered solved.

I will try this and give them a call.  When I first noticed this issue that was my first response and the DIGITS team told me that it was set up correctly and was Samsung's fault.  I will hold out hope that their outlook has changed and that they can follow your steps.

I will give them a call tonight and let you all know if it works or not. 

Hey Guys

Even though I'm not a t-mobile user I was experiencing the same issue as everyone else with receiving duplicate txt messages from my watch that I dismissed hours ago whenever my watch would switch to mobile data. And I discovered  (at least on AT&T) that this has to do with the text app you're using and Numbersync (AT&T's equivalent service for DIGITS).

I use the textra app on my phone instead of the built-in messages app. However, I decided to disable textra and then use messages. When I started digging through the settings I noticed that the messages app on my AT&T branded note 8 has a service for AT&T message sync (allows you to check and send text messages online with your AT&T phone number and must be enabled to use numbersync)

So I tested by

1) Sending myself a text message from another number

2) Dismissing the text on my watch while still connected to bluetooth

3) Waiting for 5 minutes and then disconnecting bluetooth

4) Waiting for 10 minutes and confirmed my watch no longer received a duplicate notification

I went back to my phone switched my default message app back to textra and executed the same steps above and within 5 mins I received duplicate messages again. When I reached out to AT&T support they told me that their message sync service only works with the default texting app on my phone and not 3rd party texting apps. This obviously is not the answer I wanted to here since textra is far better than the samsung messages app so I kept trying things and found a workaround that works for me.

I leave textra as my default app but I went into the samsung wearables app and blocked notifications from the default message app. I then ran the test again and no duplicate messages. I only get the notification from textra. I also tested to make sure I would still receive new txt messages by connecting to mobile data only and then sending myself a message and sure enough I only receive notifications from textra now.

Hope this helps

Note: I'm on the latest watch firmware released on 11/26 (R815USQU1BRJ6). I force checked for the update in the samsung wearables app.