@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.

@Jonathan-Newby No. It works!

@Darqu said in Smart sensor:

@Brad_Olwin does new belt work with ‘old’ smart sensor? I will consider changing it.

Yes, it does. And since the sensor itself has not changed, it is the only working combination

@Dimitrios-Kanellopoulos If I want to have that: Do you think that I should switch to vívoactive because of that?

@Bulkan said in How to view POWER data in SA?:

I don’t see power in the suunto app Link you shared.

One thing, could be possible that in the average is counting the zero? It that is the case the average power is not your average power pedaling (I hope this word is correct).

Strava only counts the time were there is power. So downhills don’t count on average.

On the link it doesn’t show, here are the screenshots

5B6D7843-3DA7-4727-90E2-6C7EF8BC0D16.png F245ED92-1B0F-4C25-9ED7-AE57DCE036A2.png

@margusl thank you very much for your help. It is not normal for us to have to find workarounds and alternatives to fill the lack of missing features / data with Suunto app. It is Suunto job to make this transition more smooth

@Yannis-Belouris said in Data quality:

Something is off in the altitude chart in SA.
Anyone noticed something similar?
S9 and MC seem fine

0_1538134627060_Screenshot_20180928-133547_Firefox Beta.jpg

0_1538134743280_20180928_133838.jpg

0_1538134761560_Screenshot_20180928-122132_Suunto.jpg

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.
20191001_181202.jpg

When the data is transferring to Movescount the pace changed to 2:13, total time of activity noted is same, 33’19 min.
2019-10-01_18-07-24.png

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.
2019-10-01_18-07-07.png

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.

“Suunto App update, Ask your neighbour pusher”

@johann-fuehrer On iOS fixed on 1.9.0 and higher, on Android should come with the same iOS lap table that we are building.

@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.

@slash Yes - great, today there was an update from RunGap - I hope it solves the problem.
(I can not test it myself because I no longer use MC.)

Yes working👍 But strava synk is behind, I expect it to catch up tomorrow…

@dombo @Akos-Hajas This has been fixed, I will wait a few days and then we can mark this as resolved.