This object is in archive! 

Minor problem downloading openandromaps theme

c.s.g. shared this problem 4 years ago
Closed

Hi,

i have a minor problem downloading openandromap Elevate theme direct within Locus. I. e.:

If I click the "Locus"-Button on OAM download page on my Galaxy Note 4 running Android 6.0.1 Stock ROM and Locus Pro 3.40.2 I can download the newest Elevate theme for OAM via Locus without any problems. The "theme"-folder is configurated in Locus to folder "/extLocus/mapsVector/_themes/" on external sd card and Locus is able to update the subfolder "Elevate" on external sd card.

But if I try the same with my Galaxy S4 running LineageOS 16 12.1, i. e. Android 9, with same configuration and folder structure on external sd card as the Galaxy Note 4, I get an error message within the Locus download and installing dialog "zip file elevate" is empty.

Is this a Locus or OAM problem?

It is not really a big problem for me. I can download the corresponding zip file direct from OAM homepage and do the installation manually as I did for years now.

c.s.g.

Replies (8)

photo
1

Maybe related - while testing locus actions I realized that the changed downloaded and installed zip files were not updated, while they were on the server. Are they somehow cached locally? That would explain c.s.g.'s case, too, if there was a download error, but the cached file is not removed.

photo
1

Hi guys,

interesting idea Tobias, but should not be.

The process is that app downloads data into a defined target directory. Content is extracted (if defined to do so) and it is also possible that downloaded file is deleted, but again: only when requested (after set to deleteSource). Otherwise, the downloaded theme remains in the downloaded directory, but most probably all is correctly set on OAM side right?

I remember, we had reported same "zip file empty" problem some time ago, mainly with downloading HGT files over the app, but I was never able to figure out the real reason.

@c.s.g. , right after you get this error message, may you check mapsVector/_themes directory, if there is downloaded OAM theme and if so, is file correct or is it really empty?

photo
1

The locus action file contains deleteSource, I hope this is correct:

https://www.openandromaps.org/wp-content/users/tobias/Elevate.xml

photo
1

Hi Menion,

there is only a Elevate-icons.zip in folder "/extLocus/mapsVector/_themes/" on external sd card with the ccurrent date-timestamp of download but an Elevate.zip is missing.

"/Locus/mapsVector/_themes/" on internal sd card only contains a .nomedia file.

c.s.g.

photo
1

Tobias, it looks perfectly valid!

Thanks c.s.g. for the test.

We discuss here two (from my point of view) different, problems. The problem with "empty zip file" is as I wrote, something I already saw before. Hard to solve when on original ROM, this works correctly (on my devices as well). LineAgeOS is nice, anyway still used by a minor portion of users.

The problem with not-overwriting old themes is weird as well. Tobias, does it happen always? Best how to try it is to create two locus-actions pointing on the two versions of a single theme and try to download them, right? Do you have such files/themes for test? If not, I may ask Petr to prepare me some ... thanks.

photo
1

"empty zip file" problem is really not a big problem for me. So far I always installed the zip file manually.

Because the internal contents of OAM elevate theme zip file has changed essential from version 4.3.2 to version 4.3.3.1 I want Locus doing the job of installlation the theme this time to be sure everything works as expected..

But I found out, that Locus can test the correct installation of themes and says everything is ok with the OAM elevate theme, even when I install it manually.

So, again, really not a big problem for me.

c.s.g.

photo
1

While trying to reproduce my issue I found the culprit:

It's not Locus, but my file explorer in Android. Solid Explorer doesn't update the preview images in Android when I tried to check if the changed icons are updated (that's where I had the issue).

Sorry for bothering!

photo
1

Ah fine :). No problem, glad that at least half of reported issues are solved :).

@c.s.g. thanks for the additional info. In this case, if you do not mind, I'll close this ticket. It is something I'm aware that rarely on some devices happens, but I was never able to track real reason. And to be true, can't imagine how to solve it now. Thanks for understanding and thanks for the bug-repot!

Menion

Replies have been locked on this page!