This object is in archive!
Extremely slow map loading
Answered
I have just bought the application. I choose a vector map and in both
the cases when I move a map or magnify it, it takes several minutes for
the changed map to show. In a freeware "mapsme" application the same
thing takes a couple of seconds.
The same question
Hi Mariusz,
we are sorry you have had this unpleasant experience, however, it is not a standard behaviour. Please let me ask you a few questions:
What kind/provider of vector maps do you use?
Do you use internal themes for the maps or some imported externals?
What kind of phone or tablet do you use and what Android version?
Thank you for the answers in advance. I hope we'll solve this issue to your complete satisfaction.
best regards
Michal Stupka
Locus team
Hi Mariusz,
we are sorry you have had this unpleasant experience, however, it is not a standard behaviour. Please let me ask you a few questions:
What kind/provider of vector maps do you use?
Do you use internal themes for the maps or some imported externals?
What kind of phone or tablet do you use and what Android version?
Thank you for the answers in advance. I hope we'll solve this issue to your complete satisfaction.
best regards
Michal Stupka
Locus team
Vector map I use from the list of vector maps inside the application LoMaps, for Europe Poland there is only one map.
I do not use internal themes for the maps nor some imported externals.
Phone is Samsung Galaxy sduoz GT-S7562
android 4.0.4 this is the newest available for this phone
What is more, the online bitmap maps, included in the app, which can be used off line OSM MTB Europe, work fast, only they occupy 100 000 times more space.
The same problem with a slow locus vector map I had two years ago, so I had to change to its bitmap maps.
Vector map I use from the list of vector maps inside the application LoMaps, for Europe Poland there is only one map.
I do not use internal themes for the maps nor some imported externals.
Phone is Samsung Galaxy sduoz GT-S7562
android 4.0.4 this is the newest available for this phone
What is more, the online bitmap maps, included in the app, which can be used off line OSM MTB Europe, work fast, only they occupy 100 000 times more space.
The same problem with a slow locus vector map I had two years ago, so I had to change to its bitmap maps.
Hi Mariusz,
unlike raster (bitmap) maps which are simple png tiles patched into one big image the vector maps are rendered (generated from raw digital data) directly in your device. So they need a bit extra computing power of the device processor and RAM. Your mobile is an entry level device that, on one hand, can launch Locus correctly and without issues but, on the other hand, rendering vector maps is probably a too difficult task for it. Therefore, using LoMaps (and any other vector maps) can be slower than using bitmaps.
best regards
Michal Stupka
Locus team
Hi Mariusz,
unlike raster (bitmap) maps which are simple png tiles patched into one big image the vector maps are rendered (generated from raw digital data) directly in your device. So they need a bit extra computing power of the device processor and RAM. Your mobile is an entry level device that, on one hand, can launch Locus correctly and without issues but, on the other hand, rendering vector maps is probably a too difficult task for it. Therefore, using LoMaps (and any other vector maps) can be slower than using bitmaps.
best regards
Michal Stupka
Locus team
As I have told you I have no problem using a vector map in "maps me"
https://play.google.com/store/apps/details?id=com.mapswithme.maps.pro&hl=pl
It moves around maps and change their magnification within a couple of second whereas your app takes several minutes. The difference in speed is to big to be blamed on the computer device. You have a slow algorithm to display maps.
As I have told you I have no problem using a vector map in "maps me"
https://play.google.com/store/apps/details?id=com.mapswithme.maps.pro&hl=pl
It moves around maps and change their magnification within a couple of second whereas your app takes several minutes. The difference in speed is to big to be blamed on the computer device. You have a slow algorithm to display maps.
Mariusz,
Maps Me uses only a portion of raw OSM data to display as it is designed for use above all in towns and roads. Locus processes a lot more data including POI database and SRTM data (elevation). If our algorithm is slow then all our users would report "several-minutes" rendering which is not true.
Mariusz,
Maps Me uses only a portion of raw OSM data to display as it is designed for use above all in towns and roads. Locus processes a lot more data including POI database and SRTM data (elevation). If our algorithm is slow then all our users would report "several-minutes" rendering which is not true.
I have not noticed a considerable differance in the amount of data shown on scren for both the apps. Your claim is not justified enough, so your app should work properly on my device. Besides, there is no way in the app options to reduce the amount of shown data.
The problem is that as the computer devices become faster and faster, the developers do not pay enough attention to the optimization of the algorithms speed.
I have not noticed a considerable differance in the amount of data shown on scren for both the apps. Your claim is not justified enough, so your app should work properly on my device. Besides, there is no way in the app options to reduce the amount of shown data.
The problem is that as the computer devices become faster and faster, the developers do not pay enough attention to the optimization of the algorithms speed.
Hi Mariusz,
I perfectly understand your point of view. You are right, devices are faster and faster. And we develop Locus so that it works fluently on majority of them. However, the same as I can't fluently use the latest issue of Photoshop on a Pentium II with 500 MB RAM, Locus doesn't work on your device as fast as on some quad-core 2GB RAM. We do optimize Locus for older and weaker devices and Android OS but all optimization has its limits on order to maintain the scope of functionality.
Hi Mariusz,
I perfectly understand your point of view. You are right, devices are faster and faster. And we develop Locus so that it works fluently on majority of them. However, the same as I can't fluently use the latest issue of Photoshop on a Pentium II with 500 MB RAM, Locus doesn't work on your device as fast as on some quad-core 2GB RAM. We do optimize Locus for older and weaker devices and Android OS but all optimization has its limits on order to maintain the scope of functionality.
You app is not just slow IT HUNGS UP!!!!!! freezes all the phone. It is buggy. I have tried several other apps with vector maps they load within a couple of seconds. Your app does not load a vector map after FIVE MINUTES.
It is worth nothing and landed in a waste basket bin.
You app is not just slow IT HUNGS UP!!!!!! freezes all the phone. It is buggy. I have tried several other apps with vector maps they load within a couple of seconds. Your app does not load a vector map after FIVE MINUTES.
It is worth nothing and landed in a waste basket bin.
Hi Mariusz,
If it is as you say we wouldn't have a half million satisfied users all over the World and Google Play rating 4.4 resp. 4.8 for Pro version. The problem is most probably in your device that can't cope with the app and the amount of data it processes. Have you tried Locus on some other device? Maybe the problem is in your configuration. Do you have Locus installed in the inner memory? We'd like to solve your problem - could you repeat the "crash" situation and create a log report about it? Look here how to do it: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
Hi Mariusz,
If it is as you say we wouldn't have a half million satisfied users all over the World and Google Play rating 4.4 resp. 4.8 for Pro version. The problem is most probably in your device that can't cope with the app and the amount of data it processes. Have you tried Locus on some other device? Maybe the problem is in your configuration. Do you have Locus installed in the inner memory? We'd like to solve your problem - could you repeat the "crash" situation and create a log report about it? Look here how to do it: http://docs.locusmap.eu/doku.php?id=manual:faq:issue_reporting
Good day,
I'm sorry to interrupt your discussion, but as a main Locus developer, I would like to say:
Thanks for understanding.
Good day,
I'm sorry to interrupt your discussion, but as a main Locus developer, I would like to say:
Thanks for understanding.
Problem is only with vector maps. Several other apps load vector maps within 3 to 10 seconds!!!! Does it mean anything? I mean moving maps to load a new area or changing magnification to show new area. Locus pro is the only app I could find that takes approximately 100 times longer to load a vector map on the same device. So locus is not killed by the OS only works extremely slowly. You should refound the purchase.
Problem is only with vector maps. Several other apps load vector maps within 3 to 10 seconds!!!! Does it mean anything? I mean moving maps to load a new area or changing magnification to show new area. Locus pro is the only app I could find that takes approximately 100 times longer to load a vector map on the same device. So locus is not killed by the OS only works extremely slowly. You should refound the purchase.
What is the zoom level you are trying ? (Use ratser maps for zooms up to 9 - overlay technique.)
What is the device you are using ? (I use latest Locus on Android 4.4 without issues, an older version of Locus even works on a HTC desire from 2010 - with vector maps)
What is the zoom level you are trying ? (Use ratser maps for zooms up to 9 - overlay technique.)
What is the device you are using ? (I use latest Locus on Android 4.4 without issues, an older version of Locus even works on a HTC desire from 2010 - with vector maps)
Replies have been locked on this page!