Messages

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)

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?

a few days ago, locus map pro updated to 3.56.4
since then, when starting locus, i get a white screen with the locus symbol for about 20s, while nothing seems to happen.
after that, i get the ususal screen with the percentage counting up, which takes one more 15s.
so the total start time now increased to 35s.

before updating to 3.56.4, i didn't have this 20s period showing nothing but the locus symbol, i.e. it directly started with the page showing the percentage.

what is locus doing while letting me wait for another 20s (introduced with the last update)?
can this be avoided?

btw:
since updated to 3.56.1, i need to run locus from the external flash card (with some issues reported in another post), but waiting for the additional 20s on startup was not recognized before 3.56.4.

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)

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

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!

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.

and here the screenshot when using a vector map and zooming out

i always used the "auto-load maps of identical type only" option and this was working fine for me.
unfortunately, a few weeks or month ago, i had issues that when using a vector map (openandromap), i had stripes in it coming from raster maps also covering the displaied area. when zooming, i always got the vector map first, and after about 1 second, i either got the stripes on it or it was completely replaced by the raster map.
after switching to "no map auto-load", i'm at least able to use vector maps as long as i fully zoom in. but when zooming out, although if i have the setting "no map auto-load", it seems to merge data from several maps, producing unusable bullshit (see attachment).
maybe i just don't understand the map selection strategy of locus and i need to rearrange the maps in the folders (then please let me know how to correctly arrange the maps).
btw: i cannot see a difference between the settings for "auto-load maps of identical type only" and "auto-load maps of any type". with both settings, when changing zoom level, it randomly changes between vector maps, any raster maps and aerial photos without giving me any control on what to use.
what i really miss here is a setting which allows me to select a subfolder in the maps or mapsvector folder and then, locus only uses maps stored within this folder.

yes, but i cannot fully compare. the former setup with A10 was:
gsak db with old gsak for locus addon (version 2.2.3 or so) and all html (with folder structure) in internal memory.
with this setup, it always took a few seconds to open waypoints from gsak db together with it's html.
for g4l waypoints, i think there was almost no delay.

the intermediate solution with A11 was:
gsak db and html (all html in 1 folder) still internal but new gsak for locus addon. this setup immediately opened both types of waypoint, no matter if from gsak (opened together with html) or from g4l (without html).

now, because there is no more quick way to store the html in internal memory, my A11 setup ist:
gsak db internal, html external (all in 1 folder). waypoints loaded from gsak for locus addon open quite quick (together with html). waypoints loaded from g4l (which do not have a html) may load quick or may take quite some time to open. no idea on what it depends.

i'm a bit surprised that this seems to work, at least so far...
on the external sd card, under /locus, i had the two map folders so far.
there i added the folder /locus/data/geocaching and copied the two subfolders html and images to this geocaching folder by inserting the flash card in the pc.
so now back in the phone, i reconfigured the geocaching folder and now, the spoiler tab occures and the html files are shown as this was befor when having the whole thing in the internal locus folder.
so i really hope this persists and does not just work for a first test ;-)

there is just 1 small issue:
all above is done with the waypoints taken from a gsak db using the "gsak für locus" addon, and there is a html for each of those waypoints.
when i move the map further away to a location not covered by the gsak db and then enable geocaching4locus to show live map waypoints, then on opening a waypoint, this may really take a long time to open after loading. sometimes it opens after a few seconds, sometimes i first get a black screen for about half a minute until the waypoint opens in locus.
does my setting of the geocaching folder have any impact to waypoints loaded from geocaching4locus?

hi menion
as having a structure instead of having all files within the same folder is no longer a real advantage (is no longer required as the days of fat32 are gone), i would for sure be able to adapt my scripts to change this.
but anyway, it's no more really possible to copy the files then to the android device in an acceptable time because of another android 11 issue (mentioned in the other thread).
so there's actually no pressure from my side to solve this as there are other android issues to be solved first.
but if it's really helpful for you to have a big set of html files in a structure, please let me know. then i can generate it for you.

hi menion

the reason for updating so many files is that they are generated from gsak. so no matter if there are changes, when you export a set of waypoints, a new html is generated. so this is then replaced on the android phone.
and besides this, when exporting a new html from gsak, all the images referenced by the html are exported too, but they are renamed on export. so after each export, all images get a new name.
therefore, there's always the whole bunch of files to be replaced...

as a workaround, i thought about having the geocaching folder on the external flash. so this would allow me to copy the data directly on a pc when i remove the flash card from the android phone.
the first test failed, as after switching the geocaching folder to the ext flash, i was no longer able to start locus. all i got was a black screen and locus failed to start.
in the mean time, i recognized that the behaviour changes, depending on the path to the folder configured for the htmls. i.e. the path configured in locus. this applies for internal and external memory. e.g.:
having the htmls under
/sdcard/locus/data/geocaching/html -> works
but
/sdcard/locus/data/geocaching/geocaching_html/html -> fails
no matter if configure the geocaching folder to
/sdcard/locus/data/geocaching
or
/sdcard/locus/data/geocaching/geocaching_html

so maybe the issue i had with the external flash (with the no longer starting locus) might have to do with this...so i'll do some more tests...but this will take time...

for showing details on saved waypoints (may be up to about 50k), i use html files saved under locus/data/geocaching, each one with the name of the waypoint.
in addition, there are many pictures, which are linked from these html files.

so far, this seemed to be a very smart solution, as replacing the whole bunch of those files on my android 10 device could be done in below 1 hour.

now, after updating to android 11, all file operations seem to be slowed down a lot. so this whole process takes up to hours...days...

even if transferring all those files to the device as a single zip (which can be done in a few minutes) and storing the zip in internal memory, unpacking the zip then (to internal memory) takes hours again:
so first the folder with the old files needs to be deleted (looks like this takes about 6h for 30000 files, is still ongoing), and then unzipping the new ones again takes a few hours.

the reason for this very long processing time seems to be that android 11 adds a fixed amount of time for handling each file. so it would be great to have an alternative way of storing the data shown under the "spoiler" tab, which does not base on so many individual files. this would probably be the only way to work around this new android issue which could probably only be solved by google.

so finally my question is:
what are the criteria for data to be shown under the "spoiler" tab?
does this really need to be "one html file per waypoint" with a name, exactly the same as the waypoint name?
or are there alternatives?
- does locus accept some compressed format?
- are only html files acceppted or does locus accept other formats?
- is it possible to have several waypoints grouped in the same file?
- can locus access several files under one waypoint (which would allow to separate html and images and access them individually)
- anything else?

any idea to works around this android 11 disaster is welcome...

looks like i'm a step forward now.
file and folder operations seem to be extremely slow with android 11, even if only internal memory is used.
so far, i had my html files and images spread over a folder structure to work around limitations from older file systems (e.g. 65k limit of fat32).
so this seems to be the reason now for the non-working waypoint access in locus.
when i copy all html files to a single folder under locus/data/geocaching instead of having a folder structure, locus can open them in about no time.
so this really seems to be a workaround for this issue ;-)

unfortunately, this brings me to a next issue which i will bring up in an another thread.