Locus Map - forum

Important links
- blog post (http://www.locusmap.eu/news-version-3-38-0) about major version (not yet published)
- list of news (https://help.locusmap.eu/announcement/version-3-38-22-5-2019) of public versions

Versions
22. 5. 2019 - Locus 3.38.0
...
13. 6. 2019 - Locus 3.38.4

Thanks menion for your work!

Will there be an automatic map change (loading) now with the "new" openandromaps V4?

Thank you for the new version, but now all my map themes are gone. I even cannot not find a setting for changing the new default (but ugly) theme. Did I miss a new menu point?

Best regards,
Tom

Ok, I didn't realise that the app switched back to the online map by default. So, after choosing a vector map I got my themes back. Rendering is great now. Thanks!

BR Tom

Hi guys,
@bezel
give it a try. New V4 should fully support auto-loading system. Because it is first attempt, it may not be 100% reliable so feedback is welcome of course.

@Tom
all themes are gone, hmm. Be you, I should firstly check, if they are (themes) in directory Locus/mapsVector/_themes. If they are correct there (mainly it's *.xml files), check default directory defined for vector maps in Locus Map > settings > misc > default directories.
Then suggest to check if you zse V4+ vector map. If even here all will be ok, best should be if you pack your "_themes" directory to zip and send me it for test together with information, which vector map use for test.
---
Ah ok :) (reaction to new post)

@menion
1. why do I have now a 10 sec delay with a black screen (free and pro) before the init screen appears?
2. from old thread https://forum.locusmap.eu/index.php?topic=6502.msg55408#msg55408
as expected both Locus maps have stopped auto backup on y Z1c Pie 9.0 :-(

Is there a possibility to start the auto backup with MacroDroid for now?

If you want again a catlog please tell me what to filter.

With 3.38 Free I lost all folders for tracks and points.
If I use old released 3.37 pro the folders are there.

Quote from: CabrioTourer on May 23, 2019, 16:20:50
With 3.38 Free I lost all folders for tracks and points.

I have all tracks but no favorites .

@tramp20
1. have no idea. Does this happen everytime you start the app or just after the update?
2. interesting problem. No support for Tasker or similar app exists currently.
What I suggest: set automatic backup to once a day and let it be. The app may really start backup in defined time +- few hours! App also needs a valid wi-fi connection. I plan to change the logic behind to one more reliable system, but it will need some time.

@CabrioTourer
Free version does not support "Folders". They are anyway stored in the database, so data are not lost.

@tramp20
what you mean by "favorites"?

Quote from: menion on May 23, 2019, 17:16:54
@tramp20
1. have no idea. Does this happen everytime you start the app or just after the update?
2. interesting problem. No support for Tasker or similar app exists currently.
What I suggest: set automatic backup to once a day and let it be. The app may really start backup in defined time +- few hours! App also needs a valid wi-fi connection.

@tramp20
what you mean by "favorites"?

Favorites: see screenshot, I had a icon for "at home".

to 1: this happens almost every time I start the app.
to 2: I use your apps from the beginning and should have enough experience :-)
The timer is set to daily, WLAN is ofc on, the backup never happens (even waiting some days), the date for the next planned backup is no longer updated. But after a occasionally reboot perhaps the next day the missing update starts automatically.
Neither a auto backup to the SDCard or to the cloud does happen.
The failure started with the last betas.

If you need a catlog at the planned start of a backup please answer how to do.

Hi menion,

thanks a lot for the hard work and the new version!
Some feedback:

• offline multi language maps entries are shown two times each: in Maps-Offline as well as in Quick Map Change:
  (https://i.postimg.cc/QBYjRypf/maps-offline.png) (https://postimg.cc/QBYjRypf)  (https://i.postimg.cc/dk7Jvj6w/quick-map-change.png) (https://postimg.cc/dk7Jvj6w)
  
• 
  LM doesn't want to close as intended: neither button down right + confirm
  (https://i.postimg.cc/1ntRYZ2C/Screenshot-20190523-183605.png) (https://postimg.cc/1ntRYZ2C)   (https://i.postimg.cc/f3P1Dnkg/Screenshot-20190523-183418.png) (https://postimg.cc/f3P1Dnkg)
  nor button down left and afterwards LM cross button top right
  (https://i.postimg.cc/f3P1Dnkg/Screenshot-20190523-183418.png) (https://postimg.cc/f3P1Dnkg)   (https://i.postimg.cc/BPbg6tyT/Screenshot-20190523-183450.png) (https://postimg.cc/BPbg6tyT)
  closes LM - it's still running (the two pictures on the right each show the status after the attempt to close).
  
  As a workaround, button down right - confirm - button down left - cross top right closes LM.
  

Regards,
Thomas

LM 3.38.0
Android 7.0
Samsung A3 2016

Quote1. why do I have now a 10 sec delay with a black screen (free and pro) before the init screen appears?

for me the delay take always ~5 sec

Oh, a huge update, thx. Will test, so interested in working mfv4 maps and theme system.
But what I see is still sad... Newest Elevate and a v4 map, and the city name overshadowed by "Wohnwagen-Platz"... Sizes of town/city names like totally random.

Attached: Kompass map at an awful zoom level. Seems like online maps are increased and interpolated drastically at times, in order to get readable text sizes. I have seen lots of blurriness on online msps.

It seems the route recalculation with track priority is now working well and routing me to a useful point on track consistently. Looks like I can give it a new chance. Very much appreciated.

Quote from: tapio on May 23, 2019, 21:10:56
Newest Elevate and a v4 map, and the city name overshadowed by "Wohnwagen-Platz"... Sizes of town/city names like totally random.

Could you post a screenshot?

Quote from: balloni55 on May 23, 2019, 20:31:34

Quote1. why do I have now a 10 sec delay with a black screen (free and pro) before the init screen appears?

for me the delay take always ~5 sec

similar for me, but has varied from ~2 to 10s. It seemed to get a little faster each time I started Locus Pro. I rebooted & then same experience - 1st start after reboot is slowest - 5s, then exit, restart ~2s, then exit, restart <1s - in fact fastest I've ever seen. But more troubling - the vector map is not always painted at app startup! Once the screen displayed "Settings > Online maps > Cached maps only". Another time the screen is all blank except GPS icon + "waiting" text at top of screen, scale at bottom, and no other controls! These 2 failures for ~30 restarts. This behavior didn't occur with 3.37.2.14. Am using single vector map.

custom screen:
rotate/slide of compas arrow/image didn´t work.
compas values work

Quote from: Tobias on May 23, 2019, 22:55:09

Quote from: tapio on May 23, 2019, 21:10:56
Newest Elevate and a v4 map, and the city name overshadowed by "Wohnwagen-Platz"... Sizes of town/city names like totally random.

Could you post a screenshot?

Cannot recreate it. But here is another example. I must correct, I used Elements theme. It displays a lot, but when zooming out town names should have the right prio...

I have also seen a start delay, black screen.

The new version has started making problems with the map.
After some time of use it stops map rendering, it is blurred. Clicking on zoom out / toom it causes the map to disappear completely.

Geocaches and offline points cannot be active (you can't click on them). Resolves Locus restart.
I use Lomap (Czechia).

I hope soon we will have v4 themes in presets.

On zooming in and out, I have seen tiles not properly painted at times. Sometimes half text, somtimes complete text at same ZL. v4 map oam.

After updating some maps (France and Italy LoMaps in the store) I cannot reliably go back out of the download page, using either the app's own back buttons or the Android back button. Occasionally it works but more often than not, it refreshes the screen but stays on the same page (saying the download and install is complete). I have had to quit the app and restart it to get back.

3.38.0 Pro - track & point exports have wrong version written to GPX:

<metadata>
<desc>File with points/tracks from Locus Map/3.37.2</desc>
</metadata>


Quote from: tapio on May 24, 2019, 08:29:55
I must correct, I used Elements theme. It displays a lot, but when zooming out town names should have the right prio...

Please use Elevate for normal or densely mapped areas. Elements is meant for countries like Iceland, northern Scandinavia etc.

Quote from: tapio on May 24, 2019, 08:39:07
I hope soon we will have v4 themes in presets.

They are. You have to edit your preset and add the option

My Locus Free has updated to 3.38.0 and is now no longer a beta (I think). However, there are no ads appearing.

Edit: ads now appearing!

I try to now exclusively use v4+ maps and themes. It seems like finally city/town/village names are displayed reliably. Great!

The rendering of v4 maps often goes along with significant delays. That smoothness of displaying also means some... confusion. I sometimes do not know if there's still some loading going on.

Starting Locus and instantly sending Locus Actions makes it crash. In Tasker, I had to insert Wait.

I confirm the functionality of the autozoom lock function.  Also, Locus now correctly detects breaks so route times and average speed are fine.  Good work.

Uff most of support on help desk finally done after two non-stop days, so let's continue here  ::)

@tramp20
should I understand that you lost all your points?
Problems with autobackup .. sorry, there is nothing how you may help me here. Maybe some optimization on your device has any effect here? Do not know. Anyway as I already mentioned, I want to rewrite service that takes of this, to little different and more reliable system. So later, thanks for understanding.

@Thomas S
1. really interesting. Just get same bug report on the help desk and have no idea how this happens. There is only a single file per map in your maps folder? Are you using "External maps (https://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_external)"?
2. Do not understand. Fact that application is visible in the list of recently used apps means nothing. This list only displays apps you used, not the apps that run. Also, on Android everything runs always, it says nothing. Important is if application do anything, if consume battery, CPU, internet etc. Do Locus Map anything when you close it? Hope not.

@Andrew Heard
quick restarts are never good :)

The wrong version in GPX, really? Please check it once more, thanks.

@balloni55
still anyone uses custom screens?  :'( Which theme should I use? Testing MS-UniCS and seems to work.

@lukasMK
this issue happens always after some time? If so, I'll probably need a bug report right after map disappear.

@chrisjk
ah, maybe two years old issue I still can't catch. Happen randomly and rarely. Solution? Quickly press back few times. If you find exact steps to reproduce it, it will be very welcome :).

@john_percy
thanks for the check of "Ads" functionality, nice :). I really hope we will be able to get rid of ads in the near future. I personally hate ads and have that all the time in Free version ... crazy.

@tapio
many posts from you, where to start ...

- sending action after app start: created log helps here
- performance of V4 maps: these maps are still little slower than optimized V3 maps. There is probably space for improvements, but this later

@Žajdlík Josef
good news, perfect, thanks!

---

General problems
- rescaling of the maps: yes, it is there :). Seems that some users have serious problems with this new system and completely ignore the fact that in previous versions, texts on raster maps were unreadable. Interesting. What you think about reducing this "rescale" to half? Compromise.

Usually, on most of the average devices with 1920x1080 resolution, rescale is currently equal to 3x. So common online map tiles 256x256px are draw on 768x768px on screen. This half cause rescale to 2x so it will be 512x512px. Still better then before and not so blurry as is now.

Delay in the start of app: still do not see a problem, but searching.

Can you allow for a userdef rescale factor? I was thinking a long tap on bottom bar +/- could do changes to the map scaling. Could even be used for vector maps.
As for rescaling: Yes, before, raster maps had ant size, and now some raster maps cause eye cancer.
Maybe the used interpolation algo is crappy? For comic like imagery, I'd say raster maps would fit here, there is an awesome upscale algo called waifu2x which I used for upscaling Dwarf Fortress tilesets, with great results.
https://en.m.wikipedia.org/wiki/Waifu2x

Also, hqx. Probably it's all about performance.

I hope, such settings it won't be needed. Anyway, it is doable in the future, just not as you suggest. Change of this parameter requires a full restart of the application.

Eye cancer: you exaggerate :). I'm sure, that with layer scale 100% maps are ok.

The custom algorithm is not possible. The whole logic is done in a lot lower in places, where I as app dev cannot touch ... somewhere deep in Android core.

Quote@balloni55
still anyone uses custom screens?  :'( Which theme should I use?

sure ;D till you implement this feature to dashboard
https://forum.locusmap.eu/index.php?topic=2340.0
sliding compas in yellow topbar isn´t visible

Quote from: menion on May 25, 2019, 16:07:14The custom algorithm is not possible. The whole logic is done in a lot lower in places, where I as app dev cannot touch ... somewhere deep in Android core.

But another idea, you could internally do a quality upscale when user downloads low resolution raster maps. You could do quality upscaling and offer such maps, if license allows, in your store and become wealthy.

For me, the raster maps are now great. Some are not available at high zooms (OSM Outdoor) so look really jaggy when expanded further to eg ZL16 @ 400% but others are available right up to high zooms.
They were completely unusable before, without using a fixed zoom on the device.

Sent from my moto g(6) plus using Tapatalk

@balloni
why you have in main.xml this
> locus:slideInfinite="[true]"?
Just remove the bracers around "true" and it should work. As I see, it does not work in latest 3.37 version, so seem you are not using it too much as well  ;)

@tapio
hmm no storing in Locus Store is unfortunately possible. Almost all data are downloaded directly from the servers of data providers. Really, there is not much to do around the quality of upscaled map tiles.

@john_percy
thanks, I see it the same. I still do not perfectly understand these complaints. Previously unusable, but crisp, maps are now finally usable like back in 2012 (no devices with huge DPI), it's amazing :).

---

Well so my idea and offer to find some compromise:

Current solution: all raster maps are scaled by device DPI, so it is usually 3x.

Possible improvement: all raster maps will be scaled by half of device DPI (rounded up), so it will be usually 2x.

What you all who use raster maps think? I'll probably release a Beta version in next few hours so we may give it a try.

Menion - can you please provide a download for the last stable version of LM for Android 4.1.1? Just for my old backup phone. Thank you.

Sure, all versions up to 3.37.2 are available here: https://docs.locusmap.eu/doku.php?id=manual:faq:devices_older_android#latest_locus_map_versions

Well, I had a look on the 2 raster maps I use. TopPlusOpen and Kompass. The size is pretty much perfect (a bit varying in different ZL). But I can see if Locus chose 2x instead 3x, it'll be too small again. I'd prefer to use it as it is now.

QuoteJust remove the bracers around "true" and it should work.

thanks, work again :)
please update manual
https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:screens#views

Quote from: menion on May 25, 2019, 15:28:06
@Andrew Heard
The wrong version in GPX, really? Please check it once more, thanks.

retested - all good - sorry to waste your time :-[

Quote from: menion on May 25, 2019, 15:28:06
@Thomas S
1. really interesting. Just get same bug report on the help desk and have no idea how this happens. There is only a single file per map in your maps folder? Are you using "External maps (https://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_external)"?
2. Do not understand. Fact that application is visible in the list of recently used apps means nothing. This list only displays apps you used, not the apps that run. Also, on Android everything runs always, it says nothing. Important is if application do anything, if consume battery, CPU, internet etc. Do Locus Map anything when you close it? Hope not.

• External Maps did the trick: in "Maps-Offline" view there was an "external" path set; after removing that path the issue is gone.
  Thanks for the tip.
  
• I try to explain.
  Press button down left and afterwards the cross top right in LM. LM just gets send to background and is still running (as LM notification in top panel says).
  You can also see if you start track recording first, then try to close as described --> track recording is still running.
  All other Apps (and all previous Locus versions) will be closed by this procedure.
  

I've got problems with my old theme, which uses the old menu style. Listing themes works, but if I select my theme it shows an infinite loading screen and after a while the menu to select styles pops up (see attached screenshot). It's rather cosmetic and not future oriented (I'm really to lazy to update it to the new structure), but probably you should know.
I use a Xperia Z5 Compact with LineageOS 14.1.
(https://i.postimg.cc/GBszdVqM/Screenshot-20190524-185013.png) (https://postimg.cc/GBszdVqM)

Zooming with hardware buttons doesn't work in route planer ...

The video shows that Locus is not able to draw the map properly if "detail (low zoom)" is turned off.

I am using a wms background map and a V4 vector map with the Voluntary UK theme as an overlay.

https://send.firefox.com/download/1546c2788b17d5d0/#kmHpxegmAO1O1jDai2nC1A

I've just published new Beta version (https://docs.locusmap.eu/doku.php?id=manual:about:free_beta_testing) 3.38.0.1 so give it a try if you will have a free moment. It should solve some major problems reported on the help desk and here as well (except new reports today).

It seems as if geocaching life map doesn't work in routeplaner anymore.
Normally I activate it in the map then switch to routeplaner and can see all the geocaches  along the road when creating a new route.

2 problems with new version:

• I have some not-yet-updated LoMaps. In last version, Locus showed me notifications about available updates once, I swiped the notification away, gone forever. Now on every start it reminds me again. Those maps I don't want to update right now, but can't get rid of the notification (other than deleting the map, I suppose).
• Activate Map Shading (relief), zoom out to an area where you don't have SRTM everywhere. I get lots of rendering errors, overlapping tiles, etc. Not everywhere, not all the time, so cannot give a recipe to reproduce, but clearly the map shading has a problem with the new map rendering. Zoom out and in once usually does the trick, but will happen again.

Quote
Now on every start it reminds me again

Same to me ...

Quote from: slarti76 on May 26, 2019, 15:51:30
2 problems with new version:

• I have some not-yet-updated LoMaps. In last version, Locus showed me notifications about available updates once, I swiped the notification away, gone forever. Now on every start it reminds me again. Those maps I don't want to update right now, but can't get rid of the notification (other than deleting the map, I suppose).
• Activate Map Shading (relief), zoom out to an area where you don't have SRTM everywhere. I get lots of rendering errors, overlapping tiles, etc. Not everywhere, not all the time, so cannot give a recipe to reproduce, but clearly the map shading has a problem with the new map rendering. Zoom out and in once usually does the trick, but will happen again.

Me too

@TrulloF
hmm, I was aware of this old system and tried to support it. But, unfortunately, I wasn't able to find any theme with this system, so please share it with me so I can test and fix it, thanks.

@jonny.blue
ah, same issue in track editor as well. Thanks, fixed

@locus.sv@heime.org
interesting issue. I'm quite sure that same issue happens in other apps as well.
From where is the theme you use? Anyway, I expect it will be a little complicated to solve. I have a similar issue in old V3 in case of shading on tiles that are without data.
edit: ah, got it (https://forum.locusmap.eu/index.php?topic=2915.msg55516#msg55516)
edit2: probably got it, the issue on Locus side, thanks

@slarti76
these updates are quite unfortunate. It should be checked once per 28 days, not more often :/. Isn't possible that one check was from Beta version and one from Pro version? Content of this notification center is shared between both versions.

And shading .. I'm playing with it and no problems. Does this happen to you with vector maps or also with raster maps?

Thank you for the new version.
I noticed a small issue: Using mapsforge V4 offline maps (openandromaps + Elevate), the track preview images are not calculated correctly.
For comparison, I attached a screenshot with the correct preview image rendered by locus 3.37 and the wrong image rendered by locus 3.38 (re-rendered by long-press on the picture).

Hallo !
I am too lazy to read all the logs here in detail  :o , however 3.38.0 stopped automatic map switching for offline maps even though "Auto-load maps of any type" remains on :-(

Quote from: Martin_ on May 26, 2019, 22:09:48
Thank you for the new version.
I noticed a small issue: Using mapsforge V4 offline maps (openandromaps + Elevate), the track preview images are not calculated correctly.
For comparison, I attached a screenshot with the correct preview image rendered by locus 3.37 and the wrong image rendered by locus 3.38 (re-rendered by long-press on the picture).

I noticed the same today.
Cheers
Michael

@menion
First, thanks for the app. It is a really great job :-)
My question concerns the resolution scaling. You see, I use Samsung A7 (2017) and have moderate myopia which works like a magnifying glass :-) So the default app resolution scaling behavior results for me in uncomfortable picture. When I change resolution with my fingers I notice that I see comfortable (for me) picture at 65% to 45% (as shown in app caption). But when I release the fingers the app changes the the scale level and the resolution  (to approximately 120%) and the picture becomes uncomfortable.
So what I am asking is - Is it possible to add the ability to "decrease resolution" in a sense of Settings->Maps->Advanced->Increase_Resolution?
I suppose it will help :-)

Quote from: menion on May 26, 2019, 21:52:17
@slarti76
these updates are quite unfortunate. It should be checked once per 28 days, not more often :/. Isn't possible that one check was from Beta version and one from Pro version? Content of this notification center is shared between both versions.

No, happens on both my phone with Pro & Free, and the one with onl Pro.
Btw, on my Moto G5 I also have a min. 5s delay at every start that others reported, too. Not on my S9.

Quote from: menion on May 26, 2019, 21:52:17And shading .. I'm playing with it and no problems. Does this happen to you with vector maps or also with raster maps?

I think I had it with a raster map. Can't reproduce it right now, either. Perhaps some caching problem that got solved with a restart, dunno. Will write again with more details if it happens again - for now forget it...

Quote from: ksv on May 27, 2019, 02:19:58
@menion
First, thanks for the app. It is a really great job :-)
My question concerns the resolution scaling. You see, I use Samsung A7 (2017) and have moderate myopia which works like a magnifying glass :-) So the default app resolution scaling behavior results for me in uncomfortable picture. When I change resolution with my fingers I notice that I see comfortable (for me) picture at 65% to 45% (as shown in app caption). But when I release the fingers the app changes the the scale level and the resolution  (to approximately 120%) and the picture becomes uncomfortable.
So what I am asking is - Is it possible to add the ability to "decrease resolution" in a sense of Settings->Maps->Advanced->Increase_Resolution?
I suppose it will help :-)

Menion, I think, finally you'll have to admit that there are legitimate reasons for zoom levels < 100%?! ;) You should allow it everywhere at least down to 50%, better 25% I think...

Hi Menion, long time Locus Maps user, thank you for this wonderful app !
I confirm the Zoom issue with SQL raster maps since latest 3.38.+ version, making views blurred and overzoomed.
(https://reho.st/thumb/self/a4782a5cecc73bd7b75d57fd831595cb6b43e09b.jpg) (https://reho.st/view/self/a4782a5cecc73bd7b75d57fd831595cb6b43e09b.jpg)
As you can see Zoom level is set to 100%
(https://reho.st/thumb/self/961c73f0a07fb32d4a1afc047a5f9d865def4a30.jpg) (https://reho.st/view/self/961c73f0a07fb32d4a1afc047a5f9d865def4a30.jpg)
And surprisingly, maps details show Zooms (tile levels) are 18 to 25, while when maps are downloaded, selected levels are 10 to 17.
(https://reho.st/thumb/self/b6660a166a0876c0519f1ee57aaab6b794b0ed23.jpg) (https://reho.st/view/self/b6660a166a0876c0519f1ee57aaab6b794b0ed23.jpg)
Maps' source is IGN.
BTW zoom level is no more displayed when you click in Map Scale zone.
Same behavior with both beta and latest Pro version.
My device is a Huawei Mate 10 Pro, its resolution is 1080x2160.
As recently suggested, being able to set a zoom level <100% could be a quick fix.
Thank you again !

Hello menion
on my small GC walk this morning i noticed that map isn´t centered althought the center button is active, if the label of the target is visible on map while i am guiding on it. If i get clother to my target the map center move more and more out.
Behavior is with FREE 3.38.0.1 as well as with PRO 3.38.0

Just updated to version 3.38 from 27.5 ...
The first start has worked.
Then I switched from an old LocusMap to new V4 Vectormap ... and I had my first crash.

Now every start of LM pro leads directly to a crash ...  :-\

Quote from: jonny.blue on May 27, 2019, 19:37:38
Just updated to version 3.38 from 27.5 ...
The first start has worked.
Then I switched from an old LocusMap to new V4 Vectormap ... and I had my first crash.

Now every start of LM pro leads directly to a crash ...  :-\

The same here :-(

Thank you for tonight's update bringing option to enable/disable atomatic map rescaling in Settings > Maps > Offline, I can enjoy again my offline raster maps  :-*

Same here - just updated and LM crashes immediately when initializing the V4 vector map. :(

Yep, instant crash. Will downgrade.
https://drive.google.com/drive/u/0/mobile/folders/1U8U1D-NGQ9CAnqXAkleEXi46wH2T7tMR
Edit: don't know how. Will wait.

I had the problem with instant crash too, but I following fixed it:
Rename the "locus"-folder on sd-card. Start locus. Select "ok" for a new Locus-folder. Exit Locus and delete the new locus-folder. Rename the old Locus folder back to "Locus".
I have no idea why, but it worked for me.

I will not experiment. Want to avoid having to reconfig Locus if shit happens.

Got 38.1 via playstore (pro)
Now App crashes after (I guess 100% initalisation). Maybe earlier. Even the Crash dialog window closed.

Same for Free

Quote from: berndy2001 on May 27, 2019, 21:02:36
I had the problem with instant crash too, but I following fixed it:
Rename the "locus"-folder on sd-card. Start locus. Select "ok" for a new Locus-folder. Exit Locus and delete the new locus-folder. Rename the old Locus folder back to "Locus".
I have no idea why, but it worked for me.

Works for me UNTIL I select V4 ML map. Now it crashes again.

Where I can get 38.0 ?
Have to guide a larger group this Thursday.

38.2 pro crashed. I urgently need version 38.0!

Quote from: CabrioTourer on May 27, 2019, 21:51:31Works for me UNTIL I select V4 ML map. Now it crashes again.

I can confim that. Fortunately, the selection is not saved and after restarting Locus I can select a different map.

Quote from: CabrioTourer on May 27, 2019, 21:53:08
Where I can get 38.0 ?
Have to guide a larger group this Thursday.

If you are happy with 3.37.2 you can find it here: https://drive.google.com/drive/u/0/folders/16q5n2FcbJ62AhWKoT3vS5CyuEhfuji25

Same issue with 38.2 free. Stopped autoupdate of pro for now...need locus over the upcoming long weekend...

Gesendet von meinem D5503 mit Tapatalk

Quote from: CabrioTourer on May 27, 2019, 21:51:31

Quote from: berndy2001 on May 27, 2019, 21:02:36
I had the problem with instant crash too, but I following fixed it:
Rename the "locus"-folder on sd-card. Start locus. Select "ok" for a new Locus-folder. Exit Locus and delete the new locus-folder. Rename the old Locus folder back to "Locus".
I have no idea why, but it worked for me.

Works for me UNTIL I select V4 ML map. Now it crashes again.

Exactly the same for me on both Pro and Free 3.38.1.
Now both working until I select a MF V4 map.

Sent from my moto g(6) plus using Tapatalk

Hi guys,
3.38.2 version crash as well?? Just published half an hour ago ...

Seems that four days of non-stop work is too much on me. Believe that 3.38.2 will be ok now. Sorry for 3.38.1, still do not understand why app crashed but should be fixed. Good night ...  :-X

Edit: seems it is not yet available for download (23:30 CET). expect it every minute ...

Just upgraded to 38.2 ... and the crash is gone.  ;)

BUT it is not possible to use a V4 map.
The screen creates only partialy tiles ... and with zooming some of them disappears while others occurs ...  :-\

Same for me.

Sent from my moto g(6) plus using Tapatalk

Interesting ... any information that helps to simulate it?
Certain map? Certain theme?

Crash gone. I switched from an sql vector map (topplusopen) to OAM v4 map/volUK - like 1 minute of white screen, I pressed zoom in/out numerous times... at some point map tiles appeared. Painfully slow.

Quote from: menion on May 28, 2019, 06:28:38
Interesting ... any information that helps to simulate it?
Certain map? Certain theme?

The Voluntary UK / Transparent theme does not draw properly, but others do.

https://www.openandromaps.org/en/oam-forums/topic/voluntary-uk/page/7

(I am using Voluntary.zip with V4 maps)

No, same non-loading and white blocks with Elevate. As for VolUk, I am using Johns latest version he posted at the end of his thread here in this forum.

You were right, it was 38.1 free which crashed for me yesterday evening...i thought it was already 38.2.

Real 38.2 does not crash any more (at least with elevate.

I have one theme which causes locus to crash under certain circumstances, but this might be related to my ongoing attempt to convert this from v3 to v4...

Gesendet von meinem D5503 mit Tapatalk

An issue with semi-transparent themes found, hmm new version will be needed, thanks.

@zossebart
long click on your theme in the list of themes > validate. If all is ok and theme still causes problems, send me it for the test.

38.2: "Increase map resolution" is absolutely ineffective for raster maps. Doesn't matter if "Select map resolution automatically" is on or off. Also, the map resolution increment in all my presets was reset to 100%. Not that bad, as I have to find new best values with the new system anyway, but still...

Apart from that bug: I know it's more complicated, but all the problems with "Increase map resolution", especially for raster maps everyone seems to be having, I think the only feasible solution is to make this a property of the map. It's obvious that different raster maps look best in different zooms/resolutions.
It's nice and well that Locus choses the base resolution based on dpi, but then the user has to have the ability to adjust this according to reality and personal tastes.
I would propose that every map gets a "Resolution adjustment factor" from, say 25% to 500%. At least all offline maps. Then there's still the general "Increase map resolution" in settings/presets which allows to adjust resolution based on activity (e.g. biking needs more zoom because I look at it from further away).

What do you think, too difficult?

PS: Ok, I tried a raster map downloaded with Locus, there Increase Map Resolution worked. But with an OruxMaps map, it doesn't have any effect. Anymore, still worked in 38.0

Sorry, not planned for now. Understand that not all raster maps look same, but this fine tuning for the specific map will have to wait.

Also, this scaling does not change map tiles itself, so downloaded map in Locus will be exactly the same as with older versions.

One quick morning request. Firstly I wanted to wait a little with the third bug-fix version in the row but seems that all major problems are now solved except this issue with semitransparent MF4 maps.

So I would like to publish a new version in the next hours. If anyone here actively translates, find 10 minutes and finish some translations on crowdin (https://crowdin.com/project/menion), thanks!

Quote from: menion on May 28, 2019, 08:44:46
Sorry, not planned for now. Understand that not all raster maps look same, but this fine tuning for the specific map will have to wait.

Ok.

QuoteAlso, this scaling does not change map tiles itself, so downloaded map in Locus will be exactly the same as with older versions.

Not sure what you're replying to? I'm still positive it's a bug that my OruxMaps raster map is not affected by "Change Map Resolution" while the ones downloaded with Locus are. It does work with OruxMaps map in 38.0, so something changed...

Quote from: menion on May 28, 2019, 09:13:48
...except this issue with semitransparent MF4 maps...

There's also a cosmetic issue with semi transparent MFv4 maps and the transition on changing zoom level. It shows up most clearly with woodlands on my Voluntary theme. The wood is shown with a semi transparent green fill. Changing zoom brings in the new layer with 0% transparency and then fades out to the correct level, so the wood transitions through a darker green flash.

Sent from my moto g(6) plus using Tapatalk

Quote from: jonny.blue on May 28, 2019, 00:04:29
Just upgraded to 38.2 ... and the crash is gone.  ;)

BUT it is not possible to use a V4 map.
The screen creates only partialy tiles ... and with zooming some of them disappears while others occurs ...  :-\

Here the same:  https://youtu.be/NTQC4dIbQw0

Faulty behavior in the interaction of Locus Pro 3.38.2 and Openandromaps V4 on May 6, 2019. Themes "Elements" from May 2019. Also Theme "Desert". Also Theme "Allgemein" ("General"?). All themes are proved as correctly installled. Android 7.1.1

Maps of version 4 are only partially displayed more or less randomly, the image build-up is slow.

From 0:52 - 1:06 I show the same Openandromap but version 3 is displayed quickly and completely.

with 3.38.0 Openandromap V4 and Elevate and Elements everything is going great
S8 with Android 9

Hello

With today's update 3.38.1, Locus Pro will no longer work on my Galaxy S8 plus (Android 9): '(
It starts, but then after the start the Starting screen the APP closed immediately.
Yesterday, Locus Map still works
Does anyone have the same phenomenon?
Is it possible to restore the previous update?

Greetings Wolli

Hi
after update to version  3.38.2  Locus Map  works again

on my SM-t311 with Android 4.4.2 (with locus pro 3.37) I receive on start up a window saying for some online maps "cannot obtain zoom level"
I tried to update to 3.38 but google says it is not compatible.
Hartmut

After update to 3.38.3, MFv4 maps work again. Phew.

Sent from my moto g(6) plus using Tapatalk

As John already mentioned, hopefully, final new version 3.38.3 is out.

As I wrote on help desk (copy content here):
If you still won't be satisfied with how maps look like or behave in latest 3.38.3 version, here are a few tips:

• automatic scaling: may be disabled in Settings > Maps > Advanced features > Optimized raster map resolution
• slower zooming: check automatic loading in Settings > Maps > Offline maps or alternatively you may try to disable some map animations in Settings > expert settings > Smooth interface
  
• incorrect display of 512x512px online maps: 512x512px tiles with same indexes (x, y) as for 256x256px does not make sense. Previously it worked more like an accident then an intent. Do make it work correctly, it is needed to use the method I described here.

Thanks for your help here and also big thanks to a few quick translators!

3.38.3 first start with nullpointer exception and no map loading. Subsequent starts ok and look like v4 vector maps work again. Slower as v3 maps but acceptable. Edit: not even sure about this. I'd say GOOD JOB MENION. A big step forward. I am finally and exclusively using v4 maps and themes.
Expecting more bugs since this 3.38 is a big update.

Many thanks that we can turn off map smoothness. It's more transparent and direct this way.

And it runs great on my meanwhile very outdated Sony Z1.

Performance of V4 maps is still little worst than older over-optimized V3 system. Maybe I'll later invest some time here as well, we will see.
Disabled "Smooth animations" has (almost) no effect on modern devices, but should be useful on some low-end phones or just for play & test. Anyway, I think animations look good and it's important :).

I still expect many problems, but main issues should be solved now and the app seems to be stable. Uff ... finally.

Animations still have problems and don't look all that good with semi transparent MFv4 maps as in https://forum.locusmap.eu/index.php?topic=6579.msg55620.msg#55620

Sent from my moto g(6) plus using Tapatalk

I still don't like the way "Magnify all maps" works. But I've also realised it doesn't respect the value in settings.
I can adjust the value to 150% in settings using the slider, but the map is actually magnified by 200%.

Sent from my moto g(6) plus using Tapatalk

I was looking on problem with alpha animation maybe for an hour before release, but then I rather decided leave it to later then risk a problem. So I know about it and will look at it.

About "magnify all" ... ah very good observation, I see it too thanks!

Sent from my Pixel 2 using Tapatalk

Just for interest: What are these "animations" for? could they be a reason that maps looks slightly more unsharp than if animations turned off (e.g. due to some picture scaling, picture filter etc.) ?

38.3: "Magnify all maps" works again for OruxMaps maps, but weirdly only on second try (first time I changed to that map, the button had no effect, after switching back to another map and then back again, it was fine. So OK now.

Still getting notifications for map updates on every start. Did you have a look at that?

@sonny
animations are for "good feeling" of course, nothing more. Effect on the sharpness of images definitely not.

@slarti76
interesting problem with OruxMaps, nothing like this noticed but will watch it.

Notifications for updates are really weird. Yes, I looked on it and should be fixed, weird ...

GC waypoints with hidden coords N 00°00.000 , E 000°00.000
> select location > Select on map
no map is visible
and
> select location > Screen center
no mini map in preview visible

Quote from: menion on May 29, 2019, 13:37:10
@slarti76
interesting problem with OruxMaps, nothing like this noticed but will watch it.

Thx. It actually happens again from time to time, but couldn't figure out the conditions yet. After switch to another map, it usually works again, but not all the time.

QuoteNotifications for updates are really weird. Yes, I looked on it and should be fixed, weird ...

Actually, now they're gone. It's possible, this time it was my fault, not cleaning the notifications. Sorry for false alarm.

One more thing: Can't find the switch to turn off map rescaling, at least it's not in Settings>Maps>Offline (I definitely saw it in the beta).

Quote from: john_percy on May 28, 2019, 20:42:03
I still don't like the way "Magnify all maps" works. But I've also realised it doesn't respect the value in settings.
I can adjust the value to 150% in settings using the slider, but the map is actually magnified by 200%.

Sent from my moto g(6) plus using Tapatalk

I can confirm this, "Magnify" uses the same factor no matter what I select in dialog. Maybe this is also in relation to my problem with it sometimes not working at all...
That being said, at least I think raster maps do look better now when magnifyed.

Excuse me, if this problem has already been mentioned here.
My English is not so good that I want to read the whole thread. Therefore I use the DeepL translator here.

After updating to Locus 3.38 and downloading openandromaps maps V4, the current map is no longer displayed or updated in the list of offline maps if the map itself was moved to Locus and a completely different map is displayed.

Screenshots: in the list the manually clicked map Berlin ML remains highlighted in orange, although Locus itself has been moved to the Canary Islands.

Another minor problem:

After restarting locus no map is displayed at the cursor position, only after zooming or moving the cursor does the map reappear. (This happens if another map is marked in the list than was last displayed at the cursor position. See 3rd screenshot)

BTW: Despite these small inconsistencies locus is one of the best apps I've ever used! (https://uploads.tapatalk-cdn.com/20190529/f35a5ac048d81b99af605dc6fa43bab7.jpg)(https://uploads.tapatalk-cdn.com/20190529/b07bb73f725ac936ec1e621b6617ce91.jpg)(https://uploads.tapatalk-cdn.com/20190529/fe4e977a4d879fbadf9cf980db55becd.jpg)

Have you upgraded to 3.38.3 ? There (most of) the vector maps issues are resolved..

Hi Menion
I think I now solved the "Magnify all maps" mystery:

• The map doesn't get magnified when I'm already in the highest available zoom level. This kinda makes sense given the new system that uses the next zoom level and then enlarges the tiles. But it's confusing to say the least. I didn't notice this in the downloaded Google Maps, because it has more levels than my OruxMaps map.
• The same observation also explains what John and I experiences: In fact, the magnification is not just 200%, it's the relation between the two levels. E.g., from level 1:50000 to 1:25000 it's 200%, from 1:25000 to 1:10000 it's 250%.

Now I'm not totally sure about your concept right now, but I have the feeling that you can't keep the current system together with a freely definable zoom factor. Either you go back to the old system, just enlarging the tiles by X% (and thereby changing the field of view). Or it becomes simply a "Magnify" switch that uses the next best zoom level, but same field of view. Of course, for the highest available zoom level (see 1), you'd still have to enlarge the tiles by a fixed factor, let's say 200%. But right now, the zoom selection is pointless.

EDIT: Well, it's probably possible to have both by choosing the lower zoom level and adjusting the zoom factor in a way that the tiles are enlarged just as demanded by the setting, while keep the field of view. Just some maths. ;)

Quote from: michaelbechtold on May 29, 2019, 18:15:20
Have you upgraded to 3.38.3 ? There (most of) the vector maps issues are resolved..

Yes I did...
(https://uploads.tapatalk-cdn.com/20190529/3a6be592d50f6e7e2bd462fbcaf9db92.jpg)

- zooming out any LoMap, till ZL12 map is displayed
- ZL11 is always blank white >LoMap "World" is visble in top label
- ZL10 world map is visible
same behavior vice versa

"magnify all maps" on vector maps was good any time before, now it's broken. 125% is not magnifying , 150% same as 200.

With 3.38.3 excellent comfort-looking raster map picture is back. Many thanks :-)

Route Planner 3.38.3 almost unusable:
All actions on points (POIs, track points) are unavailable, see screenshot ("Add" is just a text, clicking has no effect).

Quote from: slarti76 on May 30, 2019, 10:21:03
Route Planner 3.38.3 almost unusable:
All actions on points (POIs, track points) are unavailable, see screenshot ("Add" is just a text, clicking has no effect).

Cannot confirm. On Poi it offers me 3 kinds of points to add. Maybe some icon cache related thing?

Quote from: tapio on May 30, 2019, 10:39:50

Quote from: slarti76 on May 30, 2019, 10:21:03
Route Planner 3.38.3 almost unusable:
All actions on points (POIs, track points) are unavailable, see screenshot ("Add" is just a text, clicking has no effect).

Cannot confirm. On Poi it offers me 3 kinds of points to add. Maybe some icon cache related thing?

Perhaps. After restart, options did appear again for POIs and special points, but not when clicking on a plain track point. Weird...

Regarding route planner. Sometimes it losts all (or a part) of shaping points. Can't find a way to reproduce.

The reason for this post is a different one.
I have a preset with hold center disabled for planning and one with hold center active for Navigation.
Today, in the middle of navigation the hold center doesn't work anymore. It's a known issue for a long time and after switching presets (means hold center on/off) multiple times it works again in the past.Today it wasn't possible to make it work again. I tried it a long time. I generated a trace log. Maybe this helps.

In the end the only way to fix this was to stop Locus App and start again.

The Gpsies moduleis rather clunky and could be more condensed and offer multiselection.

And something easy to fix: after download of a track a new window appears with just the message that download was successful.
EDIT: btw I cannot find the download.
A green hint would totally be enough.

@balloni55
well, 0.0/0.0 coordinates are by Locus Map considered as invalid, so there is more probably some crash on the background.

@slarti76
- during last days I've found a few more problems with maps, so you issue with OruxMaps may be the same, already fixed, issue.
- the switch is in advanced settings.
- scaling issue: good observation to you and John. "Magnify all maps" did not work correctly as John mentioned some time ago. I've spent on this some time yesterday and now it finally looks correct. It will anyway need testing, so next Beta. And thanks for the precise description of the problem :).
- the problem in route planner: this happens on both your devices? Seems you have some super-huge screen resolution, it is on your Note 4?

@Graf Geo
once a selected map is for forever as the main map. So if you zoom away, this map will always be visible in the top. Maybe I'll change this later, but for now, it works this way.

Problem with empty screen after the start is interesting. It looks like automatic loading is not working correctly right after start. I'm sure it will work correctly if you keep enabled GPS, because this force app to refresh map screen every second.

@balloni55
ah thanks. All world maps use max. level 11, but this LoMaps world map is valid only to level 10, so I have to hardcode this parameter into app.

@tapio
- problem with "Magnify" confirmed and explained above in answer to slarti76
- GPSies, well not an important topic now. Tracks are anyway downloaded into MapItems system.

@CabrioTourer
there was some changes in "hold center" system and it should be automatically disabled for route planner now, so no need to play with presets because of this. Log anyway won't help, I'll have to play with it a little more with hope to simulate it.

Quote from: menion on June 03, 2019, 09:56:16
@slarti76
- during last days I've found a few more problems with maps, so you issue with OruxMaps may be the same, already fixed, issue.

Thx, but I think the real problem was what I wrote later about the magnifying: I was already in highest available zoom level, and then it didn't do anything, no matter what the (raster) map.

Quote- the switch is in advanced settings.

Ah, I see the misunderstanding. It says "Optimize raster map resolution... based on dpi". I thought there was a switch to turn off the whole dpi concept, but I remember you don't want to keep the old system at all, so obviously no switch. All fine!

Quote- the problem in route planner: this happens on both your devices? Seems you have some super-huge screen resolution, it is on your Note 4?

Actually, I could solve the issue with a "Clear Cache" from Android's App Info for Locus. Thx to Tapio, who mentioned possible caching issue - that seems to have been it. I think, whenever there is something wrong with icons, you should first clear cache. Can't hurt, anyway...

Quote from: tapio on May 25, 2019, 17:20:57
But another idea, you could internally do a quality upscale when user downloads low resolution raster maps. You could do quality upscaling and offer such maps, if license allows, in your store and become wealthy.

High quality upscaling of high contrast edgy raster graphics is much more sophisticated than upscaling of photos.

Upscalers often use advanced, edge directed interpolation, some even with support of outputs of neural network training, like NNEDI3 library of Avisynth video frameserver.



Odesláno z mého Mi A2 pomocí Tapatalk

Hello menion
any answer/solution to my post #59 ?

Ah sorry ... this is old behavior. It should be the same in all previous versions. The map is really not centered in case, there is any visible label. It should prevent jump of the label below fingers in case, you work or just watch this label.
Your correct point may be that in case, the label is out of the screen, it is not clear why the map is not centering, right? This happens to me once or twice and agree, it is not optimal.

Quote from: menion on June 03, 2019, 15:07:03
Your correct point may be that in case, the label is out of the screen, it is not clear why the map is not centering, right? This happens to me once or twice and agree, it is not optimal.

thanks for your answer.
the behavior of label  is different for now
- if i start Guide on from label with "> Guide on" the label disapeare and all work fine :)
- if i start Guide on from POI detail the label is displayed furthermore :-[
so please make it consistent, if Guide on is started, hide label

I think this isn't mention in changelog for 38.3.1. Redraw of map after zoom change / movement is much faster. Great

Ah yes, new Beta 3.38.3.1 is out.

And it is ... hidden behind "many smaller fixes". I've spent some time searching for possible performance problems. Some changes may be visible for you, some not. But if your personal overall feeling is "faster" = perfect.

@balloni55
"united" (reaction on the last post)

Something wrong with shadows, on v4 map. (https://uploads.tapatalk-cdn.com/20190603/ba9c7b83866fdf22948edaf747c566fe.jpg)

Inviato dal mio SM-A520F utilizzando Tapatalk

Beta 3.38.3.1: Thanks, I have the feeling, the rendering is now even faster. It was synonymous in version 3.38.3 already fast on my S8.  :)
In the beta 3.38.3.1 the automatic map change does not work anymore.

For me:
1. Rendering seems much faster
2. "Magnify all" works a treat!
3. Automatic map change works for vector maps for LoMaps/MF3/MF4. (That's testing moving from Wales to England.)

An observation, not a bug or request. For each long ride I keep a record of device power consumption. I have an exact set of apps running, mainly just Locus, firewall, no wifi, no data, track recording, no routing, display off. Until approx. 3.37.2 in April power consumption has been ~2.5 to 3% per hour. This has been consistent over 100s rides over last few years. But since 3.37.2 I have noticed power increase to 3.0 to 4.5% per hour. I only have 5 long rides of data yet so not 100% confident. And maybe this is the price to pay for improved map rendering. But I just thought I mention my experience anyway as power consumption on longer rides is quite important to me.

Hmm Andrew, there shouldn't be any map rendering while screen off.

Gesendet von meinem SM-G930F mit Tapatalk

@lor74cas
what exactly is wrong with shadows? HGT files used for rendering of shadows may not be the same as used for creating map and it's elevation lines.

@erfi
automatic map change: be more specific please. Which map, how they are stored on your SD card, what settings you use, thanks.

@Andrew Heard
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

Quote from: menion on June 04, 2019, 08:19:14

@Andrew Heard
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

Do I understand it right that the Kalman filtering of position applies only to screen rendering, while track recording uses unfiltered data ? But even if not, I guess battery impact would be minimal.



Odesláno z mého Mi A2 pomocí Tapatalk

Ah yes ... I did not touch track recording directly, but functionality before (work with received GPS location) is affected. So yes, location filter is applied directly on received location and then all functionality in the app use this modified location. Anyway, it is just a few matrix operations once per second, so it definitely cannot increase power consumption by 1%.
You may anyway give it a try Andrew by disabling location filter in settings > GPS & Sensors > Location filter.

Quote from: menion on June 04, 2019, 08:19:14
@lor74cas
what exactly is wrong with shadows? HGT files used for rendering of shadows may not be the same as used for creating map and it's elevation lines.

As you can see in the attached image in the previous post the shadow goes down in the sea this happens with v3 e v4 maps.
HGT and map files may not be the same, but when you reach the sea you are at 0 mt no more shadow needed.  ;D

@lor74cas
Please tell us 1) the coordinates of your screenshot, 2) what map are you using, 3) where did you get the .HGT files used for creating the shadow.
Then we could be able to tell the reason of the shadowing inside the sea.

New Beta 3.1:
"Magnify all maps" totally broken for raster maps: sometimes screen is just white (downloaded Google Maps), sometimes it works, sometimes no change at all (still in highest available zoom level). Magnification level still makes no difference. For vector maps, it basically works, but also with always the same magnification.
Sorry, unusable. Restarted several times, cleared cache, just to be sure, but that's not it :(

Quote from: menion on June 04, 2019, 08:19:14
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

only running is track recording (is it?) - correct. I've been very careful over the years to have reproducible results, and there has definitely been an increase in power consumption in ~last 6 weeks, but maybe the culprit lies elsewhere. Weird.

Quote from: Andrew Heard on June 04, 2019, 01:42:59
But since 3.37.2 I have noticed power increase to 3.0 to 4.5% per hour.

I noticed a similar behavior. Yesterday I mad a  7 hour tour (only track recording with display off) and battery went down to ~30%. Normally it should be at ~60%. I had this on two devices during my trip, one on LP 5.1.1 and the other Pie 9.0.

BetterBatteryStats or a similar tool should tell what is happening behind the scenes.
Comparing old and new Locus version on the same device, screen off is key, and maybe a "virgin" restarted device should make results comparable. And show a smoking gun ...

@menion: Excuse me, it was my mistake. The automatic map change (OAM v4) works in Beta 3.38.3.1.  :)

When I use 'nearest caches' in newest version of geocachin4locus the coordinates are not set to the cursor position.
In the old version I could point in the map to the location I want geocaches to download ... and coordinates where sent from Locus to geo4loc to that point.
This was an easy and quick way to fill a far map area without a pocket query.
Is this a problem of Locus or geo4loc (or maybe a user problem 😚)

Quote from: jonny.blue on June 04, 2019, 19:53:54
When I use 'nearest caches' in newest version of geocachin4locus the coordinates are not set to the cursor position.
In the old version I could point in the map to the location I want geocaches to download ... and coordinates where sent from Locus to geo4loc to that point.

switch gps off an you´ll get what you want

@lor74cas
can't say that I agree with "when you reach the sea you are at 0 mt no more shadow needed", but let's say here should not be a shadow. Anyway as sonny wrote, give us some data. Based on your scale and precision of HGT files supplied over Locus Map (around 50 m if I remember correctly), it will be most probably result of interpolation.

@slarti76
Petr was able to simulate something, thanks for pointing on this problem.

@Andrew Heard, @tramp20
oki, thanks for the info. Really hard to solve somehow, without more precise knowledge where may be a problem. Hmm will have to do some tests ...

Quote
switch gps off an you´ll get what you want

Thx, good workaround. 😉

... but in the version before there was no need to do this, ???

Hi Menion,

I played a bit with the new beta 3.1 and stumbled over an issue with the hill shading. When I zoom out (ZL < 9) and move to a region, where I don't have some HGT files yet, the whole app freezes for a long time (about 10 to 30 s). Then the small indicator for the missing HGT information appears. If I pan the map further in that state, the app freezes again. It looks like a high CPU usage, because when the frozen state comes to its end some super slow animations are visible (blending effects). Once I have confirmed the download of the missing HGT files the app becomes responsible again until I hit the next region with missing HGT files. I don't see the issue at all, if I turn off the hill shading.

I'm using V4 ML OpenAndroMaps together with an overview map on a Samsung A3 2017 with 128GB SanDisk SD card for vector maps and HGT files.

Best regards,
Thomas

Quote from: menion on June 04, 2019, 22:30:32
@lor74cas
can't say that I agree with "when you reach the sea you are at 0 mt no more shadow needed", but let's say here should not be a shadow. Anyway as sonny wrote, give us some data. Based on your scale and precision of HGT files supplied over Locus Map (around 50 m if I remember correctly), it will be most probably result of interpolation.

@slarti76
Petr was able to simulate something, thanks for pointing on this problem.

@Andrew Heard, @tramp20
oki, thanks for the info. Really hard to solve somehow, without more precise knowledge where may be a problem. Hmm will have to do some tests ...

Hgt from download proposed by locus.
Not a big issue, and more noticeable at some zoom levels and less in other so as you wrote it's probably due to interpolation.
Shadows for my case of use are a beautiful optional, what really matters are elevation lines and all the tools you implemented in this years to measure distance and positive gain

Inviato dal mio SM-A520F utilizzando Tapatalk

@lor74cas: The hgt-files provided by Locus are the 3 arcsecond which have "just" a Resolution of about 75 meters. Here http://data.opendataportal.at/dataset/dtm-italy (http://data.opendataportal.at/dataset/dtm-italy) you could download the ones of Italy and other countries with 1 arcsecond which equals about 25 m resolution. This should generate finer shadows at sealevel lines and also even more precise altitude information in rocky terrain.

But if you won't provide further information (map, coordinates) as told you twice now, nobody will be able to reproduce a possible bug or could give you further advices.

Quote from: sonny on June 05, 2019, 09:15:08
@lor74cas: The hgt-files provided by Locus are the 3 arcsecond which have "just" a Resolution of about 75 meters. Here http://data.opendataportal.at/dataset/dtm-italy (http://data.opendataportal.at/dataset/dtm-italy) you could download the ones of Italy and other countries with 1 arcsecond which equals about 25 m resolution. This should generate finer shadows at sealevel lines and also even more precise altitude information in rocky terrain.

But if you won't provide further information (map, coordinates) as told you twice now, nobody will be able to reproduce a possible bug or could give you further advices.

N 44°46.959' , E 014°47.380

I know and use 1 arc hgt for Italy, in this case for foreign map I use default hgt provided by locus, thank you.



Inviato dal mio SM-A520F utilizzando Tapatalk

@lor74cas:
this is in Croatia, where no high resolution .hgt are available yet. So those used by locus have a real resolution of just 60-90 meter and with additional interpolation it could be possible that up to 50-100m from the coast there are shadows within the sea of a map.

I suppose the underlying question is, should Locus know where there is water and not display shadows (or even contour lines and elevation detail).
I think it would be nice but maybe not possible.

Sent from my moto g(6) plus using Tapatalk

Quote from: menion on June 03, 2019, 20:03:46
Ah yes, new Beta 3.38.3.1 is out.
@balloni55
"united" (reaction on the last post)

no improvement
https://www.dropbox.com/s/kls16qltqrfmv1m/guide%20to.mp4?dl=0

Quote from: michaelbechtold on June 04, 2019, 15:52:03
BetterBatteryStats or a similar tool should tell what is happening behind the scenes.
Comparing old and new Locus version on the same device, screen off is key, and maybe a "virgin" restarted device should make results comparable. And show a smoking gun ...

@michaelbechtold - thanks. I had used gsam Battery Monitor Pro, but BetterBatteryStats looks interesting, however after using Locus for 5 hours today, I can't interpret the TXT file that BetterBatteryStats creates. Please help. Where can I find the % battery used by Locus for example?

Under Wakelocks (edited to only show lines with "locus"):

GpsConnectionBaseImpl (menion.android.locus.Locus Map): 4 h 59 m 59 s  Count:1 95.0%
LocationManagerService (menion.android.locus.Locus Map): 36 s  Count:19902 0.2%
*alarm* (menion.android.locus.Locus Map): 27 s  Count:1599 0.1%


Under Processes (edited to only show lines with "locus"):

*wakelock* (menion.android.locus.Locus Map): Uid: 10172 Sys: 5 h 34 m 29 s  Us: 7 h 20 m 54 s  Starts: 0
menion.android.locus (menion.android.locus.Locus Map): Uid: 10172 Sys: 15 m 6 s  Us: 49 m 40 s  Starts: 2
menion.android.locus.pro (menion.android.locus.pro.Locus Map): Uid: 10257 Sys:  Us:  Starts: 2

etc.

Attached UI showing Wakelocks.

Quote from: sonny on June 06, 2019, 09:36:38
@lor74cas:
this is in Croatia, where no high resolution .hgt are available yet. So those used by locus have a real resolution of just 60-90 meter and with additional interpolation it could be possible that up to 50-100m from the coast there are shadows within the sea of a map.

Understood, thank you. As I said before I do not worry too much about shadows.

New Beta 3.38.3.2 just uploaded on Google Play

@Tom
I understand your precise description, unfortunately, I wasn't able to simulate this issue. Give please a try new Beta as well, because I made some improvements that may affect this as well.

@John Campbell
new account? It should be possible to change almost everything in the old one like email address etc. Anyway coastlines are not directly available in the app.

@balloni55
ah damn, thanks. Second try ...

@Andrew Heard
wakelock is expected in case of enabled GPS. Locus Map keeps wakelock active as long as GPS is needed.
.

Today i used for the first time the maps from Andromaps, V4 ML OpenAndroMaps, normaly i use their V3 maps with no problems at all.
With the V4 maps my Android Honor 8 crashed several time. Now back to V3 maps.

Much better and runs smoother.

Problems with Openandromaps V4 maps and Locus Pro ?

Have now version 3.38.3

Quote from: Andrew Heard on June 06, 2019, 13:19:18

Hello Andrew,
the numbers I see tell that Locus is busy basically uninterrupted. I would expect that there is near to zero "deep sleep" (you can look up CPU states)
That would imply a heavy battery burn rate. On the other hand, if the tracking profile requests snapshots every second e.g., that would be the epxected result.
It would be interesting to see the DIFFERENCE of those metrics between the versions.
Good luck and kind regards
Michael

Quote from: michaelbechtold on June 04, 2019, 15:52:03
BetterBatteryStats or a similar tool should tell what is happening behind the scenes.
Comparing old and new Locus version on the same device, screen off is key, and maybe a "virgin" restarted device should make results comparable. And show a smoking gun ...

@michaelbechtold - thanks. I had used gsam Battery Monitor Pro, but BetterBatteryStats looks interesting, however after using Locus for 5 hours today, I can't interpret the TXT file that BetterBatteryStats creates. Please help. Where can I find the % battery used by Locus for example?

Under Wakelocks (edited to only show lines with "locus"):

Code Select Expand


GpsConnectionBaseImpl (menion.android.locus.Locus Map): 4 h 59 m 59 s  Count:1 95.0%
LocationManagerService (menion.android.locus.Locus Map): 36 s  Count:19902 0.2%
*alarm* (menion.android.locus.Locus Map): 27 s  Count:1599 0.1%


Under Processes (edited to only show lines with "locus"):

Code Select Expand


*wakelock* (menion.android.locus.Locus Map): Uid: 10172 Sys: 5 h 34 m 29 s  Us: 7 h 20 m 54 s  Starts: 0
menion.android.locus (menion.android.locus.Locus Map): Uid: 10172 Sys: 15 m 6 s  Us: 49 m 40 s  Starts: 2
menion.android.locus.pro (menion.android.locus.pro.Locus Map): Uid: 10257 Sys:  Us:  Starts: 2

etc.

Attached UI showing Wakelocks.

@michaelbechtold - are you saying the "Awake (Screen Off) 5h 99%" and "Locus *wakelock* 5h 19%" are a surprise to you? My track recording profile is 25m | 240s | 50m, so should not be continually recording while cycling; and display is off for 5 hours except ~2 minutes. What are the important clues I should be looking at? The descriptions are more suited to an Android programmer than an ordinary user. There is nothing that says "Locus used x% battery in y hours".

Hi Menion,

thank you for the new beta. I tested it, but unfortunately the behaviour did not change. I fear that me error description was not entirely correct, because when I repeated me tests in order to create a screen capture, I could freeze the app even without being informed about missing HGT data. IMHO it is just an overload condition, when visiting that huge amount of HGT tiles in lower zoom levels. Here is the screen capture of my last test:
https://drive.google.com/file/d/1PxPxrkMcuWe77F_SkP4kAzHyyGcvX5LQ/view?usp=sharing (https://drive.google.com/file/d/1PxPxrkMcuWe77F_SkP4kAzHyyGcvX5LQ/view?usp=sharing)
The small moving circle is the touch point.

Best regards,
Thomas

@AndrewHeard: these stats are indeed somewhat hard core and well under the hood.
I was indeed surprised, and the stats you shared would make me look at the cpu state stats.
And any stats that directly points to Locus (or any other app) does not tell the full truth anyway.
If an app prevents the phone form low cpu frequency (deep sleep would be ideal), this burns battery indirectly in addition to the direct cpu time by the app.
Most importantly I would compare an older version of Locus with the new version and look at the DIFFERENCES, which should give Menion some hints.

Beta 3.38.3.2: Tested yesterday with my SGS8 tracking recording.
Airplane mode, display off, interval 2 seconds, track time 1 h 2 minutes. Power display at start 66%, at target 63%. Only 3 % battery consumption, that's a very good value. The recording accuracy is also very good.

Quote from: menion on June 07, 2019, 14:14:40
New Beta 3.38.3.2 just uploaded on Google Play
@balloni55
ah damn, thanks. Second try ...

now it works ;) thanks

On my tablet I have tiramisu as a possible theme in 3.38.
Now I want to activate it on my mobile ... but it doesn't work.
Copied it 1to1 from tablet, downloaded it fresh ... but I can't choose it within Locus.

The only unusual I can see: on my tablet tiramisu theme is grey but I can choose it.
The check find no error.


Finaly got it working ...😚

Quote from: erfi on June 08, 2019, 11:00:50
Beta 3.38.3.2: Tested yesterday with my SGS8 tracking recording.
Airplane mode, display off, interval 2 seconds, track time 1 h 2 minutes. Power display at start 66%, at target 63%. Only 3 % battery consumption, that's a very good value. The recording accuracy is also very good.

I think battery % only has resolution to 0 decimal places, that is just integer values, so I've found measurements over short periods are not so accurate - the value could be 3% +/- 1%. So I've tried in the past to base measurements on 5 hour+ bike rides. But now I am going to experiment with a new recording profile that records every 5s and not moving, so I can just leave the device outside all day for a more objective test. Will see how it goes...

@Andrew Heard: That's right, a longer track time gives more accurate results. My bike tour today: track time 5h 29min., Track interval 5 seconds, display off, airplane mode. Battery indicator at start: 95%, at target 77%. This gives an approximate battery consumption per hour between 3.3 to 3.5%. A fine result.  :)

Quote from: erfi on June 09, 2019, 20:35:39
@Andrew Heard: That's right, a longer track time gives more accurate results. My bike tour today: track time 5h 29min., Track interval 5 seconds, display off, airplane mode. Battery indicator at start: 95%, at target 77%. This gives an approximate battery consumption per hour between 3.3 to 3.5%. A fine result.  :)

@erfi - good to see your results. 3.5% of course depends on the battery capacity too, so not directly comparable across phones. Your current usage is similar to mine though. Do you have records from a few months ago - have you noticed an increase? I used to regularly record 2.0 to 2.5%.

No, I have no further data to compare.

I'm using the last non-beta. My experience is, too often v4 vector map does not load. At all, or sometimes a bit. Sometimes load after map drag. Seen that especially in route planner. Sometimes Locus cache has to be cleared.
It is annoying if Locus insists on looking like in screenshot.
I think it loves to do this when the map is moved to more far away locations.

Edit:  now cache delete, restart whole phone, no matter if v3 or v4 map(only v4, oam Germany North vs. Germany mid), no matter which theme, mostly no map buildup, sometimes at zl 13,but not above. no more idea except using Osmand. Want to not risk uninstall Locus.

Not funny any more. Maps loading like sh***

https://youtu.be/-xBHgfzRXWk

It can be seen that map is Germany North, from OAM. But at some ZL it is not displayed north of Dortmund.

Edit: it says it loaded Germany North, but my impression is it auto loaded Germany mid where it is not needed.

Must be something with Germany north vs. Germany Mid. IDK, I changed to Nordrhein-Westfalen map  now, which works for me.

I have the same problem with the v4 cards.
Regardless of whether Germany North or regional maps. Reloading is constantly jammed.

Beta 3.2, "Magnify all maps"
The severe bugs from 3.1 are gone (no blank tiles/screen), but apart from that it's still not working as advertised. I'll summarize:

• Factor has no effect, always seems to be x2 (vector and raster maps)
• Raster maps: When in highest available zoom level at 100%, and I zoom in once, it enlarges to 200%. When I now switch on "Magnify", nothing happens. Things get even weirder when I use "Lock the zoom" - then I even get blank screens again. The current algorithm clearly doesn't work when in highest zoom. Probably also the case for vector maps, but there the highest possible zoom is so large that it probably doesn't matter that much. But with a raster map with max ZL17, it is!

To be honest, the most transparent and controllable way would be to have the former algorithm, PLUS a one time evaluation of DPI at the very start of Locus, to be used as an additional - or even optional - magification factor.
Just my 2c ...

@Tom
unfortunately together with my colleagues, we are still unable to simulate this problem. No matter what we do, it simply works. Are you using any overlay or WMS map?

@tapio
all other vector maps, except LoMaps, has defined area as big bounding rectangle. So huge maps like these you use, may have areas completely without a map, but Locus is unable to detect it because the definition in the map tell that this empty space should be covered. So I may currently highly recommend using more smaller maps then two huge.

@slarti76
I'm still quite sure it works, it only does not immediately change what you expected (visible camera scale). Try to use hardware zoom in/out after you change magnify and you will for sure see difference.
Anyway blank screen with combination with zoom lock is weird. Can't simulate, but will be watching it.

Quote from: menion on June 12, 2019, 13:43:54@slarti76
I'm still quite sure it works, it only does not immediately change what you expected (visible camera scale). Try to use hardware zoom in/out after you change magnify and you will for sure see difference.
Anyway blank screen with combination with zoom lock is weird. Can't simulate, but will be watching it.

Ok, I recorded a screen video, showing how it sometimes works, sometimes doesn't; plus an instance of blank screen when magnified. "Unfortunately", the factor worked in this case, but I did try it before with screenshots where the result was always the same no matter what factor I used. Can't figure out what was different.
Download: https://web.tresorit.com/l#CfD2qKZB6nRcAjJFGdbFCg
Corrected: https://web.tresorit.com/l#PVxxuyumpUpuQjSiiSCFmA

Quote from: menion on June 12, 2019, 13:43:54
@Tom
unfortunately together with my colleagues, we are still unable to simulate this problem. No matter what we do, it simply works. Are you using any overlay or WMS map?

No overlay or WMS at all. The problem even occurs with a blank map. But I did some more experiments and I think I found the root cause for the problem: If I clear the SRTM folder, then the problem does not occur. So, it is the number of files in my SRTM folder, which slows down the app. In my STRM folder there are about 3100 files. 500 of them are *.empty files. The rest are *.hgt files. I'm also a programmer and we had a similar problem too (on a Windows system). We solved it by creating a hierarchy of sub-folders ensuring that the maximum number of files per folder does not exceed a certain upper limit (must be determined by experiments). In your case you can easily use the coordinate parts of the tiles to create the names of the sub-folders.

Hope this observation helps to solve the issue.

Best regards,
Thomas

Quote from: Tom on June 13, 2019, 00:30:34
We solved it by creating a hierarchy of sub-folders ensuring that the maximum number of files per folder does not exceed a certain upper limit (must be determined by experiments). In your case you can easily use the coordinate parts of the tiles to create the names of the sub-folders.

Perhaps a much simpler solution would be to cache the names of the HGT files in memory instead of enumerating them from the filesystem every time.

BR Thomas

I confirm the problem with the white screen as slarti76. Vector maps OSM V3, android 8. The problem does not occur at all magnifications and does not show even on tablet with android 5. If you want to try to simulate on your device then try the same scale as on the screen (100m) and then map your fingers to scale 300 m. I attach the SCR.

New update, vector map v4, map magnification, no difference if 100,125 or 150 percent.

New version 3.38.4
- mainly fixed major problems

@tapio
correct, I still believe current behavior works correctly. As I wrote, there is a need for one tiny change that causes a little trouble for me. If you set 150% to magnify, the app just needs to do zoom by this 50 % (like by fingers) and then all will work as expected. Anyway, let it be for now, I'll invest more time to it and in next Beta ...

Problem with white areas reported by you and Josef are still not reproducible by me and colleagues, weird. Will need to play with it a little more.

@Tom
perfect you found reason. It means I should be able to simulate it. Weird is that Locus do not search in HGT files and mainly in zoom level on your video, shading should be completely disabled! (it should work till level 8+)

New version 3.38.4: This problem still exists: after the automatic map change (OAM v4), the map name in the upper panel (top panel) is not updated.

This is correct. With V4 maps, app has no idea which map is used, so always first selected (primary) map is displayed in the top bar and also in map manager.

Hi Menion,

Quote from: menion on June 13, 2019, 16:08:35
It means I should be able to simulate it.

Note, that my SRTM data is on an external SD card (SanDisk, don't know the exact spec). IMHO SD cards are much slower that the built-in flash memory.

Quote from: menion on June 13, 2019, 16:08:35
Weird is that Locus do not search in HGT files

I guess you compute the HGT file name from the coordinates of the visible location and then just try to open the file. So, I think it is the file system itself that slows down, when opening a file in an directory with a huge number of inodes.

Quote from: menion on June 13, 2019, 16:08:35
mainly in zoom level on your video, shading should be completely disabled! (it should work till level 8+)

Totally agree with that proposal.

Best regards,
Thomas

Quote from: menion on June 13, 2019, 16:08:35
@tapio
correct, I still believe current behavior works correctly. As I wrote, there is a need for one tiny change that causes a little trouble for me. If you set 150% to magnify, the app just needs to do zoom by this 50 % (like by fingers) and then all will work as expected. Anyway, let it be for now, I'll invest more time to it and in next Beta ...

It's slarti76 ;) Nevermind...
Tried out 3.38.4. First tried with 200% and 300%: Absolutely identical maps displayed. Then tried out 150%: No change between 100% and 150%. Then, as you hinted at, zoomed out and in again: Now it looks like it may be 150%. Tried out 200 and 300 again: Now there was a difference.
At last, tried 400%: Different to 300%, but muuuuch bigger.
Now I noticed the percentages shown in the top bar. At base resolution (no magnify), it showed "200%". Ok, probably a result of the DPI calculation, whatever. With magnify to 300%, it showed "500%" (which is 2.5x=250% magnification). At 400%, it showed "1000%" (which is 5x=500%).
No it struck me: The problem here is, I think, that my map doesn't have linear zoom levels, the highest levels are "1:50000", "1:25000", and "1:10000". I assume that when I'm in the "1:10000" level, that messes with your calculation, as you expect the lower level to have half the resolution (1:20000) and calculate the level to be used for magnification and the enlargement of tiles based on that - which has to fail.
With a Google map download done by Locus, I don't have those severe discrepancies, but there's also no difference between 250% and 300%, for example.
Also, when I zoom in more than the highest zoom level (one or two additional taps on "(+)"), I'll still get to a point where Magnify has no effect.

So in summary:

• The algorithm seems to break down when the map's zoom levels are not 1:2
• Magnifications between full 100% steps are sometimes a problem*
• Magnifying when already magnified in highest zoom level doesn't work
• Sometimes magnification is not applied directly, only after another zoom in/out

* I think it would be no loss to get rid of the 25% steps, and also all 50% steps after 200%, but at least 150% should work.

Hope this helps.

PS: Good news: Didn't have any blank screens anymore

Hello Menion,

Locus Pro 3.38.4: https://drive.google.com/file/d/1RJWHloh9xr4udLfdUrPFxeo0tNw5B49H/view?usp=sharing (https://drive.google.com/file/d/1RJWHloh9xr4udLfdUrPFxeo0tNw5B49H/view?usp=sharing)  (~54MB, 2:03min)

1st: raster map, my special one with Z13 + Z16 only  ;) 8)
2nd: vector OAM V4, Germany South ML + Elevate theme

let's concentrate on the raster map

• I guess you manage it the way that the DPI-awareness  (optimise map resolution) defines a certain %-zoom-view, here my minimum-%zoom is always 150% (if I use magnify (not shown in the video) this value changes to 150%*magnification). I don't understand this hard-limit if I am at lowest Z-level (13) and want to change %-zoom to a lower %-value than 150%, not possible currently?! Scaling the last-available-Z-level should always be without any limitations in my opionon - Z13 should be zoomable down to some-% and Z16 should be zoomable up to infinty (1px/Screen) ;D I guess this is more a mistake than intended..
• maybe this explains the white no-view-available zoom-transitions from Z16-150% in direction to Z13. Values lower than 150% seem not to be possible, available..
• changing the std-values-%-zoom is in my opinion a bit irritating as I often orientate to Z-levels and 100%/ 50%/150%/200%..often used zoom-values of mankind, not sort-of-strange values. Maybe it's better to stick to those values and leave some zooming-calculation under the hood, like this is already the case I guess.

Fresh installation on new phone, UK locale, TTS language is set as Czech. Can you not use system settings?

Sent from my moto g(6) plus using Tapatalk

Same here after update. Quite funny.

if the distance between map cursor and target becomes too small depending on the zoom level, the values are no longer displayed.
If I remember correctly, in the past the values were displayed on the other side  of the map cursor in this case.

Sorry for a delay in my responses. We never had so much support to do and with Michal, we do it almost non-stop :/.

@slarti76
I reacted mainly on the previous post from @tapio: https://forum.locusmap.eu/index.php?topic=6579.msg55898#msg55898 ;)

Anyway thanks for your long post (https://forum.locusmap.eu/index.php?topic=6579.msg55905#msg55905). Seems I'll really have to write some blog post on this topic and explain it a little bit. What happens to you is perfectly correct and expected behavior. At least I wrote it like this. I'm aware it needs a minor tweak to make it work as you expect so I'll try to improve it till next version and you will see.

@Tom
so I've downloaded more than 3.000 HGT files and ... issue simulated

@T-mo
scaling of the lowest level will be improved in next version, I already noticed this as well and agree. Anyway optimal way of displaying zoom level is not yet done. I'll have to think about it little more, but old zoom value are from my point of view useful for "geeks", but average user lives in the world of directly visible scale (like "this line" is 300 metres) or in older system of paper maps (1:25k, 1:50k etc.).

@john_percy, @Henk van der Spek
the interesting problem mainly because the Czech language has no priority in the app, all is made in English only. Was then possible for you to change it and use the correct language?

@balloni55
hmm, it is possible. I made some improvements because very often, the text was shrunk or weirdly modified. Now app check available space more precisely and if there is not enough space, the text is not drawn. In this case, you still see distance at the top ;)

@menion: I changed the TTS language to English in Locus which then gave me a weird US computer voice, and I then had to change it to UK English in Android settings. I didn't investigate further but I wouldn't have been satisfied with the weird US voice even if I was American.

Sent from my moto g(6) plus using Tapatalk

And you previously had US English in your device?

There were no changes regards languages in Locus Map except one serious change in app distribution: Locus Map now uses so-called "app bundle". The result is that when you install the app from Google Play, Google Play prepare specially for you smallest possible APK file optimized to your device with only single language bundled in the app: the language of your device. Maybe it has some side-effects here ...

QuoteIn this case, you still see distance at the top

i know, but my values are twice as big and that's important to see it clearly in sunlight.
On the opposite side of the map curser there is enough space to display the values.

I was worried you will write it :)

Quote from: menion on June 17, 2019, 20:06:20

@john_percy, @Henk van der Spek
the interesting problem mainly because the Czech language has no priority in the app, all is made in English only. Was then possible for you to change it and use the correct language?

After  the update to 3.38.4 and following first start, Locus spoke Czech (in navigation). My device is standard on Dutch.
I then switched the language setting in Locus to Dutch and then the voice sounded like American with a heavy Dutch accent or vice-versa.
I think I then restarted Locus (but maybe even my phone) and everything was normal then.

Quote from: menion on June 17, 2019, 20:06:20I'll have to think about it little more, but old zoom value are from my point of view useful for "geeks", but average user lives in the world of directly visible scale (like "this line" is 300 metres) or in older system of paper maps (1:25k, 1:50k etc.).

Sure, I understand that with raster-maps this is a bit more challenging.
The problem with extraordinary discrete %-values might also be that features like auto-zoom might be different from map to map..
At this point it might make sense to think about preserving some extra space in internally build/used map-arrays, keeping map-dependent-parameters, and integrate an additional internally used map-scale-factor, starting with 100% as same-value-on-each-map, but might come in handy if time tells some tricks needs to be done and different values might be the better way..you never know ;D staying flexibile while changing the structure. Sure, not a new idea and royal thoughts already used by devs 8)

Something happens and makes Locus go crazy for me.
I have a route with starting point near by my position and end point 10km away.
When starting Navigation it starts recalculation and recalculates to my end point. It doesn't matter which way of Navigation start I use and it happens even with other new planned route.
WTF....
Looks Locus is more or less unusable for me.

I restored 3.37.2. Looks much better.
Something is wrong in new route recalculation in 3.38 I guess.

*** Beta 3.38.5.1 with a bunch of updates & fixes *** (not just problematic navigation).

Quick test who is interested. If no serious problem, the release will be tomorrow, so on weekend riding, app, mainly it's navigation, is usable again.

Quote from: menion on June 20, 2019, 14:01:20
*** Beta 3.38.5.1 with a bunch of updates & fixes *** (not just problematic navigation).

Magnify now works flawlessly and as expected, didn't have any hiccups in (admittedly short) test. Thanx, great!

But I have one complaint:
Hiding the "world maps" from the Quick Map Switch is a NO-GO like this: I have a downloaded Google map with a wide zoom level range (7-21 or something) that is now hidden. It's my main offline map! Please don't hide maps that also contain high zoom levels.
Good opportunity to point to this again: https://help.locusmap.eu/topic/flag-to-hide-maps-from-quick-map-switch - definitely the more flexible solution... ;)

In MF4 maps, texts such as town names are frequently truncated at tile boundaries on first display (moving the map to the location, changing map) but display correctly on zooming out and then in, or vice versa.


Sent from my moto g(6) plus using Tapatalk

Beta 3.38.5.1
A first test on the couch: The issue of navigation with multiple via points and endpoint priority persists. With automatic recalculation via points are ignored. Often, after an automatic recalculation, you are taken directly to the end point of the route. However, I only tested with GPS off (simulation). With old version 3.37.2 it works fine.

@slarti76
oki, I'm really glad to read this about "magnify" system.
About world map : good point, I'll fix it.

@john_percy
I'm not sure how to quickly fix it, but I add it to my list of smaller tasks related to improving of MF4 maps, thanks

@erfi
I was quite sure that it is fixed, but not on 100%, that's why I published Beta first. Thanks, I'll do more precise tests tomorrow.

Mmm, what to say about guiding and navigation. It is still far from the quality of 3.27.1. and even 3.37.2 was better for me.

For the round-trips I tested from the couch both seam to go to the first point after the start of the loop. I do not remember that behaviour. After tapping nearest point this is corrected sometimes but most of the times NOT to more or less "nearest point".

Recalculate with "strict navigation" on, adds a route to the start point of the loop. GOOD. But I have to leave "auto-recalculate" off and that is a disadvantage when straying from the route.

Navigation in reverse on a round-trip goes actually to the nearest point in the loop and navigates me in reverse direction and leaves out the last part of the loop (since I cut in halfway, understandable but why not completing the available loop?).  Recalculating ignores completely the "reverse" setting. NOT GOOD.

Navigation and Guiding in reverse on a one-way trip so far always guides me to the end point. Tapping nearest point has no effect. NOT GOOD.

All navigation still, as before, makes my track invisible. It should stay visible under the navi track especially handy when I cut in halfway or pieces are left out of the navigation after the end point of a loop.

One of my tracks goes banana. See attachement. Upon checking it also does this in 3.38.4. This track is about 19 kms long but upon navigation (and or guiding) it is done 30 times and Locus totally freezes. Not important, so far only one, i did not test all of mine of course.

SO far my quick impression. I am outdoors next week but I will try to keep an eye open.

And the other two attachments

Hi Menion,

thank you for the new beta. The hill shading works perfectly now - even with more than 3000 HGT files.

Best regards,
Thomas

A minor point, but somewhere along the line "Overlays" has lost its icon. That's in the select online map menu. Even if an overlays.png file is present in mapsOnline/custom it doesn't display it.

LoMap world has changed (black/blue VEC) icon
my settings
- maps adv./Preload global map > LoMap World
- offlinemaps > autoload maps of identical type only

- if i display any german LoMap e.g. Germany South and zoom out world map isn´t loaded autamaticly
- next i select LoMap world manually, this map is displayed
- zooming in now there is no map displayed, no autoloaded map ?!
- now i select manually the german map (title is visible in topbar) furthermore no map is displayed :o
only restart of LM help to display this map again

Menion, 2 questions

• I played around with 'optimise map resolution' on and off+magnify. For my needs I guess magnify might not be the real solution as it also affects vector-maps and the %-value-thing. My Andoid has 401ppi. Is 'optimise map resolution' technically about using different dpi-float-scalings or about discrete factors like integers 1, 2, 3, maybe 4, to only have pixels multilpied by this? Couldn't really pick the situation in the last discussions
• folder mapsvector>_themes: some themes like Elevate and VoluntaryUK only work if they are extracted directly in this folder, but not if in a dedicated directory. Other themes like outdoorV4 and TOTMV4 work if in didicated directories. 2nd are using symbols+patterns, 1st not, if this is of meaning. 1st lead to cluttered folders. Do you see a simple solution to being able to use each theme in its own folder, locus-side or theme-creator-side?

I guess that you know that we know that you know that we know that this is what we all feel, this is an awesome piece of app and worth to talk about with passion 8)

Friday afternoon, definitelly worst time to publish a new version. But navigation problem see to be critical issue.

So new version 3.38.6, just generates. Thanks for the quick test. Wish me luck ...

Next week, I'll try to focus mainly on bug-fixing so I'll for sure give some feedback on the more or less minor issues you reported here. And also on remaining navigation issue, thanks @0709.

@Henk van der Spek
at least weird issue with navigation on your track should be fixed. Other issues with navigation itself ... next week. Sounds complicated :).

@john_percy
"overlay icon" fixed thanks

@balloni55
nice steps for a weird issue with the world map, thanks!
- the issue with autoloading happens to me once and then never more again
- the issue with selecting world map and then selecting any other LoMaps happens always. Help here is to select a map theme. But why this happens even after an hour is not clear to me, crazy. I'll look at it more precisely next week.

@T-mo
1. why "Optimize raster map resolution" settings do not fit your needs? Raster maps are then rescaled too much? Rescale by DPI use floating point values, but in most cases, it will end on integer value for raster maps. For vector maps, the situation is different and there it is always floating point value that more precisely match device DPI.
2. hmm, I'm checking code and app should list all directories in mentioned mapsVector/_themes directory and in every directory search for *.xml files. XML files in the root of the _themes directory should be ignored. Maybe you may zip me _themes directory that does not work as you expect and share it with me? Thanks.

@Henk van der Spek
at least weird issue with navigation on your track should be fixed. Other issues with navigation itself ... next week. Sounds complicated :).

Weird issue is GONE in 3.38.6 pro  :)
This version is definitely faster on my device. Start-up and scrolling and zooming.
Auto map loading V4 maps is working. Top bar name tag does not change accordingly.

Have a nice weekend.

New version 3.38.6, again a first test on the couch: The navigation with multiple via points and endpoint priority works now. :D Thanks menion!

So good news, nice.

I see in crashlytics (system for automatic collecting crashes) few crashes when using vector maps as overlays right after the start of the app. Hope it's just a few rare users ... otherwise, app looks pretty stable.

I also did last days few performance optimizations so hope, it will be fluent and usable like at early days :). Enjoy weekend!

Zooming in and out is extremely slow when map rotation is turned on.

Since some weeks geocaching live doesn't work in route planer.  :(

So I have no chance to see all the possible caches while planning a route.

Quote from: menion on June 21, 2019, 13:25:46
1. why "Optimize raster map resolution" settings do not fit your needs? Raster maps are then rescaled too much? Rescale by DPI use floating point values, but in most cases, it will end on integer value for raster maps. For vector maps, the situation is different and there it is always floating point value that more precisely match device DPI.

I just realise that magnify might not be the thing to use, %-values etc. And I use some raster maps. So I have on and off and both are not suberb to me, as often in life it could be something between, more personal taste or preference. So I still ask myself why I have on and off instead of values or possibilites, quantised steps between maybe.

btw. I often asked myself why 'settings>controlling>map screen>tap and hold to display adress' is not 'tap and hold x secs to display adress', I tap way to often and then tap stuff away... I train myself to make it getting less

Quote from: menion on June 21, 2019, 13:25:46
2. hmm, I'm checking code and app should list all directories in mentioned mapsVector/_themes directory and in every directory search for *.xml files. XML files in the root of the _themes directory should be ignored. Maybe you may zip me _themes directory that does not work as you expect and share it with me? Thanks.

see pics attached. If I put Elevate and VoluntaryUK in separate directories - which is not intended by Tobias or John I guess but by me ;D - both are not usable. The current way is working perfectly and - honestly - still ok, as working, but maybe this can be optimised, each theme-package would have a dedicated directory. Seems like I missed Elevate4.3.1 since 1 week btw :P

@locus.sv@heime.org
then there have to be something, that slow it down. A huge number of points, tracks visible at once?

@jonny.blue
I'm aware of this issue, sorry for this. Needs more work and testing, so till next 3.39, I'll for sure look at it.

@T-mo
current values are chosen to have as close as possible style of raster and vector maps. So in most cases, texts should be the same size for same zoom levels etc. Of course, it highly depends on the map (mainly raster) theme. So I would like to keep it simple.

Map themes ... as I wrote, Locus Map checks for xml files in one subdirectory level. You placed xml files into second subdirectory level (relative to "_themes" directory), so Locus Map is unable to find it.

Quick check of the map magnification of vector maps. Looks lime it works again as I expect it. As in older versions.
I am not having a degree in Locus so I must admit I did not understand our honorable padavan Menion, who taught us it was already good in the last version 😁 Well, books have been written about map magnification.

 ... really funny is that: how it works in recent version is exactly the same as it worked in previous (at least from the developer point of view) except one tiny detail ... the map immediately displays (zoom in/out) result of "magnify" change.
Well ... fine, one part of bigger problems solved, uff :)

I did a lot of v4 map switching and they all load quickly. No white boxes etc. I am happy about the vector map system again. There's just that text bug (cut text) on first load of area, as John already mentioned. Thx for your hard work!

I wonder for some time already, when I use the magnifying glass button, why it keeps the original zoom scale ?

Would not be better to display the scale the map has after zooming ?

Or, not to display it at all, instead of being wrong ?

Odesláno z mého Mi A2 pomocí Tapatalk

Menion, if Smooth Interface is off, "Fill map gaps" has no effect, is that intended? I think it worked once, so we had map gaps filled, minus the smooth transition effects. I'd prefer it this way.

@menion
Is resolving the double contour line bug in your to do list? I find it a real pain.
(Last mentioned in https://forum.locusmap.eu/index.php?topic=6502.msg55328#msg55328 .)


Sent from my moto g(6) plus using Tapatalk

A minor one:
In the data manager, tracks oberview, long tap to the left, on a preview picture, does not create a preview. If one is there, it deletes it. v4 map + totm theme.

@poutnikl
isn't it same like when you pick real magnifier? It also displays the same object but enlarged. And not some modified scaled clone. Are we talking about magnifying glass on the screenshot below? If so, which scale is incorrect?

@tapio
hmm I'm checking it and "Fill map gaps" should not be affect by any feature. There is need to see difference between effect of "smooth interface" and "fill map gaps".
"Smoot interface" is able to reuse map tiles from current visible zoom level during zoom to other zoom level. Nothing more. When you then scroll by map to are without a map in current zoom level, it has no effect.
On other side, "fill map gaps" should be able to search in available zoom levels of the current map and fill empty spaces on the screen by map tiles from different zoom levels.

Map overview for the track: complicated unsolvable problem. With LoMaps, this most probably does not happen because they have exactly defined coverage area. So question here is how to get more precise coverage for other vector maps as well ... hmm.

@john_percy
I still did not noticed this issue, never. I'll add it to my todo list, but to be true, I currently have absolutely no idea how to solve it ...

Quote from: menion on June 22, 2019, 11:24:35
@poutnikl
isn't it same like when you pick real magnifier? It also displays the same object but enlarged. And not some modified scaled clone. Are we talking about magnifying glass on the screenshot below? If so, which scale is incorrect?

I am sorry, I have used wrong terminology. :-)

I mean the zoom lock feature. It magnifies the the whole map area just by pixel upsampling, compared to the nominal state.

As it applies to the whole map area, it should be IMHO reflected by the map scale as well, or the scale should be suppressed, as no scale is better than wrong scale.

Odesláno z mého Mi A2 pomocí Tapatalk

Quote from: tapio on June 22, 2019, 10:29:10
A minor one:
In the data manager, tracks oberview, long tap to the left, on a preview picture, does not create a preview. If one is there, it deletes it. v4 map + totm theme.

No problem here with any Theme or V4 or V3 map.
Auto loading from V4 to V3 or vice versa still does not work.

@menion
It's totally reproduceable. Depends on having
- overlapping MF4 vector maps with different contour spacing, eg OAM UK Scotland ML and Great Britain ML
- automatic map loading on for vector maps
- zooming in and out between specific zoom levels.
It is always resolved by reselecting the theme or the map.
So, on changing between certain zoom levels it seems that tiles from both maps are overlaid, but not on a fresh screen draw.



Sent from my moto g(6) plus using Tapatalk

@poutnikl
oki, so zoom lock :). ... ah, I see ... bottom "map scale" bar isn't refreshed now, thanks! After zoom in/out it refreshes correctly. Consider as fixed.

@Henk van der Spek
automatic loading between various map types is no possible and planned.

@john_percy
thanks for the steps, I'll look at it.

@poutnikl
I confirm that the scale bar on the map is wrong if
- zoom lock is used and magnification increased to say 400% by zooming (scale bar changes correctly)
- zoom lock is then turned off (map reverts, scale bar does not)

Edit: Seems like Menion has picked it up while I was posting.

Menion I can confirm the preview image loading in data manager works with v3 lomaps.

BTW. Lomaps download can be a disaster when maps reside on external sd. Because you let it download the zipfile there. And extraction from ext sd to ext sd is often too much for Android. Resulting in a totally bricked device, you even have problems to reboot. After minutes of problems, it will not work and I manually do the job: copy zip file to internal sd. Extract to internal sd. Copy to external sd.
IDK, I bought a quick SD but Android seems to have limitations here. Some other dev. (Moon+ reader) told me that once.
Maybe consider offering to define a different temp file location.

@poutnikl , @john_percy
I've found that "zoom lock" seems to be completely broken now, not just the scale bar. Fixed ...

@tapio
is there any information about why it should be so big problem? I use this system for many years and I believe many users as well and I'm not aware of any problem. Or this is only about "moon reader dev told me"?

Read it a few times but cannot prove yet.I keep my eyes open. Maybe it is device dependent.

https://forum.locusmap.eu/index.php?topic=6579.msg56024#msg56024

Quote from: menion on June 22, 2019, 08:31:35
@locus.sv@heime.org
then there have to be something, that slow it down. A huge number of points, tracks visible at once?

Did some testing and it happens when I use a WMS raster map, a V4 overlay map and turn on map rotation.

Hello Menion
In the following the translation of my contributions in the German forum area to topic "Plötzlich falsches Routing" (Suddenly wrong routing).

Post 1
Today I used, besides cycling, to test the navigation with V3.38.6.
My conclusion:
As long as you stay on the route, in my case a circuit, everything works.
But...!
If you deviate from the route, the recalculation takes place according to the display, but from now on nothing happens anymore.
[Calculate...] then stands forever, without coming to any result. Sometimes an orange banner appears whose content I can't read with my bike glasses, but it doesn't change the unsuccessful recalculation.
I created the route on the tablet and imported it as GPX 1.1. How it works with the original route, if there is a difference at all, I will possibly test it again with fake GPS.

Post 2
A short test this morning showed the following.
Even the point-to-point navigation does not work.
The route is calculated correctly at the beginning, but after a deviation it is over.
Sometimes I get the orange error messages mentioned above, e.g.
"Unknown problem", "Route too long" (at 10km) or something related to BRouter , which I can't read because the message [Calculate...] is overlaid.
After some time the message "Timeout connect to service" appears.
For me this looks like an interface problem in connection with the automatic recalculation.

Greeting
Mips

Translated with www.DeepL.com/Translator

Hello menion
behavior reported with #59 (https://forum.locusmap.eu/index.php?topic=6579.msg55574#msg55574) was solved with V 3.38.3.2 > #162
Today i noticed problem is back again with V3.38.6 ::)

@locus.sv@heime.org
I do not know the device you have, but three map layers at once together with map rotation ... well, I do not expect an amazing performance here.

@Mips
so should I understand that once app start recalculates, it displays only some errors and no result is computed? What router are you using and what is your Android version? Also are you able to create a bug-report log by this method (https://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log) right after these issues happens?
Ah in the second post you mentioned BRouter. Did you tried the same route with GraphHopper routing?
S5 Neo is not the best device, on the second side, shorter routes should not be a serious problem.

@balloni55
long click on the map, click on the popup to display point detail, click on bottom navigation > Guide on and result? App returns to map with enabled guidance to point and popup is hidden. Since we talked about it, I definitelly did not touch this part of code. And in your case, popup is still visible, right?

@menion
Yes exactly, the recalculation is displayed, different error messages appear but no result. GraphHopper is not so interesting for me because I have "specialized" on BRouter since a long time. So far there were no problems with my S5 Neo (Android 5.1.1) in combination with Locus Pro / BRouter.
Is there a shorter version of a bug report for a rooted phone?

Greeting
Mips

@john_percy
may you please give me coordinates where is the problem with the double-elevation lines most significant? Because I downloaded two mentioned maps from OpenAndroMaps and I'm unable to see this problem. Thanks

@Mips
hmm there should be no problem with BRouter on Android 5.x, weird.
Shorted log: best what you may do is to create basic log by the known method, remember a time when the problem happens and from generated TXT file just extract part around this time. Thanks.

Quote from: menion on June 24, 2019, 20:50:14
I do not know the device you have, but three map layers at once together with map rotation ... well, I do not expect an amazing performance here.

Two, not three layers.....

I don't expect amazing performance, either. But I expect the response pressing a button being faster than 2 seconds on a samsung S8. Even not map related operations like opening the menu is considerable slower when map rotation is turned on (with a raster map and a vector overlay map)

You wrote " it happens when I use a WMS raster map, a V4 overlay map and turn on map rotation".
This I understand as base map layer + map overlay (V4) +  WMS map = 3 maps.

S8 is more powerful than my device (Pixel 2) and I see no serious problem with rotation of these three layers so there have to be something different.

Do you have enabled "Hardware acceleration" in Expert settings? (maybe you do not know Expert settings, then it's OK, this option is enabled by default). Otherwise map is empty, no huge number of points and tracks somewhere on the map?

Hardware acc. is on, map is empty.

Happens on the Samsung S8 and also on a Ulefone Power 3s which becomes almost unusable. Can make a video of it later today.....

Smooth interface makes a big difference (on my Samsung S8)

QuoteApp returns to map with enabled guidance to point and popup is hidden

no popup remain visible

QuoteAnd in your case, popup is still visible, right?

yes, watch screencast #152

@menion
I've just had to change my phone and reload everything, which shows me that the contour problem is a bit more complex.
Looking at N 56.69945° , W 006.05642° (in Scotland).
Firstly, I found that if I choose my (old) LoMap of England it won't autoload OAM MF3 maps of Scotland or Great Britain but it will autoload LoMap Scotland once if downloaded it. So a base LoMap won't autoload a OAM map of out of range, or so it appears.
Secondly, I found that the double contour line bug occurs if I have both OAM Great Britain and OAM UK Scotland available. (UK Scotland has extra contour lines and better resolution on the contour lines.) I just have to force map autoload by choosing UK Lakeland as the base map for example and contour lines appear from both OAM GB and OAM UK Scotland.
This happens with both MF3 and MF4 maps.
I've forced a map magnification of 200% to make it easier to see the effect.
I can't at present reproduce the bug if I choose a Scotland map as the base map - it may depend on exactly what other maps I have available. Maybe something else has changed.
I admit the example I have come up with is a bit obscure but it may serve to track down what is happening.


Sent from my moto g(6) plus using Tapatalk

I tried OAM v4 for Germany South
-> no autoloading aswell
-> no autoload of neighbour maps (e.g. Switzerland, France South)
-> no intern themes possible! (see screenshot)

(http://s12.imageupper.com/1_t/6/B15614585241018337_1.jpg) (http://imageupper.com/g/?S120001006B15614585241018337)

with OAM v3 intern themes are possible, see screenshot:

(http://s11.imageupper.com/1_t/7/P15614586021013240_1.jpg) (http://imageupper.com/g/?S110001007P15614586021013240)
(no autoloading either...)

@john_percy

Autoloading for vector maps works for maps that match the following conditions:
  - same map version (so V3 + V4 do not work at once)
  - same tilesize (LoMaps compare to other maps usually have 512x512px per tile)

Anyway thanks for additional information. It really has to be highly dependent on maps we have in Locus Map available, because no matter what I do, I see only single valid coordinates from the current base map. John, even if I'll be able to simulate it, I really have absolutely no idea how to fix it ...

@bezel:
Some answers are above in answer to John, rest then:
- internal themes works only for V3 maps.
- auto-loading maps may be a big problem for huge maps that cover a big area. Maps are defined only by its bounding rectangle and Locus Map is unable to correctly detect missing area and coverage of other maps. Sorry, I do no have improvements in the head here.

The app crashes when I try to load trackables in log manager.

Thanks, I noticed this issue today as well. Groundspeak seems to make some changes in API that break Locus Map implementation of this geocaching feature. I've already fixed it. The new version will be published most probably on Thursday.

About map slowdown ... it is complicated to solve it with current Locus Map version. I'll need a small help from you, but little later when I'll publish the new Beta version. I'll then write (Beta? during next week for sure) more if you will be interested to invest little time into test.

Hello menion
#allow define zoom level since geocaching waypoints will not be drawn. (default: 12)
#  - disable simplification at all: 0
#  - till zoom value (1 - 12 'include'): X
geocaching_map_waypoints_hide_till_zoom=0
set value of  ZL has no influence.

waypoints are grouped always at ZL value set in config "# allows to define zoom level for points simplification"

Hello Menion

Here is a video about the navigation problem (https://forum.locusmap.eu/index.php?topic=6579.msg56068#msg56068 (https://forum.locusmap.eu/index.php?topic=6579.msg56068#msg56068)).
I have been using all settings and profiles for a long time without any problems. Only since V3.38.x it doesn't work anymore.

https://drive.google.com/file/d/1xXxqNa_9dtcXQNvsITYW6Jt3UdW8xwXu/view (https://drive.google.com/file/d/1xXxqNa_9dtcXQNvsITYW6Jt3UdW8xwXu/view)

Regards
Mips

Addendum:
The same route results in the expected and correct navigation with V3.37.2.

Hi Menion, Problem with SD1 was my own problem with a "Sandisk Ultra 128 GB XC I" - it performed like crap. I bought a "SanDisk Extreme 256GB microSDXC" now, which performs in an awesome way, Lomaps download/extraction with a 1.5 Gb map was no problem. Best invest in my old Sony Z1 smartphone. Was a pleasant surprise that it works fine with this 256 GByte card.

Quote from: menion on June 22, 2019, 17:37:09@tapio
is there any information about why it should be so big problem? I use this system for many years and I believe many users as well and I'm not aware of any problem.

@balloni55
testing and seems to work.
With defined value 14, waypoints are visible since zoom level 15+
With defined value 0, waypoints seem to be visible always.
You wrote, "grouped"? This parameter does not define if waypoints are grouped or not. It just defines level since waypoints will be visible on the map (useful because of low map performance when too many waypoints are visible at once).

@Mips
I spend on testing maybe two hours now and no matter what I do, I'm unable to simulate event a single issue. During last days I ride few times on the bike and did some unexpected turns to test this and also no issue.

Hmm for my information: BRouter? Which profile, any internal from Locus Map or any custom, or internal of BRouter itself? Seems your video was made as simulation right? Are you able to try it with exactly same settings but a) with different routing profile (best with some internal) and b) with online GraphHopper? To verify that it is a problem directly of BRouter routing and not generally routing system in the app. Thank you!

@tapio
perfect :). 256 GB? Eh, crazy values ...

Quote
The app crashes when I try to load trackables in log manager.

It's not only within logmanager but also in normal log dialog when loading trackables ....

It will be fixed in next version (most probably tomorrow). Locus Map "incorrectly" implemented Groundspeak API. They made some changes in API a few days ago and Locus Map was not able to withstand these changes correctly. Sorry for this.

@menion
The problem occurs to me with different profiles. First I noticed it with "car", but also "fastbike" and "trekking" produced the same results.
I have been using the used profiles for years without any problems.
After the change back to V3.37.2, the backup was restored, the same simulation was run with the same settings and the result was immediately correct.
(I can create the video and upload it if you are interested.)
I can't tell at which V3.38.x the error occurred for the first time, but I think it was V3.38.4 or higher.

Regards
Mips
Translated with www.DeepL.com/Translator

Hmm, this is really weird ...

New version 3.38.7 on Google Play (just uploading). I believe I've found a reason why this happens but needs verification from anyone, who has this problem of course. Thanks

@menion

The first short test already looks very good.
The recalculation worked and the [Calculation...] banner disappears after a short time.
Very good!
If the long test also runs like this... 8).

Supplement:
The first longer test was also successful.  8) 8)

Thank you
Mips

I can confirm Mips' statement so far. The mentioned errors are no longer present.

Today during an outdoor test I noticed that the automatic recalculation under BRouter does not work reliably during navigation. Most of the time it is simply not recalculated when you leave the track. I tried it with GraphHopper and it works fine. So it seems to be a BRouter problem.

Anyway, many thanks to Menion for the tireless work.

Translated with DeepL

Hello guys,
thanks for confirmation of this fix. The weird problem really.

I do not know if you tested it with exactly same situations, but just keep in mind that in the app is hardcoded limit for automatical recalculation: max. once per 30 seconds.

@menion

Quote...limit for automatical recalculation: max. once per 30 seconds

Thanks for that info. I didn't know that yet but that explains some unexpected behaviour. So the setting "Deviation from which the recalculation starts" is only valid if the last recalculation took place at least 30 seconds ago. This information is especially important for narrow inner city courses.

Regards
Mips

Auto recalc every 30 seconds is an important information. I was also wondering if there is some delay. Please at least add the info close to the recalc settings... Or maybe you can even make it configurable... via config file at least?

Do not understand it incorrectly.

This value says, how much often (maximum frequency) recalculation may happen. If you start navigation and you get out of the track, recalculation happens immediately. But, if you will still ride out of this track, next recalculation won't happen sooner then after this 30 seconds.

The parameter was more dynamic in previous versions and this was a problem that happens. So in last public version is again hardcoded to 30 seconds .. for now.

From my experience during years of riding, this value is good compromise between too frequent and too late recalculations I believe.

Yes, but the information should be in the UI. Keep in mind eg people are testing/simulating routing a lot with turned off GPS. 30 seconds delay until next recalc is a necessary info in this scenario.

30 seconds is a good value.
When simulating at home with the GPS switched off, BRouter also works the way it should. The first recalculation in case of deviation takes place immediately, the next one after 30 seconds at the earliest.

Only outside with GPS switched on no recalculation took place with me mostly, neither immediately nor later after deviation.
With GraphHopper it worked as intended.

I will try BRouter again this weekend.

Translated with DeepL

@tapio

Quote...people are testing/simulating routing a lot with turned off GPS

That's exactly why I haven't just switched off GPS for ages and then moved the cursor, but always use Fake-GPS for my simulations.

@menion
Maybe you can provide a variable on the config.cfg as suggested by @tapio in  for experimental users who also know what they are doing.

Regards
Mips

Menion, currently your POI databases are only shown, if there is a v3 map file with the same name. Now we are in the transition to v4 maps and as you know, many of us use OAM maps. I buy your lomaps only for the poi db.
In order to display those poi dbs, I have to store v3 maps additionally. Which is unintuitive for people who do not kniw, but furthermore, creates a messy map overview. Pls at least accept same name v4 maps!

@menion

How is the estimated travel time calculated during route planning?
I noticed that the same route with the same settings and the same profiles on two different devices produces completely different results.
Is there an explanation?

Regards
Mips

@tapio
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.

@Mips
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.

OK. As for poi, I have:
Netherlands_ML.map (from oam)
Netherlands_ML.db (from lomaps)

Netherlands are not shown in country picker in poi screen.

Naming convention is: <country>.osm.map and ...osm.db

Quote from: menion on July 01, 2019, 14:40:22
@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.

That's actually a possibility. I've noticed a few times when I take the phone out of my pocket and look at it to see that a recalculation suddenly happens shortly afterwards. That's why I suspected the deactivated display, but it didn't seem logical to me. I will observe and test it.

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.

Quote from: michaelbechtold on July 01, 2019, 22:55:11
Naming convention is: <country>.osm.map and ...osm.db

Thx, semi related: Often after map renaming or map moving actions and start of Locus after such actions:
a) Locus shows nullpointer exception at start and
b) I see white maps - I think the last used one does not display - needs delete cache and works after restart. Cache delete is not fun because the restart takes long (the big overview map takes a long time).

As user service, when Austria.osm.map is currently loaded and I open the POI tool, it could already choose the Austria.osm.db POI.
Maybe same goes for offline geonames (but I can see it is more difficult there).

One thing that has been bothering me for a while:
In the "Points of Interest (BETA)", why do I still have to select the region myself? You can determine which maps are fitting for the currently dsplayed area, but not which set of points?
I do get that putting all points together inone big database (internally) is perhaps a little slower, especially on older devices. But it should be possible to select the Points DB "Honshu" when I'm just displaying the Locus Map "Honshu"...

EDIT: Looks like tapio is complaining about the same thing and I didn't see that. Anyway, I'm not the only one ;)

Quote from: michaelbechtold on July 01, 2019, 22:55:11Naming convention is: <country>.osm.map and ...osm.db

Sometimes!? this is not enough... Probably best is to use lowercase.

sweden.osm.db + sweden.osm.map --> WORKS
Sweden.osm.db + Sweden.osm.map --> POIDB NOT DISPLAYED

Linux filesystem is case sensitive.

Odesláno z mého Mi A2 pomocí Tapatalk

Quote from: poutnikl on July 02, 2019, 15:30:39Linux filesystem is case sensitive.

Yes. But:
Sweden.osm.db + Sweden.osm.map --> POIDB NOT DISPLAYED

EDIT: I checked it twice, because it's weird. It's the Sweden v4 map from OAM and Menions poi database.

Quote from: tapio on July 02, 2019, 17:29:14
Yes. But:
Sweden.osm.db + Sweden.osm.map --> POIDB NOT DISPLAYED

Perhaps the app is not looking for "the same filename but ext", but for hard coded lower case variant.

Odesláno z mého Mi A2 pomocí Tapatalk

Quote from: poutnikl on July 02, 2019, 17:33:10Perhaps the app is not looking for "the same filename but ext", but for hard coded lower case variant.

No. Only Menion can know. E.g.: Netherlands.osm.map+Netherlands.osm.db works.
I keep in mind: "full lowercase is better" :)

@Menion: http://brouter.de/brouter/revisions.html
...
Bicycle+Foot ETA (estimated time of arrival)
ETA data in GPX for Locus + OsmAnd
...

Is that already working in Locus ?

@tapio
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 ".osm.map" 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.

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

Great news about POI.

Wasn't aware of brouter new versions. Just did play store updates.

New Beta version 3.38.7.3 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 :).

Quote from: menion on July 03, 2019, 16:47:15
New Beta version 3.38.7.3 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 :).

For me it's faster now, but at big scale 2km for example the rendering, moving the map, is still slow. At usual scale in normal from 100 to 400 Mt it's good.
Tested with Italy map.

Inviato dal mio SM-A520F utilizzando Tapatalk

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.

Quote from: menion 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.

OAM 4 Shadow enabled with srtm 1 arc

Inviato dal mio SM-A520F utilizzando Tapatalk

3.38.7.1 & 3.38.7.3 at Locus startup: track record bottom panel + cancel button displayed for < 1 second, no progress bar, no chance to cancel track recording

any existing track > Edit Info > crash > (Locus has stopped - Open app again)
Edit Info in 3.38.7 Pro is fine.

I also note (probably not beta related) when you go Store > profile > buy LoCoin, that the balance is not updated at the top of the profile panel until you Back > Back > Back... etc then reenter Store > profile.

That store refresh thing is what I also noticed in current Google Play version.

if i stop track recording, locus V3.38.7.3 FC
after restart of Locus, track recording is paused > stop > FC
so i stopped this track recording with PRO
Log send ~9:50 this morning from my gmail account

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!

Quote from: balloni55 on July 04, 2019, 10:22:34
if i stop track recording, locus V3.38.7.3 FC

Here too.

Can't save tracks in route planner with 38.7.3
Locus restarts or simply close route planner when pressing save. No Save dialog shown.

It's because you are on too old version ;).

Quote from: menion on July 04, 2019, 20:58:12
It's because you are on too old version ;).

Which is a way of saying there's a new beta just released.

Sent from my moto g(6) plus using Tapatalk

I'm a little doubtful about the functionality of the Active items button in the left hand slide out menu
1. It only shows KML/KMZ points and tracks loaded in the Map Items screen although Map Items also works with other file types such as OV2 and GPX. That's an odd restriction.
2. To get items to show up in Active items I have to tap the eye icon in Map Items. If I then hide an item in Active items, I have a crossed out eye icon there and an active eye icon in Map Items. I found that confusing. If that's the way it is to work it might be better with a tristate icon in Map Items: blue eye (visible), ghosted eye (turned off in Active items), crossed out ghosted eye (turned off in Map Items) and with active items showing either a blue active icon or a ghosted grey one. That's just a suggestion but I don't think the present arrangement makes sense.

@Menion, please take a look at this unsolved issue
https://forum.locusmap.eu/index.php?topic=6509.msg55532#msg55532

I tried some minutes ago with the last published beta, no way.
There is something on locus app side that does not work properly, I do not think at a server issue.

1) LT ON and data connection ON (web tracking ok)
2) LT ON and data connection OFF (to simulate the operator data connection fail) wait for web LT disappear - locus app in background
3) LT ON and data connection ON locus app in background (You can wait but you do not appear again on the web LT)
4) LT ON and data connection ON locus app in foreground (Here I'm back on web LT)

So if I lose the data connection and I do not put again in foreground the locus app who is following me lose my tracking.
Case of use, trail running race, MTB ecc where in do not need to use Locus for the map but just for the LT.

"Active items" - how can I make that item appear again? I turned it on in the options, loaded my tracks, points and Lomaps POI. Blue tab bottom left does not appear.

Quote from: tapio on July 06, 2019, 08:16:49
"Active items" - how can I make that item appear again? I turned it on in the options, loaded my tracks, points and Lomaps POI. Blue tab bottom left does not appear.

It only works with KML/KMZ files from the Map Items screen rather than tracks, points and Locus POIs. The tab doesn't appear if there are no active KML/KMZ items. Is that it?

Probably, thx. Then I have never seen it I guess.

V 3.38.7.4
if i click "round button" behind coords inside POI/WP screen to correct coords locus FC
Log send this morning ~9:00

@john_percy
Whole "Active items" dialog was made because of the need to control the transparency of Ground overlay KMZ maps. Later was also added an option to show/hide part of KMZ files because some KML files may be quite complicated (it's directory structure). I absolutely agree it should be useful to apply the same system not just on the KML/KMZ files, no doubt about this.

Consider "Eye" in mapItems screen more like a toggle button. It just says "yes, the item is loaded on the map" and "no, the file is definitely not loaded in the app". But if it's content or any part of it is currently set as "hidden" in "Active items"?

I see here space for improvements (support all formats, better reflect loaded/visibility state), but I'm sorry, but Map items are really not a too high priority.

@lor74cas
for maybe a year, @milan.cejnar is 100% responsible for Live tracking feature. Milane, please look at it. Work on improvement and fixes of the web page started last week, so hopefully, things will move a little now.

@balloni55
thanks, weird issue. Probably the problem in Locus Map "caused" by any 3rd party add-on that should appear on this screen. Should be fixed now, thanks.

I found the layer transparency UX genuinely confusing. At 0% the layer is fully transparent (fine). The label "transparent" appears at the right hand end of the slider (bad), which made me think that the right hand end was the 100% transparent end of the slider.
The reverse is true regarding the label "opaque" appearing at the 0% end of the slider when the slider is at 100%.
Just put these labels at the appropriate end of the slider when they appear, please.(https://uploads.tapatalk-cdn.com/20190711/bfcb4c0beee5ea83065461ec7e8fbaa3.jpg)(https://uploads.tapatalk-cdn.com/20190711/d3c733fab9b9928890d9fb1ed7a81b1b.jpg)

@john_percy
hmm I'm using this kind of slider for so long, that I do not see there a problem :). How can I put these labels on the second side when on the second side is a small dot you use for drag. This may be only improved by putting small "transparent" and "opaque" labels below the whole slider. This slider is really really old and definitely does not fit to current Locus Map style, so good points, I'll try to improve it, thanks.

@0709
Willy, there is a really stupid issue (you already found in a different topic) that cause some mess as you noticed. In the next Beta, it will be for sure ok, sorry!

Hi.  Apologies if this was already discussed up-thread or in another language.

3.38.7 is really laggy when panning the map.  For a typical swipe-to-pan, you drag your finger across the screen, but the map doesn't react until after you've lifted the finger!

Psychologically, it sucks the energy out of exploring the map.

This happens with LoMaps, OAM V3, and OAM V4, on my low-DPI phone, also the high-DPI tablet.  Scrolling elsewhere, eg in the geocache logs list, is normal and responsive.

Is there a drag threshold that's set too high?  Is this something I can adjust?

EDIT:  Ah, I suppose I could turn off some of the ~15,000 geocaches I've got visible.  Trimming that down to ~4000 (my local area) made all the difference, performance acceptable again.  (The others were far outside the area covered by the current view, so should they have made a difference?)

Huge slowdown when more points are loaded at once is unexpected. The map is a lot slower even if an only a small portion of the points is directly visible on the current screen? Hmm are all points from +- same area or is there a few points far away, the second side of Earth for example? This may have an effect.

Just checked again.  I turned on ~21,000 geocaches in Canada, then zoomed into a Hong Kong offline map, where only 3 personal waypoints are shown, nothing else nearby, and POIs are turned off as well.  Result: lag, can lift finger before it reacts.  A small but noticeable fraction of a second.

Then I turned off (hid) all those faraway Canadian geocaches.  Result: Hong Kong is nice and fast, very responsive!

Then I enabled "POI grouping".  Same result, both cases.

I assume this might be triggered by LoMap POIs too...

Quote
Since some weeks geocaching live doesn't work in route planer.  :(

... in latest beta it's working again Thx  8)

@Viajero Perdido
I just tried something similar on my Galaxy S2 (15k caches on the map) and when caches are not visible, the map is perfectly fast. When one or two caches far away from the big group are visible, no difference, still fast.
You wrote you have visible "3 personal waypoints". Does it mean 3 cache waypoints that are connected by the thin line with it's cache? Maybe this may slow down rendering, these three lines in case you are in higher zoom.

@jonny.blue
perfect :)

Quote from: menion on July 21, 2019, 12:47:18You wrote you have visible "3 personal waypoints". Does it mean 3 cache waypoints that are connected by the thin line with it's cache?

Sorry, no.  Those were simply 3 manually-entered waypoints (great dim-sum, etc), with no connection to the great mass of caching waypoints far away.

Does it have performance issues? I have never seen that behaviour before in Locus:
I have no POI loaded and no tracks; Locus works fine.
Now I load all tracks from a folder (39) - and Locus is unusable. Moving the map takes long, double tap for showing/hiding the toolbars is unresponsive and very laggy. Feels like 100% CPU consumption.
My device is a Sony Z1, ie. not a new one, but I have never experienced Locus to be this way. Have also restarted device, no change.

With 3.38.7 I cannot confirm this. No problems with 64 active tracks on Tenerife and 20 big tracks in east-europe. Android 7. (From HOME).

@Viajero Perdido & @tapio

performance problems are really complicated to solve. Best usually is to give me steps to simulate it. If there are no simple steps, full backup over Backup manager may help (together with information what point/tracks enable and where to place a map). In the worst case, I may prepare a special version that may tell us more.

Also, suggest to try the latest Beta version or wait a few days on the new version on Google Play. I made there some performance improvements, so it may help here as well.

Quote from: menion on July 22, 2019, 16:57:44.Best usually is to give me steps to simulate it.

Short and sweet:
1. Enable 20,000+ geocaches in one region
2. Zoom in to opposite side of planet, and note responsiveness.

No tracks visible, no map overlays, nothing else fancy.  I'll charge up the old tablet I use for betas, and give the beta a try...

Yep, as I wrote here: https://forum.locusmap.eu/index.php?topic=6579.msg56523#msg56523

I should have tried the beta or waited for the next release before speaking up, sorry.  Just tried the beta, and the performance issue is gone.  Thanks!

As you said in the release notes, "massive performance optimizations".  :)

Ah perfect. Good is that once I'll have some time, there is still space for some performance improvements :).

I think the last Beta is without problems.

Graphhopper offline works for me in Locus Pro but not in the latest beta. I get an orange toast. T: Problem with the service.

Sent from my moto g(6) plus using Tapatalk

Thanks, John, I'll look at it. I'm just waiting on some updates in GraphHopper library and will publish new add-on version & new routing data.

Aaaaand topic closed ... 3.39+ is out, uf :)