Random reboots of the Suunto 7 during recording an activity

[olymay]

@isazi This is EXACTLY what is happening to me

[olymay]

@Dimitrios-Kanellopoulos I usually run with always on map ENABLED as I don’t like the small delay in the screen waking up.

But I have tried it with this setting both enabled and disabled and the problem is there regardless.

[sherani]

@Dimitrios-Kanellopoulos I have not found any difference, the problem occurs in both cases on mine and two other S7s.

[isazi]

@olymay so I tried another activity, and the watch was still in the “faulty” mode, therefore I was thrown back to the watch face without even having to check the map. Then did a restart of the watch, and now it is working properly again, although I did not check the map (because I did not need it, and because I feel it would trigger the bug again).

[olymay]

I am not long back from doing a run. I did the exact same 10K route as the previous three runs and I tracked the route as I did before.
All of the settings on the watch were exactly the same as the my previous run.

The difference this time was I did not scroll away from the default data screen.

The watch did not crash!

Therefore, I now very strongly believe that by scrolling to the map view, this re-activates the ‘power save tilt’ (I have verified that it does do this) which in turn causes the Suunto Wear App to crash.

Suunto developers, please take note, the ‘power saver tilt’ is crippling the Suunto 7. Please, please, please fix this bug or permanently disable this feature.

[Robert_mp]

Hi! Today I had no problems during my activity with the option “power save tilt” desactivated.
I’ve made a trekking of 12km and 5h20’ following a track and playing a lot with the map view.
The screen of altitude profile worked more fluent than last time (only a bit). I’ve suffered lot of lag also in other activities with the screen of hrm graphic.

[olymay]

@Robert_mp You were able to use the map view whilst tracking an activity?

What were/are your other settings in the watch (AoD, Tilt to Wake, Tap to Wake, etc… as many as you can give).

I would love to be able to use the map view, but on mine it turns the ‘power saver tilt’ back on and causes it to crash.

[Robert_mp]

@olymay said in Random reboots of the Suunto 7 during recording an activity:

@Robert_mp You were able to use the map view whilst tracking an activity?

What were/are your other settings in the watch (AoD, Tilt to Wake, Tap to Wake, etc… as many as you can give).

I would love to be able to use the map view, but on mine it turns the ‘power saver tilt’ back on and causes it to crash.

Hi @olymay . Yes, as I said before, I’ve used the map a lot during the activity I was tracking.
Other settings: airplane mode on, AoD on, tilt to wake off, tap to wake off, Map always active off, brightness auto (and low), gps 10s.

Have you done what @Dimitrios-Kanellopoulos told us? To desactivate ‘power save tilt’ option and reboot the watch… Then check the option is off.
I’ve checked this before and after my activity. The option was OFF in both cases.

[olymay]

@Robert_mp Thanks for the info

Yes, I have done what @Dimitrios-Kanellopoulos suggested and it worked. However, for me, using the map during an activity overrides this and turns ‘power saver tilt’ back on.

I have some differences in my settings to yours…
Aeroplane mode: OFF
AoD: ON
Tilt to Wake: OFF
Tap to Wake: OFF
Map always active: ON
Brightness: AUTO
GPS: 1s
I also play music from my watch via Bluetooth headphones.

I only run for a max of two hours so battery saving isn’t a concern.

If I do not go to the map view, all is ok. Going to map view reactivates ‘power saver tilt’ and it crashes.
If I turn ON ‘power saver tilt’ and try a a run, it crashes on the default data screen.
I am confident it is the ‘power saver tilt’ causing the issues.

[aeroild]

On Saturday I experienced that my Suunto 7 rebooted for the first time during an activity. I have had my watch since 31th of January and have tracked more than 160 activities with the watch. Since the September update I have tracked several runs while using the navigation. I have swiped from the main screen to the map screen, zoomed in and zoomed out on the map, let the watch turn on the power save AOD, reactivited the full color display and so on. There has been no problems, untill Saturday.

On Saturday I imported a route into the Suunto app on my phone, synced the route to the watch and went out for a hike. I walked maybe 1.5 km before getting to the point where my loaded route started. After maybe one more km I noticed that when swiping between the map screen, the altitude screen and data screen, the watch was responding extremely slow and the screens were changing like in slow motion. I walked maybe another km and then noticed that the watch rebooted. The activity had been saved and was synced to the Suunto app. In the Suunto app there is however no HR or ascent/descent info.

I hope this was a one time thing.

[olymay]

So I’ve had another play with the watch today (whilst on a boring conference call with work, shhhh, don’t tell anyone!).

I tried again with the settings I listed in my previous post. Once I scrolled to the map screen, it was game over, the app crashes. Upon checking the settings, ‘power saver tilt’ was turned back on.

I turned it off and tried again. This time it would crash in the default data screen (and it would not go into low power display). Again, the ‘power save tilt’ had turned itself back on.

I had to restart (not a full reset) the watch in order to remedy this.

I then tried another activity track, but this time I turned the Map Always Active to OFF. This time I was able to scroll to the map screen and back to the default screen and it did not crash. I cycled it round a number of times, varying the length of time and varying if I let the map go into low power mode or not. It worked every time.

This may be yet further narrowing down of the fault.

Can someone else, maybe @Robert_mp, try tracking an activity with Map Always Active set to ON please?

Any help we can give to the developers could help them resolve the issue sooner

[Dimitrios Kanellopoulos]

I had a user in another forum that said that if you disable these settings in the wear os app it fixes his issues

[olymay]

@Dimitrios-Kanellopoulos Thanks for the info.

I have tried tracking an activity (again, from sat at my desk) with these settings both on and off and I can confirm that it has worked for me.

When it crashed, I checked my settings and the ‘power saver tilt’ was again turned on, despite my having turned it off.
When it worked OK (with the settings shown turned off) the ‘power saver tilt’ stayed turned off.

So, it appears that some settings (map always on, WearOS notification settings) can force ‘power saver tilt’ to turn back on.

I use these WearOS notification settings, so this is certainly not an acceptable permanent solution.

I believe this is still a problem with ‘power saver tilt’.

[Jamie BG]

@olymay - what watch face are you using? Are you using one of the suunto power save watch faces? If so have you tried with another watch face, as it should automatically disable power save tilt?

[Dimitrios Kanellopoulos]

@olymay said in Random reboots of the Suunto 7 during recording an activity:

I can confirm that it has worked for me.

what do you mean?

[olymay]

@Jamie-BG I am using the ‘Heatmap’ watch face. It is beautiful and it is the one I want to use.

I am prepared to make only so many concessions when using a £400 smartwatch, and using a watch face I do not like is not one of them, sorry.

[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