Locus Map crash using offline OS Maps
Hi,
it has been over 1 year I am using Locus app. At first period it was as a free user. At the other half, I have PRO version.
- I test Locus into my 2 smartphones. It was in airplane mode with no sim card inside. Only with navigation apps inside.
1. Samsung GT-I9300
android 4.3 (no root)
application folder and app, into SD card - Lexar 64GB (speed x300)
2. OnePlus A5010
android 7.1.1 , next 8.0.0 , next 8.1.0 (no root)
- I am using offline vector maps like
1. openandromaps
2. freizeitkarte-osm.de
Problem
no matter what theme I choose, soon or late, when I zoom or moving the map with my fingers, the app crash.
- of course I had test a lot of different versions of app
- of course I have tested it, after hard reset of my smartphone. After clean install, after clear data, after reboot.
ALWAYS, soon or late, the app will crash
There are no "special settings" into the app. I am very "basic user"
Has anyone any suggestion / solution about this ?
The same problem 
Good day Ineam,
sorry for a late response, we had some troubles with new app version.
App crash for you on both devices? Usually best in case of the crash is to create a log by this method: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . In this case, I expect some problem with how Android works with map images, but surprising for me is that you have the same issue on both devices.
Also, may you please try it (and also create a log in case of the problem) with latest 3.32.1 version we just published on Google Play? There was a small change, that may affect this as well.
thank you,
Menion
Good day Ineam,
sorry for a late response, we had some troubles with new app version.
App crash for you on both devices? Usually best in case of the crash is to create a log by this method: http://docs.locusmap.eu/doku.php?id=manual:faq:how_to_create_debug_log . In this case, I expect some problem with how Android works with map images, but surprising for me is that you have the same issue on both devices.
Also, may you please try it (and also create a log in case of the problem) with latest 3.32.1 version we just published on Google Play? There was a small change, that may affect this as well.
thank you,
Menion
Hi Menion,
about crashes, yes this is happening on both devices
but at this period, I don't have any outdoor activities to test again this symptom. I hope new version to be stable as a rock.
----------
I have also the app OruxMaps
There is one option
menu - maps - zoom settings - bug with zoom
when i set this to ON, the problem is disappear
so I have the proof, there is not only my case.
Hi Menion,
about crashes, yes this is happening on both devices
but at this period, I don't have any outdoor activities to test again this symptom. I hope new version to be stable as a rock.
----------
I have also the app OruxMaps
There is one option
menu - maps - zoom settings - bug with zoom
when i set this to ON, the problem is disappear
so I have the proof, there is not only my case.
Hi Menion,
yesterday I make some tests using the latest version from playstore, Locus Map 3.32.2.
Unfortunately, the problem still exists, crashes when "zoom in" to the maps
On Sat, Aug 4, 2018 at 5:05 PM Locus Map <locus.map@asamm.com> wrote:
Hi Menion,
yesterday I make some tests using the latest version from playstore, Locus Map 3.32.2.
Unfortunately, the problem still exists, crashes when "zoom in" to the maps
On Sat, Aug 4, 2018 at 5:05 PM Locus Map <locus.map@asamm.com> wrote:
Good day,
sorry for a delay in my response.
Interesting that some option in OruxMaps helps here. I firstly wanted to wrote you "sorry" and offer an older version or refund (if you have made purchased not too in history), but we may at least check what exactly this error is. If you find time, may you please try to create bug report by this method, right after app crash again?
Thank you very much and sorry for a complication!
Good day,
sorry for a delay in my response.
Interesting that some option in OruxMaps helps here. I firstly wanted to wrote you "sorry" and offer an older version or refund (if you have made purchased not too in history), but we may at least check what exactly this error is. If you find time, may you please try to create bug report by this method, right after app crash again?
Thank you very much and sorry for a complication!
Hi Menion,
1. about OruxMaps
forget what I said, for some days it was working .... but after some good stress tests, the crashes has return. For the last 3 versions of the app, problems are bad friends to me. I have post this issue also to orux forum, but with no answer to my 2 posts. 3rd post ... NO thanks !!!!
2. about my 2 devices
latest period I have only one device, the 1+ 5T. Samsung S3 is given away ....
3. about refund
thanks .... but the money are to little, to make my worry about them. I wish to found a solution, soon or late.
4. about future crashes
the app shows one small window with 2 options. The second is to send the error. I will send this after next problem appears.
5. for now ...
I start using OsmAnd+. I hope with this app for my navigation needs, to forget the crashes.
6. about your delay
I understand very well your workload.
As you can see, we have 2 apps (orux + lucus) with common the map files. I believe it's very strange to have both the app a bug. Maybe something is wrong with the common map files.
Osmand has also OpenStreet maps but with it's own compress structure. So far I don't have any crash. For me, this must investigate.
thanks
On Thu, Oct 11, 2018 at 3:32 PM Locus Map <locus.map@asamm.com> wrote:
Hi Menion,
1. about OruxMaps
forget what I said, for some days it was working .... but after some good stress tests, the crashes has return. For the last 3 versions of the app, problems are bad friends to me. I have post this issue also to orux forum, but with no answer to my 2 posts. 3rd post ... NO thanks !!!!
2. about my 2 devices
latest period I have only one device, the 1+ 5T. Samsung S3 is given away ....
3. about refund
thanks .... but the money are to little, to make my worry about them. I wish to found a solution, soon or late.
4. about future crashes
the app shows one small window with 2 options. The second is to send the error. I will send this after next problem appears.
5. for now ...
I start using OsmAnd+. I hope with this app for my navigation needs, to forget the crashes.
6. about your delay
I understand very well your workload.
As you can see, we have 2 apps (orux + lucus) with common the map files. I believe it's very strange to have both the app a bug. Maybe something is wrong with the common map files.
Osmand has also OpenStreet maps but with it's own compress structure. So far I don't have any crash. For me, this must investigate.
thanks
On Thu, Oct 11, 2018 at 3:32 PM Locus Map <locus.map@asamm.com> wrote:
Hello,
I perfectly understand José (developer of Orux map) that he tries to ignore these problems :). Apps installed from Google Play, silently reports some information about crashes back on Google Play into some developers console. With the new version I see around 200 crashes, but with maybe 90% of them, I have absolutely no idea what to do. These are some serious native crashes in device itself usually caused by huge amount of bitmaps (images) app handle with. And I believe, that exact same issue has Orux.
I do not think, it will be a problem of the map itself. Anyway, you may this simply exclude: just from Locus Store download any LoMap for your area (3 are for free) and try it.
---
Hmm one more option to test:
Expect, that this will slow down the speed of map. Should be not a big problem if you are not using any overlays (map overlay, wms).
---
And last: if you send the report over dialog that appers when app crash, it is usually not too useful. A lot better is to manually create a bug report by this method and then attach it here. Thanks!
Hello,
I perfectly understand José (developer of Orux map) that he tries to ignore these problems :). Apps installed from Google Play, silently reports some information about crashes back on Google Play into some developers console. With the new version I see around 200 crashes, but with maybe 90% of them, I have absolutely no idea what to do. These are some serious native crashes in device itself usually caused by huge amount of bitmaps (images) app handle with. And I believe, that exact same issue has Orux.
I do not think, it will be a problem of the map itself. Anyway, you may this simply exclude: just from Locus Store download any LoMap for your area (3 are for free) and try it.
---
Hmm one more option to test:
Expect, that this will slow down the speed of map. Should be not a big problem if you are not using any overlays (map overlay, wms).
---
And last: if you send the report over dialog that appers when app crash, it is usually not too useful. A lot better is to manually create a bug report by this method and then attach it here. Thanks!
thanks for the tip
On Thu, Oct 11, 2018 at 8:48 PM Locus Map <locus.map@asamm.com> wrote:
thanks for the tip
On Thu, Oct 11, 2018 at 8:48 PM Locus Map <locus.map@asamm.com> wrote:
Locus Map 3.35.2
device 1+ 5T (A5010) android 8.1.0 no root
today i run the app to test the latest openandromaps with themes (ver. 12/2018). After some map unzoom / zoom the app crash again.
I tried to reboot the device, clear the app cache/data, delete locus folder from memory and run the app from the begging.
After that, I copy to the fresh folder my backup settings (2018-07-03_21-31-02), and the map/themes files. Very soon the crash appears again. i repeat this 3 times with no different results
(into the settings I have test ---disable "Map hardware acceleration"
and something new. with this version when i change "something" to the settings and the app needs to reboot, the automatic restart is NOT working for me.
Locus Map 3.35.2
device 1+ 5T (A5010) android 8.1.0 no root
today i run the app to test the latest openandromaps with themes (ver. 12/2018). After some map unzoom / zoom the app crash again.
I tried to reboot the device, clear the app cache/data, delete locus folder from memory and run the app from the begging.
After that, I copy to the fresh folder my backup settings (2018-07-03_21-31-02), and the map/themes files. Very soon the crash appears again. i repeat this 3 times with no different results
(into the settings I have test ---disable "Map hardware acceleration"
and something new. with this version when i change "something" to the settings and the app needs to reboot, the automatic restart is NOT working for me.
Thanks for tests,
unfortunately, I currently have no ace in hands. Crashes seem to be in some inner Android libraries and we with colleagues aren't able to find any hack to "fix" it.
Because you have Locus Map already for a few months, I may not offer you a refund. But if you are interested, I may provide older app versions. I'm anyway worried it will be the same.
Sorry to write this.
Menion
Thanks for tests,
unfortunately, I currently have no ace in hands. Crashes seem to be in some inner Android libraries and we with colleagues aren't able to find any hack to "fix" it.
Because you have Locus Map already for a few months, I may not offer you a refund. But if you are interested, I may provide older app versions. I'm anyway worried it will be the same.
Sorry to write this.
Menion
Hi Menion,
happy new year.
thanks for the fast response. If you have older "safe" version to test, for me it's OK.
any thoughts about this article
https://www.openandromaps.org/en/locus-direct-install-link-for-multilanguage-v4-maps
Hi Menion,
happy new year.
thanks for the fast response. If you have older "safe" version to test, for me it's OK.
any thoughts about this article
https://www.openandromaps.org/en/locus-direct-install-link-for-multilanguage-v4-maps
Hello,
oki fine. I've prepared versions from the year 2018 here: http://bit.ly/lmVersions , so feel free to play with it.
About the mentioned topic, we just started discussion yesterday here: https://forum.locusmap.eu/index.php?topic=6434.0 . In short, I'm aware of it :).
Hello,
oki fine. I've prepared versions from the year 2018 here: http://bit.ly/lmVersions , so feel free to play with it.
About the mentioned topic, we just started discussion yesterday here: https://forum.locusmap.eu/index.php?topic=6434.0 . In short, I'm aware of it :).
after the tests I report before 2 days, into the same day I make some new.
Locus Map 3.35.2
device 1+ 5T (A5010) android 8.1.0 no root
into the same version of app, after clear install from playstore, I install only my backup settings file, but now I download map files from this server
http://download.mapsforge.org
At first I install V5 maps. After 30-40 minutes of unzoom / zoom tests there was no app crash. After this, I download the same country into V3 map file to test again. When I run the locus app, into 10-20 seconds, the locus crash again. Why the V5 map files works OK ???
I tried from this server, because there are map files from v3 - v4 - v5 of OSM maps
after the tests I report before 2 days, into the same day I make some new.
Locus Map 3.35.2
device 1+ 5T (A5010) android 8.1.0 no root
into the same version of app, after clear install from playstore, I install only my backup settings file, but now I download map files from this server
http://download.mapsforge.org
At first I install V5 maps. After 30-40 minutes of unzoom / zoom tests there was no app crash. After this, I download the same country into V3 map file to test again. When I run the locus app, into 10-20 seconds, the locus crash again. Why the V5 map files works OK ???
I tried from this server, because there are map files from v3 - v4 - v5 of OSM maps
Hello,
interesting. The difference is quite big. V3 maps use an older, highly modified system of map drawing. V4 and V5 maps are not yet perfectly supported (will be most probably during May/June 2019) anyway if they work for you without a crashes, just use them. LoMaps downloaded from Locus Store are based on this older V3 version, but this will most probably change as well.
Hello,
interesting. The difference is quite big. V3 maps use an older, highly modified system of map drawing. V4 and V5 maps are not yet perfectly supported (will be most probably during May/June 2019) anyway if they work for you without a crashes, just use them. LoMaps downloaded from Locus Store are based on this older V3 version, but this will most probably change as well.
I have similar problem, however, the crashes started when I installed v3.35.2. I never experienced a crash on prior Locus Map versions on this phone (I own Locus Map Pro, Android v8.0, Samsung A5 phone) or my previous phone, Samsung S5.
I have similar problem, however, the crashes started when I installed v3.35.2. I never experienced a crash on prior Locus Map versions on this phone (I own Locus Map Pro, Android v8.0, Samsung A5 phone) or my previous phone, Samsung S5.
Replies have been locked on this page!