data stored in the data/geocaching folder crashes locus (after update to 3.56.1)

[bongo]

today, my device (a galaxy a50) updated to locus 3.56.1.
so i was forced to select new folders.
so far, i had locus in the internal memory, while maps, vector maps and geocaches were on the external sd card.
selecting internal flash as new main folder was not possible due to a lack of space, so i selected the external flash.
a few hours later, vector maps were copied and  most things were probably located in the private folder on the sd card.
as raster maps were not moved, i had to do this manually. also the geocaching folder was only partially moved, so i also moved this data to the new location.
now, locus seems to work again as long as i do not try to open a waypoint.
as soon as i do so, no matter if it came to the map from either geocaching4locus or from the gsak-addon, i get a black screen for some time and then, locus terminates.
when i rename the geocaching folder so that locus does not recognize it anymore, opening a waypoint works, but for sure i'm no longer able to see all my added data for the waypoint then.
so long, i had a few 1000 files in the geocaching folder and this worked fine, but since today's update to 3.56.1, i can no longer use files from the geocaching folder.

[michaelbechtold]

While we have no measurements yet from Menion, I sense that data updates on external SD private foldrs (in /Android/data) are a bit messy and slow.
As Locus does not (yet - Menion, this is a real life scenario, not only for bongp!!) allow to select detailed locations for the migration process, I would always advise to rename the mass data folders like mapsVector and maps, so Locus cannot find them. But do it from PC via USB, and make sure you can write to ext SD /Android/data (some phones do not work properly here), just to be sure you have the rights to the final steps.
Then a migration to internal SD should fly.
Now select ext SD card folders for maps and mapsVector and SRTM inside Locus settings. They would be empty most probably now.
Then, from PC MOVE the mass data you have put aside earlier to the new private /Android/data structure.
Maybe it would be even best to copy them to PC, then put them on the private ext SD folder, because I fear that a move via USB from PC may not be just a move, but a simultaneous download and upload via USB - I have never seen this fly in a stable way.

[bongo]

so does this mean that i still can have the folders
    maps
    vectormaps
    data/geocaching
on the external sd card, while having the rest of locus in the internal flash memory?
this is not clear for me so far.
from the migration process, i assume that i either need to have all data in the private locus folder under android in the internal memory (which is not big enough in my case), or in the private locus folder under android on the external sd card.
please clarify!
thanx a lot for your help!

[michaelbechtold]

What I can confirm is:
- maps and mapsVector on ext SD
- ALL of data on intSD
- even maps and mapsVector on int SD are used, but not for new downloads
- I cannot comment on the geocaching; I would assume you cannot mix /data components between int and ext

[Menion]

Hello bongo,
sorry for the trouble! The copy took a few hours? Uff.

There should be no problem using the app completely from the SD card, so problems with the geocaching folder are really weird. Or, as Michael wrote, have core app directory in the internal memory and maps on the SD card. This is anyway not a major problem here.

When you open any waypoint, you see a black screen. May you please let it be for a minute or two? You should probably see "Application is not responding" dialog, so just click "Wait". Does the point appear?

May you also send me please your "User ID" from the "About app" screen? I'll first look if there isn't any automatically reported error, thanks.

[bongo]

hi menion
with my original installation, i had locus in the internal memory, and maps, vectormaps and data/geocaching on the external sd card.
within data/geocaching, i had about 13000 html files and 17000 images.
opening a geocache always took a few (2 to 10s) seconds. switching between tabs within a waypoint view was possible without noticable delay.
now, having it all on the external sd card still works fine, as long as the data/geocaching folder is empty.
having all the html and images in the folder, shows a black screen for up to 2 minutes before opening a waypoint (need to press on "wait" several times).
then, once the waypoint has opened, it takes about 10s to switch between the tabs.
and in addition to that, when waiting for the screen to turn off, it often happens that locus is no longer running when reactivating the screen (seems to have crashed) and needs to be restarted.
android also reports that the app uses a lot of energy in the background (which was never indicated before).
just for a test, i moved away the images from the data/geocaching folder to only have the 13000 html in.
unfortunately, this did not seem to help in any way ;-(
my id is 6e6562c63

[bongo]

and just a question to get a folder setup similar to what i had before:
is there a way to have the data/geocaching folder on the external sd while having locus installed internally?
haven't seen this option in the settings, but maybe this would help (as this is the setup i had before the update)

[bongo]

are there any plans to allow having the data/geocaching folder on the external flash card while running locus in the internal memory (separate folder configuration for data/geocaching)?

or is there already a workaround to do so?

[Menion]

Hi bongo, I've not yet found time to do this, but a) it is doable and b) there is currently no method how to do it other than code it directly in the app.

Will try to implement it to the next app version.

[Sonny]

Just for info, there's also thread regarding this idea at:
https://help.locusmap.eu/topic/26813-custom-sub-directory-datageocaching

[bongo]

great to hear - thanx!
hope this will also solve the issue, where locus crashes whenever i have data in the geocaching folder, since i had to move whole locus to the ext sd card (with update 3.56.1)

[bongo]

thanx for the implementation of having a separate setting for the geocaching folder.
so now i am able to have a setup similar to what i had before updating to 3.56.1:
- main folder internal
- maps, mapsVector, geocaching external
so i can go on with testing...

unfortunately, updating to 3.56.5 does not seem to help concerning the crash reported for 3.56.1. behaviour is still:
- opening a waypoint takes 90-120s (if it works). often locus crashes while opening a waypoint and has to be restarted.
- once a waypoint is open, switching between the tabs of a waypoint takes about 10s
i really wonder what's going in the background making the device that slow...as at least, once a waypoint is open, i cannot see what locus could do taking that much time to switch between tabs.

my actual file structure under the geocaching folder is:
- 100 files (most of them html) directy within geocaching
-  a html subfolder with 13000 html files in
-  a image subfolder containing about 1000 subfolders holding a total of about 19000 jpg images

as already tested with 3.56.1, removing all the images as well as the appropriate folders does not help.

before updating to 3.56.1, i had the same folder structure. at this time opening a waypoint took a few seconds and switching between tabs took about no time.

as soon as i delete the content of the geocaching folder, everything works fine again...but this is not really what i like to do ;-(

[bongo]

i did a few more tests with having only few files under data/geocaching.

with 1000 html files, located directly under data/geocaching on the external sd card:
- opening the waypoint belonging to a html file, which is the first file in the geocaching folder (in alphabetical order) took a few seconds to open, switching between tabs works fine.
- opening any other waypoint shows a black or white screen and takes forever. had to terminate locus after a few minutes as it seemed to be dead.

with only 80 html files, located directly under data/geocaching on the external sd card:
- opening the waypoint belonging to a html file which is the first one in the geocaching folder (in alphabetical order) took about no time to open, switching between tabs works fine.
- opening another waypoint which belongs to a html file took about no time to open, switching between tabs works fine
- opening a waypoint which HAS NO HTML FILE IN THE GEOCACHING FOLDER took about 40seconds TO OPEN, SWITCHING BETWEEN TABS takes about 5seconds

so this latest of the tests above looks to me a bit like: locus has a problem if there are files in the geocaching folder but there is no file found for the actual waypoint yet.

i hope this is helpful for further investigations...

[Menion]

Hello bongo,

this is maybe the third topic from you with an almost identical problem = slow "something", when placed on the SD card. Isn't your SD card really really slow? Isn't corrupted somehow?

Isn't for you easy to pack your geocaching directory and share it with me over some Google Drive or similar service? Because it may take me a month to download such a huge amount of files and it may be useful to have it for tests on my device.

For your info: the point & track screen is in the Locus Map Pro really slow. I know it well and because of it, in the new Locus Map 4 was created completely new from scratch. Definitelly a lot faster.

[bongo]

hi menion

sorry for reporting things getting slow again and again!

unfortunately, the getting slow issues always start with a locus update, so it really looks like they have something to do with the new locus version.

i already thought about having a problem with the sd card. it's a samsung evo+, so i would expect it to be not that slow. but to be on the secure side, i ordered a new one 2 days ago to make sure that the issues have nothing to do with the sd card.

i will generate an example geocaching folder for you within the next few days. to what email address can i then send the link to (i don't like to post it in a forum)?

btw: what screen is called point & track?