Messages

when a map download leaves un uncomplete sql, you get this error on next locus start. its a bit unreadable on dark mode. also, you will never get rid of it unless you delete the file in a file explorer... or find the map downloader again in locus, which can be quite hard. maybe a delete/continue option right in this error window would be nice.

I have a super weird problem since Galaxy 20 FE. I always run display at maximum brightness. Quite often , the phone is in a state where everything is super bright, but as soon as Locus comes to front, the display is dimmed to quite dark. Not via settings mind you, all is still set on maximum. Display is dark anyway, as though the phone "fears" overheating.

This *only* happens when Locus is in front. Other screens are still bright until the phone gets really hot. Then everything goes dark.

It seems as if Android "anticipates" Locus to behave badly and dims in advance.

Regarding overlays... it really feels more like a render problem than a cache problem. Like... the overlay goes away immediately when I just zoom out a tiny bit, and then this tile never really wants to appear again. Or at least it needs a lot of "convincing" with multiple zooms and scrolls and godknowswhat.

Sorry for the weird description, it feels as random as it sounds

Regarding the caching issue with Strava Heat map. Everything seems properly enabled. Didn't change anything from Locus Pro anyway and there it worked nicely iirc. The pic says something 5.0MB cache size btw, which seems way too low. Is this current or max or default and where does this value come from and how can I affect it?

I use log tap to start guiding because it just feels right. I see a place on the map, I tap it, I go there. No extra menu bars to be opened before. Also... wouldn't all your other methods add a point to my database first? I don't want that, I just want to have an arrow to the next place, telling me how far to climb. And then again. And again. And again... I call it "dynamic ghetto navigation" and it makes total sense to people who make up their mind on where to go along the way. Not much of a planner I must admit... .

Anyway, it felt much better and snappier on today's trip. Maybe you fixed it... or maybe I wasn't in gsm-land long enough.

Locus still says it's recording in notifications even though it isn't. Also, the color is weirdly blue. Running dark mode. Not running Locus as service.

Btw, the new syncing things will do nothing to help reselling/planning with a buddy, right? Or am I missing something here?

I am still dreaming of a day where I can add a point to my Locus and it would simply popup on my buddy's screen right away, without further crap involved. Online... offline... in 5g-land or at night by a campfire in Bolivia 300 miles away from the next cell tower. None of that must matter.

Locus displays inclination percentage besides altitude difference underneath guide line now. It's not particularly useful in real mountains I suppose because there are always switchbacks, but maybe it's good for other purposes... like flying... or really flat mountains with straight paths. Problem is however, that text is very long now and hidden completely if it doesn't fit. I suggest not hiding it but simply clipping instead, so we could still see altitude difference. Alternatively, make percentage value turnoffable.

Something is fishy with online overlay maps, they dont seem to be properly cached anymore. I use a hack for strava bike heat map from a slow russian server and it keeps disappearing on almost every zoom in Locus. Sucks a little, because the server is really slow :-).

I move to a certain location, wait a little, after some tens of seconds, the overlays appears. Then I move around and zoom in an out to different placesy but when I get back to the exact same location and zoom level of the first time, the overlay is gone and I need to wait again. Certainly it should be cached?

I remember Locus Pro caching online overlays maps basically forever. Especially with a heat map, the zoom level doesnt even matter much.

Code Select Expand

<provider id="8888049" type="0" visible="true" background="-1">
<name>Overlay</name>
<mode>Strava Heatmap - Ride (Bluered)</mode>
<countries>World</countries>
<usage>overlay</usage>
<url><![CDATA[https://anygis.ru/server/Tracks_Strava_Ride_Bluered_HD/{x}/{y}/{z}?locusScale={ts}]]></url>
<serverPart></serverPart>
<zoomPart>{z}-8</zoomPart>
<zoomMin>8</zoomMin>    <!-- 0 -->
<zoomMax>23</zoomMax>   <!-- 15 -->
<tileSize>256</tileSize>
<tileScale dpi="0" multi="2.0" replace="19" />
<extraHeader><![CDATA[Referer#https://www.strava.com/heatmap]]></extraHeader>
<extraHeader><![CDATA[User-Agent#Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36]]></extraHeader>
<attribution><![CDATA[Сборник карт AnyGIS. <a href="https://anygis.ru/Web/Html/Locus">Проверить обновления</a>]]></attribution>
</provider>


Now even Androids problem solver thinks, Locus does "frequent crashes" . No idea what that means, but maybe it helps a little for debugging. This is with the previous beta though.

On average, I have about one crash per day while I'm using the app and about two forced quits per day (Locus disappears while track recording when the display is off and the phone is not in use).

The forced quits happended with Locus Pro as well. I still suspect my database size and Samsungs aggressive killing strategies... even though I tried hard to disable all that nonsense. It's hidden all over system settings and they make it harder to deal with ever day it seems.

Beta 911: Guiding line text stays a lot more visible now. Point popup already feels more snappy on a slow-wifi-couch. Real tests will have to wait until gsm/edge-land higher up the mountain.

Long tap is a "difficult" gesture anyway, especially with sweaty fingers in bright sunlight on a moving bicycle. If Locus makes it even harder by not reacting immediately and predictably, it becomes annoying very quickly. I might even suggest some kind of vibration and/or audible feedback here, but I guess Locus has no concept for that yet.

What I primarily use long tapping for is adding new points in general and also setting a guide line to the next point I need to reach. I do this about 20 to 30 times a day. Don't plan ahead much and fool around at every new trail junction before making up my mind.

Having the text at destination only really doesn't make much sense to me. Shouldn't it be centered between where the arrow enters the screen (or begins) and leaves the screen (or ends)?

The distance to guiding destination text above/below the arrow became quite invisible mostly. Can you fix it so that it's always visible at a proper place, regardless of where I am zoomed to? It's really the only tool I use for navigating in mountains, everything else is mostly too cumbersome.

Had Locus crash out in the wilds, but cannot tell what I did.

Happens to me too... if only Betas would write crash logs and ask us to enail them to menion automatically on next Locus start. I am usually sweaty and in bright hot sunshine and sitting on my bike with a 150 heart rate and in a bad mood anyway because Locus died/disappeared and the last X minutes track weren't recorded. That's a bad state of mind and general situation for complex debugging steps... :-).

I meanwhile suspect Samsung/OneUI3/Androud11 to aggresively kill Apps with high memory usage btw when running in background, maybe that's the reason Locus disappears silently at least twice a day for me. Does a huge database mean too much memory usage as well?

Betas unfortunately still fail miserably with long tap point window address search. All is fine when network is good, all is fine when phone is offline. All hell breaks lose when phone thinks it's online but network is bad. The point window either doesn't appear at all, or appears after a second... or 5 seconds... or 30. Absolutely horrible usability, user never knows what's going on. This thingy must always(!) show up and work after exactly [longtapdelay] milliseconds, no matter what messy state the network is in.

I really wish I could jinx your phone to edge-only and 50% packet loss for a week, menion... Locus would instantly start to become a lot nicer in the real world... outside gbit-wifi and 5g :-).

Route planners points and lines are invisible here as well. But adding new POIs on main app is much better now .