Messages

[@T-mo]

@T-mo
- yes, the profile is used to compute times. Any big differences to reality?
- I'll think about it. This limit was created because GraphHopper service was paid and I had to reduce the amount of requests to be within certain limits. Anyway, I'll look at it ...
- graphical problem: how you did it? 

@Žajdlík Josef
Do you mean adding your own photos to our public LoPoints? This is currently a work in progress and will be available this year for sure. Otherwise please describe it a little more, thanks.

@balloni55
Thanks a lot balloni. I've just fixed the crash and updated the icon and generated a new version under the same ID, so just simply update to make it work again.

Hi, I made a very simple add-on mainly for myself but didn't want to keep it from you.

The add-on allows you to add a button to the main map screen for calling a configured phone number with a single touch.

How to use:



• Install the add-on from Play Store or via the APK file.
• From your apps screen/launcher, start "DirectCall Settings" and configure the desired phone number and additional settings.
• Re-Start Locus Map, tap the "set function panels" button, tap the "+" and then "Add function button". Select "DirectCall" from the category "Add-ons".
• Tap the newly added DirectCall button to start a test call. You may need to confirm the "phone" permission the first time you do this.

Features:

• Call a preconfigured phone number from the Locus Map main screen
• Optionally display a confirmation dialog before calling
• Optionally call with speaker enabled
• Starting "DirectCall" from your apps screen/launcher will also start a call, same way as the button in Locus Map
• DirectCall does not perform a VoIP call, but uses the default phone app on your device to start a regular phone call

Source code is available on

GitHub.

Menion, I have tons of large maps on SD card, even on older devices. There is no performance problem using them in higher ZLs (although for sure you can MEASURE a significant difference).
A DATABASE on SD however, I would not even try, because the effect is obvious.

[@michaelbechtold]

@michaelbechtold
we all are well aware this is the problem (Android 11+ limitations). On the second side, to be true, I'm still not convinced, this may be a major break in the app usability. I'm looking forward to next week when we finally find the correct answer.

Topic & voting: I've expected, it may be a task that should take quite a lot of time, that I currently do not have. So voting may help me better decide if this isn't the idea of just a few people here on the forum ...

Another fact is, that most Androids are NOT Pixels. But rather the majority employs external SD card support, to allow for cheaper storage extension.

This is based on known facts? We are talking about devices with Android 11. Most of the modern devices are created with bigger internal memory instead of support for external SD cards. Sure, SD cards are usually 4x time cheaper, I know. Also, I made just a quick benchmark, and LoMaps from the SD card (average class 10 card) is 9x slower than LoMaps from the internal storage. You are the one who fights for faster maps ...

@slarti76
Manual updated a lot, hope for good.

@Žajdlík Josef
Understand. To have fast maps, it will be necessary to limit number of maps on the device. As I wrote above, SD card, no matter what I do, will never be too fast.



New version MapGooglePlay_4.4.3.31 RC_1045 just published.

It should have mainly
- option to move mapsVector and SRTM directories to the private directory on the external storage (SD card)
- integrated links to manual pages

Let me please know mainly if this nighly update in custom directories will work correctly for all of you. Thanks

Menion,
[snip]

I really have to agree with Michael here. I have no problem to open a Help Desc topic, that's not the point. But this is too slow for this important topic. I have friends for whom I am the "Locus guru", but who would never take the time to log in on the help desk or whatever. And they all have big maps on extSd that they can't move to internal.
And I'm still not even sure from the Manual entry: Does Locus even offer to move all data to extSd instead of intSd on first start with new version? The manual is not explicit on this. I'm honestly not willing to try out Beta this time (even though I always do), because this is obviously a one way street. I would be ok if you say "Google forces my hand, for now you'll just have to do it, and you can move to extSd, but next I will implement way to divide big and small data between intSd and extSd". But making this dependent on a lengthy voting process is very disappointing - and potentially p***ing off many users. As Michael says, don't underestimate the amount of users with cheap phones with small internal SD, slapping a big MicroSD into the slot...

In the route details. Can I move the "hide" button to the bottom bar?

Haha... For me, "Hide" is maybe the most used command and "Share" amongst the least.

[@tapio]

So many ideas because of three tiny colored dots 

@tapio
the issue with a refresh of the track: thanks TODO

With a dual centering button, rotate icon should really be visible, it is intent. With this solution, you may simply disable rotation without affecting centration.

If "dual-mode" needs an extra rotation button was discussed a half year ago a lot and yes, it needs  .
Good sample: center, start rotating, move with the map - now disable rotation in case you do not have this "rotate" button.

@balloni55
ah, dot attached to centering button in case, rotation is disabled and dual-centering button is enabled, is a bug, thanks

@luce
ah, the clickable area behind ... not so simple task => is this really needed? I'm more thinking about and option to put these buttons into function panels - but this also is not so simple task 

Rotation mode
I also think that icons should not be so obtrusive. Some small "A", "M", symbols should be enough. I'm waiting on our graphic.

But, the indicator is needed from my point of view. If the map rotates by the GPS, it may not be clear that rotation is enabled. Also if you start rotation of the map manually, it may not be clear that the map won't rotate by sensor anymore.

@Žajdlík Josef
thanks, as I wrote to @balloni55, the dot attached directly to the big centering button is a bug, thanks!

And sorry if I warm up another old topic: The bottom and side bars are quite big using unnecessarily much map space while the zoom buttons that are used much more often are so small it happens repeatedly that I accidentally tap beside them.

I perfectly understand that bigger zoom buttons wouldn't look good, but is it maybe possible to make the surrounding transparent area touchable – to make the buttons in fact bigger without changing the look?

[@Žajdlík Josef]

@Žajdlík Josef
hmm, but you can simply solve this by a quick "Share" button on the main screen. I'm not sure if this is really a problem. Sharing the screenshot of a single point seems a little weird to me. Isn't it a lot easier to use for example sharing over Google Maps URL or a new URL to our web portal (first option)?

@tapio
there will be a big re-work of the whole search system in next year, really. I believe the whole UI will be redesigned and simplified ... thanks for understanding.

@ADiet
ah, ok.

[@Žajdlík Josef]

@Žajdlík Josef
Options for track naming are already visible in the latest new RC version.

@michaelbechtold
We discussed this for quite a long time last week and this is the result. Value you suggest, so {t}, {city}, {activity} should be quite long. Anyway, you are of course correct, that this change should not affect already existing recording profiles. I'll try to update it somehow. Unfortunately, profiles that already changed with this version, have to be modified manually, sorry for this.

[MapGooglePlay_4.3.3.7_1034_beta]

New version ***MapGooglePlay_4.3.3.7_1034_beta***
- major update in work with sensors
- distance markers for tracks!
- sharing of point/location to web planner page

@schugur
thank you very much for the logs. Unfortunately no useful data inside. Anyway, I still made some updates in the system how Locus Map deal with a power meter, so please give a try to this new version. May I ask for log if it fail again with this new version? It print little more info for me, thanks!

[@michaelbechtold]

@michaelbechtold
Everything in the private folder is the expected result ... start count with it. Deadly? ... hard to say.

Exception for full filesystem access is no way. Google does not provide exceptions. Anyway  I'll be more precisely test it next weeks, so I'll, of course, inform about the final result ...

@Žajdlík Josef
currently, it is not an ideal solution. Tap on the first button in the bottom panel, it may help ...

@slarti76
works? Fine

@T-mo
what you see was in the app till version 4.3.0. In this version was introduced new full-screen mode that causes quite a lot troubles so in this Beta it is reverted to the old system - so black top useless panel on some devices.

@Pcmann
isn't there settings in "Preset" that active together with navigation and that overwrite this settings?

It is enough to have them in the downloaded folder. The app will detect its presence automatically when searching for an offline address source.

New features in web planner
I am listing all the features added after LM4 lunch (April, beginning of May).

• Elevation statistics in the planner tab
• Altitude formatter - using only ft/m
• Saved track detail - added elevation chart
• Remove waypoint from the map - using context menu (right click)
• Modify planned route by drag&drop everywhere on the segment (previously only possible by red handle placed in the middle of the segment)
• Show / hide waypoints in order to prevent moving statistics out of the screen
• Recalculate all segments
• And several bug fixes and minor improvements

And we are working hard to bring you another set of new features soon. Thank you for your trust and support!

[@slarti76]

@slarti76
I'm checking if there is any reason for a delay and can't see anything suspicious. Video does not help here, so do not waste a time on it. Does also other screens and dialogs "lags" (some noticeable slow-down)?

@Žajdlík Josef
labels > good point, removed
route name > only recorded. Imported or planned has different names. Also, in the recent version, you may modify the pattern for the name of the recorded track, so ...

@freischneider
what about selecting a point on the big chart? There is already a system for zoom in/out and later display on the map. Seems that the "center" button does not work correctly now - fixed.

As I mentioned before, the display of the track detail as a bottom dialog is not possible on other screens than the main map. Technical limitation.

Change in time for BRouter downloader > little more investigating and I think I've got it, thanks. Try it with next version, hopefully, it will help with automatic updates as well. Because this issue caused that default "Disabled" value was used.