Galaxy Wearable created problems connecting to the Galaxy Watch

A problem with the Galaxy Wearable application created problems connecting the Galaxy Watch to several Google Pixel smartphones and even some Samsung devices. Considering that many people cannot do without this wearable, it is indeed a complicated situation.

Galaxy Wearable created problems connecting to the Galaxy Watch

Samsung runs all of its accessories through the Galaxy Wearable app and has plug-ins for each device. If you have a Galaxy Watch 6, you’ll download that plug-in, and if you’re pairing your Galaxy Buds 2 Pro, you’ll download a different plug-in. It’s a little confusing, but it works.

Now the big problem is that many of these connections are failing. Both for many Pixel users and for those who have Samsung equipment.

Several reports are emerging via Reddit from Google Pixel owners who have discovered that the Galaxy Wearable app is not working with Galaxy Watch devices following the January 2024 update that hit Pixels yesterday. Strangely, this only appears to affect Galaxy Watch devices, not earbuds. The issue affects all of Samsung’s Wear OS smartwatches – Galaxy Watch 4, Watch 5 and Watch 6.

Not being able to access the app wouldn’t be a big problem.

The issue is the loss of connection between the watch and the smartphone. Affected users say that their smartwatch is disconnected and cannot turn on.

While the issue appears to have been triggered by the latest Google Pixel update, it seems more likely that a Samsung app update will fix the issue. So that would be the quickest fix. Otherwise, users will have to wait until February for a correction from Google.

However, Samsung and Google have yet to respond to the issue, so it’s unclear when a fix might arrive.

Meanwhile, other reports reveal that the Galaxy Wearable app is also causing problems on other devices, including Samsung’s own smartphones. The problem leaves the application stuck. In many cases it only starts working again when users put the date back in 2023. It is very likely that the two problems are linked, but the problem appeared on Pixels immediately after the arrival of the last update and appears to be something much more widespread.