@nickshutt sorry, I don’t seem to have this issue.

Today we had a new version but nothing noticeable in iOS. I like this waypoints.

@Prenj we don’t know how many watches of that type are in stores worldwide and on stock in Finland…

There is a document on how epoc is calculated at https://assets.firstbeat.com/firstbeat/uploads/2015/10/white_paper_epoc.pdf There is an Ambit app that uses stryd power reading to calculate your energy efficiency similar to the running performance on ambit which was far more accurate than relying on gps data. http://www.movescount.com/apps/app10645993-Average_energy_efficiency Notice the level of filtering on Ambits Running Performance graph relying on gps vs the energy efficiency app relying on power data. By the time you notice changes in Running performance graph to figure out whether you have proper hydration or enough carbs; energy efficiency app would react much sooner as it gets its data from accelerometers vs. gps and barometer on watch used by running performance. Your body makes subtle changes to adapt to current situation, it does not think about finishing line, thats what brain is for (or not). The sooner you notice the sooner you can react because physiological response to recover gets Progressively slower the father you fall in anaerobic energy debt. Constantly changing wind speeds would render ascent descent baro sensor data invalid even on a flat surface no matter ambit or s9. Epoc modeling has a delay, see white paper, basically loose ohr or belt ruins it. Real time running economy would react sooner than any other method. Your model is based on power, sensor will not become loose or fall off (less likely than belt or ohr) Or better yet, Having a small “sandbox“ for custom equations and graphs sent to SA from s9 like we did on Ambit To MC would stop avalanche of nagging user requests to add features. It would also let us innovate without consuming other peoples time on development. Few 32 bit floating data as temporary registers to implement equations is not much of a footprint these days. Add a few kb of data to support at 10s logging interval. It would just be much more fun even if it fed you meaningless numbers. <nudge> <nudge>

@Brad_Olwin it seems that if I forget from the app the S9 disappears also from the Bluetooth devices. The same is not true for the S7, probably because it is connected to both SA and Wear.

@Captbrad always or just recently ? Could it be linked to that ? https://support.strava.com/hc/en-us/articles/360042757051

@Kepu_23 I have been able to use my iPhone as a hotspot for the S7. You could try that as well.

Dont forget to Unpair via BT settings Uninstall app Install, pair etc

@Egika thanks! It solved the problem[image: 1586501197304-6fca2278-35be-4333-8ecb-caac62fb39b3.png]

@nigel966 If you previously had this installed you should be able to reinstall. If not, it is highly unlikely you can get it.

@Georg-Kasperkovitz This is a community to help and engage the users. While airing your opinion is fine perhaps you can find a more constructive way to do it. We are not here to check Garmin as we are Suunto users. On your point about older Ambit watches. Suunto has not closed Movescount yet and has stated they are working on a solution that I expect will be in place when Movescount is shut down. I think you should wait until Suunto implements whatever they are planning. Because your watch does not have BT I would continue using MC until you know more. I also disagree with your statement about Garmin, I can provide examples but that is not the purpose of this forum.

It looks ok today

I think what is happening with my sync is that it starts with the newest. Each activity takes about 3 to 4 minutes to sync. After doing two 30/40 minute activities my Ambit synced 16 activities. I stopped the sync after about 35 minutes. I have searched for power meters, it looks like one person has power working on the android app and a few others can’t get the power to show up.

komoot , viewranger and quick and dirty (google)maps to gpx (mapstogpx.c@m)