[Watch] Text cut in some views
-
Nothing I guess (not checking)
I was just kidding about your last reply, I didn’t meant to generate entropy, sry
-
@sartoric ouf got scared again. I think I have so far typed so many bugs…
HEad hurts, and I have this lawmower guy under my house not helping.
2 Paracetamols and keep going -
Proper (qa-)tests should have figured it out.
Really looks untested.
If tested Suunto wouldnt have released it like this?! Hmmm, OK, yes, they would, as we learnt in the last years -
@asdf123 I personally with about 100 testers did test this for about 2 months.
If there is a localization text wrong that has passed the QA from that specific country -
@asdf123 well they still have time to fix some bugs… They haven’t sent out release notes or a change log
Also…
-
So if you want to play a blame game, the corresponding department (Germany etc) did not do a good job.
There is a difference on FW and localizations. These messages localizations are pulled from QA that do this specific job
-
Plus you always are free to revert to the previus one.
-
@derek-lee yup. That is true. A new .40 will come out soon.
In sort people bricked devices with flashing whatever they found on the web.
-
Although I haven’t ran into any problems myself and I can’t speak for others, but I think I would rather wait for a firmware update that is stable than one that is quick baked. Kudos to you and @Jouko-from-Suunto for communicating all of the info to us. If anything this was a step forward in communicating with users and I am optimistic for the next update!
-
@derek-lee Sorry man, but we have tested this FW for literaly 2 months. 100 testers.
Can you explain what is the instable part apart from obviusly the localizations that was explained above which does not relate to instability?Can you elaborate?
-
@derek-lee Just to break my NDA and perhaps say something more. This FW is done closed and dusted since APR. That said since APR there have been rather no issues and the ones that have arrised Suunto is trying hard to figure out why the OHR update got broke for some models. One and a basic speculation is wrong FW flashing.
-
@asdf123 Wie sollte man das ansonsten übersetzen und abkürzen, um nicht zu viel Platz zu verschwenden? Ist doch auf einen Blick klar, dass das „Durchschnitt 3 Wochen“ heißen soll. Oder nicht?
-
No, no don’t be sorry. I’m not trying to bash Suunto, I love my Spartan Trainer and I think I can say for a majority of the users that the 2.0.34 update has made it exponentially better!
I was trying to point out that lots of people(including me) felt that an update would come in April and I think that may have rushed things a bit.
Communication about software updates is definitely a PR thing and might make Suunto look bad on not delivering on promises on time but, I think communication with the users is probably what most people want instead of speculation
. But thanks to you and this forum, I can say owning my watch has gotten a whole lot nicer! -
@derek-lee Thanks man! Thanks a lot for these words
-
No worries!
I don’t think you get enough praise for your work and time that you’ve invested into these forums! We can all agree that we’re all here to make our watches better, even if it doesn’t seem that way. -
@derek-lee
THEY listen
-
@solid_dd One of the problems here and at this moement is that a lot of bad things happened, not on this forum, but on others and a lot of people by flashing wrong FW are bricking devices.
That breaks the tremendous effort Suunto and I and other tons of testers did.
We feel “hurt” about it as testers that eg we missed a localization.
From the 1st words of @Derek-Lee I felt kinda worse like we did not test enough while we did.
You know, 100 people of about 14h per week on training on all activities pods etc are here to try to reassure that you get a piece of SW that makes you guys happy and better athletes.
So I do apologize to @Derek-Lee for misinterpreting his post and me getting stuck on the ‘hurt’ feeling.
But, just to get in my shoes, you guys test the Suunto app, when it’s released to Spartans officially and someone comes and says x,y, goes wrong I bet you might feel a bit responsible, and then as we are humans the sentiment changes a bit…
Ouf what a day .
Community Manager / Admin @Suunto
Creator of Quantified-Self.io
youtube.com/c/dimitrioskanellopoulos
https://instagram.com/dimitrioskanellopoulos
https://www.strava.com/athletes/7586105 -
You do a great job here, and also do all your testers, it is impossible to find EVERY bug or translation error.
-
@solid_dd
I totally agree, its subjective. On one hand Suunto can build trust with its current users with communicating delays and roadmaps, but on the other hand, their reputation will take a hit when they don’t deliver or when they have to delay updates. The plan I think they’re taking now is much safer which is to not release things until they’re done and to not provide information about it.
-
@catracermk said in [Watch] Text cut in some views:
@asdf123 Wie sollte man das ansonsten übersetzen und abkürzen, um nicht zu viel Platz zu verschwenden? Ist doch auf einen Blick klar, dass das „Durchschnitt 3 Wochen“ heißen soll. Oder nicht?
Nur weil ichs mir ausdeutschen kann, ist das lange nicht passend und professionell dargestellt. Da stelle ich an Suunto andere Ansprüche als an einen “chinesischen Billig- Clone”
