[ad_1]
Just a few days ago, users with Samsung’s Galaxy Watch 4 and Galaxy Watch 4 Classic received one of those news that hopefully never read when it comes to updates. The launch of a seemingly harmless new firmware has begun, and some users let their watches turn off only to later find that they would never turn on again.
Obviously, the fact that a smartwatch accidentally dies is not an expected behavior, so Samsung has withdrawn the update to prevent the situation from becoming unmanageable and the bricks from rising uncontrollably. We talked about it in our original article giving you also the first indications on how to deal with the situation, however even the most recent news is not so comforting.
Samsung has released a new firmware update for the Galaxy Watch 4 and Galaxy Watch 4 Classic, the version number of which ends with GVK4 and is expected to bring with it bug fixes and feature enhancements, as well as the November 2022 security patch.
Samsung claims that a “stabilization code relating to the operation of the power supply”which apparently seems to be an answer to the problem of clocks going off permanently.
However, it appears that Samsung has not been successful and new reports related to yet another brick after the GVK4 update are growing on Reddit and other online forums. It is too early to say if this is happening, but if the unstable condition of this update were to be confirmed, it is clear that Samsung will have to run for cover quickly by withdrawing this update as well.
At the moment the reasons behind the bricks are unclear and not all units are affected. There are also users who have not reported problems, so some speculate that the problem may be related to the age of the smartwatch, with older units seemingly more prone to suffer from it. The Galaxy Watch 4 is still one of the best smartwatches, so the best advice we can give you right now is not to update your watch until further notice.
[ad_2]
Source link
