GPS/GLONASS sgee update

This morning GPS went crazy again
Yesterday afternoon all was fine, left the watch near the phone for the night. This morming before run I’ve checked GPS sgee timestamp in my watch, it wasn’t changed, but upon starting the exercise GPS had trouble finding satellites. Ended up deleting exercise after finish because of crapy data it was collected. So definitely something fishy with Suunto app GPS data sync (at least for my Ambit3).
Will do a hard reset on watch and go full cable sync from now on and will see what will happen. If this continues like this I’m afraid the watch will end up with a “farewell” ticket on it as I refuse to waste more time on this issue.

Just a quick update: did a hard reset on watch using SuuntoLink, syncing since then only with SuuntoLink via cable, no long GPS lock time or wacky GPS tracks until now. Guess I will stick with cable sync until I see some improvement regarding “Optimizing GPS” in the release log of Suunto app.

Quick update again: when 1.71.0 and 1.72.0 versions came out I switched back to using Suunto app for sync and so far no issue with the GPS lock time.
Thanks Suunto devs for the fix!

I have the impression that Suunto app version 2.0.0 (8642) doesn’t sync GPS data anymore. Last time data was updated was on 12.1.2021 (as displayed in service menu) and was done via SuuntoLink when the watch was charged. In the last two days Suunto app briefly shows the optimizing GPS, but suddenly stops without displaying any error. Does anyone experiencing this?

surfboomerang

@andrasveres In the beginning of this year there were some sync troubles, but they seemed to be solved.
At the moment I don’t have any sync issues (S9B + Android) and I have also a AGPS file with today’s date.

Dimitrios Kanellopoulos

There is an issue that is getting a hotfix asap

the workaround is to only use GPS in GPS system setting

@Dimitrios-Kanellopoulos unfortunately the suggested workaround didn’t worked for me. I even reset the GPS data, but it didn’t helped. I will use SuuntoLink until Suunto app will get the hotfix. No problems

fritzbt2013

@dimitrios-kanellopoulos Having similar issues with S9 2.13.18 and iOS app 2.0.0. AGPS data doesnt sync unless I reboot watch. Any idea (more than ASAP-5 days) when ‘hotfix’ is coming. Thanks

Optimizing GPS is working again in Suunto app version 2.0.1 (8648).
Thanks @Dimitrios-Kanellopoulos and Suunto devs!

@andrasveres said in GPS/GLONASS sgee update:

Optimizing GPS is working again in Suunto app version 2.0.1 (8648).
Thanks @Dimitrios-Kanellopoulos and Suunto devs!

Still didn’t get it, did you do something “special”?

@andré-faria if you are referring to app update no, I didn’t do anything special, just regular checking for updates on iOS.

Update: I’m using the public and not the beta version, if that’s the case for you.

@andrasveres said in GPS/GLONASS sgee update:

@andré-faria if you are referring to app update no, I didn’t do anything special, just regular checking for updates on iOS.

Update: I’m using the public and not the beta version, if that’s the case for you.

Yes I am using the beta

SnusR

Does anyone know why the beta version on IOS is lower than the official one?

Beta: 2.0.0 (8639), Public: 2.0.1 (8648)

@snusr maybe this was a quick fix and it didn’t have to be released on beta channel. This is not uncommon in IT world.
Pretty sure next beta will include all the fixes from current public.

Sadly back to this topic again.

Today I had no GPS fix on my run! I don’t wear my watch all day, just for my runs, and apparently when I opened Suunto app about one hour before my run the GPS data got synced. Even if about one hour was passed and all this time the watch was on my wrist, so no sleep mode activated, when I started the activity tracking, GPS had hard time to get a fix. After waiting almost 10 minutes for a fix, I decided to start anyway and leaving the GPS to search for fix during activity. My run was done and guess what? GPS fix wasn’t acquired and no GPS data was recorded. The recorded distance was way off, I didn’t expected magic from the accelerometer, but almost 1 km difference… it’s crazy on a 8.3 km route. Basically today I run with just a stopwatch.

I don’t know if bad GPS sgee data or data corruption during sync or the watch didn’t had enough time to “install” GPS sgee data, but in the end I don’t even care, it’s just sad! I can’t understand why we can’t have an option in Suunto app for us to decide when GPS optimization should take place?

Tracking my runs is starting to be a joke, sometimes heart rate data is trash, other times GPS track is wonky and now no GPS at all.

This is not how I imagined the digital transition.

Dimitrios Kanellopoulos

@andrasveres so why didn’t you check if you have agps?

I see you also have an ambit. That syncs fine agps.

The no fix ain’t a problem with the agps. The watch should get gps fix without agps as well especially the ambit.

Nor should it have bad tracks.

I would contact support maybe it’s hw

@dimitrios-kanellopoulos I’ve checked and it had refreshed data and the watch had almost an hour to process it. I’m not saying that the sync doesn’t work, I’m just suspecting occasionally something goes wrong.

Yeah, I know it should get GPS fix without sgee data, but believe me, it didn’t and it was just as clear and sunny as today (and now gets fix in seconds with the same sgee data). It would be great if I had an option to do manual GPS data sync when I consider being a right time (I can use my Ambit with 2-3 days old sgee data just fine), without being forced to turn off auto-sync and do manual sync after each run.

Now if I pick up my watch for a run and Suunto app out of nowhere sync the data, mostly GPS fix issue is what I end up with. Maybe it is not related as you say, but this is what I noticed occasionally and thankfully not regularly. Usually as I noticed I get bad track (offsets or corner cuts or insane jumps) when it struggles with GPS fix at start.

Will check a couple of days from now on and if it will happen more frequently I will contact support.

PS: sorry for getting my rage out here, but after some hard days these kind of issues are getting frustrating.

Dimitrios Kanellopoulos

@andrasveres it’s ok. But just to pinpoint the issue. If agps /sgee is transfered it cannot be an app problem.

@dimitrios-kanellopoulos yep, it’s complicated. I don’t know how sync is implemented, but if in some circumstance corrupt data is transferred… or sync is done right before activity start and the watch doesn’t have enough time to process it… it’s not an app issue, but it’s an issue for the user.
Another thing I noticed long ago is that when Suunto app is syncing the watch doesn’t show “M sync” as does with SuuntoLink and as I remember it did with Movescount app. I notice that a sync is ongoing because the watch is reacting with lag to button push.

Anyway, I disabled the auto-sync again. It’s an inconvenience I can live with.

PS: even an app notification would be fine for me, just to know GPS optimization was done, so I’m aware about it before my next run.

Dimitrios Kanellopoulos

@andrasveres if you have an updated sgee timestamp then the file is ok (in theory).

It means that the watch managed to decrypt the file and extract the date.

Now wether the data that sirstar sends are fine that is where it gets complicated