Forum Discussion
Galaxy Watch LTE duplicate messages
As the title says I am getting duplicate messages to my galaxy watch. When im connected to bluetooth everything works fine, texts sync properly when read on one device. However whenever i disconnect from my phone and switch to LTE i get every text ever all pver again. Literally 1000's. You would think the solution would be to leave lte on all the time? Wrong. When i leave lte on all the time then my watch and phone dont sync! If i read the text on my watch it wont update ththe phone anand vice versa. The point of the watch is to be able for the phone and watch to sync AND to leave your phone behind. Ive read dozens of users experienceing the same problem whats the fix tmoble? Ps this isnt an issue with the apple watch lte
@dupsla and @magenta6238774 , thank you both! I sent a PM your way which should be in your inbox. I also agree about the latest update which is something I'll include in feedback because I do think @magenta6898941 has a great point.
- dupslaTransmission Trainee
Hi everyone, I just got off the phone with T-mo for another issue so I had them transfer me to the digits dept. They are aware of the problem. He said it is on their back end and have had success with a fix with others. He took my numbers and said to give it 48 hours and do a restart of both devices. Also he said you have to call in so they can expedite a fix. PLEASE call them and let them know your issue! They need your phone number and digits number for the fix. I guess I'll find out Thursday if it was fixed!
- magenta6231016Roaming Rookie
Hey guys dont waste your time with this
Spoke with tmoble and unfortunately this is how the samsung galaxy watch was "designed" for the lte model. I put it in quotes because it wasnt designed that way, they rigged it to work lol. This issue doesnt exist with the apple watch. The apple watch works and synce correctly on lte and its because of imessage. So the issue isnt 100% tmobles fault but come on tmoble your killing it right now, dont sell subpar equipment just to get it to consumers. Im reading literally 100's of people all across the internet (reddit, here, other forums, etc) return this device. Ive made more peofiles across more websites over the last 24 hours to discuss this issue then i have all year. To summerize the watch is broken on lte. Great watch, get the bluetooth model. Or switch to apple unfortunately if you want a working lte watch. Please do not mark this as "solved" you saying the watch is working as intended doesnt mean that it is.
- bruno8675Transmission Trainee
TheWolfAmongUs wrote:
I’m having the same problem with my 3! Just switched from iphone and i never had these issues with the apple watch!
Yes. I have Apple watch as well and no issue like this ever. However, I’m not blaming Samsung as this appears to be a T-Mobile issue. I’m asking T-Mobile to assign a higher level engineer to my ticket. Clearly it’s not a problem with my phone, SIM, wifi, etc.
Tired of all the dumb troubleshooting steps.
- dupslaTransmission Trainee
Under connections:
Bluetooth on
Mobile networks always on
Mobile data on
Wifi auto
Wifi networks connected using networks
I disabled the report diagnostic also.
On the phone in the app under watch connection all 3 of the settings are enabled, remote connection, connection notification and wifi sync.
Restart after all settings are changed.
I'm going to watch it a few days/week to see if the battery lasts. It was at 100% at 9am and it's at 62% now at 3:30. It did update so I'll give it a few days to settle in with new watch syndrome.
I hope this helps and I'm hoping it's not a battery killer!
I
- magenta6596678Roaming Rookie
that's what i'm afraid of having to do, is toggle the "always on" feature on the mobile data as that DOES seem to prevent the duplicate messages. The problem i have with that is that with it set to "auto" i get 3 days and 2 nights of battery before i have to charge my watch. With mobile data always on I am using about 6% of battery per hour meaning that my watch won't even last a full day which is not acceptable for me considering the device was advertised to have a 5 day battery (i have the 46mm). I don't expect actually getting that long but I don't feel that we should have to sacrifice the battery life completely just to fix a bug.
It would be great if there was any more information on the issue from T-mobile's perspective, because TBH I am getting pointed both ways. Samsung has indicated to me that it is an issue with how my DIGITS is set up that is causing the duplication while T-Mobile is indicating that it's a software issue on the watch itself.
Would my DIGITS not being set up properly cause this?
- dupslaTransmission Trainee
I honestly don't think it's on the digits side. I think its something in the software. Yesterday was the first day with the replaced watch and the new settings. I got 14.5 hours and it had 15% when I went to bed. Today I'm hitting about 5% per hour so far. So far everything is working correctly. I checked the battery usage and it is showing watch faces using the most (15%) which I'm using a stock dark face. Also notifications at 11%. I'm going to keep an eye over it the next week and see if it improves. I figured the first day or so would be a little less because of updates. Also the advertised battery life being on the longer side was for the BT version and size 42mm vs 46mm. Even the best of the best of smart watches have a 2 day battery life. If I get that or close I'll be happy!
- magenta6596678Roaming Rookie
I was asking about DIGITS in reference to the original issue being discussed on this thread which pertains to duplicate text messages being received when on LTE, not battery life. I am hoping that someone with T-Mobile can clarify if an issue with how they set up DIGITS on my watch could be what is causing that to happen as that is what Samsung is implying.
- magenta6238774Transmission Trainee
Hi dupsla, many thanks for sharing your watch settings! Since re-toggling the settings, I'm getting better battery life as well; after 12 hours I was at 25%.
To T-Mobile tech:
I'm not sure where DIGITS ends and software begins, but I think it has to do something with the intersection of these, and it does relate to battery life.
It looks to me that if the watch is not communicating through LTE and using the DIGITS framework, incoming messages are just stored until such a connection is made. This would happen when disconnecting from a BT-linked watch with LTE on AUTO (LTE off if BT is on). This behavior makes sense for a phone as most of the time it would be connected to a mobile network / LTE. For the current watches, however, the problem is that having LTE on shortens battery life from the two or more days (which we get with for BT modes) to less than a day. It would be a great thing to be able to keep LTE off when there are other connections to the phone available, but then the messages get stored for later delivery when there is a mobile / LTE reconnect. I get the same behavior when I start DIGITS on my iPad, all the messages that piled up since the last time there was a connection now come through.
So, better synchronization of messages across devices through DIGITS would potentially solve this, whether it is in the watch software or DIGITS infrastructure. My Apple-centric colleagues tell me duplicate messages aren't an issue in that system, so iMessage evidently sorted this out. I hope I am just missing a setting somewhere, and look forward to a solution.
- dupslaTransmission Trainee
Amanda, I haven't had the issue with the duplicate messages since the Samsung rep set my watch up. (The settings are above in one of my posts) The battery issue is better than the last watch lasting about 15 hours average not 3 hours. I'm assuming this watch came with the update because I have no updates available.
- dupslaTransmission Trainee
I have a post above how the samsung rep set up my second watch and it does help with the duplicate message problem. I am getting 15-16 hours average, maybe a little more. Mine is the 42mm. I have 6 hours 37 min 27 seconds since last full charge and I'm at 78%.
Related Content
- 8 years ago
- 10 months ago
- 2 months ago
- 2 years ago