What are you trying to achieve? I assume that you already chose a destination point that also shows up in "Route info". Then, depending on your goal:
- To view a route based on an arbitrary starting point, define a starting point so that it's also visible in "Route info". In "Route info", press button "Show on map".
- To immediately start routing from your current GPS position, just press Navigate.
Are you using the same start & end points? If your start or end point is not close to a road (for example in the middle of a field) Navigator will give a route not found message. Try enabling small local roads in vehicle settings. This has been known to cause error in some countries.
I have seven Heathfields and two Stroods for selection. Just choosing the firsts from the list, I can at least calculate a route from the tools menu.
What you are telling, really seems to be something, that you still not know, how to use Navigator. This app's behaviour is somewhat different from what I was used to before. I think, we only can assist you, if you tell us step by step, what you tap and not just say "Navigate".
I go into Navigator, choose free maps. For example, I search for Camden Road, Tunbridge Wells. There is a pop up that gives me an option to Navigate. I tap that. It shows the map and I get, 'Recalculating the Route' followed by 'Route not Found'.
I've tried going to the map and pointing to the destination with no success.
I am using postcodes but start co-ords are 50.59.5.892, 0.20.10.212, destination is 51°23'43.04"N, 0°30'3.33"E
problem seems to be in free maps seems like Vicarage road is not connected to A265
Free maps are created by volunteers at www.openstreetmaps.org - anybody can join and help to make maps better using their local knowledge. May be you can correct it?
Quick update - I uninstalled it and deleted all traces of the app. I reinstalled it and it has the same problem. Even starting on the A265 to go 2 miles to Burwash produces the problem.
Otherwise it looks perfect and I'm not being sarcastic!
A silly question perhaps but is your device location service service switched on & does Navigator have access to it? In Navigator Tools select GPS info. Are satellites available?
You may have to sign up for beta testing to get the 3.0.74 version. I think v2.2.78 is the latest stable version but someone from MFN should be able to confirm this.
One more thing. When you first run Navigator it asks you to choose free or Tomtom maps. I assume you chose free. I think you're then prompted to download at least one country (UK?). Did you also install the required files earth & sound signals?
I have installed the beta version and downloaded the maps, system files etc. It is still doing it. I checked GPS from within the app and it has a fix. The next step is to take it out on the open road and see if it works.
I've tried a "live" navigation from my current GPS position to the middle of Vicarage Road & it provided a route. You could try going to a nearby place then try to navigate home.
Travelling from Rochester Canal Rd to Burwash: The issue seems to be Vicarage Lane not Road. When destination is set to Vicarage Road the route is found. Set destination to Vicarage Lane the route is not found.
I have no idea if TomTom maps would solve your issue. Vicarage Lane, Burwash is on OSM map UK map 44-201701260 I have no clue why the route is not found to there. Some experts could have a look at it, info lat="183545856" lon="1208096" Vicarage Lane - Stokes Road, Burwash, East Sussex, United Kingdom
The navigation problem lies with Vicarage Road. To get to Vicarage Lane you have to go via Vicarage Road, which is correctly mapped on OSM as access="destination" for motor vehicles. Google Streetview shows a road sign restricting motor vehicles to "for access only". https://goo.gl/maps/WpU19V8qTht
You can navigate to Vicarage Road successfully, as Navigator interprets the access restriction to allow you to get to it as destination
Fairly unusually, there are a number of other roads that can only be accessed via Vicarage Road: Westdown Lane, Buckels Mews, Stokes Road, Westdown Park, April Lane, Park Hill and Vicarage Lane. None of these can be navigated to.
So in some ways the fault lies with Navigator which does not navigate through this restriction to gain access to Vicarage Lane and other roads. I suppose the logic ought to be that in a case where a route cannot be found, any "for access only" restrictions are lifted.
I will try to explain this if you set waypoint on a closed link then route will be found if several links, next to each other, are closed and waypoint is on any of these then route will be found but if one link is closed and the next (with waypoint) is open, then route will not go through the closed link
I have used MapFactor for quite some time very successfully on a Samsung J5 with Android 5.1.1 . I have just got a new phone - Samsung J3 2017 with Android 7.0 and I'm getting the "Route not Found" issue.
I have compared the settings in each phone and apart from some minor differences they seem the same. However on my old phone the maps are stored in the phone but on my new phone they are installed on the sd card. I needed a new phone because my old one ran out of space so I am reluctant to move the maps if I don't need to.
Could someone tell me if this is a storage location problem or an Android version problem? If it is Android incompatibility then I'll have to keep my old phone as my SatNav - thank goodness for offline navigation!!
I have just tried various postcodes on my new phone (including that of a church near my destination) and I have not encountered the same issue.
My destination is a private residential "village" but it does work on my old phone - in fact it takes me right to the door, could it be that it has now been excluded from your current maps? I can find it on Google maps but on their street view I can only "travel" a few yards up the private road that leads to this village.
By the way (not sure who to report this to) if I zoom the screen while I'm on this page I lose everything I have typed in the comment box - this has happened to me twice! :o/
it is not possible to see what the problem is without knowing exact position if it is some small private road then try to enable small local roads in vehicle settings