Random reboots of the Suunto 7 during recording an activity

olymay

@Dimitrios-Kanellopoulos In your message before mine, the one with the screen shot. I turned off both of those settings and was able to track an activity, following a route, scrolling to the map screen AND had map always on turned ON. The app did not crash because it did not force ‘power saver tilt’ to turn ON.

Jamie BG

@olymay - I am not suggesting as permanent fix, but it may be the cause of the issue as to why power save tilt switches back on, and knowing whether it does this with or without this type of watchface may give the devs a better idea of the cause and thus enable the fix to be found quicker.

olymay

@Jamie-BG Sorry, my last reply came across sharper than I intended.

I have now tried with a non Suunto watch face.

I tried with all of the combinations I have previously mentioned (I have done them so many times now I don’t even to refer to my notes anymore!) and I can confirm that the choice of watch face had no impact on the result.

Dimitrios Kanellopoulos

@olymay but you still have the issue after those optins where disabled (at my screenshot above)?

Just making sure

olymay

@Dimitrios-Kanellopoulos sorry, I waffled a bit.

After I turned off the notification settings in your screenshot, I no longer had the issue of the app crashing during an activity.

I now have two options before my next run (maybe tomorrow):

On the Watch, turn OFF the always on map in the Suunto Wear App: Power saving>Display>Always-on-map
On the phone, turn OFF both of the notification settings in the WearOS app: Notifications>Silence phone while wearing watch>Silence incoming calls & Silence alerts and notifications

Both of these seem to allow an activity to track and use the map screen without forcing the ‘power saver tilt’ to reactivate and crash the app.

I can also confirm that the choice of watch face has NO impact on the watch crashing, for better or worse.

Robert_mp

Hi @olymay and @Dimitrios-Kanellopoulos , yesterday I made a small test (25min walking, 2,2 km). All was ok, NO crashing… but maybe it was too short.

Configurations:
Sport mode: custom of walking with: 4 fields screen, 4 fields screen, map screen
Exit the app while recording: yes
Phone call: no
Music controls: yes
Follow a route: yes
Always on map: enabled and disabled (mostly enabled, but I tried to change between both options to test a bit more)
AoD: on
Tilt to wake: off
Tap to wake: off
Power save tilt: off (I checked before the activity, during the activity some times, and in the end of it, that this option was all the time OFF and it didn’t changed to ON)

During the activity I changed lots of times to the map view, and it was fluent while I was operating with the watch. I only had lag on the summary of the activity when I finished (I experience this always)

What I also experienced, but maybe is a different point to this thread, is that if I had “map always on” activated, when I changed to a screen different from the map, let it go to save battery mode, and the forced it on again, when I changed to the map view, it turned back to 200m zoom (it doesn’t keep the last one), and it was like it loaded the map again. With “map always on” desactivated, I haven’t experienced this issue.

olymay

After a few days of rest, I went for another run today.

Settings:
Sports mode: Basic run tracking a route
GPS: 1s
Aeroplane: OFF
AoD: ON
Tilt to wake: OFF
Tap to wake: OFF
Map always active: ON
Power saver tilt: OFF
Brightness: AUTO
Music streaming to BT headphones and controlled from headphones.

These were exactly the same settings as I reported on the 2nd November, with one key difference.
This time, I followed the advice in @Dimitrios-Kanellopoulos post and I turned off the silence notification settings in WearOS on my phone.

Everything worked perfectly!! I was able to use all of the screens, including the map screen, and the data screens always returned to the low power mode and did not crash the app.
I have checked and can confirm that ‘power saver tilt’ has NOT been turned back on.

It’s not ideal, but at least I now have a usable interim solution until Suunto roll out the proper fix for this problem.

If anyone else is still experiencing the app crashing, please try and this ‘fix’ and let me know how you get on

Piotrd

Hi all,
I am experiencing the same problem, tried different settings, no luck. But what I find the worst is the response I got from suunto. I sent it to have it fixed, described it thoroughly, and…they sent it back to me, with a note that it works fine for them.

I read here it’s a known issue, yet authorized customer service is not giving a beep about it. So they just can’t fix it and so they pretend there’s no issue? That’s so lame. Can’t use it, can’t even sell it cause I don’t want to sell a buggy device. Sorry suunto, never again. They should return money or offer replacement, but they prefer to lose clients.

pavel.samokha

@Piotrd sorry for your experience.

Have you tried what we’ve figured out in this topic:

Go to settings -> gestures -> disable “power saving tilt” and reboot the watch after that
On your mobile phone in WearOs App go to Notifications -> Silence phone while wearing watch, and check that options there are disabled

After that there were no problems for me with S7

olymay

@Piotrd i was having this exact same issue and I can confirm that what @pavel-samokha suggests works (at least it does for me). Give it a try and see how you get on.

I understand there is a fix for this coming soon

Piotrd

@pavel-samokha @olymay
Thanks a lot guys. Will test it today.

So the phone should NOT be SILENCED, is that right? Can it be done just before run and reverted afterwards or does it need a watch reboot too?

olymay

@Piotrd Correct, in WearOS app on the phone, go into notifications and turn off both toggles under ‘silence phone while wearing watch’. This is what I do and it works for me.

And yes, you can toggle this for each individual activity and you should not need to restart your watch or phone each time.
I keep a note on my running headphones to remind me to turn it off each time I go out

Piotrd

@olymay @pavel-samokha thx a ton guys, it worked! Only tried once so far, but seems that this might be the solution. If it works, I’m ok waiting for the update, at least the watch is usable now!

pavel.samokha

I guess with arrival of PXDZ.201119.005.A1 this one should be closed, it’s fixed

P.S. And thanks for all who contributed to the subject, I believe it helped solving the issue and workaround was really helpful in the meantime