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