User Profile
magenta6238774
Transmission Trainee
Joined 7 years ago
User Widgets
Contribuciones
Re: Galaxy Watch LTE duplicate messages
Hi Amanda- Battery life has gone back to multiple days since I leave the watch connected to the phone by bluetooth most of the time. The original issue of duplicate messages hasn't come back when switching to LTE, so major step forward. As before, I don't think this can be called solved until a reproducible process is in place. In that direction, how do I PM my ID to you? Also, I'm not sure if the current update solves the independent line issues, detailed nicely by magenta6898941.0Visto0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
Hi dupsla- It is still good. There seem to be some message synchronization behaviors I am not familiar with (i.e., would have implemented differently) but the core issue of getting a stream of duplicates when going onto LTE hasn't come back. Did your update work?0Visto0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
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.1Ver0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
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.1Ver0likes0ComentariosRe: 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!1Ver0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
Same here, the update did not help getting duplicate messages when switching from BT connection between the watch and phone to standalone. I am very interested to hear if this problem exists on the AT&T or Verizon systems, or if it is specific to T-Mobile/DIGITS.1Ver0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
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.2Visto1like0ComentariosRe: Galaxy Watch LTE duplicate messages
Hi Dupsla- Great to hear the new one is working well! I would very much appreciate your insight into the settings I'm using: Under the watch Settings/Connections: Bluetooth: Off Mobile Networks/Mobile Networks: Always on Mobile Networks/Mobile Data: On Mobile Networks/Data Roaming: On Mobile Networks/Network Mode: LTE/3G (auto connect) Wi-Fi: Off NFC: Off My understanding is that this would keep the watch on LTE - no bluetooth of Wi-fi connection, but communication with my phone through the Samsung account. This setup was the best before the update, providing decent battery life, no duplicate/past messages coming in when switching to LTE-only, and only a few quirks. This morning, I re-toggled all the settings listed above (turned them to their other states and back) and am getting better battery life today (5 hrs and battery at 70%) so things are looking better. Many thanks for any insight you can offer!1Ver0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
Just a one-user warning story, don't update the watch software. I got a notification this past weekend that one was available, so am now on R815USQU1BRJ3. On LTE, battery drain has dramatically gone up. Starting from a full battery at 8AM, I used to have about 50% at 7PM. Past two days, the battery ran out of power around 6PM.0Visto0likes0ComentariosRe: Galaxy Watch LTE duplicate messages
Hello. I tried both routes from the thread. With DIGITS for the watch disabled and bluetooth / wireless connection on, things work well. However, then the watch won't connect to the phone number on LTE. With DIGITS enabled for the watch and bluetooth / wireless connection off, the phone and watch get copies of all messages somewhat simultaneously. Sort of works, but as other noted, involves heavy battery drain. It isn't really a good solution to have to log in to enable / disable DIGITS each time the watch is to be used separate from the phone. It also takes time for enable / disable to take effect; a few minutes but the point is to be able to go use the watch (for a run, for example) without the phone. Inconvenient to have to wait some time before heading out. So, no good solution.1Ver0likes0Comentarios