@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.

@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here. I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.

@EzioAuditore said in What do you think of the Suunto Spark?: @Brad_Olwin Yes I have the Pro 3. Great in everything except for running. Maybe I should try other ear tips Ang give it a try. But after the open ear headphones I don’t wont to be fully isolated. The Pro 3 have complete transparency mode so there is no isolation at least not in my experience. They also have an adaptive transparency that I find works well especially with noisy environments where background is a bit muted but nearby and abrupt sounds are well transmitted.

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

@gkaempfer Same here

@Brad_Olwin @aiv4r I completely agree with you.

@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!!!

@brave_dave No, fortunately I don’t experience continuous disconnection issues. It only happens in water due to the physical limitations of Bluetooth transmission. When the arm comes out of the water, the connection is restored automatically without any problems. At least with the Vertical 2. Which device are you using?

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.

The watch and phone are connected via Bluetooth, and I’m receiving notifications, but the app shows no connection. I turned Bluetooth off and on on the phone, but it didn’t fix the problem. What else can I do? [image: 1776097483350-a11.jpg]

I don’t know what the battery is. I’ll check. But I was thinking of trying to replace the battery. This morning, during training, the watch lost connection with the heart rate monitor again. So the problem still exists. This takes approximately 30 to 45 seconds and then the connection is re-established.

@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.

@snow said in New firmware 2.53.42: You need to start the activity Ah! Yes… That works. This was incredibly convoluted… Thanks. Hope my bumbling around will help other users. Edit: Everybody is talking about the Menu only accessible from the Map screen itself (the 3 lines/hamburger icon). Edit 2: And it works even without any Route loaded. Great!

@Squirrel The update hasn’t improved the problem with wakefulness detection in sleep tracking either… I’m recording about 30-60 minutes more sleep time each day than I actually slept… it’s such a shame, it skews the resource and recovery statistics… why does Suunto always smooth out wakefulness with light sleep? Has anyone heard if they’ve fixed this problem?

I’ve been using a Polar H10 and Morpheus M7 with both my Race 2 and Vertical 1 for road and trail running and CrossFit and have had none of the issues mentioned here

@Horizontal_2 said in Batterie drain since the new Update: I’ve found something else! I did experience the drain as well. in 3 hours a drain of 3%. The Wireless Network and Discovery were on. That’s a battery killer as well Yep, turning these off definitely helps