probleme seit dem wechsel auf locus 3.38 (festgestellt auf android 5):
- seit dem wechsel auf die neue kartenengine dauert das aufstarten von locus viel länger.
- ausserdem wird bisweilen nach dem starten nicht die letzte verwendete karte, sondern eine onlinekarte angezeigt. wenn für diesen bereich aber keine onlinekarte zwischengespeichert ist erscheint an stelle der karte eine weisse fläche.
- nach dem starten von locus kann es bisweilen eine weile dauern bis die POIs auf der karte angezeigt werden
The same problem 
Hello guys,
thanks to bongo's precise testing, I believe I have found a reason for this slowdown. Even before the main map screen is visible, Locus Map test if there are any new maps. For this, it checks the content of every directory and subdirectory of "mapsVector" (or custom) directory. I know that Android SD card API is slow, but did not expect that THIS SLOW. I was able to simulate issue on own device and also with some caching, reduce this time to 10%. So in my case from 15 secs to 1.5 sec. Not best, but definitely a lot better. Fix will be included in next bug-fix version 3.38.7 (most probably in the second half of this week).
Thank you for the patience and help with this issue.
One note: because of weird limitations on SD card access since Android 5+, and even that Locus Map supports some data on SD card, I may only highly recommend placing everything into internal memory. Speed benefits (not just the start of the app) are usually noticeable.
Hello guys,
thanks to bongo's precise testing, I believe I have found a reason for this slowdown. Even before the main map screen is visible, Locus Map test if there are any new maps. For this, it checks the content of every directory and subdirectory of "mapsVector" (or custom) directory. I know that Android SD card API is slow, but did not expect that THIS SLOW. I was able to simulate issue on own device and also with some caching, reduce this time to 10%. So in my case from 15 secs to 1.5 sec. Not best, but definitely a lot better. Fix will be included in next bug-fix version 3.38.7 (most probably in the second half of this week).
Thank you for the patience and help with this issue.
One note: because of weird limitations on SD card access since Android 5+, and even that Locus Map supports some data on SD card, I may only highly recommend placing everything into internal memory. Speed benefits (not just the start of the app) are usually noticeable.
Hi,
we are sorry for the inconveniences and we are working hard on fixing the bugs. Please update to Locus Map 3.38.2. and let us know if the issue is gone or not. Thanks!
best regards
Michal, Locus team
Hi,
we are sorry for the inconveniences and we are working hard on fixing the bugs. Please update to Locus Map 3.38.2. and let us know if the issue is gone or not. Thanks!
best regards
Michal, Locus team
ok, i retested with 3.38.2:
- seit dem wechsel auf die neue kartenengine dauert das aufstarten von locus viel länger.
3.38: when starting locus, the white screen showing startup progress appears immediately. scanning local maps takes a long time. especially loading .sqlitedb maps seems to take forever.
3.38.2: when starting locus, i just get a black screen for up to 10 seconds (or even longer). then i get the startup progress screen. now the .sqlitedb maps don't seem to be a problem anymore...but overall time for startup is still about the same, i.e. much longer thatn with the version before 3.38.
- ausserdem wird bisweilen nach dem starten nicht die letzte verwendete karte, sondern eine onlinekarte angezeigt. wenn für diesen bereich aber keine onlinekarte zwischengespeichert ist erscheint an stelle der karte eine weisse fläche.
3.38: i always get a white background with a text like "online map" (instead of the last map used) when starting up.
3.38.2: i sometimes get the last map used (which would be fine) and sometimes get a white background without any text.
- nach dem starten von locus kann es bisweilen eine weile dauern bis die POIs auf der karte angezeigt werden
3.38: sometimes it takes several seconds until any pois are shown on the map
3.38.2: seems to be still the same
regards
tinu
ok, i retested with 3.38.2:
- seit dem wechsel auf die neue kartenengine dauert das aufstarten von locus viel länger.
3.38: when starting locus, the white screen showing startup progress appears immediately. scanning local maps takes a long time. especially loading .sqlitedb maps seems to take forever.
3.38.2: when starting locus, i just get a black screen for up to 10 seconds (or even longer). then i get the startup progress screen. now the .sqlitedb maps don't seem to be a problem anymore...but overall time for startup is still about the same, i.e. much longer thatn with the version before 3.38.
- ausserdem wird bisweilen nach dem starten nicht die letzte verwendete karte, sondern eine onlinekarte angezeigt. wenn für diesen bereich aber keine onlinekarte zwischengespeichert ist erscheint an stelle der karte eine weisse fläche.
3.38: i always get a white background with a text like "online map" (instead of the last map used) when starting up.
3.38.2: i sometimes get the last map used (which would be fine) and sometimes get a white background without any text.
- nach dem starten von locus kann es bisweilen eine weile dauern bis die POIs auf der karte angezeigt werden
3.38: sometimes it takes several seconds until any pois are shown on the map
3.38.2: seems to be still the same
regards
tinu
Hi Tinu,
the slow initialization - we know about it. Probably some unwanted side effect of the new map core. WIll need more analyzing, testing and developing. hopefully we'll fix it till the next production version in June.
Other issues - please test them on the newest 3.38.3. and let me know the results. Thanks
Michal
Hi Tinu,
the slow initialization - we know about it. Probably some unwanted side effect of the new map core. WIll need more analyzing, testing and developing. hopefully we'll fix it till the next production version in June.
Other issues - please test them on the newest 3.38.3. and let me know the results. Thanks
Michal
ok, hope that next release will solve the startup delay issue.
after starting locus many times, i only once had the problem that no map was shown (locus switched to online map) since updating to 3.38.3. so this might be improved with the new version.
loading pois still may take a long time. when the map is shown (after the slow startup process), i did tests where after 2 minutes, still no pois have been shown on the map.
i've recognized that moving the map around may speed up poi loading, i.e. when moving the map around as soon as it is shown, it usually only takes a few seconds to load the pois.
(btw: i use live update of the pois)
with locus versions prior to 3.38, the effect that poi loading takes that long only occured after rebooting of the phone, but never after just terminating and restarting locus.
one thing i've observed is, that when terminating locus, it first removes all pois from the map before locus terminates. i think this has not been like that with older versions. might this be a reason for the effects seen?
tinu
ok, hope that next release will solve the startup delay issue.
after starting locus many times, i only once had the problem that no map was shown (locus switched to online map) since updating to 3.38.3. so this might be improved with the new version.
loading pois still may take a long time. when the map is shown (after the slow startup process), i did tests where after 2 minutes, still no pois have been shown on the map.
i've recognized that moving the map around may speed up poi loading, i.e. when moving the map around as soon as it is shown, it usually only takes a few seconds to load the pois.
(btw: i use live update of the pois)
with locus versions prior to 3.38, the effect that poi loading takes that long only occured after rebooting of the phone, but never after just terminating and restarting locus.
one thing i've observed is, that when terminating locus, it first removes all pois from the map before locus terminates. i think this has not been like that with older versions. might this be a reason for the effects seen?
tinu
"Live update of the pois" - so you mean geocaching live map? It is served by the Geocaching4Locus add-on which is developed and maintained by another company. It streams data from the internet so there may be other factors involved. The caches are not stored - they are always streamed so when there is some obstacle in internet connection, the speed slows down.
Michal
"Live update of the pois" - so you mean geocaching live map? It is served by the Geocaching4Locus add-on which is developed and maintained by another company. It streams data from the internet so there may be other factors involved. The caches are not stored - they are always streamed so when there is some obstacle in internet connection, the speed slows down.
Michal
no. i use the gsak addon to get the pois into locus "on the fly" using live update (this still works fine up to android 7). unfortunately, with android 8 and later, this addon only works for importing from gsak db.
no. i use the gsak addon to get the pois into locus "on the fly" using live update (this still works fine up to android 7). unfortunately, with android 8 and later, this addon only works for importing from gsak db.
well, the GSAK add-on is (was) also provided by somebody else. For some time the add-on development has been abandoned and we have no influence on its performance.
Michal
well, the GSAK add-on is (was) also provided by somebody else. For some time the add-on development has been abandoned and we have no influence on its performance.
Michal
Another topic about the gsak addon and live updates of waypoints you can find here.
Another topic about the gsak addon and live updates of waypoints you can find here.
at least one of the issues is not solved at all. it still persists:
- seit dem wechsel auf die neue kartenengine dauert das aufstarten von locus viel länger.
3.38: when starting locus, the white screen showing startup progress appears immediately. scanning local maps takes a long time. especially loading .sqlitedb maps seems to take forever.
3.38.2: when starting locus, i just get a black screen for up to 10 seconds (or even longer). then i get the startup progress screen. now the .sqlitedb maps don't seem to be a problem anymore...but overall time for startup is still about the same, i.e. much longer thatn with the version before 3.38.
this cannot be shifted to any addon for sure!
tinu
at least one of the issues is not solved at all. it still persists:
- seit dem wechsel auf die neue kartenengine dauert das aufstarten von locus viel länger.
3.38: when starting locus, the white screen showing startup progress appears immediately. scanning local maps takes a long time. especially loading .sqlitedb maps seems to take forever.
3.38.2: when starting locus, i just get a black screen for up to 10 seconds (or even longer). then i get the startup progress screen. now the .sqlitedb maps don't seem to be a problem anymore...but overall time for startup is still about the same, i.e. much longer thatn with the version before 3.38.
this cannot be shifted to any addon for sure!
tinu
HI Tinu,
I've wrote to you already:
"the slow initialization - we know about it. Probably some unwanted side effect of the new map core. WIll need more analyzing, testing and developing. hopefully we'll fix it till the next production version in June."
Michal
HI Tinu,
I've wrote to you already:
"the slow initialization - we know about it. Probably some unwanted side effect of the new map core. WIll need more analyzing, testing and developing. hopefully we'll fix it till the next production version in June."
Michal
Good day Dainius,
Does this issue happen after every start of Locus Map app? What if you restart your device, is the result same?
Also what happens during these 30 seconds, you see just a black screen?
Menion
Good day Dainius,
Does this issue happen after every start of Locus Map app? What if you restart your device, is the result same?
Also what happens during these 30 seconds, you see just a black screen?
Menion
Hi, Menion
It happens every time I start program. Device restarting didn't help. During Locus map starting I see black screen
2019-06-14, pn, 22:32 Locus Map <locus.map@asamm.com> rašė:
Hi, Menion
It happens every time I start program. Device restarting didn't help. During Locus map starting I see black screen
2019-06-14, pn, 22:32 Locus Map <locus.map@asamm.com> rašė:
Good day Dainius and Pavel,
sorry to hear it. I'm a little worried that this won't have a simple solution for now. Write to me please also what devices are you using and if you have default or any alternative ROM installed. Thank you.
Good day Dainius and Pavel,
sorry to hear it. I'm a little worried that this won't have a simple solution for now. Write to me please also what devices are you using and if you have default or any alternative ROM installed. Thank you.
hi michal
after locus updated to 3.38.4 yesterday, startup behaviour got even worse.
now, when starting locus, i first get a black screen for more than 1 minute until the startup screen opens.
then, showing the startup screen again takes 1 minute or more until locus is operational.
regards
tinu
hi michal
after locus updated to 3.38.4 yesterday, startup behaviour got even worse.
now, when starting locus, i first get a black screen for more than 1 minute until the startup screen opens.
then, showing the startup screen again takes 1 minute or more until locus is operational.
regards
tinu
just to add some more info:
i see this issue (2 minutes or more to start) on a samsung s5.
i thought this might be better on a newer cubot x18 so i also tested on this device.
on a first start, it was exactly the same as with the s5 (more than 2 minutes). then, later on, i still have 1 minute of black screen, but then it immediately shows the map and no locus startup screen.
just to add some more info:
i see this issue (2 minutes or more to start) on a samsung s5.
i thought this might be better on a newer cubot x18 so i also tested on this device.
on a first start, it was exactly the same as with the s5 (more than 2 minutes). then, later on, i still have 1 minute of black screen, but then it immediately shows the map and no locus startup screen.
Damn this is almost impossible. There is nothing Locus Map can do at start so long.
May anyone from your simply restart device, wait a minute till everything starts and then start Locus Map. If the issue happens again, immediately after app start, create a log by this method. Please rather check how to do a bug report before you will need it, to be ready right after app starts. Thank you and really sorry for this unexpected problem!
Menion
Damn this is almost impossible. There is nothing Locus Map can do at start so long.
May anyone from your simply restart device, wait a minute till everything starts and then start Locus Map. If the issue happens again, immediately after app start, create a log by this method. Please rather check how to do a bug report before you will need it, to be ready right after app starts. Thank you and really sorry for this unexpected problem!
Menion
hi menion
i sent you the bug reports from both devices by email. hope they came through...
for no known reason, this time startup was much faster...but still took quite long.
black screen was almost 1 minute, but then i didn't get the locus startup page. instead, locus was ready immediately. then.
regards tinu
hi menion
i sent you the bug reports from both devices by email. hope they came through...
for no known reason, this time startup was much faster...but still took quite long.
black screen was almost 1 minute, but then i didn't get the locus startup page. instead, locus was ready immediately. then.
regards tinu
i tried to revert to 3.37.2, but when trying to install this version over the actual locus, it did not install (no error message, just the info that it did not install).
do i have to do something special to revert to 3.37.2?
i think uninstalling the actual version first would be a bad idea as this would also delete all the data. right?
and btw: did the logs i sent you show anything special?
i tried to revert to 3.37.2, but when trying to install this version over the actual locus, it did not install (no error message, just the info that it did not install).
do i have to do something special to revert to 3.37.2?
i think uninstalling the actual version first would be a bad idea as this would also delete all the data. right?
and btw: did the logs i sent you show anything special?
I just updated Locus Maps Pro to the latest version from Google Maps on a Samsung Galaxy S2 with Version 7.0. When starting the app, it remains on a black screen for MINUTES or even longer until the message appears: Locus Map reagiert nicht (doesn't react). Continuing with wait stays further on black screen. Currently Locus Maps is near to unusable on my Tablet. 5 or more minutes later Initialisation starts and again hangs at 20% for several minutes to start Offline Maps. It seems to me, that LMP produces tons of error messages, which I saw on screen, but can not interpret and clicked away (Fehler: Unbekanntes Problem, wxWidget , HTML, ... Please help. I have urgend need of LMP for my next Trip to France on Friday !!!
I just updated Locus Maps Pro to the latest version from Google Maps on a Samsung Galaxy S2 with Version 7.0. When starting the app, it remains on a black screen for MINUTES or even longer until the message appears: Locus Map reagiert nicht (doesn't react). Continuing with wait stays further on black screen. Currently Locus Maps is near to unusable on my Tablet. 5 or more minutes later Initialisation starts and again hangs at 20% for several minutes to start Offline Maps. It seems to me, that LMP produces tons of error messages, which I saw on screen, but can not interpret and clicked away (Fehler: Unbekanntes Problem, wxWidget , HTML, ... Please help. I have urgend need of LMP for my next Trip to France on Friday !!!
I now have created a bugreport-2019-06-19-09-02-25.zip, which is available for you on my google drive. please check your emails!
I now have created a bugreport-2019-06-19-09-02-25.zip, which is available for you on my google drive. please check your emails!
Good day bongo & Guenther
thank you both for your logs. I clearly see that app starts and after a while, it just hangs for a minute, two and nothing happen even in device seems that nothing serious happens. I have unfortunately no idea, no clue why this happens on your two devices.
In the case of Guenther, I see a huge list of errors at start. In your case it is most probably because of added directory "storage/0000-0000/Computer/Programmierung/Python/wxPython/" into external maps, it is possible? There seem to be many files that end with ".map" ending which Locus Map test and then report that it's invalid map format. Anyway, it may not cause so huge delay.
May someone of you give a try and make a clean Locus Map install?
For this, best is to do
The app will after start create a new empty directory, which you may simply remove if the test will fail and rename old directory back.
Does it make any difference?
Good day bongo & Guenther
thank you both for your logs. I clearly see that app starts and after a while, it just hangs for a minute, two and nothing happen even in device seems that nothing serious happens. I have unfortunately no idea, no clue why this happens on your two devices.
In the case of Guenther, I see a huge list of errors at start. In your case it is most probably because of added directory "storage/0000-0000/Computer/Programmierung/Python/wxPython/" into external maps, it is possible? There seem to be many files that end with ".map" ending which Locus Map test and then report that it's invalid map format. Anyway, it may not cause so huge delay.
May someone of you give a try and make a clean Locus Map install?
For this, best is to do
The app will after start create a new empty directory, which you may simply remove if the test will fail and rename old directory back.
Does it make any difference?
I have no idea how Locus Map happened to use this directory for default of vector maps. I indeed use an additional directory (0000-0000/mMyLocusExternMaps/ for my maps and this always worked fine and now after reinstallation again. Anyway, I did a clean installation which is now version 3. 38.4 And now start-up time is okay with short time black screen and very fast installation screen. Because of no backup I have lost tracks and waypoints, but that's not really a problem because they can be reimported easily.
Although on my smart phone Samsung Galaxy S5 it seems to me that Locus Maps does not complete initialization. After opening the main screen it permanently shows "Initialisierung ..." (Initialization) in the title bar, although functions are available, and Locus Maps seems to be fully responsive. What is going on there?
Thanks for your support
I have no idea how Locus Map happened to use this directory for default of vector maps. I indeed use an additional directory (0000-0000/mMyLocusExternMaps/ for my maps and this always worked fine and now after reinstallation again. Anyway, I did a clean installation which is now version 3. 38.4 And now start-up time is okay with short time black screen and very fast installation screen. Because of no backup I have lost tracks and waypoints, but that's not really a problem because they can be reimported easily.
Although on my smart phone Samsung Galaxy S5 it seems to me that Locus Maps does not complete initialization. After opening the main screen it permanently shows "Initialisierung ..." (Initialization) in the title bar, although functions are available, and Locus Maps seems to be fully responsive. What is going on there?
Thanks for your support
hi menion
have you also seen anything special in my logs?
and btw:
i'm still waiting for advice on how to revert to 3.37.2 which failed (see my post from 5h ago).
so this would hopefully help me out of these problems.
thanx!
hi menion
have you also seen anything special in my logs?
and btw:
i'm still waiting for advice on how to revert to 3.37.2 which failed (see my post from 5h ago).
so this would hopefully help me out of these problems.
thanx!
Hello guys,
thanks to bongo's precise testing, I believe I have found a reason for this slowdown. Even before the main map screen is visible, Locus Map test if there are any new maps. For this, it checks the content of every directory and subdirectory of "mapsVector" (or custom) directory. I know that Android SD card API is slow, but did not expect that THIS SLOW. I was able to simulate issue on own device and also with some caching, reduce this time to 10%. So in my case from 15 secs to 1.5 sec. Not best, but definitely a lot better. Fix will be included in next bug-fix version 3.38.7 (most probably in the second half of this week).
Thank you for the patience and help with this issue.
One note: because of weird limitations on SD card access since Android 5+, and even that Locus Map supports some data on SD card, I may only highly recommend placing everything into internal memory. Speed benefits (not just the start of the app) are usually noticeable.
Hello guys,
thanks to bongo's precise testing, I believe I have found a reason for this slowdown. Even before the main map screen is visible, Locus Map test if there are any new maps. For this, it checks the content of every directory and subdirectory of "mapsVector" (or custom) directory. I know that Android SD card API is slow, but did not expect that THIS SLOW. I was able to simulate issue on own device and also with some caching, reduce this time to 10%. So in my case from 15 secs to 1.5 sec. Not best, but definitely a lot better. Fix will be included in next bug-fix version 3.38.7 (most probably in the second half of this week).
Thank you for the patience and help with this issue.
One note: because of weird limitations on SD card access since Android 5+, and even that Locus Map supports some data on SD card, I may only highly recommend placing everything into internal memory. Speed benefits (not just the start of the app) are usually noticeable.
@Menion
How do you access SD card contents over SAF?
Don't use any list methods because each entry will create a seperate file detail request.If you have more then 10 files you need to directly query them.
I could reduce file listening of only 60 files form 1.5s to 0.1s on an S4 mini by using
Uri treeUrl = DocumentsContract.buildChildDocumentsUriUsingTree(mFolderUri, DocumentsContract.getTreeDocumentId(mFolderUri));
getContentResolver().query(treeUrl, fields, null, null, null, null));
instead of
DocumentFile folder = DocumentFile.fromTreeUri(this, mFolderUri);
folder.listFiles()
Please check if you do use listFiles() anywhere, because this is one example of painfull slow types of using storage access framework. I'm still shocked from that listFiles() experience.
After that, I don't trust any DocumentFile methods without checking how they performe with 5-10 files. It's just ridiculous how many CPU cycles get wasted with such low numbers of files.
For example getting mimetypes from DocumentFile is equally worse. I just guess that each method call is translated to a SAF query...
@Menion
How do you access SD card contents over SAF?
Don't use any list methods because each entry will create a seperate file detail request.If you have more then 10 files you need to directly query them.
I could reduce file listening of only 60 files form 1.5s to 0.1s on an S4 mini by using
Uri treeUrl = DocumentsContract.buildChildDocumentsUriUsingTree(mFolderUri, DocumentsContract.getTreeDocumentId(mFolderUri));
getContentResolver().query(treeUrl, fields, null, null, null, null));
instead of
DocumentFile folder = DocumentFile.fromTreeUri(this, mFolderUri);
folder.listFiles()
Please check if you do use listFiles() anywhere, because this is one example of painfull slow types of using storage access framework. I'm still shocked from that listFiles() experience.
After that, I don't trust any DocumentFile methods without checking how they performe with 5-10 files. It's just ridiculous how many CPU cycles get wasted with such low numbers of files.
For example getting mimetypes from DocumentFile is equally worse. I just guess that each method call is translated to a SAF query...
Replies have been locked on this page!