Bug in target bar on a S9B
-
Hello all,
Every time I enable target bar for distance and disable wrist hr before recording move My target bar gets stuck at the beginning. See video. It happens in custom or preset sport mode.
-
@lexterm77 This bug has been reported. Just leave wrist HR on, it won’t matter and the progress bar will work.
-
@Brad_Olwin said in Bug in target bar on a S9B:
@lexterm77 This bug has been reported. Just leave wrist HR on, it won’t matter and the progress bar will work.
Thanks,
What about when you go into route navigation to select route and instead of returning to option menu after pressing upper button navigate, it goes into navigation and does not record activity? It happened to me twice but I did not try to replicate problem.
-
@lexterm77
I notice this frequently. It just does not show if it locks satellites or not but my activities still were recorded.
if you do too many ajdustments in the start menu it runs into issues like that. -
@TELE-HO The observation that the icon does not act appropriately is known, in my experience activities are recorded as well.
-
@Brad_Olwin said in Bug in target bar on a S9B:
@TELE-HO The observation that the icon does not act appropriately is known, in my experience activities are recorded as well.
Okay, sometimes when playing with options and when you exit options you have small icons that become green when gps gets a fix hr belt or powerpod become connected, icons stay gray for minutes. What I do is swipe up for options and swipe down again and try again and they become green. I can’t think of anything else to add but it is good to know they are known issues. Is there a post with current known issues for current firmware?
-
@lexterm77 said in Bug in target bar on a S9B:
Is there a post with current known issues for current firmware?
some threads are marked as planned… I’ve asked for a summary of known bugs and planned features and bugfixes but haven’t seen anything like that yet.
you can search by tags but it is not easy to see and not at one glance -
@TELE-HO
there is an old thread about bugs afair -
@sartoric
it would be nice to have a feed (not a discussion) that informs us whats known and whats planned… everyone who is working to a minimum of systematic has a list and while I don’t expect that Suunto drops their pants and tells us a schedule it would be nice to know at least what bugs are known and planned to be fixed and in general planned features.
I would very very much appreciate that. It will also reduce redundant questions that pop up over and over again -
@TELE-HO those tags are for the app. This forum was originally designed only for the app, and the fact that we discuss watches here it’s a recent development.
-
@TELE-HO If he wants to @Dimitrios-Kanellopoulos can comment here but I can tell you that that feed will not happen. As a field tester I report all the bugs that I find. Suunto prioritizes those bugs and incorporates them into their plans for firmware updates. Depending on how the bug will be fixed I have no idea what is going to happen. All I can do is look up a bug and determine if it is reported (Suunto confirms the bugs we report). It may be a long time before the bug is fixed or a short time. It is more complex than just fixing a bug so a schedule is difficult. For example, I reported a route finding bug where on overlapping routes or out and back routes the watch would send you in the wrong direction. Since (unknown to me) Suunto was already developing waypoints the bug would be eliminated with a waypoint update. I assume that rather wasting developer time to fix the bug, the developer time was invested in waypoint functionality that fixed the bug. That should provide an idea of why bugs may not be simple to squash and are complicated by whatever development plans are on the horizon.
Planned features are unlikely ever to happen again. Suunto did that with the Spartan and they were raked over the coals for not meeting the initial deadlines.
So the questions will pop up over again I guess. -
@Brad_Olwin
that’s why I did not ask for a schedule -
@isazi
i know it made the impression of wanting more features on the watch, but in fact i’ve had issues in mind that are SA related, such as ascent for resort skiing. but anyhow, since this forum was changed from SA forum to Suunto forum also watch related things are now officially allowed, no?guys, i hope you did not get me wrong here… all i wanted is to suggest is an easy way for people to lookup if things they discover are known already and/or planned to be fixed as it would make life so much easier
… without schedules or promises etc -
@TELE-HO this is an open forum.
Why you don’t just start a thread with a table to collect all known and reproducible bugs? Others can add, and who cares if any of this if officially known to Suunto.
It’s just an awful lot of work to keep the information up to date… -
@Egika
i’ve started a feature wishlist for S9B.
the reason why i don’t start a thread with known issues is because I can not list information that i officially don’t have -
@Egika @TELE-HO I think @Egika has a great idea. I would separate bugs from desired features. I will help add to bugs if you get it set up. For features, the voting is important and unfortunately the features often become unrealistic. If you have control of the table that may not happen. I was not thinking you were complaining but just wanted to tell you how this looks from my point of view and it isn’t much different than yours. Another bug that was reported long ago is notifications on iOS, they don’t work for several of us. Still is a bug, if I have SportsTracker installed notifications work. Go figure…
-
I’ve found the post I mentioned
https://forum.suunto.com/topic/896/sa-2018-june-status-report?_=1588423670946
@suzzlo did a huge work on that and it was obviously app related
-
I suggest every public firmware followed by a post with list of new features, new bugs and bugs carried over from previous fw versions (if any) in bullet points for an easy overview. When people post new bugs in thread original post gets edited with a list of known bugs. When a bug can get replicated by another user, it can get confirmation on reproducibility.
That way it would save us time reporting them, and lessen strain sending messages back and forth on twitter or SA support.
-
@Brad_Olwin
I am not sure if I described it correct. This forum is full of bug reports and separate feature request. I don’t think it makes sense to re-list them all.
What I would like to see is a list from Suunto (not from users or testers) what they are aware of.