New beta v4.1.1 (294)
-
I forgot the default note “available within a few hours / the next day”
Thought this was general beta knowledge by now!
@Corjan-Meijerink Hallo Corjan bedankt voor al je werk voor deze update 294. Helaas dit zijn na deze update mijn ervaringen.
Wit scherm op Samsung S7 android versie 8, wit scherm op Samsung S6 android 7, niet alleen bij update maar ook na schone installatie.
De icons, snelheid richting etc, zijn nu wel zichtbaar.
Jammer dat ik je dit weer moet berichten, ik weet hoeveel werk jullie er in steken. Ik hoop dat jullie nog een oplossing bedenken want ik ben vast niet de enige die z 'n oudere samsung gebruikt als navigatie toestel. Veel succes en houd moed! -
Minor bug:
Samsung running Android 14
Android v4.1.1 - 294- Open app and default OSM map shows on 'home' page.
- minimise MRA, and then open another app
- go back to MRA
- map is no longer there
Closing MRA with the back button (i.e. closing it 'properly') solves the problem.
A bit fo an an obscure bug, but it might point to some other problem, or help out.
-
Minor bug:
Samsung running Android 14
Android v4.1.1 - 294- Open app and default OSM map shows on 'home' page.
- minimise MRA, and then open another app
- go back to MRA
- map is no longer there
Closing MRA with the back button (i.e. closing it 'properly') solves the problem.
A bit fo an an obscure bug, but it might point to some other problem, or help out.
a bit of a stupid question...
Will there also be an update for the “normal app” in this regard? Unfortunately I don't have the "beta".... -
iOS updated automatically via TestFlight
-
a bit of a stupid question...
Will there also be an update for the “normal app” in this regard? Unfortunately I don't have the "beta"....@Christian-Schrenk If the update is successful in beta it will then be released for all users.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox B8J bar buttons.
Quadlock wireless mount for IPhone 11.
Cardo Scala Packtalk Bold.
TomTom Rider 500. (In the cupboard now) -
@Christian-Schrenk If the update is successful in beta it will then be released for all users.
@Nick-Carthew
Okay, thank you for the quick answer! Since I've had no problems with MRA so far and am just a normal user, I've never really thought about the beta.
Well then I hope that the card problem can be solved. As a precaution, I have already found out about new outdoor phones. It would be nice if I could save myself having to buy two new devices.
-
@Peter-Schiefer said in New beta v4.1.1 (294):
Gibt es überhaupt eine normal Version?
Sure, in iOS, you delete the Testflight version. After that, you go to the App Store and download the public version. For Android, the procedure is a bit more complicated, I believe.
-
Hi all!
After the 4.1.0 release, the improvements to Android Auto and CarPlay were greatly appreciated and above all noticeable!
Obviously there were still some issues present and new issues were also revealed. This beta is now being released to get feedback on the following subjects.
Supporting older Android devices
Despite Google not supporting Android 9 anymore since 2022, quite some users still use these devices as their "throwaway" mounted navigation phone. We are curious to see how this beta version performs on older Android phones.Map loading issues
Across Android and iOS users reported the app showing a blank map. Both in the home screen and in the navigation module. Please let us know if / when / how much that occurs in this version.Automatic waypoint skipping
Due to an undocumented change in software we use, waypoints were quite often accidentally skipped. This also happed for viapoints
and therefore unacceptable. In this beta, we've fixed the accidental skipping of any waypoint and while working on the subject the existing auto skip algorithm has also been improved.As always, thanks so much for your feedback on the app
Cheers,
Team MRA@Corjan-Meijerink my Android S7 Android v 8 still does not show any maps.
-
Hola @Corjan-Meijerink.
Lamentablemente en mi samsung tab active 2 (Android 9) sigue sin aparecer el mapa.
Se podria volver a version posterior?
Gracias -
Hi all!
After the 4.1.0 release, the improvements to Android Auto and CarPlay were greatly appreciated and above all noticeable!
Obviously there were still some issues present and new issues were also revealed. This beta is now being released to get feedback on the following subjects.
Supporting older Android devices
Despite Google not supporting Android 9 anymore since 2022, quite some users still use these devices as their "throwaway" mounted navigation phone. We are curious to see how this beta version performs on older Android phones.Map loading issues
Across Android and iOS users reported the app showing a blank map. Both in the home screen and in the navigation module. Please let us know if / when / how much that occurs in this version.Automatic waypoint skipping
Due to an undocumented change in software we use, waypoints were quite often accidentally skipped. This also happed for viapoints and therefore unacceptable. In this beta, we've fixed the accidental skipping of any waypoint and while working on the subject the existing auto skip algorithm has also been improved.As always, thanks so much for your feedback on the app
Cheers,
Team MRA@Corjan-Meijerink hi Corjan. Yesterday another testing day with thé 294. It was installed automaticly during the night-club on my Android.
Wonderfull day no real problems what so ever. Stopped the app during the stops and it came back just as aspected. Just to be shure , it is testing, stopped the app and loaded the route again. Then skipped all the shaping points I’ve passed and continued the trip.
2 things still need Some attention
On thé way home the battery of my phone gave up. The wireless charging of my quadlock just couldn’t keep up. I know that’s due to the Here maps but it would be mighty fine if the problem was fixed
The other thing is the fuel stations. I have no clue how this works. None of the stations on the route were indicated. The ones indicated weren’t on or near the route. How should it work.
Keep up the good work team BRAVO -
Gistermorgen versie 4.11 geopend en een route gestart. Het viel mij op dat de navigatie aanwijzingen erg luid waren vergeleken met de oudere versies. Raar!!!!
Totdat ik de volume knop van de motor gebruikte. Wat stond er in mijn scherm: "Navigatie Volume". Ik helemaal blij aangezien dit niet in de wijzigingen vermeld stond. EINDELIJK!!!!Helaas toch ook weer niet.
Zo lang als MRA de enige bron van geluid is van mijn Goldwing mediaunit. Heb ik netjes de aanwijzigen via het navigatie kanaal.
Maar.....
Zodra er een bron bij komt, wat eigenlijk altijd iets van muziek is, schakelt MRA direct om naar media kanaal. Er zit dus al iets in MRA om het navigatie kanaal aan te sturen maar het is nog niet goed geschreven.Toch nog een puntje van kritiek over versie 4.11.
Tijdens mijn rit had ik op een gegeven moment een tijdje dat het zoomniveau constant in en uit klapperde. Stukje uitzoomen en weer terug naar het normale zoomniveau. Laten we zeggen van 5 kilometer terug naar 300 meter en weer terug. Tegelijkertijd wisselde het icoontje van huidige snelheid tussen een snelheid en 2 horizontale streepjes. Ook kwam de donkerblauwe routelijn constant van verder vooruit terug kruipen naar de huidige positie.
Je zou dus denken dat er er geen duidelijk GPS signaal was, maar dat was niet het geval. De navigatie aanwijzingen klopten wel gewoon. De routepijl bleef ook gewoon vloeiend bewegen. Na ongeveer 10 minuten zo aan het stuiteren te zijn geweest, crashte de app. De app opnieuw gestart en alles werkte weer normaal.
Dit alles was voor mij zichtbaar op Android Auto. Telefoonscherm weet ik niet. -
Phone: Samsung S21 Ultra
Android Auto display: Chigee AIO-5 Lite
Headset: Interphone UCOM16
Bike: R1250GSAAt Easter I build a Chigee AIO-5 Lite display with CarPlay/Android Auto on my R1250GSA. And since the MyRouteApp support now Android Auto this seems a perfect solution for me. I tested it today with V4.1.1-294 on a ride. It’s my first serious ride with Android Auto, before I had a quadlock with my mobile in vertical position in front of me. I faced several issues today:
• In Android Auto the surrounding streets not on the route are much less good visible. On the phone I get a good impression on what is coming next, in Android Auto these roads are not so well visible. My map settings are zoom ++ and angle ++. On the photos the display does not look bright, but it is in real. I had to take a photo on a low angle otherwise the display is like a mirror for the camera.
• You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
Same with waypoint 9: I clear need to go left on this intersection, but no audio instruction and a wrong display that shows again the roundabout later at the route.
As of my opinion a lot of map visibility is lost due to the large size of the blue boxes at the left (with a lot of space unused). Due to this the visibility of the navigation is pushed very much to the right of the display.
Sound: Navigation instructions are much to less loud. If I use only navigation, I can turn up the volume of my headset, but as soon as I listen internet radio, then I must reduce the general volume to avoid that I don’t hear my surrounding anymore. As soon as a navigation instruction comes, the internet radio volume is reduced, but the instruction is at the same reduced level as well. After the instruction the internet radio volume goes up again. Due to this I complete miss the audio instruction and need to look on the display to see where to go. This is as well by using Android Auto as well as with navigation on the phone only.
Hope this helps to improve MRA, since I really like the software and all possible planning options at the PC and navigation with it.
Groeten uit Zwitserland,
Hans -
Phone: Samsung S21 Ultra
Android Auto display: Chigee AIO-5 Lite
Headset: Interphone UCOM16
Bike: R1250GSAAt Easter I build a Chigee AIO-5 Lite display with CarPlay/Android Auto on my R1250GSA. And since the MyRouteApp support now Android Auto this seems a perfect solution for me. I tested it today with V4.1.1-294 on a ride. It’s my first serious ride with Android Auto, before I had a quadlock with my mobile in vertical position in front of me. I faced several issues today:
• In Android Auto the surrounding streets not on the route are much less good visible. On the phone I get a good impression on what is coming next, in Android Auto these roads are not so well visible. My map settings are zoom ++ and angle ++. On the photos the display does not look bright, but it is in real. I had to take a photo on a low angle otherwise the display is like a mirror for the camera.
• You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
Same with waypoint 9: I clear need to go left on this intersection, but no audio instruction and a wrong display that shows again the roundabout later at the route.
As of my opinion a lot of map visibility is lost due to the large size of the blue boxes at the left (with a lot of space unused). Due to this the visibility of the navigation is pushed very much to the right of the display.
Sound: Navigation instructions are much to less loud. If I use only navigation, I can turn up the volume of my headset, but as soon as I listen internet radio, then I must reduce the general volume to avoid that I don’t hear my surrounding anymore. As soon as a navigation instruction comes, the internet radio volume is reduced, but the instruction is at the same reduced level as well. After the instruction the internet radio volume goes up again. Due to this I complete miss the audio instruction and need to look on the display to see where to go. This is as well by using Android Auto as well as with navigation on the phone only.
Hope this helps to improve MRA, since I really like the software and all possible planning options at the PC and navigation with it.
Groeten uit Zwitserland,
Hans@Hans-Hüppi said in New beta v4.1.1 (294):
You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
I am not sure this is going to solve the problem, but do yourself a favor, and place waypoints at least 200 mtrs from any crossing.
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 -
Phone: Samsung S21 Ultra
Android Auto display: Chigee AIO-5 Lite
Headset: Interphone UCOM16
Bike: R1250GSAAt Easter I build a Chigee AIO-5 Lite display with CarPlay/Android Auto on my R1250GSA. And since the MyRouteApp support now Android Auto this seems a perfect solution for me. I tested it today with V4.1.1-294 on a ride. It’s my first serious ride with Android Auto, before I had a quadlock with my mobile in vertical position in front of me. I faced several issues today:
• In Android Auto the surrounding streets not on the route are much less good visible. On the phone I get a good impression on what is coming next, in Android Auto these roads are not so well visible. My map settings are zoom ++ and angle ++. On the photos the display does not look bright, but it is in real. I had to take a photo on a low angle otherwise the display is like a mirror for the camera.
• You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
Same with waypoint 9: I clear need to go left on this intersection, but no audio instruction and a wrong display that shows again the roundabout later at the route.
As of my opinion a lot of map visibility is lost due to the large size of the blue boxes at the left (with a lot of space unused). Due to this the visibility of the navigation is pushed very much to the right of the display.
Sound: Navigation instructions are much to less loud. If I use only navigation, I can turn up the volume of my headset, but as soon as I listen internet radio, then I must reduce the general volume to avoid that I don’t hear my surrounding anymore. As soon as a navigation instruction comes, the internet radio volume is reduced, but the instruction is at the same reduced level as well. After the instruction the internet radio volume goes up again. Due to this I complete miss the audio instruction and need to look on the display to see where to go. This is as well by using Android Auto as well as with navigation on the phone only.
Hope this helps to improve MRA, since I really like the software and all possible planning options at the PC and navigation with it.
Groeten uit Zwitserland,
HansHallo, warum deine nächste Richtungsänderung nicht korrekt angezeigt wird, kann ich erstmal nicht sagen. Aber ein Tipp vorab, man setzt niemals Wegpunkte in die Nähe (oder auf) Abbiegungen oder Kreuzungen.
Das gibt nur Problem und kollidiert mit der Ansagen von Abbiegungen und dem Wegpunkt gleichzeitig selber.
Also WP immer weiter weg setzen! -
@Hans-Hüppi said in New beta v4.1.1 (294):
You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
I am not sure this is going to solve the problem, but do yourself a favor, and place waypoints at least 200 mtrs from any crossing.
@Con-Hennekens same thought
-
Phone: Samsung S21 Ultra
Android Auto display: Chigee AIO-5 Lite
Headset: Interphone UCOM16
Bike: R1250GSAAt Easter I build a Chigee AIO-5 Lite display with CarPlay/Android Auto on my R1250GSA. And since the MyRouteApp support now Android Auto this seems a perfect solution for me. I tested it today with V4.1.1-294 on a ride. It’s my first serious ride with Android Auto, before I had a quadlock with my mobile in vertical position in front of me. I faced several issues today:
• In Android Auto the surrounding streets not on the route are much less good visible. On the phone I get a good impression on what is coming next, in Android Auto these roads are not so well visible. My map settings are zoom ++ and angle ++. On the photos the display does not look bright, but it is in real. I had to take a photo on a low angle otherwise the display is like a mirror for the camera.
• You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
Same with waypoint 9: I clear need to go left on this intersection, but no audio instruction and a wrong display that shows again the roundabout later at the route.
As of my opinion a lot of map visibility is lost due to the large size of the blue boxes at the left (with a lot of space unused). Due to this the visibility of the navigation is pushed very much to the right of the display.
Sound: Navigation instructions are much to less loud. If I use only navigation, I can turn up the volume of my headset, but as soon as I listen internet radio, then I must reduce the general volume to avoid that I don’t hear my surrounding anymore. As soon as a navigation instruction comes, the internet radio volume is reduced, but the instruction is at the same reduced level as well. After the instruction the internet radio volume goes up again. Due to this I complete miss the audio instruction and need to look on the display to see where to go. This is as well by using Android Auto as well as with navigation on the phone only.
Hope this helps to improve MRA, since I really like the software and all possible planning options at the PC and navigation with it.
Groeten uit Zwitserland,
Hans@Hans-Hüppi
About the zoomlevel and view.
You're right. This also what i noticed. The settings you can make in the app for zoomlevel and view does not have much effect in Android Auto. -
@Hans-Hüppi said in New beta v4.1.1 (294):
You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
I am not sure this is going to solve the problem, but do yourself a favor, and place waypoints at least 200 mtrs from any crossing.
@Con-Hennekens said in New beta v4.1.1 (294):
@Hans-Hüppi said in New beta v4.1.1 (294):
You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
I am not sure this is going to solve the problem, but do yourself a favor, and place waypoints at least 200 mtrs from any crossing.
Hi Con, thank you very much for your advice! I am using MRA for several years now and was not aware of this typical issue. In the first tutorials about 4 years ago this was not mentioned (youtube: Les 4: Routes maken in MyRoute-app). Maybe in a later lesson, but then I missed that part). I cannot remember that I had this issue with a previous MRA version on this route (my standard short route to a nice viewpoint to see a 180°+ view on the alps).
I even noticed in a short test that the automatic route creator as of today even violate against this guideline. See in the picture below; point 32 and 37 are automatic positioned exact on the roundabouts. But I unterstand, it's not easy to get this all done due to the many many influences from maps and very complicated Algorithm.
Thanks again, this helps.
-
@Peter-Schiefer said in New beta v4.1.1 (294):
@Hans-Hüppi
Hallo Hans,
wie gut die Abbildung auf den China-Diplays für CarPlay und AA sind, dies liegt nun nicht in der Verantwortung dieser bzw. aller Apps, die CarPlay und AA lauffähig sind.
Auf YT gibt es genug Videos zu div. Zusatzdisplays für CP und AA, z. B. von Carpuride. Auch da gibt es Kritik zur Abbildung, dies sogar zu Geräten, die im Auto angewendet werden.
Zu dem Verbrauch von Flächen für die Infos links gilt auch hier, das ist dem Bildschirmformat und CP bzw. AA geschuldet und Vorgaben die Apple bzw Android zur Anpassung an die verschiedenen Displaygrößen der hauptsächlich Auto-Multimediaeinheiten gibt.
Auch hier, die Möglichkeiten seitens MRA sind begrenzt. Bei anderer Navi-Software von Sygic, Google Maps, Apple selbst, TomTom Go ist die Naviroute auch sehr linkslastig im Display auf dem jeweiligen Smartphone aber mittig.
CarPlay und AndroidAudio sind schon eine Hilfe, nutze es jetzt fast nur, aber es hat halt Einschränkungen zur Anzeige auf einem iPhone A-Smartphone oder dem jeweiligen Tablett.Vielen Dank Peter für die Erläuterungen. Android Auto is tatsächlich neu für mich, und womöglich lagen meine Erwartungen da nicht ganz richtig.
Und zuletzt, die Tonausgabe bei MRA für Shaping und Wegpunkte unterliegt Konventionen in der Planung und muss auch in den Einstellungen unter Audio eingeschaltet werden.
Bei mir waren nach der Neuinstallation der 294 die Audiovorgaben in Einstellungen auch nochmals zu setzen.
Bitte mal in der Anleitung nachschauenhttps://unterstutzung.myrouteapp.com/nl/support/solutions
oder hier im Forum
Galt übrigens auch für mich, war beim Einstieg in MRA auch etwas ratlos.
Die Lautstärke habe ich im Menü "Audio" auf Maximum. Aber die MRA Ansagen, und ich habe mehrere Stimme ausprobiert (Deutsch), bleiben zu leise. Anderswo im Forum habe ich gelesen das wohl auch Anderen dies mit ihr S21 Ultra haben. Ich werde es mal mein altes S9+ ausprobieren und schauen ob es damit gelöst ist.
Ergänzung, sowohl bei Garmin, zuvor verwendet, als auch hier bei MRA, speziell an Y oder gelegentlich auch schon eindeutigen T Abzweigen werden Abbiegeanweisungen nicht genannt obwohl man sie erwarten würde. Dies liegt an der Routenengine und den Here Kartenattributen.
Kollege Rhönschrat auf YT hat mal in einem Vergleich die Komplexibilität der Berechnung und das Unterschiede in den Navis von Garmin und TT vorkommen aufgezeigt.
Sehenswert https://youtu.be/8V4YN0-L-e8?si=pjOi7PzicoXQ8ezS
Und schau ich auf denen Wegpunkt, hier als Shapingpunkt mit dem Tropfenpfeil Nr 9, oder auch als POI mit der Hand gekennzeichnet, ist bei der Planung zu beachten, dass diese nie unmittelbar vor oder auf einer Abzweigung gesetzt sein dürfen, sie blockieren die Ansage einer Weganweisung. Richtungsweisende Shapingpunkte immer hinter einer zu erwartenden Weganweisung setzen.Danke für diese Tipps, das habe ich vor zirka 4 Jahre in die Tutorial Videos nicht gehört oder wohl überhört (und verstehe die ursprüngliche Turorials sehr gut, ist ja Niederländisch meine Muttersprache). Es hat sofern ich mich erinnere mit ältere MRA Version auch richtig funktioniert (ausser Audio, das weiss ich nicht mehr).
-
@Peter-Schiefer said in New beta v4.1.1 (294):
@Jörgen
Jörgen Con und ich immerhin schon Drei denen dies mit der Nummer 9 auffällt.
Unser Freund, der dies zeigte, scheint wohl ein „absoluter Beginner“ zu sein, der nicht nur MRA zum ersten mal nutzt, sondern Routenplanung überhaupt.
Er wird möglicherweise noch an einige Fallstricken in der Routenplanung stolpern, dies aber auch nicht nur bei MRA.Hm, soll ich jetzt reagieren oder nicht habe ich mich überlegt. Android Auto ja, da bin ich ein absoluter Neuling. Aber MRA benutze ich, wie glaube ich du auch, seit mehreren Jahren. Und navigiere mit Geräten wie den «Pocket LOOX 600» und entsprechender Software, seit das GPS nicht mehr künstlich durch die Amerikaner verschlechtert wurde. Aber ich bin klar (ältere) Endbenutzer, und benutze es auch dementsprechend. Wohl kein Endbenutzer liest sich dauerhaft stundenlang durch Foren oder schaut Stundenlang Erklärungsvideos an. Ich habe anfänglich die Video tutorials angeschaut, um den Rest intuitiv herauszufinden oder auf Basis was vom MRA in Videos angekündigt wurde.
Ich bin beruflich Produkt Manager und bekomme von unser R&D immer und immer wieder Software "von Ingenieure für Ingenieure". Da muss ich doch regemässig eingreifen, weil die Intuitivität fehlt. Fallstricken sollten so wenig wie möglich vorkommen, und bei Bedienfehler situativ möglichst ein Vorschlag oder Hinweis angezeigt werden. Aber Ja, ich verstehe die Komplexität im Hintergrund (wie hier bei MRA) welche es ab und zu fast unmöglich machen.
Meiner Meinung nach macht das MRA-Team eine grossartige Arbeit, und ich verstehe die agile Entwicklungsmethode mit auch uns als Tester. Und Tester gibt es in alle Facetten, welche die auf fast Bit und Byte Niveau mitreden können, und halt welche wie ich eher reine Anwender. Vielleicht braucht es die nicht im Beta-Programm, dann kann ich aus das Beta-Programm aussteigen und auf die normale Release-Versionen zurück gehen.
-
@Con-Hennekens said in New beta v4.1.1 (294):
@Hans-Hüppi said in New beta v4.1.1 (294):
You can see waypoint 8 on this screen, and I am expecting a direction instruction to go left, but instead I get a display instruction of a roundabout later at the route.
I am not sure this is going to solve the problem, but do yourself a favor, and place waypoints at least 200 mtrs from any crossing.
Hi Con, thank you very much for your advice! I am using MRA for several years now and was not aware of this typical issue. In the first tutorials about 4 years ago this was not mentioned (youtube: Les 4: Routes maken in MyRoute-app). Maybe in a later lesson, but then I missed that part). I cannot remember that I had this issue with a previous MRA version on this route (my standard short route to a nice viewpoint to see a 180°+ view on the alps).
I even noticed in a short test that the automatic route creator as of today even violate against this guideline. See in the picture below; point 32 and 37 are automatic positioned exact on the roundabouts. But I unterstand, it's not easy to get this all done due to the many many influences from maps and very complicated Algorithm.
Thanks again, this helps.
@Hans-Hüppi said in New beta v4.1.1 (294):
I am using MRA for several years now and was not aware of this typical issue.
No I have never seen this issue either, but that is only part of the advise. Placing waypoints on crossings is recipe for disaster. Since GPS signal is only accurate for a few mtrs, it can be enough for the app to direct you into a street, just for you to turn around. That has always been a problem, also in the previous app. In today's app a waypoint's priority of announcement is higher that a navigation announcement. Effectively killing your turn by turn instructions.
@Hans-Hüppi said in New beta v4.1.1 (294):
the automatic route creator as of today even violate against this guideline.
Yes, when adding waypoints through the toolbox, or converting a track to a route, the planner has the tendency to place WPs at the direct place where the route/track changes direction. Also, in ALL manuals and presumably ALL forum posts about it, it is advised to review them, and replace them away from crossings. But you are right. In my experience it is quicker to draw a route over a track yourself, or add waypoints manually by clicking ON the route line when zoomed in. Therefore I never use those functions at all.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
