@Dave-J-0 Hi Dave Im referring to the track colour, in the MRA its blue, in other apps its higher contrast or you can choose an entirely different colour.[image: 1743862751387-img_8100.jpg] [image: 1743862758050-img_8099.jpg]

@Arjan-de-Vries Ja, je hebt gelijk - er zijn nu heel wat gebruikers die de Remote 2-controller gebruiken met de MyRoute-app. En iedereen zou heel blij zijn als het eindelijk zou werken! Laten we hopen dat @Corjan-Meijerink snel een oplossing vindt.

@stuart-marritt ok - then it's the steps I described in second sektion. You can do this at your phone

@JP-d Try and relax about updating maps and just check for updates every few weeks. The chances of you missing an update that affects your route are very small.

@Paul-c5 Tree/List view, in addition to the map view, would be nice too.

@Albyus said in problem with waypoints: @Marinus-van-Deudekom hand-shaped Hand shaped waypoints are specifically intended NOT to be auto-skipped (mandatory waypoint). So you will have to skip it manually if you do not intend to visit it.

@Tony-13 In the scenario that you experienced, I would suggest that as the incident was fresh, it’s doubtful that any diversions were in place, so I would have stopped your A - B route, driven around the obstruction and then entered your destination again into the app.

@RetiredWingMan Thanks for your contribution. My experience with that is that it;s only avoiding high-ways but not so much going for the Curly routes I’m used to with TomTom. Also, it’s going to send you the same way back if you’re not adding a via point…

@Corjan-Meijerink Thanks for your reply.

@Corjan-Meijerink said in Automatic switch Distance to next Via Point / Final Destination: This is all listed in the manuals Go to https://www.myrouteapp.com/support > "MyRoute-app" > "Bluetooth controllers". For SilverFox, it's an "A" Hello Corjan, I tried this out and compared it with the information on the support page. I first realised that all letters have to be sent as a code in lower case and not in upper case as described. (for BarButtons N=n, D=d and C=c) I can not check this for Silverfox, but I think it should also be written in lower case here. Assuming Joost (or someone else) changes the code and you could send an ‘a’ for the display switch, would you then add this function for BarButtons in MRA?

@Marinus-van-Deudekom said in Minimum tablet requirements for MyRoute App: Oh, but I can agree with THAT of course. If you buy something new, you do not want to go for less . But: Like I said not for ME actually you left out "for ME" in your post, so it sounded like "in general".

@Con-Hennekens Thank you!

@Dennis-Hoogendonk said in 6.000 kms experience with MRA + Carpuride: I would encourage developers to optimize zoom function I agree !

@Corjan-Meijerink Thank you

@Nick-Carthew Iv not upgraded to a trial. When I press this button now it says 'Thid feature is no longer available (anymore)'.

@paul69 Thank you very much

@Jörgen skipping waypoints is not visible on my carpuride CarPlay this would be a great feature it’s the only reason to have the phone on the handlebars too I would rather have the phone in my pocket any idea how best to ask for this feature? I’m a gold user

@Peter-Zehentreiter Ja, richtig! Die App benutzt zum Navigieren die HERE Karten. Du solltest nach dem Planen, die Route mit den TomTom Karte vergleichen, (unter Toolkit- Route vergleichen mit) dann siehst du wie TT die Route fährt und kannst evtl. noch den einen oder anderen Wegpunkt setzen damit beide gleich sind.

Außerdem wäre es schön, wenn es auch in AA zu sehen wäre. Gruß

Not to add fuel to the fire, but from various threads and postings both here and on other forums, it does seem iOS is a more stable environment. Android can have many differences in hardware, and even a variance of operating systems. This can make developing for Android a challenging experience, that may require work-arounds and such. Apple's walled garden has a more tightly integrated OS, and I've heard from many developers that iOS is easier to program for than Android. That said, I haven't experienced any issues with my limited time running MRA Next on my Android tablet. I need to further test out both OSs to see what works better for me.