@Peter-Schiefer, you called it a problem, not me: Das ist schon mal ein Deutsch-Holländisches Sprachproblem But whatever...

@Aggelos-Minoudis you know what you mean but I have no idea what you are asking. Suggest you review the manual(s), https://www.myrouteapp.com/support

Thanks @Con-Hennekens i will try that. Your suggestion seems sensible. I have no requirement to sync my whole library and in particular I don’t want a pre-planned route on my phone to be changed while I’m on a trip, which could happen if I inadvertently alter a route on my iPad for example

@Richard-18, yes we agree on that!

@Martin-White Ah, yes! I know of them from a couple of friends, but I had forgotten. Again. They rate PocketGPS as an excellent source. Thanks for confirming.

@Ron-Z said in Android Tablet or CarPlay?: @PieterG Also, if your bike has the BMW navigation cradle, check out Carpuride's W502B Pro or W702B Pro CarPlay screens - they'll connect directly to the BMW mount with no adapter needed. @Ron-Z Thanks for your reply! I know the models you mention. In fact, the manufacturer has screwed a loose BMW adapter to the back of these models, just like with my Carpuride W619B. What I want to do is use such a kind of adapter in combination with a small rugged tablet so that I can also place it in the BMW cradle. This way I can always easily choose between using my BMW navigator IV, the Carpuride W609B or a tablet running the MRA Navigator Next app.

@Corjan-Meijerink Thanks for the reply. Good to know I got it right. Enjoy your trip, and avoid the snow!

Dat probleem heb ik ook. zeker de afstand tot de volgende afslag ( links boven in, onder de pijl) is zo klein dat het gewoon niet te lezen is. En dat vind ik toch wel belangrijke informatie. Ik rij met een 6.5 inch telefoon, ruimte genoeg op het scherm. Kan dat niet aanpasbaar worden gemaakt?

@Brian-McG I'm happy with the current setup. I do agree that waypoints not being announced should not interfere with waypoints to be announced.

@Erik-Schreuder De route op de website maken of in de app, maar dan niet met de generator

@Marc-Brondel bedankt voor de info, nu nog de landen downloden heb nu de navigator aangekocht,

@Marco-7v Je doet niets verkeerd! Fiets- en wandelroutes kun je niet navigeren met de navigatiemodule van MRA. Als je het profiel 'Fietsen' of 'Wandelen' aan een route hebt gegeven, dan maak je de route in de OSM-kaart en kun je in de app de route navigeren door de blauwe lijn te volgen. Je krijgt geen instructies en de route wordt niet herberekend.

@Grumpy-Goat said in Trialing the NEXT app and have 2 specific questions: wonder if it has something to do with this message I get when I select my day's route: This message only comes when you have this "check" enables in the settings: check if routes are made in the HERE map. Obviously you have this setting enabled, and you have created this route using the OSM toolkit instead of the HERE toolkit. The nav module uses the HERE SDK for the navigation so to have the most accurate navigation experience make sure your route is how you like it in HERE. Now, I'll not go into how to do that now, since that is routeplanner related, but when you've planned the route in OSM, the actual route is recalculated in HERE when navigating the route. Since the two databases or maps are never identical, it may happen the navigated route is NOT identical to the one you planned in OSM. One may observe loops, incorrect turns etc etc. Maybe I did not look closely enough as by that time I was getting a bit confused and slightly frustrated... Well, probably you missed the resume option haha. Even after a force close, the resume option stays available and it'll ask you also to resume the track recording if you had one running before the force close. Not sure whether if I had selected navigate as a Track it would have behaved the way you said. Riding the track may have prevented some strange OSM /HERE occurrences, but some other quirks are applicable for that mode, so route Navi is the best use here. whether I was actually using the HERE map (since I was using the trial version) or whether I was using / seeing the OpenStreetMap This is where I must re-emphasize how the app works. The app is built in basically two parts: the 1st/main part (including all the main screen functionalities), and the 2nd/navigation part/module. This navigation module is only available to navigation next licensees whereas the main menu is available to everyone, even basic users. Now here is the basic difference between main part and navi module: in the main menu or map shown, many map layers can be selected and used to look up stuff. This also includes the route info screens when one opens a route and the stat screen of that route shows up. In the Navi module though ONLY the HERE map is available since the entire routing code is done using the HERE SDK. So as soon as you're in Navi mode, HERE is the only database applicable and that is precisely why every route shall be at least confirmed to be good in HERE, so the navigation can do its job at its finest. Now, additionally, the curvy generation/calculation of routes using the "destination" or "round tour" functionality is done using OSM(fasted option is already in HERE, but only when nav next license is purchased), but as soon as you are going to navigate that route, the app converts the generated route into HERE and proceeds with navigation. will be doing the route for Day 2 today and will try and repeat the search attempt. Well, perhaps you should recheck your routes before doing so. , or post a link to them here. We can check them quickly so that your trial experience is not negatively impacted due to "bad routes".

@Thomas-Neumeyer yes, just log in with your account

@Brian-McG Brian, regard … its just a bit counter intuative. thank you, sometimes I have similar concerns and the feeling MRA play with you hide and seek.

@Rene-Klemans Klopt! Dit was een fout in 4.3.0. De 4.3.1 update van volgende week (nu in beta) lost het op!

@Peter-Schiefer I am talking about the steps later, when my works is done and I have worked out the POI's of my interest, that I want to visit (or not). So, I have prepared my own custom list of POI - the way I arrange, categorize, and use them, with my prefixes as said - this is my organisational structure. I don't want to access common or published POI. I want an easier access to my custom POI (and yes - some of my custom POI may equal to published and official ones, but I create my own ones on top, to distinguish between those I care and (may) want to visit - all other ones I disregard). If you try to search for your custom POI while at the navigation screen with the magnifier glass you will not be successful, you can search only for public POI and by category. You cannot search by free text to find your custom POI; this is my request.

@AlanM said in Waypoints options: Easier on PC though. Like everything... My tablet is used not much more than a fancy e-reader.

@Corjan-Meijerink said in Road closures not notified at start of route: You will receive a warning in the app before starting navigation if there are any violations as of version 4.3.1 That line is worthy of mentioning in the announcement topic

@Mike-wiruth, You're welcome