Movescount App crashes after Move Sync
Ok, maybe I am wrong here but I think I will get the best and fastest response in this forum. I use an Ambit 3 Peak and sync it with the movescount app (I only have this app on the smartphone, the suunto app is not installed on the smartphone). Yesterday I make a mtb-trip over 12,5h. In the evening I synced the move via movescount app. Thats the point when something went wrong. The app crashes if I want to look at the move. The move is in the app but the app won’t transfer it to movescount. I lost my norseman move 2017 and my wife lost one ultra marathon in the same way. Is there a possibility to rescue the move?
- Forget android Movescout. Sync with cable ONLY
- Do you still have move in the watch?
- Thats what I painfully learned.
- Yes the move is in the watch and I didn’t do further actions until now.
There are few options. Probably the easiest is a cable sync with Suuntolink, this will push the activity to Suunto App and you can export it from there. Unlike Moveslink2 & MC mobile, Suuntolink does not care if the sync-flag in watch itself is set for you activity, so there’s one less problem so solve.
You could also try cable sync with Moveslink2, this would send it directly to Movescount. If it fails to pull that certain activity, you may need to reset the sync-flag, there’s a tool for that - https://forums.watchuseek.com/f233/data-logbook-ambit3-but-cannot-export-movescount-4159434.html ( use it at your own risk etc etc )
And if you want to play it hardcore, it possible to pull data from phone’s app storage and push it manually to Movescount service.
To make your MC mobile app work again, you probably need to clear at least cache and probably app data as well (been there… ), but leave it until you have recovered your Move.
Great members in this forum, thank you very much. You solved my problem in less than 30 min!
I used the tool from runningCat, here is the link: https://drive.google.com/drive/folders/129zttyToy6s1rboXepcLsU54Rnwcca30
If you read the readme.txt everything is crystal clear. By the way my 5 year old ambit battery was fully charged at the beginning and at 37% at the end (with hr-sensor, best gps-signal and 1s data-logging). If I extrapolate it 19,8 h would be possible, in reallity maybe 18h. In the tec spec’s suunto says 20h is possible in new condition. Thats great for that watch so need to upgrade to something new!
… no need to upgrade the watch