MapFactor Forum

tweakradje

Thanks for explaining. But it is odd and I have seen a lot navigation programs. None have done it like that.

There is only 1 route at the time. You can navigate that while moving or simulate it while stationary. There is no need for 2 seperate routes. It is odd.

tomas

simulate can have another departure then GPS position

tweakradje

That problem is solved another way in most programs.

It is weird that if I have a route already (with valid gps position) that is asks for another one if I go into simulate. At least accept the route that is already in there for navigation. It doesn't feel right.

Jan_Gruuthuse

Route information needs the gps chip to navigate
Tools: Route Simulation: works without GPS chip. You can simulate driving the route, up to 10 x speed.
My guess is, if you refer to calculate route, that it's there so you don't need to switch between menus

ualios

Circled in red

the point where MF returns useless "turn right" voice command. The major problem is that one could effectively turn right at the first link so going the wrong way.

Not tested in previus versions but I think it's a recent bug as all seems working well in Navigator 14 with updated map.

The OSM route coordinates HERE.

Tantum

I think that there is an issue how Navigator treats "link" roads. I experience similar behaviour as well.
--------------
Here I should get "continue straight" but I'm getting turn right
https://www.openstreetmap.org/directions?engine=osrm_car&route=48.15365,17.07573;48.15200,17.07572#map=18/48.15343/17.07575

IU0BMP

I could provide similar cases in Italy

Tantum

I don't think that this bug is related to the 1.6 version only....but it should be fixed as the navigation is not giving you right directions at the moment in the situations described above...and I experienced them quite often myself

IU0BMP

Yes.. it's an old bug

PrzemekSupak

Menu - Settings - Navigation - Detail Navigation - OFF, is much better.

(btw)

IMHO it is road:

https://www.openstreetmap.org/way/161754084

https://www.openstreetmap.org/way/85711741

https://www.openstreetmap.org/way/31433366

https://www.openstreetmap.org/way/31433363

Now Navigator 'turn right' on this node:

https://www.openstreetmap.org/node/15222312

(edit)

...or this road:

https://www.openstreetmap.org/way/72664969

is also link.

stavrich

"Assertion failed" incorrect state

I have tested the latest release v1.6.13 against v1.4.24 to check whether the assertion issue have been resolved.

These are my findings...

This was a simulation test using a verified gpx route that worked ok in real time and in simulation with v1.4.24 with both OSM and TomTom maps.

V1.6.13 using TomTom map completed the simulation with no problem.

V1.6.13 using the latest UK OSM map the simulation crashed with no error in the log file. During the simulation and prior to crashing it tries to recalculate the route (i dont think it should happen under simulation). Navigation stops and the app reverts to the starting screen "Select the map data you want to use".

See logs...

https://dl.dropboxusercontent.com/u/24255831/navigator_150512_082214.log.txt

https://dl.dropboxusercontent.com/u/24255831/navigator_150512_081551.log.txt

This could be a red herring but it happens all the time with the OSM map. So far it completed 3 simulations using TomTom maps but not tested in real time yet.

Can somebody confirm whether the "Assertion failed" bug has been looked up and resolved in v1.6.13.

Is there something wrong with OSM maps?

I like the TomTom maps as they seem to be giving better navigation but they are not updated (havent had an update yet) as often as the OSM maps.

I got stuck on v1.4.24 as any other release is unreliable and unusable in following recorded routes, just hope that this has been resolved even if its only for the TomTom maps.

ualios

Hi PrzemekSupak, you're right! Disabling "detailed navigation" option is much better, at least in that case.

With the following similar example the solution doesn't work as the router always returns erroneus "straight ahead" insted of "turn right". What could be the problem, maybe the extremely slight turn not detected by MF? In the example OSRM returns ideed the same "continue on..." while MapQuest has the correct "Turn slight right onto ramp".

https://www.openstreetmap.org/directions?engine=osrm_car&route=42.21902,14.49947;42.21722,14.49690#map=18/42.21811/14.49820

PrzemekSupak

Hi Ualios,

It is good example for Mapfactor team, to see it and maybe rebuild something.

There is motorway link connected with road, so at least 'slight right' is recommended.

You are right, with this extremely slight turn, but as I see, it is standard turn/connection.

It is better to connect this road closer to this node:

https://www.openstreetmap.org/node/311417856#map=19/42.21811/14.49861

and add 'lanes' and 'turn:lanes'.

@Stavrich, better wait for somebody from Mapfactor.

stavrich

@PrzemekSupak , I have been waiting for too long. I have the feeling that my issue has been forgotten or getting pushed back all the time..

How would I know when somebody from Mapfactor picks this up - I have reported the "assertion failed" problem some time ago.

I am disappointed and unhappy about this :(

PrzemekSupak

The only hint - try convert gpx to gpx or other format (routerconverter is one of the better).

stavrich

@PrzemekSupak , If your replying to my last post, there is nothing wrong with my routes as they work perfectly with v1.4.24. Most of them are either planned using routeconverter from scratch or garmin gpx tracks/routes cleaned and saved by routeconverter.

The problem started after v1.4.24. A change/release took place that screwed it up for me.

Now I am carrying two devices - one with v1.4.24 and the other with the latest version :)

Please note that I do appreciate your help and suggestions... thanks :)

SOFO

Hello together,

Is it possible to add the possibility to pause music or make it silent also for TTS voices?

Thank you.

Best regards

lubos

@stavrich - Can you try to repeat your crash with gles alpha build with software map renderer? (I hope this version should write something into log about your crash)

@SOFO - We are thinking about it, we are still not decided if we are going to implement it

stavrich

@lubos - happy to do it but where/how do I get "gles alpha build with software map renderer". Please advise what do I need to do and I will repeat the tests

chattiewoman

@stavrich
Find the download link here: http://forum.mapfactor.com/discussion/6476/test-of-android-gles-alpha-version/p1
The post also describes what you need to switch under settings - but not in your case, as Lubos asked you to use the software map renderer which is already default.

stavrich

@lubos - Here it goes...

Installed "gles alpha build with software map renderer" . ( @chattiewoman - thanks)

Simulation completed successfully with OSM and TomTom maps.

Reinstalled v1.6.13 and repeated test.

Simulation crashed with the OSM maps - same way as previously.
Simulation completed successfully with TomTom maps

UPDATE - Just noticed that although in v1.6.13 with TomTom maps the simulation completed successfully the log shows a number of "assertion failed" lines but somehow it recovers and carries on to the end.
ex- Line 130890: ERR 15/05/25 21:16:07 assertion failed (line:56 in src/ItineraryProxy.cpp).

the above "assertion failed" reported 12786 times out of 135225 lines.

With OSM maps it crashes - this (:56) was reported 143 times, then, it crashed after line 10211

Line 9170: ERR 15/05/25 20:27:50 assertion failed (line:56 in src/ItineraryProxy.cpp)
Line 9172: ERR 15/05/25 20:27:50 assertion failed (line:56 in src/ItineraryProxy.cpp)
Line 10210: ERR 15/05/25 20:28:16 assertion failed (line:115 in src/RouteEdge.cpp)
Line 10211: ERR 15/05/25 20:28:16 assertion failed (line:119 in src/RouteEdge.cpp).

Please note that none "assertion failed" reported with gles alpha build

Please see attached logs

https://dl.dropboxusercontent.com/u/24255831/navigator_150525_202353.log.txt

https://dl.dropboxusercontent.com/u/24255831/navigator_150525_204030.log.txt

https://dl.dropboxusercontent.com/u/24255831/navigator_150525_204556.log.txt

https://dl.dropboxusercontent.com/u/24255831/navigator_150525_180134.log.txt

PrzemekSupak

File navigation, language cs (Czech), 'sliproad_later', with tts, must be described as 'manoeuvre_tts' (now is manoeuvre).

-language 'de' and 'pl'. For tts 'sliproad_later' must be added (for both):

<manoeuvre_tts>

<type>sliproad_later</type>

<file>Bw-,%DISTANCE_AND_UNIT,-01</file>

</manoeuvre_tts>

(edit)

For 'pl' language it is better, more fluently:

File navigation.xml:

In section 'pl' add lines:

<manoeuvre_tts>

<type>sliproad_later</type>

<file>Bw-,%DISTANCE_AND_UNIT,-01</file>

</manoeuvre_tts>

<manoeuvre_tts>

<type>sliproad_now</type>

</manoeuvre_tts>

File tts.xml:

In section 'pl' change:

1. <text>Wybierz zjazd.</text> change to <text>Wybierz zjazd</text>

2. <text>zjedź z autostrady.</text> change to <text>zjedź z autostrady</text>

3. Bz-40-11 <text>potem</text> change to <text>, potem</text>

In section 'pl' add:

<text>wyjazdem</text>

</phrase>

(edit)

...and small changes with comas ',' and dots '.'.

lubos

1.6.19+ is here: http://download.mapfactor.com/mapfactor_navigator.apk

-bug fixes(crashes, intents and buying maps issue)

-waypoint checkbox clickable area in route info enlargered

-searching POI description limited to 3 lines

-experimental feature with notifying other apps about voice command hidden

stavrich

@lubos --- "-waypoint checkbox clickable area in route info enlargered" -

I haven't noticed any difference, it seems to be the same size as before.

lubos

@stavrich - there is difference only few milimeters

stavrich

@lubos - its still too small. Can you please make it a lot bigger so easier to check and uncheck the waypoint. I cannot think there is a technical restriction of not been made much bigger.

Please, please make it bigger !!

lubos

@stavrich - sorry but we wont implement bigger clickable area - there are gui items(views) structure(parents/childs) and enlargering would mean breaking this relationships of views.

stavrich

@lubos - i dont know how the whole thing is structured but I find it strange that increasing further the size of the active area button will break any relationships or affect any other views.

To be honest I wouldn't care of the size if Mapfactor could ignore missed waypoints after a set of time or next waypoint reached. Even having an easy way to ignore a missed waypoint would be much better such as a decent size box popping up an to request "proceed to missed waypoint or ignore". Anyway , these have been requested previously.

Having a bigger box would have been a simple, not ideal, workaround.

No offence but this reminded me of my techies (years passed) typical replies - :) as said no offence intended - :) :).

Anyway... we should be grateful for any size increases :-)

stavrich

@lubos @Tomas

My problem continues.......... Today I loaded the latest GLES version and run a quick, 28mile route, using OSM UK map.

Navigator crashed third way down the route. Restarted and completed the route successfully.

As you can see from the logs quite a few errors were logged on both logs, the crashed one and completed one.

I have attached both navigation logs and my route gpx file.

I hope this time you there is enough information to help you resolve this problem.

I am forced to keep using v1.4.24 and very unhappy not to be able to use the latest version with the latest enhancements ( especially with the enhancements that I have requested and were implemented :(( ).

https://dl.dropboxusercontent.com/u/24255831/NC-Woburn-NC.gpx
https://dl.dropboxusercontent.com/u/24255831/GLES 0-3-98_ERRORS_150619_101525.log.txt
https://dl.dropboxusercontent.com/u/24255831/GLES 0-3-98_ ERRORS 2_150619_103731.log.txt

Keeping fingers crossed...........

lubos

@stavrich please test current GLES version and give us know if it helps

stavrich

@lubos is there a later version than 0.38.98?

stavrich

@lubos - just downloaded 0.38.100. I will try it tomorrow, same route and let you know

Thanks

Chris

stavrich

@lubos -

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 to GLES topic as chattiewoman suggested - but I experience the same problem with the latest 1.6.20

chattiewoman

The max speed sign is changed. It's much better visible and readable than the old one. Thank you!

jd417

Similar problem to Stavrich. 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.

Moved to GLES topic as chattiewoman suggested.

chattiewoman

Issues related to hardware renderer only should be posted in the GLES topic http://forum.mapfactor.com/discussion/6476/test-of-android-gles-alpha-version

MapFactor Forum

Howdy, Stranger!

Categories

In this Discussion

Tagged