Software update 2.30.32
-
@Olaf-Gottschalk did the ohr work during when the step counter was stuck ?.
-
@Dimitrios-Kanellopoulos @Brad_Olwin
Hi, once more how this other bug ctl/atl/tsb/tss sync worked here in Finland between yesterday and today (text below is exactly the same I have written before, because the watch and the app works like this every day, with last software and the new one, tested once more, I have also pictures / screenshots of this happening if someone wants, also I can send you the logs of needed)
Yesterday evening: watch and app ctl, atl, tsb all synced and all good
Just after midnight and synced with app: new numbers for todays ctl, atl and tsb. All synced perfectly with the watch and the app.
This morning after synced with the app: ctl, atl, tsb are not synced anymore. On the app still todays numbers like it should. On the watch back to yesterdays numbers. And those wont be corrected on the watch before powering off and back on. After that works fine for today and also possible new tss scores add fine. If the power off and on is not done, also the new tss scores don’t show up.
I use ios, I don’t have multiple watches.
So once more I ask: is this sync problem also reported / someone is doing something finding a solution for this? Or do you even think this is a problem? Thank you
-
@SuuntoR Im my case (location Slovenia, it that matters at all) TSB, CTL, ATL are not syncing properly with the app. Values are different, not much, but they differ! I belive the correct one are on the watch itself. It’s a bug in my case!
-
@ppresing OT: Is that the Mangart in the background of your profile picture?
-
@robis Oh Yeeees!
-
@ppresing been there last year, made a ride on Visoska Ponca, Jalovec, Mangart. Awesome place!!!
-
@SuuntoR said in Software update 2.30.32:
@Dimitrios-Kanellopoulos @Brad_Olwin
So once more I ask: is this sync problem also reported / someone is doing something finding a solution for this? Or do you even think this is a problem? Thank youIs this Problem reported and will be solved next 2 years?
-
@GiPFELKiND next 3 years for sure.
-
I also have differences in ATL and CTL between watch and app.
Not sure if this is new to Suunto, but filed a report just this morning. -
@robis You mean Mounteneering, you can’t ride to Jalovec, Visoka ponca, Mangart. Those are pretty dangerous peaks even for climbing.
-
@Egika said in Software update 2.30.32:
I also have differences in ATL and CTL between watch and app.
Not sure if this is new to Suunto, but filed a report just this morning.Thank you so much
️ for my watch at least, it has been like this since the first launch of the watch, so with the previous and also the latest software. I hope and i’m quite positive it will be fixed, it does not sound that complicated problem. And after that together with other little improvements on new software, rock on 
oh boy it was a nice screen / maps on the watch on yesterdays cross country skiing in the night time -
Yesterday I did a hard reset of my S9PP to test if this would make a difference regarding the training stats problem. I know, it’s a different watch, but with the Race I have the exact same problem.
After the hard reset, training stats were correct. Then I did a workout and after the sync the stats were sill correct. Today I woke up at 7:30, synced the watch multiple times, and all training stats displayed yesterday’s values. After breakfast I did a 2h cross country skiing session in the most beautiful winter wonderland one can think of, synced multiple times the watch afterwards, but the training stats still display yesterdays values. And today’s TSS are missing in the training widget (it looks like as if I haven’t done a workout., although in the training volume chart the workout is there). This is exactly the same as my Race behaves and exactly as it has been before the firmware update.
I also very briefly had the Vertical with the new firmware update (sold it in the meantime). There I also had the exact same behaviour. Three watches, same bug. I am in Austria, by the way. I didn’t check the values directly after midnight, only in the morning.
I am using the latest Suunto beta app on iOS. I will install App Store version, maybe this makes a difference. Should we send logs? If yes, when? In the morning after sync and also directly after a workout has been synced?
-
Exactly the same behaviour with my Race and also that thing with those tss scores not showing up on the watch after the watch other metrics have “stucked”.
I’m using the normal appstore version of Suunto app, but no difference…
-
@SuuntoR Since the app should be the single source of truth, I thought, maybe the problem is the beta app. Ok, then I don’t think there’s anything left we users can do. Only sending logs if needed, hoping that the devs find a quick fix.
-
-
@gizmo hmmm - mine tracks very well with my chest monitor on a different device. maybe a loose band? or something else?
-
@Brad_Olwin said in Software update 2.30.32:
@wmichi Well y’all will be happy to hear that my CTL but not TSB is in sync this morning. I will add my logs to @Egika bug report. Ok, more complicated, the only wrong value is in the Race watch face mini-widget. The values in the main widgets are correct.
Ok, that sounds weird. So your numbers between watch face mini widget and for example if you go (on the watch) under the tss widget and there scroll to summary where are all those ctl/atl/tsb numbers, they (or that tsb) dont match, but they are same as the app? Never happened here, just between watch and app. Numbers on a watch have been similar, no matter where viewed.
-
@SuuntoR seems like Suunto need to do better testing before releasing new firmware. Mine threshold values and run estimat are also gone after the update. Done three runs and their not back.
-
@SuuntoR yes, that’s correct. Under the TSS widget (scroll to the bottom) the values match, to those in app. The specific TSB and CTL values on watch widgets NO!
-
@ppresing I synced my Vertical after I had non-matching values in the watch mini widgets for the Race and had the same issue, mini widgets did not match. Syncing multiple times did not fix this. However, a force restart of the Suunto App fixed the values. I am on iOS. Can someone else try to force restart the app, not the iPhone and see what happens?
Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing
