I have just installed and am testing 2.1.92 and can confirm that the hardware rendering issues I previously reported are still the same. I can also confirm hvdwolf's problem regarding contacts. The screen just goes blank when you select an address directly from your contacts. You then have to force stop and restart. As stated, if Navigator is open then it works as expected. Hope this helps.

Hi Roldorf, can I please clarify when you say that contacts works. Is Navigator open when you go to contacts and select an address? I have tested both 2.1.93 and 2.1.94 and it ends up with a black screen if you go to contacts and select to open with Navigator but Navigator is NOT open. If I open Navigator then go to contacts, it works as expected. This on an HTC One M8 running Android 6 Marshmallow.

Navigation to adresses from contacts app does not work either here (MF 2194+, Android 5.1.1, Xperia compact 1).

If an adress including housenumber exists on the map, Navigator opens shortly, when it was closed before, and closes immediately without remaining any icon in the status bar.

If Navigator was open (icon at the status bar), "navigating" from contacts just switches to the map of navigator.

If housenumber does not exist and navigator is closed, navigation from contacts opens Navigator's menu "Choose action", with options "navigate", "set as start" etc. and I choose navigate, answer is "could not find routing point. Eventually point is in a country not downloaded." Same result for set as start. Navigator ends in a blue map. But I can add such an address to my favorites.

That is exactly how OsmAnd does it (but that one doesn't work either currently :) ) and how Here Maps does it. I don't know wether Here Maps also uses internet when it can't find the address in its internal database but it seems not.

I guess that Google's service is the most easy and convenient one as its parser is extremely well and returns a correct addresss out of almost everything you throw at it.

But the statement that Mapfactor can work offline is not entirely true.

Perhaps a setting for users to enable/disable online search would be better. This would of course require new functionality to first search in navigators internal address databases. The TomTom maps should be almost complete, the OSM maps less complete.

@tomas typed: "well, it can be done, but it would not find anything quite often- overall too much work for questionable result"

1. questionable also depends on how robust Navigators internal parser will become.

2. It depends on the country: There are 3 countries in Europe that have 99+% addresses correct: Netherlands, Denmark (even by law 100%) and either Latvia or Lithuania (never can remember which one). So these countries could really use it. I assume lots of other countires especially in "exotic regions" have hardly any addresses registered but in this case Google Maps is not a big help either.

By now this bug might get way too much attention and a way too high priority (as it is not at all a hard requirement or showstopper to be able to navigate correctly), but the "use a contact to start navigator and do something" is still not functional. I get one step further: It is now in the popup screen where I can set it as "Navigate to", departure, destination, show on map. I can even select one of the options (it gets focus), but then it hangs again until Androids "watchdog" offers me to "close, wait, report".

Now i have find out why it sometimes crash while exit.When i stop NMEA-Recording and go outside the Menu with the Right Bottom Button on Smartphone, the map will be on display. When i wait a short while and house numbers are visible and press then the Back-Button on the Phone and Exit, it works good. When i make this to fast and the map is not yet 100% on display, it freeze.

@Tomas: Your remark surprises me a little. You are testing a new version (and others within MapFactor I guess). I assume Mapfactor has change & release management in place. You should know what has been solved, or tried to solve, in your version compared with the 2.1.97 which is the current google play version.

Or at least there should be a changelog in your development environment based on the commits in that environment.

nothing will get changed in already released version, you have to wait for the next releaseI am not a developer, but I know that a lot of changes have been made to hardware rendering in v2.2.xjust be patient please

@tomas: That's not my point about the current and the future version. I can wait as the 2.1.97 version functions fine (for me).

What puzzles me is that you don't know what has been improved/fixed/added in your 2.2.x test version compared to the google play store version.

"Someone" should know what's in the changelog. I can't imagine you folks are just blindly fixing left and right and nobody knows what he/she or his/her colleague is doing, and neither that a test user doesn't even know what fixes he is supposed to test which were bugs in the google play story version.

One of the key focus points of development is to track what you have developed especially when multiple programmers are working on the same code.

@hvdwolfI am not the one to follow all the changes and list them on this forum, I am not in charge of development and I am not programerI know that hardware renderer has been substantially reworked, so it is not something we can list in detail

in any case, I do not recall anybody else reporting this issue, not even you, who usually comment quickly on any issue

I have been change & release manager for several OS projects (also for my own projects but that's obvious then). And maybe I did a terrible job, but for me it should be possible to answer very easily: "what has changed between the the previous versions and the version I'm supposed to test", because that's also what the end/test users want to know.

If you don't want to answer that question because you have some great new functionality coming up, I can fully understand. But in the past we have often seen (because I was also one of the users asking for it) from MDX and Lubos and some others as well (windows build) "alpha/beta x.y.z, fixed in this release, etc..".

And we as testers could verify that.

That is what my "complaint" is about, and that "changelog"question hasn't been answered.

please calm down. I've had just a simple question and nobody should have been blamed.

I'm patient and can wait for the next release. Up to now the 2.1.97 is fine for me. I can live with the minor bugs that obviously are based on the hardware of my cheap mobile phone. But I trust in stability and accuracy to go to Ireland in July >:D< . BTW: Any issues depending left hand traffic ? :-\"

Hi Joopy,I drove in Ireland about 2000 km in 2012 using MFN free and never got problems. My tip: exclude using of motorways and chose shortest route. You'll need more time but will get best impressions. But please look at sheep on roads then.Greetings to the shamrock shore and have a great time over there.

Ok, back to 2.1.*:Getting Information about map-updates and trying to load them direvtly out of that, I get a failure and can't download any. But starting MFN and the map management inside, updates ar shown and possible. This problem exists since more than a month or so.