User Profile
magenta6238774
Transmission Trainee
Joined 7 years ago
User Widgets
Contribuciones
Re: 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.4Visto1like0Comentarios