Software Update 2.30.38 (Race / Vertical / 9 Peak Pro)
-
@isazi so, each workout calculation is far less variable than previously I would imagine, hence why it’s sitting at 59 and a bit the whole time?
-
@The_77 what kind of training are you doing? I did some marathon training with some faster runs, and my VO2max (estimation, this is just an estimation not a measurement) increased. Normally with contant base training it does not move.
-
@isazi oh yeah, I never do those usually, I just do anything I feel like, with some speedwork & races thrown in. Nothing that would improve it in a notable sense. I’d need to consciously do more efforts on the flat and road to see estimated values go up and that’s not for me
-
@Highlands said in Software Update 2.30.38 (Race / Vertical / 9 Peak Pro):
Last night during charging battery, my maps got updated. Forgot to perform a soft reset or at least a simple reboot. Today during my hiking, the Race froze at 2.89 km and at the same time my upper fields on the first screen were missing: vertical speed and altitude. After a couple of minutes the watch got rebooted on its own, 2.87 km from my activity got saved. No idea if the freezing of the watch and the consequent reboot were due to my not rebooting the watch last night. My 9PP has never ever crushed like that. And this was my first time on the Race. Running latest stable software. Sent logs and tomorrow, during working hours, I’ll contact support to inform them about my sent logs.
Today it happened again. This time during a walking activity. At 3.29 km. The activity got saved and watch rebooted. Sent logs 14:08 Helsinki time, now contacting support to let them know about the logs.
-
@Highlands Just managed to get in touch with Suunto support, reported the time of my logs from 26.12 and yesterday. Hopefully, my logs contribute to solving the crashing issue. Got a ticket.
They asked if I did soft/hard reset and if I use any Suunto Plus apps and suggested I uninstall and reinstall my apps. -
Another one with the reworked resources, does it bottom out at 10%? I’ve had a look and can’t find any values below 10% in recent weeks, even when active. Appreciate it might just be me.
-
@The_77 same. mine never drop below 10% but i think this is more logic compared to drop until 0%
-
@The_77 I have seen a similar pattern on my 9PP. I do understand that resources would ‘drop slower’ once arriving close to 0, but still I don’t fully see the point of a bottom at 10%. Maybe a field tester or dev could give some insight, here, about the logic?
-
@Ryan-Carney In the meantime do you get the values race prediction times and lactate thresholds displayed? It doesn’t work for me and support hasn’t been any help so far
-
Another one for resources - they don’t seem to cope with timezone changes very well.
Having hopped back from Germany to the UK, I’ve gained some resources arbitrarily whilst flying according to the graphs.
Now I’m sure I was very relaxed flying but not to gain that amount of resources in such a short period of time.
Anyone else?
-
@The_77 While flying you’re sitting, not moving. Heart probably not very hight.
I would say it’s pretty normal that the algorythm count this as rest time, so ressources gain ? -
@Tieutieu I would have agreed if there was a logical step pattern and green pattern in the path.
In hindsight I should have checked the watch before I undid flight mode to check, and I’m not abroad for a couple of months to test any more unfortunately.
-
@Tieutieu
Nah the rise is way too sharp, and the sharp rises are noted in green.
Besides I noted in planes my HR usually sits a bit high, and Spo2 go down, so definitely not a “really resting” situation where the resource monitor would rise -
-
@Tieutieu sometimes for sure it is just grey as opposed to green, see last night for evidence as I’ve attached the rest of the data/hr.
Still though, TZ functionality I think must have something to do with it. It could have cropped out an hour of gains I suppose.
-
I also noticed this behavior and the resources were reset to zero, that is, they started at 70% when my time zone changed to -3 hours.
-
Addition: I flew with a transfer, the first difference was -3 hours, the second -1 hour. The increase in resources is visible in the screenshot.
-
@Sergei-Ladeishchikov so it seems that there are some issues when changing timezone, I will report it to Suunto.
-
@RaDeck same here. Resources flat at 10% from December 1st.
-
@isazi I can second that having had a flight over 7hrs TZ. I didn’t mind it much though tbh as the data of these days would be somehow ‘bad’ anyways. I also saw that it gives me an average sleep time of the last 6 weeks still very late (it seems to be taking the other TZ I was in for 2 weeks into consideration w. +7 hrs)