Gear S3 screen wake-up goes out of order after Tizen 3.0.0.2 update

Samsung Gear S3 series users can awaken their device’s screen either by pressing the power button or by enabling the Wake-up gesture (which uses motion sensor to awaken the gear).

Needless to say, the first thing a user would want to see after screen wakeup is time. But, after the recently pushed Tizen (3.0.0.2) update, the music app automatically pops-up on waking the gear’s screen instead.

While the problem is mainly reported by those who have enabled the ‘Wake-up gesture’, we have come across similar reports from users who manually wake up the gear by pressing its power button. Majority users report that the stock music player automatically launches on waking up the gear, and even plays music in some cases. Quite entertaining, isn’t it?

In some cases, it’s the Spotify app that launches instead of the in-built music app. For more clarity, take a look at how some of the affected Gear S3 and S3 Frontier users (1,2,3,4,5) word the issue:

I updated my gear s3 frontier to tizen 3.0.0.2 and ever since I have done that my watch will wake up on the music app and randomly start playing my music through my phone. This has been very frustrating as I haven’t been able to wear my gear at work.

I’m having exactly the same issue right after Samsung updated the Tizen software on my watch to version 3.0.0.2. Upon waking up with wake-up gesture, the stock music player shows up instead of time. When this happens, I have to click a button to display time.

Since I updated to 3.0.02 I’ve had this same issue with the stupid media player popping up, it seems to happen every time I press the top right button when my watch is asleep.

It’s also worth mentioning that the problem is being majorly put across by those on T-Mobile network. Even an expert on XDA noted that this could be a T-MO specific issue, but we are not sure about it.

Samsung’s take on the matter

The matter in question recently got addressed by a Samsung moderator at the company’s official help forum. They were also in agreement with users, that it’s an update triggered issue and shall hopefully be take care with another update.

Here’s their exact statement:

Since it certainly appears to be the update at fault, there isn’t much troubleshooting that can be done. I’m going to instead forward all the information you’ve given to our engineers so that they can fix this with another update

That being said a few days back, it’s safe to assume that the concerned team must have been made aware by now. And we hope they debug as well as fix whatever is causing the problem soon. Rest assured, we are keeping a close watch and will update as and when any new development catches our sight.

Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur