Via-punt niet herkend - te kleine marge

[Stefan Hummelink]

@Nick-Carthew Oh Gosh ... Getting a Brit aroused is way beyond my expectations and certainly not a what I call positive collateral hahahahahaha.

[Con Hennekens]

@Nick-Carthew, I am glad for you that you reach such a state on written words alone I am the first to admit my knowledge on the subject is rather slim. I am just trying to wrap my head around the problem at hand.

@Stefan-Hummelink, yes I am aware that the app itself does not talk directly to the hardware. But if devs want to solve this, they first must know what to solve. In my imagination, while the hardware switches from antenna to antenna, there will be a short moment of "no data" while the signal strength is high. The problem is that switching antennas can happen literally ANY time. implementing an internet connection bandwidth test will NOT prevent the hardware from switching towers, resulting in a short "no data" phase. If we know that, for example, the "no data" phase of such a switch is 20ms, dev could perhaps implement a second calculation event 50ms after the first one fails. Probably enough to overcome a no data phase, and little enough for anyone to notice. All completely hypothetical of course.

@Nick-Carthew, are you okay?

[Nick Carthew]

@Con-Hennekens said in Via-punt niet herkend - te kleine marge:

@Nick-Carthew, are you okay?

I'm lying back now and having a cigarette

[Con Hennekens]

@Nick-Carthew said in Via-punt niet herkend - te kleine marge:

I'm lying back now and having a cigarette

[Reinier007]

Today I drove on the A12 near Gouda and saw 2 times that the app was going offline for a moment. Just a few seconds and than it was back again. That’s a problem I’ve never had before. This must be a bug in the MRA-app.

[Tom Cat]

I experienced the same issue as the OP this week. At first I thought maybe my waypoint was off the road. I knew where I was going so it didn't matter but when I got home and checked the route, the waypoint was on the road.

It also happened at the end of two different routes with my endpoint. I rode through the final waypoint and it kept trying to route me back to it. I am using a Pixel 7 and this happened once on my phone and twice through Android Auto.

[Con Hennekens]

@Tom-Cat said in Via-punt niet herkend - te kleine marge:

I rode through the final waypoint and it kept trying to route me back to it.

This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.

[Tom Cat]

@Con-Hennekens said in Via-punt niet herkend - te kleine marge:

@Tom-Cat said in Via-punt niet herkend - te kleine marge:

I rode through the final waypoint and it kept trying to route me back to it.

This is by design. If you pass the finish, it will keep calculating to it, in case you need the assistance.

This is a bit unusual. I've never seen that in a navigation app before.

[Stefan Hummelink]

@Tom-Cat I prefer it that way though!

[Jack van Tilburg]

I find it inconvenient. Extra work and annoying.

[Con Hennekens]

@Jack-van-Tilburg, it's ideal. You don't have to restart the route of you need to go around the block. It's VERY convenient. About what extra work are you talking?

Thereby, it has been discussed before. It's by design, so it is what it is.

[Jack van Tilburg]

@Con-Hennekens said in Via-punt niet herkend - te kleine marge:

Thereby, it has been discussed before. It's by design, so it is what it is.

So no further reaction is necessary.