Messages

@Milan:
I got another idea/request:
Right now, the map displayed is the exact same as on the phone. So any zoom factor is also used on the phone. That's not so great, as I change the phone's zoom factor with my presets, e.g. having higher zoopm for biking because the phone's further away. But the watch is always more or less same distance.
So it would be much better, if the phone had its own zoom factor. Would that be possible?

Oh, one more question:
What GPS is the app using? The one in the phone or is everything just being transmitted from the connected phone?

Well, alternatively (but probably more complicated) would be to include a Widget that displays the dashboard data and a tap leads you to the map. Just dreaming... 

Hi again
I now bought the Galaxy Watch anyway. Switching phones is in fact reasonably doable when using Samsung backup. Of course, app settings are not restored (including Health data, which is ok when using Samsung Health on the phone, too), but the important stuff like watchface, widgets and app order are. So I'll do that for longer trips with another phone, and for shorter ones, I'll just go without connection (don't need mail notifications on a hike, anyway). [that's nonsense, of course, as Locus won't work then - so either do the reset-switch-cycle or go w/o Locus on watch]

Apart from that, I find the Locus app very nice, but I agree with others before that the recording mode should have a map page, too. Going back to map and then back to the dashboard again is just the kind of annoying actions that you don't want to do on a trip (back button - tap the small icon and then again). Please consider, as proposed before, to add a zoomable, non-movable map screen as part of the dashboard. Thx!

@milan:
Thx a lot for your answer. Unfortunately, that pretty much disqualifies more or less any Tizen watch for me. I have a phone for everyday, one for mountain sports, and one for travels. While a reset would perhaps be just about acceptable for a longer holiday, it certainly isn't for a weekend hike.
In case anyone's interested: With Android Wear, it's at least possible to switch phones without factory reset: https://www.xda-developers.com/pair-android-wear-without-factory-reset
I can only hope that Samsung realizes sometime in the future that that's a good thing...
Well, now I'll check for Android Wear watches...

I was so far on the fence about Smartwatches, missing the real killer application, especially on Tizen - to me, the Samsung devices always seemed to have the best hardware and now with Gear S3 and Galaxy Watch also the best looks.
Now with Locus for Tizen, that killer application might have come. But I have a few questions left, perhaps somebody can answer those?

• What are the differences between Tizen and Android Wear add-ons? The Wear add-on is older, so does it also have more features?
• Are database points and tracks shown on the map, too? Can I tap on points for further information? Or is it just a static map image?
• Can I connect the watch to different phones, and if so, is this also no problem for Locus? Admittedly, this is more a general question, but I could also imagine that the watch app stores available recording profiles, which might differ on different phones.

Thanx for your help !

I think I reported problems with the automatic backup before, but it's still not ok:
I have several devices where backup is turned off, but it is still executed. It's always when I have Free and Pro installed together. One thing that seems to happen very often is that a backup is done after a phone restart even if turned off. I can't give much more info, unfortunately, as I rarely see the actual backup notification, I just see the backups piling up in their folder.
Also, the GUI is still buggy: The date shown ("Next update") is obviously the last "next date" before I turned of backups. Now when I open the dialog after that date, I can't press "Save" because of the old date, even if backups are turned off. The whole date widget should be deactivated then, I'd say...

I thought there was already a thread for this, but couldn't find it, definitely not recently, so I'll start a new one:
What phones you own have the best GPS quality (with Locus)?
I'm especially interested in experiences of people with several phones.
I personally have owned a bunch of Samsung Galaxys over the years - but surprisingly enough, my cheap Moto G5 has not only the best precision (although not necessarily better than the newer Samsungs), but combine that with the best battery performance by far! In flight mode, I can easily record for 6hrs and still have around 50% battery left. I'm actually not sad that my most expensive phone (Galaxy S9) is much worse in this regard, as I prefer to take another phone outdoors anyway, but it's still weird.
What are your experiences?

Vote here: http://help.locusmap.eu/topic/cloud_map_and_data_storage_sync

Not sure if this is new:
On my tab, I got Pro and Beta installed. For both, I turned off Automatic Backups (aside: On the "Edit" dialog, it says "Next backup 10 May 2018", but that should be empty, if auto backups is off).
Still, everytime I boot the tab, both versions create a backup (complete with the "Backup in progress" notification).

Understand, I'll look at it. We thought a while about some inner logic where only single notification will be visible with the most important information, but ... what is most important when navigation, track recording and live tracking are running at once? Best to allow enable/disable then separately over app settings, agree.

Yes, thx.
Just one additional comment: The thing about the "Guidance" notification, as you can see in the screenshot, is that it doesn't hold any information. It's obviously purely functional. It didn't try Navigation, perhaps that notification holds more information like the next change of direction; but guidance is kinda useless.
Anyway, it's necessary for Android, but if you put it in a different category, anybody can disable it if annoyed by it

Ah finally understand.
Yes, what you see is the result of changes on Android 8. Track recording may be stopped independently on Navigation/guidance so I should rather stick with both notifications active at once, thanks for understanding.

Yes, understand - but can't you define different notification categories for them? That way, the user can hide the ones that are not needed. That shouldn't be a biggie?!

[@slart76]

@slart76
what means "Guidance" notification? Maybe a screenshot + describe better what you hear. By "Track recording" notification you mean announcements from "Audio coach" right?

Sorry, nothing audio at all. Just talking about notifications in the notification area of Android.
Attached screenshot.

I'm not sure how new this is, but when having a navigation running, I now get a "Guidance" notification, at least on Oreo. Which I assume is due to background running restrictions - so that's fine.
However, when also recording a track, there are now two notifications! I'm pretty sure, that for ensuring background running, one would be enough?!
Unfortunately, they both have the same category ("Ongoing notifications"), so I can't turn off the guidance notification without also hiding the recording notification (which I absolutely need).
So would it make sense to automatically hide the guidance not. when there is a recording running, or at least put them into different categories so the user can decide? (which however is only possible on Oreo, granted)

1. In presets, Orientation Lock option is not preserved if I generate a new preset. I have to tap the pencil icon, make the option available, and then the setting is copied from existing state.

I think that's a bigger (and not new) problem: A new preset only ever contains a fixed set of settings, as far as I can see. So for all settings not in there, you first have to select them in the Edit dialog.
My proposal:
1) Initially activate all possible settings
2) Make copying presets possible - that way you can boil your presets down to the settings you actually want to change. I know that you can manually copy a preset by copying the .lb file in data/presets and renaming it. Never tried it though, not sure if that works (naming could be a problem) - so an in-app solution would be better.