[iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction

aldnet

@johan6504 mmm… strange, in my case is not exactly the same.

All I have tested is with SSSWHRBaro

If I deleted the route I had previously in the watch via Suunto App (last build) and create some activities I have some scenarios:

App in Windows doesn’t sync nothing.
If I open MC Mobile app first, activity is synced, and after that SA synced too.
If I open SA Mobile app first, activity is synced, but MC Mobile doesn’t sync the activity.

So, apart with the problem with Windows App, as @SlaSh said before seems something has changed regarding with marking activities as already sync.

So to be able to use both Suunto App and Movescount you have to reset the watch ~~phone~~

@SlaSh I think you are in my scenario, if you deleted the route via Suunto App.

But the same scenarios resetting the watch ~~phone~~, and doesn’t do nothing with routes section, everything works fine. Sync via Windows App, Sync first via MC app, after SA or Sync first via SA and then MC app

Perhaps there are some bugs here, for some different behaviors we could see, my recommendation, if you update Suunto app, doesn’t use nothing related with routes in Suunto App till the scenario is clear

Edited: In fact I was thinking now and I there’s somebody using Suunto 3 with the beta app, he could use last version without problem

Edited 2: Fixed, resetting the watch, not the phone

aldnet

@slash see my comment for long explanation, short one: reset the watch

johan6504

Even after we get this to work as a short tirm solution, I strongly believe it is time for Suunto to be outspoken about what the intention is here. Where is Suunto App going? What is the long tirm status of Movescount, and if MC is on its way out, what comes instead. Only app is just not going to cover all the expectations, no matter what Suunto marketing thinks…

Luís Pinto

@johan6504 Pertinent thoughts.

And i remember once again, owners of Ambit’s don’t have access to Suunto app. And even they had already, Movescount app can’ t be switch off because implementation features for Ambit customers doesn’t exist yet in SA. Sport tracker can switch off, most people don’t care about platform.

SlaSh

@aldnet yes sync is broken with suuntolink and mc, so you suggest me to reset my phone you are kidding me? Maybe you mean reset watch not the phone? and how to recover settings and etc after reset of the watch?

aldnet

@slash sorry I was speaking about the watch yes. I will fix in the comment

Everything will be sync in the first sync with Movescount, except weekly objective, a known bug, and HR zones if you have customized. I’m sure of that after resetting the watch 3 times this afternoon

SlaSh

@aldnet bad news

aldnet

@slash yes but at least you will sync via 3 options without problems.

You will loose the diary in the watch, but in MC website everything will be there.

SlaSh

There should be RED FLAG for beta testers who are having suunto app routes, delete them prior first sync with latest app. As we now have quite frustrating bug

Brad_Olwin

@slash said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

Houston we have a problem via cable activities do not sync, so if workout is synced with suunto app there is no suunto way to sync them to the MC only 3rd party applications… this is really bad…

Yes, I have confirmed this as well, a short test move synced with the app no longer syncs with EITHER cable or mobile MC to MC.

Brad_Olwin

Even more annoying at least to me…the elevation bug in routes via the SA is still not fixed!!! There is no elevation data when routes are transferred to the Spartan. 0_1527614553688_nUQ8ryKJT+uh4yETfLioIQ.jpg

fleshymutant

Cable sync works as long as it is done BEFORE a sync is done with the Suunto App. @Brad_Olwin I’ll try it in reverse to confirm what you have found.

Brad_Olwin

@fleshymutant Please let me know, I did SA sync first and now cable sync states all up to date and no sync of short walking move.

fleshymutant

@brad_olwin I couldn’t reproduce it with a Hiking move. I sync’d with SA and then used cable and in both cases the activity was captured.

Brad_Olwin

@fleshymutant @aldnet I can confirm.

1.01 (6183) installed, sync route with app. The elevation profile bug is not fixed.
Sync move.
Move is no longer synced to MC either via MC app or cable (no routes synced either)
Reset the watch (doing that now and will update). Resetting the watch worked but…

I am likely to delete SA. I tried a short test move and had force quit the app in iOS. The BT connection picked up the watch and still synced to SA before I could get the cable attached. No sync to MC.

Resetting the watch restored the route I had picked from MC.

aldnet

@brad_olwin point 3 will work if you sync first via MC mobile app before Suunto App sync, but the best scenario is reset and forget Routes feature till they fix it.

aldnet

And I don’t know why is so complicated, but yes, elevation bug is still present, in the notes of the version is indicated.

Brad_Olwin

@aldnet as you can see from my final note below, even when I force quit the app it synced before I could get the cable attached and synced. I cannot afford to lose my sync with MC and until there are more tests done I am unwilling to use SA.

Frankly, this is what I was concerned about a couple weeks ago when the route notification first showed up. We have no idea where Suunto is going and basic bugs in the app have yet to be fixed. (route elevation profile among others). I realize this is beta but…if the beta compromises what I use the hardware for it is a real problem.

aldnet

@fleshymutant In my case, no, is not working, in fact the windows app disabled some options after manipulating routes in suunto app.

Brad_Olwin

@aldnet said in [iOS] 1.0.1 (6183) Movescount - Suunto Routes restriction:

And I don’t know why is so complicated, but yes, elevation bug is still present, in the notes of the version is indicated.

I am not talking about the elevation bug in the app for reporting elevation, at least the watch knows what is correct. When you sync a route with SA the breadcrumb syncs (where you are going) but the elevation profile does not so you have no elevation profile for the route…I use the elevation profile more than the breadcrumb track. I reported this bug when route syncing first appeared, it is still not fixed and is a basic functionality of routes implemented on the Spartan.