Software update 2.11.38 for S5/S9
-
@Łukasz-Szmigiel said in Software update 2.11.38 for S5/S9:
@cosmecosta but you have the belt paired, right?
Yes, you are right. But with previous firmware and the SSU I never had problems with the polar H10 belt. Besides is like a cyclic problem, today I did the soft reset and probably I’ll be issues free for more than a month…
-
@Dimitrios-Kanellopoulos said in Software update 2.11.38 for S5/S9:
@cosmecosta I never heard of this.
I will wait until it happens again and then I’ll do a hard reset if the new firmware is not out yet.
-
@cosmecosta sure, I’m just thinking that maybe the bug is related to hr belt, bt functions, etc. as I haven’t had any problems with current firmware prior to using the belt.
-
Also - since the bt connectivity is broken due to this bug (watch won’t pair with belt or phone) it may be related.
-
Could it be memory? Eg something like disk full lagging the watch ?
Perhaps a delete some old activities helps ?
-
@Łukasz-Szmigiel said in Software update 2.11.38 for S5/S9:
Also - since the bt connectivity is broken due to this bug (watch won’t pair with belt or phone) it may be related.
Yes, this sound quite plausible.
-
@Dimitrios-Kanellopoulos is there an easy way to wipe the diary from the watch without manually removing the activities one by one? Apart from hard reset that is
-
@Łukasz-Szmigiel nope. Unfortunately.
-
@Dimitrios-Kanellopoulos bonkers. Any way to test the memory availability? Send debug data from watch to Suunto, etc.?
-
@Dimitrios-Kanellopoulos also - if it was a full memory issue shouldn’t the bug occur every time after reaching the critical point? The diary is getting bigger and bigger and yet after soft reset it gets back to normal for some time (and several activities).
-
@Dimitrios-Kanellopoulos said in Software update 2.11.38 for S5/S9:
Could it be memory? Eg something like disk full lagging the watch ?
Perhaps a delete some old activities helps ?
The problem is that you do not know when it is going to happen, the other times I noticed because I miss the outer ring in the watchface and another checking the AGPS info, and today after the run.
Related to what @Łukasz-Szmigiel comments, I couldn’t connect the watch with SA and only after the softreset I could pass the activity to SA, not before and nothing was deleted, so I have the same logbook. Besides, the watch memory is cyclic, isn’t it? It deletes the older activities to allow space to the new ones. Maybe it gets stuck at some point and the soft reset forces the correct working.
-
@cosmecosta right. Also I’ve noticed the bug on my watch after picking it up from shelf in the morning - not right after an activity or before. And I believe everything was OK day before. So it happened without any activity - perhaps it was trying to connect to phone (Android) or doing some background maintenance, no idea.
I’ve also checked my diary - the oldest activity I can see is from April so it must be cyclic.