Rolling out 3.19.18
-
A minor update but everything counts
Improved the accuracy of sleep monitoring
Fixed the issue of excessive battery power consumption in some special scenarios
The stability of the system has been enhanced -
@Hari-Seldon said in Rolling out 3.19.18:
Fixed the issue of excessive battery power consumption in some special scenarios
it seems that the daily battery consumption is lower
-
Hi,
after the update I am facing a lot of chest strap disconnection/connection messages while running. However when I sync with SA the HR data is all there.I forgot to mention that this happens when listening to music, sorry!
Anybody else?
-
@Hari-Seldon, I have a Polar H9 chest strap connected to my Run, and I haven’t had a single disconnection during several exercises.
-
@Oskari-Forsblom yes, sorry I forgot to mention this happens when listening to music at the same time
-
@Hari-Seldon said in Rolling out 3.19.18:
However when I sync with SA the HR data is all there
I apologize again for returning to this topic, but I think I understand what happened. I knew that when using a chest strap, it takes precedence over the oHR, but (to my surprise) if, for whatever reason, it stops working, the oHR is reused. In addition, a flashing heart icon appears to alert me to this. This explains why I still had data even when the chest strap kept disconnecting. I was not aware of this feature (always wondered why the oHR continued to function even when the chest strap was used)
This could also explain why the memory function is not implemented on the watch. -
@Hari-Seldon yes, on Suunto Run, even when you’re using an external hr belt, if you look under the watch during the workout, you’d notice OHR is always on, as you already know, Suunto Run does switch automatically to OHR if belt stops recording, this is done to avoid losing hr data, this behavior happens only on Suunto Run by design at the moment.
Coming back your issue, I don’t listen to music while running, at least not stored directly on the watch.
Is your issue while playing music from watch internal memory? -
Hi @herlas thanks for the confirmation. Regarding the connection problem, yes, I listen to music from the watch and the problem is exacerbated when using a chest strap (Suunto Smart Sensor, if that matters)
-
@Hari-Seldon okay I’ll try to reproduce the issue on my side.
-
@herlas while we are on the subject (I assume you are a field tester) I would also like to point out that I sometimes have to do a soft reset because the music player will not start (as the stored tracks were not recognized. I use flac since I read on the forum it’s a supported format)
TIA
-
@Hari-Seldon said in Rolling out 3.19.18:
I use flac since I read on the forum it’s a supported format
I was already having problems with FLAC before the update; some songs just didn’t seem to be there in the watch. MP3 always worked, but I haven’t tested it extensively since the last update.
@Hari-Seldon said in Rolling out 3.19.18:
always wondered why the oHR continued to function even when the chest strap was used
I’ve had problems connecting the Smart Sensor from the beginning (for a month now). It’s been interrupting once or twice a day. The “disconnect” message appears, sometimes immediately followed by a second “connect” message; sometimes I have to manually reconnect in the options.
But this problem seems to have disappeared, or at least the messages about it. However, the problems with HR recording have become more severe. @herlas thinks it seems to be a defect in the sensor/strap. But at least the first part of my problem also has something to do with the watch: Details here: https://forum.suunto.com/post/171315
-
@Yves-Jenni said in Rolling out 3.19.18:
some songs just didn’t seem to be there in the watch. MP3 always worked,
I haven’t tried it with MP3s yet, but if it happens to you with FLAC files too, there may be a potential issue with this format. Thanks for poininting that out.
I’ve had problems connecting the Smart Sensor from the beginning (for a month now). It’s been interrupting once or twice a day. The “disconnect” message appears, sometimes immediately followed by a second “connect” message; sometimes I have to manually reconnect in the options
After contacting support because the watch had restarted and lost activity, I was advised to perform a factory reset, and since then I have had no further issues with any chest strap. It reappeared after the last update but only when I listen to music. So there could be something weird with multiple BT connections…
-
@Hari-Seldon said in Rolling out 3.19.18:
So there could be something weird with multiple BT connections…
This is a potential weak point. I couldn’t say if I’ve connected both at the same time. Recently, I’ve been listening more Audible on my smartphone than music. But I’ll test it out to see if it works for me.
The factory reset is the standard advice from every support team. But it rarely helps, unless you’re lucky
One more note on the audio format: I’ve come to the conclusion that FLAC doesn’t make sense for such devices.
- The format requires more resources than MP3 (maybe not much).
- The better sound won’t be heard with open-ear headphones.
-
@Yves-Jenni @Hari-Seldon
Afaik the BLE connection from watch to ear phones is not using a lossless codec but something on a AAC level. So it would not make sense to use FLAC unless you only have the music in this format only. -
@Gunnar said in Rolling out 3.19.18:
it would not make sense to use FLAC unless you only have the music in this format only.
Being an audiophile and a bit lazy… I am already converting tracks via ffmpeg to see if that solves my problem. I will try it out in the next few days.
-
@Hari-Seldon said in Rolling out 3.19.18:
Improved the accuracy of sleep monitoring
I have the impression that it didn’t get better with the sleep recording. Before the update, too little was recorded, now too much.
What about you?
I still wish that Suunto would allow a correction in the app or the import from another source: https://forum.suunto.com/post/170029
Here is an example. Yesterday I had done something at the desk in the evening, so relaxed that it was recorded as a nap. I saw that in the watch when I went to bed almost an hour later. In the morning, I see that the nap was then counted on sleep, with almost an hour of waking up
The nap had almost reached the time window at the set bedtime. I have now made it a little closer again.
-
@Yves-Jenni Frankly, I don’t look at it (I mean I totally ignore the sleep stages), it’s only enabled to record HRV, but I must say that the recorded sleep intervals are correctly detected more often than in the past, and the same goes for naps. That said, the above recording is rather bizarre, and I suggest you report it via the app.
-
@Hari-Seldon said in Rolling out 3.19.18:
I suggest you report it via the app.
I want to see how it works
Sleep itself wouldn’t be important to me if I didn’t assume it’s a key factor in calculating recovery and progress. Or am I wrong?
I brought up the topic once, but it didn’t get any response: https://forum.suunto.com/topic/13369/recovery-data-sleep-monitoring-how-do-you-handle-it?_=1754582587888
But yes, HRV is of course an important indicator.
-
@Hari-Seldon said in Rolling out 3.19.18:
Hi,
after the update I am facing a lot of chest strap disconnection/connection messages while running. However when I sync with SA the HR data is all there.I forgot to mention that this happens when listening to music, sorry!
Anybody else?
I tried again today and found the opposite behavior: no disconnections with the chest strap, numerous disconnections with the earphones
. It’s not a problem, of course, listening to music while running is not my priority, but it’s something that I think needs to be investigated further -
@Yves-Jenni said in Rolling out 3.19.18:
I brought up the topic once, but it didn’t get any response
I’ve never understood if the blog is read in any way by support or anyone else. I just hope that some mod or field tester forwards it to the developers; in my opinion it is better if you also send feedback via app, so that there is a better chance that reports are not lost in the void.
