AGPS not updating on Suunto 9 Baro
I am continuing to have issues with AGPS not updating on my S9 Baro and GPS lock taking increasingly long times.
Currently AGPS timestamp on my watch shows 2019-11-18. I sync almost daily.
Every two weeks or so I have to reset my watch after which it does download new AGPS file, but after a few days the issue repeats.
I remember this issue has reportedly been fixed a few months ago, and it was a server side issue, but that doesn’t appear to be the case for me. I wonder if anyone else continues having these issues.
I sync mostly with MC app if that matters, but supposedly that shouldn’t matter.
I synch only with SA, never used MC, and don’t have this issue.
I only sync to SA, too and don’t see this issue either
Syncing with SA (Bluetooth) and MC (cable) … no issues either (S9 - non-Baro)
No issues… Syncing with SA… S9B…
My S9b is not having this issue but my S5 is. Requires many sync attempts to get the AGPS file to finally copy. I will ask about this and file a bug if needed. I do not understand why this is happening iOS 13.3; latest SA beta.
the problem is in latest version of Movescount or suunto link, I dont know which one. I had the same problems. I still use Movescount as my primary app, but I also sync with SA, just for updating AGPS. I just can not use android Movescount enymore. You can use custom graphs in movescount also if you are patien and imaginative and you can have best from both worlds
I really wanted to avoid syncing with SA until I have to switch, but it looks like I have to give it another try. I really dislike that it wants tons of permissions and wants to run all the time in background. That has no upside in my use case and only shortens the watch battery life. And on top of that, it will now force the wrong starting day of week on my watch.
@silentvoyager You can also not give the permissions.
Movescount as far as I know has more permissions that are granted on Install time not on runtime.
The only permission SA really needs is BT / Location and the location permission is due to BT that is a location leaking module.
The apps does not run in the background, a sync service to listen to BLE runs that is part of the app.