Random reboots of the Suunto 7 during recording an activity
-
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.
-
@olymay had very similar symptoms. For some reasons watch can’t switch to offload(ambient)-mode and as I said - factory reset fixed the issue for me
-
@pavel-samokha I’ve done one factory reset. I’ll try another later today when I have some time. I’m also getting a new phone tomorrow (Pixel 5) so that will also force another reset and maybe that combination of three resets and a new phone will persuade it to work.
If not, it’ll go back to Sunnto for a refund and I’ll buy a Garmin
-
@olymay I also reported this to Suunto, will try to push the issue
-
@olymay with a new phone you do not need to reset the S7. Search for the adb solution in xda-developers. It’s easy to use.
-
A walk with a loaded route and fused track didn’t cause any problems. I cancelled the route on the way and reloaded it, no problem.
I am sure that it’s a software related problem in connection with the phone.
-
@pilleus Can you try with the higher accuracy gps track? I have never used the fused track (I don’t run for long enough to worry about battery life… yet).
And when I run I do not take my phone with me, so how could that connection be the issue?
I do agree with yo in that it is likely a software issue, as this has only been happening since the recent big update.
Yes, I do know that I can use the ADB solution (used it before with other Wear OS watches) but as I seem to be resetting the S7 almost daily at the moment it isn’t really an issue to do it when I get my new phone
-
@olymay if you’re able to work with adb - then try to do
adb bugreportplease -
@olymay okay, I don’t use the S7 without phone, because both gadgets are on board.
Tomorrow I will be back with an activity with best GPS settings and without phone connection.
-
@pavel-samokha More than happy to try, but that isn’t something I have done before. Do you have a link to a guide please?
-
@olymay don’t have exact guide, roughly the same as with android phone:
- Install ADB on you computer
- Enable Dev mode on Suunto 7 (in Settings->About-> click multiple times (7 or 10, don’t remember) on Build Number)
- Enable ADB debugging on Suunto 7 (Settings -> Dev options -> ADB debugging)
- Connect Suunto 7 to your computer via cable
- Authorize this computer to debug on S7 (popup should appear on S7)
- Open Command Prompt on your computer and type
adb bugreport
After that you should have file with bugreport
-
@olymay That is not normal, and I have not seen this problem. I would definitely contact support. They are typically quite helpful.
-
there is a problem if 2 applications are installed and running simultaneously on the Smartphone - Movescount and SuuntoApp
-
@Brad_Olwin I have a friend in the exactly situation and my S7 doesn’t do it.
-
The problem seems to be solved for my S7 after 3 crashes and 3 factory resets.
5 activities with different settings and without any problem.
2 activities with connected phone, AOD, tilt-to-wake, best and good GPS settings, no route and route.
3 without connected phone, with and without AOD, with and without tilt-to-wake, with best GPS and route.
May be that after the update something was left in the cache or something else was wrong.
It’s okay for me now.
-
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.
-
@olymay said in Random reboots of the Suunto 7 during recording an activity:
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.
It’s magic!
-
Unfortunately I was not so lucky, yesterday fifth hard reset and I can still reproduce the app crash during the activity following a path. Going through the various screens you first notice a slight slowdown passing from the laps screen to the one with the altitude profile while all the others transitions are smooth. However, the problem occurs just after 5-6 km until the final crash of the app and loss of activity data. I state that I always run without a mobile phone and I also tried to activate the airplane mode to see if anything changes, obviously without success.
-
@sherani That sounds like a right pain in the a**! It also sounds like yours it lasting significantly longer before crashing than mine did (mine was crashing as soon as it tried to go into power saving mode).
By hard reset, do you mean a full disconnect and factory reset? If not, I would suggest trying this, and it may take a few times (it took me three!). If that is what you have done, then you may have to send it back to Suunto -
Hello guys.
As you know I reported the bug and response is that it’s known and top priority at Suunto. Should be fixed with next update but unfortunately third-party (hardware provider) is involved so no ETA.