Messages

[@Graf Geo]

@Graf Geo
ah, how I've missed it? Thanks, fixed

Text rotation slowdown > not sure what happens on your device. I'll have to test it on some older phones. Anyway, there should be almost no performance negative effect.

Quick search > yes, more options are planned. This is the first testing option of how to integrate various search results into one screen ...

@Andrew Heard
web planner does not fill elevation to imported data. We do not have a fast online "Fill elevation" tool (yet). So original data should be preserved. Anyway, the difference in the slope may be in how Locus Map optimizes chart data. But to confirm precisely, shared track that causes this difference is welcome, thanks.

This is the limitation of the Locus Map implementation, not the BRouter. In the next Locus Map 4, alternative routes will be possible in testing mode for internal offline LoRouter only. The problem here is that alternative routes have a pretty bad performance and it's computation takes a lot of time. Unfortunately. That's why I hesitate to make this feature widely available ...

Hello,
Garmin maps are not well supported and to be true, I plan to remove this bad support completely. I'm aware that maps in Garmin IMG format are still used and may contain some interesting maps, but the complexity of correct implementation on Android is big and it simply is not worth it (at least for us), sorry.

If I see correctly, Michal answered the rest on our help desk.

Could you please share your planned route over the Web planner + info on which place this happened? Thanks

However, I remember a message from some time ago regarding a possible adjustment. Menion wrote that this solution would not be implemented because it could not be implemented within IOS due to security requirements within IOS. If I remember correctly, it was about improving search methods. Using an API from Google was then stopped.

Ah, that's a clear description, thanks. Btw. hope you are already fine!

Yes, I wrote this. iOS restrictions were one of the reasons here, but not the only one. I'm sure, I've explained this problem in "search topic". Simply: we need a robust united search system usable everywhere (Android, iOS, web) and dependency on Google is generally not possible, dot.

Anyway ... our logical dream is to have both apps "identical". This is anyway not possible and we will not push too much to this dream. In the app is already many many features that won't be possible on iOS and it is ok.

So no worry, Android won't be limited by iOS except cases, we do some global feature that needs!! to be united on all platforms.

Hello,
I'm not sure what you expect. Locus Map does not have any direct integration for 3rd live-tracking trackers, but offer an option to use custom trackers on your own. More about it here. You wrote that LiveTrack24 already has an API, so this should be correct solution.

Hi guys,
I'll try to answer all questions during next day or week. Anyway for now, one very interesting Beta version before the weekend. Let's call it "Beta 4.25.1.7, Release Candidate".

And the news? Enjoy it

   - add: text rotation for vector (MapsForge V4) maps
   - add: quick search results for features and settings in the base search
   - chg: improved loading of custom icons from external files
   - chg: updated top panel items dividers
   - chg: improved request to enable location when disabled in the system
   - chg: updated default function panels actions
   - chg: customizable speed for MTB, Gravel and Touring bikes in LoRouter
   - chg: removed (optional) caching of vector tiles
   - fix: incorrectly working hiding of bottom panel
   - fix: not working cache for WMTS maps
   - fix: min zoom limit for overlays
   - chg: many smaller tweaks and fixes

[Beta version 4.25.1.5]

Thanks guys, got it. What a stupid issue. On the line with the crash is a method that informed me, that this method is available since Android 15 (that's why it does not crash on my device), but it worked before without a problem (it is code I wrote a few years ago) and in the description of this method is "Available since Android 6". Uff, hope, there won't be many of such problems ...

Beta version 4.25.1.5 generated.

And APK size seems to be correct. There seems to be removed compression of some internal libraries, but the final size of the app on devices should be identical.

[Beta version 4.25.1.4]

Hi guys,

new Beta version 4.25.1.4 before the weekend.

4.25.1.4
  - chg: major! update of various libraries and whole build system and tools. Anything un-usual is a bug
  - add: (SILVER) remaining up and down elevation during the navigation to dashboard
  - add: support for "Array" option for BRouter external profiles
  - chg: improved color for background and popup menus in the dark mode
  - chg: load/unload app data now available on A10 as well
  - fix: (SILVER) reconnection of BT devices when BT was disabled in the system
  - fix: correct hiding of street bar during navigation when route does not have street info
  - fix: refresh of the list of map/nav cursors and it's deleting
  - fix: (SILVER) restore of top panel when restoring app and dashboard is active

Two important notes:

Firstly, there is a HUGE number of changed libraries (mainly some base Google libs) in the background together with an updated minimal Android version (RIP Android 5, now min. Android 6) and more ... hope, it won't cause any problems anyway I'll leave previous 4.24.1.3 available, just for sure (for downgrade is not needed un-install, all have identical 1142 version code).

Second, as I see, the new version of APK is a lot bigger. I do not know why yet, but it is some side-effect of changes in step 1. Anyway, I believe it won't cause any problems.

Thanks @Graf Geo , will be fixed in the next (Beta) version.

Hello,
graph smooth values a little, compared to raw data visible in the detail of the trackpoint. But in this case, the difference is quite huge. If you share a track with me, I'll gladly look at the reason. But I expect, there is some high single peak that is simply smoother by the chart a lot ...

[@Graf Geo]

Hi guys,

@Graf Geo
visual problem in the track detail > fixed, thanks

@Tapio
search click > fixed, thanks

@Andrew Heard
Notify center > hmm. Also because of some Android changes in how the long-running processes should be done, we will have to recreate a big part of this notify center system. So I'm sure, this will be solved next year (and some new bugs will be created  )

Map cursors dialog > thanks. I've noticed that also deleting of cursors does not work, so fixed as well.

Hi,
this is quite a complicated question that depends not just on the profile, but also on your preferences in certain situations.

In the case of BRouter available in the Locus Classic, you have to experiment or ask on the BRouter forum.

I may suggest trying some online routers, like the official BRouter web planner or our own planner that uses identical profiles as Locus Map 4. It may help to easier find ideal routing profiles for your tours.

Hi,
in case, you need a more complex map and do not want to recalibrate it, the TAR format should still work, so feel free to use it.

You may use SQLite format used by the app, or an almost identical but documented MBT file format for raster data.

I would also like to read more about this