v5.2 (473) Feedback
-
I just finished a 10 day, 4900mi trip, where I followed the planned routes, as well as recorded the tracklog. This years trip leader created the routes in Google Maps, and I created the routes in the MRA Webplanner based on those so I could follow along. All good.
I had recently purchased a Carpuride 702 to use via the CarPlay function, and as it turns out, was one great decision - it worked very well.
So I'll start with this - I have to say I was pleasantly surprised at how well this version worked.
That said, there were some annoying issues. I had previoulsy tried to use the NN app and tracklog with much less than satisfaction.
Details:
-
Navigation/GPS - started each days route & tracklog via the 702.
- at NO TIME did I even entertain using the NN app as the daily temps were in excess of 90deg F most days, and with the extreme battery usage the app uses, it would have been an excercise in futility.
- the 702 never dimmed or lost brightness, so it was actually a pleasure to be able to see the entire route each and every day - shout out to Carpuride.
-
Waypoints - for the most part, this worked well - auto skip was on - if the route detour appeard to be small. However, there were 3 instances where the auto skip did not work well AT ALL. Beacuse I was only following, I did not go into Waypoints and delete the troublesome point, I let it run to see what would happen.
- on at least 2 of these occasions, the app continually tried to re-route me back to that waypoint (yes, I know the difference between a waypoint and a via point) FOR OVER 20mi and at least 6 - 7 voice attempts to re-route. It's my understanding that after 3 attempts, the waypoint is skipped and on to the next - THIS did not happen - unacceptable for any group leader - luckily, it wasn't me this year.
-
Tracklog - very substantial improvement here, IMO, compared to the last time I used this function.
- the only issue is when saving the tracklog...it MUST be a VERY good internet connection. I found that on an iphone with 2 bars of service in a 5G+ area simply did not work. Because of this, I did lose that days tracklog. Worked flawlessly on a good WiFi connection every time.
-
Crashing each time the bike was stopped (for gas, food, the night, etc), EACH & EVERYTIME upon start up, the app crash error came up on the iphone. E.A.C.H and E.V.E.R.Y.T.I.M.E
The crash issue even happens when the app is NOT EVEN USED AT ALL, and has not been started. At different version upgrades, the instances of crashes tends to dwindle, or almost go away. BUT it comes back with each and every new version release - baffling.
Fortunately, when it was time to continue the route, the Navigate message that shows up on the 702 worked well, and the route picked right back up. So did the tracklog.
The only real issue where this occured was the last 100mi of the trip - the 702 screen went blank. Tapping the screen to bring up the search/settings icons and attempting to restart the route with the search function did restart the route, and the distance box showed up and appeared to be working - HOWEVER, no actual map would display. When I opened the app on my iphone, the route was there, just as it should be - but nothing would carry over to the 702 (closing app, reopening, etc).
- managed to get everything back up and running once the iphone was rebooted. Once the phone was back on, I restarted route & tracklog via the 702.There were a couple other crashes that did the same things, but in those instances, simply opening the app on the phone, hard closing it, then re-opening on the 702 worked - it was the last crash that had the serious issues.
All in all, I have to admit that the app/702 CarPlay worked very well!!
I was very dissappointed with the app and had not used it in a very long time (as mentioned above, still won't use it standalone on the iphone for said issues), however, with the continued improvements and the 702 CarPlay abilities, has re-installed my faith that things are moving in the right direction. May it continue.
-
-
undefined Nick Carthew moved this topic from [Web] Problems, Bugs and other Issues
-
Thanks for sharing this report!
Then I have great news for you because the issues you mentioned are all solved in the next update
I've dedicated all my time to stability improvements in 5.2.1 and the results are promising.Expecting public release next week. Google is a bit slow in reviewing....
-
I just finished a 10 day, 4900mi trip, where I followed the planned routes, as well as recorded the tracklog. This years trip leader created the routes in Google Maps, and I created the routes in the MRA Webplanner based on those so I could follow along. All good.
I had recently purchased a Carpuride 702 to use via the CarPlay function, and as it turns out, was one great decision - it worked very well.
So I'll start with this - I have to say I was pleasantly surprised at how well this version worked.
That said, there were some annoying issues. I had previoulsy tried to use the NN app and tracklog with much less than satisfaction.
Details:
-
Navigation/GPS - started each days route & tracklog via the 702.
- at NO TIME did I even entertain using the NN app as the daily temps were in excess of 90deg F most days, and with the extreme battery usage the app uses, it would have been an excercise in futility.
- the 702 never dimmed or lost brightness, so it was actually a pleasure to be able to see the entire route each and every day - shout out to Carpuride.
-
Waypoints - for the most part, this worked well - auto skip was on - if the route detour appeard to be small. However, there were 3 instances where the auto skip did not work well AT ALL. Beacuse I was only following, I did not go into Waypoints and delete the troublesome point, I let it run to see what would happen.
- on at least 2 of these occasions, the app continually tried to re-route me back to that waypoint (yes, I know the difference between a waypoint and a via point) FOR OVER 20mi and at least 6 - 7 voice attempts to re-route. It's my understanding that after 3 attempts, the waypoint is skipped and on to the next - THIS did not happen - unacceptable for any group leader - luckily, it wasn't me this year.
-
Tracklog - very substantial improvement here, IMO, compared to the last time I used this function.
- the only issue is when saving the tracklog...it MUST be a VERY good internet connection. I found that on an iphone with 2 bars of service in a 5G+ area simply did not work. Because of this, I did lose that days tracklog. Worked flawlessly on a good WiFi connection every time.
-
Crashing each time the bike was stopped (for gas, food, the night, etc), EACH & EVERYTIME upon start up, the app crash error came up on the iphone. E.A.C.H and E.V.E.R.Y.T.I.M.E
The crash issue even happens when the app is NOT EVEN USED AT ALL, and has not been started. At different version upgrades, the instances of crashes tends to dwindle, or almost go away. BUT it comes back with each and every new version release - baffling.
Fortunately, when it was time to continue the route, the Navigate message that shows up on the 702 worked well, and the route picked right back up. So did the tracklog.
The only real issue where this occured was the last 100mi of the trip - the 702 screen went blank. Tapping the screen to bring up the search/settings icons and attempting to restart the route with the search function did restart the route, and the distance box showed up and appeared to be working - HOWEVER, no actual map would display. When I opened the app on my iphone, the route was there, just as it should be - but nothing would carry over to the 702 (closing app, reopening, etc).
- managed to get everything back up and running once the iphone was rebooted. Once the phone was back on, I restarted route & tracklog via the 702.There were a couple other crashes that did the same things, but in those instances, simply opening the app on the phone, hard closing it, then re-opening on the 702 worked - it was the last crash that had the serious issues.
All in all, I have to admit that the app/702 CarPlay worked very well!!
I was very dissappointed with the app and had not used it in a very long time (as mentioned above, still won't use it standalone on the iphone for said issues), however, with the continued improvements and the 702 CarPlay abilities, has re-installed my faith that things are moving in the right direction. May it continue.
on at least 2 of these occasions, the app continually tried to re-route me back to that waypoint (yes, I know the difference between a waypoint and a via point) FOR OVER 20mi and at least 6 - 7 voice attempts to re-route. It's my understanding that after 3 attempts, the waypoint is skipped and on to the next - THIS did not happen
The definite skip of a waypoint is at 5 recalculations I think, not at 3.
What happens at recalc 3 is that a new decision is made to skip the missed waypoint or not. Which it gets to be is dependent on your route layout, and distance to the next waypoint. Many parameters are in play here, which is why it sometimes is considered illogical.the only issue is when saving the tracklog...it MUST be a VERY good internet connection. I found that on an iphone with 2 bars of service in a 5G+ area simply did not work. Because of this, I did lose that days tracklog.
I tracklog that did not upload is usually not lost. It goes into an upload queue, and a small up-arrow appears on your profile icon.
The crash issue even happens when the app is NOT EVEN USED AT ALL, and has not been started. At different version upgrades, the instances of crashes tends to dwindle, or almost go away.
I think it would be interesting to know if the same happens when the app is actually running on the phone in the background. But apparently Corjan already found the problem (hopefully!)
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.
Check out RideSleepRepeat.eu, a biker community for sharing stays across Europe
-
-
on at least 2 of these occasions, the app continually tried to re-route me back to that waypoint (yes, I know the difference between a waypoint and a via point) FOR OVER 20mi and at least 6 - 7 voice attempts to re-route. It's my understanding that after 3 attempts, the waypoint is skipped and on to the next - THIS did not happen
The definite skip of a waypoint is at 5 recalculations I think, not at 3.
What happens at recalc 3 is that a new decision is made to skip the missed waypoint or not. Which it gets to be is dependent on your route layout, and distance to the next waypoint. Many parameters are in play here, which is why it sometimes is considered illogical.the only issue is when saving the tracklog...it MUST be a VERY good internet connection. I found that on an iphone with 2 bars of service in a 5G+ area simply did not work. Because of this, I did lose that days tracklog.
I tracklog that did not upload is usually not lost. It goes into an upload queue, and a small up-arrow appears on your profile icon.
The crash issue even happens when the app is NOT EVEN USED AT ALL, and has not been started. At different version upgrades, the instances of crashes tends to dwindle, or almost go away.
I think it would be interesting to know if the same happens when the app is actually running on the phone in the background. But apparently Corjan already found the problem (hopefully!)
I think it would be interesting to know if the same happens when the app is actually running on the phone in the background. But apparently Corjan already found the problem (hopefully!)
appreciate the feedback/thoughts.
If I understand your point - the app is running in the background (I believe) when, in my case, I was doing everything from the 702 - and yes, each and everytime it crashed upon reastart after a stop (bike turned off).
Other than this, the app is always closed upon completion of the route, etc - so if it is still running in the background, I do not know why.
Hopefullly the new update resolves all the crash issues - even the ones that occur when the app has not been opened for weeks on end - looking forward to finding out.
Left out one comment on this trip:
Online/Offline - I had the Offline navigation set to off, as I like working online to see any potential upcoming traffic issues (traffic issues - worked 'ok' I guess....seems HERE maps are way behind in realtime related updates). There were plenty of times when there was no cell signal at all (10,950' elevation on the Going to the Sun Road in Glacier National Park, for example) and each time after a stop for a Kodak (picture) moment, when the bike was started up and the route coninued. the map/route and tracklog immediately picked up where it left off - awesome!
-
Just to add my experience from today regarding skipping of points. Please see the screenshot of the route below for reference. I currently run NN on my phone in my pocket with the screen turned off and just listen to the voice prompts. I do this alongside my Garmin Zumo which shows the route and also gives me voice prompts.
I avoided points 9 and 10 on the map due to roadworks/closures. On the Zumo (set to prompt to recalculate) I didn't recalculate, followed the posted diversion signs and rejoined the magenta line a bit further down the road. With NN I expected the app to skip point 9 and 10 after a number of attempts (I also thought 3). However, what actually happened was that NN persisted in trying to navigate me back to point 9. There were dozens of audio prompts until I got fed up with it and stopped the navigation just short of point 29 when the Zumo directed me to turn right and NN directed me to turn left, clearly trying to get me back to point 9.
I have the skip points automatically switched on. I run NN in offline mode.
-
Just to add my experience from today regarding skipping of points. Please see the screenshot of the route below for reference. I currently run NN on my phone in my pocket with the screen turned off and just listen to the voice prompts. I do this alongside my Garmin Zumo which shows the route and also gives me voice prompts.
I avoided points 9 and 10 on the map due to roadworks/closures. On the Zumo (set to prompt to recalculate) I didn't recalculate, followed the posted diversion signs and rejoined the magenta line a bit further down the road. With NN I expected the app to skip point 9 and 10 after a number of attempts (I also thought 3). However, what actually happened was that NN persisted in trying to navigate me back to point 9. There were dozens of audio prompts until I got fed up with it and stopped the navigation just short of point 29 when the Zumo directed me to turn right and NN directed me to turn left, clearly trying to get me back to point 9.
I have the skip points automatically switched on. I run NN in offline mode.
@Stevedo-6-0 Point 9 is a via point. Via points are never automatically skipped.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox BJ8 -
@Stevedo-6-0 Point 9 is a via point. Via points are never automatically skipped.
@Nick-Carthew - thanks for clarifying Nick
Earlier in the thread @con-hennekens stated that "The definite skip of a waypoint is at 5 recalculations I think, not at 3.
What happens at recalc 3 is that a new decision is made to skip the missed waypoint or not. Which it gets to be is dependent on your route layout, and distance to the next waypoint. Many parameters are in play here, which is why it sometimes is considered illogical."I've just re-read the manual (after reading Con Hennekens post) and have clarified for myself that a Waypoint can be either a Via Point or a Shaping Point which is why I believed that a Via Point could be skipped (from Con Hennekens assertions).
I think all responders in these threads need to be particularly careful when referring to any type of point on a route/track. In my experience, this is one area which can cause much frustration for many navigation app users (not just MRA).
PS on that final note what are "trip points" as mentioned in the Waypoints section of the manual? "MRA Routeplanner trip points can be exported to Garmin devices."
-
Hi,
ich verwende aktuell die Version 5.2.1 - 486 auf meinem iPhone 16 Pro.Ich hatte heute bei einer Tour mehrmals, dass die App nicht den aktuellen Standort angezeigt hat. Vielmehr war die Karte auf einen alten Tourabschnitt fixiert bzw. eingefroren!?
Weiterhin ist die Anzeige auf dem CarPlay Gerät mehrmals abgestürzt.
In den "alten" Versionen von MyRouteApp hatte ich die beiden beschriebenen Fehler nicht.Und nein, es liegt weder am iPhone noch am CarPlay Device, denn eine andere Routen-Software zeigte die beiden oben beschriebenen Fehler nicht!
Wäre für jede Hilfestellung dankbar.
-
@Nick-Carthew - thanks for clarifying Nick
Earlier in the thread @con-hennekens stated that "The definite skip of a waypoint is at 5 recalculations I think, not at 3.
What happens at recalc 3 is that a new decision is made to skip the missed waypoint or not. Which it gets to be is dependent on your route layout, and distance to the next waypoint. Many parameters are in play here, which is why it sometimes is considered illogical."I've just re-read the manual (after reading Con Hennekens post) and have clarified for myself that a Waypoint can be either a Via Point or a Shaping Point which is why I believed that a Via Point could be skipped (from Con Hennekens assertions).
I think all responders in these threads need to be particularly careful when referring to any type of point on a route/track. In my experience, this is one area which can cause much frustration for many navigation app users (not just MRA).
PS on that final note what are "trip points" as mentioned in the Waypoints section of the manual? "MRA Routeplanner trip points can be exported to Garmin devices."
@Stevedo-6-0, Nick is right (of course!
) I should have been more particular with the term shaping points instead of waypoints. But yeah, that VIA points don't skip automatically is considered more or less basic knowledge. It is their only function to never be skipped automatically The term "trip points" is very likely the Garmin counter part of the more general term "route points".
A waypoint is simply a location on a map, defined by it's coordinates. Waypoints can be stand alone points (Point of interest for example, or favorite points) or be part of a route, in which case we talk about route points. Route points can then be divided in shaping points (garmin uses the term soft points) that can be skippedm automatically if missed, or via points (hard points in garmin language) that can not be skipped automatically.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login-
09181
-
0431.1k
-
0778
-
010308
-
0352
-
06221
-
017342
