- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2022 09:29 AM in
Discussion- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2022 09:58 AM in
Discussion
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
03-10-2022 03:38 PM (Last edited 03-10-2022 03:39 PM ) in
DiscussionHi @AndrewC70 and @VueeyLe, that's strange. Thank you for bringing this to our attention.
If you experience the issue again, please send this through as an error report from both Samsung Members and Galaxy Wearable for our research and development team to look into.
To send an error report:
Samsung Members > Get help > Error reports > select issue category > describe issue and frequency > Tick ‘send system log data’ > Send in top right.
To send an error report for a wearable, follow these steps:
- Go to Galaxy Wearables app > click on the device desired on the side menu
- In the side menu, tap Contact us > Error reports (in the Get help section)
- Fill in details and the frequency of the issue that you have with the wearable.
- Click send.
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2022 06:32 PM in
Discussion- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-10-2022 03:35 PM in
DiscussionTo send an error report:
Samsung Members > Get help > Error reports > select issue category > describe issue and frequency > Tick ‘send system log data’ > Send in top right.
I haven't experienced that with my Fold3 & Watch4 Classic or Buds Pro.
But I also don't use Bixby, if that's the cause.
