Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - menion

Pages: 1 2 [3] 4 5 ... 729
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 04, 2019, 10:32:05 »
Ah, nice issue. Thanks for pointing on the problem with recording. Fixed. Same issue in Live tracking screen. Will rather double change whole critical places.

The issue in Store > thanks as well, fixed!

Hi guys,
can't promise I'll fix this to next 3.39 version. In the worst case, it will be fixed in 3.40.
Thanks for the bug report. I'll write you here once it will be fixed and ready for the test.

rozhodně, základní věc. Nastavení > ovládání > hlavní obrazovka s mapou > Držet pozici uprostřed.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 03, 2019, 18:55:42 »
And we talk about vector maps? Do you have any other content on the screen (overlay, wms, huge number of points/tracks)? Not all is optimized, but map rendering itself (map, overlay, wms) is.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 03, 2019, 16:47:15 »
New Beta version just published.

I've spent almost two days by tracking possible places of slowdown during map rendering. Do not know if anyone of you had any problems with it, but I register many reports that maps are slower and using more CPU then before. And I believe it was well invested time, so give it a try. Maybe you will feel any difference :).

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 03, 2019, 08:53:16 »
hmm really weird. I do not see a problem in the app, but on a few places, I've set to completely "ignore case", so hopefully it will help here.

The system is pretty simple ... for every vector MapsForge map Locus finds, it replaces it's ending from "" to ":osm.db" and search for this file. It does not matter what map version it is.

And complicated usage of POI.db? May only confirm. It is one of the top priorities to a more radical change in next months.

nice. Just tested it and indeed, Arndt correctly returns required time parameters for segments between route waypoints!

proč se tohle stalo opravdu netuším, nicméně mělo by pomoci se znovu přihlásit. V horním menu (tři tečky) je možnost se odhlásit, tak prosím zkus.

Maps / Re: Increase map resolution
« on: July 03, 2019, 08:09:02 »
Do not know if too fast, I worked on this around half of the year, but yes, it's done.

Resolution is chosen automatically based on device DPI, currently, I do not plan to allow its modification, but who knows.

With the world map, it is an interesting idea. I'll have to think about it, thanks.

[CZ&SK] - diskuze o Locusu / Re: ZOOM level ve verzi 3.38
« on: July 02, 2019, 15:50:20 »
Tak to klobouk dolů za trpělivost s odesíláním :).

Za mapy děkuju, jeden problém který by mohl být na vinně jsem našel a opravil. Pro tu multi-mapu se opravdu špatně generovalo její pokrytí a bralo se pouze z první mapy ve složce, v tomhle případě z té "ZABAGED_16_C2". A chyba je na světě. Díky

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 01, 2019, 23:52:35 »
Then it really looks like a problem I'm aware of, but I still do not find a method of how to "hack it". Seems that on Android 8, because of some issue directly in Android, apps running on background can't connect to 3rd party service over method we use (Locus Map & BRouter). On Android 7 and 9+, this problem does not exist. Also with GraphHopper (online), no problem ... stupid.

Troubles & Questions / Re: Problems with navigating a route
« on: July 01, 2019, 20:28:11 »
to the problem with "recalculation" ... believe it's better now, thanks!

[CZ&SK] - diskuze o Locusu / Re: ZOOM level ve verzi 3.38
« on: July 01, 2019, 15:13:12 »
Zdravím Čeldo,
díky za precizní popis, to bych snad nebyl schopen vymyslet takže jsem upřímně rád, že jsi tomu věnoval čas a problém našel.

Abych ušetřil trochu čas a přípravou dat které mi též nebudou fungovat (protože bez nich to prostě neopravím), poprosím tě o nahrání něčeho k testu, ideálně sem ať to máš snadnější. Děkuju!

Troubles & Questions / Re: Problems with navigating a route
« on: July 01, 2019, 15:08:28 »
thanks for the feedback. The positive one is rare and always welcome :).

When we talk about recalculation & BRouter, it is a little bit complicated. Locus Map already sends to BRouter information about the direction of users movement. It has a small effect on the final router, but not so big.

Current solution: Locus Map perform two recalculations in a row. When results of both are ignored, it places no-go point behind your movement which blocks recalculation back. So, if you miss turning and will ride still straight, in the worst case after 90 seconds you receive the result that won't force you back.

As Willy correctly mentioned, there are two options that may be fine-tuned (among others).
- number of ignored recalculations till way back is blocked (may be created as an optional parameter)
- hardcoded timeout (is in app +- since begin, have to be improved in the code itself)

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 01, 2019, 14:40:22 »
I do not agree. Some value "30 s" has nothing to do in UI. Firstly, no one should be interested in such value. The app works or not, that's the point. I told you this to give a better overview of what happened under the hood. And secondly, I really plan to make this value more dynamic, so there won't be a single "30-sec" value.

POI database should work the same, no matter which map version you have. Do you have correct naming, same as your map?

@Graf Geo
does problem with recalculation in the field happen also when the screen is on? Because if you have Android 8.x, there is a possible problem on some devices in case, the screen is turned off.

agree that fake GPS or any similar app is definitelly better and more robust system how to test. But, a lot more complicated (more steps).

Travel time: you mean travel time at bottom panel? In case of GraphHopper routing, times on route segments is estimated on their server. From my experience, they are usually quite precise.

In case of BRouter, there are no time and Locus Map know absolutely nothing about the route itself (surface, city/highway, ...). Just a routing type and is able to compute elevation. So app internally records your traveling speed during track recording or navigation for known activity and then use this average speed for a time estimate. Time is something like an "average" from the last 60 minutes. So these times are usually fine for a hike, where your speed is around the certain average value. In case of a bike, it may be worst mainly if you change a surface or bikes. In case of the car, these values are usually useless, mainly if you combine hour of a ride over the city and then you plan route over highway :). Hope my explanation is clear.

Perfect, I'm glad it works.

About tiles ... only "vector" tiles Locus Map works with are the one in LoMaps and other vector offline maps, like OpenAndroMaps. All online maps build in the application or added over this XML file are always raster maps.

Pages: 1 2 [3] 4 5 ... 729