Thanks for the replies folks.
I actually did a full u turn a bought something completely different. I went into Go outdoors and came out with an Ambit3 Peak…
After owning a couple of Garmin watches with power hungry displays with all the bells and whistles, I thought id have a look at going back to raw basics with a solid tried and tested watch that focuses solely on the outdoors with a solid construction and decent battery life.
I bought it thinking that I could take it back within 28 days so could get a refund if I didn’t like it. After having a play for a few days I absolutely love it! It feels solid and more of a proper rugged abusable trail watch rather than a smart activity tracker watch. I can just leave it on with no concern about the battery and it does everything I need.
Ive now realised the features that the ambit doesn’t have from my last garmin were actually a little gimmicky(to me anyway)…………. the weather forecast was never accurate, 24/7 HR was was absolutely no use to me whatsoever (so therefore wrist hr was pointless) and I never really bothered with the daily tracking features like steps,floors,sleep etc.
Thanks again for the replies and if anyone has an ambit3,i’ll no doubt speak to you in that forum.
Gaz

@sindre-svellingen That’s great!

@Krzysztof-Gąsior I see the issue there. Looks like pressure leak. Try to let it on the table, and see if it fluctuates. Then take on hand, wear it and see if it changes. (altitude).

If yes , ask for replacement unfortunately

@hdemooij neither Suunto nor Samsung nor Apple has public roadmap for their watches, but of course there will be software updates for S7

@isazi @martin-vrska thanks for trying!
I’m hoping it was just an anomaly that won’t happen again until they update diary to let us resume after any technical issues like strava (fingers crossed) It’s all saved in diary so we should be able to use that and resume even if we aren’t at that exact gps coordinate. Strava just does a straight line the next starting point (doesn’t look the best but it’s better than nothing).
TDLR tech isn’t perfect which means there needs to be safety nets

@olymay Barotrend, does have an option to input SLP but it’s pointless as if not stationary the graph will be off. To give props the S7 is by default calculating absolute pressure as you lunch Barotrend app and that is spot on with my Davis weather station and my Casio. So the sensor in the S7 is incredibly accurate and it would make fine prediction as you said only when stationary at the same altitude. Finger crossed for a new S7 😉

This is what happens when I run! After about 10 minutes it matches my Polar OH1 fairly closely.
Even if i go for a walk it spikes for the first few minutes. It hit 140 during a gentle stroll today.
9C137897-D1B5-4369-8DF3-6DA2064C286F.jpeg

@marty313 I would expect cycling to be reduced accuracy as you are moving faster. The battery in 1s mode should last a long time cycling so I would not used FusedTrack unless necessary. Great news regarding paddling.

@steff Strange because it was even able to be preordered. Maybe I came across something that was supposed to be secret still or maybe it was an intentional unintentional mistake lol.

@eurohiker
now it’s the 4th watch not working?

@aleksander-h said in Spotify offline support now rolling out:

A bit of good news. It seems YT Music will make its way to older devices as well.

https://9to5google.com/2021/09/27/youtube-music-wear-os-2/

I saw this last night. I am hoping it will come to the S7 soon.

Although It’s unlikely I will use it due to battery drain, it’ll be a nice to have (and arguably something we should never have been without!).

@brad_olwin - map usage - depends on the model - on the MIP screens it really isn’t that bad, and on the Epix I estimate it around +15hrs of continuous tracking with map (as long as not using dual-band GPS) - that is with AOD and heavy map usage. Based on around 10% for 85min hike. Most of time was on map (new area to me) with a bit of climbpro screen in between. Occasionally just on data tracking screen.

@dimitrios-kanellopoulos I have the same problem with S7 but I think is the suunto app the question. if I use strava (standalone not connected to the phone) for my bike rides there’s no problem. the suunto app registers double elevation. so I presume that strava don’t use barometer but only gps. I like so much suunto app in the watch but I don’t use it anymore.

@jonathan-schwarz said in Adding Waypoints to Routes that Overlap:

@nigel-taylor-0 SO update - with the new update today, if you have komoot linked on your Suunto app (partner connections) - any “Tour”/route you create on komoot is AUTOMATICALLY synced to your Suunto app route list. All you have to do is enable “Use on Watch” and you are good to go.
Pretty slick.

I think its been enabled since yesterday, I tried this but its nowhere near as useful as simply syncing routes created with Plotaroute (or other services) with personally made Waypoints for direction notifications.

Good if you want to use Komoot, and are happy with the excessive directions that they create!

I tried a 5k route yesterday via this process, it inserted TWENTY EIGHT instructions when it synced to SA, where I wouldn’t really need more than maybe 4 or so, if I just tagged the junctions…and of the instructions it created, I looked at a few of them and one was actually completely incorrect, suggesting a “U-Turn” when it should have been “Straight” (or actually just nothing!).

@hqvkamil they are both S7, but agree I prefer the flanges as not only provides protection (as I have already discovered) but also just helps it look really nice.

On this graphics I not see any strange, this is a speed graph, not altitude graph. This spikes on the speed in MTB sport mode for me are totally normal. At first time I believed that was created by crossing under bridges or tunnerls, but later I discovered that not. I have between 1 or 3 of this spikes on any activity of MTB of more than 1 hour of duration. It’s common come back from a MTB activity at flatlands with max speed between 80-120km/h… 😂

The altimeter have their own topic, sometimes do have strange behaviors that I can’t explain the origin. Nothing of the logic reasons can be applied, but also not bigger differences like yours of 2000 vs 25.

I can’t explain why, but all the these kind of problems happen to me on MTB or Inline Skating. Running or Trail Running no. Also this happen only with the SWA, I tried to replicate in other apps without using SWA without success, that means that hardware it’s OK. The most strange it’s that I practice the sports in similar areas, that means that the enviroments are clear sky, without trees, without building close, etc, and on MTB with SWA I can repeat this spikes or erros, but on Running this did not happen. I expect more this kind of errors on Running, because the watch it’s not clearly exposed to the sky, on MTB yes, have a perfect exposition to the sky. About if something is blowing air into the sensors: I don’t know if it’s possible, but on MTB/Cycling the baro sensor could be directly exponsed into the wind, I don’t know if this can cause some problem or it’s directly related to something in this sport mode on the SWA.

Also in the past I had the problem of the bug that the S7 reebots or freeze in mid-activity. I don’t know if Suunto worked on this or push some kind of silient update to the S7 because in the last months did not happen again. Normally this happened each 2 months and now already they passed 4 months without problems 🤞

Start the activity before did not help, like wait until I have fixed GPS on SWA. Looking the activities this not happen on the start of the activity, that could sound logic, this spikes or strange shifting in the altitude happens after really long time that the activity is started (more than 30’).

@blenedfly said in Altimeter:
@freeheeler
6f271584.jpg image url)

@Gareth-Stockdale There’s a sync from Movescount to Suunto (if you connected the two) but not in the opposite direction. If you still need to have things in MC, I recommend a third party app like PhoneGap or SyncMyTracks.

@giulio I have an iPhone and my carrier allows tethering. I am able to download maps using my iPhone as a hotspot. It is much slower than downloading from a fast WiFi. It is possible that your phone will terminate the connection after some time or if the phone does not remain on the connection terminates. Mine requires 15 min to 20 min to download the maps.

@olymay As I wrote, my experience was totally diffenent. But that’s no problem for me any more. I was able to send the faulty suunto 7 back to amazon and got a refund. At the moment I am a really happy garmin user 😄