[solved] Reboot during activities
-
@isazi I sent my logs after a reboot (once I did a hard reset). I’ve had no feedback so far. If you need more info, let me know…
Do you think I should contact support ? -
@glaucidium-passerinum Yes, you should contact the support and provide the log ID but be prepared that the response you get is to try hard reset (does not fix anything) or send the watch to the service. Sending logs most probably means nothing (at first I also taught it is just enough to send the logs).
I recommend downgrading to the previous version. For me, 6 days have passed and so far so good - no reset (that’s 12 training sessions with GPS active).
or
sell the watch. -
@fecek
@glaucidium-passerinum
this is what I understand:
sending logs means a lot actually. with the correct failure description, time logs sent, account name and time crash happened, it is the best information developers can get to look into what might cause the crash. -
This is probably my last post on this forum as I am switching to a passive mode.
I really do not want to argue with you guys as I’ve already spent too much time and energy investigating the issue, reporting it via “official” channels (also unofficialy here), and other than that due to a bug I’ve lost 75$ that I would donate to an animal care organization.@sartoric said in Reboot during activities:
@fecek said in Reboot during activities:
moderator should not be a middleman between Suunto “secret” society of suunto testers and devs.
@fecek said in Reboot during activities:
I would ensure the customer that we are at least investigating.
Just to avoid misunderstanding, it should be remembered that this is a community forum with no “official” relation with Suunto HO or support.
That said, some moderators are testers too, so they helps reporting issues that people expose here and they may know if some bug has already been reported.
Being a tester for a company makes you officially related because you are bound by an employment contract. At least if you speak of real-deal testers. Your argument seems invalid.
So once a bug is reported (by one of the testers) “we” know that Suunto is working on it, it’s somehow implicit.
It’s not a masonic lodge
Please define “we” in your sentence I don’t know if you mean a tester, community mod, mod-tester, these forum users, someone from the masonic lodge, or a pope If you ask me I know nothing (call me Jon Snow).
Then is up to Suunto, based on testing done, to communicate what’s going on. But as you probably know, as a project manager, this is not as easy as it seems.
Well from my experience as a project manager, it is EASIER than it seems, once you have defined a bug in the internal tracking system you respond to the customer that you are investigating and ask for details on how to recreate a bug. Suunto has many social media channels available to communicate anything:
Maybe the impacted units are few (of course many of it are here in the forum because it is seen as a sort of point of contact, even if “officially” it’s not) maybe they are still uncertain of the cause so they prefer to further investigate … we don’t know.
You can get shadowbanned on social media and reporting it there might be hidden from other users.
Some people are going to be critical of Suunto for their approach to Ukraine-Russia war (well since 2019 Suunto is owned by a Chinese capital group).
Others will be critical for lack of an official statement when the software fails but remember there will be always people and employees who defend the company no matter what and no matter the cost.Bye!
-
@freeheeler said in Reboot during activities:
@fecek
@glaucidium-passerinum
this is what I understand:
sending logs means a lot actually. with the correct failure description, time logs sent, account name and time crash happened, it is the best information developers can get to look into what might cause the crash.Invalid logic. You cannot provide any description when sending the logs using the Suuntolink app.
You can provide a “correct failure description” only via contact with customer support.
So you need to do two actions:- Send logs, save the ID
- Contact support and provide failure description.
Above actions can be interchangeable.
Bye
-
-
@fecek said in Reboot during activities:
This is probably my last post on this forum as I am switching to a passive mode.
I really do not want to argue with you guys as I’ve already spent too much time and energy investigating the issue, reporting it via “official” channels (also unofficialy here), and other than that due to a bug I’ve lost 75$ that I would donate to an animal care organization.Being a tester for a company makes you officially related because you are bound by an employment contract. At least if you speak of real-deal testers. Your argument seems invalid.
So once a bug is reported (by one of the testers) “we” know that Suunto is working on it, it’s somehow implicit.
Bye!
The testers are not paid so there is no employment contract and they are not employees. We sign an NDA and that is all. Second, we are testers only, we can certainly provide opinions and send bug reports but we have no say in prioritizing fixes to those bugs or other information. We only know if a bug has been acknowledged officially, that is it.
So you seem to think we know so much more than we do. All of our time here is voluntary as we try to help. Reporting via official channels is important as we do not provide numbers of affected users. -
Brad_Olwin said in Reboot during activities:
So you seem to think we know so much more than we do.
@fecek I approve this, this guy even don’t know which watch he wears, how could you ask him to share more, it’s way too much.
-
@zhang965 said in Reboot during activities:
Brad_Olwin said in Reboot during activities:
So you seem to think we know so much more than we do.
@fecek I approve this, this guy even don’t know which watch he wears, how could you ask him to share more, it’s way too much.
Hey kid, stop it.
The joke is (maybe) funny once, the second time is boring, then it bombs so hard that can even be heard in other galaxies making aliens so unhappy to beg for death.
You start sounding as a sad old doomed comedian that probably forgot too to get his pills.You don’t like him ? We get it. Your problem.
Since this kind of comments are useless, off topic and very probably violate any existing netiquette, it will be deleted from now on.
-
@sartoric said in Reboot during activities:
@zhang965 said in Reboot during activities:
Brad_Olwin said in Reboot during activities:
So you seem to think we know so much more than we do.
@fecek I approve this, this guy even don’t know which watch he wears, how could you ask him to share more, it’s way too much.
Hey kid, stop it.
The joke is (maybe) funny once, the second time is boring, then it bombs so hard that can even be heard in other galaxies making aliens so unhappy to beg for death.
You start sounding as a sad old doomed comedian that probably forgot too to get his pills.You don’t like him ? We get it. Your problem.
Since this kind of comments are useless, off topic and very probably violate any existing netiquette, it will be deleted from now on.
I’m so sad that you consider it was a joke,
It never be a joke, it’s a tragic . -
-
@zhang965 said in Reboot during activities:
I’m so sad that you consider it was a joke,
It never be a joke, it’s a tragic .Well, I’ll live with it
-
@freeheeler said in Reboot during activities:
@zhang965
I support @sartoric 's statement. it is a technical forum and not about bashing on anybody. especially not on supportive and helpful people who spend a lot of time improving the product and give advice to people who seek helpOh so what, scare me to delete my post?
It looks like you guys are already well integrated into a Chinese company.
-
@zhang965
the condescending comments will go on, but I’m not getting involved in that.
useless and off-topic comments reduce the quality of this forum.
I appreciate the high quality of this forum and I wish it remains like that. -
@zhang965 said in Reboot during activities:
Brad_Olwin said in Reboot during activities:
@fecek I approve this, this guy even don’t know which watch he wears, how could you ask him to share more, it’s way too much.
Well at least you know now that all Suunto bugs arise from my ineptitude.
-
So in another post it has been mentioned that people that want to downgrade to the previous stable firmware because of this issue will be helped to downgrade.
-
@chargerunner said in Reboot during activities:
Could you keep us updated after maybe 10 more days?
Issue solved by users himself… No more crashes since downgrading.
100% stabile since 18 days!Big shame on suunto, they missed the chance to provide good support on this topic.
-
@isazi this morning I faced this issue for the first time. I updated to the latest FW few days after it was issued. No problem up to today. Restart occured for the first time today. Activity was Indoor Cycling and sport App used was Drink Reminder. Therefore no GPS. Does it still make sense to provide you the logs?
Thanks! -
@zadow sure, I can ask you some details in PM
-
I am not impacted here, and can’t help in any way, except with silly logic of testing. What about this one :
From my past experience, downgrading seems to reset the watch quite very deep.
What about testing a downgrade AND re-update after, and see…?