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

GPS problem in first 4-6 minutes

Hello everyone!

Hello tech support Garmin!

 

Six months have passed, and the problem has remained in its place. The same scenario. The first 4-6 minutes watch does not catch satellites. More precisely, they show that they catch, but they don’t. Below are examples of what is happening. No, these are NOT jammers. I’m waiting 4-6 minutes before my run. Buildings are no obstacle to the watch - running with friends on the same route proves it. Running in the opposite direction this place my watch records the perfect track. Starting in different locations gives the same results. At the same time - if you turn on the watch, catch satellites, but do not start the training and run for about 5 minutes, and then turn on, the exercise will record normally! It started from FW 12.23!!! In September last year!!!

Guys, if you can’t fix your product, at least give the option to rollback to the version when the watch worked normally! Look around how many people suffer with bugs! Yes, if you turn on the option of rolling back, it will be harder to find and fix bugs. But people would be happier. Wouldn’t be? And now the problems are not solved, and just go from version to version firmware.

 

My current settings:

FW 14.17 (starting with firmware 12.23)

3D speed / 3D distance off

GPS doesn’t matter.

GPS ver.: 2.37

CIQ: 4.2.0

BMX: 11.0.3

CIAM 11.00.03

ANT/BLE/BT: 24.78

TSC: 1.14

Sensor Hub: 23.09

ETE: 6.14.9.1

LHE: 2.1.5.1

Ephemeris: Current

 

At the same time, the watch works without complaints in other functions! But why do I have to run 1 km to catch the satellites in training? Half a year… day by day?

Friends, I understand that work is going on. I understand that there are real people behind all this work... but six months without changes is a fiasco.

If you can’t fix a bug, then give the opportunity to return to that firmware when the watch worked normally! Why make people use a buggy product?

 

https://connect.garmin.com/modern/activity/10632861838

https://connect.garmin.com/modern/activity/10592270404

https://connect.garmin.com/modern/activity/10626142610

https://connect.garmin.com/modern/activity/10612130897 - start with delay – check it. NO jams.

  • The watch was a gift from colleagues and brought to my region from another country. Garmin warranty does not worldwide. I do not consider that the problem is solved. The issue remains open. Anyway, thank you for your replay. Hope you can solve the problem as soon as you can.

  • If that were true, then all the other gadgets with gps have had the same probles. The photo is someone's fantasy actually.
    In any case, I don't want to get into a discussion of that. Just trust that many athletes use their watches and everything goes fine. And in those areas, too.

  • I provided a real scenario related to the problem. That problem is not because of the area or jammers. Let me tell you a secret - they (jammers) work differently and on different frequencies.

  • GNSS signals are very low power. If something overpowers the 1.6GHz band a receiver will have trouble. If they also broadcast at 1.2Ghz, even multiband mode will struggle.

    Because these frequencies are line-of-sight if perhaps a road's direction aligns with a transmitter, the interference will affect receivers with line of sight to the transmitter along that road. Once the receiver moves away from that line, buildings and vegetation will reduce the interfering signal, even if the transmitter is on high ground.

    The British military regularly tests GPS jamming off the far northwest corner of Scotland. It usually warns shipping and aviation when it does.

    My suggestion is to start the run away from that main road, in a region where you have in the past had a clean GPS track. This would prove whether or not there is something on that road which causes problems.

  • https://connect.garmin.com/modern/activity/10652561347

    I've already tried it. Ran a trail. The result was the same. The first 5 minutes the gps couldn't lock. Then it was perfect. Same scenario. Regardless of the location.
    I have written before, but I will write it again. As soon as I bought the watch everything was perfectly fine. But after installing the FW 12.xx it became like that in subj.
    I keep my hope alive and waiting for an update of the gps module up to 2.40 or higher.

  • Seems you are not alone - although possibly a slightly different issue. I guess you did speak to support also. This thread is long now to scroll back through.

    forums.garmin.com/.../1591862

  • Looks similar, but the problem here is different. My local suppurt can't help me because of Garmin's warranty is not a worldwide. Actually I tried to replace my system files by files from other FR955. On next run will check if there any changes.

  • From that track it looks like the first and last 1km was perfect, then there was some interference in the wooded area which affected both the outward and (to a lesser extent) the return part of the run, with all the rest of the route tracked correctly.

    Losing lock in an area when going under trees is not unusual, especially if you're in GPS-only mode. That's what multiband mode is supposed to mitigate.

  • No, just at the beginning. On the way back, I ran a little aside. On the other path. Everything is perfectly drawn there. These area I've run many times. My old Fenix 5 has never lost connection. And here's a premium watch and this all. Oh, come on... Sounds like a joke.
    I run with All + Multi-Band.