Locus Map - forum

New Locus Map (4) version

Important links
- list of news (https://help.locusmap.eu/announcement/locus-map-version-4-18-2-8-2023) of public versions
- Public versions (http://bit.ly/lmVersions)
- Beta versions (http://bit.ly/lmVersionsTest)

Versions
2. 8. 2023 - Locus 4.18.0
4. 8. 2023 - Locus 4.18.1
15. 8. 2023 - Locus 4.18.2

Sharing with G-Maps does not work. I select a store, restaurant in Maps. In the opened POI I then go to Share, there I select Locus.
The whole thing is now passed to Locus in the search and this finds nothing.
If I make a long click on the map in Maps, a red poi is created. If I go there to Share and select Locus, a Locus is created at this point a temporary point.

I can confirm this.
However, if you use Google Maps in the browser, it works.

Sharing of my own created "red push pin" from GMaps to LM4 now works - thanks! But sharing of existing GMaps POI doesn't work/ has different behavior to 4.17. Now LM4 Search will display the shared link as text, for example https://maps.app.goo.gl/zmQaPsNkSRVfqtDn6, and display "No search results" rather than moving to that point. When I open this example URL in my web browser, it displays the correct POI.

Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.

Or you had a different experience with Locus Map 4.16-?

Hello,
"add: option to hide all other tracks except the currently active one"
useful, but a little too hidden in the track menu under tools, an icon on the track info header would be better.

Be aware that if you use my attached icon you have to pay me the rights  ;D

Quote from: Menion on August 03, 2023, 08:11:37Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.

What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

Router Source online

• with Google I always get a request-error
• with graphhopper I get this error when end-point is not set at street but at building. Moving it slightly by some meters all is fine. So solvable if you are aware of possible troublemakers. Maybe optimisable.

Quote from: Andrew Heard on August 03, 2023, 00:56:16...But sharing of existing GMaps POI doesn't work/ has different behavior to 4.17. Now LM4 Search will display the shared link as text, for example https://maps.app.goo.gl/zmQaPsNkSRVfqtDn6, and display "No search results" rather than moving to that point. When I open this example URL in my web browser, it displays the correct POI.

I guess that is about PlaceIDs (https://developers.google.com/maps/documentation/places/web-service/place-id) and requires API-usage, if possible at all.
This can not be simply decoded or parsed like simple MapURL (https://developers.google.com/maps/documentation/urls/get-started)s with lat-lon. Currently only sharing a nearby set marking seems to be of help.

Quote from: slarti76 on August 03, 2023, 13:18:55What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

++
You may be interested in my Pluscode<->Latlon converter. Supports both types of Pluscode. Works locally, except Pluscode with city name needs a www lookup.
Intermediate Tasker users will know how to use this function. https://taskernet.com/shares/?user=AS35m8kdDIMDeveQcQfRglam%2Fah1mTW%2FWcg05FZ39c0i1q%2F77iY3E7cIwxCkXqJTaTA%3D&id=Task%3AfGPS_Pluscode
See: https://youtu.be/N5vhMGWpFs8

Quote from: Menion on August 03, 2023, 08:11:37Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.

Or you had a different experience with Locus Map 4.16-?

@Menion - strange, different to my experience, it (red push pin) had worked ~4.16, stopped working ~4.17, and is now working again. I only started using GMaps recently as a workaround for the broken LM4 online search experience which I now find frustrating. Sorry to complain, but it's just how it feels.

Quote from: slarti76 on August 03, 2023, 13:18:55What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

@slarti76 - thanks, hadn't used +codes before. Still slower (many more taps) than direct "share" of a point from my testing:

• drag POI details down a few times
• tap on "See all"
• tap on +code (very little visual feedback BTW)
• switch back to LM4
• open Search (maybe side panel button)
• paste clipboard (maybe more steps here)

Quote from: T-mo on August 03, 2023, 17:53:23I guess that is about PlaceIDs (https://developers.google.com/maps/documentation/places/web-service/place-id) and requires API-usage, if possible at all.
This can not be simply decoded or parsed like simple MapURL (https://developers.google.com/maps/documentation/urls/get-started)s with lat-lon. Currently only sharing a nearby set marking seems to be of help.

@T-mo - thanks - I guess an "ordinary" user like me doesn't know those IT details, and just "expect" that tapping the GMap Share, then selecting LM4, will seamlessly work. Unrealistic expectation I guess, but tell that to the confused user - what is the purpose of the "Share" button otherwise?

Quote from: Andrew Heard on August 04, 2023, 01:21:38but tell that to the confused user - what is the purpose of the "Share" button otherwise?

Transporting one fixed format information to another user. This cannot work for inter-app communication, with target app being an unknown entity for the sender.

Quote from: Andrew Heard on August 04, 2023, 01:17:34

Quote from: slarti76 on August 03, 2023, 13:18:55What about then at least adding support for PlusCode? That can be copied from Maps with one tap and surely be parsed by Locus search without ambiguity?!

@slarti76 - thanks, hadn't used +codes before. Still slower (many more taps) than direct "share" of a point from my testing:

• drag POI details down a few times
• tap on "See all"
• tap on +code (very little visual feedback BTW)
• switch back to LM4
• open Search (maybe side panel button)
• paste clipboard (maybe more steps here)

Yeah, agreed, but
a) if we don't have another always-working solution,
b) surely no problem with parsing (well-defined as far as I understand)
c) at least last two steps could be improved if Locus adds a PlusCode support by automatically inserting clipboard content in search field (if it parses as PlusCode).
Heck, Locus could parse the clipboard when opening the search and automatically switch to PlusCode if it parses.

Honestly, I'm a little diappointed how the missing ability to correctly share positions from Google is waved away here. Menion et al should be aware that this is an ability that is absolutely crucial for "normal" users. OSM is nice and well, but let's face it, GMaps will always be more up-to-date. Rarely anyone relies on OSM POIs alone, so we all search stuff in GMaps all the time and want to easily enter the points in Locus. This is not something to just say "hasn't been working for a while, so what?"...

Activating a dashboard.
Each tap on back button deactivating the dashboard. Intended?

@lor74cas
hidden button > yes, sorry, it will remain hidden. It is too low priority feature.

@slarti76
oki, let's try OpenLocationCodes in search in the next version. Just a warning ... Google as I see now use mostly short version of these codes so an internal geocoder needs to be used. For now. it will work only on Google-certified devices (devices with Google Play services).

Direct checking of the content of the clipboard and using it ... it is more on @Marek Scholtz. But agree, may be useful to have the result immediately as the first suggestion ...

@T-mo
Google router > it is still using by anyone :o. Have to delete this, sorry.
GraphHopper endpoint > post me here please exact coordinates of the problematic endpoint and routing type you use, thanks.

@Christian
It depends on the Dashboard setup. Open dashboard in the editor > top toolbar Settings > "Close by back button" option.

Quote from: Andrew Heard on August 04, 2023, 01:06:40

Quote from: Menion on August 03, 2023, 08:11:37Hi guys, sharing points from Google Maps does not work for years as I know. Somewhere in 2021 maybe even later, they changed the format and the information app receives can no longer be simply converted to any text or coordinates.

Or you had a different experience with Locus Map 4.16-?

@Menion - strange, different to my experience, it (red push pin) had worked ~4.16, stopped working ~4.17, and is now working again. I only started using GMaps recently as a workaround for the broken LM4 online search experience which I now find frustrating. Sorry to complain, but it's just how it feels.

More or less the same for me. Latest version of Locus did not fix anything here though, I still cannot share points from Google Maps app. All I get is a silly URL in the Locus search window.

It used to work nicely for me for a long time, likely before Locus rewrote the Search function. Or before gmaps app changed the sharing... I have no idea. All I know is that it worked for years and not it doesnt.

I also find the new Locus online search useless. It almost never gets anything I want. When I need a "bike shop", I want a list of shops at the town where my map is pointing at. Locus online search gives me mostly utter nonsense from 500 kilometers away though.

To put it mildly: Usability regarding search has gone completely southwards recently.

Good interaction with Google maps is essential on my trips. I need opening/closing times, I need the websites of stores, I need to streetview the store front to judge wether it makes sense to cycle there and look for something. Locus internal search will never be able to compete... and it should not. Google Maps is the perfect tool for that.

I think it is time for a drastic correction of approach here: whatever you do for iOS should not screw the 100000s of users from whom you make your living.
As long as the new search function is not professional, give the Android users back the Google based search.
Equal functionality is not a valid argument against this request, as the iOS version will lack essentials for years to come anyway.
At least give the existing and fully functional Google based search as an option to your (Android) users, PLEASE!

Quote from: michaelbechtold on August 04, 2023, 11:28:55whatever you do for iOS should not screw the 100000s of users from whom you make your living.

Locus on Apple/iOS??? When did I miss that? Definitely can't find it...

Transfer to other maps.

https://play.google.com/store/apps/details?id=com.donutpond.sharecoordinates

Copy & Share GPS Location / Coordinates
     ✔ copy/share/feed Map GPS location from one map (e.g. Google Map) to your favorite maps

Operation.
Search a place in Google maps > Share > Select Transfer to other map > Select Locus map.

Problem with SRTM/HGT:
I downloaded some 1" elevation data from here: http://viewfinderpanoramas.org/dem1d.html
To my surprise, suddenly the deepest canyons of our planet are in Northern Italy, and the Swiss lakes have the deepest trenches - have a look at the screenshots...

(I did clear all temp/cache data before turning on map shading again, so shoudln't be a caching artefact - also obvious from the -21753m altitude shown in att1)

Quote from: joeloc on August 04, 2023, 11:12:12I still cannot share points from Google Maps app. All I get is a silly URL in the Locus search window.

@joeloc - you express your frustration more directly than me, although precisely the same feeling. Sharing points (sorry to repeat myself yet again but):

• sharing long-tap (new) red push pin points works for me
• sharing single-tap of (existing) POI - yes, same silly URL for me too

I've made a video to be 100% clear - https://youtu.be/_jmaoGtxvqM

Quote from: 0709 on August 04, 2023, 14:46:53Transfer to other maps.
https://play.google.com/store/apps/details?id=com.donutpond.sharecoordinates

@0709 - installed - tested - wow it works - fixed the LM4 "online search silly URL" issue - thanks so much!

Quote from: slarti76 on August 05, 2023, 00:25:57Problem with SRTM/HGT:
I downloaded some 1" elevation data from here: http://viewfinderpanoramas.org/dem1d.html
...

Go for Sonny's LIDAR DTMs instead. Much better than SRTM.

I'm missing the 4.18.1 AFA on GD, Menion.

Quote from: michaelbechtold on August 05, 2023, 07:32:09I'm missing the 4.18.1 AFA on GD, Menion.

Me too ...
The link is present, but doesn't work.

OLC Search (4.18.1) failure:

HGVV+465, Lünen - not found.
should be
51.592763,7.543109

Quote from: michaelbechtold on August 05, 2023, 07:32:09I'm missing the 4.18.1 AFA on GD, Menion.

Me too.

Playstore shows new version 4.18.1 and I must take care not to update my AFA version accidentally...

Quote from: jonny.blue on August 05, 2023, 08:29:47

Quote from: michaelbechtold on August 05, 2023, 07:32:09I'm missing the 4.18.1 AFA on GD, Menion.

Me too ...
The link is present, but doesn't work.

Had the same problem on phone, but worked on PC browser *headscratch*

PC browser goes to GD folder from Aug 2nd, version 4.18.0, not 4.18.1, even on PC.
Or do you have a MAGIC link instead :-) ?

Quote from: michaelbechtold on August 05, 2023, 12:23:56PC browser goes to GD folder from Aug 2nd, version 4.18.0, not 4.18.1, even on PC.
Or do you have a MAGIC link instead :-) ?

Sorry, my bad, didn't see it's about the .1 :(

Quote from: michaelbechtold on August 05, 2023, 07:31:02

Quote from: slarti76 on August 05, 2023, 00:25:57Problem with SRTM/HGT:
I downloaded some 1" elevation data from here: http://viewfinderpanoramas.org/dem1d.html
...

Go for Sonny's LIDAR DTMs instead. Much better than SRTM.

Thx, seems to work with that. Still perhaps worth looking into whether the (other) data is buggy or Locus...

Theme selection doesn't work at all in latest version for me. Where do we need to put them? Updated Play version over AfA one accidentally.

Quote from: TrulloF on August 05, 2023, 19:17:36Theme selection doesn't work at all in latest version for me. Where do we need to put them? Updated Play version over AfA one accidentally.

Fixed it by choosing folder in app again. Moving files to android/media wasn't enough.

Ah damn, .1 version on Drive! I was releasing the version at Friday afternoon and forget on it (still a manual task). Since Saturday I`m on a small vacation, but I`ll try to connect home and upload it tomorrow. Sorry!

Hello, in the daily forecast detail panel it would be useful to have a link to the next and previous day at the bottom, avoiding having to go back to the main forecast menu each time.

Hi guys,

@freischneider @Graf Geo @Andrew Heard @Tapio @joeloc

thank you for your feedback, that at least red push pin works. Now, we have updated also POI handling to new Google Maps format and hopefully they won't change it in a month. If you encounter silly URL in search window in the next release version, check if you are on latest Google Maps version and if yes, let us know.

@joeloc @michaelbechtold

Guys, I think you already forgot that our old search definitely wasn't the same as the one available in Google Maps app/web. You describe it as it was and we ruin it with new search. In fact, that "bike shop" example was completely unusable before as it is now. I understand what could be the ideal state, and believe us, we know the importance of the search capability.

So,
1) The new search what we introduced this year is far from final. Even thanks to your feedbacks, we have clear vision what should be our next steps in order to significantly improve it. But for summer, we had to relocate our limited resources also to other tasks. We plan to get back to it during fall.
2) Yes, it is technically possible to implement Google Search/Maps API (not the one which was in app before), but if we did "just" that, it would bring several MAJOR downsides for us, not mentioning that it would still don't fully replicate search experience as on Google Maps. Some of these are for example limitation of use by only portion of our users, queries limits, inability to search our own/future content and interconnectedness with it, costs, and so on. So we anyway had to start with revamping our own search platform from the ground which will be able to get several search feeds together. What you have in the app now is its first iteration.
3) iOS is definitely not the reason why we choose this path, it is much wider than that. Remember, to find shops in the city around you, Google will always be ahead of us. We are not aiming in exactly same direction as they are. Only after we reach the point when we are unable to do improvement on top of current solution and still be too week in some search use-cases, we will merge it with another search provider to get better results.
4) Smart search MUST be able to return result >1000km far away if it might be relevant. You can already filter results to your map area. I don't consider this to be problem, I believe all issues related to this is rather that search is unable to find places what you expect to find (for example those around you). And this is matter of improving search in general. 
5) There are few main areas to work on now.
- The current implementations of POI category search and search by POIs names are too separated now
- improvements of "search dictionaries" so it will better understand what user want to get
- better data for determining POI significance.
- better work with different languages
These might have significant impact, but they will be tough to conquer, so which us luck.

@Andrew Heard
6) Topic with sharing data from Google Maps is only indirectly relevant with search capabilities. First, it is not "meant" to be used this way - it is implemented primarily for sharing data via emails/messages etc. where receiver ends up on Google Maps again. Note, that not many of other navigation apps registers this command and shows itself in such sharing dialog. Locus Map is, and we are trying to overcome this by parsing provided data and in case we can't determine its location, we throws its name to search.

But Google recently changed something and what previously partially worked now throws unusable URL to search field. Current app version didn't change anything in this and as Marek stated above, he already fixed it again for new upcoming version.

As stated above, our priority is now to get better search relevance on top of data we are working with, which might increase change you find shared location from Google Maps in Locus Map. Indeed parsing name from Google Maps might probably work better even with old Google SDK which we used in the app before. On other hand, we will have hard time to pair the result with data of POI in our DB with this approach. So the final solution to this remains to be seen, I can assure you we are aware of your feedback in this.

Quote from: slarti76 on August 04, 2023, 12:41:43Locus on Apple/iOS??? When did I miss that? Definitely can't find it...

See:
https://help.locusmap.eu/topic/32424-locus-map-lite-ios-beta-program-open-for-new-testers

I need the Afa Version and get into trouble when downloading from Google Drive.
Hitting the download button effects nothing and clicking the linktext leads to a 404 Error.

I have checked it with every browser on my phone.

https://forum.locusmap.eu/index.php?topic=8572.msg72908#msg72908

@Saturo & @Tapio
APK files are already on Google Drive since yesterday and it seems to work correctly. Which file are you unable to download? Give it a second try, thanks.

Correct. Download and installation of version 4.18.1 afa from GD works fine.
Thanks, Menion.

Quote from: Saturo on August 08, 2023, 19:39:29I need the Afa Version and get into trouble when downloading from Google Drive.
Hitting the download button effects nothing and clicking the linktext leads to a 404 Error.

I have checked it with every browser on my phone.

Same problem for me ...

Works fine (Google Drive app), I was just stupid and checked the beta folder instead of the release one.

Quote from: Marek Scholtz on August 08, 2023, 08:50:33Now, we have updated also POI handling to new Google Maps format and hopefully they won't change it in a month. If you encounter silly URL in search window in the next release version, check if you are on latest Google Maps version and if yes, let us know.

@Marek - am using LM4.18.1 with GMaps (updated just today) & still experience "silly URL in search window". But I have an excellent workaround now from @0709.

Quote from: Jan Čapek on August 08, 2023, 14:38:484) Smart search MUST be able to return result >1000km far away if it might be relevant. You can already filter results to your map area. I don't consider this to be problem

@Jan - sorry to sound like a broken record (for those old enough to remember) but why would I (as a user) want to see search results from >1000km at the expense of results I know for sure are closer? Sure, put them at the bottom of the list, but sort by distance surely? MUST?

Quote from: Jan Čapek on August 08, 2023, 14:38:486) Topic with sharing data from Google Maps is only indirectly relevant with search capabilities. First, it is not "meant" to be used this way - it is implemented primarily for sharing data via emails/messages

I only use this as a workaround. The combination of the app that @0709 suggested has really improved this method of sharing greatly.

@Andrew Heard

The fix will be available in the next version.

Hi, I've always used Locus and never had a problem. On my previous phone (Nexus, Android 8.1) it worked fine until a few days ago, I recorded a track without any problems. Having got a new phone (Edge, Android 13), I first tried updating the app on the old Nexus, and it installed this latest version (4.18.1). I did this to see if it was reading my offline maps to me, with success. So on my new phone I installed this latest version. However, I have seen that there are problems in recording tracks, it starts, but almost always it does not mark any distance, and when I stop it returns to the initial map screen without having saved any tracks. I have this problem on both phones. Anyone encountering these problems? Maybe I should do some setting to avoid this? Thank you

Addition: I tried on both devices to install an old version at home (4.14.1), it works fine on both. Evidently version 4.18 has some problems when you press stop and then go to the save track screen.

Shara

@Andrew Heard I replied to your question regarding search here:
https://forum.locusmap.eu/index.php?topic=8436.msg72936#msg72936

Quote from: Andrew Heard on August 09, 2023, 08:02:32I only use this as a workaround. The combination of the app that @0709 suggested has really improved this method of sharing greatly.

Yep, it is handy tool, but unfortunately the app isn't compatible with recent Android versions, nor is working offline.

Quote from: Graf Geo on August 08, 2023, 21:15:24Correct. Download and installation of version 4.18.1 afa from GD works fine.
Thanks, Menion.

And after reducing some security options from Chrome it works for me too. ::)

I don't really know where you want to go with your search. In any case, here are some thoughts from a power user (10 hours every single day, 300 days a year, since day one of Locus, always on the road):

You will never ever be able to compete with Google (or Apple) maps search. Period. This idea is completely delusional, even if you hire 50 more Locus programmers just for search. Here's a few reasons:

Google Maps gives me local results which are most relevant to my current situation. That works in completely foreign languages as well, where I cannot even read the alphabet. Searching for "bike shop" will show me local bike shops, in places with cyrillic writing, who might never have even heard of OpenStreetMap.

Google Maps knows if and when businesses are open.

Google Maps allows me to streetview directly into a stores front window. Very useful in judging whether it's worth taking a one hour detour in brutal heat to go there of if it's just a cheap bullshit shop with a fancy website that cannot help me anyway.

Google Maps sometimes allows me to chat to the store owner directly, including automatic translation. Yes... that is super handy in countries when you're not fluent enough for phone calls.

To be brutally honest, I wouldn't mind if you completely removed online search from Locus. It can never seriously compete with the worlds biggest players anyway, so why bother? Just make the sharing interface to Google Maps as smooth as humanly possible and concentrate on OFFLINE search in Locus... that is still a massive mess as well, leaving a lot to be desired.

For starters... why would I choose BEFOREHAND on where I want to search?! That is so completely last-millenium it's not even funny anymore :-).

When I search for "everest", I want to see
* all my tracks that contain "everest" in name or description or embedded waypoints or their description.
* all my points that contain "everest" in name or description.
* all track or point folders or groups names with "everest"
* all my custom maps that have everest in their name.
* all stuff from mapitems folder with "everest" in filename or contents (kml, gpx, anything)
* dashboards names and contents
* prefs items
* etcpp... you get idea... every(!) single(!) word(!) that locus has access to... anywhere. And you have exactly one search string that does it all. Not a dozen searches hidden all over the place.

You index all that and present the results all at once, immediately, while I'm typing. No clicking on "search" and make me wait for half a minute... and for the life of good... no pre-selection of where I want to search. That was a horrible idea from the start and needs to go.

Sorry for the longish post, that's just my two cents to bring offline search up to speed. Online search should be left to online search companies.

Share GMaps: Now wait for the next version. And then we'll see. The whole writing costs the developers unnecessary time.
Workaround from 0709: I have written to the developer about Android 13.
Search: Here, too, wait and see is the order of the day.  Besides, it doesn't belong here. There is a separate topic for this. Therefore no more contributions should come here.

Quote from: Jan Čapek on August 09, 2023, 13:41:39Yep, it is handy tool, but unfortunately the app isn't compatible with recent Android versions, nor is working offline.

@Jan - interesting/ thanks - yet another reason NOT to replace my 2017 phone (despite the very occasional/ rare LM4 deep down code exceptions that are too hard for Menion to fix).

Quote from: freischneider on August 09, 2023, 19:25:11Share GMaps: Now wait for the next version. And then we'll see. The whole writing costs the developers unnecessary time.
Search: Here, too, wait and see is the order of the day.  Besides, it doesn't belong here. There is a separate topic for this. Therefore no more contributions should come here.

@freischneider - it was the developer (by mistake) that wrote about online search in this topic. Next version - I had 4.18.0 & waited for what I thought was maybe fixed in 4.18.1. Honest misunderstanding. Sorry.

@Shara97
please check if any points are recorded when you simply keep the screen enabled and opened the side recording panel. If nothing happens when you stop recording, it most probably means there is nothing to save. Crucial is really checking if something records when the screen is on. When not, check the recording parameters of the used profile.

@Andrew Heard
we found some remaining issues in the app, so another bug-fix version will be during next week.

@Menion
Now I have installed the 4.14 version (but if I have to do a test I install the new version again...): however with the 4.18 version it definitely didn't score any points, the distance traveled always remained at zero (even the graph above was stationary ). But there was also another problem: although I had given the permissions to acquire the gps position, often after starting the recording it said that I didn't have these permissions... (only with this version did I have all these problems).
Hi thank you

Buddy tracking is super unreliable btw, if anybody still cares about that function. It stops working at least least five times per day and we have to manually turn it off and on to see our points again.

It always happens when network reception is bad for a while. Locus seems to mess up internally and never gets back on track.

Btw... if you have code in there like

if phone.isOnline()
  do_stuff();
else
  do_other_stuff();

that might be the main problem. Once you leave your LTE development couch and travel through the real world, your phone will quite often only THINK it's online... like in zero bars 4G or even Edge. Transmitting a single byte might take ages though or come back with a failure after some longish timeout. Quite likely Locus hickups on that... maybe if the network error timeout is longer than the tracking interval? Just guessing.

And nope... we're not in rural India... we're in the mountains of southern France right in central Europe. Buddy tracking still fails plenty.

There are obviously at least a dozen other things wrong with buddy support in general. But unless the likely answer is different from "not a priority" (as for the last five(?) years), I won't bother repeating myself over and over again. Ask if you want two more pages of neccessary fixes... or just go cycling with a buddy, then you might finally notice yourself and do something about it :-)

Quote from: joeloc on August 11, 2023, 18:45:39Buddy tracking is super unreliable btw, if anybody still cares about that function. It stops working at least least five times per day and we have to manually turn it off and on to see our points again.

It always happens when network reception is bad for a while. Locus seems to mess up internally and never gets back on track.

Btw... if you have code in there like

if phone.isOnline()
  do_stuff();
else
  do_other_stuff();

that might be the main problem. Once you leave your LTE development couch and travel through the real world, your phone will quite often only THINK it's online... like in zero bars 4G or even Edge. Transmitting a single byte might take ages though or come back with a failure after some longish timeout. Quite likely Locus hickups on that... maybe if the network error timeout is longer than the tracking interval? Just guessing.

And nope... we're not in rural India... we're in the mountains of southern France right in central Europe. Buddy tracking still fails plenty.

There are obviously at least a dozen other things wrong with buddy support in general. But unless the likely answer is different from "not a priority" (as for the last five(?) years), I won't bother repeating myself over and over again. Ask if you want two more pages of neccessary fixes... or just go cycling with a buddy, then you might finally notice yourself and do something about it :-)

I have experienced the LT fails so many times that I no longer use it.Unfortunately, I confirm that where there is reception difficulty, it freezes. I understand the technical difficulties and now I turn off data reception to save battery life.I prefer a tried and tested system I made with tasker based on text messages only, using only the telephone network is very reliable. The applicant asks for the position and the phone answers.

https://taskernet.com/?user=AS35m8kc9lYIafma1bmhSsdc5aW41wXP5NeuM1RwE0hptzS4hAh4n%2Fj3ZJVJ%2BEksDoEnzn7H%2FxM%2BAQ%3D%3D

Same what I do. Send position (plus retry if necessary), gmaps link and address on a regular basis, when hiking. Address lookup needs internet but failure is treated and won't stop task. Also I allow retrieval of position via incoming sms. Yes, SMS because it's the most robust system we can use.

PS. No love for "Multiple Variables Set"? 😀 I think %err is unreliable in case of SMS (that was my experience), I use additional "SMS Success"/"SMS failure" profiles (triggers). But more complexity then.

I just installed LM 4.18.2 and tested sharing POIs from the Google Maps app to Locus. Should be improved in this version.

Now a search list is displayed in Locus, which is mostly unhelpful.

Example: I click on a public toilet in Google Maps and share it with Locus. There, I am now shown a list with countless public toilets instead of the shared one.

Another example: I share the Kleistdenkmal (monument of Kleist) in Berlin, nearby Wannsee. Locus now shows in the list only the Kleistdenkmal in Saxony, 167 km away from the shared monument...

If I long click on the POI and then share it, it shows up correctly on the map in Locus.

All worked well ... until I switched to Alps.oam to create a route.
When I went back to my current home position the map appears only as a white map.
Sitched maps and themes (to elevate) ... no map is shown.
I tried the route planner ... and he works.
Only a LoMap is properly shown ....

Any ideas?

... after examing all settings I saw that the text size was set to 0.
Change to 100 produces a better result:

Quote from: jonny.blue on August 18, 2023, 23:09:16... after examing all settings I saw that the text size was set to 0.
Change to 100 produces a better result:

That's what you call a better result?  ;D

The google maps point sharing "fix" now extracts the points name from the funny url and does a new Locus "search" for that. It's unfortunately almost as unusable as before. I now tried it 10 times in real world situations (still being on an endless bike journey). 3/10 times Locus didn't find the point (by name) at all. 5/10 times if "found" something completely different by the same or a similar name, sometimes 100km away. 2/10 times it found the right thing.

Verdict: still an almost complete failure. re-searching in that way is not an option. if you cannot extract proper coordinates from a funny url, we're f*cked forever.

Apparently this "workaround point sharing fix app" that people here talk about manages to do it fine though. Too bad it's no longer supported and doesn't install on current Androids without jumping through hoops :-)

Quote from: joeloc on August 21, 2023, 18:00:35The google maps point sharing "fix" now extracts the points name from the funny url and does a new Locus "search" for that. It's unfortunately almost as unusable as before. I now tried it 10 times in real world situations (still being on an endless bike journey). 3/10 times Locus didn't find the point (by name) at all. 5/10 times if "found" something completely different by the same or a similar name, sometimes 100km away. 2/10 times it found the right thing.

Verdict: still an almost complete failure. re-searching in that way is not an option. if you cannot extract proper coordinates from a funny url, we're f*cked forever.

Apparently this "workaround fix app" that people here talk about manages to do it fine though. Too bad it's no longer supported and doesn't install on current Androids without jumping through hoops :-)

You are in the wrong topic. here was written so that it works only with the next version. 4.18.2.2. or 4.19.
https://forum.locusmap.eu/index.php?topic=8436.msg73062#msg73062

New Beta version 4.18.2.2

Major new change - LoRouter customization & warnings (https://forum.locusmap.eu/index.php?topic=8604.0)

Enjoy the weekend!

One of those ideas...  ;)

Online/Offline Lopoi (Eye toggle) to Presets

Reason: Better working together of Locus with themes. How? Themes can come up with no POI icons at all. I meanwhile have such a Layer in Tapiola. So Locus can exclusively display POI. And it would be convenient to turn everything on via preset.

New Beta version 4.18.2.3

We focused mainly on the "Warnings" & bug fixes.

So still a valid topic related to warnings - LoRouter customization & warnings (https://forum.locusmap.eu/index.php?topic=8604.0).

More updates in the "Customization" system will be introduced during the next months, but not in the coming version.

Enjoy the weekend!

Hi Menion, AFA is not working in this latest version. Wants to move the working directory. EXIT ...
TXs and cheers
Michael

Damn, you are right. In the recent app version is a major change in the "Target API" version that do again some changes in the file-system support. Hmm, AFA removed from the Google Drive and I'm going to look at it, thanks!

EDIT
uff, hopefully fixed

TXs a lot, Menion!
AFA operations seem fine so far. Only special behavior is attached.
I went back to the 4.18.2.2 beta yesterday, and as before, there was no screen like attached after start. Now, with the corrected 4.18.2.3 this screen appears. Hitting "confirm" triggered a successful start, though.
Fingers  crossed.
TXs and cheers and enjoy the weekend
Michael

This window jumps into the scene, from bottom to center, see video.

https://youtube.com/shorts/qqHwebVTvHw?si=jITJFYh_XwGBMkcv

Menion, can you add an expert setting which centers the map to the starting point of a track, when clicking see screenshot? I can only speak for myself, but at any time the starting point is of primary interest for me, track center and overview comes second.

Auto hide copyright:
When the screen is turned on, the copyright is immediately visible and stays on for 9s until it is hidden.
With the sidebars it is like this. They are hidden when the screen is turned on. They are only shown when I double click on the screen. Then they stay on for 9s and are hidden again. Can this behavior be done for the copyright as well. Or hide it already after 1-2s. I have a dashboard at the point and it is so bad Visible. 

@Tapio
The jumping window > weird issue in Android. Anyway hack was found, so will be fixed, thanks.

Centering on the start instead of "overview" > I'm not sure it is useful for now.

@freischneider
hmm indeed, thanks, will look at it

Hi to all,

version 4.19.0 published: https://forum.locusmap.eu/index.php?topic=8631.0

"Warnings" are currently in the online version, special MTB custom parameter as well. The task on next month is to get all this to offline LoRouter + finalize few more router customizations. Hope we will get some feedback from the usage ;).

Thanks again for the help with new version, appreciate it!