@lubos: What Larry means is the so called "worldwide altitude correction". The calculated altitude by a GPS needs correction for every latitude/longitude because the GPS calculated altitude is based on the WGS84 reference ellipsoid, not based on sea level or some other standard level.
Some Nav apps deliver a "worldwide altitude correction" data file with their apps to compensate for these inaccuracies (see OsmAnd for example). If you search the web you can find prefilled databases/CSV files and so on to convert this to a suitable format for your application/appliance.
@Larry: Be aware that cheap GPS sensors might have an additional deviation simply because they are not accurate enough. What's more: they can be terribly innacurate for altitude.
Just installed 2.1.81. Hardware rendering issue still there - incorrect font on some place names, also rendered as white. If you zoom out too far then all place names disappear. Tried uploading photo but failed.
Quick update to state that I have tried 2.1.82 and the hardware rendering issues I experienced are still present. Missing place names at certain resolutions etc. Software rendering works fine. Hopefully the screenshots I sent Lubos will help identify this.
I have tried 2.1.82 on LG L7II (768 MB RAM) and tablet Nexo Smart (more than 1 GB RAM). MFN on tablet works perfect but on smatrfon there is a big problem. Adding second, and sametime first, point via to the route couse that MFN is frozen and must be killed by task manager.
After upgrading to Android 6 with maps stored on the SD card adopting the SD card as internal storage navigator hangs when opening with the message waiting for SD card, only option was to force close. Will uninstall and reinstall to see if that cures problem.
I reset to default but this don't correct problem. But ..... I discovered that this problem appear only when route is calculating from form (window) "route plan". So ..... when after adding second point via (when appear window with list of point) I return to main window I select calculate route from utilities this work correctly.
Some feedback on 2.1.86 & 2.1.88 all in hardware rendering mode, Samsung S5 Mini stock android 4.4.2:
- Buildup of initial map screen still (much) slower compared to software mode
- losing GPS position and wandering off like reported before: In the last 6 150+ km trips and a few 5-15 km trips, it happened twice:
once on a almost straight motorway where it moved parallel to the highway (so no hard bends in the road), but it did not really loose position and did not do recalculations. This was a long trip.
once in a town (short trip) with many parallel streets where I picked a one too early "take right" bend. This street went parallel (about 50 meters apart) to the calculated route. The cursor showed I was on the wrong road, but the voice direction simply continued as if I was on the correct road. On the next crossroad (after about 100 meters) I wanted to do a "go left, go right" to get back on the route while Navigator still continued "as if nothing was wrong". Once back(!) on the original route, where the cursor and the route merged again, Navigator lost complete GPS position. And then it took way too long before it had recalculated the (original) route. So it simply continued as if nothing was wrong, and once on the right track again it lost GPS position.
From my point of view the first might be something wrong in the "prediction" algorithm to make the map movement fluent.
The second is of course due to my incorrectly taking the wrong road in a dense street network, but the fact it lost position only when back on the original route, coupled with the fact that it took so extremely long to recalculate the road in a 8 km trip, was weird.
Note: before every trip, even the short ones, my phone was rebooted (even though I hate to do that).
I will send my logs. I did record NMEA logs when it happened "all the time", but after Lubos asked me to record debug logs with setting to high, as he preferred that, I did not record those NMEA logs anymore.
I am still not able to reproduce the problem that occurs when you select an address from your contacts. Can you please provide more info? Is Navigator already running or do you start it from contacts? Does it hang every time for any address or just some? Thanks
I open contacts and tap an address and select Navigator to open it.
Then the screen gets black and Navigator does not react anymore.
After a very long time Android gives the popup that Navigator doesn't react anymore and offers met to close with the options wait, report OK.
Of course I choose OK to stop because if I don't it simply repeats itself.
Navigator always hangs. The only time I didn't hang was after a complete uninstall and fresh install.
And the next day it hung again.
Cleaning the cache didn't help.
And now that you are asking so specifically.
If I have Navigator opened, go to the main screen and open the contacts app and select an address from the contacts app it functions, and it functions all the time.
Then I closed navigator again.
Tried again from the contacts app and now navigator hangs again.