20-08-2023 09:00 PM - last edited 20-08-2023 09:36 PM
21-08-2023 04:11 PM
Hi guys,
I've asked at our side if this is an error or new concept for the Wearable app. Me or one of the other Moderators will let you know what the developers answer with.
21-08-2023 04:18 PM
30-08-2023 12:34 AM
@AntS Received the following response from Samsung Support (cannot make out what they are trying to say 🙃)..
30-08-2023 08:18 AM
30-08-2023 10:10 AM
@Neo001 , Yeah, that response from them isn't the best. Are they just stating what they found, or how things are supposed to work now? I really can't tell from that. And either way, it's not a lot to go on.
I still haven't got an answer to my question at the Samsung side to this one, which was:
30-08-2023 11:11 AM - last edited 30-08-2023 11:18 AM
Thanks AntS!
@smg1 - I have asked again.
Now we wait .... 🙂
----
Got the following response - they don't say that it will be fixed in the next update for sure ...
30-08-2023 01:23 PM - last edited 30-08-2023 01:59 PM
I've just reported about this issue through Samsung Members app too.
The more the reports, the faster the fix 🙂
Besides, I asked to inform me when the issue is fixed. Because What's New section in Samsung updates is too ambiguous. For example, the latest version of Galaxy Wearable update (2.2.56.23071861) says: "Fixed the error". What error? No user knows.
I wonder, how many years will pass before Samsung's release notes become as detailed as Microsoft's ones?
30-08-2023 02:17 PM
@smg1 wrote:
I think they were drunk when they wrote this
From my experience, Samsung makes good products. But tech support is awful. And always been, at least for the past three years. It doesn't depend on country and the way (phone, chat, email). The result is always the same—unhelpful. One more evidence: there is no answer from Samsung representative in this three-pages-long one-week-old topic.
It's such a shame for such a giant like Samsung! 😡
30-08-2023 10:41 PM
10-09-2023 02:12 PM