More and more people are turning to smartwatches powered by the Wear OS operating system Wear OS to take a break from the distractions of smartphone screens.
The idea of being able to leave the house, leaving your smartphone on the nightstand, carrying with you a device capable of handling your basic needs, has become a habit for many users.
Among these needs, entertainment plays a fundamental role: listening to music, podcasts or audiobooks during a workout session or a walk is an experience that is hard to give up.
For many, the preferred app to manage this audio flow is YouTube Music. However, precisely those who rely on this service are encountering particularly annoying obstacles that undermine the entire mobile experience.
YouTube Music, new problems on Wear OS smartwatches
The bug manifests in a specific and limiting way for those who own devices such as the Pixel Watch and the various iterations of the Galaxy Watch.
According to the numerous testimonies gathered online, particularly on Reddit, the offline playback system of the app is proving to be unreliable.
The standard procedure requires the user to download a full playlist directly into the smartwatch’s memory, to be able to enjoy it offline. The fault occurs when playback starts: the application executes the first track of the list correctly, then abruptly stops right after.
To make matters worse, the graphical interface partially locks up. The buttons to skip to the next track and to access additional options appear gray, completely disabled, preventing any interaction to scroll the playback queue.
It is easy to imagine the level of frustration this anomaly causes in a runner or hiker who, being miles away from home without a smartphone, finds their music entertainment paralyzed for the rest of the activity.
Attempts to resolve and the wait for an intervention
In light of this issue, the community has sought to identify do-it-yourself procedures to restore normal software operation.
Some users have reported trying to clear the cache, delete the app data or fully restarting their smartwatch. Unfortunately, these actions provide only temporary stopgaps.
The problem tends to recur relentlessly after a few usage sessions, showing the lack of a definitive, self-manageable solution for those who own the wearable.
Reports indicate that this bug has persisted for over 30 days. Despite the number of reports, Google has not yet taken official action to curb the situation.
A check of the official bug tracker does not reveal any open discussions on this specific topic.
For the moment, the true causes triggering this lock remain unknown. Note that not all Wear OS devices seem to be affected systematically.
