Wear OS 2.39

[masi0]

still on 2.35 - how to check updates on the watch?
update: 2.40 on the phone

[Jamie BG]

@masi0 - I assume you aren’t referring how to check to see what version, but how to see if an update is available? If so:
Watch firmware - Settings / System / About / System Update (you should be on H - MR2).
Apps updates - these come through the google playstore. If you have auto-update they will come through automatically, otherwise you will need to go into the playstore and manually update them.

[Zab_55]

Hey !
Have you experienced some issues with this latest WearOS update ? I’m iPhone user, so not sure if the issue is due to iP or it just sucks.
Since last update :
Alarm clock doesn’t show how much hours left until the alarm turn on.
It’s still showing Disconnected phone , but sometimes it receives notification, but mostly not. In app it’s showing disconnected too and syncing takes much longer.
Tilt to wake was working better on previous firmware too.
I tried forget and disconnect watches in phone, made factory reset and it’s the same, so I assume that it’s due to firmware. Wondering if it’s not better to delete update and just stay on previous firmware until they make it work properly.

[Egika]

@Zab_55 Hi!
I have not experianced any bad side effects from the last FW update.

This topic is about the WearOS app though, which is part of the built-in apps and just recently was updated independently to the watch OS.

[Zab_55]

Yes I’m talking about the build in app which recently updated to 2.39. I assume this might be the issue since the watch worked perfectly fine until I received this “silent” update as the others.

[Jamie BG]

@Zab_55 Your watch has 3 main versions of software:

Updated by manufacturer:
Firmware - should be on H MR2 (google supplies to manufacturers who incorporate it and roll it out - this will include the suunto app on the watch - this is the one you can update via the settings. Its the base underlying structure of wear os.

Updated by Google via the Google Play store on your watch:
Wear OS - should be 2.19 - from what I can make out this is the flesh and muscles to the bone structure of the H MR2, and can be considered your operating system. Most users, especially those on 0.5GB of ram have noticed some performance and battery improvement off this update (note this is with most of them running firmware of H MR1 or older - only Suunto has the H MR2 update at this time.

Wear OS home - should be 2.39 - this is your home launcher - the skin over the wear os experience and seems to be what may include the built in apps - but not certain. I do know that when we get 2.40 (no idea when) it will give us more tiles (looking forward to that) and I suspect the new weather app.

Suunto of course isn’t responsible for this, however of course the rest of us on this forum or on reddit would be happy to assist you in trying to resolve any issues you may have with wear os.

Disconnects are generally phone and or app related. Make sure that all of your wear os apps are on latest version (see above for watch - firmware doesn’t matter). Not sure what your phone should be as only know for android.
I dont know if apple has this functionality - but make sure it isn’t restricting the wear os app on your phone in any regard - if the iOS system is closing down the app when not in use it will disconnect from your watch.

If all your apps are up to date, a roll back may help for watch and or phone. (I know that iOS recently updated, so may be a case of wear os hasn’t yet caught up with that update, in which case only fix may be iOS rollback). Alternatively try restarting the watch - as sometimes it can help fix glitches like this, and or try restarting your phone (Had it happen once a couple of months ago with regular disconnects - it was something glitching on the phone - restarted phone and no more issues).

[Zab_55]

Thank you very much for your answer. It seems to be hit and miss with finding out what exactly is the issue. That iPhone update is a good point though.
We will see what 2.40 brings, but as I mentioned before, the older version was just fine and I didn’t have issues ( at the time when I bought S7).
My Suunto firmware is up to date, and ofc I don’t blame Suunto for this, not at all. I understand that this is probably Google’s fault and their lack of updates for WearOS ( hopefully they’ll change this soon)
Thanks again !

[Jamie BG]

@Zab_55 - you can go back into the google play store and roll back the update, but not sure how much that will help as might roll it all the way back to the base (not that you have anything to lose).

You might also want to consider setting your play store to manual update from autoupdate so that:

1. you know when an update is available and can decide whether to install it or not (by seeing feedback etc).
2. Saves battery life. Can sometimes try to update at very bad times, and as it can activate wifi, though most of the time it just does it through your bluetooth connection, making it a slow process (the 4100 chip shows it muscle on this task), it keeps your watch awake for longer and causes battery drain.

I have mine on manual update, and every couple of days once I have it on the charger, I check the play store and then trigger any updates - so at least it uses wifi so quicker; and as charging no impact to battery life.

[Zab_55]

@Jamie-BG yes mate, that’s what I did, so actually testing it out. Hopefully it helps and as well setting the play store to manual updates might be the good point. Thanks !

[pilleus]

WearOS version 2.21 on my Mobvoi watch, on my S7 2.19.

New information about an update?

[Mi_chael]

2.39 for me waiting for 2.40 with the new météo widget and no tile limit.

[pilleus]

@Mi_chael this is WearOS home app. 2.39 on the S7. Correct.

I speak about this version:

[Mi_chael]

Where see that ?

[pilleus]

@Mi_chael said in Wear OS 2.39:

Where see that ?

Settings - system - info - versions

[Mi_chael]

I see 2.21

[iTomB]

2.19 on my S7

[DavorP]

2.19 on my Mobvoi watch (Ticwatch Pro 2020).

[pilleus]

Somebody an explanation why there are different versions on the same watches?

[johann.fuehrer]

@pilleus said in Wear OS 2.39:

Somebody an explanation why there are different versions on the same watches?

Staged rollout in different countries/ IP network ranges…

But also other algorithms are possible. They like to balance network traffic to their servers to prevent peak load. Nearly everyone does this today if a larger number of devices are affected.

[mjposner]

My watch lost its custom face this a.m., thought it was an update but still on 2.39 here in the USA.