Low zoom level on big Vector Maps Causes Crash!!
Thank you for your interest in Locus
Your Device ?
Your OS version ?
Your Locus Pro Version ?
What means "low zoom level" eg
You have downloaded your map from..?
How old is your map?
How big is your map?
Can you explain step by step what happend?
Have you already sent an error report inside Locus?
Have you sent an error report as described here: http://docs.locusmap.eu/doku.php/manu...
Choose your described map and move/zoom the map in the same way.
this is device you use right? http://www.gsmarena.com/huawei_u8180_...
I`m worried, that this will be problem in this case. Are you using one big map of Netherland (complete) or you downloaded smaller parts and use this?
Anyway problem here is, that your device have really low amount of memory that is available to single process. It`s really deadly combination.
Android 2.2 together with 16MB of available memory for Locus ... sorry, but here is absolutely nothing I can do. You just have to keep as low as possible, number of visible points and tracks on screen
Yes that is the one.
Strange is that when he once took the map(for the moment Spain) without a crash, afterwards it works OK but sometimes somewhat slow.
For the moment we are in Turkey, and for walking, cycling, and even car traveling it gives not much off a problem.
This is visible when you use automatic zoom, but this is not a big problem, you can work with it.
Thanks for your research.
problematic for memory are areas with huge amount of data. For example huge, well mapped cities may cause problems and also almost almost whole netherland. Anyway I really suggest to use smaller vector maps if possible and good luck (and in future, at least little bit better phone ;) )
This phone is very well and very cheap, since he has been rooted he is nearly no more giving big problems(thanks to Link2SD).
Maybe you could do something, even if you think you can`t.
I explain, the crashes occur when zoom-level is very low. This is when you try to make an overview off a map or regio(500 to 1000 km). On that moment you don`t need much detail, and I think that Locus tries to give to much detail --> Crash.
Higher zoom levels don`t give problems(less than 2Km on screen).
Problems start from 300->500Km on screen.
I think that you as a programmer, could maybe make it a little bit easier for processor and memory, without quality loss for the program(Locus).
I guess there are around 100.000 active Locus users around the world. This number is growing.
And I guess, there are around 100 active Locus users with the same device as you have. And this number is shrinking.
If you were a developer, would you invest 20 hours of your working time to solve this issue?
This is a stupid answer.
If a whole lot off the calculations are not needed, don`t execute them, this makes room for much more interesting options even on very much heavier machines.
If you make machines do unnecessary work, it is no use to have a heavier machine.
It`s only a stupid answer, when you didn`t understand the meaning of RAM.
hmm sorry Berkley, cannot agree.
I agree with Bert and it`s logical. If there is place for improvements, why not do it. To save some device power on any place, even if most device have no problems with it, save power to another tasks and also save battery (by less cpu usage)
anyway in this case it`s worst. For rendering of vector maps, I use library MapsForge (http://code.google.com/p/mapsforge/) , so speed any memory usage is not on me. Rest yes and in rest of app I`m still improving some parts to achieve less cpu usage
Come on, it`s ridicolous to even think about working on it.
I`ve got 30k active installations and 3 errors on dev console. Guess what device manufacturer?
I`m not saying I`ll work on it. I just say that from principle point of view, it`s not bad to work on something that work, to make it work better :)
In the case of vector maps and low zoom level it mainly can help to reduce information during creation of the map and maybe additionally when map is rendered (theme).
We’ve re-created new “Netherlands (complete)” map with some changes that could help with your outOfMem problem. Please, update Netherland map via Map manager and let me know how it works.
I am not creating maps, I use vector maps from Mapsforge.
I just don`t know how to create them, and they differ completely from SQL-maps.
I think this is a very good attitude.
Bert, this comment wasn`t directed to you but should expain where changes could be done to reduce the memory footprint. Petr is one of the guys who creates maps and modifies themes. Seems he realized already , see his post below.
Hello Petr Voldan,
I am not living in the Netherlands but in Belgium.
If you want I shall test your map, where can I get it?
Thanks at forehand,
"...map via Map manager..."
I’m sorry but I’m little bit lost in these topics so I thought that your problem was with Netherland map.
So as Gynta already asked: You have downloaded your map from..?
We offer for Locus users own vector maps. There are some information how to download our vector maps http://docs.locusmap.eu/doku.php/shop...
That`s so funny to read! ;)
Actually, the process of purchase vector map via Locus store could not be suitable for you. I can create new map of Belgium and give you direct link for downloading. Is it OK for you?
yes, its tricky ;)
bert is a special customer and sometimes he should read and answere
that could make it easier, to help him
can you please read and comment my 2nd reply ?
I don`t even belive, that he is a real customer ;)
Is this your second reply?
I am sorry but sometimes my answers dissapear, maybe I forget something or do something wrong.
Besides that I am not the whole day before PC.
I downloaded the file but I don`t see what I can do with it, I must not put to much on my phone, problems could arise.
SD-card only 28Gb, second partition 1Gb.(needed for Link2SD)
I posses the map off Belgium, and as I thought she is working fine(small country).
Map causing biggest troubles Spain(Mapsforge), I don`t know how I managed to download there, for the moment it isn`t working anymore.
Start this mapviewer - load your mentioned map - and check it again.
The reason is - if you have the same problems, so you know your phone is lame. The app is a simply mapviewer
OK.,I will check it
With mapviewer no problem(no crash) only little bit slow.
PS.: Tomorrow I will be making test with new version from Menion.
Why is this topic marked as solved? The problem still exists.
Sure, people with phones with many GB's of RAM might not encounter the crashes, but that does not mean that the app is flawless. It crashes when operating the app. When memory is not permitting certain kind of operation, it should handle the exception gracefully. For example, by not allowing to zoom out more.
Also, the Netherlands is not very big. In fact, it's one of the smallest countries in Europe. The app should be capable of handling big maps like any other navigation app on my phone. They don't crash using the same OSM data of the same countries. They simply don't calculate things like buildings and bus stops when viewing a whole country.
If you want to be precise, I'll remark this topic to "unsolvable". There is nothing I may do to better support 2.X devices.
Comments have been locked on this page!