MapFactor Forum

Tantum

Thanks for the advice tomas. It turns out that the custom color scheme was the issue...when I reverted back to the default color scheme and then back to the custom scheme again...everything was fine...but the reset to default settings would have worked as well I suppose

Roldorf

0.38.98 works ok in simulation will try incar tomorrow. Moto g2 5.0.2

IU0BMP

I have tried.95 with my tablet for the first time while sitting on the beach. No gps loss at all. Maybe the issue is only on my phone. Will investigate further.

Tantum

@IU0BMP, not sure what's your OS but Lollipop has serious GPS issues across many devices...you can easily seach google for this...for example I only can use GPS on Nexus 5 in an airplane mode otherwise I get GPS drops every 5 minute or so. The issue is with the retrieval of the AGPS data as far as I understand

Android M should address this

chattiewoman

Then I'm lucky as I have Android Lollipop, but no GPS issues....

Roldorf

I also have no GPS issues on my phone. Orux maps works fine no drop of GPS signal.

IU0BMP

Hi all, here is what I have found. With my tablet running Android 4.4.2 there were no GPS issues with GLES .95 (I haven't tried .98 with this device).

With my phone (Lg L9) running Android 4.1.2 using GLES .98 there were frequent GPS losses (with the grey triangles) but the white dot was not blinking. Every time I lost the GPS, I tapped on 'tools', 'GPS info' to check the satellites and here there was no GPS loss. That is, according to GPS info, I had the fix. Going back to the map, the fix was still there but was lost again in about a couple of minutes or maybe less.

chattiewoman

Since a week, I am testing each latest GLES version on a Sony Xperia Z3 compact. My tours were not longer than 20 minutes, though.

Navigation was always stable, and there were never issues with lost signal or similar. The layout has improved much for me since the very first version.

What I have to report are not bugs, but mere suggestions:

When you turn into another direction than Navigator is directing you, the map is rotating into the direction Navigator wants you to turn. It takes more than a second until the actual GPS position "wins" and the map is rotated into correct direction again (and route recalculated).
I think this can be an issue when you are driving through an unknown city centre, missing turns or skipping them due to road works. Suddenly rotating maps can be a dangerous distraction then.
I understand this is a necessary result the smooth position change in map. Is it possible maybe that whenever Navigator wants you to turn somewhere (exactly then), the calculated progress is stopped for two seconds, considering only GPS?
Autozoom improved a lot since first version, but imho it could zoom in even more.
Compare the same position in old renderer vs. new renderer.
This is not especially for GLES, but I find here even more important than for old renderer: Please, please make service roads (much) thinner. This would improve clearness so much ... See also here.

IU0BMP

Chattie, point 1 is also related to the non-GLES version, right? I believe some delay is necessary before Navigator is "sure" that you have moved away from the right path.. IMHO, this has to do with the distance tolerance of the GPS system. Navigator might see that you are, say, 10 meters off course, but this can be normal when driving between buildings, etc. When the difference is more than that, then the app knows that you have really left the suggested path anf this can take more than a second...

chattiewoman

I cannot remember point 1 was an issue in old renderer too, because it showed no calculated progress. The map did not rotate in advance (!).

IU0BMP

Chattie, you are right.. the problem is worse with the new renderer, because it tends to predict your moves a bit too early. I noticed this in pedestrian navigation.

mdx

http://download.mapfactor.com/mapfactor_navigator_gles_alpha.apk
now points to version 0.38.100:
- update from DEVELOP 1.6.20+ [previous version was from 1.6.19 not 1.6.20, so some fixes were missing]
- optimization of click in the map
- delayed dehighlight of the current route
- fixed filtering of entities in different zooms (e.g. small creaks vs. small rivers)

hvdwolf

BUG: When tapping the map where a poi exists, normally 2 square brackets are displayed and when when tapping the i(nfo) button on the right it would also display the info for the poi. The 0.38.100 doesn't in hardware mode. It does in software mode.I don't know whether previous versions had the same bug, but that's not really relevant.
EDIT: It doesn't do this in hardware mode with imported POIs.

chattiewoman

GLES is still not usable in 2D mode, because of incorrect zoom level.

Back to 3D: when I run simulation and stop it, all fonts on map are upside down (this is fixed when I leave map and open it again):

hvdwolf

It has been mentioned before but tapping on the map works terribly bad. I have the idea that it works even worse compared to previous versions.

jd417

Hardware render version 0.38.100 crashed after two miles. Restarted & crashed again 6 miles after waypoint. Also suffered crash when updating maps from notification banner. Had to restart device then update maps from map manager.

stavrich

tested GLES version 0.38.100 and at the same time had version 1.4.24 running on another device.

GLES - OSM maps - failed again. It crashed after 4-5 miles. Restarted from the crashed point (cleared the first 3 waypoints) and completed the route.

Again, as you can see from the logs although it completed the route a number of errors were logged as well

I am attaching the route, the crash log, the completed log and the log from v1.4.24 which has no errors.

https://dl.dropboxusercontent.com/u/24255831/NC-Woburn-NC.gpx
https://dl.dropboxusercontent.com/u/24255831/GLES_0.38.100_OSM_150620_Crashed.log.txt
https://dl.dropboxusercontent.com/u/24255831/GLES_0.38.100_OSM_150620_Errors.log.txt
https://dl.dropboxusercontent.com/u/24255831/navigator_1.4.24_OSM_150620.log.txt

Let me know if you need anything else.

Many Thanks
Stavrich

Moved from 1.6x topic as chattiewoman suggested - but I experience the same problem with the latest 1.6.20

tvo

I have tried the GLES versions 0.38.98 and 0.38.100 in hardware render and 3D mode, for about 800 km and it is mostly running very well, and I like it, but I have some remarks.

1) I have also seen some problems with the gps. The 4 grey triangles are shown for 2 to 20 seconds and don’t move. As far as I remember, I never saw it in the “stable versions” of MF.

2) When I arrive to a roundabout the red maneuver arrow is still shown, but when I am inside the roundabout, the red arrow disappear and the map zooms out. I feel this a little bit frustrating. I would really prefer that this 2 things were delayed until I reach the end of the red arrow. And I also would prefer the same for a normal turn.

chattiewoman

I suggested it for something that affects GLES ONLY ;-)

lubos

@stavrich - it seems there is possibility to make renderer incompatible custom color scheme... see you PM please

stavrich

@lubos - done

hvdwolf

BUG: GPX file display.

When I open MNF and select to display a gpx track, it doesn't do that. It simply displays my last position. It does not move to the map location where the gpxtrack/route is to be displayed.

I first need to move the map to the approximate location where the route/track is to be displayed and then I see it.

This is a bug of course.

I don't know whether this is a gles bug or not, but I mentioned already before that there were GPX track errors in the GLES version.

mdx

The link http://download.mapfactor.com/mapfactor_navigator_gles_alpha.apk points to 0.38.103+
- experimental limit for FPS (Settings > Advanced > Maximum FPS)
- fixed option to change arrow/highlight color
- fixed order in info dialog
- fixed text orientation during switching navigation modes
- revised scheme editor (patterns on links)

known issues:
- confirmed bug @tvo 2 with roundabout autozoom
- missing texts/info for imports

chattiewoman

Can you explain what FPS is and how it works please? Never heard of it, and I bet some others neither.

lubos

FPS=Frames Per Second. When you reduce FPS limit rendering is less smooth but it should reduce overheating of device.

chattiewoman

Thanks!

hvdwolf

In this 103 and the previous 100 version I see "pins" on the road. Especially in curves, probably these are the nodes that define the "way".

Please remove, it is quite annoying.

Samsung Galaxy S5 mini (res 1270x720), Android 4.4.2, MNF gles 0.38.103

(Edit: Now the image gets so "blown up" I see that the icon in the top bar shows a pedestrian instead of a car which is my current profile. I checked to make sure)

And another edit: I now suddenly realise MNF is in software mode. why? Anyway, when switching backto hardware mode the pins are gone. Nevertheless, I prefer not to see those pins in any render mode

See image

IU0BMP

I have tried 103 and found that hardware mode was enabled by default (just as .100 version, maybe it remembered my old settings...). I don't see the pins on my phone, even in software mode. From the above screenshot, pins appear anywhere on the map, not just on the route and I agree they can be annoying. I guess they were not meant to appear on the map.

More important, in my case, this time I had no GPS issues. I used to lose GPS signal very often with the previous GLES version. If the developers haven't changed anything regarding this, then it must have been my phone acting up..

tomas

I cannot see nodes either, but I think that these may be text labels and not nodes
could it be that it is only because simulation is set to 10x speed?

mdx

@hvdwolf - those are not "pins" but "texts"/street names - did you experiment with scaling text?
@IU0BMP - yes, it remembers your previous settings if you "upgrade" APK (i.e. after uninstall you lose your settings)

hvdwolf

@mdx: Text size was almost to it's minimum setting in software mode and I didn't change that. At least not that I know. In hardware mode the text size setting was at its normal (default?) size.

Also: the menu tells me that I can change the size of text, road and icon size.

I can do that in the software mode, but in hardware mode only text and icon size are available. Road has disappeared.

mdx

@hvdwolf - thanks, this is probably a bug. I was told that the settings should be separate now (i.e. 3 for SW rendering and 2 for HW rendering = 5 different parameters in total) because they have different scale. Older GLES/HW versions ignored this settings completely and there was maybe intermediate phase when it used SW params. We will investigate it, thanks.

Roldorf

Route not found: start Fridolfing Landkreis Traunstein start, destination Lübeck, lübeck.

Tantum

Zooming is really good now, great job guys. I was wondering whether it'd make sense to make the roads just a bit narrower (since we can not adjust it anymore) cause roads close to each other still overlap.

hvdwolf

I agree with Tantum but at the same time I would like to display the minor roads at a lower zoomlevel as well. You really have to zoom in deep before you see them. I don't care about all the other details, but roads are important.

hvdwolf

A couple of bugs in 0.38.103:

Last afternoon and night I had to drive 140 km back and forth. I had rebooted the phone just before leaving.

When going back home at 23:30 it was still at day mode with the setting at automatic mode.
When I switched it manually to night mode, the sky still stayed blue instead of becoming black.
MNF crashed 3! times on the way back.

With regard to 2: Once I restarted the app, now of course in manual night mode, the sky was black.

W.r.t. 3: I know it is an alpha, but MNF crashes more often, also previous builds. I mostly reboot my phone when going on a trip now. It is as if MNF doesn't "clean up" after first use and crashes on what it left behind (in memory?) when starting again.

Tantum

I couldn't provide this earlier....but just to put my previous post into perspective. When you only have time to glance at the navigation...it's really hard to understand which road you are on...all of them are kind of just overlapped --- this is just before the turn...so zoomed in to max

Edit - just a comparison to see how many roads there actually are...very unclear from the GLES rendering

jd417

Motorola Moto G with Lollipop 5.0.2 & Navigator GLES 0.38.103.

In hardware render mode there is still the occasional random crash. I re-started my phone before a recent 45 mile (65km) journey & Navigator worked fine. I re-started it again today before a 6 mile (10km) journey & Navigator crashed after about 1.5 miles (2km). I re-started Navigator (not the phone) & the journey completed with no further crashes, as did the return journey. I've also noticed that Navigator crashes at the end of a journey (after the "Destination reached" message) but stays running in memory. Re-starting the phone appears to be the only way to close Navigator when this happens.

On a different theme I've not found any map updates yet for July.

mdx

OK, thanks for info. Regarding map updates I will write in different thread (http://forum.mapfactor.com/discussion/3999/mapfactor-osm-data-processing).

OT if you would like to translate GLES version there is now crodin project also for Android:
https://crowdin.com/project/mapfactor-navigator-android

mdx

Hello,
the link http://download.mapfactor.com/mapfactor_navigator_gles_alpha.apk now points to version 2.0.0
It is original GLES version merged with other features from DEVELOP like "i" in toolbar to switch between version with and without texts, some bugfixes, translation of list of maps taken from planet.osm, GPX changes ...

tvo

@mdx I think the problem with roundabout autozoom has been solved in version 2.0.0, only tested by simulation but it looks good. Thanks.

IU0BMP

Well, GLES 2.0.0 works as expected. It is usable. In hardware mode, the only flaw for me is that it is a bit slow when I browse the map on my device. Maybe it would be more fluid on a quad core....

In software rendering, it is more or less the same as 1.6.20, right?

rab

During route simulation, displayed navigation and voice gets sometimes complete asynchronous. Especially, when the simulation speed is increased

chattiewoman

@rab That's normal and not a GLES issue, because the voice itself cannot speak quicker, although the progress on road is. The instructions are then queued and appear on wrong places.
The alternative would be that while instruction 1 is not finished spoken yet, instruction 2 will be already started. Are you multitasking enough to handle that? ;-)

rab

I did not have this issue before. Now I get voice instructions minutes after displayed navigation has ended. So it must be related to my ancient single core phone, if you´re right.
:)

hvdwolf

I mentioned a few topics above that I have regular crashes with the gles version. I know it is alpha, but am I the only one? (As I see no other reports)

Yesterday over 187 km I had 3 crashes. The third at a moment I could really use the assistance. That was with the Netherlands map.

This morning in (Kingston-Upon-)Hull 2 times in 3 km!, and I really needed the assistance.

And then from Hull to York not once.

Please note that nowadays I reboot my phone (Samsung S5 Mini Android 4.4.2) before every trip.

So again: Am I the only one experiencing one or more crashes during every trip?

tomas

I do not travel often, but did some 60km on Saturday and had no crash

IU0BMP

Hvdwolf.. I may suggest you try the software rendering and see how it goes..

(there's a guy complaining about 'freezes' in the thread below and he's using the 'stable' version..)

hvdwolf

I will indeed try the software rendering the coming days. Such a useful and also such an obvious suggestion (Why didn't I think of that?)

Thanks

chattiewoman

But to answer your question: no, not a single crash with GLES (and hardware renderer).

MapFactor Forum

Howdy, Stranger!

Categories

In this Discussion

Tagged