S9B, bad new GPS version

[Łukasz Szmigiel]

Can confirm I had a similar problem today (01.01) with GPS + GLONASS and S5.

The path recorded was way off for ~500 meters and 4:35 min (hiking). Apart from that it was as perfect as it can be in mountainous area for whole ~3 hours of recording.

I’ve marked an estimated route in green in the image below. Around 4:35 min from the beginning it catched up and was perfect till the end:

[Dimitrios Kanellopoulos]

Example from Garmin groups. Looks like sony chips are affected. Join the conversation at facebook if you like here

https://www.facebook.com/groups/SuuntoAmbit/permalink/3599180883507282/?app=fbl

And Garmin

https://www.facebook.com/groups/545431909254763/permalink/1056020898195859/?comment_id=1056037584860857&reply_comment_id=1056043231526959

[Dimitrios Kanellopoulos]

Please all reboot the watch via 12 upper button(s) to wipe the cache.

Looks like sony had some cache issue.

[freeheeler]

@Dimitrios-Kanellopoulos
I double checked my activity. It is to the spot accurate, except for the first few meters where the track is anywhere fantasizing.

Will do the 12s reboot

[surfboomerang]

@Dimitrios-Kanellopoulos done

[surfboomerang]

No idea if someone is interested, but I found this little clean app for GNSS information:

https://app.qzss.go.jp/GNSSView/gnssview.html

[freeheeler]

@surfboomerang
bookmarked

[Fenr1r]

@surfboomerang @TELE-HO Used it happily for a while now. If you can be bothered, you can play around with the AR view to check sky mask and decide which GNSS to blame for any inaccuracy you are experiencing at that specific moment. Very minor Japanese geo-bias: if you set up your current location manually, the default first “Europe” location is Vladivostok. Nerdy fun.

[Stefan Kersting]

New year new run nr 2. Absolutely unacceptable gps today too. Blue line supposed to be the track. No update on the s9b and reset yesterday

[nseslija]

Reset the watch, but now can’t update AGPS. Neither with SA nor SL…

[Dimitrios Kanellopoulos]

@Stefan-Kersting did you reboot the watch as mentioned ?

[Oktan]

Restarted the watch and todays 43km ride was good from the GPS side.

[Stefan Kersting]

@Dimitrios-Kanellopoulos yes rebooted my s9b yesterday with the upper button

[Hans Martin Graf]

Had problems with erroneous tracks for two days (even flagged on Strava). Now rebooted: Thank you @Dimitrios-Kanellopoulos and best wishes for a safe and successful 2021!

[Matjaz Cvetko]

Same problems today, all day.

[nseslija]

@Matjaz-Cvetko it is the problem on the Sony side, just put the watch outside and leave it there for some time on start screen…

[Matjaz Cvetko]

@nseslija THX for tip.

HNY 2021

[isazi]

So I restarted my watch yesterday evening, got the 1/1/2021 AGPS file. Today I didn’t get the update, went for a short hike (made short by a storm coming in), got GPS signal in a couple of seconds. Because I was following a route it was clear there were issues still.

In red the track (from Runalyze), in black the real path. After this initial mess the track was pretty good, and I could follow the route pretty easily.

[A Former User]

Maybe it’s not entirely the Sony chips fault as yesterday I got strange GPS reading too with an Ambit3, but not 100% sure as here it was overcast all day long. And today my altitude reading went crazy and showed higher value then two days before in the same place, with FusedAlti on in both cases.

[freeheeler]

@isazi
I just wanted to simulate this as one of my recent activities had a bad start but was to the spot accurate after a while.
Then I discovered the following: I did the soft reset. Then put the watch static (!) on our uncovered balcony after GPS lock and started an activity. I expected to see a wild curve on the breadcrumb screen… but instead:
duration: ~15min
distance: ~0.01km
ascent: 15m
descent: 3m

maybe this one is related: https://forum.suunto.com/topic/5682/suunto-9-gps-optimization-fail-wrong-altitude