I agree this is confusing and that “official” apps are in the app store. My understanding is the SA app is considered in “beta” whether or not you are in the beta program. The only watch that SA app is “official” for is S3F. Dimitrios can correct me if I am wrong. We have been through this before and I would rather not dig up the long posts about it.
Don’t get me wrong…if it were me, I would have done it differently. Nothing wrong with how the beta is handled here but I would not make any version of SA available on an app store for any watch other than S3F until the app was out of beta. I struggle with this too and use both MC and SA, which erases my custom sports profiles…
Enable custom sport modes on SA = disable Suuntolink sync to MC but still charge and update firmware via Suuntolink.
Hack to sync to MC is to use MC app but you MUST sync to MC app BEFORE SA sync. ( My SA sync is automatic so this can be tricky!) This will erase ALL custom sport modes in SA everytime you do an MC sync. You must force quit the app you are NOT using to sync so it is not running on the phone, otherwise you can get watch reboots and resets so be forewarned.
Syncing via a 3rd party app is safer but not always as satisfying since some data may not transfer. See this helpful post from one of our busiest moderators Kudos to @suzzlo
@ColdBeer said in 3.53 version - Strava sync not working:
I know it, but each everyone is using beta (as it’s opened, as you know).
… All those questions are coming just from a too soon opened beta, IMHO. It’s debatable if it’s too fresh to beta (the SA app), but for my experience, I have no doubts it’s still too fresh to be opened all around, as it still have risk of losing workouts, and need some workabouts or hacks here and there.
Perhaps, it will be fair to say a few words from another point of view.
First of all, using of beta versions of SA is based on explicit free will of a user: i.e., nobody forces him/her to do that.
Obviously, using of beta version gives a perk of an early access to new features. And in real world everything has its own price: in our case, mentioned perk comes paired with bugs, sometimes really painful and drastic.
Thankfuly, really drastic ones are fixed pretty soon (as I saw)… Thanks to @Dimitrios-Kanellopoulos …
Thus, it’s not fair to use beta and at the same time blame it for bugs in it… However, providing of feedbacks with bug reports, I think, is welcomed though…
Please note, all said above is just my opinion not intended to offense anyone.
@Dimitrios-Kanellopoulos said in Android 3.50.0 Generic comments:
@jumalca sorry again for misinterpreting your words, but I got scared as fuuu when you said bad altitude as I am eyballing on those stats
Sure, I’m not saying it’s wrong, but that the graph looks weird.
Despite the scale values, all the points should be drawn inside the graph, or the line shouldn’t be drawn.
It should be considered that the BMR will be reached by the end of the day, so on Monday we are on a limit / special case
@Dimitrios-Kanellopoulos said in Android 3.42.0 : Generic Comment:
@WEM_t what do you mean ? Its beta due to testing if the fixes are OK and there are no crashes.
Yes! Everything works fine for me like before the update. No improvement in performance found but did also not have issues before…
But maybe this is exaclty what Suunto wants to know. (testubg on Samsung S8)
If I try to edit a route (GPS inactive) the map is not centered on the route and is shown at the the lowest zoom level.
Same issue with active GPS
If I rotate the phone while in edit mode, at each rotation it does something
center map to route
looks like it stop zooming at a certain point (doesn’t seem to be the max zoom level)
Maybe is a map refresh issue ?
Is it just my problem ?
@borgelkranz said in Blockers to full SA adoption:
What I miss:
Training plans and planned moves
Connection with Stryd
Several metrics, e.g., power
Customization for interval screens
A web page or desktop variant (also for Linux)
I stick with borgelkranz (and others).
@Dimitrios-Kanellopoulos said in 3.54.2: SA -> Strava. Wrong autosync (moving time):
@kolyany4 you dont want to see their feature request forums. There is still from many years ago power for running requested.
Perhaps, it’s because they lack someone like you, who do put efforts to provide real help / push product forward, rather than generate lame excuses…
@suzzlo said in Notifications on Android?:
Still pending implementation
it is one of the 2 or 3 things that make me keep MCapp as main app on Android, and SA as an app to be tested and launched occasionnaly (after each move to be up to date) but forced closed each time.