Samsung Galaxy Watch 4, Watch 5 users report this issue with latest wearOS update – Times of India

Samsung launched the Galaxy Watch 4 series in 2021 and the latest Watch 5 lineup came out in 2022. Both smartwatches are available in India as well. Now, some Galaxy Watch 4 and Galaxy Watch 5 users are reportedly facing an issue with their wearables. According to a report by 9to5Google, some Galaxy Watch 4 and Galaxy Watch 5 owners have reported issues with the “raise to wake” feature. As per the report, this feature is “not working properly” on these smartwatches. Here are all the details about how the latest wearOS bug is affecting Galaxy Watch users.
What is the “raise to wake” feature
The “raise to wake” ability is a common feature that is available in most smartwatches. This feature allows users to see the time, notifications or other information on the display. With this feature enabled, users can simply raise their wrists and the screen will “wake up” to show screen data. This feature on smartwatches is powered by sensors which are included within the smartwatch.
How is this feature affecting Galaxy Watch users
The report claims that some Galaxy Watch 4 and Galaxy Watch 5 users have complained that their devices are locking themselves immediately and going back to sleep, even with the “raise to wake” feature enabled.
In an ideal situation, these wearables are expected to go to sleep a little while after the user performs the raise-to-wake gesture (unless further input is made). However, Galaxy Watch 4 and Watch 5 users have reported that their smartwatches are going to sleep much faster than the ideal situation.

Several Galaxy Watch 5 and Watch 4 owners have shared this issue on Reddit. Other users have also reported a similar bug on Samsung’s support forums. Moreover, one user has also shared a video showing the issue.
Samsung’s reaction to this issue
The report doesn’t mention if the South Korea-based tech giant is aware of this Galaxy Watch issue. Moreover, the company also hasn’t officially shared any comment about the bug and if they are planning to fix it. The issue also doesn’t seem to be a widespread one, the report adds.
Also Watch: