Can't Acquire GPS Fix last few days

Mike 4 months ago

Since Monday my 255 Music is unable to aquire a GPS fix, despite being in the latest software version and in a clear view of the sky for more than 30 minutes.

Last Sunday everything worked as normal, with a fix being acquired within seconds. But now it seems impossible.

Anybody else with this issue?

Top Replies

Mike 3 months ago in reply to carlo3k +2

I mean, I just can't understand how it stops working consistently from one day to the other, and the only attempt at a solution is to reset the watch. And when that doesn't work, the only thing they…
Garmin-Sierra 4 months ago in reply to Mike +1

All,

If your watch is unable to locate satellites, please see Why Does My Garmin Watch Take So Long to Locate Satellites?

It doesn't look like we have any reports of this yet, but I will keep an eye out…
Mike 23 days ago +1

This issue went away by itself about a month ago. One day it just started working, not hard reset or anything, Instant GPS lock every time.

However, since last week it started happening again. I'm not able…

All Replies

0 Alex_____ 3 days ago

Same here since weeks

GPS lock now takes now up to 15–20 minutes (working time to time as expexted) and gps signal if often lost during run in open area, never occurred previously. I’ve tried everything factory reset, removing remoteSw files,.... but without improvements.

Looks more a sw issue than a hardware one, but can't find any rationale.

0 Alex_____ 3 days ago

Same here since weeks

Looks more a sw issue than a hardware one, but I can't find any rationale.

0 1853521 2 days ago

Each of my runs since 10 June had issues, either with obtaining a GPS lock or losing it during the run, typically varrying in duration from 5 to 30 minutes (basically ruining the run tracking or worse messing up navigation in races). Loses GPS lock in open fields too.

Tried different GPS and a reset, but doesn't make a difference. The linked document doesn't help either. Also, never had any issues with this in the 1.5 year before. Given the other reports, I suspect a software issue.