The link now points to 0.38.90+ GLES Alpha:- fixed long routing highlight (I am not sure if that helps also in Tantum's case)- optimization in click into map (set routing points)- fixed loading icons from imports- increased size of internal cache for current view data- added "Automatic" into renderer selection dialog (note that your current HW settings changes to SW now, so you have to re-select it again ... Settings/Advanced/Map renderer/Hardware

it's good to see such an intensive development for GLES version, thanks mdx and the mapfactor team

- the bigger street names are giving you better overview of where you are however now it seems too big and rather distracting. In the certain view (I couldn't capture it) the street names now cover more than 1/3rd of my screen

- the lanscape zoom out seems still a bit too far when the next turn is further away (imagine that you're looking at this on a 5 inch screen which is cca 70-80 cm away from you)

EDIT:- also when I edit the color scheme and try do get back to the map view the navigator crashes

So far I like the GLES version a lot. However, it is still much slower in screen rendering compared to the software renderer. If you simply take a favorite and do "show on map" or calculate a long route (700+ km) and display the route on the screen, the screen is instantaniously drawn in software render mode and takes "some time" to render in hardware mode. I know this is an alpha build, but do you think the rendering speed will (much) improve?

I assume you use api version 2 for android 2.2 and up? Or version 3 for Android 4.3 and up? Based on the reports for also Android 4.2 users it must be version 2.

And ... I just downloaded 0.38.90 which has an automatic switch between hardware/software renderer and it chooses software on my device (Samsung S5 mini, Android 4.4.2). (I found out as it was set to hardware and the map didn't look like hardware).

@hvdwolf - I am not sure what do you mean? The map looked like SW rendering, but was selected HW rendering?? Or automatic?

The choice for "automatic" in 0.38.90 is simple - return SW. It is placeholder for future changes and it should be default value for release on Google Play (one day). The decision may change from version to version, but I expect device resolution, computation power and maybe also version of maps.

well.. I have been following this thread since it started but only today I decided to try this version. I have only looked at maps and tried a simulation with hardware rendering. No major bugs. The app works and looks smooth, but text size and icon size are too small for me even though I have set them to maximum size. My phone is an LG L9 (aka P760), I will try on my tablet, 7", Android 4.4.2. I will report if I notice something wrong.

I have a question though: does hardware rendering affect battery consumption?

@hvdwol - thanks. The dialog indexing shifted and that's why old HW (2nd position) changed to new SW (2nd position) ... yes, it could be done better. (as side-effect several people tested old SW rendering in 0.38.90 and it was crashing in some cases, but fix probably on Monday)

@Oldie - can you change projection? (Lubos says that it is probably the source of problem)

@IU0BMP - we did not investigate the battery consumption yet. We would guess that it will be slightly higher than in SW rendering. There is already (internal) parameters to limit the framerate, if it will help later the battery consumption.

UK download worked fine for me first time this afternoon on GLES. Anyone got any suggestions for screen sleeping during navigation?It makes this version totally useless for me, as I have to keep pressing button to turn back on.EDIT: (screen sleep fixed see below)

Yesterday I was driving and navigating.. The red arrow disappeared and reappeared again about every second. After a few minutes navigating, my phone froze and I had to remove the battery to turn it on again. Until next update, I will be using the stable version.

Hi folks - is it possible to ensure that the lower level roads are also rendered when zoomed out a little? If there is an issue with performance I'd rather disable the building rendering than the road rendering when zoomed out.

Only one comment after a short drive...the red color of the supporting arrow that shows the turns is not ideal as it has the same color as the arrow that represents your car...and when these two render on top of each other it's not clear which is which. The green color was better in my opinion.

I have tried 0.38.95 navigating. MFN didn't freeze or crash anymore, but lost the satellites very soon. The get the fix again, I switched to GPS Test (it seems to speed up the fix) and the fix was there, only to be lost again after a few seconds. This happened several times and I went back to the stable version which worked as usual.

Yes, I meant 1.6.19. If the GLES version really deals with satellites in a different way to 1.6.19, I can investigate further and let you know the results. This is the first time that I notice a different behaviour regarding satellites, between two different versions of MFN. Anyway, my test with 0.38.95 lasted only a few minutes...

I experienced similar behaviour than IU0BMP. Not sure whether it was related to gps fix or not but on a 10km route the gles version showed a status as of I wasn't moving 5 times. This did not happen with the previous test version.

Getting better with each fix. No more crashes in software render. Still a little zoomed out in hardware render compared to software render. As reported by IU0BMP & Tantum I too have seen loss of GPS (map appears frozen) for a few seconds before it recovers. Keep up the good work.

GLES 0.38.95 hardware rendering, only tried it in simulation mode, but nevertheless:*) after starting the app and calculating a route the initial map-display does not zoom to the route (shows whole Europe), from the second time on it does (see images)*) autozoom - the sizes look practical to me - a good mix of zooming in at maneuvers and giving overview the other time*) after some minutes of simulation the app crashes, especially, but not only when speeding up the simulation*) the speed limit symbol still is too small. It must have at least double the size to be useful while driving motorbike*) 2D-mode: the waypoint symbols in the standard app are too big for my taste, in GLES-version on a Moto G (4,5") they look alright (about 2 mm), while on a Nexus 7 they are way too small (about 1 mm)

(we are not sure if you report "old issue" or something new which could be wrongly interpreted as lost of GPS signal - due to snap to the same place or something similar)-----------The link http://download.mapfactor.com/mapfactor_navigator_gles_alpha.apk now points to 0.38.98:- fixed progress dialog for calculate route- fixed restart engines- fixed DPI scale of models (departure/destination/waypoint)- gray navigation sign during lost of signal- map scale for icons/texts- fixed coordinates in info panel- updates from 1.6.20- temporarily removed Mercator projection

known issues:- slow first click into map (due to lookup text for info panel) .... second click is "usable"

I believe the issue was really the loss of GPS signal. I remember the white dot blinking in the notification bar. I then switched to GPS test app and the fix was gone and then reaquired soon, only to be lost again when navigating. I guess I won't be able to make a video, but this issue is easy to describe. I will try again with 0.38.98 when walking or driving this weekend.