Hi again,
I have another new issue with version 3.38: If I zoom in to a very close zoom level, it's quite impossible to move to another map section by finger swiping. In most times nothing does happen. And then, if increasing the swiping distance an speed, suddently I'm on a map section, I never wanted to go to. Very annoying! If I zoom out some levels, the reaction on finger swiping gets better. But now it's hard to adjust the map to the desired location, since all map details are very tiny, and the swiping distance must be minimal. Is it possible to improve the reaction on finger swiping at close zoom levels?
Best regards
tkansgar
The same problem 
Hi Benjamin,
this should help:
1) activate expert settings: https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings
2) turn off "smooth interface"
3) turn on "Map hardware acceleration"
Then, here are some more tips how to maintain Locus Map's performance: https://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance
Hi Benjamin,
this should help:
1) activate expert settings: https://docs.locusmap.eu/doku.php?id=manual:advanced:customization:config#expert_settings
2) turn off "smooth interface"
3) turn on "Map hardware acceleration"
Then, here are some more tips how to maintain Locus Map's performance: https://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance
I have the same issue. I tried the solution in Michal's reply, but it does not really help. The point is more that it takes 1.5 seconds for the map to respond when panning/dragging the map. In that time, address markers pop up. And it is rather annoying when swiping the map more than part of the page, since you cannot swipe-swipe-swipe, but every time you release the screen, the next swipe takes >1 second to respond to the new touch. Scrolling the map has become very uncomfortable.
I think it is more the response time for touching the maps screen then the rendering of the map itself. Although, I have the feeling that also the map renders slower since the latest 3.38.6 update.
I use the latest Locus Pro on a Sony Xperia Z3.
I have the same issue. I tried the solution in Michal's reply, but it does not really help. The point is more that it takes 1.5 seconds for the map to respond when panning/dragging the map. In that time, address markers pop up. And it is rather annoying when swiping the map more than part of the page, since you cannot swipe-swipe-swipe, but every time you release the screen, the next swipe takes >1 second to respond to the new touch. Scrolling the map has become very uncomfortable.
I think it is more the response time for touching the maps screen then the rendering of the map itself. Although, I have the feeling that also the map renders slower since the latest 3.38.6 update.
I use the latest Locus Pro on a Sony Xperia Z3.
Hi,
what maps cause these lagging problems? LoMaps or OpenAndroMaps or some downloaded rasters? We are trying to figure out the problem and simulating it is quite difficult.
Michal
Hi,
what maps cause these lagging problems? LoMaps or OpenAndroMaps or some downloaded rasters? We are trying to figure out the problem and simulating it is quite difficult.
Michal
Lo maps and openandromaps are having this problem since latest update. The app become useless with this slow panning
Lo maps and openandromaps are having this problem since latest update. The app become useless with this slow panning
Also loading of Locus and map takes much more time than before.. Now it automatically start track recording because I had set the count down to 5 seconds, but the program loads in 7-8 seconds at first start
Also loading of Locus and map takes much more time than before.. Now it automatically start track recording because I had set the count down to 5 seconds, but the program loads in 7-8 seconds at first start
I use the same maps as before : Openandromaps Netherlands. Strange enough, locus is a bit more responsive today than yesterday, although I stopped the app and reloaded it after changing the mentioned options,and then it made no difference. Still, it's showing a lag in map panning, and is slow in redrawing the (vector map) tiles. I made a screen capture movie and will try to measure the response and delay time.
Can I find an older version somewhere so I can make a quantitative comparison?
I use the same maps as before : Openandromaps Netherlands. Strange enough, locus is a bit more responsive today than yesterday, although I stopped the app and reloaded it after changing the mentioned options,and then it made no difference. Still, it's showing a lag in map panning, and is slow in redrawing the (vector map) tiles. I made a screen capture movie and will try to measure the response and delay time.
Can I find an older version somewhere so I can make a quantitative comparison?
Hi,
we are sorry for inconveniences. We are testing what you are reporting but to no avail - we can't simulate it. What do you mean by "it's quite impossible to move to another map"? The map doesn't move or Locus shows no map on the place where the map should be? What kind of map are you writing about? Raster? Vector?
best regards
Michal
Hi,
we are sorry for inconveniences. We are testing what you are reporting but to no avail - we can't simulate it. What do you mean by "it's quite impossible to move to another map"? The map doesn't move or Locus shows no map on the place where the map should be? What kind of map are you writing about? Raster? Vector?
best regards
Michal
Tried the new version today, but it's all the same : program starts slow (8 seconds and it's starting track recording for me.. before was under 5 seconds) and the map panning especially in more zoom~200 or 300 meters ~ is slow. So nothing changed
Tried the new version today, but it's all the same : program starts slow (8 seconds and it's starting track recording for me.. before was under 5 seconds) and the map panning especially in more zoom~200 or 300 meters ~ is slow. So nothing changed
P. S. I have Samsung galaxy S8.. Should not be a slow device
P. S. I have Samsung galaxy S8.. Should not be a slow device
I have Moto Z Play, frst gen with Android 8. Hope that helps. Locus behaved directly with Locus <3.36.6. i did the same things before. So it is from my point of view not the phone causing the trouble.
Update is not available for me now. I guess a google thing.
Thanks to all the other users for their patience figuring out the problem. I do not have time for that now.
I have Moto Z Play, frst gen with Android 8. Hope that helps. Locus behaved directly with Locus <3.36.6. i did the same things before. So it is from my point of view not the phone causing the trouble.
Update is not available for me now. I guess a google thing.
Thanks to all the other users for their patience figuring out the problem. I do not have time for that now.
Hi Michal,
you missed one word from my sentence: "it's quite impossible to move to another map section". The screen doesn't move the map section in most cases, when swiping with a finger. The higher the zoom level, the worse this effect. In the highest zoom level finger-swiping the map section is quite impossible. Do you understand, what I mean?
Best regards
tkansgar
Hi Michal,
you missed one word from my sentence: "it's quite impossible to move to another map section". The screen doesn't move the map section in most cases, when swiping with a finger. The higher the zoom level, the worse this effect. In the highest zoom level finger-swiping the map section is quite impossible. Do you understand, what I mean?
Best regards
tkansgar
Hi,
ah, you're right, my mistake. So it's impossible to shift map or zoom it... We registered this problem from several users but couldn't determine what devices have these problems, anyway we tried to fix it - update to 3.38.7. version, it should be already available at Google Play. Does this problem still persist?
Michal
Hi,
ah, you're right, my mistake. So it's impossible to shift map or zoom it... We registered this problem from several users but couldn't determine what devices have these problems, anyway we tried to fix it - update to 3.38.7. version, it should be already available at Google Play. Does this problem still persist?
Michal
Currently there still is 3.38.6, which I have already. I will wait for 3.38.7. Many thanks for the info.
Currently there still is 3.38.6, which I have already. I will wait for 3.38.7. Many thanks for the info.
I measured the delay while panning the map on a Sony Xperiz Z3 for the latest versions 3.38.7 (after the latest update) and with version 3.37.2. With the legacy version, I get a response delay of 0.15 sec, which is hardly noticeable, and with the latest version it is 0.48-0.62 sec. Unfortunately, the screen capture files are too large to attach here.
However, it seems like this issue is not really fixed or has changed at all in the latest upgrade of Locus Pro. I suppose it has to do with the way the generated map image (either from vector maps or online map tiles) is cached and slided by the app. Or maybe there is another reason for a delay in the response, where a touch event is handled and the phone is instructed by Locus to response with sliding the map image. I don't know, I'm not an Android developer.
But I hope you can use my feedback to fix this. I like for the moment the old version much better than the latest.(I don't know what features I'm missing, though). Is there somewhere where I can find more recent versions than 3.37.2, so I can help determining at what version the delay was introduced? I'd be happy to test all intermediate APK's.
I measured the delay while panning the map on a Sony Xperiz Z3 for the latest versions 3.38.7 (after the latest update) and with version 3.37.2. With the legacy version, I get a response delay of 0.15 sec, which is hardly noticeable, and with the latest version it is 0.48-0.62 sec. Unfortunately, the screen capture files are too large to attach here.
However, it seems like this issue is not really fixed or has changed at all in the latest upgrade of Locus Pro. I suppose it has to do with the way the generated map image (either from vector maps or online map tiles) is cached and slided by the app. Or maybe there is another reason for a delay in the response, where a touch event is handled and the phone is instructed by Locus to response with sliding the map image. I don't know, I'm not an Android developer.
But I hope you can use my feedback to fix this. I like for the moment the old version much better than the latest.(I don't know what features I'm missing, though). Is there somewhere where I can find more recent versions than 3.37.2, so I can help determining at what version the delay was introduced? I'd be happy to test all intermediate APK's.
Good day guys,
thank you for your testing and patience. Difference between 3.37.2 and 3.38.x is huge (100k+ changed lines of code) so it is almost impossible to find the reason for any problem by comparing app source code. Unfortunately, no one from our team has the same problems as you describe here.
Anyway, I'll ask for help with it, if anyone will have a little time. I've just published a Beta version on Google Play (it may take an hour or two till it appears for download). Install it, start it, use it. Seems that problem happens mainly in high zoom levels. So zoom in as much as possible to make app really slow. Then do these steps:
Result of this will be a file in Locus root directory which I need for analyzing. Thanks!
Good day guys,
thank you for your testing and patience. Difference between 3.37.2 and 3.38.x is huge (100k+ changed lines of code) so it is almost impossible to find the reason for any problem by comparing app source code. Unfortunately, no one from our team has the same problems as you describe here.
Anyway, I'll ask for help with it, if anyone will have a little time. I've just published a Beta version on Google Play (it may take an hour or two till it appears for download). Install it, start it, use it. Seems that problem happens mainly in high zoom levels. So zoom in as much as possible to make app really slow. Then do these steps:
Result of this will be a file in Locus root directory which I need for analyzing. Thanks!
I think this problem is related to the one with slow panning of maps that is described in other topic
I think this problem is related to the one with slow panning of maps that is described in other topic
I managed to get a better time with panning by disabling setting /maps/Advanced features /preload global map. Here I had Google hybrid map before, but after disable this timing is better, but not quite good as in previous versions
I managed to get a better time with panning by disabling setting /maps/Advanced features /preload global map. Here I had Google hybrid map before, but after disable this timing is better, but not quite good as in previous versions
Also the issue appears only beginning with zoom 700 meters and more (300,200,etc)
Also the issue appears only beginning with zoom 700 meters and more (300,200,etc)
Hi Menion,
I am willing to help and installed the beta. However, I am not really sure what to do after tracing started. What do you actually mean with “only move with the map a little”? If I try panning the map using the touch screen , the app freezes (Android message pop-up).
Where do you want me to send the trace-file?
Best wishes,
GuRa
Hi Menion,
I am willing to help and installed the beta. However, I am not really sure what to do after tracing started. What do you actually mean with “only move with the map a little”? If I try panning the map using the touch screen , the app freezes (Android message pop-up).
Where do you want me to send the trace-file?
Best wishes,
GuRa
I have created some trace files. How can I send them to you?
I have created some trace files. How can I send them to you?
Send them to locus.map@asamm.com
Send them to locus.map@asamm.com
Hello guys,
I've already received yesterday very useful trace from Marius (thanks for this!) so no testing needed now.
I hope for some single bug clearly visible and easily fixable. But it does not look so. In Marius trace is visible small slowdown due to screen rotate and some visible points on the map (is it possible?), but nothing serious. Anyway, I've invested quite a lot time during last two days to various optimizations here and there and I think results should be significant.
I'll publish a new Beta version during next days, so if you will have time to play a little with it and write to me "feelings", it will be really welcome. Thanks.
Hello guys,
I've already received yesterday very useful trace from Marius (thanks for this!) so no testing needed now.
I hope for some single bug clearly visible and easily fixable. But it does not look so. In Marius trace is visible small slowdown due to screen rotate and some visible points on the map (is it possible?), but nothing serious. Anyway, I've invested quite a lot time during last two days to various optimizations here and there and I think results should be significant.
I'll publish a new Beta version during next days, so if you will have time to play a little with it and write to me "feelings", it will be really welcome. Thanks.
Hi, some of the traces I made with the slow planning test beta version. During the trace, my phone asked a couple of times if I wanted to stop the program because it was not responsive, but in the end the map did move.
Best regards, Jan-Gerard van der Toorn
On July 2, 2019 12:35:29 PM GMT+02:00, Locus Map <locus.map@asamm.com> wrote:
Hi, some of the traces I made with the slow planning test beta version. During the trace, my phone asked a couple of times if I wanted to stop the program because it was not responsive, but in the end the map did move.
Best regards, Jan-Gerard van der Toorn
On July 2, 2019 12:35:29 PM GMT+02:00, Locus Map <locus.map@asamm.com> wrote:
Hi Alex,
we don't register any massive Locus Map performance dropout, moreover on such a powerful device as yours. Please make sure you don't have too many tracks or too many points active (displayed on map), that you don't use some excessive map overlay or huge KMZ map file (more tips for improving Locus perfomance).
Yesterday we published a new beta with much enhanced performance so if you are interested, please try it.
best regards
Michal
Hi Alex,
we don't register any massive Locus Map performance dropout, moreover on such a powerful device as yours. Please make sure you don't have too many tracks or too many points active (displayed on map), that you don't use some excessive map overlay or huge KMZ map file (more tips for improving Locus perfomance).
Yesterday we published a new beta with much enhanced performance so if you are interested, please try it.
best regards
Michal
Maybe it's the same problem from this :
https://help.locusmap.eu/topic/slow-panning-and-zooming-displaying-of-uwanted-marks
Maybe it's the same problem from this :
https://help.locusmap.eu/topic/slow-panning-and-zooming-displaying-of-uwanted-marks
Hi,I upgraded to v3.39.1 an hour ago just to find out that the panning/zoom is still slow.
However, this could be a bit different problem than others have. If I understand correctly, majority of users reported slow rendering of the vector maps (here and elsewhere). Unlike them I've been having extremely slow Locus responses when panning the raster maps (namely those by SHOCart) thorough all the 3.38.x versions. Unfortunately, the eagerly awaited v3.39 did not bring me the promised massive performance optimizations, and SHOCarts are still slow as hell, if not even slower than before. Instead of smoothly moving, the map waits a second or so, then jumps to a new position. Sometimes jumps once again, but a shorter distance, sometimes it does not move at all and displays an info popup instead.
However, I did not ever notice any problem with vector maps (either LoMaps, ore any other open street ones). Even though I do have a very obsolete phone by today standards, the Lenovo A1000, 4". Which sounds totally illogical to me, as I would guess that the phone needs to compute the vector map view first, then display it. While, in the case of the raster map, phone only needs to copy bitmap. Now, my question is: Did not you guys change yet something else, in addition to the rendering engine? Perhaps reading from the map database? It could explain why the SQLite maps are so slow.
To solve my troubles somehow, I finally downgraded to v3.36.2 which was like a drop of the water of life to my phone. The SHOcart maps panning is seamless again. Can you recommend me please the last version before big changes? Sure I would prefer the newest shiny one, but sadly, whole 3.38.x to 3.39 range does not work well for me.
Michal
Hi,I upgraded to v3.39.1 an hour ago just to find out that the panning/zoom is still slow.
However, this could be a bit different problem than others have. If I understand correctly, majority of users reported slow rendering of the vector maps (here and elsewhere). Unlike them I've been having extremely slow Locus responses when panning the raster maps (namely those by SHOCart) thorough all the 3.38.x versions. Unfortunately, the eagerly awaited v3.39 did not bring me the promised massive performance optimizations, and SHOCarts are still slow as hell, if not even slower than before. Instead of smoothly moving, the map waits a second or so, then jumps to a new position. Sometimes jumps once again, but a shorter distance, sometimes it does not move at all and displays an info popup instead.
However, I did not ever notice any problem with vector maps (either LoMaps, ore any other open street ones). Even though I do have a very obsolete phone by today standards, the Lenovo A1000, 4". Which sounds totally illogical to me, as I would guess that the phone needs to compute the vector map view first, then display it. While, in the case of the raster map, phone only needs to copy bitmap. Now, my question is: Did not you guys change yet something else, in addition to the rendering engine? Perhaps reading from the map database? It could explain why the SQLite maps are so slow.
To solve my troubles somehow, I finally downgraded to v3.36.2 which was like a drop of the water of life to my phone. The SHOcart maps panning is seamless again. Can you recommend me please the last version before big changes? Sure I would prefer the newest shiny one, but sadly, whole 3.38.x to 3.39 range does not work well for me.
Michal
Hi,
since yesterdays update to version 3.92.2, my rendering problems are gone. It works with Locus maps and osmandromaps as well. Hill shading works well. Different Raster maps as well.
Thank you!
Hi,
since yesterdays update to version 3.92.2, my rendering problems are gone. It works with Locus maps and osmandromaps as well. Hill shading works well. Different Raster maps as well.
Thank you!
The latest update has fixed my rendering problem as well, thanks guys!
The latest update has fixed my rendering problem as well, thanks guys!
I just updated and the maps are so much more responsive now. Excellent! I am extremely happy. Thanks, locus is the best map app there is (again).
I just updated and the maps are so much more responsive now. Excellent! I am extremely happy. Thanks, locus is the best map app there is (again).
Yes, great! Version 3.39.2 fixed my panning issues too. Many, many thanks for this app!
Yes, great! Version 3.39.2 fixed my panning issues too. Many, many thanks for this app!
Hi guys,
4 positive responses on new version regard slow maps, this is really positive result, thanks too :).
And one negative, sorry to read it Michal (@hpmickey). I've copied your two posts to separate private topic so we may discuss it there deeper without "spamming" others. I'll write to you tomorrow, thanks.
Anyway generally, problem solved.
Hi guys,
4 positive responses on new version regard slow maps, this is really positive result, thanks too :).
And one negative, sorry to read it Michal (@hpmickey). I've copied your two posts to separate private topic so we may discuss it there deeper without "spamming" others. I'll write to you tomorrow, thanks.
Anyway generally, problem solved.
Replies have been locked on this page!