Suunto 9 Peak Pro 2.44.48 Beta Test
-
@Francesco-Pagano oh nooooo - now I tried to pair it and it says pairng failed twice.
I will try to remove the “old” watch in the app and re-pair it again. -
okay - removed the watch from blutooth devices (iOS) traid pairing again - failed.
Now I choose not to pair in the watch and will check if I can get it working later. -
Okay - now it is paired again. Did turn Bluetooth off and on again and updated the suunto app from 3.1.0 to 3.1.1
-
Ooooh - what a mess. Seems like data from the suunto account is there like TSS but everyting else is on factory reset now.
Anyting I should provide to suunto???
Did just dl. the beta as usual and started the update from the watch at 50% bat.
After the install finished it ask me about gender, weight, height and to pair it as a new watch. -
Firmware downloaded and installed successfully.
For doubt’s sake, I’ve redefined the HR zones but they were maintained during the installation process, as well as all the other personal data.
With respect to the new recovery state widget, I’ve found that the suggestion message reported in the widget second screen does not fit the dedicated window, so I’m able to read the body of the message but I’m not able to read the top and bottom part.
Sensors re-paired smoothly.
-
Strange. Nothing got reset on my watch. The update went smooth - all personal data remained untouched, as well as custom sports modes.
S9PP 2.44.48 beta
-
P pavel.samokha pinned this topic
-
@pavel.samokha I’d love to test it on my S9PP but how can I avoid my watch factory resetting like it happened on my SV last Friday? Tomorrow I have a long hiking in the higher mountains and tonight no free time to tinker around with it.
-
@Highlands I bet nothing at all
so leave it as it is.
All personalized sport modes are gone, hr zones, pace zones, sleep tracking and so on too and I get a guide on how to start my first training.Watchface and complications where kept. Dual Watch time not.
Custom sportmodes gone but SuuntoPlus Apps in Sportmodes still selected.So I belive it is not predictable why this is happening at the moment.
Would be great if more data would be kept in the suunto account instead of the watch only.
I don’t could cope with a lost watch face config but hr-zones and so on that really hurts.
Log book is empty - glad that I did do a sync before.Never had this happen to me at another suunto (beta) update.
-
@Ecki-D. You’re right. I won’t risk it. I went through that mess last Friday with my SV. No desire to experience it twice in 8 days.
-
@Łukasz-Szmigiel Lucky You
-
Got everything sorted in between bei using my data from runalyze and brain,
but whats weird I get a notification beep sometimes but there is no notification. -
@Ecki-D. Phantom notifications have been a thing with this update. A soft reset might help.
Have you double checked your running pace zones? Not sure if you’ve followed, but many have reported that they were set to generic paces after the update and thus affecting TSS scores and activity categorization.
-
Just installed. Also had training zones reset, exactly the same as on my Vertical.
Another oddity is that “Special HR zones for running” was turned ON after the update. I’ve always had this set OFF. However, “Special HR zones for cycling” was turned OFF. And I had this set to ON. So they all flipped.
I’m also wondering if, for those that had running pace zones reset, we all got the same paces? I forgot to write down what mine said after the update, but they were very slow compared to what I had them at. Something like 7’10/km for Zone 5 minimum rather than the 4’30/km I had it set to.
-
@duffman19 Mine was “factory” reset by install. So of course I had to change the pace zones, hr zones, sleep tracking and on and on. I did not write down the defaults but you might be correct with 7:10
-
@Ecki-D. I might be mistaken about the 7’10. Now I’m thinking it was something like 6’30/km Z5 min, which would match what @sky-runner saw on his post here at 10’30/mi. Really wish I would have written them down!
If anyone sees this before updating, could you let us know what your running pace zones reset to, if they reset?
-
I’ve recorded two activities (one walk, one cycling) and no major issues other than training zone reset. 9PP is operating the same as my Vertical. Paired multiple HR sensors without issue. GNSS traces and distances look excellent. iOS notifications are finally more visible! And the climb guidance zoom worked well on a route with waypoints.
One remaining gripe is that the zoom function on the breadcrumb/route page remains unchanged. I really wish this functioned liked the Vertical, with the top button operating the zoom (short push to zoom in, long push to zoom out). The current implementation makes it impossible to scroll backwards through the data fields since a long press of the middle button brings up the +/- icons. The zoom function on the altitude profile works the new way, so can we please have this on the breadcrumb page?
Also, the zoom +/- icons are not visible if the theme is set to “Light.” Just looks like their color is still set to white instead of black.
Vertical Ti / S9PP Ti / S9P Ti
-
After installation only pace zone got corrupted. I had an easy 5 km run with Suunto trainer. So far so good. thanks for the beta version
-
Beta Update just installed on my wife’s S9pp.
Went perfectly fine, no data lost or reset -
Feedback is kinda same as everyone else initially. Lost all my zones, cycling zones turned off entirely, but else kept the rest.
Also new recovery widget has some awful colour choices, unless it’s with the system highlights. Unreadable on one of them.
Sleep widget getting the update for average is nice, but also needs scaling properly on the watch, currently it’s hard to see anything.
Oh and one more thing, why is it the default to sync the resources from the app to watch after an update, rather than resetting it to 70%. Renders the day moot.
-
Have you been able to check if the touchscreen function is fully operational on the navigation screen (breadcrumbs)?
There was a bug in the last update that caused me to revert to a previous software version. I hope it’s been fixed.
