Messages

Hi,
Any feedback?

No stress...only 3 days have passed. At the moment there are few in the forum. If you have an urgent question, next time create a ticket in the helpdesk. There you have a guarantee of an answer....not here.
https://help.locusmap.eu/

ok, I see, many thanks.  Actually I was about to ask their difference. Thanks again! Merry Christmas.

Menion, I was wondering:
You're not the first to suffer under Google restrictions. I know quite some apps that offer a "Google-impaired" version on Google Play, and another without those restriction on their website.
I mean, I'm not an expert on Android development, but if I remember correctly, you can request any Android right from the user if the app is sideloaded. So you could tell the user: "Play version only allows to store map and other extra data in internal app dir. If you need to access data stored anywhere on your system, please install the version from the website (sideload): <link here>".
Wouldn't that be a compromise to appease Google and the power users at the same time?

[New version 4.5.5 is available on the Google Play]

New version 4.5.5 is available on the Google Play.

Change in the A11+ file-system > check app settings > Misc > File manager and enjoy it . And please, do not forget to keep in mind (we will be writing it everywhere) > we have a temporary exception!! from the Google team. Temporary for how long? No one knows. So we have to prepare, it will end one day ...



Locus Map Pro is currently in the verification process ... we'll see how things go ...

I am not sure. I think, after moving "maps" to the external storage the map in "Preload global map" wasn't configured any more.

Here I zoom from the global map into some random area, which is not cached. Hillshading is on and I use Sonnys 24mb hgt files. SRTM on ext sd (those are "NM" cards on Huawei). Map is OAM V5, Device is Mate20X.
I don't think it was faster on int sd. Definitely alright for me.
https://youtu.be/e0dnk8q71Gk

[@freischneider]

@freischneider
SRTM data needs fast access when you use hill-shading. Anyway, truth is that HGT files that are currently used should be cached in memory, so it should be slow only for this first-time app to use it. I'll have to do some benchmarks, but if you do not feel any difference when using hill-shading, no worry, and use it directly from the SD card.

@michaelbechtold
thanks for the summary and help with this complicated topic! The current state is definitely not a final version. We will be updating also based on the problems and support on the help desk!

Difference in performance > as mentioned in second topic - it will need some benchmark to verify the real impact on battery and performance.

"Is it then possible to divide app and data over private directories in internal memory and SD card" - not yet. If there will be bigger interest, I may work on it and this is definitely a doable task.

1000% supported! I have very big non-vector maps (OruxMaps format) on extSd, which won't fit on intSd, but also don't want to take the performance hit to database operations on extSd.
I don't want to spend lifetime getting angry at Google for this change, we few people won't be able to change it. And I don't really care about the actual paths to data (I would care about inability to share this data, but I don't need that, so I'm fine). But if there's any way to make use of the data on int and ext SD at the same time, that would be a big improvement! I would probably wait with updating Locus if you now tell us, you'll tackle this... Thx for considering!

Terminology is really confusing here.  "Internal storage" vs "Internal memory" in the Set Working Directory dialog.  "Internal" vs "External" in this discussion, but both seem to be inside the phone somewhere.  Those who know that one is removable and called "SD" would be confused by an "Internal" option being /sdcard/Locus, which (I think) is in non-removable memory despite the "sdcard" name.  I think only an Android developer could understand all this.

Here's the chance to be clear and non-confusing.  And if there's no need to worry because you're on Android 10 or lower, then please say so in the UI.  Thank you.

After all, users will choose between internal/external SD. The precise place is something they not necessarily need to know. Locus UI could simply offer a matrix which let's the user pick the desired place with radio buttons (so, pick int or ext sd) for vector maps, srtm, whatever else... And it should manage the file movements in a secure way.
I don't like the move towards apple, where people even don't need to be aware of files and folders. But otoh, bullshit apps, malware, messing with other apps, idk, most people have just a glimpse of clue and need to be protected 😐

To be honest, I would rather not rely on SD card with its "ability" to handle database fast random read/writing, its stability etc. Not long ago I lost all my data on an SD card due to its malfunction and the necessity of formatting.

I appreciate your twofold warning, Michal!

Question to Menion:
I saw that many apps have a /Android/data folder on external SD, BUT their working directory in fact is on internal storage.
Are you able to access BOTH of them simultaneously? E.g. SRTM and large maps on external SD, while databases and other essential objects with high performance and reliability needs are kept on the internal /Android/data storage.

An Presets binden? Seit einiger Zeit speichern Presets ja auch die Detaileinstellungen von Themes. So mache ich das. Die eigentliche Theme-Auswahl nutze ich selten.

I don't think navigation by track is bad. I personally use her in winter hiking. I have a phone in my pocket and turn instructions to hear in headphones.
Navigation from the route scheduler is fine too. But I have a bicycle ride like such a wandering for attractions. When I take me something along the way, I turn me there and I'll be back on the route until I fucks it. Often, I also keep a group of cyclists and each of them has their needs or interests. If I had all attractions to include in the route, it would kill me a lot of time spent at the mobile. And that's tired of me. LOCUS routing profiles do not suit me and use their own. So I still use http://brouter.de/brouter-Web with a profile from the pilgrim. So it is better for me to ride by line. In addition, for navigation, it bothers the turn off. When I'm going through the city, I better have the screen onto the screen. Mostly I use Zoom in town and Zoom.
Lately, I often ride only according to a very simple line without a map at Garmin 130, which I use Due to the Garmin Varia radar.
This will not miss the distance to your destination. Although I would like it to work as before, but it's not very important. I'm just responding to a colleague Wlashack.
But thank you for your advice

CZ:
Nemyslím si, že je navigace podle stopy špatná. Osobně ji často používám při zimní turistice. Telefon mám v kapse a pokyny k odbočení slyším ve sluchátkách.
Navigace z plánovače tras je taky v pořádku. Já ale jízdu na kole mám spíš jako takové toulání po zajímavostech. Když mě něco po cestě zaujme, tak tam odbočím a na trasu se vrátím až se mi to hodí. Často taky vedu skupinu cyklistů a každý z nich má své potřeby či zájmy. Kdybych měl všechny zajímavosti zahrnout do trasy, zabralo by mi to mnoho času stráveného u mobilu. A to mě nebaví. Routovací profily na webu Locus mi nevyhovují a vlastní tam použít nejdou. Takže stále používám http://brouter.de/brouter-web s profilem od Poutníka. Je pro mě tedy lepší jezdit jen podle linky. U navigace mi navíc vadí to zhasínání. Když jedu městem, raději mám obrazovku stále rozsvícenou. Většinou používám ve městě i zámek zoomu.
V poslední době taky často jezdím jen podle velmi jednoduché linky bez mapy u Garmin 130, který používám kvůli radaru Garmin Varia.
To zobrazení vzdálenosti do cíle mi až tak moc nechybí. Byl bych sice rád, kdyby to fungovalo jako dříve, ale není to moc důležité. Reagoval jsem jen na dotaz kolegy Wlashacka.

as michaelbechtold said, create a suggestion topic

All geo App developers should unite and kickk Google's ass.
Now all of them - and their customers and users are suffering separately.

Unacceptable.

Maybe the export option "Overwrite files" is usually not turned on. Of course there is workarounds, one gpx would work, but the problem is a nasty one, people may not realize the loss of data.

Locus says "Exported 1600 tracks" and user may not notice there is just 1300 files. People may rely on re-import (personally I've done that often) and then have silently lost tracks.

The track name is just not unique. I think Locus should populate a list of export file names beforehand. Then resolve collisions before writing files. Add indexes maybe on collisions. It's really bad that it overwrites files which it has created in the same export run. I'm sorry, I always put stuff on your monstrous pile of work. 😁

User id 1aacaff2a2, I will try to find the cause of import crash, maybe find limits... EDIT: Not yet found a cause. Happens pretty much at ~1004 import files.

...
But it doesn't provide the possibility to download the gpx, right?  It just shows route on map?
Did I missed this Feature?
...

I thing you missed it. When I select a track or any other route, the context menu offers a "share as gpx". The tools available then depend on the staging of your smartphone (apps).

In the App the share gpx can download the gpx and you can send it to friends somehow

I talked about the share in the Web. This will create a url you can send to your friends. If you open that url you see the track on the map. I see no way to download a gpx. That's what I mean.

Sharing the track via URL is a nice modern way but today the possibilities with such a link is very limited. If would be nice if adding gpx download doesnt make much work.