Using Movescount web and Suunto app simultaneously
-
@Oktan
yes exactly. that’s what I did with my a3p.
after sync to SA you need to force stop of SA in app manager as closing SA will not drop the connection between SA and a3p. -
At least for Ambit, sync order doesn’t really matter, it works both ways, at least for me on Android. There are sync flags but SA doesn’t care about nor set those. And it seems that MC app has stopped settings those as well, but does respect sync flags set by Moveselink2.
It’s just that SA seems to be more aggressive (or just more successful) when connecting to the watch, so it kind of makes sense to let SA do it’s thing in the background and when you want to sync to MC, kill SA and switch to MC. Disabling bluetooth and then letting MC to re-enable it seems to increase success rate. But I usually still need two or so attempts - SA service restarts itself and can get to the watch before MC.
Cases where I actually have to kill MC are quite rare, at some point SA just takes over the connection. But it could be because of my power settings or permissions.
-
@Mff73 It is not perfect but the Moves are properly labeled, it does a very good job.
-
@Brad_Olwin I use RunGap to sync with MC web (because sometimes MC app doesn’t sync).
The negative of syncing via RunGap is that you lose LAPS. All other data is transfered correclty. -
@Maryn said in Using Movescount web and Suunto app simultaneously:
@Brad_Olwin I use RunGap to sync with MC web (because sometimes MC app doesn’t sync).
The negative of syncing via RunGap is that you lose LAPS. All other data is transfered correclty.Submit a ticket request to RunGap…they are very responsive and might fix this issue!
-
@Brad_Olwin ok
good idea .
