Software update 2.18.18 Sept 28 2021
-
Today I did some hill repeats and I want so bad the new ascent/descent algorithm for the S9B.
@Dimitrios-Kanellopoulos do you have any news/hint if we will have it for the S9B?
-
@cosmecosta I am not Dimitrios, but I can say that this is at least being investigated. As already said the sensor is different, and the positioning of the baro holes different (and more prone to bad readings on the baro), so it is a challenge. But I know for sure some people are checking the feasibility, so letâs hope it comes to fruition!
-
@cosmecosta experiment completed, lost 8% of battery (in around 11 hours) just having my S9 on a drawer with everything disabled. This is more than I remember happening in the past where if it left alone it would consume almost nothing. I am reporting it to Suunto.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi said in Software update 2.18.18 Sept 28 2021:
@cosmecosta experiment completed, lost 8% of battery (in around 11 hours) just having my S9 on a drawer with everything disabled. This is more than I remember happening in the past where if it left alone it would consume almost nothing. I am reporting it to Suunto.
Thank you @isazi for the time dedicated!!! I hope Suunto discovers what is happening and fixes it!
BR
-
This post is deleted! -
@cosmecosta said in Software update 2.18.18 Sept 28 2021:
(Important: Same conditions). With the new firmware, and in my case two upgrades in a week, I noticed an increase of
I did not notice any significant difference in battery performance. I notice, however, that the watch is slower when finishing an exercise in saving and, after checking the results, in going back to the main (time) screen. Am I the only one?
Not a big deal, but it is clearly slower than before.
J
-
@cosmecosta @Dimitrios-Kanellopoulos @isazi I have an S9baro running production software and can test this as well. I will fully charge and just let it sit.
-
@isazi I can confirm that this battery draw for an idle watch is happening with my S5. With the 2.18.18 update, the watch battery remaining approximately 10 percentage points burndown in 24 hours ( 100% -> 90% -> 80% etc ) while sitting idle with no disturbances, Bluetooth sync turned on and notifications turned off. This is after two complete battery charge and discharge cycles and is substantially higher than previous SW versions.
-
@bradleyd it is under investigation at Suunto, will be most certainly fixed with the next update. Iâll keep everyone informed if I can.
-
I was discharged by 8% in 24 hours. Battery saving mode. Everything is disabled.
-
@isazi said in Software update 2.18.18 Sept 28 2021:
@cosmecosta experiment completed, lost 8% of battery (in around 11 hours) just having my S9 on a drawer with everything disabled. This is more than I remember happening in the past where if it left alone it would consume almost nothing. I am reporting it to Suunto.
For comparison my watch lay unused for a little over two days and it dropped to 97% off a full charge. Mine seems to have come out of this update relatively unscathed
-
@efejota Yes I experience the same. Much more âsluggishâ reaction on any screen than the previous FW that was as smooth as butter
-
A couple of things here.
The battery drain is on idle mode aka laying on the table
It can be realted to the watchface you use.Regarding sluginess. Only media controlls at teh main watchface (and only there) could have an impact. All other views have not been touched. We dont load all views. 1 view at a time
-
Thanks, @dimitrios-kanellopoulos It is interesting, because when I noticed it, I disabled and experienced the same behavior. Of course, slugginess is quite subjective, but I am pretty sure that the watch is much slower in saving and transitioning to the watch interface after finishing an exercise (not in screen transition during exercise, it works as before then).
I thought it might be linked to (i) new S+ burner app -but I experienced with or without it during the exercise and the results were the same) or (ii) differences in how the watch manages data saving connected to a faster (clearly noticeable) sync process with the App. I am not programmer, so I was just trying to find any possible explanation.
J
-
@dimitrios-kanellopoulos , Very well, my master. However, I need to argue a bit with you
-
regarding battery drain: I noticed battery drain on âS9pâ watchaface. I changed then to Outdoor watchface, but the battry drain was again higher than it used to be on previous FW.
-
regarding responsivity, hmmâŚduring activity recording, watch responses are very good and smooth, just as was before upgrade. right after activity finish and during normal - watch - operation, I noticed that chagne of displays, listing up and down, etc., is not as smooth as it used to be. watch seems to be a bit reluctantâŚ
-
-
@zadow similar experience here for second pointâŚ
-
@efejota
to add something regarding sluggishness: I learned that the lock function (yes, Iâm still a lock addict and I will always beâŚ) has a delay just after starting an exercise. Hence, with my natural learning curve I adjusted my behavior and wait few seconds bevor I hit the lock buttonâŚ
normally you have this two level tone for starting and locking, right?!
today the start tone was very looooong on the low and barely noticeable on the high level⌠similar when I locked the watch⌠never noticed this before but could be a similar root cause as the sluggishness of the screens, no? -
@freeheeler there always was some delay in locking the screen right after the start of an activity. When I changed to the s9p the delay was longer than with the S9. Not sure if it is model or firmware related.
Also the time between pressing âstartâ and seeing the actual data fields is longer than before.
This is just an observation
It doesnât bother me much, I just wait a little bit longer in both cases. -
On an activity yesterday with my phone on a run, I had a mid activity crash of S9B with latest firmware. Had media controls on, was playing music/had media open and just had received some very large text messages on screen. Left the place I was in on my run and changed data screens to the map/breadcrumb screen when it crashed and rebooted. GPS took a long time to reacquire, 2 mins maybe, and then was fine for the rest of run. At end of run watch guidance told me to sync my watch prior to activities with the app for best GPS performance. I sync my watch several times per day so this was not the issue. Seems to be an issue with the GPS chip and it seemed related to the media and/or messages coming in. Is there a way to submit logs for this? Thanks!
-
@northeast_trekker itâs possible that when the watch rebooted the AGPS cache was cleared - hence long first fix and the notification you received.
As for logs - you can send logs from suuntolink with watch connected and share the ID here for debugging.
