Suunto Vertical: Bug Collection
-
@jjpaz Hello, I have lost this widget, where can I find this recovery widget? and problems with maps location Ukraine
-
i have a strange new “problem” lately of minor importance though:
the oHR is turning on at random times while i have turned it off . The difference to the previous situation is that I enabled the widget for Blood oxygen (and its metrics)
I don’t really mind about the oxygen because it typically gives erroneous valus of no interest to me but for some reason i tend to relate those two things
-
@trailcafe Hello. Lately I’ve had this error: the media player seems to be greyed out, music is playing, even the track titles are changing, but it’s not controllable with the watch. I’ve tried powering the watch off/on, doing a soft reset, removing and basically adding the “media control” option, but nothing helps. Does anyone have any idea how to fix this? This error appeared long after the last SW update.
-
@Martin-Vrska I have the same; where it does not allow you to control the media from the touch screen. It will also hang up or not switch between various media platforms (music, podcasts, etc.) that are both native and added to my Android phone.
-
@Todd-Danielczyk Thanks for your response. I just don’t understand why this is happening for no apparent reason - as we have already stated - I have been observing this for the past week.
-
@Martin-Vrska I didn’t see it grey out on previous firmware but have seen it on 2.33.14.
The switching from media players (in my case Oto Music, Podcast Republic on Android) has been there since I’ve owned the Vertical. That and the media countdown timer not refreshing when replaying a track is something I have also seen.
-
@Todd-Danielczyk Unfortunately - even the update to 2.33.16 beta and resetting the watch, but didn’t help.
-
I am quite annoyed, as my Vertical crashed / froze in the map view in the middle of an activity, after 4,6km of planned short 6,5km-Oslo-city run.
After a restart the run was synchronized … at least the part until the Vertical froze.
What was active/activated:- the route
- map view
- external HR-monitor (Wahoo Tickr Fit … as usual)
- Burner-App
Anything special? Not really, usual weather, changed the size of map once (shortly afterwards it froze)!
-
The tones and vibration seem not correct . Setting the tones as to vibration the watch still rings on notifications
-
@Shrek3k did you send logs after the event?
-
@thanasis
Today I observed the oHR while at rest to start increasing to 150+… while the actual Hr was around 80-82 (measured via a medical device)
I changed it to various positions without any successI had to turn off the switch and the turn oHR measurements and the watch started 85-86 (normalish values )
Never have I observed such a strange behaviour before
-
@Shrek3k
happened to me twice this year during hiking activity. Froze in the map view. So i need to do soft reset. After synchronized the ascent and descent value in SA is show zero. I didn’t turn on any Suunto+ -
@isazi unfortunately not. As I have no fully accessible computer with me I could not create the log-file … I will check when I am at home today what I can export before doing the next activity tonight. Depending on the result I will send the log and the fit-file to support.
-
@Shrek3k logs are sent via the app, not a computer. But it is probably too late at this point, the log file is overwritten more or less every 24 hours as far as I know.
-
@isazi OK. I searched for a description how to create log-files, as I could not find the option in the app, and found a description in the lounge, which mentioned the computer. I will check and search, and will be prepared the next time … (Although another crash might create more intense reactions
) -
@Shrek3k currently sending logs is in “Settings”, then all way to the bottom of that screen.
-
@isazi Given the number of software problems, the option to send logs should be easier and more intuitive.
Or even an official bug tracking system where you can report them and see the progress of work on solving them.
-
@maszop bug tracking in Suunto is not a platform open to the public. It would just explode from the many users that THINK they found a bug but their device but it’s actually working as designed.
-
@maszop as already specified elsewhere in the forum, that function is only there to be used when requested by support, not on your own, so it should not be too prominent in the interface.
Because some people here can fill in bugs for Suunto we sometime requests users to do it (if they want) and tell them how to do it. But this is just voluntary, we are not support.
-
@Egika while I definitely agree, that its good that tickets are not open to all, I still think the process is much harder that it needs to be (and I speak as a QA engineer…)
- the fact that we have absolutely no control (we can’t even see, from a privacy standpoint that’s a big no-no) over what is sent, i already mentioned it elsewhere, but just providing a sample, or allowing to store the file locally would be enough
- we can’t add remarks, that would GREATLY help the people receiving, for example, i could say “the problem XXX happened at precisely 8h31am, when the watch was supposed to vibrate for the 2nd km of the run”
- we don’t know how “deep/long” a log is, we are very, very, very much in the dark, even when asked by support.
It needs to be better, even for me its too involved and convoluted
