@Stanko-Mar You tried to keep pressed the power button until the S7 turn-off and restart? This happen to me few times and I was solved doing this.

@kurko I wrote to Suunto numerous times pleading for a software update. I suggested some fitness and outdoor features. They are not listening A real shame as the S7 can remain relevant in 2022 with incremental updates. Suunto is struggling to to decide what to do with the S7, Finger crossed we get a surprise before the end of 2022!

@jamie-bg Thank you!

@binoworld-uk Agreed

@freeheeler Merci pour toutes ces réponses qui mon bien aidées

@pilleus said in Sunnto 7 Sensor Support: I moved from S7 back to SSU. Because I like WearOS too, I have a Oppo Watch (46 mm) to gather heart rate, steps (natively in Google Fit, the health app of Oppo is deactivated by ADB) and show notifications during the day. S7 without sensor support is not suitable for cycling (mounted on the handle bar there is no heart rate and no data from the power meter) and not for kayaking (on the wrist no option to read the data, on the deck no heart rate). I have been trying to use Suunto 7 for cycling, but after 2 weeks I have already given up. Sensor support works only via 3rd party apps, so at the end of the ride I have data in two separate recordings that cannot be merged / analysed correctly. I cannot even connect Suunto’s own product - Suunto Bike Sensor. Handlebar mount without external sensor does not make any sense either - no heart rate. In short - if you are after a watch to replace your biking computer just look somewhere else (unless Suunto comes up with an update).

@freeheeler yes i turned the watch off and on again a couple of times and it didn’t do anything

@deaquinogeorges, @judnoe Sorry for late response. It occurs few times. Then I send it to service. They replace it. That was good, but unfortunately it happened also with second one. Now I have third and keeping fingers crossed that it will not happen any more. Btw: official service response is that mainboard is broken

Thanks for the help guys. It’s arrived and is now all up-to-date

@flypg I have had similar issues occasionally. It was more when I tried ski touring and the altitude was off by a few hundred meters at times. When I download the route / gpx file and upload the gpx file into the app, it has the elevation correct. My question is, why doesn’t the FusedAlti solve this in real time?

Ok. @flypg, so I will next time. Thank you.

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 [image: 1655314027761-6f271584.jpg] image url)

I would like to have Suunto Plus Guides, Suunto Plus functions… external sensors, auto pause, set the zones of pace, hr, power… I love the s7 but there is space for new features and features request for the watch.

@aleksander-h said in April is Coming ! (S7): @metalmi said in April is Coming ! (S7): Fossil said the Gen 5 (with Snapdragon Wear 3100) is in line for Wear OS 3. This information apparently came from Fossil customer support who are frequently wrong on these kind of things. That’s why we didn’t get any info for a year, haha

[image: 1654753969139-img_20220609_074701.jpg] Problem is solved in less than one week! Great !

@freeheeler maybe that’s why they never bothered with giving it belt support

@aeroild sorry for the late reply, yes all of a sudden confirmations works from the watch.

I just received a 10% off voucher from Jabra. If anyone is interested, PM me