Suunto 7 update 30-06-2020

Brad_Olwin

@olymay A couple of questions. First, is this the same route or different routes? Second, did you create the routes on SA or were they imported from another app. Third, do you check to see that the route maps are downloaded after adding the route?

I can try to help once I have these answers.

olymay

@isazi Sorry for posting multiple times. I made this original post and then saw other posts by people with similar issues.

I have also been dealing with Suunto Customer Services for over two weeks and am starting to get quite frustrated, so the more posts I make the more chance I have of someone seeing it and helping me.

olymay

@Brad_Olwin It has now been with three different routes. The routes were created with the Suunto App on my phone. Yes, I checked to ensure the routes were downloaded.

Yesterday, I was getting the exact same issues but this time I was NOT tracking a route. This means that I am not able to track any activity at all. I am almost at my wits end and considering returning the watch

isazi

@olymay do you have many apps installed?

Bulkan

I have a friend with the same problem. He is using a Xiaomi linked and exactly the same, the suunto wearOS crashes, he tried sportygo and worked fine.

I mention the phone to narrow points in common.

I don´t have the same issue, but I don’t use the S7 as often the s9 for running but in my tests it doesn’t crash.

pilleus

@Bulkan my phone is a Xiaomi too. But after the third factory reset it is okay now. The last 6 activities were okay.

olymay

@isazi On the Suunto 7? No, I have installed Google Maps, Google Messages, and Google Play Music on top of the default, that is all.

pavel.samokha

@olymay Try to make hard reset “Settings -> System -> Disconnect and reset”, setup all updates then and record a workout

olymay

@pavel-samokha I did this at the weekend and it made no difference whatsoever.

pavel.samokha

@olymay that’s sad cause it fixed the similar issue for me, and seems the same to @pilleus. So it seems contact support and make it fixed by them your only way.

olymay

@pavel-samokha it looks like @pilleus had to do three factory resets for it to work. I will try one more later today, and I have new phone arriving tomorrow which will force me to do another reset, Maybe it will work, maybe it won’t.

olymay

I have taken a video of the issue as it happening today. This was recorded indoors, so there is no GPS lock, however it does the same thing even with a lock.

Suunto 7 Video

isazi

@olymay I tried on my watch but I don’t have the crash. Interestingly, your watch does not seem to get into the low power mode in the video, while mine does after 10 seconds more or less.

olymay

@isazi It used to go into the low power mode, until yesterday. Before yesterday and after the update) when following a route it would be after just over 1K when it would throw it’s wobble. But it does it almost straight away as you can see.

isazi

@olymay to be honest, I would ask support to take your watch and try to fix it, or send you a replacement unit.

olymay

@isazi I’m going to persevere with some more factory resets, as I really don’t want to be without my watch for up to a month. Especially as right now I am in the middle of a charity run during October.

olymay

GOOD NEWS EVERYONE!!

After three factory resets my watch seemed to be behaving last night (was only tested indoors and not on a run). My new phone arrived this morning so I went through a fourth factory reset to connect that.

I have just been for a 7K run following a route and it worked PERFECTLY!!

It seems that multiple factory resets (three seems to be the magic number) manages to clear whatever glitch may be present.

pilleus

@olymay said in Suunto 7 update 30-06-2020:

GOOD NEWS EVERYONE!!

After three factory resets my watch seemed to be behaving last night (was only tested indoors and not on a run). My new phone arrived this morning so I went through a fourth factory reset to connect that.

I have just been for a 7K run following a route and it worked PERFECTLY!!

It seems that multiple factory resets (three seems to be the magic number) manages to clear whatever glitch may be present.

For me the 3 factory resets solved the problem too.

pavel.samokha

I guess I’m lucky - I had to reset only once

olymay

@pavel-samokha Very lucky, but at least it worked