GPS/GLONASS sgee update
-
-
This is getting out of my hands
A notification would be nice, but also an option to disable automatic GPS optimization and activate it manually when needed could be a solution.
Or maybe I should change my habits and do a 10 minute walk around before session start just to be sure I get proper GPS lock
-
@andrasveres which watch are we taking about?
In general, if you sync with the SA app, once a day or every two days you should have a GPS lock within seconds, it has been for me that way with the SSU and with the S9B.
I usually go for a run every two days so I sync the watch at least every two days and I get a lock within seconds. The problem is if you sync just before running and the AGPS needs to be updated in the watch, after the syncing the watch needs some more minutes to deploy the AGPS info. My advice, do not sync just before running, do it the day before or some hours before. -
@cosmecosta it is an Ambit3 Vertical. The fact is I do not sync before my run, but Suunto app does it anyway (sometimes when I get out of bed my sgee data has been updated, sometimes in mid day). And if that happens then on my very first run GPS lock takes very long time. And yes, if before my run there was no sgee data updated, GPS lock is within seconds.
I was thinking to disable bluetooth sync on my watch and do manual GPS optimization, when charging it, with SuuntoLink, but then I will not have notifications.UPDATE: as I noticed my Ambit will start deploying the updated GPS data on the first GPS use and not right after sync. Not 100% sure, but can’t explain the long lock times otherwise.
-
@andrasveres Funny thing is that I used to own the Ambit3 Vertical but I never used it with SA, only Movescount. In my experience it was very unstable watch regarding GPS (locking it and tracks). I think this watch won’t be among the best GPS watches in Suunto history.
Then I switched to the SSU and was a big step forward for me and my needs (I lost the vertical summaries and the nice track shape when finishing a run).
-
@cosmecosta Never had GPS problems till now using both Movescount app and then Suunto app. Just not so recently started to have these issues and I can’t figure out why: the more frequent GPS data updates, bad GPS data, sync issues with my iPhone or just the watch is starting giving up.
-
@andrasveres
Maybe it could be good to have some watch hard reset. Something could have been stucked in the time.
Not scientific suggestion though, but it could worth it to try. -
@Mff73 First I will try disabling bluetooth sync to Suunto app and only use SuuntoLink for sync (it is strange to me that issues started since when the app had an update a month ago) and if that doesn’t help will do your suggested hard reset.
-
Does this happen via SA or SL ? OR both ?
-
@Dimitrios-Kanellopoulos I occasionally use SL (maybe 2-3 times a month), but as I noticed it happens with SA only, but can’t pronounce 100% sure. Now I’m testing with SL only sync. So far as I see right after GPS optimization via SL the watch locks in max. 1 minute, that is far more less then 10 minutes. In the afternoon I will do a run and see how it performs on tracking.
-
@andrasveres SA iOS or Android ?
-
@Dimitrios-Kanellopoulos iOS (I’ll add gear info to my signature
). Thanks for looking into this. -
@andrasveres do I understand correctly that iOS might not update the AGP from when you check the timestamps ?
-
@Dimitrios-Kanellopoulos Not sure what is happening, it might update bad data or other format that normaly the watch expects, don’t know. All I know is that SA updates GPS data very frequently and after the update the watch is struggling to lock at first use. I check GPS data timestamp from my watch service menu.
-
@andrasveres could it be that you sync -> AGPS is not updated asap (eg takes a 15mins) and you try to go out with broken AGPS?
Try this
-Sync AGPS via SA
- Close BT on the phone.
- Wait 30 mins
- check how long it takes to lock
-
@Dimitrios-Kanellopoulos I will try that too. However before my last run I’ve checked the GPS data timestamp (was quote recent), went to a run, after finish checked again and timestamp was the same, but GPS track was missing for the first 10-12 minutes.
Do you know or can ask what and how exactly the watch is doing after new GPS data gets uploaded to it? Not the S series but the old Ambit3. Just to be sure that deploy/unpacking GPS data is not done at first query of GPS, but right after it gets uploaded? -
@andrasveres Bot sure the pal I wish I knew
-
@Dimitrios-Kanellopoulos Yesterday I tried what you suggested and here is an interesting thing:
- checked GPS data timestemp on watch
- synced watch with SA (GPS optimization took place)
- verified GPS data timestamp on watch and it was updated with new time/date
- turned off bluetooth completely from watch (as opposed on phone only) - just to be sure I will not turn on accidentally
- waited 45 minutes
- started exercise on watch and GPS lock succeeded in just ~90 seconds
- I left bluetooth off and this morning I’ve rechecked the GPS lock process and it succeeded in ~20 seconds
Now as a conclusion since SA updates, correctly watch deploy it correctly in normal conditions, all I can think of is that somehow the watch timeout for sleep is the culprit. Let me detail why:
- I use my watch as alarm and I place it bedside (not wearing it on my hand)
- watch times out and goes to sleep
- on some movement watch wakes from sleep and SA sync kicks in and updates GPS data
- watch times out again and the deploy process is interrupted leaving undeployed data
What do you think? Could that be the explanation?
Anyway, I will test my theory somehow just to be sure. -
@andrasveres at least I like the theory
-
@andrasveres I think it might be the case. That’s was my suspicion pretty much as well
