Forum Discussion
Galaxy Watch LTE duplicate messages
- Hace 7 años
@dupsla y @magenta6238774 , thank you both! I sent a PM your way which should be in your bandeja_de_entrada. I also agree about the latest update which is something I'll include in feedback because I do think @magenta6898941 has a great point.
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.
Contenido relacionado
- Hace 8 años
- Hace 3 meses
- Hace 11 meses
- Hace 2 años