Constantin: monitor effort drift against your session average

[Łukasz Szmigiel]

@Lazyjones I’m working on a new version with split templates. Three templates instead of one. Let’s see if hardware will like it more.

[Łukasz Szmigiel]

The new version is in - 1.42 which should be easier on the UI processing. Happy testing!

[Speed Man]

@Łukasz-Szmigiel Your application is truly useful. I hope Suunto will support you on the hardware side as well — your work deserves to be integrated into the ecosystem.

[Stavrogin]

Today my V2 crashed. Only running Constanin and a workout. When I tried to go through the pages the watch was fun until I hit the button again to go to Constanin. Rather than go to the page it froze for about 20 seconds followed by a restart.

Sorry I would love to use this, but crashing makes me sad. Nothing worse than crashing watches mid-workout.

[Łukasz Szmigiel]

@Stavrogin I’m sorry to hear that. The real issue is that I’m unable to debug this app on V2 as the only way to do so would be to have access to real hardware and logs and I only have S9PP and Race S. I suspect there’s something wrong in current V2 firmware as it doesn’t crash on older watches - or I haven’t experienced it yet.

What activity did you try it on? Did you have other features turned on like guides or routes.

[Stavrogin]

@Łukasz-Szmigiel Thanks for reaching out.
I was doing a Trail Run with a workout Guide on. Nothing else. No Routes. I had a Polar HRM attached.

To your point the HexHunter much the same thing. It was a crasher for me.

[Łukasz Szmigiel]

@Stavrogin thanks for extra info. A guide is de facto an S+ app. So you had Constantin + Guide (2 apps). But it shouldn’t crash the watch nevertheless. Suunto watches are pretty clever and if they see that there are no resources left, they will kill non essential apps, it’s hard to crash the watch and the latest version is simplified.

I’ll do some more digging into optimising the issue but the problem is that on S9PP when I’m using navigation and 2 S+ apps, current version doesn’t hit the limit. I’m surprised that the issues happen on V2 which is newer hardware.

Perhaps @suuntopartnerteam can shed some light on it?

But just to clarify - it didn’t crash at the beginning of the run but later, when you were cycling the screens, right?

[Stavrogin]

@Łukasz-Szmigiel That is correct. The freeze and reboot was triggered by cycling through screens. I feel like that was what happened with the HexHunter app as well.

[Łukasz Szmigiel]

@Stavrogin it seems to me that the UI is still too heavy and, perhaps, tries to do all the painting at once after the screen cycle. I’ll let you know after I release a new version with delayed rendering and we’ll see if it helps.

[Łukasz Szmigiel]

@Stavrogin new version should be available now in SA, you may want to give it a try. The code is ~25% smaller in general and there are some additional optimizations added to how the UI drawing is being handled. If that still crashes - I’m afraid I can’t do much without the support from Suunto or logs from V2 running the app

[Stavrogin]

@Łukasz-Szmigiel thanks and I will give it a try