MyRoute-App - worst navigation experience ever
-
@Hans-van-de-Ven-MR-MRA
z.B.: https://www.myrouteapp.com/de/social/route/10113994?mode=share
I would start by placing the points well on the road line. If you have a ferry crossing in your route, point 4, use the route optimization "Shortest" (toolkit), this currently only works with the car profile. Furthermore, I would definitely add some more points on the last 100 KM if you don't want to drive on the highway
-
Thank you very much for your effort, but what you corrected (those detours) were precise destinations with street names and house numbers
and possibly dead ends. Nevertheless, the sat nav should have taken me there, which it did.
Nowhere in the instructions does it say that you should set a waypoint every 20 kilometres. If you're planning a long journey with lots of stopovers, that might be fun, but that's not why I chose MRA, it was simply to have the option of splitting the journey into different road profiles.
The journey to the Rhine was only the 9th test to see whether the app works at all. But I also think that the main problem is the interaction with AA. With the app only on the phone, at least I never had this voice output problems. However, this is not really an option. Because I need the vehicle-specific touch display for AA in my field of vision. The phone is not placed in the direct field of vision and also has to display another app while driving and I don't want to plaster the windscreen on my face.
If there was some clear trigger or error message, or if it was always the same things that led to the failure, I would have already sought help. But this diffuse failure certainly requires a lot of effort to find the cause, especially if AA is also involved. I don't want to test anymore how long the app works and when it fails, and then work on error messages. It really bothers me to have to look for a parking space or a suitable spot on the side of the road, restart the app and maybe even the whole smartphone, only to end up on Google Maps or similar alternatives. And to be honest, I can't imagine that a waypoint placed maybe 1 meter from the side of the road could be to blame for this. Maybe AA or MRA will make further progress in the next few months or years, but at the moment it can't offer me what I actually expected. But it was worth a try.
@Thomas-Piechocki said in MyRoute-App - worst navigation experience ever:
Nowhere in the instructions does it say that you should set a waypoint every 20 kilometres. If you're planning a long journey with lots of stopovers, that might be fun, but that's not why I chose MRA, it was simply to have the option of splitting the journey into different road profiles.
Ah - the reason behind that is that once underway on the day, if there is a traffic jam or a closed road, MRA will do it's best to get to the next waypoint. If you place the waypoints say 100km apart it gives the app a lot of leeway to go somewhere off-route, for the right reason of course, but it's disconcerting unless you notice the blocked road on the map. It's a minor detail, but that's annoyed me before until I worked out why.
The journey to the Rhine was only the 9th test to see whether the app works at all. But I also think that the main problem is the interaction with AA. With the app only on the phone, at least I never had this voice output problems.
The Android Auto side of the app is the newest part, and the least developed at this point. I don't use AA, so maybe I only get to see the sunny side of the app.
-
@Marinus-van-Deudekom
I would really like to know which of the 4 waypoints on my route are supposed to be "off the route"? And above all, where in the official instructions is such an on route / off route problem explicitly mentioned?https://unterstutzung.myrouteapp.com/de/support/solutions/articles/12000098593-app-routen-tracks
I haven't read anything about it and I think that I have followed the instructions correctly. As I said, my problem is not that the navigation is incorrect or deviates, but that the navigation app doesn't work at all. If it's not enough to read the instructions provided and I also have to watch loads of videos or use forums to use a navigation app easily, this should be communicated accordingly before purchase. So far, every nav app has accepted waypoints entered via address and implemented them correctly, why should it be any different with MRA and why is it not in the official instructions?
@Thomas-Piechocki
starting point:
This shows the start of the route inside a house and about 30/40 meters from the road itself.
Unless You're able to get your car inside that house you'll never get started at the beginning of the route. and thus the app will try to send you back. 2 sollutions, place the beginning of the route ON the road like in the picture below. Or start from the nearest waypoint.
routepoint 3: same story
routepoint 4
routepoint 5 (the finish) same story
Looking again at your route it's not what I would call a "fun" ride to take but most of all a navigation tools to get from Berlin to Frenkhausen with a couple of stops.
Tips to improve your ride:
place the routepoints ON the route
if, in your case your driving mostly on the Hiway place some extra routepoints on that hiway when it changes direction. make sure that those routepoints are on the wright side of the hiway to prevent a detour.
Make the routpoints of your stops a viapoint (hand symbol) placed ON the road.
for tha last bit of the trip add enough routepoints te make shure that the route goes as you want it tooThe tips we give you are free and it might be usefull if you would follow those.
have fun
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@Thomas-Piechocki
starting point:
This shows the start of the route inside a house and about 30/40 meters from the road itself.
Unless You're able to get your car inside that house you'll never get started at the beginning of the route. and thus the app will try to send you back. 2 sollutions, place the beginning of the route ON the road like in the picture below. Or start from the nearest waypoint.
routepoint 3: same story
routepoint 4
routepoint 5 (the finish) same story
Looking again at your route it's not what I would call a "fun" ride to take but most of all a navigation tools to get from Berlin to Frenkhausen with a couple of stops.
Tips to improve your ride:
place the routepoints ON the route
if, in your case your driving mostly on the Hiway place some extra routepoints on that hiway when it changes direction. make sure that those routepoints are on the wright side of the hiway to prevent a detour.
Make the routpoints of your stops a viapoint (hand symbol) placed ON the road.
for tha last bit of the trip add enough routepoints te make shure that the route goes as you want it tooThe tips we give you are free and it might be usefull if you would follow those.
have fun
Many thanks for your advice. The issue of the starting point has already been discussed here. I would just like to say that so far every Android sat nav app and my internal vehicle sat nav accepts my home address as the starting point and sets its routes from there and back again without forcing me through the walls of my living room. I have now learnt that with MRA I have to explicitly set the start to some point on a nearby road, but that is not the real problem. The other waypoints you showed were entered as an address with a house number, exactly as described in the official MRA instructions, and that's exactly where I wanted to go. That can't be wrong! My problem on this route was that at some point after waypoint 4, the voice announcements stopped. In the dark and in heavy rain, however, the failure of the voice output is a complete no-go. I haven't the slightest idea how you think setting waypoints could cause or justify the failure of an essential MRA function. If it were not possible to set waypoints by entering an address, this would have to be mentioned and the application would simply not be ready for the market, period. But apart from the necessary workaround with the start point, I still see no error in my route and no cause for the various massive problems of MRA that make its use pointless. I have no idea why and where I should start again with the route planning to make it better. The route would look the same today apart from the start.
And at this point to @Hans van de Ven MR.MRA (because the forum only allows posts every 60 minutes): Thank you for the advice. But no, I didn't want to take the ferry across the Rhine, I wanted to go exactely there, where the car park of a restaurant is located.
I actually only set waypoints to reach intermediate destinations or to define certain road profiles, regardless of whether the route is 600 or 1200 km long. I always assumed that the sat nav would choose the route itself depending on the desired profile (motorway - extremely winding). -
@Con-Hennekens said in MyRoute-App - worst navigation experience ever:
In the settings of the app, you explicitly configure online or offline use. I think it is a courtesy that you are warned and given a choice if you want to break the explicitly configured options. If that all is too much of an effort, it is better to stick to a simpler app indeed.
not a simpler app, just a smarter one
anyway, I'm not here to bash the MRA team, I was just trying to say what's the main shortcoming of this app. And I'm aware some don't like it and some do, so let's just use whatever float our boats and be happy all together
@cvlmtg said in MyRoute-App - worst navigation experience ever:
not a simpler app, just a smarter one
No, I really think a simpler one. You cannot automate a thinking process for everyone in general. What is smart for you, can be very dumb for me (en vice versa of course). Many features lead to many switches and toggles and sometimes it is too much for the one, while the other desires even more.
I'm not here to bash the MRA team
That's fine, I was not trying to bash back either
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Marinus-van-Deudekom
I would really like to know which of the 4 waypoints on my route are supposed to be "off the route"? And above all, where in the official instructions is such an on route / off route problem explicitly mentioned?https://unterstutzung.myrouteapp.com/de/support/solutions/articles/12000098593-app-routen-tracks
I haven't read anything about it and I think that I have followed the instructions correctly. As I said, my problem is not that the navigation is incorrect or deviates, but that the navigation app doesn't work at all. If it's not enough to read the instructions provided and I also have to watch loads of videos or use forums to use a navigation app easily, this should be communicated accordingly before purchase. So far, every nav app has accepted waypoints entered via address and implemented them correctly, why should it be any different with MRA and why is it not in the official instructions?
@Thomas-Piechocki said in MyRoute-App - worst navigation experience ever:
I would really like to know which of the 4 waypoints on my route are supposed to be "off the route"? And above all, where in the official instructions is such an on route / off route problem explicitly mentioned?
Personally I think some people stress too much about off-road placed waypoints too. Usually the app is not very critical about it. Just in urban areas with many small streets next to each other it leads to problems. Where it can also lead to problems is when you pass such a point but not really "hit" it. The app will make you turn around for a while and eventually skip it, along with other points. So in your example, iiuc, your waypoints are obligatory stops. Turn them into via points (hand shape) so they do not get skipped unintentionally.
Placing waypoints that far from each other basically means that you don't care how you get from one to the other. You are leaving a lot of interpretation on the route to the device, and to circumstances (traffic e.g.).
What might be of interest for your specific use (which does not look like scenic routing, for which the app is originally intended), is that in upcoming updates a lot of work is done on a great track-navigation experience. That might fit your needs probably more.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
Many thanks for your advice. The issue of the starting point has already been discussed here. I would just like to say that so far every Android sat nav app and my internal vehicle sat nav accepts my home address as the starting point and sets its routes from there and back again without forcing me through the walls of my living room. I have now learnt that with MRA I have to explicitly set the start to some point on a nearby road, but that is not the real problem. The other waypoints you showed were entered as an address with a house number, exactly as described in the official MRA instructions, and that's exactly where I wanted to go. That can't be wrong! My problem on this route was that at some point after waypoint 4, the voice announcements stopped. In the dark and in heavy rain, however, the failure of the voice output is a complete no-go. I haven't the slightest idea how you think setting waypoints could cause or justify the failure of an essential MRA function. If it were not possible to set waypoints by entering an address, this would have to be mentioned and the application would simply not be ready for the market, period. But apart from the necessary workaround with the start point, I still see no error in my route and no cause for the various massive problems of MRA that make its use pointless. I have no idea why and where I should start again with the route planning to make it better. The route would look the same today apart from the start.
And at this point to @Hans van de Ven MR.MRA (because the forum only allows posts every 60 minutes): Thank you for the advice. But no, I didn't want to take the ferry across the Rhine, I wanted to go exactely there, where the car park of a restaurant is located.
I actually only set waypoints to reach intermediate destinations or to define certain road profiles, regardless of whether the route is 600 or 1200 km long. I always assumed that the sat nav would choose the route itself depending on the desired profile (motorway - extremely winding).@Thomas-Piechocki said in MyRoute-App - worst navigation experience ever:
The issue of the starting point has already been discussed here. I would just like to say that so far every Android sat nav app and my internal vehicle sat nav accepts my home address as the starting point
They don't. They just start where you are, you do not enter a starting address when you start an AtoB route, do you?
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Thomas-Piechocki said in MyRoute-App - worst navigation experience ever:
The issue of the starting point has already been discussed here. I would just like to say that so far every Android sat nav app and my internal vehicle sat nav accepts my home address as the starting point
They don't. They just start where you are, you do not enter a starting address when you start an AtoB route, do you?
No, I enter a starting point (e.g. home) and a destination and then have the route calculated.
-
@Thomas-Piechocki said in MyRoute-App - worst navigation experience ever:
I would really like to know which of the 4 waypoints on my route are supposed to be "off the route"? And above all, where in the official instructions is such an on route / off route problem explicitly mentioned?
Personally I think some people stress too much about off-road placed waypoints too. Usually the app is not very critical about it. Just in urban areas with many small streets next to each other it leads to problems. Where it can also lead to problems is when you pass such a point but not really "hit" it. The app will make you turn around for a while and eventually skip it, along with other points. So in your example, iiuc, your waypoints are obligatory stops. Turn them into via points (hand shape) so they do not get skipped unintentionally.
Placing waypoints that far from each other basically means that you don't care how you get from one to the other. You are leaving a lot of interpretation on the route to the device, and to circumstances (traffic e.g.).
What might be of interest for your specific use (which does not look like scenic routing, for which the app is originally intended), is that in upcoming updates a lot of work is done on a great track-navigation experience. That might fit your needs probably more.
Thank you very much for the tips and advice on waypoints and route creation. But to be honest, I don't have a problem with that at all. On my example route, I was taken exactly where I wanted to go, without turning or driving in circles, everything was fine - until the cancellation. Of course, everyone has different ideas and expectations of the route planner, I haven't made any criticisms in this regard. My requirements are always the same: I want to get from waypoint to waypoint as quickly as possible, be it on the motorway or on winding roads. That's why the necessary interruption when the MRA sat nav stops working bothers me so much. I just want to enjoy driving fast and not have to worry about sat nav problems. I think I'll keep trying to see if there has been any progress in the stability of MRA in conjunction with AA, but I won't use it regularly on my journeys. The potential is definitely there and I like MRA's display better than other alternatives.
-
Thanks for the discussion here.
Just quickly a response from me:
- waypoints not exactly on route should never ever really lead to any problem. If the route is calculated, there is a map matched location of the waypoint that is on route
- Android Auto does sometimes have stability issues which we continuously keep improving especially since the last 2 updates (4.3.2 and 4.3.3)
- Every user uses MRA differently and that should just work
- Starting from nearest waypoint should definitely not be an issue anymore unless that has been explicitly turned off
@Thomas-Piechocki that said, your biggest two issues would then be audio and Android Auto stability?
-
Thanks for the discussion here.
Just quickly a response from me:
- waypoints not exactly on route should never ever really lead to any problem. If the route is calculated, there is a map matched location of the waypoint that is on route
- Android Auto does sometimes have stability issues which we continuously keep improving especially since the last 2 updates (4.3.2 and 4.3.3)
- Every user uses MRA differently and that should just work
- Starting from nearest waypoint should definitely not be an issue anymore unless that has been explicitly turned off
@Thomas-Piechocki that said, your biggest two issues would then be audio and Android Auto stability?
Exactly. I have no complaints about the navigation performance itself. My problem is that the app simply stops working after a few hours. Very often the voice output suddenly stops. Or only the local position is displayed, but no further navigation instructions and no local route properties such as speed limit. In these cases, I have tried restarting the MRA app and also restarting the entire phone. But when I called up MRA, I kept coming back to exactly the same point: either no sound, or only position display without navigation information for the saved route, or neither. Then you simply switch to another sat nav app and everything works perfectly for the next few hours. The next morning on the return journey, I tried again with MRA with a simple route from A via B to C. Everything was fine for the first few minutes, then a two-hour walk (phone stayed in the car) and then five kilometres further on the sound and navigation disappeared. Then two hours of trouble-free driving with Google Maps. Then tried MRA again (the waypoint now behind is skipped), sat nav works perfectly for about 30 minutes, then no sound. These are my problems with MRA.
-
Exactly. I have no complaints about the navigation performance itself. My problem is that the app simply stops working after a few hours. Very often the voice output suddenly stops. Or only the local position is displayed, but no further navigation instructions and no local route properties such as speed limit. In these cases, I have tried restarting the MRA app and also restarting the entire phone. But when I called up MRA, I kept coming back to exactly the same point: either no sound, or only position display without navigation information for the saved route, or neither. Then you simply switch to another sat nav app and everything works perfectly for the next few hours. The next morning on the return journey, I tried again with MRA with a simple route from A via B to C. Everything was fine for the first few minutes, then a two-hour walk (phone stayed in the car) and then five kilometres further on the sound and navigation disappeared. Then two hours of trouble-free driving with Google Maps. Then tried MRA again (the waypoint now behind is skipped), sat nav works perfectly for about 30 minutes, then no sound. These are my problems with MRA.
@Thomas-Piechocki Interesting, thanks!
And that was all with Android Auto? -
OMG!
It's an old song, but 'How Long Has This Been Going On' (ACE 1974). Listen to the song and read the lyrics at YouTube.I mean the discussion in this topic and the ever continuing answers: Will someone ever be convinced or will this discussion never stop?
-
@Thomas-Piechocki Interesting, thanks!
And that was all with Android Auto?yes.
-
OMG!
It's an old song, but 'How Long Has This Been Going On' (ACE 1974). Listen to the song and read the lyrics at YouTube.I mean the discussion in this topic and the ever continuing answers: Will someone ever be convinced or will this discussion never stop?
Well then, be glad that I haven't turned to the forum every time over the last six months, but only shared my experience at the end. As various people have suggested that incorrect route planning may be one of the causes, I wanted to set the record straight. And I think it's polite to answer questions. But don't worry, everything has been said and the subject is closed for me, so you can get back to more enjoyable things.
-
Just a question.
How do you connect your phone to AA?@Corjan-Meijerink did explain it already. The stability of MRA in AA or ACP not there yet. Because of this.
How you connect to AA can affect MRA more than other apps.Besides this
AA and ACP have some limitations.
With apps like Google Maps you do not notice this so much. But when you starting using an app like MRA or TomTom Go for riding a pre-planned route. You will see those limitations.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Just a question.
How do you connect your phone to AA?@Corjan-Meijerink did explain it already. The stability of MRA in AA or ACP not there yet. Because of this.
How you connect to AA can affect MRA more than other apps.Besides this
AA and ACP have some limitations.
With apps like Google Maps you do not notice this so much. But when you starting using an app like MRA or TomTom Go for riding a pre-planned route. You will see those limitations.@M-Schrijver
The connection is made via Bluetooth. -
@cvlmtg said in MyRoute-App - worst navigation experience ever:
not a simpler app, just a smarter one
No, I really think a simpler one. You cannot automate a thinking process for everyone in general. What is smart for you, can be very dumb for me (en vice versa of course). Many features lead to many switches and toggles and sometimes it is too much for the one, while the other desires even more.
I'm not here to bash the MRA team
That's fine, I was not trying to bash back either
@Con-Hennekens said in MyRoute-App - worst navigation experience ever:
not a simpler app, just a smarter one
No, I really think a simpler one. You cannot automate a thinking process for everyone in general. What is smart for you, can be very dumb for me (en vice versa of course). Many features lead to many switches and toggles and sometimes it is too much for the one, while the other desires even more.
Can't think of any situation where I need a switch to tell the app not to use the internet because there is no internet.
-
@Con-Hennekens said in MyRoute-App - worst navigation experience ever:
not a simpler app, just a smarter one
No, I really think a simpler one. You cannot automate a thinking process for everyone in general. What is smart for you, can be very dumb for me (en vice versa of course). Many features lead to many switches and toggles and sometimes it is too much for the one, while the other desires even more.
Can't think of any situation where I need a switch to tell the app not to use the internet because there is no internet.
@cvlmtg said in MyRoute-App - worst navigation experience ever:
Can't think of any situation where I need a switch to tell the app not to use the internet because there is no internet.
That switch is there to prevent data usage when there actually IS an internet connection. Also to prevent the app from accidentally using internet data when you don't want that. It's not that difficult...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Thomas-Piechocki Interesting, thanks!
And that was all with Android Auto?@Corjan-Meijerink sort of off topic but here is something that I discovered with Android Auto and my Africa Twin which might help some folk.
I recently got a new phone a Motorola edge 40 neo (Android14). When I used it for Android Auto plugged into the car for AA or if I tried it on my Africa Twin it would invariably operate normally for a while, then repeatedly cycle on and off AA every couple of minutes. I never had this when using my old Motorola G8 or G7. I tried a few different leads and that did not make any difference, then I tried using wireless AA in the car and it never glitched. Long story short after a lot of Googling and my own observations, I realised that the glitching started when the phone Battery was 100% full. Some phones are set up so that Android issues regular notifications when the battery is 100% full. Flashing the phone screen at a regular interval (completely pointless??). This appears to cause Android auto to glitch. Anyhow, I turned this notification off on the phone (not easy to find as its part of the OS) and have had no issues since. My old MotoG8 (Android 11) and my wifes old MotoG7 (Android 10) had the 100% charged warning switched off by default. This might help someone who is having similar issues.
The glitch affected all apps.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
