Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - slarti76

#331
Another thing:
See the attached screenshot. An obviously unrealistic hiking time estimation: The profile says "600 Vm/h" downwards, but the whole track with 640m descent and even 80m ascent should be done in less than half an hour?! I know these calculations are rough at best, but that is sooo off...
#332
Weird "Process successful" toast
Yesterday, I went biking, but had Locus recording the track, but mostly running in the background (yes, I was sometimes playing Pokémon Go...). Which was running fine, but every few minutes, there was a green "Process successful" toast popping up. I'm pretty sure it's a Locus toast, had the exact look and text that I know from open Locus. But there was no user interaction for which a toast was warranted. Everything was running fine.
I have no idea what could have caused that (saving track part perhaps?).
If I'm right and it was Locus, I think Locus shouldn't do toasts while in background, especially not if everything's fine. Another thing would be an error, but at least there should be more information what actually happened...
#333
Something else:
May I ask about the Cloud Map/Data Storage/Sync?
Topic https://help.locusmap.eu/topic/cloud_map_and_data_storage_sync is locked, but that's 14 months ago... Is that part of LM4 or postponed because of that?
Thx for your answer!
#334
I'm not really sure what got improved about the two-finger measuring?!
The distance is still not better highlighted (eg. with a different background) and it's possible to get it hidden by the magnifier. See screenshot
#335
Quote from: slarti76 on April 05, 2020, 17:36:22
But when I use the Navigation menu and add Via Points?! I mean, that's not intuitive, I'm sure everyone who adds a Via Point in the Navigation dialog expect Locus to always keep this Via Points. I mean, it's just like car navigation: I want to reach my hotel for the night, but on the way visit some sights. I don't want my navigation to skip sights because at some point the hotel is closer than the next sight.
Update: I tried to recreate the problem, and couldn't! I have no idea what went wrong Saturday morning, I definitely tried several times, but now when I start navigation with Via Points, all is fine!

So, please just ignore me ;)
Ok, I'll just ask that one question again:
Is there a way to get up the list of Via Point used for the Navigation again or, once it started, they're gone? Thx and sorry for that...
#336
Quote from: menion on April 05, 2020, 11:10:52
Navigation problems:
- what you describe in the first paragraph: Locus works correctly.
"Point priority" search for next defined "Via point", which most probably was your destination. To have real via-points, you need a "blue rectangle" in route planner ( https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning#add_via_points ).
For the round trips, I highly recommend "Route priority", that tries to stick you on the planned route.

EDIT: ah, just correctly commented by @pountikl, thanks!
Ok, I do get it when I planned the route with the route planner. I will also try to remember to use Route Priority for this usecase next time.
But when I use the Navigation menu and add Via Points?! I mean, that's not intuitive, I'm sure everyone who adds a Via Point in the Navigation dialog expect Locus to always keep this Via Points. I mean, it's just like car navigation: I want to reach my hotel for the night, but on the way visit some sights. I don't want my navigation to skip sights because at some point the hotel is closer than the next sight.

QuotePaused track recording
Never ever happen to me, do not know. Anyway Locus itself definitely does nothing like this. Isn't there any tasker you use for example that may do this? In case of any battery optimization when the system kill Locus completely, navigation will stop.
Yeah, that's what I thought.
Anyway, I have to admit that I'm using Tasker, so it might have been some of my automatics there running wild. I will just keep an eye on it, whether it happens again. For now, ignore me ;)

QuoteAdditional question:
If you planned route in Route planner, you may simply open Route planner over specific route > context menu > Route planner. If you use "Navigate to" function, then exactly what you need is not possible, good point.
Ok, good to know.
Still, just to reiterate: Route Planner was only my desperate alternative attempt, because the Navigation Dialog didn't give me a usable result.
#337
Navigation with Via points problems

I did a bike roundtrip around a lake today. Locus 3.44.3 (beta not installed on that phone). I wanted to use Locus navigation, so at the starting point, I opened navigation, chose 3 via points to get me nicely around the lake, started navigation. Route looked good, but only for a few seconds, then suddenly it was only a few meters from here to the destination point. Obviously Locus recalculated and forgot the via points!
I checked the settings, got "Point priority" turned on.
Next I tried to plan the route in the Route Planner first, saved it, right-clicked on it and chose "Navigation". Same behaviour: Looks good for a few seconds, then Locus recalculated and the route was gone.

Another thing that happened during the trip:
Several times Locus just suddenly paused my recording! I couldn't see any obvious reason for it. Granted, another app was in foreground, but I did this many times before and never was a problem. Battery saving is off for Locus (and anyway, Locus was still running, just the recording paused).
Only thing that was different is that navigation was running, too (usually, when navigating, I have Locus in foreground). Perhaps a recalculation caused Locus to paused recording?

Edit: Additional Question:
Is there a way to, after starting the navigation, get to the list of via points again? Or start a new navigation with the same via points? I might be overlooking something, or that is part of the navigation improvements planned for LM4?
#338
Quote from: menion on March 22, 2020, 09:53:16
@slarti76
missing section: hmm good observation. It seems to be a problem not directly in my code. I'll have to do something with it, thanks.
Confirmed working in latest beta.Just a tiny thing: At the bottom, a section "Various" is always shown, even if there are no icons. As far as i remember, this section, this was for icons that didn't have their own section.
#339
Another thing, which I still think is a bug:
In the store, when I choose "Check for Updates", it will show me for which maps there are updates. However, this is only based on whether I bought the updates, not if my maps are up-to-date.
I have several phones, so when there are new LoMaps out, on one phone it will show me the updates. Then I buy the updates and download them, but on the other phones "Check for updates" doesn't show them anymore. Yes, I bought them now, but the maps on those phones are not updated, so I think they should be displayed there, too.
#340
In the icon selection dialog, there it's possible to order the icons into section with a special file in the ZIP. I know that because I once redid the icon collection in the store (Menion, perhaps you remember).
Today I noticed that the sections are still there, but the section titles are gone. Don't know since when, but definitely in 3.44.2. Is there a reason or is that a bug?
#341
Quote from: menion on February 26, 2020, 10:42:44
@slarti76
thanks, I got it. Bug-fix version is just in preparation ....
Confirmed, thx!
#342
Dunno if that's new in 3.44.0, but I can't add waypoints to existing tracks in my database any more. When clicking the "+" button I get the input dialog, but after "Save" (or is it "OK"?), nothing happened, the list of waypoints is still empty. Tried with several tracks, doesn't seem to be related to something specific.
#343
Quote from: menion on February 14, 2020, 13:12:21
Thanks balloni. It works for you correctly?
The great advantage is that in case you use the app mainly in the landscape, you may have full top bar with buttons, no matter, how long is it, if you use a tablet or tiny old small phone, etc.
Hi Menion
It's an improvement, sure, but I still would've liked to see a years-old proposal of mine: Different icon setups for portrait and landscape. I don't find the flowing very useful, because for example I always have specific icon in the upper right. However, e.g. I can have separate points and tracks icons in landscape, but the combined points/tracks icon in portrait. And so on...
Any chance for that?
#344
Quote from: menion on January 13, 2020, 13:05:42
This init dialog is visible only when it's needed. It may be during the first run in case, you have any (for the app) unknown maps or later in the case, there is a lot of points/tracks that need to be loaded on the map.
Cannot really be the reason. As I said, I can reproduce the lag every time. Can't say if it's new in this very release, but I'm sure the problem is "newish" - I was on a longer holiday in Nov/Dec and don't remember anything like that. Didn't update during that time, to be on the safe side, so can't say which version I used all the time.
#345
Quote from: menion on January 13, 2020, 12:02:58
@slarti76
I can't imagine it display sooner. G5 is not so old so 10 seconds is way too much. The same delay is in all other app starts or just for the first time? Weird, anyway really can't imagine why this happens and how to speed up. In the first moment, Locus notice that UI is visible, it displays loading dialog.
Tried it again after closing Locus with swipe from the task switcher:

  • Blank screen with centered Locus icon for like 2s.
  • Locus UI with all buttons and blank map for 10s
  • Map appears, Locus is usable
This time, the "Initializing" dialog didn't appear at all, but that seems to be normal if Locus wasn't killed completely. I tried to, but in the "App info", the "Force Stop" button is greyed out.
When I close Locus with Double-Back from within the app, startup is much faster, no blank map.
Still, didn't see the Initializing dialog again since I updated. Would probably appear again after a reboot, I assume.