This object is in archive! 

Offline Tile-Maps take minutes to load since 3.23

Hannes S. shared this problem 7 years ago
Solved

Android 4.4.2 / Locus 3.23.1

If I try to open any of my offline tile maps (vector maps work) then it will take ages to load. If the map is larger than 500MB then after about a minute I get the message that Locus is not responding. If I click "Wait" then for a 0.9GB map it took another 3-5 minutes (!!) to finally load. As soon as I scroll the map it freezes again.

It makes no difference whether the map is on the internal storage or on the sd card.

In Locus 3.22 it definitely still worked. I don't know if this started with 3.23.0 or 1

I certainly didn't do anything to my S5 mini during that time.

All these maps loaded inside seconds for the last 2 years... What happened?

Thanks in advance

Hannes

Replies (4)

photo
1

Good day Hannes,

sorry to hear it. Can't say if anything has changed, but there were some smaller changes in handling of SQLite base maps.


Is it possible for you to share with me one of your problematic maps? It should help a lot to simulate ( I hope ) this issue on own device. Thank you!

photo
1

Hi Menion!

Sorry for the delay. I looked for my smallest map to send and opened a 116 MB map. It loaded! But then I zoomed out and it froze again... Since I didn't want to send you a 116MB file I looked further and found a 16MB map. Loaded it and worked. Zoomed out and worked...

This got me thinking. This map was one of a kind so I suspected Autoload. Once I deactivated Offline Map-Autoload (had it on for maps of same type) I noticed that several of the maps are still working normally.

Testing this further to then send you the smallest map that definitely stopped working i noticed that size doesn't seem to be the issue. I have a working 0,98 GB one and a not-working 326MB map.

And then it hit me that the 0,98GB map was the only one of the larger maps that I really sat out waiting for it to load (about 5 minutes).

So at the moment my theory is the following: Based on your comment that there were smaller changes of SQLite i think it might build a new journal or do whatever to the sqlite file and once this is done the map works normally again.

Since I had Autoload on, I seemed to have triggered the process on one of the large maps every time but I never had it finish its job... just a theory. At the moment I am waiting for my favorite map (5GB) to "convert". 10 minutes in and counting =) Will keep you updated

photo
1

Hi Menion! It's working!

Took "only" 16 minutes for the 5GB map to "convert" (would have estimated at least half an hour). I am confident now for the rest of the maps that I can work it out the same way and should eventually be able to turn on autoload again.

Checked the map files: journal file seems to have stayed untouched (old timestamp). sqlitedb-file has been updated.

I will stop loading maps for the time being if you should want me to send you one that hasn't been updated yet. I am using that one map 90% of the time anyway.

I consider this issue resolved since I am confident I can get the rest of the maps working by "loading/converting" them.

Thanks a lot for the quick support.

Best app ever

photo
1

Hello,

ahh I'm stupid. I had made small update of SQLite map so these maps needs to be re-initialized. Anyway I've forget to change one global parameter. Result is, that maps are re-initialized only when it's needed ( after you select them ) and now all at once at start. If you wants to re-init all maps at once, simply delete Locus/cache/map/init directory. This will force Locus Map to reload all at once. Do not forget to do it when you won't need a device for a while, because as I see, it will take a while for such huge maps!


Sorry for a complications.

Replies have been locked on this page!