Samsung is bringing out a fresh Samsung Galaxy Watch 4 update. The company is providing a fix to earlier reported issues. These issues have affected users who had updated their wearables to version R870XXU1GVI3.

This new software update arrives with firmware version R870XXU1GVK4.It offers system stability improvements. It even includes the latest November 2022 security patch.

Also Read: Twitter Blue Tick In India, Check The Prices Now!

Issues With The New Update

The users of Samsung Galaxy Watch 4 and Samsung Galaxy Watch 4 Classic have complained that their smartwatches are bricking or becoming unresponsive. This occured after installing the R870XXU1GVI3 update.

Howeve this new update claims to fix the problem. But some users are still facing the same issue.

The South Korean electronics brand has begun roll out of the new software today to the smartwatch. This update has the version number R870XXU1GVK4. It is meant to replace the previous R870XXU1GVI3 update. This was discontinued after several users reported that this update had bricked their smartwatches models.

Also Read: WhatsApp Community Feature Now Available!

New Update

The latest update claims to improve the stability and reliability of the software. It upgrades the Android Security Patch to November 2022 from August 2022. Further, Samsung stated that a “power operation-related stabilization code” is applied in this update. It may be an act to fix the issues. These issues was caused by the previous R870XXU1GVI3 update. The new update will be available through the Galaxy Wearable app.

The Problem Still Remains

But hours after this rollout took place. A number of smartwatch owners are still complaining that their watches are bricking or becoming unresponsive.

However, the smartwatches units had not faced any problems with the October update. But even they are also facing troubles with the new update.

Also Read: Reliance Jio 5G Now In More Cities!

One of the user of this smartwatch said that their device restarted a few times during installation. But finally worked as usual. While the issue still remains unclear. Furthermore, Samsung has not worked on this problem yet.


Comments