@Rayfox remove Gym Timer, select two other SuuntoPlus apps in Track Running, reinstall Gym Timer. My guess is that this will work, as both app slots are already taken by a different app and therefore Gym Timer cannot be selected anymore…

I reverted back to the Athletics watch face (+ soft reset for good measure). Immediately my battery consumption is back to where it was before. It seems that the specific complications may have significant effect on battery usage. I have the following on Athletics: Steps Weekly training duration Callories HR Battery % left. I guess that getting immediate reading of compass, barometer and elevation requires some background work that consumes battery. What I don’t really understand is why this is needed even during activities (where I also observed significant increased battery usage)

FWIW a soft reset after using the chest strap seems to mitigate the issue…

@Horizontal_2 Nice

Is the update schedule for the Suunto Run the same as for the rest of the Suunto range, or does it follow a separate schedule?

ok, then the state I have probably is what you will get with the next update.

@Steven-Hambleton i wish there was more customization for the graph (and everything else)

@2b2bff ahhh thx

@Manuel-Extreme said in Unboxing 90th Anniversary Edition: @zhangschmidt I loved that big “nose”, it felt super extreme outdoor … Me too

@runomatic said in Turn-by-turn guidance on headphones?: @maszop said in Turn-by-turn guidance on headphones?: @runomatic It seems to me that a watch is supposed to HELP the user navigate, not mindlessly guide them like a car sat-nav. That’s what GPX route navigation is all about. Really? Who decides that? I wrote that it was just my opinion: It seems to me…

@Squirrel Sorry, I thought that’s what he meant by “yes it live from sync to sync”.

https://forum.suunto.com/post/187596

@neverhood I’m quite certain it isn’t possible

I had the same issue last year with my Race S after trying to charge it in a hotel room usb plug. It took the watch several attempts to restore the firmware. All I can suggest is to keep trying and hopefully it will finally restore. I’ve haven’t had any issues with the watch since then.

Just registered to let you know that I believe this is an issue with how SDS (the server interfacing w/ the IDE extension and the watch’s protocols ?) is spawned by the Suuntoplus Editor. I’m facing the exact same issue, only on a macbook w/ an M4 Pro chip instead of an M3 Max one. Running the following command starts SDS, which after a few seconds picks up the watch and starts the pairing process. SDS_MACOS_BLE_SCAN=1 ~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/macos/SDSApplicationServer.bin 9801 As a workaround, I tweaked my local version of Suuntoplus Editor to prevent it from starting SDS (via a coding agent, which worked surprisingly well from the first try), and I’m starting it manually in a terminal. The relevant file is ~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/dist/sds.js The watch is then displayed in VSC, and could be loaded with my app without any issue. [image: 1774720045117-0695f3ac-b672-40ca-87a4-3b948013860b-image.png] I hope that this info will let you debug and patch the Suuntoplus Editor As a side note, I was quite happy to see this editor being available free of charge and without any signup process