@rdcritchlow I had a similar situation with 9baro, the battery was completely discharged in 10 hours. The discharge did not depend on activities, heart rate measurements or anything else. During diagnostics, a local unofficial service revealed a faulty charge or battery controller (I don’t remember exactly what it was) (the warranty on the watch had expired at that time). After replacing this element, the discharge returned to normal.

Usually it is not necessary to use a high amp charger as the charging circuit in the watch will never allow high currents anyway. If the battery is in deep discharge then a state of the art charging circuit will trickle charge it until it can come back to a normal charge. This is why it can take a long time on the charger until he device comes back to life. Thus the recommendation for deep discharged devices is: leave it on the charger for a longer time. I would only call it defective if it does not come back after a day or so. This does not solve the initial high discharge though…

@eugene-benkovskiy Thank you for the additional comments. I also like the watch a lot - especially my STEEL variant… And yes, I also use and enjoy the watch a lot in combination with imported .gpx-tracks from komoot. Hiking is so much more relaxing, if you don’t have to get your phone out regularly to check the route! Best, Alexander

As I am still not able to understand the way S9b works with the laps data in different modes I made a series of tests (trail running) over the same route. Here you have: MODE PERFORMANCE - NAVIGATOR SCREEN OFF § https://www.suunto.com/en-be/move/davidzuelballester/60bb0e0f9859195d40b93320 MODE ENDURANCE - NAVIGATOR SCREEN ON (E-ON) https://www.suunto.com/move/davidzuelballester/60cd9fb2852b3c080621258a MODE ENDURANCE - NAVIGATOR SCREEN OFF (E-OFF) https://www.suunto.com/en-be/move/davidzuelballester/6097121145cefd139a2aaa00 Looking at the maps, neither reading E-ON or E-OFF matches reading P. Whilst E-ON guidance was completely correct, the route recorded is significantly less accurate than reading P. Looking at the total distances: The actual distance is 13.9 kms P recorded distance is 13.87 kms, last split ends at 13.9 Km, so is coherent. E-ON recorded distance is 14.8 kms, last split ends at 13.3 kms (why is that?) E-OFF recorded distance is 14.55 kms, last split ends at 14.4 kms (why is that?) Moreover I don’t get the actual difference between split duration and split min/km. In P these readings are different although though, but in E-ON and E-OFF, these readings are far one to the other.

@jon-murua What is power saving in Spartan Ultra? And next tests to do : confirm the first one (full power and watch in pocket), and full power watch on backpack.

GPS and OHR worked really well : https://beta.quantified-self.io/user/88tGXoxa0YOtAw07abZo8jK8mN93/event/3cPQA91MbTn2CvY9nukbwvqsE5BRQodXKmw79U2Pe41tGmy