@TrailEyes To me it seems weird they both messed up the same way. I also didn’t see either as overly defensive, and not sure what “music” there is to face. I know the videos of DesFit better, and he doesn’t seem the type to throw someone else under the bus unwarranted; I’d see him more as easily saying he made an error if he thought it was an honest mistake. It really doesn’t matter though if there was a late change or not, as we know the situation now. It would minorly explain the question of “why you’d buy a 64GB over a 4GB model” though if the 4GB wasn’t originally intended for maps. However, I think 64GB is also explained well enough by those who want significant maps and/or significant downloaded music files.

@Inge-Nallsson said: I asked the Google Neural Network. Just typed in “SHRM2” and got as a starting paragraph: “The Suunto Smart Heart Rate Belt 2 (SHRM2) is an advanced ECG heart rate monitor featuring Bluetooth 5.4 connectivity and ZoneSense optimization, with pre-orders opening on September 8, 2026, and global availability starting September 15, 2026, at a recommended retail price of AUD 249.” Don’t know where the data comes from (global availability). from here: https://www.prnewswire.com/apac/news-releases/suunto-run-2-a-35-g-running-watch-built-for-road-running-and-marathon-training-302871116.html

Seems to be working now Thanks everyone

@johann.fuehrer for me the soft reset after charging doesn’t help with battery run time. But it certainly helps with Resources. Will keep doing it…

@elbee said: bluetooth connection problem and battery drain So not only me? thats why I am here. Its going down so fast! I have to charge my watch every 7 days, before was like 10-12 days… Can i come back with update like 2-3 back?

@Tami999 said: As I used Vertical Ti in past I enjoyed more Titanium more than Solar:D That was my point. Titanium look is so great.

@elbee said: 6 crashes in 2 years is way too much. I only had 1 in just over one and a halve year. Obviously it happened in a race. Once in a race, within weeks of having the watch. Another two or three times during tracking and two times on holiday while charging and once while sleeping that I described in another topic…

@sky-runner how frustrating. Reliability is the number item no matter what. If you are in the mountains and the watch fails, its very frustrating and problematic imo. Sure, important to always have a back up gps unit with you but still. I haven’t had any issues with my watches during long outings but it does concern me.

@isazi ah, didn’t know thanks!

@isazi Oh okay, so Marathon mode is basically a preset custom sport mode consisting of standard sport settings from the flagships (or old OS if that phrasing is preferred) by the sound of it? Edit: tested it out and it is possible to add the distance progress as well, as you mentioned less fancy. [image: g8bZfgN_d.webp?maxwidth=1520&fidelity=grand] But I assume this is the way it looks on V2 as well then. But with the V2 you have the ability to add a ETA. Is that ETA bound to route end point or can it be set to target distance as well?

@johann.fuehrer right. New we start over at the beginning: The energy saving display only cannot display more data than what is available. It cannot be configured. To show the needed data, it is totally possibly to use the full wake mode. One has to decide between energy saving or a lot of information. I was now referring to the statement that not a single watch face could display the required data.

We are working actively on this. Good morning to all.

@mcmahonsport said: This morning the Suunto app on my phone automatically updated itself to 6.13.6 (stable release, not beta [edit: it is beta: now removed]). The exact same pairing loop came back immediately: Phone confirms the Ambit3 Peak is paired App then starts the pairing process again Infinite loop Device details for reference: Phone: Lenovo P2 Android version: 14 Desktop OS: Manjaro Linux (so SuuntoLink + USB is not an option) I have once again uninstalled 6.13.6 and sideloaded 6.7.12. Pairing works again and the phone is currently re-synchronising the same 35 activities (took about 40 minutes this time). This confirms that the regression is still present in the current public 6.13.6 build. Auto-update has overridden the previous working version, so anyone who rolled back will eventually be forced back into the broken state unless they keep auto-update disabled. Please treat this as a confirmed, reproducible issue with Ambit3 Peak on Android 14. I sideloaded to 6.7.x and then I now disabled the auto-update so that it won’t be updated until it is (hopefully) fixed.

@VoiGAS I don’t think we’ll be able to get it onto the watch, but it would be enough to see it in the app.

@Sascha-Domres If you sync with the mobile first, the GPS satellite data should be updated as well. The you wait until the arrow goes green, that should work also.

Why Suunto, why… Today, a new bug with the watch face. You didn’t correct the previous bugs with the watch face either, and today a new bug appeared on the watch. And this morning I didn’t get the morning report again. I didn’t get the morning report yesterday either.

Is this issue solved? I did three dives with the new firmware and until now I did not see any Mandatory Gas Time Alarms in the beginning of the dive…