Messages

Long tap on map content to toggle last two maps is nice! A little problem though: I believe when Locus restarts and maybe also when I select a new overlay map, you forget the previously used map and replace it with the overlay map. That doesn't make much sense, I never want the overlay to move into one of the toggle spots.

Switching between maps is something I do very frequently on the trail, most of the time toggling between OSM and a satellite map. I believe this is a very frequent operation in Locus, especially now that you have these gorgeous satellite maps in Gold without google hacks. Anyway, map changing has become a bit of a cumbersome multi-tap operation recently: tap on the map icon, tap on the current map name (feels a bit illogical here), find new map in the list, tap on new map name. One could probably put the quick map change function in a toolbar, but that doesn't make the tap orgy less complex really.

How about using a long tap on the map icon (currently unused) to toggle between the previously selected map and the current one? That would make things super-easy and fast if all you need is two maps, like OSM and Satellite.

[@joeloc]

@joeloc

Heat map > sorry, but it works quite slow and when I spend a little more time on this, I do not see any clear problem. Because it is not an official app map and because no other (official) map does not have any similar issues, I won't spend time on this.

Understood. Would you maybe consider putting the (multiple?) max_timeout and max_failure_count variables into config.cfg then? That way we could still download from slow servers... even if runs 12 hours overnight.

Right now, slow server download is simply impossible with Locus. Nobody wants to watch his phone and click retry every 3 minutes.

Ps, Strava Heatmap might be lagging and from Russia, but it nevertheless is *the* *most* *valuable* overlay for mountainbiking today, not just some funny idea of mine :-).

See Attachments for the add point crash, happens 100% when clicking Speichern. Point "Auto" is already in the db in the same folder. Adding points with other names is no problem.

Locus crashes and quits hard when I click on one of the POIs in the attached image. I believe those are online POIs or some such, at least their not my own points and they don't appear when I'm offline.

N28.1614 W17.2680 Map is latest CanaryIslands from openandromaps.

On Android 11 (at least Samsung Variant), when an app asks for Location Permission after first install, you can only allow "while app is being used". This will prevent Locus from recording a track when the display is off, for example. You have to actively enter Android Settings and enable "always" for the location permission.

It would be nice if Locus could check the state of this permission when a user starts track recording and open those settings for him in case they are wrong. Otherwise users will not be able to properly record tracks unless they keep display on and Locus in front.

The track that is currently being recorded fails to refresh properly when display was off for a while. Only after repeated zoom operations will it appear on the map again.

Latest Beta finally fixed the superlaggy Track Editor when deleting/editing points. It's orders of magnitudes faster now, minutes of waiting time turned to split seconds, no matter how huge the database.

Also, laggy list scrolling in track lists with plenty images in their description tags is fixed. Mini maps in track list still don't seem to be updated and mostly stay empty though. Shouldn't that happen automatically? What map data is used for that anyway, something online maybe?

Zooming in general with plenty points and lots of enabled tracks (tenthousands of trackpoints) seems way faster too. Zooming other regions of the map (where the enabled tracks aren't visible), is orders of magnitude quicker, as if no tracks were enabled at all. Impressive.

In fact, Locus feels so snappy now that I might consider trying to enable all my tracks of all my trips at the same time. This idea would make current Pro from Playstore cry for mercy and pretty much die in notime. Maybe this beta could handle it...

Good job with the performance... really! I'm impressed.

Database size is indeed the issue with editing performance. I deleted mine and imported a single track only: Editing points is super fast, like it should be.

Editing the same points of the same track in a 1GB-Database: Locus spends a full minute on confirmation. Nothing else(!) in the huge database is enabled. I mean... what the heck is going on here? Why do totally unrelated and non-enabled parts in the database slow down any edits to an unimaginable crawl?!

No idea on your SQL stuff really, but that simply cannot be right. Do you maybe run a weird "sql commit" and "compact database" on every single operation?

I really wish there were more power users out there so these things couldn't be ignored for years and years and more years. With a few hundred tracks only, you will never notice anything odd on a fast phone. Obviously, editing tracks will consume orders of magnitude more battery this way. But since people usually edit at home, that won't matter either.

Ps, menion, I PMed you a link to a huge database if you want to check. Couldn't find a recent email address, sorry.

My database is 1.4GB. I still can't see how this would affect changing/deleting a single point of a single track so badly, but I know nothing of SQL, let alone its Android implementations. What I do know though, is that if your tracks where simply a doubly linked list like in the good old days of C programming, Locus would likely be orders of magnitude faster :-). And if Locus used GL or Vulcan or whatever it is these days in Android, I could enable 30.000 tracks instead to 30 and still be 60fps.instead of 1fps on zooming :-))

Only very few of my tracks and points are enabled at any one time. I'd love to see more, but unfortunately Locus also gets unbearably slow on startup and zooming then.

I'll upload my zipped database somewhere and email you a link, menion... if you want to give it a try.