There is a GPS problem with tunnels and so

Hexxer said:

So the Fenix 6 have som magical Sensor inside?

Not sure how the F6 did it, but definitely not with GPS. There is no chance to receive GPS signal in a tunnel, indoors (except near windows), or under water. F6 probably used accelerometer and gyro to estimate the track. Possibly that method was abandoned at Epix 2, because it was inaccurate too, and led to many complaints from users. As I wrote, get a speed sensor, it costs just a few bucks and it is the most accurate method to measure the distance.

Hexxer said:

As you can see here (i cant Upload direct in the answer) with the Fenix6 it was perfect

Well, from screenshots it is clear that the track is straight too, and does not follow the curve, so it was not corrected by any algorithm using the accelerometer and gyro. Just the distance was adjusted using your average speed, or interpolating the speed at the beginning of the tunnel and at its end. Looking at the speed colors on both graphs, I see they vary significantly, hence the estimates will vary too. Getting the speed sensor still remains the best advice.

I realize that "it" interpolates. But at least it is done. I have 3 tunnels on the round.

Oh yes, the German support said "The clock must first get used to me"....absolut unusable. That's not a leg break for me, but should be feasible for a company like Garmin.

Would I now, because I'm allowed, so drive through the Elbtunnel I would be missing on my 20km round 3.3km - because even interpolated that's better than the crap the F7 / Epix calculated there.

The interpolation will never work reliably. It may work in some situations, but will fail in others. Curves, stops, etc will mess it up anyway. With F6 it might have been working in your situation, but it might have been worse in others. Get the speed sensor, it costs almost nothing, and will assure that you get the most accurate data regardless of the situation. 

That is not the point at all. In Shell, this is a simple if/the/else loop and has nothing to do with accuracy and co. I wear the F6 and also the Epix, or Garmin in general, long enough. My wife wears a simple Fitbit and it can do that as well as the Fenix6.

I wouldn't even expect this to happen on the watch, it only cost 700€ and the processor shouldn't be overloaded. But the web frontend should be able to interpolate server-side, at the latest.

After all, the German Garmin support expected that the clock must first get used to me. I stroked it and gave it affectionate names, but it was nasty and refused to cooperate.

You have two basic options:

1. Go on complaining and wait a few years hoping to get an improved firmware once (forget any postprocessing on the server - that's won't happen at Garmin, it is against their policies)
2. Buy the speed sensor and enjoy accurate data instantly

Well, you could also return your Epix 2, and use another device meeting your needs better.

That means that you do not have to use the forum when you criticize? So rather buy new and write here only good? So I am neither brought up nor do I live so and always duck away when I see / find errors. Others are welcome to do that, but they are not allowed to complain when bugs appear without end and no one reports them. Probably the end of song is that you rather have to buy something new instead of saying that something is stupid.

Hexxer said:

That means that you do not have to use the forum when you criticize?

Oppositely, you certainly can - it is the option one, that I suggested. Just do not expect it will quickly change something. If you want an instant solution, use the option two.

solved