How to stop MRA asking to add to favourites to route?

[richard 3v]

@Corjan-Meijerink
Thankyou

[Con Hennekens]

@Corjan-Meijerink said in How to stop MRA asking to add to favourites to route?:

In that case you definitely have something “touching” your screen.

That's exactly what I was thinking...

@Malcolm-Bradley, I recommend a thorough cleaning of the screen, but it might also be broken.
The reason you do not have a continuous problem with other apps, might be that the MRA app actually has a screen covering function for long-pressing an area (add a waypoint). Not many apps have that.

[David Rudgley]

Don't you think that we'd realise that something was touching the screen? and your first thought that it was the user causing the problem ‍️

[Con Hennekens]

@David-Rudgley, to whom are you targeting your comment, and what do you really mean by it?

[Malcolm Bradley]

Many thanks all, there was definitely nothing touching the screen, the screen is clean, unbroken / uncracked and has an unbroken / uncracked screen protector covering the screen.
It was raining at the time but I don't see why the app should be susceptible to rain as I'm sure most people using the app live in countries where the screen gets wet.
Hopefully the update when implemented gets rid of this really annoying feature. It isn't needed and as someone earlier wrote - a real pain.
I'm not really sure, as this is an app targeting bikers predominantly, who thought introducing annoying pop-ups whilst riding would be a good thing.
Other than this, I'm happy with the app

[Con Hennekens]

@Malcolm-Bradley, no pop-ups are programmed to annoy bikers...
If you were driving during rainy conditions, that explains a lot. It is not the app that is susceptible to rain, but your phone (any phone) is. This is due to the way phone screens work: capacitive. A little explanation about this (which is mainly about LFDs but works for phones as well) is added below this message. Usually the common dedicated navigation devices use resistive touch technology. The XTs are capacitive though. All smartphones I know use capacitive technology, and are therefore sensitive to raindrops.

An already existing feature to prevent this has been implemented long time ago. While navigating, you will find a "lock screen" function in the settings (three dot menu). This makes the screen insensitive for raindrops (and finger touches ) but presents a small unlock button to unlock the screen again. The chances of a raindrop catching exactly that unlock spot is of course much smaller than it messing with the whole screen.

The newly introduced feature to help against rain messing things up, changes the way you can add waypoints or set a destination. That can still be done by a long-press, but the map needs to be panned (moved) a bit first. That is usually what you do when looking for waypoints to add or destinations to set anyway. The chance of a raindrop first moving the map and secondly long-pressing a spot are probably slim. But it is no guarantee rain will not mess up anything.

[Malcolm Bradley]

Thanks for your reply Con but...this has never happened before the most recent update. I've been using MRA in the rain for the past 2 years or so without ever having this happen.

[Con Hennekens]

@Malcolm-Bradley, I must admit I am a nice-weather-biker. I have seen my share of rain, but V5 not yet . However I cannot think of any reason why this would be different then it was in V4...

[Brian McG]

@Malcolm-Bradley it happens to me often enough due to rain & because I have my phone orientated quite horizontal/flat I often have to resort to the Lock Screen" function

this is NOT a v5 phenomenon

maybe the angle you mounted the phone was a little different to normal, maybe you were doing slightly slower speeds so there was more rain/water on the screen

[Corjan Meijerink]

Oh and to add to it, we added a new feature where tapping a POI on the map triggers this feature too as opposed to v4 where we only had a long press feature anyway.

Thus is makes sense that undesired touches can now be triggered more easily. As said! 5.0.1 will include a method to prevent this automatically along the existing “lock screen” feature.