@Dimitrios-Kanellopoulos importation from Movescount done on september this year.
But…
I just discovered last week that a lot of moves were wrong in Ascent / Descent values once imported :
on Movescount, these moves are fine ;
on SA, they are wrong.
I think the problem is coming from moves that were on the two platforms (in 2018, i was using the two platforms and synced my activities on the two services) : the Ascent / descent bug on SA wasn’t solved last year and i always get wrong values. So i stayed on Movescount the time to get this bug solved.
I remember reading some information telling us that once the bug solved, all the old moves with incorrect Ascent / descent values will be updated ? Am i wrong ?
What is the solution to have some correct datas for Ascent / Descent which correspond to the right values that are on the Movescount platform ?
I’m trying to ask some assistance from Suunto :
nobody on French phone assistance ;
i don’t find any way to contact some mail assistance…
Any idea, suggestion ?
This is the place for creating new feature suggestions for the Suunto app or up-voting existing ones. You can also add your thoughts and comment on other user’s suggestions. Please remember to up-vote or down-vote already posted feature suggestions.
surprisingly I’ve planned a biketour in an area I completely don’t know. So I did my first glimpse at the navigation in the Ambit… never used it before. But it looks awesome. Route planning or loading from an existing route is a piece of cake.
…hope the Ambit will be supported for that in SA, soon. Because in SA it looks great, too… a bit tricky for fatfingers but then there’s still hope for SA web, right?
…never ever thought I would try and use it, but it is so simple!!
@loopylou72 said in Share your experience with the Suunto app here!:
@isazi why can’t we see intervals in the app only 1km/5km/10km splits - this seems a very basic function to have.
My intervals on showing on SA iOS at least all of the manual ones, I have not used the interval function in awhile.
Jamie, from the UK. Was super active in the days prior to smartchwatches, in my youth, mainly running, swimming, rugby, hockey, waterpolo and sailing dinghys and yachts (racing at a very high level) etc, but haven’t done much in the last 20 years or so. A recent health scare has encouraged me to try and start getting healthy and lose some weight.
So I am back walking (getting up to running), hiking, cycling and paddleboarding (which I love).
Been a proponate of smart watches for a couple of years now, always on Wear OS platform so I get that superb integration with my phone and that massive customization and ability to use specific apps I require. However I found that the available options in regards to fitness were very basic, so am delighted with what Suunto provides with the Suunto 7. While I can see and understand it isn’t as fully featured as the rest of the lines, from my more casual perspective it does what I need very well, so am happy (there are some features I would still love to see though).
@Dimitrios-Kanellopoulos I had an AGPS issue today with my SSU.
My last run was 3 days ago, AGPS was up to date, the SSU found GPS quickly. After that run I’ve synced to movescount via cable (using both MC and SA atm.). I missed to sync with SA as power saving mode was active on the watch.
Today I vent to run and the watch didn’t find GPS. I disabled power saving and synced with SA. The sync completed, the last run appeared in SA. The watch still didn’t find GPS. I checked the AGPS data on the watch, which showed N/A. Tried to sync again, still got N/A. Finally I did a 12s reset, after which the sync updated the AGPS data correctly.
I’m using the latest SA beta on Android.
Thanks all it was possibly due to sensor was covered.
I had another run last night, this time I strapped watch over the jacket and got correct readings.
A friend of mine also gets these 200 bpm spikes at the start of activities … new watch, new belt, new sensor, wets the belt properly before start but the spikes at start are quite random. I myself have had some issues with the sensor, but mostly flatlines at the start of recording for a couple of minutes or occasional spikes over 200 bpm (which are an abnormality for me).
@Yannis-Belouris said in Data quality:
Something is off in the altitude chart in SA.
Anyone noticed something similar?
S9 and MC seem fine
Yes I’ve noticed the same! I like a problem with the scales.
@silentvoyager
the distance was always higher than what I got from phone with runtastic.
but when running with friends having ambit2 or garmin fenix5 I noticed that on distances there were not high differences, but on altitude yes.
I was setting S9 to get altitude from barometer and they were taking the altitude from GPS.
I had 50-60m differences on 800m total altitude gain.
I don’t know which one is more accurate or if it’s good or bad.
cheers,
Florin
Hi @Dimitrios-Kanellopoulos could you please explain why we have difference between pace data in watches and movescount during pool swimming? Autolaps were disabled.
Let me show my activity.This is data displayed on watches, as you can see the pace is 1:58, total time of activity is 33’19 min.
When the data is transferring to Movescount the pace changed to 2:13, total time of activity noted is same, 33’19 min.
I understood that we have difference between Strava and watches, due to different calculation, but why we have difference between watches and Movescount?
This is data from Strava, the pace is 1:58, BUT activity time is 29’37 min! Its moving time without time for refreshment between swimming intervals.
To be more clear i got swim 3 times per 500 meters with refreshment abt 1 minute between intervals. As i noted autolaps is disabled and i didn’t use pause button during activity.
@margusl said in How to view POWER data in SA?:
@lexterm77 said in How to view POWER data in SA?:
I wonder what would happen if you changed device id from A3P to S9 it would actually show up as it should
For activities the latest Suuntolink is using an API endpoint that seems to be set up only for Ambits & Traverse, in other words, I’m not too keen to mess with device spoofing.
But I went back to fill those empty values in summary with some dummy min/max/avg power figures and …
avg_power & max_power made it also into fit-file session data, but there’s still no power data stream, so it’s use is kind of limited. Though at least Training Peaks picks those up (original w/o power vs “assisted” with avg/max power):
If someone has the right amount of commitment, setting up a mitm proxy for Suuntolink in a controlled network for adding correct avg/max for power before data reaches Suunto App, is actually doable.
Though adding / enabling the same thing in a proper way in Suuntolink would be a really low-hanging fruit for Suunto to pick.
If I had time I would make a Rasberry Pi pair with Ambit and act as a middle man to connect with phone and do the proper conversion and device spoof and correct data format instead of meddling with SA. Also, you can always snoop BT on data exchange between SA and Ambit to see what is really going on, I bet log file of conversation between those two wouldn’t be that long to figure out.
@josephkarl said in Disappointed Android users:
oid device has started lagging and the device becomes slow and many apps are getting affected with that and affecting the outlook app was one of them.
The phone might get slower due to one single app if this one is using huge amounts of CPU, but it’s impossible that other apps are directly affected in terms of they stop working or have crashes because of Suunto. Each app running on an Android phone acts as a single user in a multi-user Linux system. This means that the apps live in their own sandbox regarding security, performance, etc.
There is one pop-up when you install the SA asking you to allow the app to run in the background in order to provide a better service. If you don’t allow this (can also change it in the settings), the performance/battery of the phone will definitely not be affected although you might miss a couple of notifications.
@nigel-taylor said in New Android Diary Section:
Agree the diary is an improvement and seems good at first glance, but if I look at my activities in the equivalent section in SportsTracker then that is a LOT more functional and useful.
Do we know what the future of the diary is going to be? If it remains as the simple single list it’s going to be next to useless for monitoring progress and performance, if it gets the ability to search and filter by year and month etc as per SportsTracker, then it could be a solution that keeps me away from the web interface.
Anyone know? Or…is the Android GUI going to change from its SportsTracker roots and this is a spurious discussion?
Hello,
i have just update to today’s 3.37.0 built.
An still nothing to filter by month or activities, etc… Or may I lost something.
I really prefered the first builds in term of diary informations.
I must admit, i am not using SA anymore, just test new things, but in fact did not find any new stuff
I am a good student, I upload my activities each time, but not more, if i need stats, I go to movescount web.
@Cuba1hr said in Migration to Suunto App in 04/2020 and very unhappy with the result:
Those minor things that SHOULD be easily fixable-activity setting memory and more screens…I don’t know why those features for SuuntoPlus arrive so slowly.
I don’t get it why not more than 3-4 screens if it was possible on the Movescount, how long we have to wait for something that was already available.
I think the same, that updates should be released more often.
