Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Just got updated to 3.30, first ride has 80% GPS dropout

winfij
over 5 years ago

Not a great start - my watch notified me it had been updated when I looked at it this morning, 3.30 plus the sensor and GPS updates.

The commute ride this morning recorded with those updates recorded no speed/position at the start for the first couple of mins, then recorded them for about 10 seconds, then nothing for 13 mins, then recorded OK for the last 10 mins.

The other sensors (cadence, HR) recorded fine the whole time.

This was with GPS + Galileo

I've not had this happen before the update to 3.30, normally recordings have been fine.

I don't know if this is a problem in the base FW update or the GPS update.

EDIT: As pointed out below, GPS wasn't updated. so it is likely an issue in the base FW.

  • 0 over 5 years ago

    There was no GPS update along with v3.30.

    Sensor Hub and ANT/BLE/BT updates yes, but the GPS is still v2.50.

  • 0 over 5 years ago in reply to jmto

    Ah, ok, thanks for the clarification - I remembered there was a second thing updated and misremembered what it was.

    Well, I guess that absolves GPS and makes it more an issue in the base FW.

  • 0 over 5 years ago

    Try killing Galileo.  I tried a few trail runs with it, hoping it would give me a cleaner track, but it ended up making my runs FAR less accurate.  Back to GPS + GLONASS, and all is well.

  • 0 over 5 years ago

    Do a hard reset (reboot the watch basically). Press and hold top left until shuts down, then restart. Sync first if you don't want to lose any steps etc.

  • 0 over 5 years ago in reply to Dr Phil

    I thought the watch rebooted itself after doing the sw update already?

    Are you suggesting this is a one-off reboot requirement, or that it's now broken such that users must regularly manually reboot before recording an activity?

    Either way seems pretty poor.

  • 0 over 5 years ago in reply to winfij

    I've always treated updates to my watches like my Windows computer and rebooted after installing new sofware, irrespective of whether it's shutdown and restarted. So no I am not suggesting that it's necessary, just that it might be a preferred step.

    The other thing to ensure after an update is that you get a good GPS fix before starting your first activity. It's just possible that your CPE file is/was out of date. It's just possible you did not have a good GPS lock, it lost it then struggled to regain it.

    How was the ride home? Was this a one-off or has it been repeated?

  • 0 over 5 years ago in reply to Dr Phil
    Dr Phil said:
    How was the ride home? Was this a one-off or has it been repeated?

    I'll post here later tonight when I get home Slight smile

  • 0 over 5 years ago in reply to winfij

    Turns out the ride home was fine, as was the ride in this morning.

    So, an isolated problem?

    Still not great, but whatever.

  • 0 over 5 years ago

    My guess is that the update cleared the CPE (no recent satellite data to bootstrap the GPS) and that as a result, it took unusually long to acquire signal.

  • 0 over 5 years ago in reply to rtperna

    Galileo is not fully deployed yet but is definitely more accurate when coverage is good.

    For now, you should always check the estimated coverage at any given point in space and time before using it:

    https://galmon.eu/experimental/geo/coverage.html

    You will also see on the same website that GPS & Beidu can also be patchy at times...