MRA Community Forum

@Martijn-Peereboom systemen die wel alles kunnen laten zien. Diverse, variërend van een goede telefoon tot en met rugged tablets. Die laatste heb je ook weer in diverse uitvoeringen. Zoals je in mijn handtekening kunt lezen gebruik ik zelf een Thora DMD2 8inch tablet type T865X. Daarover heb ik in dit forum ook een blog geschreven

@Herman-Veldhuizen Mijn voorbeeld was een route, geen track. Bij tracks verwacht ik dergelijke problemen niet.

@M.-Schrijver said in Herberekenen route: Als ik een adres invoer (een typische A naar B). Verwacht ik dat ik zo snel mogelijk of via de kortste weg (wat je ook gekozen mag hebben), naar het eindpunt gestuurd wordt en niet onderweg rondjes aan draaien ben omdat ik iets gemist zou hebben. Dat klopt, en zo werkt het ook. Bij een directe route (dus zonder kronkel-opties) naar één bestemming is er ook helemaal geen track of routepunt waarnaar je teruggestuurd zou kunnen worden. Wat het vreemde gedrag in @henry-van-den-belt zijn geval veroorzaakt heeft, geen idee. Ik zou wel willen weten of in zijn geval dit gedrag herhaaldelijk voorkomt, of dat het bij die ene keer is gebleven.

@Corjan-Meijerink Like .. I don't think

@white.mouse said in Streetview: Misschien even een ticket aanmaken! Dat is misschien wel wat ja. Dank voor de tip. Gr Ruurt

@Corjan-Meijerink I know you do all you can to fix problems. In this case I’d say It takes twi to tango. Keep up you excellent work

hi @Gilles-collignon welcome the wonderful world of MRA, don't listen to the nay sayers, if unsure ask a question ️

Probleem is opgelost. In plaats van de file op de iPhone te openen en dan via de Garmin Drive app door te sturen, selecteer ik de file op de iPhone in de downloads map en stuur hem dan naar de Garmin drive, dus zonder hem te openen dan lukt het wel. Het gaat overigens om een Zumo XT en niet de XT2 (anders HD ik dat wel gemeld…)

That's the fun part of this issue, it's extremely device / environment / charger dependant We (as app) would not be performing as well if everyone had this issue. If everyone had this issue, it would have been easier to solve as well That said, a lot of my time lately has gone into improving the battery usage and the results are getting there. Yes, I know we've said that more often in the past year (but minor improvements were also already made).

@Con-Hennekens thx!!!

@Con-Hennekens Thanks for this great hint!

@M.-Schrijver said in Route recalculation: Can I ask why you switched recalculation off? Because with recalculation enabled (but also when it is disabled), there is no warning that you have left the planned route, and if you don't notice that the route has been recalculated when you look at the screen again, you mistake the new route for the one you should have taken. Last time, it made me go around a mountain to return to the village where I took the wrong road, adding about ten kilometres to my journey. when all it would have taken was to immediately notify me to make a U-turn within 100/200 metres of where I took the wrong turn. Another time, on an almost figure-eight route, when I took the wrong turn, it recalculated the route, making me take the final part of the route, cutting out a large part of the route I had planned, and since I didn't know the area well, I realised it too late.

This has already been addressed. Patience https://forum.myrouteapp.com/post/64206

Sorry for the delay, I was travelling for 5 days, this time with the convertible and also MyRouteApp. I had the problems described above on a motorbike trip with a Pocophone F1 running Android 9 natively, i.e. without the use of Android Auto. Unfortunately, my story of frustrations is not over yet. We were travelling in the convertible for 5 days as mentioned and this time we have MRA on a Pixel 7 with Android Auto. (Android 15) At first everything went smoothly. Paired the mobile phone with AA, started MRA and selected and started the route. No problems until the first break. After the break I started the car, AA established the connection, only MRA did not want to run on the AA monitor. The route was displayed on the mobile, the current location was displayed on the AA monitor, but the cursor did not move. As we drove on, nothing moved on the AA monitor, only the navigation was displayed on the mobile phone. Stopped, shut everything down and restarted. Now it worked again until the next break. After this happened to me several times, I downloaded the route from MRA as gpx, imported it into kurviger and continued with kurviger. In kurviger there is an option to switch to the mobile phone on the AA monitor. And on the mobile there is a button to switch to AA. I don't know anything like that with MRA, but it would probably have helped me in this situation. The rest of the week we drove the daily stages planned in MRA on Kurviger and there were no more problems.

@Corjan-Meijerink said in MRA use on 2000 mile trip: You can actually get 2 pints for £9.99? That's amazing! indeed you can @Corjan-Meijerink , you just have to look in the right places, off the beaten track, obviously sometimes it was a little expensive, but hey, it's a holiday. ️

@Marinus-van-Deudekom thx Marinus

Hi @Sam-Kramer , as @RetiredWingMan wrote: access rights for MyRoute-App to location must be granted for all time. Not limited for time in wich App is used! And battery saving for the App must be off! Then, as @Nick-Carthew wrote, tap the red circle icon down right on the screen, to get it green. This will start recording your trip. At the end of your trip, you need to tap again the now green circle icon, to start saving procedure; this will take a couple of seconds. If you don't have Internet connection this time and saving fails, check upload queue in App. You can repeat uploading of failed tracks, if you have a Internet connection later on. And about wording: you are right. "Via Points" in MRA-Routeplanner are called in other navigation devices differently; may called Waypoints... Inside a gpx file (file format is common), you can see: if there is a route, the points are called routepoints. If there is a track, the points are called trackpoints. And if there is a POI (Point of Interrest) included, it's called waypoint. Sounds a bit irritating, but take a moment to think about, then you will understand. Also you need to understand: what you usually are planning before a ride, is a route. Defined by routepoints (via, or shaping). At MyRoute-App you will see a blue line as overlay on map. And you will see turn instruction icons on screen and you will get additional voice instructions during ride. In opposit: you can record your ride, then it's a track and you will see a yellow line as overlay on map. Both also at same tine: following a route and recording your ride as track. If you will follow later on your saved and reloaded ride (track), or get a recorded trip of someone else as gpx file - then you must check ongoing the track line on map and compare, if you are still on right road. You will not get turn instruction icons on screen and you will not get additional voice instructions from tracks! Usually... But new in MyRoute-App: you can use a route - but navigate as track. Then you will get additional voice instructions during ride! The advantage is: navigation is really calculating the path exactly on the track. You know - if you share a route with others, each navigation device is calculating the path by it's own algorithm. Result will be different at each device.

Thanks. Let me play with it, and I will get back to you.

Tja … dann könnte ich gleich wieder auf ein Saugnapf-Navi umsteigen … ;-( Ich versuche es bei einer nächsten Tour nochmal. Aber - lästig. Man braucht tatsächlich einen Plan B…

@Inge-Bakermans, Your opening post was in English, so I will continue in English. What is it exactly that is not good on your screenshot?