@Stefano-M64 said in [Vertical 2, 2.53.42] Map and Navigation features are greatly improved but there are still a lot of old issues and also new bugs introduced in the latest update: Hi, since I found your document very useful, I took the liberty to translated it to english. It’s mostly based on automatized Google Translate function, but I had to correct some parts by myself, hope everything is correct; SUPER THANKS!!!

@Egika I get your point, and yes—if there are actual ROM limitations on the V1, then obviously that’s a valid constraint. Navigation improvements like these have been on the table for quite some time, and seeing them finally arrive—but only for newer (AMOLED) models—naturally raises some questions. Also, when competitors are managing to deliver similar or even more advanced navigation features on MIP devices, it makes it harder to fully accept that this is purely a hardware limitation, rather than at least partially a product segmentation decision. And to be fair, a company like Suunto doesn’t just “run into” ROM limitations overnight. These constraints are typically known and planned from the design stage of each model. So it’s hard to ignore the possibility that the limits of the V1 were already defined from the beginning—and that now we’re simply at the point where those limits are being used to justify pushing users toward newer AMOLED models. I do appreciate that Suunto mentioned ongoing support for the V1, but the lack of what will actually be possible going forward doesn’t exactly inspire confidence it’s not just about this update—it’s about how much headroom the V1 really has left, and whether users can expect meaningful improvements or just maintenance updates.

@Audaxjoe yep they’re headphones, so for calls and music, you can just connect to your phone and your good to go

@aiv4r @elbee Yeah, even though I would advocate to also include segments (fun stats to have) on the page as its own metric, I would be fine with how it is now if it actually updates Because now it is kind of flawed, here is an example: I participated at a 10km race, clocked in at 44:48 (official result time). The clock logs 9,65km at 44:59, which is ok (either the race track was not exact or the gps struggled in the urban environment but actually both). Now this did not update the 10 km personal best (which can be discussed if it should have). The distance was off by 3.5% and did not get registered. However, for other activities like the personal best for the half marathon it displays an activity that clocked in at 20 km and not 21 km. So the distance was off by 5.2% and still got registered. So the threshold appears to be set differently (tighter tolerance for shorter distances), That is why segments make sense as such a threshold would not be needed for anything that is over the desired distance of interest and the distance/time would be right. Then when I manually set the 9,65km to 10km it got registered as a personal best. But the run yesterday that clocked in at exactly 10.0 km did not update.

1.0.16(93) appears to be working for me now. Thanks! I’ll test it on a run tomorrow probably.

@Egika Ahh ok. Many thx

@BrunoH said in Charging of battery: One internet trick was to put the device in the freezer for 30 mins Just be careful and do not charge while the battery temperature is below 0°C (32°F). From https://www.batteryuniversity.com/article/bu-410-charging-at-high-and-low-temperatures/ Many battery users are unaware that consumer-grade lithium-ion batteries cannot be charged below 0°C (32°F). Although the pack appears to be charging normally, plating of metallic lithium occurs on the anode during a sub-freezing charge that leads to a permanent degradation in performance and safety.

@pavel.samokha Ah, thanks—I had to go into the PDF to find it, but there it was!

Unlike the first glance the Vertical (1) and the Race (1) seem to have different internals apart from the display. Or maybe the display itself need to be addressed differently than the AMOLED variant. However, they couldn’t make it a stable release on time, so they postponed it for the Vertical and only relased it for the other watches. But Suunto is still working on it… And yes, there are some features that are exclusive to the Race 2 and Vertical 2, as they have newer, faster chipsets…

@Michał said in Downloading map takes a very long time: Since the last software update (version 2.53.42), it takes a very long time to download the map. My configuration is the same: the watch is plugged into the charger and lies 20 cm from the router. A 200 MB map takes 5 hours to download. The WiFi connection sometimes breaks, so the download needs a couple of restarts. The process is always the same: the selected map downloads up to ~18% in 2 hours, then the connection crashes. A Swatch soft reset is needed. Maps always take a long time to download, but it’s now awful. odd, mine is ~190MB and it took barely 20min or so

@borgelkranz said in Suunto and Concept 2 indoor rowing: @off242 what I can add: as of late, SmartRow does directly connect to EXR. What I learned in that context: there are different versions of the SmartRow pulley. The old, silver one and the new, black one. They seem to differ slightly with respect to connection. I own the silver one and EXR had to provide a bug fix for it to connect. The ability of EXR to connect to the SmartRow pulley directly is a fairly new development, and happened due to collaboration between the two companies. For those new to this, previously the only way to work was by a “broadcast” method, where the SmartRow pulley connected to the SmartRow app on one device (like an iPhone) then the SR app “broadcast” to EXR on a second device (e.g. iPad or Apple TV). You’re correct that the original silver metal pulley behaves a bit different from later black plastic pulleys. Both transmit in SmartRow’s own format as I understand with subtle differences. The “broadcast” method is either FTMS or very close to it. Some people disliked this method due to requiring two devices; additionally, the broadcast method adds a slight delay, so EXR is about a half-stroke “behind” the SR app. The new “direct connection” improves things in most regards, but has the negative consequence that sessions are no longer written to the SmartRow online logbook. EXR can write session data to the Concept2 logbook for those people, but not yet to the SR one. Additionally, SmartRow also has a “power handle” meant for air-resistance rowers like the Concept2. People who happened to get a cheaper air-resistance machine with poor metrics can get this handle to get more accurate data. However, I suspect the cost of a cheaper rower and the SmartRow handle would be close enough to the Concept2 one might just get that anyway. The SmartRow handle also works with the Concept2, and while C2 people don’t necessarily need better data (given C2 is the standard) the handle also has four buttons, each with two top/bottom selections which can be used to do things like control a music player and perhaps eventually may have game effects in EXR (like the Zwift Play buttons in the cycling world). SmartRow is working on a “handle version” for WaterRower to give those media controls over there as well, and that version of the handle has dual bluetooth support, which allows one to have that direct EXR connection as well as a second connection to SmartRow app for those who want consistent logbook records. I believe the handle versions qualify as FTMS based on SmartRow’s web site.

@gkaempfer Same here

I can confirm now : extra battery drain on daily use has been fixed

The glitch is slightly more extended. I have to repeating alarms. One for mo, tu, we, th on 6:30 and one on fr on 7:00 (thank you Suunto developers for more fine grained alarm settings!!) This morning (tuesday), while I was dismissing morning report, I noticed morning report showed the alarm for 7:00. Have to say, I rather have Suunto working on an option to disable morning report all together than fix this bug. There is no info on morning report that I need to know first thing in the morning and now it is annoying to dismiss this useless screen every day.

I have the same problem for 7 days. It is not possibile doing neither soft nor hard reset. No answer from Suunto Help Desk. Really disappointed. The only thing i can do is buying a new Watch

I was thinking this was about the titanium Race 2 because It seems you all are comparing the Race 2 titanium with the Vertical 2 titanium. But the thing is I have the Race 2 steel and I’m seeing a little discrepancy of what I have recorded with Garmin. But my watch is very new (2 days) and I need much further testing. There’s also something very strange with the Race 2 (at this very new moment for now). When I import a GPX track (downloaded from Garmin Connect) into Komoot to have the turn-by-turn indications while navigating with the Race 2, is like the indications are a bit later than they should (just some few seconds). When there’s a roundabout, or a turn it seems the watch pop-ups the remaining indication a bit later or even after the turn or roundabout. I need more testing but I’m posting this because I don’t know if it can be related with the issue you are posting here. And the thing is that those tracks are working fine in Garmin and other brands. Or perhaps does not have sense at all, but using the same track for both the Race 2 and the Vertical 2, perhaps there’s a mechanism to see if there’s any delay with the GNSS of the Race 2. I’d be interesting if someone could test the navigation with the same track and indications with the Race 2 and the Vertical 2 to see if there are GNSS discrepancies.

@2b2bff you perfectly right! I’ve checked and I had zonesense for trail mode. Thanks a lot! Instead yesterday night the ohr does not work and this cause a bad recording info for the sleeping data. I think it’s the first time after a lot of correct night!I would like to add the usually the data ara incredible align with the real info (I’m a father and when my son wake up in the night and I bring him in parents bed, the watch are able to capture this awake time)