Quick update after a third battery test. This time I re-enabled both 24/7 heart rate and sleep tracking, performed a soft reset, and kept the watch in airplane mode to see whether the Bluetooth connection / phone notifications could be responsible for the high background drain. Settings: 24/7 HR: ON Sleep tracking: ON Airplane mode: ON Medium brightness Always-on display: OFF Raise to wake: Full wake Discovery mode: OFF From October 25 at 18:00 (100%) to October 30 at 19:00 (29%), the watch consumed 71% in 121 hours. [image: 1793435155481-5747.png] That works out to approximately 14.1% per day, or around 7.1 days of theoretical battery life. So airplane mode did improve the result compared with my previous tests (~17–18% per day), but the background consumption still seems quite high to me. For comparison, my three tests so far are: HR + sleep ON, normal connectivity: ~18.1%/day (~5.5 days) HR + sleep OFF, normal connectivity: ~17.2%/day (~5.8 days) HR + sleep ON, airplane mode: ~14.1%/day (~7.1 days) This also seems to confirm that 24/7 HR and sleep tracking are not the main cause, since disabling them made almost no difference. At 29% on October 30 at 19:00, I disabled airplane mode and then recorded a 1-hour run. The battery was at 16% the following morning. I therefore excluded this last part from the 14.1%/day calculation because the conditions were no longer the same. I’m a bit disappointed that, even after trying all of this, I can’t seem to get significantly better battery life out of the watch. At this point, I think I’ll just accept the ~7 days I’m getting and live with it.

@matram Thanks for the info… I’ll give that a try tomorrow (fairly busy today)… I’m a software developer by trade, so am not scared of getting my hands dirty! The only app I have is the Parkrun app (for the barcode at the end), and as it was a Parkrun, there was no navigation in play; the courses are pretty well marshalled and well detailed! The watch is paired to a chest strap for heart rate. Luckily, the watch crashed after 4.95km, so I got most of the activity recorded, losing only around 15 seconds at the end. I didn’t notice any sluggishness - it was literally just as I crossed the finish line I went to stop the activity, and the watch was displaying the Suunto logo!

@sky-runner if it happened within the last few hours, please also send logs from app and provide account mail and time logs sent. Thx!

@winelouk Am I understanding this correctly? I can’t open a training session actually created on the watch during an activity. 

@sky-runner i had washed it as you mentioned but the issue wasn’t solved, so I have send it to repair. Suunto received it on 4/09 and the Estimated repair time is currently 10 business days.

[image: 1789649636751-2026-09-17-14_52_42-conversation-_-communication-planning-de-production-_-segafredo-zanetti-france-s.png] I have a little bit more data, clearly, on the night more the battery is low more the drain is high. during the day, there is no change (I don’t have enought data between 0 and 20% during the day)

I have the exact same problem. This always happens to me with Garmin Vector 3 pedals, not with Favero Assioma Pro MX-2s. This is a data sample from September 12th ride. I had power recording on Hammerhead Karoo2 and Race. [image: 1789392532136-c6d684c8-7b03-4f14-b778-cac025e3f91d-image.jpeg]

@Miroslava no of course you are not alone, since it is kind of functionality of the watch. It is not ideal for sure, I am just happy that I rarely use interconnected routes or when I do I know the route but definately happened few times.

@HomeRunner 2 options: Start with exercise (standard way): Choose the sport mode you want to use and then in the pre-start screen scroll to “Navigation”, select it and choose “Routes”. Then pick your planned route to follow. Go back and start exercise Sart with navigation: Open the maps widget. press lower button for options and select “Routes”. Pick your route and select to navigate it. The watch will ask if you only want to navogate or also start an exercise. Choose exercise and proceed with selecting the sport mode.

I’m also on beta (Android), and I can confirm it seems to be solved on my Race 1

@Stefano-M64 Just to clarify, CG2 itself seems to work fine, its just the pop up notification for an upcoming red climb or green descent that are doubled up in the new then old format a few seconds apart.

@VoiGAS thanks!! I’ll look into it. My hope is to get him thinking about training sessions using RPE first, and HR as secondary feedback. So this might be the way I go.

@Kelley-Lim https://forum.suunto.com/topic/15621/suunto-app-stats-difference

@shakra2005 Ja, das geht - jeder Bluetooth Herzfrequenz Sensor funktioniert, also auch z.b. die von Polar und Coros. Deren Oberarmsensoren sind sehr beliebt. Zu Zonesense gibt es eine lange Diskussion. Für mich funktioniert es nicht für andere schon. Deine anaerobe Schwelle kannst Du auch durch Tests abschätzen und dann die Herzfrequenz Zonen danach einstellen

Thought I’d add an update as I’ve just received a new sensor & belt from Suunto support who tested the old one & agreed that it was faulty. Also worth mentioning, whilst it was away at support I had to use the watch based optical sensor as I don’t have a back up & it performed surprisingly well

@sky-runner Yep, that’s exactly the same thing. I just upvoted your post.

@maszop can you give me some details about your disconnects with Vertical 2 and the new firmware? I will forward them to Suunto.

@elbee Thanks!