This object is in archive!
2gb map limit
Solved
I've made a fairly large map in the MBtiles sqlite format. I can't load it with locus, it says an Android limitation of 2Gb. The same map file works fine with Orux. Is there a fix for this?? I paid for Locus Pro, and prefer it over Orux!!
The same problem 
Good day Myron,
may I ask you, what device you use? This limit was on older devices with 2.X Android on board. Is this your case? Because otherwise this limit is 8, maybe even 16 GB?
I'm also surprised that map works in different app. 2 GB limit was limitation of internal SQLite database engine of Android. Interesting.
Good day Myron,
may I ask you, what device you use? This limit was on older devices with 2.X Android on board. Is this your case? Because otherwise this limit is 8, maybe even 16 GB?
I'm also surprised that map works in different app. 2 GB limit was limitation of internal SQLite database engine of Android. Interesting.
I haven't tried the map on a stock rom yet. I will try to do that today. Thanks for your help so far.
I haven't tried the map on a stock rom yet. I will try to do that today. Thanks for your help so far.
Stock android does not read NTFS SD cards, which is needed to put my map file on to it, because it's too large a file for fat32.
Cyanogenmod includes NTFS built in. I think someone made something which allows stock Roms to use NTFS, so I'll have to try that yet.
Stock android does not read NTFS SD cards, which is needed to put my map file on to it, because it's too large a file for fat32.
Cyanogenmod includes NTFS built in. I think someone made something which allows stock Roms to use NTFS, so I'll have to try that yet.
Any idea when the next version will come out? Thanks
Any idea when the next version will come out? Thanks
I also just confirmed this issue. I have a map in mbtiles that is 1.8GB that loads fine and any map I create that is larger than 2GB will not load. I never receive an error, Locus just tries to load it and the loading progress bar never completes.
I also just confirmed this issue. I have a map in mbtiles that is 1.8GB that loads fine and any map I create that is larger than 2GB will not load. I never receive an error, Locus just tries to load it and the loading progress bar never completes.
Hi everyone!
Perhaps interesting fact: My biggest map is 24.7GB, sitting on an exFAT formatted microSD card. Has been working flawlessly since at least 3.3.0 on an Android 4.4 device. It's definitely sqlite, dunno about MBtiles.
Hi everyone!
Perhaps interesting fact: My biggest map is 24.7GB, sitting on an exFAT formatted microSD card. Has been working flawlessly since at least 3.3.0 on an Android 4.4 device. It's definitely sqlite, dunno about MBtiles.
Thanks for all the help. I finally got the map to load after 1 hour & 30 minutes. Now that it is loaded, it works great! I also tried the map on another device and it took about 1 hour & 10 minutes to load (Galaxy S5). Debug log did not show anything useful. It is kinda weird that my maps under 2GB load in less than 5 minutes and I have 2 maps that are between 2gb and 3gb that take over an hour. The only difference I can think of is I am generating more tiles (non transparent) at zoom 21.
Thanks for all the help. I finally got the map to load after 1 hour & 30 minutes. Now that it is loaded, it works great! I also tried the map on another device and it took about 1 hour & 10 minutes to load (Galaxy S5). Debug log did not show anything useful. It is kinda weird that my maps under 2GB load in less than 5 minutes and I have 2 maps that are between 2gb and 3gb that take over an hour. The only difference I can think of is I am generating more tiles (non transparent) at zoom 21.
Brandon, for me it is sometimes also mystery why simple request into database may took more then even 10 minutes. Anyway I'm glad it works for you now! Enjoy
Brandon, for me it is sometimes also mystery why simple request into database may took more then even 10 minutes. Anyway I'm glad it works for you now! Enjoy
Replies have been locked on this page!