Messages

[Android/media]

@Menion, please take note! Message from C. Ghisler, tcmd dev.

https://ghisler.ch/board/viewtopic.php?p=407841#p407841

Try asking the author to use Android/media on the SD card instead of Android/data. The app should be able to access this folder without special rights, and other apps can write there just fine.

Maps in the media folder - that would be awesome. Well, not awesome compared to pre-A11 behaviour - one might ask what's the point for Google to enforce all these changes, when there's still a folder that can be accessed freely? -, but still. If it works, I'll take it!

PS: after that Locus will download all maps LoMaps and OAM (vector and raster for world) to the ext SD, While you control ont SD manually

Tried that now, works well.

@Menion: Perhaps you could mention that in the "Change directory" dialog, along the lines of "Even when choosing external SD as directory, data in the equivalent internal directory will still be used". No need to change functionality, just as a reassurance to "power users"...

I have the main folder on intSD, maps and mapsVector on extSD.
But I also have a few maps on the resp. intSD as well. And Locus finds them all. This gives enough flexibility.

That's interesting - I couldn't try that, because when updating, I chose the intSd as main directory. After that, changing the folder for maps or mapsVector makes Locus move the data unconditionally. How did you do it?
I guess I could first move away the maps from the intSd folder, than change the directory in Locus, then move the maps back on the intSd - is that what you did?

I just started trying it out on my tab (not ready to dare it on my outdoor phone). It works well, within the constraints, of course. I only now realized that I can't sync Locus data via SyncThing - for example, I synced my Locus/data/media folder like that, but SyncThing doesn't accept Android/data/xxx as source. Thank you Google! 

Anyway, one more question about the storage space change:
You offer to switch between internal and external SD for specific directories. However, would it be possible to use both, at least for maps? Or is that prohibited by Google, too? I do have a lot of maps, currently the most used on intSd, the others on extSd. Of course it would all fit on extSd, but especially the OruxMaps format (database) are faster from intSd. So it would be great if there's a way to use both at the same time. You don't even have to provide an organizing tool, at least not urgently - I can move the data without problems by attaching the MicroSD to my Windows machine. So no changes in the UI, there's still the "main" directory for maps and mapsVector, just also use the data from the not-selected directory if there is any. Possible?

Did anybody try things with a rooted phone? I assume there every directory should be accessible?!

You are right, Tapio. But a lot of flexibility is lost, isn't it? It is no longer very pleasant.

If I have to decide between performance and still-being-able-to-use-all-my-maps, that's much more than "flexibility". For the first time since I'm active in Locus testing-and-giving-feedback, this could be a make-or-break-moment for me. My outdoor phone (XCover Pro) is neither the fastest nor has the most internal memory. I'm not gonna use my "good" phone for outdoor stuff, so I'm not gonna say it's a no-go, will have to see how it performs, but I'm really anxious...

Menion,
[snip]

I really have to agree with Michael here. I have no problem to open a Help Desc topic, that's not the point. But this is too slow for this important topic. I have friends for whom I am the "Locus guru", but who would never take the time to log in on the help desk or whatever. And they all have big maps on extSd that they can't move to internal.
And I'm still not even sure from the Manual entry: Does Locus even offer to move all data to extSd instead of intSd on first start with new version? The manual is not explicit on this. I'm honestly not willing to try out Beta this time (even though I always do), because this is obviously a one way street. I would be ok if you say "Google forces my hand, for now you'll just have to do it, and you can move to extSd, but next I will implement way to divide big and small data between intSd and extSd". But making this dependent on a lengthy voting process is very disappointing - and potentially p***ing off many users. As Michael says, don't underestimate the amount of users with cheap phones with small internal SD, slapping a big MicroSD into the slot...

I also stumbled over one sentence in the docs (under "What if I refuse"):
"you can load the original data any time from the app main menu or from settings > miscellaneous > default directory"
I honestly don't understand that - what does "load" mean in this context? Do you mean I can start the copying of the old (original) data at a later time? However, the sentence more sounds like "you can start Locus without copying the data and then change the default directory at runtime and have access to the old data again".
Anyway, this should be worded more clearly.

"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!

Can totally find no rule behind it. Not related to straight lines here mostly. Looked through my "Planned" folder, there's 80 tracks, seems like maybe 1/3 lost their shaping points, leaving just 3 shaping points AFAICS.

Same here. I also experience lost shaping points sometimes, but fail to see a pattern...

As for Pause (no movement) detection.

@tapio I'm hoping internal accelerometer will be used some time in the future for "no movement detection". Far more reliable than current GPS location method. Plenty of apps already use this for an "alarm". As far as I can tell, some Garmin GPS have used this method for a long time. Fellow riders with Garmin GPS beep nearly instantly they stop, whereas the Locus track can show constantly moving position +/-7m.

Yes, current "pause detection" is very unreliable depending on GPS quality and settings. Accelerometer would save us from a lot of "track wildly jumping around the same position" when making a pause...

So I guess an option to add Waypoints like "Pause @ {t}: mm:ss" shouldn't be too far away.

+1 nice idea - add a Help suggestion for voting?

+1

Or minimize # of trackpoints...

Secretly hoping for that for ages...

I just tried out the new "naming preset" for recordings. The preview obviously uses my current location, which renders to "Zurich (Zürich)". As I'm not going somewhere else in the next few days: What is in the parentheses? If it's the (Swiss) canton/state/subdivision: Please remove that, there's rarely a need and it makes the name very long. If it's English + Local language: Either decide on one or offer additional variants. I don't think it's needed in more than a few cases where both differ very much.

I like the new Distance Markers, but disagree with removing the unit. Now they look like tram or metro line numbers. I really liked Josef's proposal with a big number and the unit small in a second line. That looked nicely like a milestone. Please consider...

[@slarti76]

https://forum.locusmap.eu/index.php?topic=7438.msg64586#msg64586:

@slarti76
Also a problem, I'm unable to simulate it. You test it on the "Galaxy Tab" right?

Changelog 4.3.2.1:

Missing point/track screen bottom buttons on tablets

Looks like you were able to simulate it, no? Anyway, I can confirm it working fine now. Thx!