Via-punt niet herkend - te kleine marge

[Stefan Hummelink]

@Con-Hennekens Well, I'm definitely not into the application side of the hardware, also known as Software muhaha, but the hardware itself really doesn't care about any drop of signal, from "good signal strength" to "almost none".

The issue with a drop of signal should be tackled in the software. The hardware can only do so much, but not solve the issue of having no signal, besides triggering it's BIT signals to the phones software.

[Con Hennekens]

@Stefan-Hummelink said in Via-punt niet herkend - te kleine marge:

The issue with a drop of signal should be tackled in the software.

Yes of course, but it would be handy for devs to know what they have to tackle in their software

[Stefan Hummelink]

@Con-Hennekens That's true, but unfortunately I cannot think of something that the hardware produces that helps in tackling this. I think the app talks to the phone software and not directly to the hardware itself, but I'm note sure about that since that is not my cup of tea.

I would perhaps try to get the actual data speed and based on that determine whether to trigger a recalculation. A "no data" report may be based on a hard limit, instead of being a "workable" limit. Not an issue if your going from great speed to bad speed after which the app moves from on- to offline, but the other way around would be a issue for going from off- to online. If the app checks for a "data present" status with the limit of the datarate being too low, the recalculation might not succeed.

Maybe the app should stop trying to recalculate if the datarate is just too low, and stay offline untill the datarate is above a pragmatically determined workable dataspeed.

[Nick Carthew]

@Stefan-Hummelink @Con-Hennekens As someone who has zero knowledge of any of the technical matters that you two are discussing, I find myself becoming slightly aroused with your conversation

[Dave J 0]

Not the only one @Nick-Carthew. This is fascinating @Stefan-Hummelink and @Con-Hennekens, and something I knew nothing about until now.

I know that the Dev Team are looking at testing speed of connection with the offline and online auto action following some feedback that others and I have given. I too have had similar issues to @Con-Hennekens with strong signal areas. Curious where this may end up and the solution. Intriguing thread guys.

[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

[reinier.beenengmail.com]

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.