Skip to content
  • Categories
  • Recent
  • Popular
  • Support
  • MyRoute-app
Collapse
Brand Logo

MRA Community Forum

  1. Home
  2. [Beta] The MyRoute-app
  3. [Beta] Announcements
  4. New beta v4.1.1 (294)

New beta v4.1.1 (294)

Scheduled Pinned Locked Moved [Beta] Announcements
25 Posts 17 Posters 512 Views 6 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Corjan Meijerinkundefined Corjan Meijerink

    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

    RetiredWingManundefined Offline
    RetiredWingManundefined Offline
    RetiredWingMan
    Valued contributor
    wrote on last edited by
    #13

    @Corjan-Meijerink my Android S7 Android v 8 still does not show any maps.

    2010 GL1800 Goldwing using Samsung Galaxy S20 5G Android 13.

    1 Reply Last reply
    0
    • Marlanjosundefined Offline
      Marlanjosundefined Offline
      Marlanjos
      wrote on last edited by
      #14

      Hola @Corjan-Meijerink.
      Lamentablemente en mi samsung tab active 2 (Android 9) sigue sin aparecer el mapa.
      Se podria volver a version posterior?
      Gracias

      1 Reply Last reply
      0
      • Corjan Meijerinkundefined Corjan Meijerink

        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

        Marinus van Deudekomundefined Offline
        Marinus van Deudekomundefined Offline
        Marinus van Deudekom
        Valued contributor
        wrote on last edited by
        #15

        @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

        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

        1 Reply Last reply
        0
        • M. Schrijverundefined Online
          M. Schrijverundefined Online
          M. Schrijver
          Valued contributor
          wrote on last edited by
          #16

          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.

          (I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)

          1 Reply Last reply
          0
          • Hans Hüppiundefined Offline
            Hans Hüppiundefined Offline
            Hans Hüppi
            wrote on last edited by
            #17

            Phone: Samsung S21 Ultra
            Android Auto display: Chigee AIO-5 Lite
            Headset: Interphone UCOM16
            Bike: R1250GSA

            At 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.

            1.png

            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.

            2.png

            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

            Con Hennekensundefined Jörgenundefined M. Schrijverundefined 3 Replies Last reply
            -1
            • Hans Hüppiundefined Hans Hüppi

              Phone: Samsung S21 Ultra
              Android Auto display: Chigee AIO-5 Lite
              Headset: Interphone UCOM16
              Bike: R1250GSA

              At 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.

              1.png

              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.

              2.png

              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

              Con Hennekensundefined Offline
              Con Hennekensundefined Offline
              Con Hennekens
              Alpha tester
              wrote on last edited by
              #18

              @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

              Jörgenundefined Hans Hüppiundefined 2 Replies Last reply
              0
              • Hans Hüppiundefined Hans Hüppi

                Phone: Samsung S21 Ultra
                Android Auto display: Chigee AIO-5 Lite
                Headset: Interphone UCOM16
                Bike: R1250GSA

                At 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.

                1.png

                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.

                2.png

                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

                Jörgenundefined Offline
                Jörgenundefined Offline
                Jörgen
                Valued contributor
                wrote on last edited by
                #19

                @Hans-Hüppi

                Hallo, 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!

                Hardware
                iPhone 12 pro (iOS 17.0.2)
                Oukitel RT3 (Andr. 12)
                Samsung Galaxy XCover 4 (Andr. 9 Pie)
                Wireless CarPlay mit (Elebest C650)
                Wired CarPlay (SEAT Arona - 2021)
                For more information, click here

                1 Reply Last reply
                0
                • Con Hennekensundefined Con Hennekens

                  @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.

                  Jörgenundefined Offline
                  Jörgenundefined Offline
                  Jörgen
                  Valued contributor
                  wrote on last edited by
                  #20

                  @Con-Hennekens same thought 😊

                  Hardware
                  iPhone 12 pro (iOS 17.0.2)
                  Oukitel RT3 (Andr. 12)
                  Samsung Galaxy XCover 4 (Andr. 9 Pie)
                  Wireless CarPlay mit (Elebest C650)
                  Wired CarPlay (SEAT Arona - 2021)
                  For more information, click here

                  1 Reply Last reply
                  0
                  • Hans Hüppiundefined Hans Hüppi

                    Phone: Samsung S21 Ultra
                    Android Auto display: Chigee AIO-5 Lite
                    Headset: Interphone UCOM16
                    Bike: R1250GSA

                    At 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.

                    1.png

                    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.

                    2.png

                    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

                    M. Schrijverundefined Online
                    M. Schrijverundefined Online
                    M. Schrijver
                    Valued contributor
                    wrote on last edited by
                    #21

                    @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.

                    (I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)

                    1 Reply Last reply
                    0
                    • Con Hennekensundefined Con Hennekens

                      @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.

                      Hans Hüppiundefined Offline
                      Hans Hüppiundefined Offline
                      Hans Hüppi
                      wrote on last edited by
                      #22

                      @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.
                      1.png

                      Thanks again, this helps.

                      Con Hennekensundefined 1 Reply Last reply
                      0
                      • Hans Hüppiundefined Offline
                        Hans Hüppiundefined Offline
                        Hans Hüppi
                        wrote on last edited by
                        #23

                        @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 nachschauen

                        https://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).

                        1 Reply Last reply
                        0
                        • Hans Hüppiundefined Offline
                          Hans Hüppiundefined Offline
                          Hans Hüppi
                          wrote on last edited by
                          #24

                          @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.

                          1 Reply Last reply
                          0
                          • Hans Hüppiundefined Hans Hüppi

                            @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.
                            1.png

                            Thanks again, this helps.

                            Con Hennekensundefined Offline
                            Con Hennekensundefined Offline
                            Con Hennekens
                            Alpha tester
                            wrote on last edited by
                            #25

                            @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.

                            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

                            1 Reply Last reply
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • 1
                            • 2
                            ACTIVE USERS
                            Nick Carthewundefined
                            Nick Carthew
                            Con Hennekensundefined
                            Con Hennekens
                            RetiredWingManundefined
                            RetiredWingMan
                            Corjan Meijerinkundefined
                            Corjan Meijerink
                            Marinus van Deudekomundefined
                            Marinus van Deudekom
                            Rob Verhoeffundefined
                            Rob Verhoeff
                            M. Schrijverundefined
                            M. Schrijver
                            Jörgenundefined
                            Jörgen
                            richtea999undefined
                            richtea999
                            Jan Weerheimundefined
                            Jan Weerheim
                            Stefan Hummelinkundefined
                            Stefan Hummelink
                            Lynchy67undefined
                            Lynchy67
                            Christian Schrenkundefined
                            Christian Schrenk
                            Hans Hüppiundefined
                            Hans Hüppi
                            Marlanjosundefined
                            Marlanjos
                            POPULAR TOPICS
                            • Herberekenen route
                              henry van den beltundefined
                              henry van den belt
                              0
                              11
                              80

                            • Silverfox H1+ long-press
                              Nick Carthewundefined
                              Nick Carthew
                              0
                              9
                              87

                            • Uploaden naar Zumo lukt niet vanaf iphone
                              Mzokkundefined
                              Mzokk
                              0
                              8
                              110

                            • Route app werkt helaas nog niet hoe ik het graag zou zien.
                              Con Hennekensundefined
                              Con Hennekens
                              1
                              30
                              680

                            • I Can't Find a YouTube Video on How to "Trace" My Ride for the Day
                              RetiredWingManundefined
                              RetiredWingMan
                              0
                              4
                              73

                            • Newcomer
                              Gilles collignonundefined
                              Gilles collignon
                              0
                              9
                              119

                            • Android Auto bugs and improvements
                              bluetuzundefined
                              bluetuz
                              2
                              6
                              257

                            • Number of waypoints
                              Gilles collignonundefined
                              Gilles collignon
                              0
                              3
                              49
                            MY GROUPS
                            • Login

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Popular
                            • Support
                            • MyRoute-app