I noticed that as well but in my case above there are speed limits sets and displayed correctly when running a simulation - see screenshots
Somehow it picks a 30mph speed limit on the short road in/out of the car park but fails to change to the next speed limit until MNF is restarted. Possibly the 30mph speed limit been on a very short road is the problem....
Stopping and restarting navigation has no effect - the 30mph is shown all time.
Correct in simulation but shows 30mph when navigating the route
@lubos - it happened again today while navigating from A- B ( not following a route file).
I think it started when reached Wellingborough - speed limit changed to 30mph and displayed as 30mph. The 30mph display did not change till destination reached although were different limits on route.
Reversing a route did not behave as expected. As you can see from the attached screenshots the route did not reverse as expected. Attached "forward" route and the equivalent "reverse" route
I think this cause was the Waypoint positioning in those 2 locations but I would expect Navigator to take that into consideration and move the waypoints to the other side of the road instead making the long diversions.
Version 2.0.31 on Sony Xperia Z3 Compact. APP & all maps on sd card.
This happened to me today. I left my start point on a 30mph road & travelled home (40 miles) on a mix of 30, 40, 50, 60 & 70mph roads. The speed limit displayed 30mph for the whole journey but the speed limit sound warnings operated correctly. On an earlier journey today (45 miles) as well as the speed limit freezing at 60mph, gpx recording stopped, the next instruction window in the bottom left of the screen froze, there was no lane guidance & the road name at the very bottom froze. Map & sound navigation worked fine. I've sent the logs for the two trips.
Hi folks, re my previous concern of the HW rendering on Nexus 5, Android 6.0 - the navigation starts but the map is black. Tried version 30 and 31 as well...no change. Please see the log below..might help you to identify the issue. The SW rendering seems to be working fine.
If you could advise what to do...it'd be much appreciated. Thanks
@Lubos - I see jd417's failed using OSM maps but I will try tomorrow with the OSM maps and the same gpx file ( I think I tried that already but I cannot find the log file ).
Let me know if you need anything else...and nice to have you back :)
Why does "Back" button in the Navigator main menu hides Navigator to background?
When map is opened, I press Menu button to change some settings. When settings are updated I press Back button to return to Map. But instead application goes to background. It confuses a little.
@stavrich - I was checking both issues for few hours but I didnt find anything... now there are lot of other priorities in company, sorry @dmytro - menu has same function as back button in navigator. Menu is app's root screen.
hardware rendering: I've mentioned this earlier for earlier versions but it still isn't gone. Quite often the GPS position is not correct and another road is selected leading to completely wrong recalculations. The GPS is not lost, it's simply 5-50 meters wrong (guess).
I was lucky to update my Android device to the new 6.0 Android. But now, so my impression, in hardware-rendering the map isn't shown anymore. Software-rendering works fine.
I usually don't use Google Play Store for Navigator Free, even not for an alpha or beta version. Don't you have a link to your (MapFactor) directory like for the beta version?
The 2.0.33 version has some serious issues with themes. I use 2 themes (day/night) which I created myself. Every now and then they disappear.
Upon reloading them again from a file manager, navigator free always asks twice to import or set as day/night mode. If I click once and cancel the second, or the other way round, the theme is not in navigator after a restart although it seems to still use it.
I also mentioned this somewhere in the 3rd or 4th week of July.