On 20.04.24 00:17, Tom Crocker wrote:
>
>
> On Fri, 1 Mar 2024, 13:10 'Martin Trautmann' via OsmAnd,
> <[email protected] <mailto:[email protected]>> wrote:
>
>
> So what I would like is any mechanism to make osmand faster again - e.g.
>
> ...
>
> * I could mark certain maps as currently inactive - there are several
> contries where I do not want to use the bandwith to delete and download
> the data again and again, although I won't go there within the next 12
> months.
>
> I can't tell from what you've written if you know you can mark certain
> maps as inactive/ reactivate them as necessary? I have several dozen
> maps deactivated and only a couple active. It does make a surprising
> difference.
I wonder whether my system is completely messed up by now, due to the
changes of Googles memory policy.
For a few days now osmand always asks me on startup about its storage place.
At the moment it's on multiuser space 2 which names a path of
/storage/82A1-7ABC/Android/obb/net.osmand.plus
It's just a guess that this might be the "SD-Card".
The file managers that I checked no longer have access to these folders.
So I re-installed the typical maps which I actually need - and those now
are used again.
However, when I check for my local maps, all the other maps are still
shown. They are all marked with green, claiming to be the most recent
version, although all the old ones are from 1.12.2023 while the actual
new ones are from 01.04.2024
The map info does not show me where those maps actually are. I have the
icons
1) box with dropdown, telling me zero of one files have been deactivated
2) refresh spin arrows, do not work
3) edit pencil, does not work
4) upload from box, which asks me for the file manager
5) trash
So the maps are there, but are not there. I guess I'll walk through all
of them and trash them manually. But when I try, osmand tells me "zero
of one files have been deleted".
I feel it's not only Google's memory concept that was flawed by a
protection that I actually do not want, but also by osmands failure to
provide a useful migration policy and a now corrupted memory concept.
I wonder where else I still have dumps of former map storage locations
since those were created once and now are not longer accessible, while
they still are found by some other way.
Deactivation of maps should be done within osmand automatically, in
order to use only the most relevant maps within <100 km distance for a
reasonable startup speed.
I guess I should tell the system setup to delete all of osmand directly.
Is there any other way to clean up that mess?
I do not even understand the difference of "standard maps" vs "sources":
Standardkarten: 21.2 GB
Quellen: 33.84 GB
How can I save and export my own data (tracks, favorits etc.) before I
tell the system to remove all osmand data?
--
You received this message because you are subscribed to the Google Groups
"OsmAnd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/osmand/d04f8da0-1547-4fcc-aac2-6825df21a8ee%40gmx.de.
